[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: About using Linuxconf



> 
> 1.  It would probably be better to just have the linuxconf package come
> with them, i.e. We would go through all the packages that install anything
> in init.d and make dropin's for them.  We would then put this in a
> linuxconf-dropins package.  This package would have a postinst script that
> would go through the installed packages and "activate" the dropins.
> 

OK.  Now I think I get it.  So what I was suggesting isn't that
far off the mark.  I was suggesting having a utility that
dynamically built the dropins for the packages.  My assumption
was also that one could use linuxconf to modify package behavior
(and thus the dropins) so I also suggested that this utility
should be able to dynamically construct the "standard" package
conf files from the dropins in the event a user wanted to purge
linuxconf.  That way packages could check some state flag or
something to see if linuxconf was active and just run the utility
to create (or update?) the dropins.

Now this seems to make sense.  We have a similar problem with
base-files.  If a user has modified his/her passwd or group
files, base-files gives you the choice to keep them instead of
installing the new files.  This isn't good enough however.  If I
have local mods in these files, I'm going to say "No" and keep
the files.  But then I don't get the new additions made to
the base-files package.  The same would hold true for linuxconf
dropins.  Instead of devising some way to make it possible to
upgrade linuxconf dropins (with package tags or something), it
may just be better to devise a database style approach for all
config data.  That way Linuxconf could use that for dropin
management just as other packages could use it for their own
configuration management.  Data could easily be tagged in such a
case to identify where it came from (i.e. the package or a user,
etc.) and management is much easier.

Now I think I get it.  And now I think that linuxconf isn't the
answer, because we'd still need to develope some Debian specific
way of managing dropins and upgrades, etc.  What Bruce is
proposing makes much more sense to me now.  I think that a
linuxconf package would be a great idea -- especially with a way
to manage dropin files, etc. the way we've been discussing.

Sorry Shaya, but I'm jumping ship.  Good luck with your exam
though!

Richard G. Roberto
richr@bear.com
011-81-3-3437-7967 - Tokyo, Japan


--
*******************************************************************************
Bear Stearns is not responsible for any recommendation, solicitation, offer or
agreement or any information about any transaction, customer account or account
activity contained in this communication.
*******************************************************************************


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com


Reply to: