Changeset 64216 in vbox
- Timestamp:
- Oct 12, 2016 6:46:04 AM (8 years ago)
- svn:sync-xref-src-repo-rev:
- 111215
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_Installation.xml
r64214 r64216 360 360 very tightly into the system. To do this it installs a "driver" 361 361 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 363 365 VirtualBox manager to configure virtual machines, but they will not 364 366 start. It also installs network drivers called 365 367 <computeroutput>vboxnetflt</computeroutput> and 366 368 <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 building371 external kernel modules.</para>372 373 <para>Most Linux distributions can be set up simply by installing374 the right packages - normally, these will be the GNU compiler369 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 375 377 (GCC), GNU Make (make) and packages containing "header files" for 376 378 your kernel - and making sure that all system updates are
Note:
See TracChangeset
for help on using the changeset viewer.