Page: Previous  1, 2, 3, 4, 5, 6, 7, 8  Next

techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 1877
Location: East Coast, West Coast? I know it's one of them.
Back to top
Posted: Oct 4, 09, 8:29    
Big set of bug fixes, should finally fix the broken vbox non ose installation of guest additions.

Cleaned up all code, added more error handling and error logging to improve debugging and end user control.

got rid of exit on non critical script errors and replaced with warn user then return to script for non fatal error conditions like a package failing to download.

Tnanks to orbit for his/her patience to get this issue finally resolved.
Crust
Status: Contributor
Joined: 08 Sep 2008
Posts: 58
Back to top
Posted: Oct 5, 09, 10:50    
Is it possible to have the kernel module rebuilding for the vbox-non-ose work for people who get virtualbox from the virtualbox repos? i.e., just running:

:: Code ::
/etc/init.d/vboxdrv setup
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 1877
Location: East Coast, West Coast? I know it's one of them.
Back to top
Posted: Oct 5, 09, 13:34    
how would svmi know if it is a deb based install via dpkg or an apt based install from non ose sun repos?
Crust
Status: Contributor
Joined: 08 Sep 2008
Posts: 58
Back to top
Posted: Oct 5, 09, 17:58    
does it need to know? can't it just look for

:: Code ::
/etc/init.d/vboxdrv


or

:: Code ::
/etc/init.d/vboxdrv-ose


and run

:: Code ::
/etc/init.d/vboxdrv setup


or

:: Code ::
/etc/init.d/vboxdrv-ose setup


if it finds the file and depending on which file it finds?

The repo packages and the deb package names are different so the svmi logic will not work with packages installed from sun's repos.
Crust
Status: Contributor
Joined: 08 Sep 2008
Posts: 58
Back to top
Posted: Oct 5, 09, 18:09    
If it helps, the package name of the latest version of virtualbox from sun's repos is:

:: Code ::
virtualbox-3.0
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 1877
Location: East Coast, West Coast? I know it's one of them.
Back to top
Posted: Oct 6, 09, 17:56    
I'd have to look at the logic, I don't remember anymore why one method was used and not another.

if /etc/init.d/virtualbox exists and accepts that non-ose build module command it can probably be updated I'd guess.
iotaka
Status: Interested
Joined: 13 Apr 2009
Posts: 48
Back to top
Posted: Oct 7, 09, 0:51    VirtualBox 3.0.8
New VirtualBox 3.0.8 for Linux
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 1877
Location: East Coast, West Coast? I know it's one of them.
Back to top
Posted: Oct 7, 09, 9:05    
updated
Crust
Status: Contributor
Joined: 08 Sep 2008
Posts: 58
Back to top
Posted: Oct 7, 09, 9:48    
Thanks for looking into it. Half of my systems use the sun repos for virtualbox, and I'm really liking how they are packaging virtualbox and maintaining their repos.
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 1877
Location: East Coast, West Coast? I know it's one of them.
Back to top
Posted: Oct 7, 09, 12:44    
crust, svmi already does this for non ose modules: if you select the build vbox non ose module option, that's the command it runs.

What I wonder is if that should be the command ose runs as well, currently it checks for module deb first, then m-a module.

However, that looks like it might have been broken because of that bug that was just fixed re getting the installed version data, and that should also be working again now as a side affect of fixing that bug, re non ose modules.

Just to make sure, show me this output from a sun repo installed vbox non ose:
:: Code ::
dpkg -l | grep virtualbox | awk '{print $2}'
Display posts from previous:   
Page: Previous  1, 2, 3, 4, 5, 6, 7, 8  Next
All times are GMT - 8 Hours