Opened 17 years ago
Closed 17 years ago
#1614 closed enhancement (fixed)
Missing Run Level shortcuts with generic Linux .RUN install => Fixed in 1.6.2
Reported by: | BobRobertson | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 1.6.0 |
Keywords: | Run Level | Cc: | |
Guest type: | other | Host type: | other |
Description
I have installed VB three times, using the generic Linux .RUN installer. I noticed that the VirtualBox kernel driver and networking are not initialized in run level 2, which is the default run level in Debian. I'm using "testing" and "unstable", so the pre-packaged Debian binaries for "stable" are not usable for me.
Symbolic links
S20vboxdrv -> ../init.d/vboxdrv S20vboxnet -> ../init.d/vboxnet
are installed in /etc/rc3.d/ and /etc/rc5.d/ but not /etc/rc2.d/ which is the Debian default run level.
Please consider putting the symbolic links into Run Levels 2 through 5. People who know enough to alter their run level will know to delete these symbolic links if they do not want those drivers to be active. Sadly, it took me a while to figure out why VirtualBox would give me an error when I first started my machine, but work once I "rebuilt" the driver.
The initial installation and subsequent driver "rebuilds" all occurred in Run Level 2, which I must assume your installer does not check before creating the symbolic links.
Change History (2)
comment:1 by , 17 years ago
Summary: | Missing Run Level shortcuts with generic Linux .RUN install → Missing Run Level shortcuts with generic Linux .RUN install => Fixed in 1.6.2 |
---|
comment:2 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Your observation is right and this problem will be fixed in 1.6.2.