Sergio Belkin <[email protected]> wrote: > I was talking about technical issues not about licenses,
But a technology with commercial licensing, such as some of the "guest" functionality of VirtualBox cannot be covered by LPI (LPI Exam Developers can correct me if I'm wrong), only OpenSource licenses -- and in the case of the kernel -- GPLv2 compatible. > for example this case: https://www.dedoimedo.com/computers/kvm-virtualbox.html That's for the "host" modules. Objective 102.6 has to do with "guest" support. > I think that 102.6 objective has nothing to do with licenses issues. The entire LPI Objectives avoid all non-Open Source, and in the case of the kernel, non-GPLv2 compatible licenses. That's why I brought it up, because it's the #1 detail that will _remove_ a technology from consideration. It's unavoidable. > But again, it could be nice if someone of people that wrote the last > LPI version could clarify what does stand for "linux extensios". > Again, my question is: is about kvm? is about cgroups (containers)? If you re-check my initial quote, I only addressed your comment: "Also it could be interesting be aware of conflicts between kvm and virtualbox." For the "guest" objective, I don't see how LPI could cover "guest" conflicts between KVM and VirtualBox. VirtualBox has many components that are not GPLv2 compatible in the kernel. - bjs -- Bryan J Smith - http://www.linkedin.com/in/bjsmith E-mail: b.j.smith at ieee.org or me at bjsmith.me _______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
