Skip to Content.
Sympa Menu

sm-discuss - [SM-Discuss] init.d and networking configuration

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Casey Harkins <charkins AT upl.cs.wisc.edu>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: [SM-Discuss] init.d and networking configuration
  • Date: Thu, 24 Oct 2002 19:05:44 -0500 (CDT)

I've just been looking over the most recent init.d stuff (great work
nealbirch!). Anyway, I have a couple thoughts I wanted to get people's
opinion on.

1) Currently the init.d spell contains the basic init.d scripts and others
are in relevant spells (net-tools, ssh, etc). While this at first would
seem logical, it prevents us from keeping the init.d system abstracted. It
may be possible in the future to allow different init systems to be
dropped in by casting a spell (i.e. init.d, runset).

What I am proposing is to keep ALL of the init scripts within the init.d
spell. Gurus would need to send their init scripts to the init.d
maintainer to have them included/updated. This should ensure that all init
scripts make use of the functions when possible to give a consistent look
to the startup process. A TRIGGERS file could then be added to the init.d
spell to have it cast_self when a spell which has init scripts is cast.
The init.d spell would then check which spells are installed and
install/update the relevant init scripts. (Could this be handled with
optional_depends?)

The trick here is preventing a 'make install' from installing any init
scripts.

Should scripts then be auto-updated? Should there be a "HOLD" mechanism
for init scripts to prevent certain scripts from being updated?

2) The init.d spell now uses a dialog to ask the user which scripts to
install. However, this could cause a system-update to sit at the dialog
waiting for input. Should it ask something like "Choose which scripts to
install? [n]". This way it would only open the dialog if the user selected
yes (similar to "configure kernel?" when casting linux).

3) The network configuration dialogs also get brought up when casting.
What I propose here is to keep the network configuration stuff separate
from the networking.sh init script. Maybe add a "netconf" script to the
net-tools package which handles creating, modifying and removing device
files from the /etc/sysconfig/network directory. I am going to start
working on this piece right now.

Ok, enough rambling. What do people think? Yeah I know, too close to
1.0...

-casey






Archive powered by MHonArc 2.6.24.

Top of Page