On 1/3/02 at 5:42 PM, arne @ loopback . org <[EMAIL PROTECTED]>
wrote:
> ... but it should be clear that this
> will only work with configuration files NOT containing
> anything else than configuration keys-value pairs and
> comments (and no shell script functions like dachstein had
> in previous versions).
What about dhcpd (DHCP Server)? Or DNS? Or squid? Or ProFTPd? Or
xinetd?
There's lots of configuration files that don't fit the model. I
assume you mean:
# This parameter does...
PARM=value
...etc... Most of the examples I gave either have this pattern:
SomeTitle {
ParmEntry X
ParmEntry2 Off
}
...or...
<Parm Value>
Entry values...
Entry2 values...
</Parm>
Entry value value
Entry2 value value
...etc...
I wrote a big menuing setup for Oxygen while making it generic enough
for others. It only makes the assumption that every configuration
file is editable and that all are in the *.conf file. I wrote mine in
the shell using dialog and ncurses. It also attempts to configure
EVERY package which is loaded when it runs... or it can...
I've not looked at it in a while as I wanted to get a new version out;
I should return to it. Other problem is the nature of a setup
program: it modifies your disk image.
One thing about my setup was this: it ran scripts to set up various
things (networking, etc.) and setting up something new was just a
matter of adding a shell script in a setup.d directory.
PS: Arne, weren't you working on making busybox tar work with LRP
instead of needing to use ctar? How's it going?
--
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
