[SOLVED] Remove all traces of VirtualBox?

business_kid · 05-11-2022, 11:30 AM

I want to purge my system of VB and start over. I'm getting this error on startup

Code:

VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel 5.15.27.

/etc/rc.d/rc3.d/S10vboxadd: line 293: /opt/VBoxGuestAdditions-6.1.18/other/check_module_dependencies.sh: No such file or directory
vboxdrv.sh: Starting VirtualBox services.
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
Cannot run /usr/sbin/VBoxService

I'm not on VB-6.1.18, I'm on VB-6.1.34 (not that it works), and VB-6.1.26 was in between. I also thought the guest additions were for guests, so I raised an eyebrow at the host accessing them. They are usually installed by the .run file which does have a --replace option, but not an --uninstall one.

How can I purge that on Slackware?

bassmadrigal · 05-11-2022, 11:47 AM

Have a look in /etc/rc.d/init.d for the actual virtualbox startup files (vbox*) and then the /etc/rc.d/rc[0-6].d/ folders for the symlinks to run the virtualbox startup files depending on the runlevel.

pan64 · 05-11-2022, 11:50 AM

it is not an advice, just a possibility: if you want you can remove /etc/rc.d/rc3.d/S10vboxadd or just move to it into another directory.
And if you want to completely remove vbox you need to [re]move this file too.

business_kid · 05-11-2022, 01:45 PM

Thanks, it's hust the init stuff, is it?

Code:

cd /etc/rc.d
rm rc?.d/* && rm init.d/*

That does it. I also got /opt/VirtualBox/, & /usr/bin/V* symlinks. We'll see what good that does.

bassmadrigal · 05-11-2022, 04:19 PM

Quote:

Originally Posted by business_kid

Thanks, it's hust the init stuff, is it?

It should be if you already got /opt/ and /usr/bin/ stuff.

business_kid · 05-12-2022, 04:36 AM

Quote:

Originally Posted by bassmadrigal

It should be if you already got /opt/ and /usr/bin/ stuff.

Yeah. I even thought of /lib/modules/whatever.

rkelsen · 05-12-2022, 07:47 AM

Quote:

Originally Posted by business_kid

Code:

cd /etc/rc.d
rm rc?.d/* && rm init.d/*

This would have also removed your functions script. Future installations of VBox or other software which expects "RedHat-isms" may not work.

business_kid · 05-12-2022, 01:15 PM

Quote:

Originally Posted by rkelsen

This would have also removed your functions script. Future installations of VBox or other software which expects "RedHat-isms" may not work.

Nope - just vbox stuff. No functions script was there

Windu · 05-12-2022, 01:57 PM

Quote:

Originally Posted by business_kid

Nope - just vbox stuff. No functions script was there

Well then you already broke your box long ago. You might want to re-install the 'sysvinit-functions' package.

business_kid · 05-12-2022, 03:22 PM

Well, I reinstalled it, but I'm not sure I did break it. It was searching the rc?.d directories already.

bassmadrigal · 05-12-2022, 04:09 PM

VirtualBox should've installed four scripts in /etc/rc.d/init.d/ and then many symlinks in /etc/rc.d/rc[0-6].d/. At least that's how it's done with VB 6.1.32 installed using their .run file.

Code:

jbhansen@craven-moorhead:~$ tree /etc/rc.d/*/
/etc/rc.d/init.d/
|-- README.functions
|-- functions
|-- vboxautostart-service
|-- vboxballoonctrl-service
|-- vboxdrv
`-- vboxweb-service
/etc/rc.d/rc0.d/
|-- K65vboxautostart-service -> /etc/rc.d/init.d/vboxautostart-service
|-- K65vboxballoonctrl-service -> /etc/rc.d/init.d/vboxballoonctrl-service
|-- K65vboxweb-service -> /etc/rc.d/init.d/vboxweb-service
`-- K80vboxdrv -> /etc/rc.d/init.d/vboxdrv
/etc/rc.d/rc1.d/
|-- K65vboxautostart-service -> /etc/rc.d/init.d/vboxautostart-service
|-- K65vboxballoonctrl-service -> /etc/rc.d/init.d/vboxballoonctrl-service
|-- K65vboxweb-service -> /etc/rc.d/init.d/vboxweb-service
`-- K80vboxdrv -> /etc/rc.d/init.d/vboxdrv
/etc/rc.d/rc2.d/
|-- K65vboxautostart-service -> /etc/rc.d/init.d/vboxautostart-service
|-- K65vboxballoonctrl-service -> /etc/rc.d/init.d/vboxballoonctrl-service
|-- K65vboxweb-service -> /etc/rc.d/init.d/vboxweb-service
`-- K80vboxdrv -> /etc/rc.d/init.d/vboxdrv
/etc/rc.d/rc3.d/
|-- S20vboxdrv -> /etc/rc.d/init.d/vboxdrv
|-- S35vboxautostart-service -> /etc/rc.d/init.d/vboxautostart-service
|-- S35vboxballoonctrl-service -> /etc/rc.d/init.d/vboxballoonctrl-service
`-- S35vboxweb-service -> /etc/rc.d/init.d/vboxweb-service
/etc/rc.d/rc4.d/
|-- S20vboxdrv -> /etc/rc.d/init.d/vboxdrv
|-- S35vboxautostart-service -> /etc/rc.d/init.d/vboxautostart-service
|-- S35vboxballoonctrl-service -> /etc/rc.d/init.d/vboxballoonctrl-service
`-- S35vboxweb-service -> /etc/rc.d/init.d/vboxweb-service
/etc/rc.d/rc5.d/
|-- S20vboxdrv -> /etc/rc.d/init.d/vboxdrv
|-- S35vboxautostart-service -> /etc/rc.d/init.d/vboxautostart-service
|-- S35vboxballoonctrl-service -> /etc/rc.d/init.d/vboxballoonctrl-service
`-- S35vboxweb-service -> /etc/rc.d/init.d/vboxweb-service
/etc/rc.d/rc6.d/
|-- K65vboxautostart-service -> /etc/rc.d/init.d/vboxautostart-service
|-- K65vboxballoonctrl-service -> /etc/rc.d/init.d/vboxballoonctrl-service
|-- K65vboxweb-service -> /etc/rc.d/init.d/vboxweb-service
`-- K80vboxdrv -> /etc/rc.d/init.d/vboxdrv

