Quoting Benjamin Kiessling (mittages...@l.unchti.me):
> Hi,
>
> > That's still doable, just a bit more work. Take a look at
> >
> > ls -l /dev/lxc
> >
> > (or whatever is the vg you're looking at). It has symlinks to the real
> > devices. When you look at the link targets, you can find their
Hi,
> That's still doable, just a bit more work. Take a look at
>
> ls -l /dev/lxc
>
> (or whatever is the vg you're looking at). It has symlinks to the real
> devices. When you look at the link targets, you can find their maj:min.
> For me,
>
> serge@sergelap:~$ ls -l /dev/lxc
> total 0
> l
Quoting Daniel Lezcano (dlezc...@fr.ibm.com):
> On 05/13/2011 12:13 AM, Benjamin Kiessling wrote:
> >Hi,
> >
> >under Debian (and in general I think) LVM requires udev to work
> >at all which makes it unusable in a container environment. Has
> >anybody tried to get it working in a container?
>
> Y
On 05/13/2011 12:13 AM, Benjamin Kiessling wrote:
> Hi,
>
> under Debian (and in general I think) LVM requires udev to work
> at all which makes it unusable in a container environment. Has
> anybody tried to get it working in a container?
You can use udev inside a container. It is not optimal beca
Hi,
under Debian (and in general I think) LVM requires udev to work
at all which makes it unusable in a container environment. Has
anybody tried to get it working in a container?
My setup consists of a logical volume that's mapped in the container
which the container user should be able to subdiv
