On Fri, 2011-07-01 at 15:36 -0700, Linda Walsh wrote:
Felix Miata wrote:
On 2011/06/30 15:54 (GMT-0700) Greg KH composed:
So what have we done that break things that were not fixed? Daily/constantly I'm reminded of https://bugzilla.novell.com/show_bug.cgi?id=584493 on boxes running openSUSE kernels but not on openSUSE running vanilla kernels or in other distros.
Moving to grub, before it was ready...
I've had SuSE then openSUSE on my desktop(s) / laptop since 9.4. I've never once experience boot issue regarding grub. And I typically use fairly 'advanced' configurations.
and thus dropping support for XFS for a while (not sure if it is officially supported again, yet, or not, but still seem to remember getting a message about boot problems with root on XFS in last install).
XFS works well, I've never noticed it not supported. SIMPLE RULE: Create a 256MB ext3 /boot partition. I do this on every box running any distro - and as I said - I've never had a boot issue. Then put everything else in LVM on whatever filesystem you like.
and dropping support for booting from YOUR HARD DISK (instead of a RAM DISK); As a result of this, and not using the SUSE boot-ram-disk, with all it's hidden operations, I wasn't able to get output turned on the console until AFTER full boot (login prompt). With suse kernel -- got full kernel output during bootup, with a vanilla kernel booting with no-ram disk, was not able to get it to give any output -- same kernel with lilo loads fine (this was earlier in the 11.x series, don't know about now, dropped grub and haven't looked back!).
I don't think people who play with kernels count as 'typical users'. If you play with kernels you know (a) to keep backups (b) have a fail-over strategy and (c) read release notes. Someone who plays with kernels and doesn't a, b, & c has nobody to blame but themselves.
As a result, I lost the ability to do snapshots in 11.2 after some kernel update about a year ago.... Required a knew lvm lib...but that was part of the boot rpm and well enmeshed!... (Maybe it will work now on 11.4, but am a bit wary of trying it, since once opened, there was no way to close a snapshot (it would just eventually overflow and become corrupt)... Or support for linking modules into the kernel, vs. dynamically loading them -- several RC scripts would fail trying to load a module that was already loaded... not bother to check /sys/modules....) There's been TONS of issues over the years with each new update making the boot process more difficult and making everything that follows more difficult. (Like not being able to update LSM, without updating my boot-ram disk which I didn't use...)...etc...
In part this is due to the increasing complexity of booting a modern system - I see all the above as an argument for systemd. Something has to change. As a professional system's admin of 15+ years... the boot / startup process and scripts have reached a rather boggling complexity and tree of interdependency. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org