[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#674994: marked as done (Linux Container support)

Your message dated Fri, 13 Jul 2012 18:05:34 -0600
with message-id <20120714000534.GJ5758@mykerinos.kheops.frmug.org>
and subject line This bug does not belong to tasksel...
has caused the Debian Bug report #674994,
regarding Linux Container support
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

674994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674994
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Hash: SHA1

Package: tasksel
Version: 3.09
Severity: wishlist

It would be very nice to have support for installing virtual
desktop systems based upon lxc.

The idea is to setup thin clients on the users' desktops
(Windows or Linux) and a pool of powerful lxc servers running
Debian, providing virtual desktop systems including kde,
gnome, xfce, etc. The system could be based upon vnc, rdp or

Currently the tasksel meta packages depend upon a _lot_ of
packages relying upon the presence of hardware (real or virtual):
udev, XWindow drivers, audio support, packages for defining
keyboard layouts or console fonts, etc. These packages get into
trouble on kernel-based virtualization. They try to bypass libc
to access the kernel and get some kind of "permission denied".
If you are lucky then they just don't work at run time, but
usually they fail in the postinst script. This is fatal.


Version: GnuPG v1.4.12 (GNU/Linux)


--- End Message ---
--- Begin Message ---
...but more to packages that tasks depend upon.

So, I suggest that, if some "lxc-friendlyness" is required for some
packages in the tasks, it should be required from the packages in the
task, not something that tasksel can solve itself.


Attachment: signature.asc
Description: Digital signature

--- End Message ---

Reply to: