On Tue, Oct 14, 2008 at 03:08:17PM -0400, Hal Vaughan wrote:
> For instance, stating it in the file: Again, not everyone has time to
> read all the comments in all the files. As to unrealistic
> expectations, what would be so hard with using a bash script specifying
> the rewrite was going to happen? It's not that hard.
Hal,
I agree that there should be some mechanism to prevent a user from
shooting him/herself in the foot if they make a change to a file between
two markers that remind the user that those changes will be overwritten
on the next kernel upgrade. It shouldn't be necessary, but since it can
prevent the system from booting, and since with raid and LVM it may not
be as simple to fix as it used to be, it would be a nice touch if
something was done.
However, everyone who edits a config file should at least read from the
top of the file down to where they want to edit, at least enough to read
prominent warnings such as are in menu.list. It goes with the territory
of su - ing, sudo-ing, or logging in as root. Perhaps put a line in
root's .profile or somewhere that gives you a warning whenever you
become root:
WARNING: YOU HAVE A LOCKED AND LOADED ASSAULT RIFLE POINTED AT
YOUR FEET AND YOUR FINGER IS ON THE TRIGGER.
Doug.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
