Re: [cobalt-users] /etc/issue.net

[Duncan Laurie <duncan@xxxxxxxxxx>]

In article <442200404.20000915154814@xxxxxxxxxxxxx> you wrote:
| 
| Hello,
| 
| I want to change /etc/issue.net out of security purposes. I will copy
| the original to /etc/issue.save and modify issue.net with pico -w
| 
| Anyone else did this? Can any problems arise? What to do in the case
| of an update (e.g. OS Update)? Restoring issue.save or can I just
| install the update over it?
| 
| Thanks,
| Florian
| 

You can replace it with whatever you want, my choice is usually to
make it a zero-length file.  The only catch is you will need to
remove (or comment) a line in /etc/rc.d/rc.local, otherwise it will
be recreated the next time you reboot.  The exact line number differs
from product to product, but they should all read the same:

cp -f /etc/issue /etc/issue.net

It is doubtful updates will harm your changes; the /etc/issue.net
file is not actually owned by any RPM since it is created on boot,
and rc.local is part of the initscripts RPM, which has not yet
been part of any Cobalt update.


-duncan