[Bug 26689] Re: Device mapper devices have incorrect ownership and permissions.

2008-09-23 Thread Scott James Remnant
This is clearly not a clear duplicate - if it's not the same bug, don't just reopen an old one ** Changed in: devmapper (Ubuntu) Status: Confirmed = Fix Released -- Device mapper devices have incorrect ownership and permissions. https://bugs.launchpad.net/bugs/26689 You received this bug

[Bug 26689] Re: Device mapper devices have incorrect ownership and permissions.

2008-06-24 Thread Reinhard Tartler
/dev/vg* are device mapper devices as well, no? -- Device mapper devices have incorrect ownership and permissions. https://bugs.launchpad.net/bugs/26689 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list

Re: [Bug 26689] Re: Device mapper devices have incorrect ownership and permissions.

2008-06-24 Thread Eric Shattow
I don't know how it does this. I thought it was the vgscan command that created those /dev/vg* device nodes. I'm remembering an early system I ran to use LVM. The /dev/mapper/* entries existed when there were no /dev/vg* nodes. When I wanted /dev/vg* nodes I had to issue a vgscan --mknodes

[Bug 26689] Re: Device mapper devices have incorrect ownership and permissions.

2008-06-06 Thread Reinhard Tartler
the bug reappeared in gutsy and is still present in hardy. I've noticed it via bug #235689 that is a clear duplicate of this one ** Changed in: devmapper (Ubuntu) Status: Fix Released = Confirmed -- Device mapper devices have incorrect ownership and permissions.

[Bug 26689] Re: Device mapper devices have incorrect ownership and permissions.

2008-06-06 Thread Eric Shattow
How is bug #235689 a clear duplicate? The /dev/mapper entries in bug #235689 are fine, it is the LVM / crypt stuff in /dev/vg* that is messed up. -- Device mapper devices have incorrect ownership and permissions. https://bugs.launchpad.net/bugs/26689 You received this bug notification because