Updating sarge to etch wyoming dating laws
During installation, say that the system clock is set to GMT.
Debian will take care of setting your localised time correctly (as an offset from GMT).
I have no experience of running a server openly on the Internet or a (Linux) server at high capacity for large numbers of users so expect the advice as applied to these realms to be vague.
Everything in here comes from direct experience at one time or another but my most thorough day-to-day server knowledge, reflected in sections in here and in other guides from thegoldenear.org, is in Samba domain controllers; mail servers; print servers; Linux and Debian.
Download and apply any security updates using 'aptitude update' then 'aptitude dist-upgrade' Make a rescue/boot floppy disk: If you have a SCSI hard disk (or disks) and a USB-attached disk, say, for backing up to, and you aren't using Linux RAID and/or LVM, then the machine can fail to boot when the USB-attached disk is connected.
Similarly the downloadable ISO images available for installing Debian are updated, they have a 'r' designation.
Today I had some problems with updating my Debian system because some of the updates had unresolved dependencies.
I found out that my provider made a small mistake inside /etc/apt/– can you find it? In my the security updates are loaded from the stable repository and the other packages from the sarge repository.
Three weeks ago these two were the same (because sarge was stable) and now etch is stable – problem!
I changed the security update path to sarge and everything works fine again.
If the USB-attached disk is attached on startup then most of the time, but not always, some way into loading the system Linux fails because the USB-attached disk has been recognised as and part of the kernel is trying to be loaded from the backup disk.