Re: [lxc-devel] [Lxc-users] lxc-start and lucid container

2010-05-18 Thread Wilhelm
Am 17.05.2010 16:53, schrieb l...@zitta.fr:
> Le 17/05/2010 18:09, Wilhelm a écrit :
>
>> Am 17.05.2010 14:59, schrieb zitta.fr:
>>  
>>> Hi,
>>>
>>> try this :
>>>
>>>  cat>  /path_to_lucid_root/etc/init/console.conf
>>>  # console - getty
>>>  #
>>>  # This service maintains a getty on stdin from the point the
>>> system is
>>>  # started until it is shut down again.
>>>
>>>  start on stopped rc RUNLEVEL=[2345]
>>>  stop on runlevel [!2345]
>>>
>>>  respawn
>>>  exec /sbin/getty -8 38400 console
>>>
>>>
>> this is exactly the contents of /etc/init/tty1.conf
>>  
> Sorry, I did let a comment that could makes you think it is tty1.conf
> But no, it is not.
> Look at this diff :
>
> --- tty1.conf2010-04-02 02:13:25.0 +0200
> +++ console.conf2010-05-17 16:59:53.770083492 +0200
> @@ -1,4 +1,4 @@
> -# tty1 - getty
> +# console - getty
>   #
>   # This service maintains a getty on tty1 from the point the system is
>   # started until it is shut down again.
> @@ -7,4 +7,4 @@
>   stop on runlevel [!2345]
>
>   respawn
> -exec /sbin/getty -8 38400 tty1
> +exec /sbin/getty -8 38400 console
>
>> but it doesn't work
>>  
> did you even try?
>

oh yes, overlooked that.
Ok, works fine!

Thanks!

>>  
>>> Regards,
>>>
>>> Guillaume ZITTA
>>>
>>> Le 17/05/2010 16:31, Wilhelm a écrit :
>>>
 Hi all,

 I have a slight problem using a lucid container (on a lucid host): if I
 start the container via lxc-start, no console login starts up. I
 have to
 use lxc-console from a differnet terminal. If I use a lenny container,
 lxc-start shows the start up log messages and finally the getty/login.

 I'm using the lxc-packages from lucid:

 r...@ubuntu01:~# dpkg -l lxc
 Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig
 Löschen/Halten
 | Status=Nicht/Installiert/Config/U=Entpackt/Fehlgeschl. Konfiguration/
 Halb installiert/Trigger erWartet/Trigger anhängig
 |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler:
 GROSS=schlecht)
 ||/ Name
 VersionBeschreibung
 +++-==-==-

 ii  lxc
 0.6.5-1Linux containers userspace tools


 The start trace is:

 r...@ubuntu01:/var/lib/lxc/lucid# lxc-start -n lucid
 --logfile=/dev/stderr --logpriority=TRACE -- /sbin/init --verbose
  lxc-start 1274106224.666 INFO lxc_conf - tty's configured
  lxc-start 1274106224.669 DEBUGlxc_start - sigchild
 handler set
  lxc-start 1274106224.669 INFO lxc_start - 'lucid' is
 initialized
  lxc-start 1274106224.681 DEBUGlxc_conf - instanciated
 macvlan
 'mcwEvnvl', index is '8' and mode '0'
  lxc-start 1274106224.699 DEBUGlxc_cgroup - using cgroup
 mounted at '/lxc-cgroup'
  lxc-start 1274106224.699 DEBUGlxc_cgroup -
 '/lxc-cgroup/20474' renamed to '/lxc-cgroup/lucid'
  lxc-start 1274106224.711 DEBUGlxc_conf - move 'eth1' to
 '20474'
  lxc-start 1274106224.711 INFO lxc_conf - 'lucid'
 hostname has
 been setup
  lxc-start 1274106224.713 DEBUGlxc_conf - mac address
 '4a:49:43:49:79:bd' on 'eth0' has been setup
  lxc-start 1274106224.714 DEBUGlxc_conf - 'eth0' has been
 setup
  lxc-start 1274106224.714 INFO lxc_conf - network has
 been setup
  lxc-start 1274106224.715 DEBUGlxc_cgroup - using cgroup
 mounted at '/lxc-cgroup'
  lxc-start 1274106224.716 DEBUGlxc_conf - cgroup
 'devices.deny' set to 'a'
  lxc-start 1274106224.716 DEBUGlxc_conf - cgroup
 'devices.allow' set to 'c 1:3 rwm'
  lxc-start 1274106224.716 DEBUGlxc_conf - cgroup
 'devices.allow' set to 'c 1:5 rwm'
  lxc-start 1274106224.716 DEBUGlxc_conf - cgroup
 'devices.allow' set to 'c 5:1 rwm'
  lxc-start 1274106224.716 DEBUGlxc_conf - cgroup
 'devices.allow' set to 'c 5:0 rwm'
  lxc-start 1274106224.716 DEBUGlxc_conf - cgroup
 'devices.allow' set to 'c 4:0 rwm'
  lxc-start 1274106224.716 DEBUGlxc_conf - cgroup
 'devices.allow' set to 'c 4:1 rwm'
  lxc-start 1274106224.716 DEBUGlxc_conf - cgroup
 'devices.allow' set to 'c 1:9 rwm'
  lxc-start 1274106224.716 DEBUGlxc_conf - cgroup
 'devices.allow' set to 'c 1:8 rwm'
  lxc-start 1274106224.716 DEBUGlxc_conf - cgroup
 'devices.allow' set to 'c 136:* rwm'
  lxc-start 1274106224.716 DEBUGlxc_conf - cgroup
 'devices.allow' set to 'c 5:2 rwm'
  

