Can't find /etc/fstab on 10.5.6

Then, I surmise that you deleted it, since it exists on my machines. Download Pacifist and extract it from you install disk or reinstall the 10.5.6 COMBO update.

My error then. The command that used to control it is fstab.hd, which is what I thought you deleted. As for fstab, a cat on the fstab.hd command, returns:

+cat /etc/fstab.hd+
+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.+

I conclude that's why fstab isn't there.

As for mount, I suggest posting your queries to the Unix forum under OS X Technologies, since I don't use it.

Good luck.

There is no etc/fstab, there is an etc/fstab.hd, etc/fstab is for
the most part deprecated, although it still works for mounting local volumes (limited support).
If you know how.

If you are mounting a network disk, use AutomountMaker instead: http://www.versiontracker.com/dyn/moreinfo/macosx/21383

Leo does not use netinfo manager, it uses Launchd instead.

Kj

Message was edited by: KJK555

If you are mounting local disks just attach them, launchd will find them and mount them unless
you are trying to mount them on a special folder or something, that includes all usb and firewire
devices. eSATA devices must be on and connected at boot time, they cannot be mounted at
login unless you have a raid card (hot plug support).

/etc/fstab MUST be in the following format no more, no less:
[UUID=_universal unique identifier of the volume_ [_mount point_] [_file system_] [ options]
example:
UUID=97AC9040-81DD-351B-8675-20C53C555620 /macdata hfs rw,auto

Kj

although fstab is deprecated, it still will work, but it is neither supported nor is there any guarantee it will even exist in the future.

If you
man auto_master
you see a reference to fstab relating to /Network/Servers
automount reads auto_master
Then there is automountd which is connected to autofs
But
man autofs is empty
However, there is an
audofsd

It's a zoo out there 🙂
I have read some posts of users creating and using fstab to prevent an automount, and they say it works.

"I have read some posts of users creating and using fstab to prevent an automount, and they say it
works"

Hi nerowolfe:
It does indeed work.
for the mount point enter "none"
eg: UUID=97AC9040-81DD-351B-8675-20C53C555620 none hfs rw,auto

"auto and noauto" have spotty support, they may or may not work (they make good placeholders).
The only fstab parameters that work 100% reliable are the UUID, mountpoint and filesystem.
Leo will accept the rw, ro, noauto and auto options, but may or may not honor them, with
the exeption of the "rw" switch, which is the default, so if you don't put it, most of the time
fstab will work. I recommend putting it there though as the above combination of parameters
and options works pretty reliably.

I also recommend using the vi command line edit tool to edit the fstab file. Do not use any other
usual Unix fstab parameters or options. Strange behavior, kernel panics, lock ups, or failure to
mount will result.

The mountpoint cannot contain spaces in the name. Putting the name in quotes or using the bash
escape character "\ " will not work. Failure to mount will result. Recommended mount point is
some folder at the root directory, but it will mount at most any path that does not contain spaces.

It's not neccessary to use fstab to mount any type of network drive. AutomountMaker (freeware) is
a much better choice as it modifies the proper files to work hand in hand with launchd.

I believe at some point Apple will add this functionality to launchd or the diskutility mount
command and fstab will be no more. If the mount command could read UUID's now
there would be no use for fstab. A simple bash script or automator script on login would do.

That's the skinny on it!

Kj

"I believe at some point Apple will add this functionality to launchd or the diskutility mount
command and fstab will be no more. If the mount command could read UUID's now
there would be no use for fstab. A simple bash script or automator script on login would do."

True but needs clarifying:
Diskutil mount command can read UUID, but cannot custom mount a volume on a user's directory.
it will only mount a volume in the /Volumes directory with the default name (of the volume).

The "Mount" command will mount a volume where the user chooses, but cannot identify a volume
by its UUID, a device name (/dev/disk..) must be specified, which is many times a "moving target"
in OS X leopard as it doesn't predictably mount the same Disks in the same numerical order all
the time.

Kj