On Wed, 2004-02-04 at 16:09, Stroller wrote: > On Feb 4, 2004, at 8:10 pm, Paul de Vrieze wrote: > > > On Wednesday 04 February 2004 20:51, Don Seiler wrote: > >> Interactively merge the two and you should be all set. > > > > The problem is that this file should not need to change at all. The > > baselayout > > ebuild should be smart enough to see that /etc/fstab must not be > > changed > > (same as passwd and group) > > I recall a while back there were some changes that were necessary to be > merged into fstab; in fact mine contains the following 3 lines: > # added by baselayout-1.8.6.8-r1 - 5/7/2003 > # NOTE: The next line is critical for boot! > none /proc proc defaults > 0 0 > > But aside from that, fstab and some other systems files never change; I > always think these should be distributed as /etc/fstab.example and so > on. The Installation documentation could be changed to say "copy & edit > your fstab like so: cp /etc/fstab.example /etc/fstab && nano -w > /etc/fstab`" and users would have the benefit of a back-up of the > original should they ever b0rk theirs up.
I absolutely agree here. baselayout should not try to provide something key like fstab, I've seen etc-update wreck my own fstab and several users entries before. In the end to preserve my sanity I've ended up having to do chattr +i /etc/fstab /etc/X11/XF86Config to keep these file from ever getting overwritten. > > Stroller. > > > -- > [EMAIL PROTECTED] mailing list -- Ned Ludd <[EMAIL PROTECTED]> Gentoo Linux Developer
signature.asc
Description: This is a digitally signed message part
