On Sat, Feb 10 2018, Rich Freeman wrote: > On Sat, Feb 10, 2018 at 10:02 PM, allan gottlieb <gottl...@nyu.edu> wrote: >> On Sat, Feb 10 2018, Rich Freeman wrote: >> >>> >>> Interesting. Does /sbin/reboot exist? >> >> gottlieb@E6430 ~ $ ls -l /sbin/reboot >> lrwxrwxrwx 1 root root 16 Jan 28 13:08 /sbin/reboot -> ../bin/systemctl >> >>> What does "qfile /sbin/reboot" return? >> >> gottlieb@E6430 ~ $ qfile /sbin/reboot >> sys-apps/systemd (/sbin/reboot) > > Ok, your systemd is built with USE=sysv-utils. > >>> Ultimately it comes down to whether you care about the compatibility >>> symlinks. It probably isn't a bad idea to have them though. Maybe >>> some day you'll install a UPS and its shutdown scripts will just call >>> shutdown/poweroff/etc and not work. Software that shuts down using >>> either systemctl or dbus would be fine. >> >> Since you lean toward having the symlinks, why is the new default for >> the use flag on? Upstream? > > When the flag is on the symlinks are created. They're only missing > (from systemd) when the flag is off. > >> Also why do I have the symlinks with the 236-r5 system, contracting the >> news item. (This is true for both machines.) > > You have them because the default is USE=sysv-utils, which installs > the symlinks. > > The real question is why euse didn't show you has having the flag > enabled. That I'm not sure about. It shows it as enabled on my > system. I'd have to dig into where it is getting its data and how > this might get out of sync. > > To avoid a second email - a lack of depcleaning might explain why > software like openrc/netifrc is still installed. I don't believe it > has anything to do with the output of euse.
Thank you (and dale) again. allan
