Re: [opensuse] disk device names and libata

On Sat, Dec 12, 2009 at 04:35:06PM -0500, Felix Miata wrote:
On 2009/12/12 20:12 (GMT+0100) Lars Müller composed:

Or to ask with as less shaking head: How often are you _creating_ or
even touching /etc/fstab by hand?

Routinely. YaST never gets HPFS or my MSDOS options right,

Then this is a case for bugzilla.

never gets VFAT
options the way I want them, and usually doesn't even get EXT3 options the
way I want them.

YaST doesn't even get many things like I'm used to do it. The question
is if this is a bug in YaST or in my head?

I don't even want to think about using YaST to do my NFS
entries.

Same as with the weather. I'm very happy YaST doesn't touch it. ;)

And it's still up to you to use /dev/sd*. But here we're at the
starting point of this thread. This even includes the risk to end with
an unbootable system as soon as you (have to) change something.

Compared to that the requirement to use approximately 60 additional
chars is negligible. At least to me. YMMV.

/dev/disk/by-label/ata-ST3320620AS_6QF3PJXC-part10 is just not something I
can get my head around to start with, much less remember.

I have all the ata and scsi IDs of all of the systems I use in my head.
;)

No, I don't care about them. I simply let the tools use them. If it is
vi or emacs or any other editor. All are able to manage this file. As
are able to disable line wrapping.

That's just too
long a space-free string for any purpose other than pasting a URL into a
browser's location window.

This sounds like you compare apples with peaches. The content of
/boot/grub/menu.lst is not intended to win the Mr File of the year
award. The purpose is to ensure reliable booting.

An alternative approach is to use disk labels.

I've been doing that several years, but the easy way to use labels has been
broken for nearly a year: https://bugzilla.novell.com/show_bug.cgi?id=483136

That's bad. In particular as Harald offered a patch with comment 12.

a) osc branch -c openSUSE:Factory mkinitrd
b) quilt setup mkinitrd.spec
c) cd mkinitrd-2.5.10/
d) quilt new mkinitrd_bnc483136.diff
e) find -type f -name boot-storage.sh
f) $EDITOR ./scripts/boot-storage.sh
g) quilt refresh
h) cd .. && rm -rf mkinitrd-2.5.10
i) osc add mkinitrd_bnc483136.diff
j) $EDITOR mkinitrd.spec to add the required Patch1 and %patch1 lines
k) osc build standard x86_64 mkinitrd.spec # testing if it builds
l) osc cv # add some chnage log with a reference to bugzilla
m) osc submitrequest -m "- Try to make root=LABEL work; (bnc#483136)."
home:lmuelle:branches:Base:System mkinitrd Base:System
created request id 26331

Less than 15 minutes even on Saturday evening.

The openSUSE Build Service and the osc command simply rock!

Lars
--
Lars Müller [ˈlaː(r)z ˈmʏlɐ]
Samba Team
SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

Attachment: pgpd1CT5B7Cue.pgp
Description: PGP signature

Relevant Pages

  • Re: [opensuse] what does 127.0.1.1 mean?
    ... If you did it with YaST, ... The main problem with manually writing the zone files is that ridiculous syntax. ... host 192.168.1.1 ... That's bugzilla matter, by the way;-) ...
    (SuSE)
  • Re: [opensuse] Yasts Zypper is Stuck Again
    ... Yast isn't the only kde4 app that does this, but I didn't know whether the dialogs called by yast would be common kde stuff or yast specific. ... You don't need to worry about that, if you create a bug in novell's ... enter it in novell's bugzilla. ...
    (SuSE)