Anton Aylward wrote:
Linda Walsh said the following on 04/12/2013 10:19 PM:
Anton Aylward wrote:
Linda Walsh said the following on 04/11/2013 09:59 PM:
Also, it's not just about / and /usr, but also /usr/share --- at least a few current booting progs make use of it, Would you care to be more specific - tell us exactly what those are and where they occur in the boot sequence, please.
They are in areas that were used as reasons to move files from '/' to '/usr/... what I would mostly call 'services'...
Again that's a bit vague. Can you be specific. I can't see any services that move files that way.
Services like DNS, Apache aren't part of the boot.
Not an issue.
Are you talking about what are symlinks between /bin and /usr/bin? I suppose that gets back to your question about PATH.
--- Which most programs handle with no problem, but systemd wants to revert to hardcoded paths... that a step backwards.
Personally I think you're asking the question the wrong way round. I think you need to ask "what binaries are needed by the shell to get the system booted". Of course that means different things to different people. Some people think 'booted' means "all the way to the graphical login prompt". I don't. I think it means "to a state where it can begin to execute and run programs in user space".
----
If we look at it like that, then being able to run the shell, being able to run all those goodies in /usr/bin, isn't part of booting.
--- Ok -- most basic: mount. How do you mount /usr if it has been moved off root onto /usr? Most or all of coreutils. lvm, dm-setup, udev -- all of those now need /usr as their libraries were moved to /usr/lib64. I asked why I couldn't run boot off of disk and boot /usr/ first thing then continue with the rest of the normal suse boot. I was told that couldn't be done because mount (and lvm and dm_eventd all require usr now (or an image of usr on initrd)). That didn't used to be the case. Those are the ones I'm complaining about.
The whole point of the initrd is that it should contain all that is needed to boot, all the binaries and libraries, before they become available in the file system hierarchy.
---- I want the systemd recommended optimization of getting rid of initrd and booting from disk. It's an optimization I put in 10 years ago and it cut boot time by 50%. I don't want to go back to slowboot. Second thing is when things go wrong, I want to be able to come up on my root if possible to fix it. That way I can boot with the kernel I'll need to come up -- and when I get it running, I can just say 'go'. I don't have to reboot from a rescue disk or pivot root off of an initrd. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org