[opensuse] Re: disk device names and libata
Le 12/12/2009 18:40, Lars Müller a écrit :
Till now I've only found one use case where the old approach is an advantage. if you have to build a fstab by hand, the new system is very difficult :-(
jdd -- http://www.dodin.net http://valerie.dodin.org http://news.opensuse.org/2009/04/13/people-of-opensuse-jean-daniel-dodin/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2009/12/12 18:56 (GMT+0100) jdd-gmane composed:
Lars Müller wrote:
Till now I've only found one use case where the old approach is an advantage.
if you have to build a fstab by hand, the new system is very difficult :-(
+1 But, thank goodness that in fstab the easier old LABEL= method works as always since its original introduction long before libata. Too bad it's broken for getting booted. http://bugzilla.novell.com/show_bug.cgi?id=483136 :-( -- " We have no government armed with power capable of contending with human passions unbridled by morality and religion." John Adams, 2nd US President Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, Dec 12, 2009 at 06:56:44PM +0100, jdd-gmane wrote:
Le 12/12/2009 18:40, Lars Müller a écrit :
Till now I've only found one use case where the old approach is an advantage. if you have to build a fstab by hand, the new system is very difficult :-(
Are you still using [ ] uucp [ ] lilo [ ] elm ? No, I honestly don't like to know the answers. ;) And yes, as it is weekend even this was again a trial of a joke. Or to ask with as less shaking head: How often are you _creating_ or even touching /etc/fstab by hand? 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. An alternative approach is to use disk labels. As this requires additional input and knowledge from the user it's harder to automate while the initial setup. See section "6. Labels" of the "Linux Partition HOWTO". For reierfs see reiserfstune. Independent of the disk device name topic it might be usefull to suggest the utilization of filename completion in the editor of choise[1]. Now cake is waiting in the citchen ... Lars [1] for vim see http://www.linuxjournal.com/article/3805 for emacs http://www.emacswiki.org/emacs/Icicles_-_File-Name_Completion_Tips might provide the required starting point. -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-12-12 at 20:12 +0100, Lars Müller wrote:
if you have to build a fstab by hand, the new system is very difficult :-(
Are you still using
[ ] uucp [ ] lilo [ ] elm
?
No, I honestly don't like to know the answers. ;) And yes, as it is weekend even this was again a trial of a joke.
:-)
Or to ask with as less shaking head: How often are you _creating_ or even touching /etc/fstab by hand?
Me? Quite often. And cryptotabwhatever, too O:-)
An alternative approach is to use disk labels. As this requires additional input and knowledge from the user it's harder to automate while the initial setup. See section "6. Labels" of the "Linux Partition HOWTO". For reierfs see reiserfstune.
Actually, the YaST partitioner manages them. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAksj//UACgkQtTMYHG2NR9XoXQCeILIckOqtxO7aZAW2T6Opc8r8 n+8An3cppDvc297kiOYKIToCKemo0mm/ =EFrL -----END PGP SIGNATURE-----
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, never gets VFAT options the way I want them, and usually doesn't even get EXT3 options the way I want them. I don't even want to think about using YaST to do my NFS entries.
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. That's just too long a space-free string for any purpose other than pasting a URL into a browser's location window.
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 -- " We have no government armed with power capable of contending with human passions unbridled by morality and religion." John Adams, 2nd US President Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-12-12 at 18:56 +0100, jdd-gmane wrote:
if you have to build a fstab by hand, the new system is very difficult :-(
I don't find it difficult. Tedious, perhaps. Though, a YaST fstab editor would be nice. Part of the code could be reused from the YaST partitioner ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAksj/zsACgkQtTMYHG2NR9X7LwCfUxxn4D5L42oAwOzDgeFAmQHe s44AoIVlI2Rwn/Wzy7vfhewimowO/lSc =YgX0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2009/12/12 21:38 (GMT+0100) Carlos E. R. composed:
On Saturday, 2009-12-12 at 18:56 +0100, jdd-gmane wrote:
if you have to build a fstab by hand, the new system is very difficult :-(
I don't find it difficult.
I find editing difficult any time I'm editing a file with lines of more than about 79 chars or with (unspeakable) words of more that about 20 chars, particularly when several or more very similar long words are on adjacent or nearly adjacent lines. Kernel lines in menu.lst that include strings like /dev/disk/by-label/ata-ST3320620AS_6QF3PJXC-part10 invariably are longer than a typical editor window width, and thus wrap, besides including words around 50 chars long. The same goes for lines in fstab when the options column contains more than just "defaults" and/or when fstab is tabbed out for ease of reading instead of just spaced. -- " We have no government armed with power capable of contending with human passions unbridled by morality and religion." John Adams, 2nd US President Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-12-12 at 16:24 -0500, Felix Miata wrote:
On 2009/12/12 21:38 (GMT+0100) Carlos E. R. composed:
On Saturday, 2009-12-12 at 18:56 +0100, jdd-gmane wrote:
if you have to build a fstab by hand, the new system is very difficult :-(
I don't find it difficult.
I find editing difficult any time I'm editing a file with lines of more than about 79 chars or with (unspeakable) words of more that about 20 chars, particularly when several or more very similar long words are on adjacent or nearly adjacent lines.
I just copy-paste them; and labels are shorter, when they can be used.
Kernel lines in menu.lst that include strings like /dev/disk/by-label/ata-ST3320620AS_6QF3PJXC-part10 invariably are longer than a typical editor window width, and thus wrap, besides including words around 50 chars long.
They don't wrap on the editors I use, or I disable wrapping. I use joe or mcedit.
The same goes for lines in fstab when the options column contains more than just "defaults" and/or when fstab is tabbed out for ease of reading instead of just spaced.
I use very long lines in fstab. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkskC4gACgkQtTMYHG2NR9XUBQCdGLApcPF+zOzWNfWMYXPcpKyy c8gAn2prNu9M+KJTfR9pSMbc/foGp7nL =JoUw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carlos E. R. -
Carlos E. R. -
Felix Miata -
jdd-gmane -
Lars Müller