Changes between Version 84 and Version 85 of Linux build instructions

Timestamp:

Jan 28, 2016 8:19:16 AM (8 years ago)

Author:

Frank Mehnert

Comment:

--

Linux build instructions

@@ -130 +130 @@
  In case you have more than one CPU core, kmk will automatically do a parallel build.
 
- 4. If you made a ''hardened'' build (that is, you omitted the ''--disable-hardened'' switch from configure) you have to set some symbolic links manually to be able to start VMs from the bin/ directory:
-{{{
-cd out/linux.x86/release/bin/components
-ln -s ../VBoxDDU.so .
-ln -s ../VBoxREM.so .
-ln -s ../VBoxRT.so .
-ln -s ../VBoxVMM.so .
-ln -s ../VBoxXPCOM.so .
-}}}
-
+ 4. Running a hardened build from tue bin/ directory will not work because all hardened binaries do explicit link against libraries from /opt/VirtualBox (fixed path).
 
 == Building !VirtualBox packages for distribution ==
@@ -167 +158 @@
 == Running your build ==
 
-You can run !VirtualBox directly from the build target directory (`out/linux.x86/release/bin/`). But first of all, you must build and install the !VirtualBox kernel module, whose sources will have been copied to the build target directory. 
+You can run !VirtualBox directly from the build target directory (`out/linux.x86/release/bin/`) if the build was not hardened. But first of all, you must build and install the !VirtualBox kernel module, whose sources will have been copied to the build target directory. 
 
 So, issue the following: 
@@ -178 +169 @@
 Then it should have been installed to your modules directory and you can load it using {{{modprobe vboxdrv}}}. Make sure you give yourself read and write access to {{{/dev/vboxdrv}}}.
 
-If you made a ''hardened build'', make sure that the setuid stubs have the correct permissions:
-{{{
-for f in VirtualBox VBoxHeadless VBoxSDL VBoxBFE VBoxNetDHCP VBoxNetAdpCtl; do
-  chown root.root $f
-  chmod 4511 $f
-done
-}}}
-
 Finally, you can start one of the frontends, e.g.
 {{{