Hi. I might have spotted a policy violation here (therefore the sevirity serious). Policy section 9.1.1. specifies: "The location of all installed files and directories must comply with the Filesystem Hierarchy Standard (FHS), version 2.3, with the exceptions noted below,..." The FHS in turn specifies: "The following files, or symbolic links to files, must be in /sbin if the corresponding subsystem is installed: ... fsck.* mkfs.* " (see http://www.pathname.com/fhs/pub/fhs-2.3.html#SPECIFICOPTIONS8). As far as I can tell this is not the case, right? I also do not see any exception for this in section 9.1.1. I don't judge whether /sbin is really a better location,.... just wanted to bring this to your attention :) Cheers, Chris.
severity 589228 minor thanks mkfs.ubifs and mkfs.jffs2 link against liblzo2 which is in /usr/lib so putting these binaries in /sbin doesn't make sense. These binaries are not used as traditional mkfs utilities which create filesystems on block devices. Instead they are used to create "loopback" files which include a prebuilt filesystems. keeping the bug open in case someone else wonders about the same issue. Riku
But isn't jffs2 used as root-fs in some embedded devices? And wouldn't it be necessary for that to have it in /bin ? Then we should use wontfix, shouldn't we? Cheers, Chris.
yes it used rootfs no they dont need in mkfs.jffs2 in sbin. please try to understand that mkfs.jffs2 is not used to format block (or nand) devices. it is used to precreate filesystems on regular files. yes.