The mount point specifies at which location in the directory hierarchy a device or disk partition appears.
If you want to move /home
to a new partition, you have to create a new partition for it, say /dev/sda4
and format it, e.g. with ext4. Creating partitions and formatting them can be comfortably done using e.g. gparted.
Then you have to copy the old contents to the new partition and modify /etc/fstab
so /home
points to the new partition. As root do something like this after having the partition created and formatted. Again, I assume /dev/sda4
for the partition, this is just an example and you have to use your real partition device:
$ mkdir /mnt/tmphome
$ mount /dev/sda4 /mnt/tmphome
$ cd /home/
$ find . -depth -print0 | cpio --null --sparse -pvd /mnt/tmphome/
$ umount /mnt/newhome
$ mv /home /old_home
$ mkdir /home
$ mount /dev/sda4 /home
Now check if your system is still working correctly. If it does, add a line like this to /etc/fstab
:
/dev/sda4 /home ext4 defaults 1 2
and delete the backup in /old_home
if however you find that something went wrong, you can move back by not adding respectively removing the above line in /etc/fstab
and doing as root
$ umount /home
$ rmdir /home
$ mv /old_home /home
This answer is inspired by the howto on http://embraceubuntu.com/2006/01/29/move-home-to-its-own-partition/
First and foremost, this is going to depend solely on your architecture, and customs.
I for instance mount things like this under /mnt. I know people that create top level directories, and people who put this stuff in /home. It all depends on what you're comfortable with. There is no distinct standard on this anymore, the architecture of the system has changed, and you have varying views now, on things that used to be 'gospel'. Things like /usr/local or /opt/share, rpm or source...you get the drift.
Secondly, if you re-read through your link at pathname.com, you'll notice the paragraph under /media that states
Rationale
Historically there have been a number
of other different places used to
mount removeable media such as /cdrom,
/mnt or /mnt/cdrom. Placing the mount
points for all removeable media
directly in the root directory would
potentially result in a large number
of extra directories in /. Although
the use of subdirectories in /mnt as a
mount point has recently been common,
it conflicts with a much older
tradition of using /mnt directly as a
temporary mount point.
So personally, I advocate /mnt/windows or some iteration of that. It keeps the top level dir free, and is simple and intuitive. When I'm looking through or auditing a system, that's where I look for mounts right off the bat.
Best Answer
Thanks for the link LJKims, it helps me to answer my own question. I forgot that the suid/sgid bit can also be set for directories.
According to the GNU coreutils documentation files and directories that are created in a suid-directory inherit the owner of the directory (sgid-directories inherit the group obviously). So, if you want to avoid this behaviour, setting both noexec and nosuid on a mount point makes sense.
For completeness: in my tests on a current Debian, the suid bit on directories takes no effect, but only the sgid bit makes files/directories inherit the group of the directory.
Edit: For completeness: The nosuid mount option does not affect sgid-directories (on Debian 8 at least).