Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: Change a disk's mount point' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Change a disk's mount point
Authored by: ocdinsomniac on Aug 11, '05 12:36:19PM

This is an interesting hint. But in my clean installs of Tiger, I have no fstab file. I do have /etc/fstab.hd, which only contains the following text:

"IGNORE THIS FILE.
This file does nothing, contains no useful data, and might go away in
future releases. Do not depend on this file or its contents."

Anyone know what's happened to fstab in Tiger?



[ Reply to This | # ]
10.4: Change a disk's mount point
Authored by: escowles on Aug 11, '05 03:49:48PM

fstab has always been used only in single-user mode -- that's why you need to load the info into NetInfo for it to have any effect.

-Esme



[ Reply to This | # ]
10.4: Change a disk's mount point
Authored by: ocdinsomniac on Aug 11, '05 04:49:35PM

Ah! Thanks! I missed that NetInfo part.

I never knew how to get tht UUID number for a drive. And now I do. Cool.



[ Reply to This | # ]
10.4: Change a disk's mount point
Authored by: macshome on Aug 12, '05 09:13:07AM

It's just not installed by default anymore. fstab worked fine in Jaguar and Panther in multi-boot mode. I've used it several times when setting up failover clusters. The main thing to remember is that you had to use the disk name as defined for the partition, not the traditional disk number as you would on other *NIX. Mac OS X has dynamic disk mounting and the disk number might change from boot to boot.

AFAIK it works fine in Tiger as well, but I've not tested it yet.

---
http://www.afp548.com
Breaking my server to save yours.



[ Reply to This | # ]
fstab
Authored by: sjk on Aug 13, '05 07:12:32PM

That's incorrect, Esme. I've used an entry like:

UUID=383FD42C-EA30-48A4-B260-BE51F9A206FC /Users hfs rw

... in /etc/fstab on 10.3 & 10.4 to mount the users volume on /Users without loading data into NetInfo.

Works flawlessly, except for an ignorable "no such file or directory" warning from the mount command run from /etc/rc when booting.

I disagree with gidds' post that claims the symlink method of users volume relocation is "much safer and easier". Well, at least the "safer" part because (IMO) there's less risk of some obscure error with a directly mounted volume than referencing it through a symlink. Pretty sure I've read of trouble (maybe a bogus installer?) caused by such a symlink although that was a few years ago and may be irrelevant nowadays. Whichever method works to your satisfaction is what's best for you. :-)



[ Reply to This | # ]