FYI
If the windows filesystem is NTFS, you will not be able to write to it. Linux only mounts the NTFS in read-only and cannot be changed even with a remount.
0 0 means that the filesystem partitions will not be checked at each startup.
for showing partitions use fdisk:
fdisk /dev/hda
The number of cylinders for this disk is set to 2432.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p <--- print partitions
Disk /dev/hda: 20.0 GB, 20003880960 bytes
255 heads, 63 sectors/track, 2432 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 1217 9775521 83 NTFS
/dev/hda2 1218 1226 72292+ 83 Linux
/dev/hda3 1227 2432 9687195 83 Linux
Command (m for help): q <--- quit
now if you know the partition of your Windows system you also need to have the ntfs-filesystem option as module or fix compiled in you kernel.
I notice a file .autofsck (0 bytes) in / i am assuming when a system is properly shut down it deletes that file if you shutdown clean and writes it again when you boot backup and if you pull the plug on a machine when the machine boots it checks for the file and if its there it does an fsck. Can anyone confirm or deny my hypothesis?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.