Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-11-14 01:31, Linda Walsh wrote:
I have no initrd -- and I never saw this solution proposed on this (as someone else calls it, "development discussion" list -- and they thought this wasn't a development issue?).
I did.
You need initrd- If you do not want to use it, then you will need to hack your own solution.
WHY should one need initrd -- just for systemd, no? the linux kernel doesn't need initrd. Why force all customers/users to use it? Just because of systemd? Why would you slow down all customers because of systemd? Why would you no longer support booting directly from a hard disk? Even windows doesn't required a preboot kernel. Yet linux does? Note -- I tried it -- it made debugging boot problems *impossible*. I can't boot single user off of an initrd and bring up my system manually -- as I have had to due more than once (most likely chances of needing it are during a suse distro upgrade (at least since 12.1).. I tried to use the native BIOS modes to display text -- but the boot disk was one-closed monolithic 'thing' that prevents easy debugging and modification of the boot process. At the time, grub wasn't able to boot off my hard disk due to it being incompat with my file system, and suse's initrd wasn't compatible with lilo -- I wouldn't get any output during boot until the login prompt. I was trying to enable 'control-s/control-q' in main boot script to be able to read some error messages as they flew by as they were not logged to disk before the system was crashing. initrd set it's own mode and ignored the files in /etc/init.rc on the root disk. I.e. it was a nightmare to work with. It was also the case at the time that many of grub's features wouldn't work without the kernel already running (like looking up disk labels), so. If it required booting a kernel to support grub -- (I don't know about now), it somehow seemed insane to load some unrelated kernel that generated warnings about missing modules during the mkinitrd phase, that took 3X time to make, just to support a boot util that didn't work natively with my fs. I don't see why there is this drive to make the boot process opaque and unmaintainable/modifiable/debuggable to users when that's the critical time when I need it to work the most. about missing modules during the mk-initrd phase (because they were modules that were built-in to the kernel) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org