4 ms·
I didn't study the busybox connection, but why would anyone think vmkernel and vmklinux could be "reasonably considered independent and separate works in themse
by paxcoder 10y ago
I didn't study the busybox connection, but why would anyone think vmkernel and vmklinux could be "reasonably considered independent and separate works in themselves" especially considering the source from the sfconservancy site linked to in the article?
- rrdharan 10y agoI don't think anyone considers vmklinux independent, and indeed vmklinux is itself open-sourced (in a kludgey but compliant way): https://my.vmware.com/group/vmware/details?downloadGroup=ESXI650-OSS&productId=614 https://my.vmware.com/group/vmware/details?downloadGroup=ESX... The debate has always been about whether the vmkernel is itself a derived work of vmklinux or Linux.
- belorn 10y agoCan vmware replace the linux kernel and vmklinux, and still have a functioning vmkernel? Ie, for some definition of independence and separation, how independent are vmklinux and vmkernel, and how separated are they in function and use? Could one simply remove the linux parts and plug in a different unix like kernel? With two independent work I should be able to put them each on a different computer and have a meaningful result from doing so. Two work can have a cumulative effect when brought together, but independent they need to still be meaningful and working on their own. If I arbitrary separate a program, I can obviously not do so since they will not start, function proper or produce a meaningful effect on their own.
- deleted 10y ago[deleted]
- paxcoder 10y agoI asked why anyone would think that vmklinux (the linux derivative) and vmkernel were independent. Please refer to the quote from the license I've provided, and belorn's thought experiment here.