• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: fsck / never in fstab?  (Read 1083 times)
jaycatt
Newbie
*

Karma: 0
Posts: 4


View Profile
« on: July 29, 2009, 01:15:08 PM »

Hi.  General question for the group...  I was trying to set up /etc/fstab and I noticed that the file system entries all end in 0, to never fsck on boot.  The guide I read suggested that / should be set to 1 and everything else to 2, so that fsck checks 1 first and then everything else simultaneously. 

Here's what it looks like now (without my USB HD and SD card entries)
Code:
# UNCONFIGURED FSTAB FOR BASE SYSTEM
tmpfs /lib/init/rw tmpfs rw,nosuid,mode=0755 0 0
/proc /proc proc rw,noexec,nosuid,nodev 0 0
sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
varrun /var/run tmpfs rw,nosuid,mode=0755 0 0
varlock /var/lock tmpfs rw,noexec,nosuid,nodev,mode=1777 0 0
udev /dev tmpfs rw,mode=0755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0
rootfs / rootfs rw 0 0
tmpfs   /var/cache/apt  tmpfs   defaults,noatime

1) Why is / set to never fsck?
2) Is there a reason I shouldn't change / to 1 and the others to 2 to check on boot as needed?

Thanks!

John
Logged

birdman
Sr. Member
****

Karma: 4
Posts: 443


View Profile WWW
« Reply #1 on: July 29, 2009, 04:42:12 PM »

They're all either kernel-based (sysfs, proc), or built-from-scratch-at-boot (tmpfs).
Expect /, which is rootfs.  But I think that is built at boot time too? (I'm sure someone will correct me if wrong).
So there's no point fsck'ing them as they all only just been created.
Logged

Pages: [1]
Print
Jump to: