On Thu, Jul 15, 2010 at 11:42:07PM +0200, Christoph Anton Mitterer wrote: > Package: vmfs-tools > Severity: serious > Justification: Policy 9.1.1 > > > 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 :)
That was actually done so on purpose, because while the intent is that the program is a normal fsck program, at the moment, it really doesn't do much, and doesn't work as people using /sbin/fsck would expect it to. So until the program actually does what it is intended to, I'm not exactly sure it is safe to put it in /sbin. OTOH, I could rename it, but except for nitpicking, what exactly would be the point? What do fellow developpers think? Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
