"Faster than virtualization, but harder to implement, containers are a promising security technology for Linux. Watch the 2.6.24 kernel for experimental support for creating and managing containers."
To read all comments associated with this story, please click here.
Member since:2006-01-03
"Because of an ever-changing environment with 'so so' ABIs. Maybe the should first introduce a stable and developer kernel again beforce trying to be professional."
What do you mean? The kernel userspace ABI is very stable (you can run stuff compiled for linux 1.0 on a recent 2.6 kernel, as long as it is statically compiled, that is, since (g)libc has changed a lot since then). Now, the kernel _internal_ ABI isn't stable, but I don't see how that affects virtualization/containers...
Member since:2006-01-12
Member since:2005-07-06
I was about to say:...
"A. Main-line tree kernel modules that are effected by any ABI change are fixed by the submitter.
B. Non-mainline tree kernel modules are of no interest to the ABI change submitter. (And rightly so)
Now, you may claim that working in a dynamic environment is harder then working in a static one, and you'll be right - but nobody is forcing the vserver developer's to do so.
Plus, the number of major ABI breakages is far lower then you imagine/claim. As someone that does maintain a very size-able out-of-tree project, I usually make one fix per 2-4 kernel releases, and unlike other environments (*Cough Windows NDIS *Cough) Linux ABI changes are well documented (LKML, code documentation, etc) in advance."
... But then I saw this: "beforce trying to be professional."
- Gilboa
P.S. someone that calld other people unprofessional should -really- consider checking his spelling before going on a rampage.
Edited 2007-11-11 14:27
Member since:
2006-07-15
>Faster than virtualization, but harder to implement
Because of an ever-changing environment with 'so so' ABIs. Maybe the should first introduce a stable and developer kernel again beforce trying to be professional.