Kingdomcome,
I reinstalled today to make the install persistant with boot parameters :
tce= hda1 opt=hda1 home=hda1. It works fine for the extensions.
But it turns out it'll need some scripting for VirtualBox... According to the VBox user manual, the .run script :
• It builds the VirtualBox kernel module (vboxdrv) and installs it.
• It creates /etc/init.d/vboxdrv, an init script to start the VirtualBox kernel module.
• It creates a new system group called vboxusers.
• It creates symbolic links to VirtualBox, VBoxSDL, VBoxVRDP, VBoxHeadless and VBoxManage in /usr/bin.
• It creates /etc/udev/60-vboxdrv.rules, a description file for udev, if that is present, which makes the module accessible to anyone in the group vboxusers.
• It writes the installation directory to /etc/vbox/vbox.cfg.
Apart from the /opt/VirtualBox folder, nothing remains after a reboot. Do you think this is something that can be "fixed" in a way or another ?
The OpenGL extension you refer to was freeglut. I installed it and it worked, but it turns out Xorg (which is dependent of it) was the one who really fixed my problem.
While I was reinstalling, I tried to use only the necessary extensions from my previous post.
The ones necessary (at least for me) to have a working environment for VirtualBox are the following (indented are dependencies) :
make
Qt-4.5-base
glib2
openssl.0.9.8.h
qt-4.5-base
linux-header-2.6.29.1-tinycore
binutils
gcc
gcc_libs
python-dev
python
sqlite3
openssl-0.9.8h (already installed)
tcl_tk
XVesa
Xorg-7.4
expat2
fontconfig
openssl-0.9.8m
pixman
SDL
libmad
Hope this answers you question and will help in the extension development.
PS : I already did the trick for ps after installing procps, I was wondering if they could replace BusyBox' binaries or symlink automatically. Anyway, this doesn't prevent VBox from running, so the priority is low on this one.
Take care !
dondamiano