Package: initscripts Version: 2.86.ds1-1 Severity: minor The use of /forcefsck to force fsck to run on a clean filesystems is problematic if / is read-only. Notably you must first remount / read-write and create the file (yuck), the init scripts will be unable to remove it, and you end up having to go through another remove; rm; remount cycle. (I should note the wishlist bug #339850 also features an even more bogus version of this problem)
I have to suggest the use of similar files on /var, which is guarenteed to be read-write. The disadvantage would be /var has to be mounted before testing. The issue of needing / being read-only isn't be an issue, as you'd only need this if / was read-only. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | [EMAIL PROTECTED] PGP 8881EF59 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ \___\_|_/82 04 A1 3C C7 B1 37 2A*E3 6E 84 DA 97 4C 40 E6\_|_/___/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]