0 directories, 34 files

The files in red are part of a normal Slackware install.

You should've removed the /etc/rc.d/init.d/vbox* files and /etc/rc.d/rc?.d/*vbox* symlinks. If you did a full removal of the contents of /etc/rc.d/init.d/, then you are missing the functions script, which may cause 3rd-party packages that rely on /etc/init.d/ for startup/shutdown to not function properly.

business_kid · 05-13-2022, 06:23 AM

As you see from my previous post I have reinstalled the functions script.

Foe sure, VB is the only thing using /etc/rc.d/rc?.d/ directories, so 'RedHat-isms' (which I personally loathe) are zero besides VB. I'll now reinstall VB-6.1.34, along with some ancient windows version and try zoom on it.

pan64 · 05-13-2022, 06:43 AM

/etc/rc.d is a system directory, contains all the init scripts used during the boot. https://unix.stackexchange.com/quest...-vs-etc-init-d

bassmadrigal · 05-13-2022, 10:47 AM

Quote:

Originally Posted by pan64

/etc/rc.d is a system directory, contains all the init scripts used during the boot. https://unix.stackexchange.com/quest...-vs-etc-init-d

business_kid was referencing the rc[0-6].d/ folders that are under /etc/rc.d/. Those are not used with normal Slackware startup, but allows Slackware to support pre-systemd 'RedHat-isms' startup with little to no modification.

I'm pretty sure they're aware of what /etc/rc.d/ itself is for.

business_kid · 05-15-2022, 07:38 AM

I finally decided to reinstall VB: The reinstall had this line:

Code:

Removing previous installation of VirtualBox 6.1.34 r150636 from /opt/VirtualBox

Python found: python2.7, installing bindings...

So I obviously hadn't got it all out

.