http://doc.coker.com.au/computers/going-live-linux-server/ Documents that are not date based Thu, 20 Nov 2008 16:29:06 +0000 http://wordpress.org/?v=2.6.3 http://doc.coker.com.au/computers/going-live-linux-server/#comment-41 Jon Holdsworth Wed, 23 Jan 2008 04:11:27 +0000 http://doc.coker.com.au/computers/going-live-linux-server/#comment-41 Keep a separate copy of /boot on a separate disk, and keep it up to date with the _exact_ same contents as the real /boot. Have a rescue disk handy with a grub installer on it and PRACTICE using it before you install anything. Keep a separate copy of /boot on a separate disk, and keep it up to date with the _exact_ same contents as the real /boot. Have a rescue disk handy with a grub installer on it and PRACTICE using it before you install anything.

]]> http://doc.coker.com.au/computers/going-live-linux-server/#comment-40 ZOG Wed, 23 Jan 2008 04:02:03 +0000 http://doc.coker.com.au/computers/going-live-linux-server/#comment-40 yes the memtest thing has bitten me a few times.. also maybe (some of these are more basic security things): run nmap from a remote location to make sure no un-needed services are running. lock down ssh via sshd_config (no root logins, etc) if possible check switch port duplex settings are all matching what the eth interface thinks it should be, and after blasting with traffic no errors on ethernet interface or packet loss to nearby host. yes the memtest thing has bitten me a few times..
also maybe (some of these are more basic security things):
run nmap from a remote location to make sure no un-needed services are running.
lock down ssh via sshd_config (no root logins, etc)
if possible check switch port duplex settings are all matching what the eth interface thinks it should be, and after blasting with traffic no errors on ethernet interface or packet loss to nearby host.

]]>