Re: a note or two about configuration management r6
I said once that I'm (still) making something like a Control Panel for Debian.
Unfortunately, just after I sent that e-mail, my mail server stopped working
and I've lost all the replys (I got only some of them.. ), and I tried to look
at the archives at the Debian site, but it was not updated enough.
Well, let me explain better :
I'm doing it as modules. There are , at the moment :
- A printer module, configures the printer
- A network module, configures the network
- A partitions modules, sets where a partition or device should be mounted.
There will be more soon, like : sound , modules, modens, ....
This Control Panel is not stand alone.. let me explain better : I'll not create
¨another¨ configuration file, or create new ones. For example : the printer
module shows the window, the user configurates in a GUI and the, that module
calls magicfilterconfig and configure it. The network module changes the file
/etc/init.d/network , the partition module changes /etc/fstab and the next
modules will do like you were doing ¨by hand¨ .... but in a GUI...
If you think it is better to do it in the way you are thinking (doing database,
configuration files, etc..) no problem, I can change that. I am doing it only
to be more easy for people to configure things, like printers, networks, sound,
etc...
Diego Lages
Em Wed, 24 Mar 1999, Jonathan P Tomer escreveu:
> i've just read wichert's most excellent proposal for a configuration
> management system. i like it a lot, and it fits with the things i'd been
> thinking of (mainly the qualities of excessive modularity and generality,
> which are essential for anything and especially config databases). i had a
> few comments to make about it though.
>
> 1. in the metadata layer, it is important to note that we need a special
> type for "list", which seems that it might need special support. for
> example:
>
> Template: printers
> Type: list (printer)
> Description: a bunch of printers
> Specifies all the printers on your network.
>
>
> 2. The most basic possible front-end is not one that uses stdin/out. It uses
> sockets. That's a little more general, and can be more easily run remotely
> (i'm thinking along the lines of a configuration server for the machine, so
> i can do telnet foobar debconfig and get to the configuration server for the
> machine. could be useful if you want to store common information on
> individual machines, and skip the option of a central remote server (who
> knows why)).
>
> 3. there is no 3.
>
> --phouchg
> "Reasoning is partly insane" --Rush, "Anagram (for Mongo)"
> PGP 5.0 key (0xE024447449) at http://cif.rochester.edu/~phouchg/pgpkey.txt
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--
Numquam retrorsum
Reply to: