On Thu, 01 Jan 2004 18:53:26 +0100
Norbert Kamenicky <[EMAIL PROTECTED]> wrote:

> SN wrote:
> > ----- Original Message ----- 
> > From: "Andy Arbon" <[EMAIL PROTECTED]>
> > To: "gentoo-user" <[EMAIL PROTECTED]>
> > Sent: Tuesday, December 30, 2003 6:38 PM
> > Subject: [gentoo-user] Base layout causing pointless config updates
> > 
> > 
> > 
> >>Hello,
> >>
> >>I'm just wondering if anyone here knows if anything is being done
> >with>etc-update or the baselayout package to stop it pointlessly
> >trying up>update a load of configuration files that I'm never going
> >to let it>touch every time it is updated?
> >>
> >>It seems like baselayout's changed quite regularly recently (this is
> >in>the x86 branch) and every time it does I get asked to update:
> >>1) /etc/DIR_COLORS
> >>2) /etc/devfsd.conf
> >>3) /etc/fstab
> >>4) /etc/group
> >>5) /etc/passwd
> >>6) /etc/rc.conf
> >>7) /etc/shadow
> >>8) /etc/conf.d/net
> >>9) /etc/modules.autoload.d/kernel-2.6
> >>
> >>Aside from rc.conf and maybe devfsd.conf I can't think of a single
> >one>of those that should ever be replaced or merged with a vanilla
> >copy. In>fact with most of them accidentally replacing the file with
> >a vanilla>one would be somewhere between an annoyance and a major
> >headache.
> > 
> > 
> > What if baselayout introduces a new group or user????
> > Think about it.
> 
> In that case it should be done by script, which at first checks
> the presence of the new user and then adds it to the copy of
> existing system passwd file (if necessary).
> 
> I am sorry, but I thing, that adding a new user by replaceing
> passwd file with new uniform passwd file (from baselayout),
> which do not fit to any configured system (except of just
> installed one) is a the most stupid way how it can be done.
> And I am sure that it's not only my opinion.
> 
> Happy New Year to everybody!
> 

Yes, it's totally asinine to present total replacement changes that
can break a running system, but don't hold your breath. I've
complained about this for three years now.

-- 
Collins


--
[EMAIL PROTECTED] mailing list

Reply via email to