On 10/16/2013 2:18 PM, Greg Freemyer wrote:
On Wed, Oct 16, 2013 at 4:42 PM, John Andersen <jsamyth@gmail.com> wrote:
It seems to me that there was some noise on this list with systemD making this more complicated than it was in the past (it was never drop dead easy, unless, as mentioned you are sitting on a bunch of unallocated space).
Yes... it does.
If you have a initrd (which is default and almost everyone** has), then /usr is mounted via logic in initrd prior to the systemd even starting from what I understand.
--- **"everyone"=those who don't care as much about speed. The systemd reference pages suggest *NOT* using initrd for faster boot. Who knows, maybe suse will support faster boots in the future. Right now, they are still trying to cope with all the reqs and changes of systemd to get to secure EFI booting to produce appliance systems. I threw in a few crutches for the rest of the boot process in: /etc/rc.d/boot.d: S01boot.sysctl@ S01boot.usr-mount@ S02boot.udev@ S05boot.clock@ S06boot.device-mapper@ S06boot.loadmodules@ S06boot.localnet@ S07boot.assign_netif_names@ S07boot.cgroup@ S10boot.lvm@ S11boot.localfs@ <-- this is about 14secs from kernel unpacking. S13boot.klog@ S13boot.lvm_monitor@ S13boot.swap@ <--- and at ~16 secs... [ 10.200027] bio: create slab <bio-1> at 1 [ 10.843408] bio: create slab <bio-2> at 2 [ 14.414724] XFS (sdc3): Mounting Filesystem [ 14.485300] XFS (sdc3): Ending clean mount [ 14.492799] XFS (dm-3): Mounting Filesystem [ 14.676810] XFS (dm-3): Ending clean mount ... [ 16.374981] Adding 8393924k swap on /dev/sdc5. Priority:-1 extents:1 across:8393924k FS Kernel logging (ksyslog) stopped. --- Before that it's all HW startup... ~20-25 seconds later and all services are up. Basically I use the "boot" phase to setup the system to handle system services ... with systemd starting after the initial "boot" phase (or initrd phase)... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org