Edited by dlanor at Wed Nov 26, 2014 02:52 |
I agree, of course. I never argued against your repo.
mattrix replied at Tue Nov 25, 2014 14:20 We need the complete source in a GIT repo.
The benefits of having it in a repo is huge and shouldn't need explaining.
Transferring 3GB files around the internet is not good for anyone.
(Perhaps I phrased that post badly, as I was in a hurry at the time.)
Not as the only repo. But it can be a useful way to present individual patches and deviations from the main repo.
Hosting just the changes as well is not ideal.
It can be a good way to share things for testing and improvements which are not yet ready for adding to the main repo.
Regarding VMware VS VirtualBox:
VMware offers a choice of how many CPUs to emulate and how many virtual cores each virtual CPU should have.
And even with a total number of virtual cores set to just 1, the emulator software can still use more, though it only emulates 1.
But software in the guest OS intended for multi-core use will of course work better with more virtual cores being emulated.
VirtualBox also offers a choice of how many CPUs to emulate, though it's really a choice of cores, without emulating the ties between core and the CPU they belong to.
So I guess my earlier phrasing was incorrect. It's not multi-core that VBox is lacking, but multi-CPU emulation.
Also, the GUI shows a red warning for any choice above 3, which I consider silly for a physical i7 CPU which has 4 physical cores and 8 threads.
As for Vagrant I don't use it. What does it offer beyond what the VBox GUI does ?
All-in-all I simply prefer using VMware. I guess it's a matter of personal taste.
I especially dislike how the VBox 'Guest Additions' modify the behavior of Ubuntu's Unity GUI.
Good. Then we don't need to change build instructions to handle it.
If you look in the build script for the Kernel, it's actually using -J* anyway
But in a later post you seem to be saying that this multi-core use had to be disabled for stability.
Was this really the case ? Or was the instability rather due to some other problem (like too little RAM) ?
Best regards: dlanor