public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Stroller <root@stellar.eclipse.co.uk>
Cc: gentoo-user@gentoo.org, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-user] "etc-update" versus Manual update opinions..
Date: 17 Sep 2003 11:46:34 -0400	[thread overview]
Message-ID: <1063813594.3092.42.camel@localhost> (raw)
In-Reply-To: <F4DE20B2-E91F-11D7-9EE5-000A95795F3E@stellar.eclipse.co.uk>

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

On Wed, 2003-09-17 at 11:02, Stroller wrote:
> On 17 Sep 2003, at 1:24 pm, Gwendolyn van der Linden wrote:
> 
> > brett holcomb [mailto:brettholcomb@charter.net] wrote:
> >
> >> Well, if you use etc-update on files like /etc/fstab your
> >> system will break.
> >
> > Exactly.  I would vote for keeping /etc/fstab.example in portage, and
> > making the copying/editing part of the installation procedure (cp
> > /etc/fstab.example /etc/fstab; nano -w /etc/fstab).
> 
> I agree. I wouldn't be surprised if this was changed, were you to file 
> it as a bug. I'm cross posting to gentoo-dev to see what they think.
> 
> Stroller.

I think it is a great idea.

You definitely have my support.

-- 
Chris Gianelloni
Developer, Gentoo Linux
Games Team

Is your power animal a pengiun?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-09-17 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OLEMJKKJBJMMNIPIEKLLGENIDBAA.Gwendolyn.van.der.Linden@technolution.nl>
2003-09-17 15:02 ` [gentoo-dev] Re: [gentoo-user] "etc-update" versus Manual update opinions Stroller
2003-09-17 15:46   ` Chris Gianelloni [this message]
2003-09-17 17:09   ` Alexander Gretencord
2003-09-17 18:11     ` John Mylchreest

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=1063813594.3092.42.camel@localhost \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-user@gentoo.org \
    --cc=root@stellar.eclipse.co.uk \
    /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