On Tue, Aug 16, 2005 at 09:49:31PM +0200, Bastian Blank wrote:
> On Tue, Aug 16, 2005 at 12:53:56PM +0200, Wouter Verhelst wrote:
> > The devmapper system requires the /dev/mapper directory and the
> > /dev/mapper/control node to exist in order to function correctly. When
> > using DevFS or udev, these nodes are created automatically when the
> > devmapper module is loaded; however, if you use a static /dev directory
> > (which is what I'm using), then you have to set those up manually.
>
> A strace of dmsetup shows the following:
> | stat64("/dev/mapper/control", 0xbfffe5a8) = -1 ENOENT (No such file or
> directory)
> | umask(022) = 027
> | stat64("/dev/mapper", 0xbfffd4fc) = -1 ENOENT (No such file or
> directory)
> | mkdir("/dev", 0777) = -1 EEXIST (File exists)
> | mkdir("/dev/mapper", 0777) = 0
> | umask(027) = 022
> | mknod("/dev/mapper/control", S_IFCHR|0600, makedev(10, 63)) = 0
> | open("/dev/mapper/control", O_RDWR|O_LARGEFILE) = 3
That only works if you use dmsetup. If you use cryptsetup (which I did),
then it doesn't.
--
The amount of time between slipping on the peel and landing on the
pavement is precisely one bananosecond
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
