Re: Leopard and scripts on startup
Re: Leopard and scripts on startup
- Subject: Re: Leopard and scripts on startup
- From: Dave Zarzycki <email@hidden>
- Date: Wed, 19 Mar 2008 10:15:10 -0700
On Mar 19, 2008, at 7:08 AM, Geoff Lee wrote:
I've searched the archives of this and several other lists but this
doesn't seem to have come up.
We currently have a Tiger network install image which runs our
custom installer script (written in bash) from /etc/rc.local,
outputting to the console. The windowserver is never started. I'd
like to emulate this behaviour using a Leopard install and am having
problems.
on a standard Leopard installer CD, /etc/rc.install /System/Library/
LaunchDaemons/com.apple.install.cd.plist is started by /System/
Library/LaunchDaemons/com.apple.install.cd.plist and should run /etc/
rc.local if it exists. On my image (which started as a clone of the
installer CD) this is happening, but rc.install (and thus rc.local)
are running in the background. Is there any way I can cause it to
run in the foreground and send it's output to the screen? Setting
StandardOutPath to /dev/console in /System/Library/LaunchDaemons/
com.apple.install.cd.plist doesn't seem to make any difference.
Any hints as to where to look for more information would be
appreciated. I've scoured the Boot process documentation on Apple's
site but the possibility of running without the window server
doesn't really seem to be covered.
Geoff,
As of Leopard, the console tty is no longer used or even setup during
boot. You're going to have to do that yourself. Please also keep in
mind that manipulating /dev/console is not a supported feature of the
operating system.
davez
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden