Date: Sat, 8 Jul 2000 22:53:03 -0700 (PDT) From: "Eugene M. Kim" <ab@astralblue.com> To: "Andrey A. Chernov" <ache@FreeBSD.ORG> Cc: Adam <bsdx@looksharp.net>, "David O'Brien" <obrien@FreeBSD.ORG>, Peter Wemm <peter@netplex.com.au>, Robert Watson <rwatson@FreeBSD.ORG>, Sheldon Hearn <sheldonh@uunet.co.za>, Brian Somers <brian@Awfulhak.org>, Thomas Gellekum <tg@FreeBSD.ORG>, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc rc.shutdown Message-ID: <Pine.BSF.4.20.0007082248170.87521-100000@home.astralblue.com> In-Reply-To: <20000708220113.A81167@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm afraid you probably misunderstood my point, which was to *drop* the start|stop comment hack in the end, leading to the simple start/stop argument scheme. The start|stop hack is only temporary and its purpose is just helping the users to migrate to the next step. And IMHO making separate scripts for startup/stop has its own demerits. One would be scattering the two tightly coupled jobs into several places. Regards, Eugene On Sat, 8 Jul 2000, Andrey A. Chernov wrote: | On Sat, Jul 08, 2000 at 12:29:24PM -0700, Eugene M. Kim wrote: | > That sounds like a good idea, provided that it will be gone after a | > reasonable heads-up grace period. One scenario might be: | > | > * In FreeBSD 4.1: | > | > - Add a `# start|stop' line to every startup script in ports. | | I object such indirect magic as local hack hard to remember and not in Unix | style. Separate directories for sturtup/shutdown is much clearer solution. -- Eugene M. Kim <ab@astralblue.com> "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.0007082248170.87521-100000>