[lxc-devel] [GIT] lxc branch, master, updated. 1f1b18e754e4c1157ffaadeb3d0ae05e5c83cb5a

2010-05-18 Thread Daniel Lezcano
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "lxc".

The branch, master has been updated
   via  1f1b18e754e4c1157ffaadeb3d0ae05e5c83cb5a (commit)
  from  9232212afdad25536afc8d241606e00eac3b0c87 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
commit 1f1b18e754e4c1157ffaadeb3d0ae05e5c83cb5a
Author: Daniel Lezcano 
Date:   Tue May 18 17:40:04 2010 +0200

support ipv4 broadcast specification

Add the broadcast specification, if none is specified, it is automatically
computed from the addr & mask.

syntax:
lxc.network.ipv4 = 172.20.0.2/24 172.20.255.255

Signed-off-by: Daniel Lezcano 

---

Summary of changes:
 src/lxc/network.c |  112 ++--
 src/lxc/network.h |7 +++-
 2 files changed, 71 insertions(+), 48 deletions(-)


hooks/post-receive
-- 
lxc

--

___
Lxc-devel mailing list
Lxc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-devel


[lxc-devel] Using initctl inside a container with upstart?

2010-05-18 Thread Wilhelm
Hi all,

is it safe to use initctl in a container using upstart (as ubuntu lucid)?

Especially, upstart-init uses an abstract unix-socket:

connect(3, {sa_family=AF_FILE, path=@"/com/ubuntu/upstart"}, 22) = 0

Is this socket separated from the parent (host) namespace, so the 
container can't affect the host-system?

-- 
Wilhelm



--

___
Lxc-devel mailing list
Lxc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-devel


[lxc-devel] [GIT] lxc branch, master, updated. 0093bb8ced5784468daf8e66783e6be3782e8fea

2010-05-18 Thread Daniel Lezcano
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "lxc".

The branch, master has been updated
   via  0093bb8ced5784468daf8e66783e6be3782e8fea (commit)
  from  1f1b18e754e4c1157ffaadeb3d0ae05e5c83cb5a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
commit 0093bb8ced5784468daf8e66783e6be3782e8fea
Author: Daniel Lezcano 
Date:   Tue May 18 19:13:26 2010 +0200

added locally modified files for broadcast support

Signed-off-by: Daniel Lezcano 

---

Summary of changes:
 src/lxc/conf.c|9 +
 src/lxc/conf.h|2 +-
 src/lxc/confile.c |   17 -
 3 files changed, 18 insertions(+), 10 deletions(-)


hooks/post-receive
-- 
lxc

--

___
Lxc-devel mailing list
Lxc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-devel


Re: [lxc-devel] [Lxc-users] Using initctl inside a container with upstart?

2010-05-18 Thread Serge E. Hallyn
Quoting Wilhelm (wilhelm.me...@fh-kl.de):
> Hi all,
> 
> is it safe to use initctl in a container using upstart (as ubuntu lucid)?
> 
> Especially, upstart-init uses an abstract unix-socket:
> 
> connect(3, {sa_family=AF_FILE, path=@"/com/ubuntu/upstart"}, 22) = 0
> 
> Is this socket separated from the parent (host) namespace, so the 
> container can't affect the host-system?

Yes, so long as you use a private net_ns, it will be separated.  If
you don't use a private net_ns, then not only will it talk to the
host's upstart, but, bc of current limitations on credentials passing,
upstart won't be able to tell if the container doesn't have
CAP_SYS_BOOT.

-serge

--

___
Lxc-devel mailing list
Lxc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-devel