Difference between revisions of "Fstab"

m
Fixed some typo
m (Specified root owns fstab)
m (Fixed some typo)
Line 34: Line 34:
* UUID=<uuid>
* UUID=<uuid>
to uniquely identify a filesystem you want to mount.   
to uniquely identify a filesystem you want to mount.   
As a [https://en.wikipedia.org/wiki/Universally_unique_identifier UUID] is necessarily unique, you will find that this is the onn in use on more modern systems whereas a device name and label are only in use on older systems, so we'll concentrate on UUIDs in this tutorial, but know that if you insist on using these order systems, they still work at the time of this writing.
As a [https://en.wikipedia.org/wiki/Universally_unique_identifier UUID] is necessarily unique, you will find that this is the default in use on more modern systems whereas a device name and label are only in use on older systems, so we'll concentrate on UUIDs in this tutorial, but know that if you insist on using these order systems, they still work at the time of this writing.


To get the UUID for all of your devices, execute the command  {{ic|blkid}} elevated to root:
To get the UUID for all of your devices, execute the command  {{ic|blkid}} elevated to root:
Line 66: Line 66:
* booting from the '''E'''FI '''S'''ystem '''P'''artition on the new disk instead of its own ESP
* booting from the '''E'''FI '''S'''ystem '''P'''artition on the new disk instead of its own ESP
* failing to mount its own Windows partition because you just added another one and this takes precedence (or not: depending on the exact kernel version and filesystem driver resulting in a boot only working 50% of the time and other weird problems)
* failing to mount its own Windows partition because you just added another one and this takes precedence (or not: depending on the exact kernel version and filesystem driver resulting in a boot only working 50% of the time and other weird problems)
* failing to mount a disk because the disk you just inserted into M2 slot #1 gets named /dev/sda and the one in slot #2 which used to be called /dev/sda now suddenly becomes /deb/sdb.
* failing to mount a disk because the disk you just inserted into M2 slot #1 gets named /dev/sda and the one in slot #2 which used to be called /dev/sda now suddenly becomes /dev/sdb.
* etc, etc.
* etc, etc.


Line 72: Line 72:
This field describes the mount point (target) inside your filesystem. For swap partitions, this field should be specified as `none'. If the name of the mount point contains spaces or tabs these can be escaped as `\040' and '\011' respectively.
This field describes the mount point (target) inside your filesystem. For swap partitions, this field should be specified as `none'. If the name of the mount point contains spaces or tabs these can be escaped as `\040' and '\011' respectively.


For more information on the Linux Filesystem Hierarchy standard refer to the [[#See Also]] section, but in a nutshell you should specify an existing directory on your silesystem where you want to mount a partition.
For more information on the Linux Filesystem Hierarchy standard refer to the [[#See Also]] section, but in a nutshell you should specify an existing directory on your filesystem where you want to mount a partition.


In the example {{ic|fstab}} file above, the following line in it's {{ic|blkid}} output:
In the example {{ic|fstab}} file above, the following line in it's {{ic|blkid}} output:
1

edit