public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Beland <matt@rearviewmirror.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] /etc/init.d
Date: Mon, 11 Mar 2002 10:54:08 -0800	[thread overview]
Message-ID: <20020311185408.GC28735@rearviewmirror.org> (raw)
In-Reply-To: <3C8CF48D.5000106@colubris.com>

[-- Attachment #1: Type: text/plain, Size: 3598 bytes --]

On Mon, Mar 11, 2002 at 01:16:45PM -0500, Yannick Koehler wrote:
> Craig M. Reece wrote:
> >On Mon, Mar 11, 2002 at 12:48:08PM -0500, Yannick Koehler spoke thusly:
> >
> >>Guys,
> >>
> >>	not sure for anyone else but is init.d really need to be protected?  
> >>	I mean does someone really change files in that directory (other 
> >>	than adding or removing)?
> >>
> >>	That dir should always get merged.  It would also get really nice of 
> >>	the portage could detect that no changes has been made to the file 
> >>	since its installation and therefore merge it without any issues.
> >>
> >>	Like if the protected config file's time were saved in a temp files 
> >>	that portage would look into before merging to see if the date has 
> >>	or not change since the last install.
> >>
> >>
> >
> >Yes it needs to be protected. I, for instance, have my own version of
> >pcmcia in there that I don't want stepped on. Also, I have a couple of
> >other custom scripts for things not in portage yet; and when they are in
> >portage, I want to be able to compare the differences before using one
> >or the other.
> 
> The reasoning I have is that those are scripts, and not config files. 
> If ... instead of modifying pcmcia script for example like you 
> mentionned you were to cp pcmcia pcmcia.modif and rc-update add 
> pcmcia.modif default / rc-update del pcmcia default the system would 
> work and you'll never get concerned about the new pcmcia scripts.

They are sometimes both scripts and config files. Personally, I like the 
layout of the Gentoo initscripts, particularly with regard to the "local"
script and the ability to start "simple" daemons and scripts with a config
file. However, many of the scripts we add to the init.d directory are not
custom-written for Gentoo, they're written for Linux in general. They 
include the necessary config settings in the init file itself. And those
should not be clobbered.
 
> If you changes those scripts maybe it's even better to tell people about 
> your changes as they may get implemented such that the script itself 
> read a config files (like net.eth0) so that other people can re-use your 
> modifications.

That's fine for things like the tweaked pcmcia script - but what if the 
tweaks are in order to permit a specific driver to work properly? Those 
changes should not be in the default initscript, they should at most be
provided as a commented-out section - which, again, would require user 
intervention to create the required "tweaked" script.

It wouldn't solve the problem for custom scripts. Suppose (as an example)
that I have installed OpenSSH by compiling it from source, then later
I emerge the ssh ebuild. I would have installed an initscript already,
I would call it 'sshd' by default. Before I blindly replace it with the 
Gentoo initscript, I would want to examine it and see how it did things.

> And maybe a user's scripts directory should exists, something like 
> /etc/user.d where people can move their custom scripts and the stuff 
> behind rc-update would got here first and if it doesn't found the script 
> then to /etc/init.d.

While I don't agree with everything that "the standard linux" build does, 
particularly as defined in the LSB project, I don't think we should be 
creating new directories within /etc/ just to make things a little more 
convenient. Especiually when that convenience comes with a price in the 
form of an increased risk of system breakage.

-- 
Matt Beland
matt@rearviewmirror.org
http://www.rearviewmirror.org

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2002-03-11 18:57 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-11 17:48 [gentoo-dev] /etc/init.d Yannick Koehler
2002-03-11 17:52 ` Matt Beland
2002-03-11 17:54 ` Ric Mesier
2002-03-11 18:43   ` Benjamin Ritcey
2002-03-11 18:45     ` Ric Mesier
2002-03-11 18:47       ` Ric Mesier
2002-03-11 19:55   ` Ian Smith
2002-03-11 18:02 ` Craig M. Reece
2002-03-11 18:16   ` Yannick Koehler
2002-03-11 18:52     ` mbutcher
2002-03-11 19:05       ` Craig M. Reece
2002-03-11 21:11       ` Yannick Koehler
2002-03-11 18:54     ` Matt Beland [this message]
2002-03-11 19:43       ` Martin Schlemmer
2002-03-11 20:44       ` Yannick Koehler
2002-03-11 21:10         ` Martin Schlemmer
2002-03-11 22:16           ` Matt Beland
2002-03-11 23:28             ` Yannick Koehler
2002-03-11 18:45   ` Per Wigren
2002-03-11 19:06     ` Craig M. Reece
2002-03-11 19:35     ` Yannick Koehler
2002-03-11 18:17 ` Yannick Koehler
2002-03-11 18:42   ` Matt Beland
2002-03-11 19:32     ` Yannick Koehler
2002-03-11 19:37       ` Ric Mesier
2002-03-11 21:13         ` Yannick Koehler
2002-03-11 22:07           ` Defresne Sylvain
2002-03-11 22:42             ` Ian Smith
2002-03-11 22:49               ` Defresne Sylvain
2002-03-11 22:55               ` Martin Schlemmer
2002-03-11 23:12                 ` Ian Smith
2002-03-11 23:29             ` Yannick Koehler
2002-03-11 22:28           ` Ian Smith
2002-03-11 22:33         ` Ian Smith
2002-03-11 19:50       ` Martin Schlemmer
2002-03-11 19:56       ` Matt Beland
2002-03-11 21:25         ` Yannick Koehler
2002-03-11 18:41 ` Thilo Bangert
2002-03-11 19:49 ` Joachim Blaabjerg
2002-03-11 21:15   ` Yannick Koehler
2002-03-11 21:03 ` Tod M. Neidt
2002-03-11 21:30   ` Yannick Koehler
2002-03-11 16:26     ` Bob Phan
2002-03-11 21:39       ` Craig M. Reece
2002-03-11 16:42         ` Bob Phan
2002-03-11 22:33           ` [gentoo-dev] /etc/init.d the real question!? Corvus Corax
2002-03-11 23:33             ` Yannick Koehler
2002-03-12 11:03           ` [gentoo-dev] /etc/init.d Craig M. Reece

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020311185408.GC28735@rearviewmirror.org \
    --to=matt@rearviewmirror.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox