Lars Müller wrote:
On Sat, Dec 12, 2009 at 04:29:50PM +0000, Peter Nikolic wrote:
Le 12/12/2009 08:44, Bob S a écrit : Thin it is time to re- visit the old way of doing things /de/hda ect this /dev/disc/by ID ect is nothing but a mine field over which there is very
On Saturday 12 Dec 2009 08:25:26 jdd-gmane wrote: little control .
The approach of using /dev/disk/by-id makes things more reliable. The device name stays idependent of the order the controllers get initialized.
Or think about adding a new disk to an existing system. Your old device names stay independet if a controller or new disks get added.
Yeah, except, with the old way I could copy an opld drive to a new drive and the new drive would still be that same /dev/sdXx, and all bootloader configs would magically still work without editing or adjusting even though I'd completely replaced the drive. The by-id way breaks in that case. all the id's change. This is not really a problem, or not a larger problem than what by-id solves. I'm just pointing out that there is no single right way for everyone in all cases. (The rest isn't diretced at you Lars, at the thread in general) As for being mystified by hda vs sda... come on if that's a problem then you should not even be trying, just hire the closest 11 yr old to figure out all this hard stuff. As for being mystified by the bios drive ordering vs the OS drive ordering, well, yes, that's the explanation right there. The bios sees things in whatever way it does, and the OS sees things in whatever way it does, and the two do not have anything to do with each other except by coincidence. Neither is the way they see things static over time let alone the same as each other. Various bios config options that you the user may set, may change which devices the bios sees, what kind of device the bios sees some devices as, and what order it sees them in. And all that is also true for the OS. The mystery is why anyone is mystified that these things are mutable. The way to configure the bootloader is no specific particular way. Wish there was? Oh well, tough. The only simple instruction is "Configure the boot loader to reflect what you want to happen, given the particulars of your various hardware and firmware and software." You simply need to know at least a few things about how the bios and the os works, and how the bootloader works so you can know how to make it work with the other two. Not a lot really, but you can't avoid having to know at least a few things. And, these things do not have to be conferred from God. You can google them and do a little trial & error yourself. All 4 elements (hardware, bios, os, bootloader) are required to have a working system, all 4 affect each other, and all 4 are changeable. You change any one element, and it affects all the others and may require a matching change in one or all of the others. You have to understand at least a few things about all 4 sides before you can hope to make things work. But, you only need to know a few things about each, and then you can always make a working system any time no matter what. No stupid being helpless in the face of mysteries. Theres no need for mysteries. Just stop trying to avoid having to learn. Or, if you have other things you'd rather think about, that's fine. We don't all have to be in IT. Go find someone who does grok this stuff, tell them what you want, and then don't mess with it. Or else don't cry to anyone when it breaks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org