Arch Linux

I have updated files to the latest initscripts.
Please include this fix in the next initscripts. These are trivial fixes and they works for me few months and doesn't break anything.

Do we include the shfs module in the arch kernel? I can't find it.

No, because it is not included in vanilla kernel. shfs is in Community.
There are two ssh-based remote filesystems: sshfs (which requires fuse) and shfs (standalone kernel module). Both of them (and all fuse filesystems) need these proposed fixes to work seemly from fstab.

I see that you are preparing a bunch of fixes for the next initscripts release. Please include these fixes too.

@Judd even if shfs isn't included in -current, this small fix will give full support to whom is actually using it

Re-opened by Roman Kyrylych:

Please add 2>/dev/null to /sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK as in my proposal or else when fuse or shfs will be mounted on boot user will see fsck messages about errors in fstab (that's because fsck doesn't like # char)

And please change "Unmounting network filesystems" to "Unmounting Network Filesystems" for better consistency with "Mounting Network Filesystems" in netfs.

PS: intoducing $NETFS was nice idea! :-)

>> Please add 2>/dev/null to /sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK as in my proposal or else when fuse or shfs will be mounted on boot user will see fsck messages about errors in fstab (that's because fsck doesn't like # char)

Hmm, that's a bit of a problem for me. Some users may very well want to see the output from fsck, since it could contain useful information if they have filesystem issues.

>> And please change "Unmounting network filesystems" to "Unmounting Network Filesystems" for better consistency with "Mounting Network Filesystems" in netfs.

Sure.

I suppose we could test. Does fsck spit out the useful information on stdout or stderr?

I use this almost 5 months already and I always see useful fsck messages. Only messages about errors in fstab go to stderr, but # char is not an error, it is required by fuse and shfs (at least). The most correct fix would be to patch fsck, but IMHO redirecting stderr to /dev/nul is not bad workaround.

I see initscripts-0.7.2-7 moved to Current. :-) But you didn't include redirection of fsck stderr messages to /dev/null.
Line 140 should be /sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK 2>/dev/null
I'm sure that fsck doesn't output any usefull info to stderr except errors in fstab. These errors are false in case of using fuse or shfs, which means that on every boot usersof fuse or shfs will get those error messages visible (of course, fuse and shfs are mounted correctly after that but these messages are annoying).
Messages about errors in filesystem are produced to stdout. I've had few filesystem problems and didn't miss any usefull otput from fsck with my patched initscripts. So I'm pretty sure it is safe to redirect fsck stderr output to /dev/null.

Of course it would be better if this false error messages were fixed in mainstream (directly in fsck), or maybe apply patch to fix it, but I cannot supply such patch.

Judd, please add 2>/dev/null and close this trivial bug finally. ;-)