Hi Richard, It is not that startup is not waiting for that volume, rather it is that we chose we not to mount it until you log in. The volume is on a disk marked external, which on a Client install, does not get mounted until someone logs in. You should be seeing it mount at boot on a Server install just fine, by contrast. There are two ways to have it mount at boot. The first one, also the ideal one, is unfortunately not working in 10.3.x due to an oversight on our part. I mention it only for future reference. It would be to list the volume in question by UUID in /etc/fstab along with the "auto" option. This would override any default. My alternative would be to create the preference file in /Library/Preferences/SystemConfiguration/ com.apple.DiskArbitration.diskarbitrationd.plist with this: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist SYSTEM "file://localhost/System/Library/DTDs/PropertyList.dtd"> <plist version="0.9"> <dict> <key>DAMountDeferExternal</key> <false/> </dict> </plist> Dan On Jun 11, 2004, at 4:24 AM, OpenMacNews wrote:
Thibaut,
This is completely wrong, from a UNIX point of view.
"/etc" (or anything under "/etc") has never meant to be put aside
"/", and whatever UNIX OS you use, if you want to do this it's both
risky and tricky.
I suggest you take a look at Google searching for "/etc on separate
partition", you'll see various explanations about why it's wrong.
Basically, /etc contains the early startup scripts, and putting /etc
anywhere else than "/" (or even part of it) would be equally as
dangerous as putting parts of "/sbin" on another partition.
These are parts of the core files needed to boot so they have to be on
the same disk. That's why they're so compact (disk space), and that's
why there is a "/usr"...
hi,
that may well be the wisdom for "/etc". so let's take that particular
dir out of the equation ...
my example seems to have confused matters, and folks are focusing on
the "/etc" usage, rather than the disks-not-mounting issue ...
are you saying that NO service to be launched at Startup can have any
of its config, or other, data (/etc, /usr/, or anywhere else) on any
drive OTHER than the boot drive?
i'd honestly be surprised if that is the case ...
if not, then the problem is, per my example, how to get SystemStarter
to *DELAY* trying to launch any/those services UNTIL diskarbitrationd
has VERIFIED that all drives have finished mounting ...
the real issue is *how* to prevent SystemStarter trying to start up
any services until drives have finished mounting.
Hi,
are you starting Postfix from /System/Library/StartupItems ?
Have you tried moving it into /Library/StartupItems ?
Not sure if it will make a difference, it is far too early to
remember what kicks what off
Let me know how you get on, and when I'm more awake I might have a
better solution :)
Sam,
Its not any issue of WHICH service, or in which path, rather, as
above, its the wait-for-the-drives thing ...
richard
_______________________________________________
darwin-kernel mailing list | darwin-kernel@lists.apple.com
Help/Unsubscribe/Archives:
Do not post admin requests to the list. They will be ignored.
_______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.