[opensuse] Bugs: in SuSE11 - Grub boot & fsck.xfs 'enhancement'[sic]
Rajko M. wrote:
I don't see problem.
The /boot/grub/menu.lst has /dev/disk/by-id/ata-WDC_<...1> and /dev/disk/by-id/ata-WDC_<...2> entries.
If that syntax is supported, I'd have never brought this issue up. But that wasn't the syntax that the SuSE installer placed in my boot file. It clearly put in /dev/sda. I know I didn't manually create a custom grub file to boot from when I installed the system. I barely know how to do that with lilo! :-) Not to mention the overblown, pompously named "GRand" Unified Boot" loader. A grub -- bringing the image of an ugly gross thing thing (sample of especially ugly one: http://upload.wikimedia.org/wikipedia/commons/thumb/5/59/Witchetty_grub.jpg) that roots around in the dirt eating eating the roots of of my plants causing them to wilt while the grub grows into a nasty *bug* (a beetle or scarab, to be more precise), while my software, it's roots eaten tries to boot into some wilted expression of a running OS if it boots at all -- WHAT a horrid, perverted name for a boot loader considering it eats at the roots of what is trying to spring from the soil. *Cough*, but I digress....if that syntax is supported by "Grub" (involuntary yuck), why isn't SuSE using it? If it isn't, isn't that a fundamental bug or flaw in how SuSE is setting up the boot-params in grub? It seems if SuSE is converting to 'permanent' device names, it's majorly missing out on the most basic steps of ensuring that the machine boots properly. As for the "numbers" at the end of /etc/fstab being a directive for 'fsck's order to check disks in -- "technically", my bad for not indulging in 'SuSE's rigid bootup procedures regarding XFS. XFS doesn't have an 'fsck' command. It was originally a 'no-op' and apparently was "enhanced" (bug added), to check for device existence and return failure on device non existence. If the device isn't there, there is not file system to check, so there can be no BAD file system. Duh! Bug # two. Took me a while to get into a mental state of being able to properly figure out why these issues where bugs. The fact that all the "helpers" take all these "problems" for granted is only a symptom/feature and proof of linux's (SuSE's) continued unfriendliness -- and even migration toward increased 'non-fault-tolerance' (vs. a fault-tolerant system that tries to do the right thing (or at least something "productive" rather than just throwing out a syntax or fatal error and dying). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 07 May 2009 11:54:45 am Linda Walsh wrote:
Rajko M. wrote:
I don't see problem.
The /boot/grub/menu.lst has /dev/disk/by-id/ata-WDC_<...1> and /dev/disk/by-id/ata-WDC_<...2> entries.
---- If that syntax is supported, I'd have never brought this issue up.
If it wouldn't be supported then I couldn't give sample.
But that wasn't the syntax that the SuSE installer placed in my boot file. It clearly put in /dev/sda. I know I didn't manually create a custom grub file to boot from when I installed the system. I barely know how to do that with lilo! :-) Not to mention the overblown, pompously named "GRand" Unified Boot" loader.
A grub -- bringing the image of an ugly
Different languages have different associations to the same word. I would not try to explain how dangerous is improper accentuation while ordering pizza in some languages that I know. Besides, GRUB syntax is easier on user then to YaST Boot Loader. I remember that your system admin skills are better then mine, so don't tell me that you can't get it. :-)
*Cough*, but I digress....if that syntax is supported by "Grub" (involuntary yuck), why isn't SuSE using it?
Yours was probably taken over from old installation that had such entries and YaST was just a obedient servant. There was many complaints on very long entries, so I can imagine that YaST doesn't change anymore what user set up. It just takes those settings to new installation.
If it isn't, isn't that a fundamental bug or flaw in how SuSE is setting up the boot-params in grub? It seems if SuSE is converting to 'permanent' device names, it's majorly missing out on the most basic steps of ensuring that the machine boots properly.
File bug report, and don't forget logs in /var/log/YaST2/ that can explain what happened.
As for the "numbers" at the end of /etc/fstab being a directive for 'fsck's order to check disks in -- "technically", my bad for not indulging in 'SuSE's rigid bootup procedures regarding XFS.
XFS doesn't have an 'fsck' command. It was originally a 'no-op' and apparently was "enhanced" (bug added), to check for device existence and return failure on device non existence. If the device isn't there, there is not file system to check, so there can be no BAD file system. Duh!
I told you that you have good eye :-) Though fstab can be another thing taken over from old installation.
Bug # two.
Took me a while to get into a mental state of being able to properly figure out why these issues where bugs.
The fact that all the "helpers" take all these "problems" for granted is only a symptom/feature and proof of linux's (SuSE's) continued unfriendliness -- and even migration toward increased 'non-fault-tolerance' (vs. a fault-tolerant system that tries to do the right thing (or at least something "productive" rather than just throwing out a syntax or fatal error and dying).
When you spend on a computer too much you get used to problems and use workarounds. That is why old guard can't see problems even when they are evident, but in this particular case, file bug reports. It is easier to discuss things when one can see logs. -- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Linda Walsh -
Rajko M.