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

Re: It's Huntin' Season

>>"Steve" == Steve Langasek <vorlon@netexpress.net> writes:

 Steve> At issue here is whether a startup script really counts as a
 Steve> configuration file.  If a script is in /usr, we don't expect
 Steve> local changes to be preserved on upgrade.  I don't believe
 Steve> that init scripts meet the definition of a configuration file
 Steve> by any stretch of the imagination.  Still, we have to face the
 Steve> truth that many users will think they can edit these files
 Steve> simply on the basis that they're located in /etc, a conclusion
 Steve> they arrive at by reading our policy and the FHS.

     configuration file
          A file that affects the operation of a program, or provides site-
          or host-specific information, or otherwise customizes the
          behavior of a program.  Typically, configuration files are
          intended to be modified by the system administrator (if needed or
          desired) to conform to local policy or to provide more useful
          site-specific behavior.

	When a machine starts up, a number of processes are started,
 and the behaviour of these processses, or whether they start at all
 (which changes the behaviour of my machine), is governed by the start
 up scripts. alsa actually loads and unloads modules from the kernel
 (changing the behaviour of the kernel in a marked
 fashion). bootmisc.sh is another nice place to hook things into. Or
 checkfs.sh. console-screen.sh. I could go on.

	If I put an exit 0 at the top of the script, I do not expect
 an upgrade to change that.

 I don't care where I sit as long as I get fed. Calvin Trillin
Manoj Srivastava   <srivasta@debian.org>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Reply to: