On Tue, 2004-10-12 at 18:02, Bao Cao wrote: > I just naively followed the settings for hda6 and > changed /etc/fstab by using: > /dev/hdb6 /mnt/homewd ext3 > defaults 0 0 Change the "0 0" at the end of this line to "1 2". This will cause the filesystem to be checked periodically at reboot. > df -hl > Filesystem Size Used Avail Use% Mounted on > /dev/hda3 13G 4.2G 7.8G 35% / > /dev/hda2 97M 7.6M 85M 9% /boot > none 252M 0 252M 0% /dev/shm > /dev/hda6 5.0G 3.7G 1.1G 78% /home > /dev/hdb1 48G 35G 14G 73% /mnt/win_g > /dev/hdb5 48G 102M 48G 1% /mnt/win_h > /dev/hdb6 89G 13G 72G 16% > /mnt/homewd > /dev/hda1 19G 4.9G 14G 27% > /mnt/windows > > It seems hdb6 is back, but I am not sure any possible > future risk. I have to logon as root to do "chmod 777 > /mnt/homewd" to get write permission, how to change > fstab so that I get all the permission automatically? Having done this once, you shouldn't need to do it again. However, mode 777 is a security risk (any user on your machine can write to it); you would be better off changing it to mode 755 (owned by root) and creating subdirectories belonging to each user, with mode 700. If you are the only user of the machine, change ownership of /mnt/homewd to your account and make it mode 700 (or 755). > > and (as root) > > fdisk -l /dev/hdb > > bash: fdisk: command not found > > Does that mean I didn't install fdisk? No, it means you became root using "su" (which doesn't set up root's PATH) instead of "su -" (which does). With the PATH set up properly, fdisk will work. Paul. -- Paul Howarth <paul@xxxxxxxxxxxx>
