2015-03-03 16:57 GMT-03:00 Frank Mehnert <[email protected]>: > On Tuesday 03 March 2015 13:37:24 Larry Finger wrote: >> On 03/03/2015 05:43 AM, Marcos Felipe Rasia de Mello wrote: >> > And we are bitten again. >> > >> > https://www.virtualbox.org/pipermail/vbox-dev/2013-August/011718.html >> > >> > Suggestion (plus grep cleanup): >> > >> > --- vboxadd.sh.orig 2014-05-06 07:02:16.000000000 -0300 >> > +++ vboxadd.sh 2015-03-03 08:27:39.199344842 -0300 >> > @@ -286,8 +286,8 @@ >> > >> > start() >> > { >> > >> > begin "Starting the VirtualBox Guest Additions "; >> > >> > - uname -r | grep -q -E '^2\.6|^3' 2>/dev/null && >> > - ps -A -o comm | grep -q '/*udevd$' 2>/dev/null || >> > + expr `uname -r` '>=' '2.6' >/dev/null && >> > + ps -A -o comm | grep -q '/*udevd$' || >> >> Ah, a long-term solution! :) >> >> Seriously, is anyone going to be using VirtualBox on any version of Linux >> older than 2.6? After all, 2.6.32 is the only 2.6 kernel still being >> maintained at kernel.org. > > That doesn't matter. The VirtualBox Guest Additions still support Linux 2.4 > and I see no reason to restrict the code to newer kernels. Of course that's > completely different on hosts. >
Run legacy stuff in VMs is pretty common. It is a virtualization selling point after all. _______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
