Disclaimer: I have used edgy
but have no experience with feisty
UUID is a Universally Unique Identifier
Originally Posted by cjae
What is the UUID thing all about?
. In the case of Linux disk partitions, it is assigned to a filesystem when the filesystem is created. Historically, fstab
could use the device name (e.g. /dev/hda1
), the volume label, or the UUID to specify a partition. I am a little shaky on udev
, but I believe, depending on how it is set up, the traditional device names can be unreliable under udev
, and they are using UUID to make sure there is no ambiguity. (I bought a notebook preloaded with edgy
. They had modified things so fstab
was using the device names, so it can be done. But when I played around with doing a second installation of edgy
, it used UUIDs in fstab
. I suspect, but haven't verified, that System76 altered the udev
setup to make the partition mounting reliable.)
When I was installing I had my normal PATA hd be labeled as sda and such same with the optical drives be labeled as sca and such, as you can see from my intial fstab. Does this kernel see all drives as sata in this distro?
I noticed the same thing with the above mentioned notebook. I believe
it has to do with the module libata
, but I have not figured everything out. But you now have a term you can plug into a search engine if you like.
Plus I could not switch this during the install as the non-graphical setup seems to be missing.
I don't understand what you mean.
I also have problems using dvdshrink as it will not even set the title from dvd. I seem to be able to use my / and /home partitions fine, but am having a problem with the write capabilities of the windows partitions. I used the automatix script to install the 3 g driver but it set flaky mount points so I changed them.
Sorry, this is beyond my knowledge and experience.
Can anyone help me get this working properly? I am assuming that it has something to do with the devices nodes created during install.
I believe under udev
the device nodes for the drives are created dynamically at boot rather than at install. (But apparently some other device nodes aren't -- as I said I still have much to figure out about udev