On Tue, May 31, 2011 at 11:37:18PM -0500, Eric Sandeen wrote: > > I'm less certain of the change from fsck -t $FSTYP to fsck.$FSTYP > > What issue are you avoiding? wouldn't fsck -t ext4dev invoke > fsck.ext4dev anyway? This is a change I make locally when I've been debugging my bigalloc code as well. There reason for that is because I want to override the fsck.ext4 that would get used by using path hacking. The problem was that fsck -t ext4 will look for /sbin/fsck.ext4, where as I wanted it to use the fsck.ext4 that was first in the PATH. So I changed "/sbin/fsck -t $FSTYP" to "fsck.$FSTYP" and made sure /sbin was tacked onto the path. It might be that the right answer is that fsck should have an environment variable or some other way of controlling the search path it uses to find the fsck.XXX binary. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
