1. 17 Nov, 2009 4 commits
    • batched reads for lxc_console · 92db2bb0
      Michael Tokarev authored
      Instead of doing I/O one-byte-at-a-time in lxc_console,
      which is slow, let's do it in batches.  Only for output
      (from container to the host system), since input is most
      likely one-byte-at-a-time anyway (from a keyboard).
      Signed-off-by: 's avatarMichael Tokarev <mjt@tls.msk.ru>
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • host consoles/ttys in containers · 994f905e
      Michael Tokarev authored
      I noticed that container's consoles aren't quite useable
      (be it lxc-console or lxc-start with getty bound to /dev/console).
      The main problem is a complete lack of window resizing support:
      when I resize an xterm window with lxc-start or lxc-console, the
      "guest" does not know about that and continues to think that the
      terminal is 80x25 still.
      
      Is it just a lack of functionality (missing implementation) or
      something problematic?
       
      Ok, the attached patch fixes this.
       
      It moves the 'master' variable out of main function so it's
      accessible from the signal handler, sets up SIGWINCH handler
      to call a (newly created) winsz() function that gets the
      current tty size using TIOCGWINSZ ioctl and if that works,
      sets up the pty size using TIOCSWINSZ.  That same function
      is called at the start as well, when setting up the signal
      handler.
      Signed-off-By: 's avatarMichael Tokarev <mjt@tls.msk.ru>
      Signed-off-By: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • Choose configuration directory · aef4ebcf
      Andrian Nord authored
      Maybe it will be more logical to keep configs into /etc/lxc/?
      
      Or, maybe, just use --with-config-path=/some/path switch into configure,
      which could be overridden as user wants to? Something like this one (in
      assumption, that this is up to user to create corresponding directory):
      Signed-off-by: 's avatarAndrian Nord <NightNord@gmail.com>
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • cleanup <lxc/lxc.h> · 00b3c2e2
      Cedric Le Goater authored
      <lxc/lxc.h>  should only include what is needed. This patch removes
      all useless headers from lxc.h and fixed other .c files.
      Signed-off-by: 's avatarCedric Le Goater <clg@fr.ibm.com>
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
  2. 13 Nov, 2009 12 commits
  3. 12 Nov, 2009 3 commits
  4. 11 Nov, 2009 1 commit
  5. 09 Nov, 2009 1 commit
  6. 04 Nov, 2009 2 commits
    • lxc: lxc version to reflect string in AC_INIT (V2) · d5cf4386
      Michel Normand authored
      I changed the code to have lxc version to reflect the
      string set in AC_INIT of configure.ac
      rather than to report only the 3 first digits
      
      update: use PACKAGE_VERSION in place of VERSION
      Signed-off-by: 's avatarMichel Normand <normand@fr.ibm.com>
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • configure.ac - allow user to switch off/on documentation generation · 5c8f9bd8
      Andrian Nord authored
      Andrian Nord <NightNord@gmail.com>:
      >> > > As documentation requires docbook2man to be installed, which is not,
      >> > > otherwise, required for proper LXC work or compilation process, it
      >> > > might be usefull to be able to switch it off.
      
      Michel Normand <normand@fr.ibm.com>:
      > > For me, it is Ok to add a --enable/disable/-doc,
      > > but not make configure to fail if no option specified
      > > and no docbook2man package.
      > > 
      > > For me it should be optionnal.
      > > I like the current behaviour where configure is running without option
      > > and is enabling/disabling by itself the doc building.
      > > Could you send a new patch with this idea ?
      
      Andrian Nord <NightNord@gmail.com>:
      Of course. You mean, that you what default behaviour to remain
      auto-detection? That is:
      --enable-doc: require docbook2man or fail, generate mans
      --enable-doc=auto, or not specified (default): check for docbook2man,
      generate mans if found, silently ignore if not found (I suppose
      diagnostic message is redundant, as information already contains into
      ./configure --help)
      --disable-doc: never check for docbook2man and don't gen mans
      
      Here comes a patch what do this, as far as I see
      (I'm sorry for violating post-rules in previous mail, now I'll do all
      right, I hope. Should I attach patch anyway, as it might be usefull
      for applying?)
      Signed-off-by: 's avatarAndrian Nord <NightNord@gmail.com>
      Acked-by: 's avatarMichel Normand <normand@fr.ibm.com>
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
  7. 03 Nov, 2009 1 commit
  8. 23 Oct, 2009 1 commit
  9. 22 Oct, 2009 3 commits
  10. 15 Oct, 2009 1 commit
  11. 12 Oct, 2009 4 commits
  12. 09 Oct, 2009 7 commits