[Bug 925513] Re: plymouth should not run in container

2012-02-16 Thread Michael Adam
@Serge, I might have misready your statement about network config. I do add nettwork config (veth0, dev=virbr0, etc) manually. There is no /etc/lxc/lxc.conf in my system. The reason I used a config file snipped for lxc-create was exactly to get this network virtualization layer into the container

[Bug 925513] Re: plymouth should not run in container

2012-02-16 Thread Michael Adam
@Serge, thanks for your comments. I have experimented a little more. And I found that --path is indead at the very least misleading: If I don't use --path, then the config (snippet) given to lxc-create by "-f" is merged with the config that the template creates. If i do use paht, then the -f fil

[Bug 925513] Re: plymouth should not run in container

2012-02-16 Thread Michael Adam
Confirmed: running the same lxc-create command with "--trim" creates a directly usable container. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/925513 Title: plymouth should not run in

[Bug 925513] Re: plymouth should not run in container

2012-02-16 Thread Michael Adam
@Serge, Could you explain why use of --path can lead to X crashing where lxc-create without --path is not? My motivation was: I don't want lxc-create to create the rootfs under /var/lib/lxc. I need the stuff to be stored elsewhere. I thought that the --path option in the template was made exactl

[Bug 925513] Re: plymouth should not run in container

2012-02-15 Thread Michael Adam
Hi, plymouth running in the container prevents me from using the container at all, it kills my X instead: I created a 11.10 container with the following lxc-create command on freshly installed 11.10: sudo lxc-create -n ubuntu1 -f ./ubuntu1-template.conf -t ubuntu -- --release=oneiric --path=/dat

[Bug 271922] Re: Default ACL not applied on files created through CIFS filesystem (mount.cifs)

2009-02-05 Thread Michael Adam
I was looking for a reason why Ubuntu kernels dont have CIFS_POSIX_XATTR set? So the nifty posix acl extensions can never be used with stock kernel. Should we open a new enhancement bug report for this or was I just not clever enough searching... Michael -- Default ACL not applied on files crea