On Fri, 18 Aug 2006, Kay Sievers wrote:
On Fri, 2006-08-18 at 08:59 -0700, Andrew Pimlott wrote:
On Fri, Aug 18, 2006 at 02:13:53PM +0200, Kay Sievers wrote:
It's almost impossible to make libvolume_id stricter, in most cases,
even the kernel mounts a mkswap formatted (and obviously
I suspect I have a similar problem to the reporter of this bug. I have
a swap partition that is set up as an encrypted dm device with a random
key, using the cryptsetup package. cryptsetup now has a test that calls
vol_id, which thinks that my partition is vfat:
% sudo /lib/udev/vol_id
To follow up, I just filed bug 383581 against util-linux (the package of
mkswap). I chose to pick on mkswap because that was the case I could
reproduce--indeed, it leaves the first 1k (containing MSDOS5.0)
untouched; whereas mke2fs overwrote it.
Andrew
--
To UNSUBSCRIBE, email to [EMAIL
On Thu, 2006-08-17 at 22:46 -0700, Andrew Pimlott wrote:
I suspect I have a similar problem to the reporter of this bug. I have
a swap partition that is set up as an encrypted dm device with a random
key, using the cryptsetup package. cryptsetup now has a test that calls
vol_id, which thinks
On Fri, 2006-08-18 at 08:59 -0700, Andrew Pimlott wrote:
On Fri, Aug 18, 2006 at 02:13:53PM +0200, Kay Sievers wrote:
It's almost impossible to make libvolume_id stricter, in most cases,
even the kernel mounts a mkswap formatted (and obviously corrupt) fat
volume just fine and allows
On Fri, Aug 18, 2006 at 02:13:53PM +0200, Kay Sievers wrote:
It's almost impossible to make libvolume_id stricter, in most cases,
even the kernel mounts a mkswap formatted (and obviously corrupt) fat
volume just fine and allows writing to it.
Ok, thanks for the explanation.
It's mkswap which
6 matches
Mail list logo
