An alternative idea to help work round the desktop developers dislike
of worrying about / & /usr/{bin,lib/etc} seperation issues.
On 2 July 2011 20:33, Linda Walsh
Rob OpenSuSE wrote:
I said: I'm booting from my Hard Disk -- Not from a RAM DISK.
There is no 'initRD'. Thus there are no drivers available to the kernel until it mounts the disk. Maybe it was in a different thread, but I had problems getting my own kernel to boot properly from the suse initRD. For some reason I couldn't get any console output during boot until I hit the login prompt.
So it indeed booted with an initrd but you found a bug about console output... I thought this was a general discussion about systemd and distro support for boot process, my response was not intended as specific comment on your personal choice of setup, including self building a kernel; though I advised ppl not to bother with that and use generic, from SuSE 7.1 or so, and Red Hat 6.0 days; as the fashionable optimisation at time, was IMO more trouble than it was worth for 99% of newish systems..
you can have race conditions -- AND a journaling file system only adds to those potential problems. However, as I understand it, Grub was fixed some time ago.
Now I just noticed watching a hibernate on my Tumbleweed box that the kernel, is now "freezing" applications and quiescing the disk, which is a new feature which crept under my radar. That actually works more generally, than GRUB code (16 bit?) having to deal with all the complexities of FS's like ReiserFS & BTRFS in a "live" state. Isn't it great that Linux is developing, improving and changing at a pace, rather than being STUCK for the convenice of some Enterprise SA department who love paper pushing & certification! :) Rob -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org