other:vb:update
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
other:vb:update [2016/01/20 13:12] jypeter Slight updates |
other:vb:update [2016/09/19 15:19] (current) jypeter [Updating Linux] Improved... |
||
|---|---|---|---|
| Line 76: | Line 76: | ||
| du -sh /var/cache/yum | du -sh /var/cache/yum | ||
| </code> | </code> | ||
| + | |||
| + | Recent machines (Fedora Core 22 and later) may use ''dnf'' instead of //yum//, and PackageKit. Use the following commands for cleaning the cache: | ||
| + | * **dnf** (/var/cache/dnf): ''dnf clean all'' | ||
| + | * **PackageKit** (/var/cache/PackageKit): ''pkcon refresh force'' | ||
| It's also a good thing to clean the //journal// (note: limiting the journal size probably has to be done only once) | It's also a good thing to clean the //journal// (note: limiting the journal size probably has to be done only once) | ||
| Line 91: | Line 95: | ||
| </code> | </code> | ||
| + | Note: **abrt** ([[http://abrt.readthedocs.io/en/latest/|Automated Bug Reporting Tool]]) may also leave some big directories in several places on the system (/var/cache/abrt, /var/spool/abrt-upload, /var/tmp/abrt, ...). The content of /var/tmp/abrt can be cleaned by deleting the reports in ''gnome-abrt''... | ||
| ==== Updating the Linux guest additions ==== | ==== Updating the Linux guest additions ==== | ||
| Line 110: | Line 115: | ||
| * In the VB window (the one where the guest is running), select //Devices->Insert Guest Additions CD Image...//. A //virtual// CD icon should appear on the desktop of the Linux guest | * In the VB window (the one where the guest is running), select //Devices->Insert Guest Additions CD Image...//. A //virtual// CD icon should appear on the desktop of the Linux guest | ||
| * Click on //Force unmount// in the popup Window, if a previous virtual CD is still present | * Click on //Force unmount// in the popup Window, if a previous virtual CD is still present | ||
| + | * Right-click on the CD icon and choose //Mount Volume// | ||
| * Click on //Cancel// if you get a popup window displaying //This medium contains software intended to be automatically started. Would you like to run it?// | * Click on //Cancel// if you get a popup window displaying //This medium contains software intended to be automatically started. Would you like to run it?// | ||
| * Become root in a window: ''sudo su -'' | * Become root in a window: ''sudo su -'' | ||
| Line 135: | Line 141: | ||
| If you want some details about how the graphics are handled by the current installation of you VB (i.e. **is your VM using the graphics card of the Windows host** or is it running is it use the sloooow software mode?), you can use the following commands | If you want some details about how the graphics are handled by the current installation of you VB (i.e. **is your VM using the graphics card of the Windows host** or is it running is it use the sloooow software mode?), you can use the following commands | ||
| - | * **glxgears**: if things work correctly, you will get a window with smoothly rotating gears (you can make the window fullscreen and check that it is still working) and the terminal will display some frames per second statistics | + | * ''modinfo vboxvideo'' will give you some information about the video driver provided by VB. Theoretically, //vboxvideo// should also appear when you type ''lsmod'' |
| + | * ''glxgears'': if things work correctly, you will get a window with smoothly rotating gears (you can make the window fullscreen and check that it is still working) and the terminal will display some frames per second statistics | ||
| * You may get some warning and error messages, but you should be good if the gears are rotating smoothly | * You may get some warning and error messages, but you should be good if the gears are rotating smoothly | ||
| - | * You can run the //glxinfo// command and you should see a reference to your graphics card if the video is indeed using it\\ **glxinfo | \grep -i opengl**\\ OpenGL vendor string: Humper\\ OpenGL renderer string: Chromium \\ OpenGL version string: 2.1 Chromium 1.9\\ **NVIDIA card =>** OpenGL shading language version string: 4.40 **NVIDIA** via Cg compiler\\ **Intel HD Graphics xxxx card =>** OpenGL shading language version string: 4.00 - **Build 10.18.10.3993**\\ OpenGL extensions: | + | * You can run the //glxinfo// command and you should see a reference to your graphics card if the video is indeed using it\\ ''glxinfo | \grep -i opengl''\\ OpenGL vendor string: Humper\\ OpenGL renderer string: Chromium \\ OpenGL version string: 2.1 Chromium 1.9\\ **NVIDIA card =>** OpenGL shading language version string: 4.40 **NVIDIA** via Cg compiler\\ **Intel HD Graphics xxxx card =>** OpenGL shading language version string: 4.00 - **Build 10.18.10.3993**\\ OpenGL extensions: |
| - | * You can get some additional information (including the screen resolution) with the //xdpyinfo//\\ **xdpyinfo | less** | + | * You can get some additional information (including the screen resolution) with the //xdpyinfo//\\ ''xdpyinfo | less'' |
other/vb/update.1453295570.txt.gz · Last modified: 2016/01/20 13:12 by jypeter
