[conspire] ... /etc/debian_version, /etc/issue, /etc/motd, ...

[Paul Zander]

Yes, I was not familiar with those files.  

Since that time I have verified they are automatically generated.  Possibly by `apt-get dist-upgrade`. 

Here is my SOP when I do mess with important configuration files, especially ones I don't understand well. I make a copy of the original with a .0 suffix.  Use `cp -a` to preserve the creation date.
Then it is trivial to inspect what was changed or to back out the changes.
Over time, I might have a file.0, file.1, file.2.
Sometimes I have totally forgotten that I had tweaked something until `apt-get dist-upgrade` pauses with a message about some file.  I look for the file and find the history and can see what I changed and ...



      From: Rick Moen <rick at linuxmafia.com>
 To: conspire at linuxmafia.com 
 Sent: Wednesday, July 4, 2018 12:52 AM
 Subject: Re: [conspire] ... /etc/debian_version, /etc/issue, /etc/motd, ...
   
Quoting Michael Paoli (Michael.Paoli at cal.berkeley.edu):

> (and of course if one has dozens/hundreds or more Debian
> systems, also *manually* wouldn't be the way to manage those
> (individual) files either).
> 
> However, /etc/issue - and perhaps likewise /etc/motd ... not quite
> 100% in agreement.

I think you're attributing to me some sort of position I don't hold.

All I was trying to stress to Paul was that editing either of those
files doesn't _change_ what Debian branch you're on, only _reflect_ what
branch you're on -- because it seemed to me he might have briefly
thought otherwise.

_______________________________________________
conspire mailing list
conspire at linuxmafia.com
http://linuxmafia.com/mailman/listinfo/conspire


   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxmafia.com/pipermail/conspire/attachments/20180704/6620d616/attachment.html>