existing line in the /etc/fstab file, and modify it to reflect the new
     drive.

     The device name (/dev/xxx) can be got from viewing:

dmesg | less
            ____________________________________________________

In Short, Dig This

   Wed, 31 Mar 2004 01:45:38 -0800
   Jim Dennis ([54]the LG Answer Guy)

   Possibly there's not a sysadmin around who hasn't needed to do a host lookup
   now and then, to make sure they know what addresses are really being found
   when a DNS lookup is made.

   nslookup is deprecated, host can be confusing, dig is the nice tool for the
   job - regardless of attempts to claim it is old too, it will be around a
   long time. But who really wants to get a long listing full of semicolon
   comments and things?

; <<>> DiG 9.2.3rc4 <<>> linuxgazette.net
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 605
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;linuxgazette.net.              IN      A

;; ANSWER SECTION:
linuxgazette.net.       86400   IN      A       64.246.26.120

;; AUTHORITY SECTION:
linuxgazette.net.       86400   IN      NS      ns1.linuxmafia.com.
linuxgazette.net.       86400   IN      NS      ns1.genetikayos.com.

;; ADDITIONAL SECTION:
ns1.linuxmafia.com.     61864   IN      A       198.144.195.186
ns1.genetikayos.com.    61864   IN      A       64.246.26.120

;; Query time: 153 msec
;; SERVER: 216.240.40.162#53(216.240.40.162)
;; WHEN: Wed Mar 31 01:39:18 2004
;; MSG SIZE  rcvd: 144

   Unless I'm tracking the path of authority rather than just checking the
   address, I don't care either.

(jimd@phobos) ~$ dig +short a linuxgazette.net
64.246.26.120

   Short, sweet, and to the point. Replace "a" with "mx" or "ns" as you please,
   but this is a lot handier for scripting; I don't have to invoke my talent
   for awk and grep one-liners on DNS checks anymore.
            ____________________________________________________

DNS proxy/cache (Tip)

   Tue, 16 Mar 2004 00:11:33 +0100
   Karl-Heinz Herrmann ([55]kh1dump from khherrmann.de)

   Hi,

   I had an annoying little problem: My home network has grown to 3 PC's -- one
   directly on the phone line, the others connected via WLAN. Usually I would
   pick one dial-up provider and stick with that. Unfortunately the German
   ISP's are a big mess of call-by call providers with constantly changing
   tarifs.

   The directly connected box is only the dial-in and firewall/NAT Router, the
   other two are my Laptop and desktop.

   The annoying problem: Everytime I change the provider I had to change the
   resolv.conf on all systems according to the new nameservers as transmitted
   via [i]ppp protocol.

   My solution: dproxy
          [56]http://dproxy.sourceforge.net

   It serves as a proxy/cache for DNS lookups. It uses regular sys-calls for
   namelookups and reacts instantly (no kill -HUP or similar) to new entries in
   /etc/resolv.conf. This is on the router of course and everytime pppd changes
   the resolv.conf for the new provider it simply uses the new values.

   The other two machines have the router as the nameserver and always get the
   correct  information  (even  offline, so a connection is of course not
   possible). No manual changing anymore.

   K.-H.
            ____________________________________________________

Making filenames lowercase

   Wed, 31 Mar 2004 10:05:38 -0500
   Ben Okopnik ([57]LG Technical Editor)

   Sometimes, despite our best eforts with "unzip -L", we end up with a bunch
   of files the names of which are ALL IN CAPS. The easy way to deal with these