Running VirtualBox VM host on ReadyNAS Pro

WhoCares? wrote:

jmalmlund wrote: Edit: It seems Netgear has made some mistake or I'm just tired... the new GPL source supplied contains kernel version 2.6.37.5.RNx86_64.2.2 but the kernel that's included in 4.2.16 is version 2.6.37.5.RNx86_64.2.1 I don't know how you come to that conclusion. The GPL sources I'm using contain a kernel that identifies itself as "2.6.37.5.RNx86_64.2.1" - as can be checked by cd linux-2.6.37.5/arch/x86/configs grep "RNx86" * Should list defconfig.smp with a CONFIG_LOCALVERSION string of ".RNx86_64.2.1"

Well, just like you said Stefan, it was the second alternative that turned out to be correct, I was tired (and running a fever) and clearly not paying enough attention to what I was doing. Thank you for pointing that out to me ;)

When I started out working with *nix systems a friend of mine helped me and gave me a script that I've kept around , it's purpose was to make a diff between two kernel sources and transfer manual changes from the old source tree to the new one's config. A nice help back then before I learnt how to configure the kernel I needed for the computer I had, but not very foolproof I've now learnt... because I hadn't copied /arch/x86/configs/defconfig.smp to .config it took my entire .config file from the 4.2.15 source and basically copied that into the 4.2.16 source tree... now you might remember that the kernel in 4.2.15 was CONFIG_LOCALVERSION=".RNx86_64.2.2" and THAT'S what I saw and noticed that it didn't match `uname -r` ...

So this is to all I've might have offended by saying that the Netgear guys had messed up, Please forgive my mistake! :oops: :oops:

The good news is that since I started over with a fresh source doing all my changes manually I've now got all needed bits and pieces up and running and my VirtualBox servers are back up. Still running a slight fever so I'm going to hit the sack again (already slept most of the day) and unless someone else beats me to it I'll try and write an short how-to on installing/updating all that's needed to get VirtualBox up-to-date and running on 4.2.16.

Once again, thank you Stefan for :slap: you gave me, guess I needed it :roll: :lol: