VirtualBox

Changeset 64216 in vbox


Ignore:
Timestamp:
Oct 12, 2016 6:46:04 AM (8 years ago)
Author:
vboxsync
svn:sync-xref-src-repo-rev:
111215
Message:

8530: Documentation: improve automated instructions for building kernel modules: further refine the description of how to build kernel modules in the manual, and add back some information about networking which was removed in the last change: the user should not be told unnecessary details, but some details are useful to know.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/manual/en_US/user_Installation.xml

    r64214 r64216  
    360360      very tightly into the system.  To do this it installs a "driver"
    361361      module called <computeroutput>vboxdrv</computeroutput> which does
    362       a lot of the work. Without this kernel module, you can still use the
     362      a lot of that work into the system kernel, which is the part of
     363      the operating system which controls your processor and physical
     364      hardware. Without this kernel module, you can still use the
    363365      VirtualBox manager to configure virtual machines, but they will not
    364366      start. It also installs network drivers called
    365367      <computeroutput>vboxnetflt</computeroutput> and
    366368      <computeroutput>vboxnetadp</computeroutput> which let virtual machines
    367       make more use of your computer's network capabilities.</para>
    368 
    369       <para>The modules will be built automatically during installation or
    370       after kernel updates if your Linux system is prepared for building
    371       external kernel modules.</para>
    372 
    373       <para>Most Linux distributions can be set up simply by installing
    374       the right packages - normally, these will be the GNU compiler
     369      make more use of your computer's network capabilities and are needed
     370      for any virtual machine networking beyond the basic "NAT" mode.</para>
     371
     372      <para>Since distributing driver modules separately from the kernel
     373      is not something which Linux supports well, we create the modules
     374      on the system where they will be used.  This usually means first
     375      installing software packages from the distribution which are needed
     376      for the "build" process.  Normally, these will be the GNU compiler
    375377      (GCC), GNU Make (make) and packages containing "header files" for
    376378      your kernel - and making sure that all system updates are
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette