Changeset 105289 in vbox for trunk/doc/manual/en_US/dita/topics/install-linux-manual.dita
- Timestamp:
- Jul 12, 2024 9:07:43 AM (7 months ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/dita/topics/install-linux-manual.dita
r99797 r105289 5 5 6 6 <body> 7 <p> 8 If you cannot use the shell script installer described in 9 <xref href="install-linux-alt-installer.dita#install-linux-alt-installer"/>, you can perform 10 a manual installation. Run the installer as follows: 11 </p> 7 <p>If you cannot use the shell script installer described in <xref 8 href="install-linux-alt-installer.dita#install-linux-alt-installer"/>, you can perform a manual 9 installation. Run the installer as follows: </p> 12 10 <pre xml:space="preserve">./VirtualBox.run --keep --noexec</pre> 13 <p> 14 This will unpack all the files needed for installation in the 15 directory <codeph>install</codeph> under the current 16 directory. The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application files are contained 17 in <filepath>VirtualBox.tar.bz2</filepath> which you can 18 unpack to any directory on your system. For example: 19 </p> 11 <p>This will unpack all the files needed for installation in the directory <codeph>install</codeph> under the 12 current directory. The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application files are contained 13 in <filepath>VirtualBox.tar.bz2</filepath> which you can unpack to any directory on your system. For 14 example: </p> 20 15 <pre xml:space="preserve">sudo mkdir /opt/VirtualBox 21 16 sudo tar jxf ./install/VirtualBox.tar.bz2 -C /opt/VirtualBox</pre> 22 <p> 23 To run the same example as root, use the following commands: 24 </p> 17 <p>To run the same example as root, use the following commands: </p> 25 18 <pre xml:space="preserve">mkdir /opt/VirtualBox 26 19 tar jxf ./install/VirtualBox.tar.bz2 -C /opt/VirtualBox</pre> 27 <p> 28 The sources for <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s kernel module are provided in 29 the <filepath>src</filepath> directory. To build the module, 30 change to the directory and use the following command: 31 </p> 20 <p>The sources for <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s kernel module are provided in the 21 <filepath>src</filepath> directory. To build the module, change to the directory and use the following 22 command: </p> 32 23 <pre xml:space="preserve">make</pre> 33 <p> 34 If everything builds correctly, run the following command to 35 install the module to the appropriate module directory: 36 </p> 24 <p>If everything builds correctly, run the following command to install the module to the appropriate module 25 directory: </p> 37 26 <pre xml:space="preserve">sudo make install</pre> 38 <p> 39 In case you do not have sudo, switch the user account to root 40 and run the following command: 41 </p> 27 <p>In case you do not have sudo, switch the user account to root and run the following command: </p> 42 28 <pre xml:space="preserve">make install</pre> 43 <p> 44 The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> kernel module needs a device node to 45 operate. The above <userinput>make</userinput> command will tell 46 you how to create the device node, depending on your Linux 47 system. The procedure is slightly different for a classical 48 Linux setup with a <filepath>/dev</filepath> directory, a 49 system with the now deprecated <userinput>devfs</userinput> and a 50 modern Linux system with <userinput>udev</userinput>. 51 </p> 52 <p> 53 On certain Linux distributions, you might experience 54 difficulties building the module. You will have to analyze the 55 error messages from the build system to diagnose the cause of 56 the problems. In general, make sure that the correct Linux 57 kernel sources are used for the build process. 58 </p> 59 <p> 60 Note that the <filepath>/dev/vboxdrv</filepath> kernel module 61 device node must be owned by root:root and must be 62 read/writable only for the user. 63 </p> 64 <p> 65 Next, you install the system initialization script for the 66 kernel module and activate the initialization script using the 67 right method for your distribution, as follows: 68 </p> 29 <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> kernel module needs a device node to operate. The above 30 <userinput>make</userinput> command will tell you how to create the device node, depending on your Linux 31 system. The procedure is slightly different for a classical Linux setup with a <filepath>/dev</filepath> 32 directory, a system with the now deprecated <userinput>devfs</userinput> and a modern Linux system with 33 <userinput>udev</userinput>. </p> 34 <p>On certain Linux distributions, you might experience difficulties building the module. You will have to analyze 35 the error messages from the build system to diagnose the cause of the problems. In general, make sure that 36 the correct Linux kernel sources are used for the build process. </p> 37 <p>Note that the <filepath>/dev/vboxdrv</filepath> kernel module device node must be owned by root:root and must be 38 read/writable only for the user. </p> 39 <p>Next, you install the system initialization script for the kernel module and activate the initialization script 40 using the right method for your distribution, as follows: </p> 69 41 <pre xml:space="preserve">cp /opt/VirtualBox/vboxdrv.sh /sbin/rcvboxdrv</pre> 70 <p> 71 This example assumes you installed <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to the 72 <filepath>/opt/VirtualBox</filepath> directory. 73 </p> 74 <p> 75 Create a configuration file for <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, as follows: 76 </p> 42 <p>This example assumes you installed <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to the 43 <filepath>/opt/VirtualBox</filepath> directory. </p> 44 <p>Create a configuration file for <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, as follows: </p> 77 45 <pre xml:space="preserve">mkdir /etc/vbox 78 46 echo INSTALL_DIR=/opt/VirtualBox > /etc/vbox/vbox.cfg</pre> 79 <p> 80 Create the following symbolic links: 81 </p> 47 <p>Create the following symbolic links: </p> 82 48 <pre xml:space="preserve">ln -sf /opt/VirtualBox/VBox.sh /usr/bin/VirtualBox 83 49 ln -sf /opt/VirtualBox/VBox.sh /usr/bin/VBoxManage
Note:
See TracChangeset
for help on using the changeset viewer.
