I read this article https://www.theregister.com/2022/04/27/fedora_starts_to_simplify_linux/.
The question is whether we can still use old laptops. I have an HP 6710b and it works very well at the moment with Fedora 36.
In this case, my opinion is that the development team will release a special Fedora Spin for laptops with old hardware. What do you think?
On Apr 23, 2022, at 22:36, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
> As far as I know there isn't really a technical argument for systemd
> or any particular systemd.* on Fedora workstations. The various
> traditional inits and daemons work fine in that environment.
There are several features in systemd that directly benefit the desktop.
1.) systemd service dependencies can ensure that the desktop environment doesn’t launch until all dependencies are met. The side benefit of this is that with parallel startup of services, the desktop launches faster, but it also launches with all the services it needs.
2.) systemd-logind helps contain desktop processes in cgroups, meaning that if you want it to, it will terminate all user processes *for that session* when it logs out. This is a huge thing for the enterprise desktop environments. For example, I managed engineering desktops and there was a particularly finicky circuit designer that loved to leave background processes that would survive logouts, and if another user logged in it would interfere.
But this process management also introduced resource management per-user session, so you could ensure a single user couldn’t abuse the system. This was also important to me, since we had multi-user systems running graphical sessions via VNC, and we wanted to make sure one user didn’t overwhelm the system.
3.) systemd now launches your GUI. You have your own private systemd --user running every time you log in. This process launches services and apps, maintains your environment, and can run other systemd units such as timers. This gives you a similar interface to system services, scoped just to your account. Since there’s only one user systemd per user, you can launch a process that can be used and managed by both the graphical login and a ssh session. (This is actually annoying to me, since it means stuff like Kerberos and AFS works differently than it used to)
4.) the desktop session output and error are captured in the journal. Previously init systems had user console lost to the user. There was some attempt to capture the X logs and the gnome session, but in systemd each user unit can be individually examined with journalctl.
This is just stuff off the top of my head. While I do agree that there has been a lot of focus on server with systemd, a lot of cool things (like unit templating) were introduced because of systemd on workstations. Don’t forget that nearly all the common benefits of systemd also help desktops, because at its core, it’s the core init system to launch the OS.
Well, merged into kernel some weeks before likely means that it will be a
few weeks before the kernel.org with it is released, and it will take weeks
to month or more after that before fedora updates has that kernel.
And merged into the kernel also means that there are almost certainly still
going to be some sorts of bugs for a while.
And the management of access times and such means that you would have
likely written to the metadata (if you read any files) if the
implementation handles updating access times.
And there are now articles saying that code that was merged into the kernel
has a bunch of patches waiting to be accepted, and the maintainer has not
responded to any of those requests and that new NTFS code is suspected to
have immediately been orphaned by the company that asked for it to be
merged and agreed to help support it. The articles indicate the linux
kernel is working though what is going on with the maintainer.
On Tue, Apr 26, 2022 at 10:28 AM Lily White <lilywhite2005(a)outlook.com>
> I didn't mount as readonly, but I didn't write to it also. I'm
> speculating that the implementation on Fedora and macOS are broken in
> the same way so that they can actually read each other's broken output.
> I thought that NTFS supported just got merged into the kernel some weeks
> before? Anyone know about the progress?
> On 4/26/22 05:16, Patrick O'Callaghan wrote:
> > On Mon, 2022-04-25 at 10:41 -0500, Roger Heflin wrote:
> >> On Mon, Apr 25, 2022 at 10:11 AM Lily White
> >> <lilywhite2005(a)outlook.com>
> >> wrote:
> >>> I got a spare drive and it does work (at least for now, this drive
> >>> worked for a while before everything broke). So I sent my old drive
> >>> back
> >>> to Sandisk and I'll see if it was with that specific model.
> >>> I'll also wait for some time and see if wear and tear may cause
> >>> problems.
> >>> What's interesting is that the broken drive works on both Fedora
> >>> and
> >>> macOS, but not Windows. That's why I didn't speculate the drive
> >>> itself
> >>> was broken before.
> >> I am going to bet that the NTFS code is very similar on Fedora and
> >> MacOS.
> >> So likely it is a code bug or a usage bug (see comments below).
> >> you did make sure to umount it on Linux/BSD before removing it right?
> >> And if you hibernate the machine(any os) and remove the usb device
> >> while
> >> hibernated the filesystem may not be consistent, it has to be
> >> explicitly
> >> unmounted on both windows and fedora before removal so that all data
> >> is
> >> fully written.
> >> In the past it was suggested to not use NTFS as a transfer drive and
> >> to use
> >> something simpler like FAT32 as that fs's format is better documented
> >> and
> >> simpler than NTFS. That may or may not still be the case.
> > Most NTFS installation on Linux use a user-space implementation via
> > Fuse, which is known to have some limitations (IIRC it's fine for
> > reading but might be problematic when writing). A new kernel-based
> > implementation is apparently on the way and is said to have a higher
> > degree of compatibility.
> > poc
> > _______________________________________________
> > users mailing list -- users(a)lists.fedoraproject.org
> > To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct:
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > Do not reply to spam on the list, report it:
> From LilyWhite with love
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> Do not reply to spam on the list, report it:
I'm trying to execute a user systemd function from /etc/rc.local: 755,
My thought is to use su. Is there a better way?
This is where I'm at now.
su --login mike --command=systemctl --user start <some service>
Anybody know how to accomplish this? I personally know about 100 ways
to do it wrong ;D
On 2022-04-28 00:04, users-request(a)lists.fedoraproject.org wrote:
> I think the answer's going to depend on the age.
> I have a 2007 era laptop that still works, though its battery doesn't,
> and is painfully burdened by modern Gnome. But managed Gnome from way
> back then quite acceptably. It has a no-longer supported NVidia
> graphics chipset (NVidia removed drivers for that model some time ago).
Very old nvidia drivers may not be available through rmpfusion but
drivers back to the 304 series for Geforce 6 chips are still available
on nvidia.com. You just download and install the rpm.
I have an IBM T60 which was first introduced in 2006. Like your laptop,
the battery is very short-lived, but the computer works fine. Presently
running Fedora 35 with, iirc without looking, the 340 series nvidia
driver (Geforce 9600 gpu, I think).
Removing the legacy BIOS boot is a step backwards and will hurt a large
number of Fedora users who are, in the end count, a large testing group
for a cutting edge distro.
I'm having an odd problem. On two of my laptops, on which I've just done
fresh installs, I cannot get the external monitor to work. Using either
the XFCE display configuration tool, it shows up, but it's marked as
'disabled'. I do not seem to have the usual such tool under KDE, which
is one of my puzzles.
The install was done the same way in both cases, and somewhat
non-standardly, so I'm guessing I might be missing some package(s). I've
had trouble using KDE with Wayland, so I installed the XFCE spin, then
installed KDE via dnf, so Wayland does not get loaded, and is not even
Graphics processor on this machine is AMD Renoir. It's a System 76 Pangolin.
i was convinced that i was running wayland on my F34.
i see ... in my env,..
but inxi -G sez,...
Device-1: Intel HD Graphics 530 driver: i915 v: kernel
Device-2: NVIDIA GK208B [GeForce GT 730] driver: nouveau v: kernel
* Display: server: X.Org v: 18.104.22.168 driver: X: loaded: modesetting
unloaded: fbdev,vesa gpu: nouveau resolution: 3840x2160~30Hz*
OpenGL: renderer: NV106 v: 4.3 Mesa 21.1.8
so, which is it? wayland or no wayland??
So after updating my system and rebooting, I found all of my audio settings
I know it's "new" and all, but when are things going to settle down?
$ dnf history info 287 | grep pipe
On Mon, Apr 25, 2022 at 10:11 AM Lily White <lilywhite2005(a)outlook.com>
> I got a spare drive and it does work (at least for now, this drive
> worked for a while before everything broke). So I sent my old drive back
> to Sandisk and I'll see if it was with that specific model.
> I'll also wait for some time and see if wear and tear may cause problems.
> What's interesting is that the broken drive works on both Fedora and
> macOS, but not Windows. That's why I didn't speculate the drive itself
> was broken before.
I am going to bet that the NTFS code is very similar on Fedora and MacOS.
So likely it is a code bug or a usage bug (see comments below).
you did make sure to umount it on Linux/BSD before removing it right?
And if you hibernate the machine(any os) and remove the usb device while
hibernated the filesystem may not be consistent, it has to be explicitly
unmounted on both windows and fedora before removal so that all data is
In the past it was suggested to not use NTFS as a transfer drive and to use
something simpler like FAT32 as that fs's format is better documented and
simpler than NTFS. That may or may not still be the case.
Xfce's bluetooth manager find my Jabra 85h but
when I try to pair with it, I get "Disconnected"
# rpm -qa | grep -i blue | grep -v fish | grep -v bird
# dnf install pulseaudio-module-bluetooth
Problem: problem with installed package
- package pipewire-pulseaudio-0.3.50-1.fc35.x86_64 conflicts with
pulseaudio provided by pulseaudio-15.0-2.fc35.x86_64
When I try to pair, journal give me:
bluetoothd: src/device.c:load_gatt_db() Unable to load key file
from /var/lib/bluetooth/00:19:0E:19:3F:C4/cache/7F:A5:9F:E8:AA:26: (No
And there really is no file of that name:
# ls -al /var/lib/bluetooth/00\:19\:0E\:19\:3F\:C4/cache/
drwx------. 2 root root 4096 Apr 22 19:15 .
drwx------. 4 root root 4096 Apr 22 19:15 ..
-rw-------. 1 root root 1078 Apr 22 19:15 30:50:75:48:88:97
-rw-------. 1 root root 29 Mar 21 20:31 CC:82:EB:4C:D5:D5
What is interesting is that 30:50:75:48:88:97 says it is
my Jabra 85H
Name=Jabra Elite 85h
If I erase the cache and start over, the same thing
happens. A new file is created but the error log
says it can't find a different file.
Yours in frustration,