Neil Blakey-Milner wrote:
> On Sat 2000-09-09 (00:05), Matthew Thyer wrote:
> > The point is that people are worried about scripts that aren't aware
> > of the "start" and "stop" argument trying to start apps again at
> > shutdown time. With my scheme, the script wont be executed at shutdown
> > time if the K* script doesn't exist.
> If it's there, it gets executed. If it's there, it was put there. If
> it was put there, it'll have support for "start" and "stop".
> If an administrator puts a script in there that does the wrong thing,
> that's his fault. He could use the fall-back rc.local method.
> We needn't support stupid behaviour by complicating the matter.
I'm behind on cvs-all and freebsd-current so forgive me but I'm basing my
comments on rc.shutdown executing /usr/local/etc/rc.d/* with argument
"stop". Which seems very dangerous given that people may not have
rebuilt their ports for a long time.
With my way the old scripts may not even be run until the admin reads
up on the new scheme.
> # before zope
> # before apache
> # after networking
> # after nfs
> is much better than:
> and then figuring to use S43.foo.sh.
We'll have to disagree on this point. Given that we've had no order
control in the past and that ports are generally (yes its bad to generalise)
not dependent on each other, should the situation arise I think that any
admin worth his/her pay can work out how to change the order with the
Remember that I'm trying to stay remotely compatible with other systems.
We dont have to re-invent the wheel.
I still think a dependency based system is way more complicated than what
> I'm not particularly attached to perl, but it has a convenience in some
> sections, like ports, that is unmatched by sed and awk. Note the
> excessive use of "perl -i -pe 's/foo/bar/'" for in-place substitution.
> I've asked on at least two occasions for a simple, easy-to-use, thing to
> do it without doing a two-liner that copies to another file, and then
> replaces the old file with the new file.
My point is that its worth some ugly awk and sed to get away from the
base OS depending on perl. I dont care how elegant perl is.
Thats about all I'll say on this thread.... got to sleep.
> Neil Blakey-Milner
> Sunesi Clinical Systems
> [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message