I forgot to also mention that upgrading via the update manager did not modify my fstab either, so the issue must be how fstab is generated in breezy's installer?
On 10/4/06, Cody Somerville <[EMAIL PROTECTED]> wrote: > > I originally installed Ubuntu and then upgraded to Breezy via update > manager. In my original install, my fat drivers were marked 0 0 (ie. don't > check) in fstab and I didn't modify them. Some also said on IRC that they > thought this was fixed before (I forget the handle, sorry). > > On 10/4/06, Scott James Remnant <[EMAIL PROTECTED]> wrote: > > > > I can find no evidence of any attempt to prevent FAT filesystems from > > being checked on boot. > > > > Also from investigation, there's no way to exclude FAT filesystems from > > the boot check. The filesystem list is inclusive, so to disable FAT, we > > > > have to list the filesystem types we do want to check and omit FAT from > > that list. > > > > That is just too error-prone to consider. > > > > Will revisit for edgy+1 when we do fsck-on-block-device-add rather than > > "fsck -a" > > > > ** Changed in: Ubuntu > > Sourcepackagename: None => sysvinit > > Importance: Undecided => Wishlist > > Status: Unconfirmed => Confirmed > > > > -- > > vfat filesystems checked by fsck > > https://launchpad.net/bugs/48806 > > > > > > -- > > > Firefox (www.getfirefox.com) -- A browser you can trust -- Firefox (www.getfirefox.com) -- A browser you can trust -- vfat filesystems checked by fsck https://launchpad.net/bugs/48806 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
