Date: Tue, 30 Jun 1998 18:11:53 -0500 From: "Matthew D. Fuller" <fullermd@futuresouth.com> To: Mike Smith <mike@smith.net.au> Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: Adding a new user interface to FreeBSD administration Message-ID: <19980630181153.08867@futuresouth.com> In-Reply-To: <199806302146.OAA08168@dingo.cdrom.com>; from Mike Smith on Tue, Jun 30, 1998 at 02:46:18PM -0700 References: <19980630163313.49201@futuresouth.com> <199806302146.OAA08168@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 30, 1998 at 02:46:18PM -0700, Mike Smith woke me up to tell me:
> > On Mon, Jun 29, 1998 at 04:29:31PM -0700, Jordan K. Hubbard woke me up to tell me:
> > >
> > > linux(enabled) = YES
> > > linux(doc) = { This variable controls whether linux emulation support
> > > will be automatically loaded at startup. You can also do it manually
> > > with the /usr/bin/linux command. }
> > > linux(exec-command) = "linux > /dev/null 2>&1"
> >
> > OK, so what's wrong with a simple /etc/rc.conf script that looks
> > something like:
>
> It doesn't scale.
I don't see how.
Unless there's a limit (that we're likely to reach) on how long a shell
variable can be. I'm sure there is, but I'm not sure if it's low enough
that we're likely to hit it on a bootup sequence.
I mean, it's the same way Jordan was going with a 'registry', except
thrown into a script. I can see it getting a little unwieldy at extreme
sizes, but then again, there's only so much you're really going to be
DOING on bootup. Have an /etc/configfile.conf which which points
something like:
ppp_linkup = '/etc/ppp/ppp.linkup'
httpd_conf = '/usr/local/www/conf/httpd.conf'
system_cshrc = '/etc/csh.cshrc'
...
which will A) allow you to see where all the files are and B) allow a
monolithic 'sysconfig' script/program/cutesy thing to know right off the
bat where all the config files are. Heck, you can even C) move all them
to /etc/config/ if you wanted to.
Perhaps not an ideal solution, but fairly easy to thrown together and
better than it is now.
> Yes. And you could call it /etc/rc too.
>
> Wrong direction, sorry.
Well, the way I describe redoing (bootup) procedure above would drop
quietly into the present setup; just replace /etc/rc with that nice
little 4-line script, and rc.conf with the above. It's a bit more
self-explanatory than the present, anyway.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| FreeBSD; the way computers were meant to be |
* "The only reason I'm burning my candle at both ends, is *
| that I haven't figured out how to light the middle yet."|
* fullermd@futuresouth.com :-} MAtthew Fuller *
| http://keystone.westminster.edu/~fullermd |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980630181153.08867>