From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] where to put mknod & chmod
Date: Fri, 13 Oct 2006 16:33:19 +0100 [thread overview]
Message-ID: <20061013163319.1c9d72c6@hactar.digimed.co.uk> (raw)
In-Reply-To: <20061013152204.77228.qmail@web31708.mail.mud.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
On Fri, 13 Oct 2006 08:22:04 -0700 (PDT), maxim wexler wrote:
> IIRC the last time I updated baselayout it overwrote
> some important files and my system was un-usable. In
> all the excitement I failed to note what they were.
That wasn't baselayout, it was you when running etc-update.
> Is there a list somewhere?
Yes, etc-update shows it to your before asking what to do. Check the
contents of each file before allowing it to be overwritten, and never,
ever let etc-update overwrite etc/fstab, /etc/passwd or /etc/group.
--
Neil Bothwick
Artificial Intelligence usually beats real stupidity.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-13 15:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 16:00 [gentoo-user] where to put mknod & chmod maxim wexler
2006-10-11 16:24 ` Alan McKinnon
2006-10-12 14:44 ` maxim wexler
2006-10-12 17:10 ` Alan McKinnon
2006-10-13 15:22 ` maxim wexler
2006-10-13 15:33 ` Neil Bothwick [this message]
2006-10-15 4:40 ` [gentoo-user] Is it possible to protect *INDIVIDUAL FILES* against etc-update? Walter Dnes
2006-10-15 7:06 ` Bo Ørsted Andresen
2006-10-16 21:57 ` Walter Dnes
2006-10-17 0:47 ` Richard Fish
2006-10-18 4:09 ` Walter Dnes
2006-10-17 13:11 ` Neil Bothwick
2006-10-15 12:27 ` Neil Bothwick
2006-10-17 13:16 ` Bo Ørsted Andresen
2006-10-17 14:28 ` Neil Bothwick
2006-10-13 23:51 ` [gentoo-user] where to put mknod & chmod Drew
2006-10-11 18:09 ` Neil Bothwick
2006-10-11 21:31 ` [gentoo-user] where to put mknod & chmo Richard Fish
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=20061013163319.1c9d72c6@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.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