There are a few ways to manage the lx brand. Discussing the various ways is both off-topic on the discuss list as well as pointless till someone's willing to start cutting their teeth.
I still feel that lx brands have a certain place (e.g. you gain the usual benefits of zones, and they work even if your Illumos is running under a hypervisor itself). Long-term, it is also potentially easier to keep up-to-date than Xen, too. As I said, if people are wanting to actually work on it, rather than talk about working on it, contact me. :) I'll see if I can't procure resources to make it workable, provided there's commitment to the task, as well as sharing the ideas which have been proposed to me in the past few months. --Matt -- Matt Lewandowsky Greenviolet http://greenviolet.net/ ---------------------------------------- > Date: Thu, 2 Sep 2010 22:42:05 +0200 > From: [email protected] > To: [email protected]; [email protected]; [email protected] > CC: [email protected] > Subject: Re: [illumos-Discuss] Fate of the lx brand? > > Matt Lewandowsky wrote: > > > > > There's always been more interest in the community than effort when it > > comes to the lx brand. As Garrett said, it's extremely non-trivial to > > maintain, let alone enhance. Dragons have been sighted in the realm of lx. > > > > If someone is really going to put effort into this piece of code, I would see > it integrated in a different way as a final goal: > > We are no longer forced to do political decisions like Sun did in the past. > So it would make sense to allow to use the lx brand not only in a dedicated > zone > but also anywhere else. > > The basic idea for this module is a re-implementation of LKP (Linux Kernel > Personality) from SCO. > > I did not boot UniXWare since 2 years, so let me explain from memory: > > From a UNIX process, you see a tree: > > /linux/* > > that contains a complete Linux installation. > > From a Linux process, you see a tree: > > /unix/* > > that contains the complete UNIX installation. > > If you try to exec() a new process with a PATH that begins with "/linux", > then the Linux compatibility is turned on. Any further process inherits an > environment that grants Linux behavior even though the PATH does not begin > with "/linux" as the chroot() for Linux processes is inside "/linux". > > Jörg > > -- > EMail:[email protected] (home) Jörg Schilling D-13353 Berlin > [email protected] (uni) > [email protected] (work) Blog: http://schily.blogspot.com/ > URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily _______________________________________________ Discuss mailing list [email protected] http://lists.illumos.org/m/listinfo/discuss
