/dev/sdc1    /media/usb  auto  rw,user,noauto  0 0 

 /dev/fd0    /media/usb  auto  rw,user,noauto,unhide  0 0

/dev/fd0    /media/usb  auto  rw,user,noauto,unhide  0 0
/dev/cdrom /media/cdrom   auto    ro,user,noauto,unhide   0      0
/dev/dvd /media/dvd   auto    ro,user,noauto,unhide   0      0
UUID=1ca9f25d-b134-439d-a5ce-96742e82318d swap swap defaults 0 0
UUID=65340826-b5ea-48ed-b2e6-5696d7523a02 / ext3 defaults 0 1
UUID=b0da76d2-2e7d-4051-923d-ff69f07bc4d9 /usr ext3 defaults 0 1
UUID=d668b720-89c8-4a34-9b33-d8829b33a11e /home ext3 defaults 0 1
UUID=de3e5194-1002-4a0a-b132-27c3b6f89571 /boot ext2 defaults 0 1
/dev/sda1 /media/C ntfs-3g defaults,users,auto 0 1
/dev/sda5 /media/D ntfs-3g defaults,users,auto 0 1
/dev/sda6 /media/E ntfs-3g defaults,users,auto 0 1
/dev/sda7 /media/F ntfs-3g defaults,users,auto 0 1
 

USING PASSWORDS
 
 FTP
 
   To ftp files using name+passwd, include them in the URL like:
 
        curl ftp://name:[email protected]:port/full/path/to/file
 
   or specify them with the -u flag like
 
        curl -u name:passwd ftp://machine.domain:port/full/path/to/file
 
 FTPS
 
   It is just like for FTP, but you may also want to specify and use
   SSL-specific options for certificates etc.
 
   Note that using FTPS:// as prefix is the "implicit" way as described in the
   standards while the recommended "explicit" way is done by using FTP:// and
   the --ftp-ssl option.
 
 SFTP / SCP
 
   This is similar to FTP, but you can specify a private key to use instead of
   a password. Note that the private key may itself be protected by a password
   that is unrelated to the login password of the remote system.  If you
   provide a private key file you must also provide a public key file.
 
 HTTP
 
   Curl also supports user and password in HTTP URLs, thus you can pick a file
   like:
 
        curl http://name:[email protected]/full/path/to/file
 
   or specify user and password separately like in
 
        curl -u name:passwd http://machine.domain/full/path/to/file
 
   HTTP offers many different methods of authentication and curl supports
   several: Basic, Digest, NTLM and Negotiate. Without telling which method to
   use, curl defaults to Basic. You can also ask curl to pick the most secure
   ones out of the ones that the server accepts for the given URL, by using
   --anyauth.
 
   NOTE! Since HTTP URLs don't support user and password, you can't use that
   style when using Curl via a proxy. You _must_ use the -u style fetch
   during such circumstances.
 
 HTTPS
 
   Probably most commonly used with private certificates, as explained below.
 
PROXY
 
 Get an ftp file using a proxy named my-proxy that uses port 888:
 
        curl -x my-proxy:888 ftp://ftp.leachsite.com/README
 
 Get a file from a HTTP server that requires user and password, using the
 same proxy as above:
 
        curl -u user:passwd -x my-proxy:888 http://www.get.this/
 
 Some proxies require special authentication. Specify by using -U as above:
 
        curl -U user:passwd -x my-proxy:888 http://www.get.this/
 
 A comma-separated list of hosts and domains which do not use the proxy can
 be specified as:
 
        curl --noproxy localhost,get.this -x my-proxy:888 http://www.get.this/
 
 If the proxy is specified with --proxy1.0 instead of --proxy or -x, then
 curl will use HTTP/1.0 instead of HTTP/1.1 for any CONNECT attempts.
 
 curl also supports SOCKS4 and SOCKS5 proxies with --socks4 and --socks5.
 
 See also the environment variables Curl support that offer further proxy
 control.