Changeset 38021 in vbox for trunk/doc/manual/en_US
- Timestamp:
- Jul 18, 2011 2:17:42 PM (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_Installation.xml
r36005 r38021 273 273 allocation and to gain control of the processor for guest system 274 274 execution. Without this kernel module, you can still use the VirtualBox 275 manager to configure virtual machines, but they will not start. In addition, 276 there are the network kernel modules <computeroutput>vboxnetflt</computeroutput> 277 and <computeroutput>vboxnetadp</computeroutput> which are required for 278 the more advanced networking features of VirtualBox.</para> 275 manager to configure virtual machines, but they will not start. In 276 addition, there are the network kernel modules 277 <computeroutput>vboxnetflt</computeroutput> and 278 <computeroutput>vboxnetadp</computeroutput> which are required for the 279 more advanced networking features of VirtualBox.</para> 279 280 280 281 <para>The VirtualBox kernel module is automatically installed on your … … 359 360 <para>If you have built your own kernel, you will need to make 360 361 sure that you also installed all the required header and other 361 files for building external modules to the right locations. The362 details of how to do this will depend on how you built your363 kernel, and if you are unsure you should consult the documentation364 which you followed to do so.</para>362 files for building external modules to the right locations. 363 The details of how to do this will depend on how you built 364 your kernel, and if you are unsure you should consult the 365 documentation which you followed to do so.</para> 365 366 </listitem> 366 367 </itemizedlist> … … 438 439 (<computeroutput>vboxdrv</computeroutput>, 439 440 <computeroutput>vboxnetflt</computeroutput> and 440 <computeroutput>vboxnetadp</computeroutput>) and installs them.</para> 441 <computeroutput>vboxnetadp</computeroutput>) and installs 442 them.</para> 441 443 </listitem> 442 444 … … 454 456 <listitem> 455 457 <para>It creates symbolic links in 456 <computeroutput>/usr/bin</computeroutput> to 457 the a shell script (<computeroutput>/opt/VirtualBox/VBox</computeroutput>) 458 which does some sanity checks and 459 dispatches to the actual executables, 458 <computeroutput>/usr/bin</computeroutput> to the a shell script 459 (<computeroutput>/opt/VirtualBox/VBox</computeroutput>) which does 460 some sanity checks and dispatches to the actual executables, 460 461 <computeroutput>VirtualBox</computeroutput>, 461 462 <computeroutput>VBoxSDL</computeroutput>, … … 467 468 <listitem> 468 469 <para>It creates 469 <computeroutput>/etc/udev/rules.d/10-vboxdrv.rules</computeroutput>, a470 description file for udev, if that is present, which makes the470 <computeroutput>/etc/udev/rules.d/10-vboxdrv.rules</computeroutput>, 471 a description file for udev, if that is present, which makes the 471 472 USB devices accessible to all users in the 472 473 <computeroutput>vboxusers</computeroutput> group.</para> … … 481 482 <para>The installer must be executed as root with either 482 483 <computeroutput>install</computeroutput> or 483 <computeroutput>uninstall</computeroutput> as the first parameter.</para> 484 <computeroutput>uninstall</computeroutput> as the first 485 parameter.</para> 484 486 485 487 <screen>sudo ./VirtualBox.run install</screen> … … 507 509 <computeroutput>usermod -G group1,group2,vboxusers 508 510 username</computeroutput>.</para> 509 </note></para>511 </note></para> 510 512 </sect3> 511 513 … … 630 632 <para>To configure the installation process of our .deb and .rpm 631 633 packages, you can create a response file named 632 <computeroutput>/etc/default/virtualbox</computeroutput>. 633 The automatic generation of the udev rule can be634 prevented by the following setting: <screen>INSTALL_NO_UDEV=1</screen>635 The creation ofthe group vboxusers can be prevented by <screen>INSTALL_NO_GROUP=1</screen>634 <computeroutput>/etc/default/virtualbox</computeroutput>. The 635 automatic generation of the udev rule can be prevented by the 636 following setting: <screen>INSTALL_NO_UDEV=1</screen> The creation of 637 the group vboxusers can be prevented by <screen>INSTALL_NO_GROUP=1</screen> 636 638 If the line <screen>INSTALL_NO_VBOXDRV=1</screen> is specified, the 637 639 package installer will not try to build the … … 646 648 <para>The Linux installers create the system user group 647 649 <computeroutput>vboxusers</computeroutput> during installation. Any 648 system user who is going to use USB devices from VirtualBox guests 649 must be member of that group. 650 A user can be made member of the group 650 system user who is going to use USB devices from VirtualBox guests must 651 be member of that group. A user can be made member of the group 651 652 <computeroutput>vboxusers</computeroutput> through the GUI user/group 652 653 management or at the command line with</para> … … 752 753 753 754 <sect2> 755 <title>The vboxuser group</title> 756 757 <para>Starting with VirtualBox 4.1, the installer creates the system 758 user group <computeroutput>vboxuser</computeroutput> during installation 759 for Solaris hosts that support the required USB features for VirtualBox. 760 Any system user who is going to use USB devices from VirtualBox guests 761 must be a member of that group. A user can be made a member of this 762 group through the GUI user/group management or at the command line by 763 executing as root:</para> 764 765 <screen>usermod -G vboxuser username</screen> 766 767 <para>Adding an active user to the group will require that user to log 768 out and back in again. This must be done manually after installing 769 VirtualBox.</para> 770 </sect2> 771 772 <sect2> 754 773 <title>Starting VirtualBox on Solaris</title> 755 774
Note:
See TracChangeset
for help on using the changeset viewer.