https://wiki.archlinux.org/api.php?action=feedcontributions&user=Dax&feedformat=atomArchWiki - User contributions [en]2024-03-29T10:26:06ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Unofficial_user_repositories&diff=105893Unofficial user repositories2010-05-07T09:32:12Z<p>Dax: /* x86-64 */</p>
<hr />
<div>[[Category: Package management (English)]]<br />
== Why unofficial user repositories ==<br />
Since the AUR only allows users to upload PKGBUILD and other package build related files, but does not provide a means for distributing a binary package, a user may want to create a binary repository of their packages elsewhere.<br />
<br />
== The future of Unofficial repos ==<br />
I'd like to see more work of this type. Sometimes there are certain projects that don't mesh well with other things, such as the community repo. The 'kdemod' project is a good example. If you want to contribute with your own builds, you can check page [[Custom local repository]].<br />
<br />
In the future, well-thought-out user repositories may be ideal for lots of supplementary things. Forming a "web of trust" is important in cases like this, so we may begin keeping a list of "recommended" repositories somewhere, in order to make it seem more official and trustworthy.<br />
<br />
[[User:Phrakture|Phrakture]] 12:50, 18 May 2007 (EDT)<br />
<br />
== The community repository, maintained by the TUs==<br />
The community repository is included in pacman's default configuration.<br />
<br />
[community]<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
== List of PUR (unofficial user repositories) ==<br />
===Any===<br />
"Any" repos are architecture-independent, i.e. they can be used on both i686 and x86_64 systems.<br />
<nowiki><br />
[xyne-any]<br />
# The home of Powerpill and Xyne's other contributions.<br />
# More info including a package list can be found at http://xyne.archlinux.ca/repos<br />
Server = http://xyne.archlinux.ca/repos/xyne-any/<br />
<br />
[ninerepo-any]<br />
#perl packages, include Moose and Catalyst from pacpan (PKGBUILD's diff'd <br />
#against AUR/offical repos, if available).<br />
Server = http://icenine.sdf1.org/repo/ninerepo-any<br />
<br />
[herecura-stable-any]<br />
# just some stuff, few java apps, wallpapers, small scripts, xbmc-skin<br />
Server = http://herecura.be/repo/herecura-stable/any<br />
<br />
[herecura-testing-any]<br />
# some any testing stuff, xbmc-svn skin<br />
Server = http://herecura.be/repo/herecura-testing/any<br />
</nowiki><br />
<br />
===i686===<br />
<nowiki><br />
[unarch]<br />
# it offers support mainly against devel packages<br />
# contains stable packages that aren't in official repo<br />
Server = http://us4all.info/unarch/arch/i686<br />
<br />
[adslgr32]<br />
#The Hellenic (Greek) archlinux unofficial repository with many interesting packages.<br />
Server = http://adslgr32.tiven.org/archlinux/i686<br />
<br />
[kde4-eyecandy-32]<br />
#Useful and beautiful plasmoids and themes for KDE4<br />
Server = http://adslgr32.tiven.org/kde4-eyecandy-32<br />
<br />
[compiz-fusion-git]<br />
Server = http://adslgr32.tiven.org/compiz-fusion/git<br />
<br />
[andrwe]<br />
# for a list of packages see: http://andrwe.dyndns.org/doku.php/blog/repository<br />
Server = http://andrwe.dyndns.org/repo/i686<br />
<br />
[alsvartr]<br />
# just a small repo for a few programs in [unsupported]<br />
# (at this time - qutIM Instant Messenger and xneur/gxneur packages)<br />
Server = http://www.rootshell.be/~alsvartr/i686/<br />
<br />
[archaudio-stable]<br />
# and/or *-testing, *-experimental<br />
# Pro-audio repo:<br />
# - http://archaudio.org<br />
# replace "stable" with repo type (testing/experimental)<br />
Server = http://repos.archaudio.org/stable/i686<br />
<br />
[archlinux-es]<br />
# Repositorio Hispano (Spanish/Hispanic Respository)<br />
Server = http://repo.archlinux-es.org/i686<br />
<br />
[archlinuxfr]<br />
## The french Arch Linux communities packages<br />
Server = http://repo.archlinux.fr/i686<br />
<br />
[archlinuxve]<br />
# Home of the splashy packages<br />
Server = http://repo.archlinux.com.ve/i686<br />
<br />
[archrepo]<br />
#Mixed packages, suited for our and <br />
#our friends (You can be one of them!) needs<br />
#more info http://archrepo.net<br />
Server = http://archrepo.net/i686<br />
<br />
[archstuff]<br />
# AUR's most voted packages<br />
Server = http://archstuff.vs169092.vserver.de/i686<br />
<br />
[arch-games]<br />
# The Arch Linux Gaming repository project<br />
Server = http://arch.twilightlair.net/games/i686<br />
Server = http://pseudoform.org/arch-games/games/i686<br />
<br />
[arch-graphics]<br />
# repository aimed to provide applications mainly for 3D graphics<br />
# for more info, look at http://arch-graphics.kx.cz/<br />
Server = http://arch-graphics.kx.cz/repo/i686<br />
<br />
[awesome]<br />
#awesome3<br />
Server = http://www.camazotz.de/awesome/ <br />
<br />
[blaster]<br />
# Bl@ster maintains a repo with some interesting packages from the AUR, for all the purpouses<br />
Server = http://ilportalinux.it/arch_repo/i686<br />
<br />
[blind]<br />
# Chris Brannon maintains a small repo of packages from the AUR. All are<br />
# command-line utilities that Chris and friends find useful.<br />
Server = http://the-brannons.com/blind/i686<br />
<br />
# Crapkit,dbus,hal,etc stripped packages compatible with archlinux (from http://hereticlinux.org/)<br />
[cake]<br />
Server = http://hereticlinux.org/repo/cake/i686/ <br />
<br />
[cgr-i686]<br />
# packages for some ChicoGeek's PKGBUILDs<br />
Server = http://cgr.i686.googlepages.com/<br />
<br />
[chaox-stable]<br />
# pentesting packages and custom kernel patched for wifi injection<br />
Server = http://repo.chaox.net/stable<br />
<br />
[compiz-fusion]<br />
#compiz-fusion-git<br />
Server = http://compiz.dreamz-box.de/i686<br />
<br />
[cinan]<br />
#contains packages which aren't in official repos<br />
#info at cinan.tk or cinan6.tk<br />
Server = http://cinan.yw.sk/i686<br />
<br />
[dragonlord]<br />
# Mixed packages, I don't want to move into [community],<br />
# but are worth having them or the build time is long.<br />
Server = http://repo.dragonlord.cz/arch/i686<br />
<br />
[englab]<br />
# Packages of englab (mathematical programs), its toolboxes and dependencies<br />
Server = http://englab.bugfest.net/arch/i686<br />
<br />
[esclinux]<br />
# Mostly games, interactive fiction and abc notation stuffs already on AUR<br />
Server = http://download.tuxfamily.org/esclinuxcd/ressources/repo/i686/<br />
<br />
[gimpstudio]<br />
# Gimp Studio (http://codaset.com/foxbunny/gimp-studio) and support packages<br />
Server = "http://gimpstudio.brankovukelic.com/i686"<br />
<br />
[pozitpoh]<br />
Server = http://pozitpoh.is-a-geek.org:8080/repo/i686<br />
<br />
[fukawi]<br />
# Some Nagios Stuff; molly-guard; celtx and various networking tools.<br />
Server = http://repo.fukawi2.nl/i686/<br />
Server = ftp://repo.fukawi2.nl/i686/<br />
<br />
[kdemod-core]<br />
# Provides core KDE 4.x packages.<br />
# Requires Arch community repository which provides additional packages.<br />
Server = http://chakra-project.org/repo/core/i686<br />
Server = http://kdemod.iskrembilen.com/core/i686<br />
Server = http://archlinux.puzzle.ch/kdemod/core/i686<br />
Server = ftp://ftp.wh-stuttgart.net/kdemod/core/i686<br />
<br />
[kdemod-extragear]<br />
# Provides additional KDE 4.x packages.<br />
Server = http://chakra-project.org/repo/extragear/i686<br />
Server = http://kdemod.iskrembilen.com/extragear/i686<br />
Server = http://archlinux.puzzle.ch/kdemod/extragear/i686<br />
Server = ftp://ftp.wh-stuttgart.net/kdemod/extragear/i686<br />
<br />
[kdemod-playground]<br />
# Provides unstable packages for testing purposes.<br />
Server = http://chakra-project.org/repo/playground/i686<br />
Server = http://kdemod.iskrembilen.com/playground/i686<br />
Server = http://archlinux.puzzle.ch/kdemod/playground/i686<br />
Server = ftp://ftp.wh-stuttgart.net/kdemod/playground/i686<br />
<br />
[kdemod-legacy]<br />
# Provides KDE 3.5.x packages. <br />
# Requires Arch community repository which provides additional packages.<br />
Server = http://chakra-project.org/repo/legacy/i686<br />
<br />
[kpiche]<br />
# Stable OpenSync packages.<br />
Server = http://kpiche.archlinux.ca/repo<br />
<br />
[rfad]<br />
# Repository made by haxit | Contact at: requiem [at] archlinux.us for package suggestions!<br />
Server = http://web.ncf.ca/ey723/archlinux/repo/<br />
<br />
[sergej-repo]<br />
# ion3 and some other stuff<br />
# http://code.google.com/p/archlinux-stuff/source/browse/trunk/my-repo<br />
Server = http://arch.pp.ru/sergej-repo/i686/<br />
<br />
[skipper13]<br />
# java and ham-radio related and some other stuff<br />
Server = http://skipper13.root.ua/packages/i686/<br />
<br />
[zen-eee]<br />
# Zen-sources kernel for Asus Eee PC 901<br />
Server = http://robertek.brevnov.net/files/linux/arch<br />
<br />
[dstr-repo]<br />
#qutim, psi, kdevelop with plugins dev builds and other stuff<br />
Server = http://dimon.homeftp.org/repo/i686<br />
<br />
[xdemon-repo]<br />
#madwimax, kismet-svn and aircrack-svn, et cetera...<br />
Server=http://repo.x-demon.org/archlinux/os/i686<br />
<br />
[nightly]<br />
#nightly builds of some packages from the AUR<br />
# Repo-Tracker: http://tracker.kromonos.net/projects/show/nightlyarch<br />
Server = http://nightly.uhuc.de/i686<br />
<br />
[pozitpoh]<br />
# Fresh psi-plus, kvirc4, urtconnector, etc. More info at http://pozitpoh.is-a-geek.org:8080/wiki/index.php?title=ArchLinux_Repo_en<br />
Server = http://pozitpoh.is-a-geek.org:8080/repo/i686<br />
<br />
[seiichiro]<br />
# VDR and some plugins, mms, foo2zjs-drivers<br />
Server = http://seiichiro.homelinux.org/repo/i686<br />
<br />
[herecura-stable]<br />
# additional apps not found in community<br />
Server = http://herecura.be/repo/herecura-stable/i686<br />
<br />
[herecura-testing]<br />
# additional apps for testing build against stable arch<br />
Server = http://herecura.be/repo/herecura-testing/i686<br />
</nowiki><br />
<br />
===x86-64===<br />
<nowiki><br />
[unarch]<br />
# it offers support mainly against devel packages<br />
# contains stable packages that aren't in official repo<br />
Server = http://us4all.info/unarch/arch/x86_64<br />
<br />
[adslgr64]<br />
#The Hellenic (Greek) archlinux unofficial repository with many interesting packages.<br />
Server = http://adslgr64.tiven.org/archlinux/x86_64<br />
<br />
[kde4-eyecandy-64]<br />
#Useful and beautiful plasmoids and themes for KDE4<br />
Server = http://adslgr64.tiven.org/kde4-eyecandy-64<br />
<br />
[andrwe]<br />
# for a list of packages see: http://andrwe.dyndns.org/doku.php/blog/repository<br />
Server = http://andrwe.dyndns.org/repo/x86_64<br />
<br />
[archaudio-stable] # and/or *-testing, *-experimental<br />
# Pro-audio repo:<br />
# - http://archaudio.org<br />
# replace "stable" with repo type (testing/experimental)<br />
Server = http://repos.archaudio.org/stable/x86_64<br />
<br />
[archlinux-es]<br />
# Repositorio Hispano (Spanish/Hispanic Respository)<br />
Server = http://repo.archlinux-es.org/x86_64-<br />
<br />
[archlinuxfr]<br />
## The french Archlinux communities packages<br />
Server = http://repo.archlinux.fr/x86_64<br />
<br />
[archlinuxve]<br />
# Home of the splashy packages<br />
Server = http://repo.archlinux.com.ve/x86_64<br />
<br />
[archrepo]<br />
#Mixed packages, suited for our and <br />
#our friends (You can be one of them!) needs<br />
#more info http://archrepo.net <br />
Server = http://archrepo.net/x86_64<br />
<br />
[archstuff]<br />
# AUR's most voted and many bin32-* and lib32-* packages<br />
Server = http://archstuff.vs169092.vserver.de/x86_64<br />
<br />
[arch-games]<br />
# The Arch Linux Gaming repository project<br />
Server = http://arch.twilightlair.net/games/x86_64<br />
Server = http://pseudoform.org/arch-games/games/x86_64<br />
<br />
# Crapkit,dbus,hal,etc stripped packages compatible with archlinux (from http://hereticlinux.org/)<br />
[cake]<br />
Server = http://hereticlinux.org/repo/cake/x86_64/ <br />
<br />
[compiz-fusion]<br />
#compiz-fusion-git<br />
Server = http://compiz.dreamz-box.de/x86_64<br />
<br />
[cinan]<br />
#contains packages which aren't in official repos<br />
#info at cinan.tk or cinan6.tk<br />
Server = http://cinan.yw.sk/x86_64<br />
<br />
[englab]<br />
# Packages of englab (mathematical programs), its toolboxes and dependencies<br />
Server = http://englab.bugfest.net/arch/x86_64<br />
<br />
[fukawi]<br />
# Some Nagios Stuff; celtx; various other tools.<br />
Server = http://repo.fukawi2.nl/x86_64/<br />
Server = ftp://repo.fukawi2.nl/x86_64/<br />
<br />
[haskell]<br />
# Complete Haskell libraries and tools suite, snapshot of hackage.haskell.org<br />
Server = http://code.haskell.org/arch/x86_64<br />
<br />
[kdemod-core]<br />
# Provides core KDE 4.x packages.<br />
# Requires Arch community repository which provides additional packages.<br />
Server = http://chakra-project.org/repo/core/x86_64<br />
Server = http://kdemod.iskrembilen.com/core/x86_64<br />
Server = http://archlinux.puzzle.ch/kdemod/core/x86_64<br />
Server = ftp://ftp.wh-stuttgart.net/kdemod/core/x86_64<br />
<br />
[kdemod-extragear]<br />
# Provides additional KDE 4.x packages.<br />
Server = http://chakra-project.org/repo/extragear/x86_64<br />
Server = http://kdemod.iskrembilen.com/extragear/x86_64<br />
Server = http://archlinux.puzzle.ch/kdemod/extragear/x86_64<br />
Server = ftp://ftp.wh-stuttgart.net/kdemod/extragear/x86_64<br />
<br />
[kdemod-playground]<br />
# Provides unstable packages for testing purposes.<br />
Server = http://chakra-project.org/repo/playground/x86_64<br />
Server = http://kdemod.iskrembilen.com/playground/x86_64<br />
Server = http://archlinux.puzzle.ch/kdemod/playground/x86_64<br />
Server = ftp://ftp.wh-stuttgart.net/kdemod/playground/x86_64<br />
<br />
[kdemod-legacy]<br />
# Provides KDE 3.5.x packages. <br />
# Requires Arch community repository which provides additional packages.<br />
Server = http://chakra-project.org/repo/legacy/x86_64<br />
<br />
[sergej-repo]<br />
# ion3 and some other stuff<br />
# http://code.google.com/p/archlinux-stuff/source/browse/trunk/my-repo<br />
Server = http://arch.pp.ru/sergej-repo/x86_64/<br />
<br />
[dstr-repo]<br />
#qutim, psi, kdevelop with plugins dev builds and other stuff<br />
Server = http://dimon.homeftp.org/repo/x86_64<br />
<br />
[nightly]<br />
#nightly builds of some packages from the AUR<br />
# Repo-Tracker: http://tracker.kromonos.net/projects/show/nightlyarch<br />
Server = http://nightly.uhuc.de/x86_64<br />
<br />
[vbox]<br />
#virtualbox-ose for x86_64<br />
Server = http://archlinux.ro/~ioni/vbox<br />
<br />
[zen]<br />
#Various and zengeist' AUR packages<br />
Server = http://zloduch.cz/archlinux/x86_64<br />
<br />
[digitalpioneer]<br />
#Recent GIT/SVN/whatever builds of selected AUR packages<br />
#x86_64 only<br />
Server = http://dl.getdropbox.com/u/453116/repo<br />
<br />
[seiichiro]<br />
# VDR and some plugins, mms, foo2zjs-drivers<br />
Server = http://seiichiro.homelinux.org/repo/x86_64<br />
<br />
[herecura-stable]<br />
# additional apps not found in community<br />
Server = http://herecura.be/repo/herecura-stable/x86_64<br />
<br />
[herecura-testing]<br />
# additional apps for testing build against stable arch<br />
Server = http://herecura.be/repo/herecura-testing/x86_64<br />
</nowiki><br />
<br />
== Add your own repository to this list ==<br />
If you have your own repository, please add this to this list, so that all other users knows where to find your packages.</div>Daxhttps://wiki.archlinux.org/index.php?title=Unofficial_user_repositories&diff=105892Unofficial user repositories2010-05-07T09:31:24Z<p>Dax: /* i686 */</p>
<hr />
<div>[[Category: Package management (English)]]<br />
== Why unofficial user repositories ==<br />
Since the AUR only allows users to upload PKGBUILD and other package build related files, but does not provide a means for distributing a binary package, a user may want to create a binary repository of their packages elsewhere.<br />
<br />
== The future of Unofficial repos ==<br />
I'd like to see more work of this type. Sometimes there are certain projects that don't mesh well with other things, such as the community repo. The 'kdemod' project is a good example. If you want to contribute with your own builds, you can check page [[Custom local repository]].<br />
<br />
In the future, well-thought-out user repositories may be ideal for lots of supplementary things. Forming a "web of trust" is important in cases like this, so we may begin keeping a list of "recommended" repositories somewhere, in order to make it seem more official and trustworthy.<br />
<br />
[[User:Phrakture|Phrakture]] 12:50, 18 May 2007 (EDT)<br />
<br />
== The community repository, maintained by the TUs==<br />
The community repository is included in pacman's default configuration.<br />
<br />
[community]<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
== List of PUR (unofficial user repositories) ==<br />
===Any===<br />
"Any" repos are architecture-independent, i.e. they can be used on both i686 and x86_64 systems.<br />
<nowiki><br />
[xyne-any]<br />
# The home of Powerpill and Xyne's other contributions.<br />
# More info including a package list can be found at http://xyne.archlinux.ca/repos<br />
Server = http://xyne.archlinux.ca/repos/xyne-any/<br />
<br />
[ninerepo-any]<br />
#perl packages, include Moose and Catalyst from pacpan (PKGBUILD's diff'd <br />
#against AUR/offical repos, if available).<br />
Server = http://icenine.sdf1.org/repo/ninerepo-any<br />
<br />
[herecura-stable-any]<br />
# just some stuff, few java apps, wallpapers, small scripts, xbmc-skin<br />
Server = http://herecura.be/repo/herecura-stable/any<br />
<br />
[herecura-testing-any]<br />
# some any testing stuff, xbmc-svn skin<br />
Server = http://herecura.be/repo/herecura-testing/any<br />
</nowiki><br />
<br />
===i686===<br />
<nowiki><br />
[unarch]<br />
# it offers support mainly against devel packages<br />
# contains stable packages that aren't in official repo<br />
Server = http://us4all.info/unarch/arch/i686<br />
<br />
[adslgr32]<br />
#The Hellenic (Greek) archlinux unofficial repository with many interesting packages.<br />
Server = http://adslgr32.tiven.org/archlinux/i686<br />
<br />
[kde4-eyecandy-32]<br />
#Useful and beautiful plasmoids and themes for KDE4<br />
Server = http://adslgr32.tiven.org/kde4-eyecandy-32<br />
<br />
[compiz-fusion-git]<br />
Server = http://adslgr32.tiven.org/compiz-fusion/git<br />
<br />
[andrwe]<br />
# for a list of packages see: http://andrwe.dyndns.org/doku.php/blog/repository<br />
Server = http://andrwe.dyndns.org/repo/i686<br />
<br />
[alsvartr]<br />
# just a small repo for a few programs in [unsupported]<br />
# (at this time - qutIM Instant Messenger and xneur/gxneur packages)<br />
Server = http://www.rootshell.be/~alsvartr/i686/<br />
<br />
[archaudio-stable]<br />
# and/or *-testing, *-experimental<br />
# Pro-audio repo:<br />
# - http://archaudio.org<br />
# replace "stable" with repo type (testing/experimental)<br />
Server = http://repos.archaudio.org/stable/i686<br />
<br />
[archlinux-es]<br />
# Repositorio Hispano (Spanish/Hispanic Respository)<br />
Server = http://repo.archlinux-es.org/i686<br />
<br />
[archlinuxfr]<br />
## The french Arch Linux communities packages<br />
Server = http://repo.archlinux.fr/i686<br />
<br />
[archlinuxve]<br />
# Home of the splashy packages<br />
Server = http://repo.archlinux.com.ve/i686<br />
<br />
[archrepo]<br />
#Mixed packages, suited for our and <br />
#our friends (You can be one of them!) needs<br />
#more info http://archrepo.net<br />
Server = http://archrepo.net/i686<br />
<br />
[archstuff]<br />
# AUR's most voted packages<br />
Server = http://archstuff.vs169092.vserver.de/i686<br />
<br />
[arch-games]<br />
# The Arch Linux Gaming repository project<br />
Server = http://arch.twilightlair.net/games/i686<br />
Server = http://pseudoform.org/arch-games/games/i686<br />
<br />
[arch-graphics]<br />
# repository aimed to provide applications mainly for 3D graphics<br />
# for more info, look at http://arch-graphics.kx.cz/<br />
Server = http://arch-graphics.kx.cz/repo/i686<br />
<br />
[awesome]<br />
#awesome3<br />
Server = http://www.camazotz.de/awesome/ <br />
<br />
[blaster]<br />
# Bl@ster maintains a repo with some interesting packages from the AUR, for all the purpouses<br />
Server = http://ilportalinux.it/arch_repo/i686<br />
<br />
[blind]<br />
# Chris Brannon maintains a small repo of packages from the AUR. All are<br />
# command-line utilities that Chris and friends find useful.<br />
Server = http://the-brannons.com/blind/i686<br />
<br />
# Crapkit,dbus,hal,etc stripped packages compatible with archlinux (from http://hereticlinux.org/)<br />
[cake]<br />
Server = http://hereticlinux.org/repo/cake/i686/ <br />
<br />
[cgr-i686]<br />
# packages for some ChicoGeek's PKGBUILDs<br />
Server = http://cgr.i686.googlepages.com/<br />
<br />
[chaox-stable]<br />
# pentesting packages and custom kernel patched for wifi injection<br />
Server = http://repo.chaox.net/stable<br />
<br />
[compiz-fusion]<br />
#compiz-fusion-git<br />
Server = http://compiz.dreamz-box.de/i686<br />
<br />
[cinan]<br />
#contains packages which aren't in official repos<br />
#info at cinan.tk or cinan6.tk<br />
Server = http://cinan.yw.sk/i686<br />
<br />
[dragonlord]<br />
# Mixed packages, I don't want to move into [community],<br />
# but are worth having them or the build time is long.<br />
Server = http://repo.dragonlord.cz/arch/i686<br />
<br />
[englab]<br />
# Packages of englab (mathematical programs), its toolboxes and dependencies<br />
Server = http://englab.bugfest.net/arch/i686<br />
<br />
[esclinux]<br />
# Mostly games, interactive fiction and abc notation stuffs already on AUR<br />
Server = http://download.tuxfamily.org/esclinuxcd/ressources/repo/i686/<br />
<br />
[gimpstudio]<br />
# Gimp Studio (http://codaset.com/foxbunny/gimp-studio) and support packages<br />
Server = "http://gimpstudio.brankovukelic.com/i686"<br />
<br />
[pozitpoh]<br />
Server = http://pozitpoh.is-a-geek.org:8080/repo/i686<br />
<br />
[fukawi]<br />
# Some Nagios Stuff; molly-guard; celtx and various networking tools.<br />
Server = http://repo.fukawi2.nl/i686/<br />
Server = ftp://repo.fukawi2.nl/i686/<br />
<br />
[kdemod-core]<br />
# Provides core KDE 4.x packages.<br />
# Requires Arch community repository which provides additional packages.<br />
Server = http://chakra-project.org/repo/core/i686<br />
Server = http://kdemod.iskrembilen.com/core/i686<br />
Server = http://archlinux.puzzle.ch/kdemod/core/i686<br />
Server = ftp://ftp.wh-stuttgart.net/kdemod/core/i686<br />
<br />
[kdemod-extragear]<br />
# Provides additional KDE 4.x packages.<br />
Server = http://chakra-project.org/repo/extragear/i686<br />
Server = http://kdemod.iskrembilen.com/extragear/i686<br />
Server = http://archlinux.puzzle.ch/kdemod/extragear/i686<br />
Server = ftp://ftp.wh-stuttgart.net/kdemod/extragear/i686<br />
<br />
[kdemod-playground]<br />
# Provides unstable packages for testing purposes.<br />
Server = http://chakra-project.org/repo/playground/i686<br />
Server = http://kdemod.iskrembilen.com/playground/i686<br />
Server = http://archlinux.puzzle.ch/kdemod/playground/i686<br />
Server = ftp://ftp.wh-stuttgart.net/kdemod/playground/i686<br />
<br />
[kdemod-legacy]<br />
# Provides KDE 3.5.x packages. <br />
# Requires Arch community repository which provides additional packages.<br />
Server = http://chakra-project.org/repo/legacy/i686<br />
<br />
[kpiche]<br />
# Stable OpenSync packages.<br />
Server = http://kpiche.archlinux.ca/repo<br />
<br />
[rfad]<br />
# Repository made by haxit | Contact at: requiem [at] archlinux.us for package suggestions!<br />
Server = http://web.ncf.ca/ey723/archlinux/repo/<br />
<br />
[sergej-repo]<br />
# ion3 and some other stuff<br />
# http://code.google.com/p/archlinux-stuff/source/browse/trunk/my-repo<br />
Server = http://arch.pp.ru/sergej-repo/i686/<br />
<br />
[skipper13]<br />
# java and ham-radio related and some other stuff<br />
Server = http://skipper13.root.ua/packages/i686/<br />
<br />
[zen-eee]<br />
# Zen-sources kernel for Asus Eee PC 901<br />
Server = http://robertek.brevnov.net/files/linux/arch<br />
<br />
[dstr-repo]<br />
#qutim, psi, kdevelop with plugins dev builds and other stuff<br />
Server = http://dimon.homeftp.org/repo/i686<br />
<br />
[xdemon-repo]<br />
#madwimax, kismet-svn and aircrack-svn, et cetera...<br />
Server=http://repo.x-demon.org/archlinux/os/i686<br />
<br />
[nightly]<br />
#nightly builds of some packages from the AUR<br />
# Repo-Tracker: http://tracker.kromonos.net/projects/show/nightlyarch<br />
Server = http://nightly.uhuc.de/i686<br />
<br />
[pozitpoh]<br />
# Fresh psi-plus, kvirc4, urtconnector, etc. More info at http://pozitpoh.is-a-geek.org:8080/wiki/index.php?title=ArchLinux_Repo_en<br />
Server = http://pozitpoh.is-a-geek.org:8080/repo/i686<br />
<br />
[seiichiro]<br />
# VDR and some plugins, mms, foo2zjs-drivers<br />
Server = http://seiichiro.homelinux.org/repo/i686<br />
<br />
[herecura-stable]<br />
# additional apps not found in community<br />
Server = http://herecura.be/repo/herecura-stable/i686<br />
<br />
[herecura-testing]<br />
# additional apps for testing build against stable arch<br />
Server = http://herecura.be/repo/herecura-testing/i686<br />
</nowiki><br />
<br />
===x86-64===<br />
<nowiki><br />
<br />
[adslgr64]<br />
#The Hellenic (Greek) archlinux unofficial repository with many interesting packages.<br />
Server = http://adslgr64.tiven.org/archlinux/x86_64<br />
<br />
[kde4-eyecandy-64]<br />
#Useful and beautiful plasmoids and themes for KDE4<br />
Server = http://adslgr64.tiven.org/kde4-eyecandy-64<br />
<br />
[andrwe]<br />
# for a list of packages see: http://andrwe.dyndns.org/doku.php/blog/repository<br />
Server = http://andrwe.dyndns.org/repo/x86_64<br />
<br />
[archaudio-stable] # and/or *-testing, *-experimental<br />
# Pro-audio repo:<br />
# - http://archaudio.org<br />
# replace "stable" with repo type (testing/experimental)<br />
Server = http://repos.archaudio.org/stable/x86_64<br />
<br />
[archlinux-es]<br />
# Repositorio Hispano (Spanish/Hispanic Respository)<br />
Server = http://repo.archlinux-es.org/x86_64-<br />
<br />
[archlinuxfr]<br />
## The french Archlinux communities packages<br />
Server = http://repo.archlinux.fr/x86_64<br />
<br />
[archlinuxve]<br />
# Home of the splashy packages<br />
Server = http://repo.archlinux.com.ve/x86_64<br />
<br />
[archrepo]<br />
#Mixed packages, suited for our and <br />
#our friends (You can be one of them!) needs<br />
#more info http://archrepo.net <br />
Server = http://archrepo.net/x86_64<br />
<br />
[archstuff]<br />
# AUR's most voted and many bin32-* and lib32-* packages<br />
Server = http://archstuff.vs169092.vserver.de/x86_64<br />
<br />
[arch-games]<br />
# The Arch Linux Gaming repository project<br />
Server = http://arch.twilightlair.net/games/x86_64<br />
Server = http://pseudoform.org/arch-games/games/x86_64<br />
<br />
# Crapkit,dbus,hal,etc stripped packages compatible with archlinux (from http://hereticlinux.org/)<br />
[cake]<br />
Server = http://hereticlinux.org/repo/cake/x86_64/ <br />
<br />
[compiz-fusion]<br />
#compiz-fusion-git<br />
Server = http://compiz.dreamz-box.de/x86_64<br />
<br />
[cinan]<br />
#contains packages which aren't in official repos<br />
#info at cinan.tk or cinan6.tk<br />
Server = http://cinan.yw.sk/x86_64<br />
<br />
[englab]<br />
# Packages of englab (mathematical programs), its toolboxes and dependencies<br />
Server = http://englab.bugfest.net/arch/x86_64<br />
<br />
[fukawi]<br />
# Some Nagios Stuff; celtx; various other tools.<br />
Server = http://repo.fukawi2.nl/x86_64/<br />
Server = ftp://repo.fukawi2.nl/x86_64/<br />
<br />
[haskell]<br />
# Complete Haskell libraries and tools suite, snapshot of hackage.haskell.org<br />
Server = http://code.haskell.org/arch/x86_64<br />
<br />
[kdemod-core]<br />
# Provides core KDE 4.x packages.<br />
# Requires Arch community repository which provides additional packages.<br />
Server = http://chakra-project.org/repo/core/x86_64<br />
Server = http://kdemod.iskrembilen.com/core/x86_64<br />
Server = http://archlinux.puzzle.ch/kdemod/core/x86_64<br />
Server = ftp://ftp.wh-stuttgart.net/kdemod/core/x86_64<br />
<br />
[kdemod-extragear]<br />
# Provides additional KDE 4.x packages.<br />
Server = http://chakra-project.org/repo/extragear/x86_64<br />
Server = http://kdemod.iskrembilen.com/extragear/x86_64<br />
Server = http://archlinux.puzzle.ch/kdemod/extragear/x86_64<br />
Server = ftp://ftp.wh-stuttgart.net/kdemod/extragear/x86_64<br />
<br />
[kdemod-playground]<br />
# Provides unstable packages for testing purposes.<br />
Server = http://chakra-project.org/repo/playground/x86_64<br />
Server = http://kdemod.iskrembilen.com/playground/x86_64<br />
Server = http://archlinux.puzzle.ch/kdemod/playground/x86_64<br />
Server = ftp://ftp.wh-stuttgart.net/kdemod/playground/x86_64<br />
<br />
[kdemod-legacy]<br />
# Provides KDE 3.5.x packages. <br />
# Requires Arch community repository which provides additional packages.<br />
Server = http://chakra-project.org/repo/legacy/x86_64<br />
<br />
[sergej-repo]<br />
# ion3 and some other stuff<br />
# http://code.google.com/p/archlinux-stuff/source/browse/trunk/my-repo<br />
Server = http://arch.pp.ru/sergej-repo/x86_64/<br />
<br />
[dstr-repo]<br />
#qutim, psi, kdevelop with plugins dev builds and other stuff<br />
Server = http://dimon.homeftp.org/repo/x86_64<br />
<br />
[nightly]<br />
#nightly builds of some packages from the AUR<br />
# Repo-Tracker: http://tracker.kromonos.net/projects/show/nightlyarch<br />
Server = http://nightly.uhuc.de/x86_64<br />
<br />
[vbox]<br />
#virtualbox-ose for x86_64<br />
Server = http://archlinux.ro/~ioni/vbox<br />
<br />
[zen]<br />
#Various and zengeist' AUR packages<br />
Server = http://zloduch.cz/archlinux/x86_64<br />
<br />
[digitalpioneer]<br />
#Recent GIT/SVN/whatever builds of selected AUR packages<br />
#x86_64 only<br />
Server = http://dl.getdropbox.com/u/453116/repo<br />
<br />
[seiichiro]<br />
# VDR and some plugins, mms, foo2zjs-drivers<br />
Server = http://seiichiro.homelinux.org/repo/x86_64<br />
<br />
[herecura-stable]<br />
# additional apps not found in community<br />
Server = http://herecura.be/repo/herecura-stable/x86_64<br />
<br />
[herecura-testing]<br />
# additional apps for testing build against stable arch<br />
Server = http://herecura.be/repo/herecura-testing/x86_64<br />
</nowiki><br />
<br />
== Add your own repository to this list ==<br />
If you have your own repository, please add this to this list, so that all other users knows where to find your packages.</div>Daxhttps://wiki.archlinux.org/index.php?title=VirtualBox&diff=68413VirtualBox2009-05-08T00:55:31Z<p>Dax: /* Windows Xp and Nokia phones */</p>
<hr />
<div>[[Category:Emulators (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|:VirtualBox}}<br />
{{i18n_entry|Italiano|:VirtualBox (Italiano)}}<br />
{{i18n_entry|简体中文|:VirtualBox (简体中文)}}<br />
{{i18n_entry|Русский|VirtualBox (Русский)}}<br />
{{i18n_entry|Español|VirtualBox (Español)}}<br />
{{i18n_entry|Português|VirtualBox (Português)}}<br />
{{i18n_links_end}}<br />
<br />
== What is VirtualBox ==<br />
[http://www.virtualbox.org VirtualBox] is a virtual pc emulator like vmware. It has many of the features vmware has, as well as some of its own. It is in constant development and new features are implemented all the time. eg. version 2.2 introduced OpenGL 3D acceleration support for Linux and Solaris guests. It has a nice GUI interface (Qt and/or SDL) or command line tools for managing virtual machines. Headless operation is also supported.<br />
<br />
=== Editions ===<br />
VirtualBox is available in two editions: VirtualBox (OSE) and VirtualBox (Personal Use and Evaluation License (PUEL))<br />
<br />
==== VirtualBox (OSE) ====<br />
VirtualBox (OSE) is the open source version of VirtualBox, which can be found in the community repository. It lacks some features such as USB device support and the built-in RDP server.<br />
<br />
==== VirtualBox (PUEL) ====<br />
VirtualBox PUEL is a binary-only version (free for personal use) which is available from the [http://aur.archlinux.org/packages.php?ID=9753 AUR] or directly from the <br />
[http://www.virtualbox.org/wiki/Downloads VirtualBox] website. The PUEL edition offers the following advantages:<br />
<br />
*'''Remote Display Protocol (RDP) Server''' - a complete RDP server on top of the virtual hardware, allowing users to connect to a virtual machine remotely using any RDP compatible client<br />
<br />
*'''USB support''' - a virtual USB controller which allows USB 1.1 and USB 2.0 devices to be passed through to virtual machines<br />
<br />
*'''USB over RDP''' - a combination of the RDP server and USB support, allowing users to make USB devices available to virtual machines running remotely<br />
<br />
*'''iSCSI initiator''' - a builtin iSCSI initiator making it possible to use iSCSI targets as virtual disks without the guest requiring support for iSCSI<br />
<br />
== Installation ==<br />
<br />
=== Install VirtualBox (OSE) ===<br />
<br />
VirtualBox (OSE) is available from the community repositories :<br />
<br />
# pacman -S virtualbox-ose<br />
<br />
'''Note:''' This package seems not to be in x86_64 Repositories. Version 2.0.4 does not build on x86_64. Version 2.1.0 should have better 64-bit support (to be confirmed).<br />
<br />
This will select by default <tt>virtualbox-ose</tt> and <tt>virtualbox-modules</tt> packages. Once installed, a desktop entry can be located in ''Applications > System Tools > VirtualBox OSE''<br />
<br />
Now, add the desired username to the '''vboxusers''' group:<br />
<br />
# gpasswd -a USERNAME vboxusers<br />
<br />
''('''Note:''' You must logout/login in order for this change to take effect)''<br />
<br />
Lastly, edit <tt>/etc/rc.conf</tt> as root and add '''vboxdrv''' to the MODULES array in order to load the VirtualBox drivers at startup. For example:<br />
<br />
MODULES=(loop '''vboxdrv''' fuse ...)<br />
<br />
To load the module manually, run the following in a terminal as root: <br />
<br />
# modprobe vboxdrv<br />
<br />
'''HowTo:'''<br><br />
[[VirtualBox-HowTo]]<br />
<br />
=== Install VirtualBox PUEL (virtualbox_bin) ===<br />
VirtualBox PUEL is available from the [http://aur.archlinux.org/packages.php?ID=9753 AUR: virtualbox_bin].<br />
<br />
Download the tarball from the [http://aur.archlinux.org/packages.php?ID=9753 AUR: virtualbox_bin] page, unpack, run <tt>makepkg</tt>, and then as root:<br />
<br />
# pacman -U PACKAGE-NAME.pkg.tar.gz<br />
<br />
'''However, there's an alternative way to install the virtualbox_bin package:'''<br />
<br />
Firstly, add as root the followings into /etc/pacman.conf:<br />
[archlinuxfr]<br />
Server = <nowiki>http://repo.archlinux.fr/i686</nowiki><br />
or<br />
[archlinuxfr]<br />
Server = <nowiki>http://repo.archlinux.fr/x86_64</nowiki><br />
depending on your CPU's architecture.<br />
<br />
Then you can install it successfully via:<br />
# pacman -Sy virtualbox_bin<br />
<br />
Now, add the desired username to the '''vboxusers''' group:<br />
# gpasswd -a USERNAME vboxusers<br />
<br />
''('''Note:''' You must logout/login in order for this change to take effect)''<br />
<br />
Lastly, edit <tt>/etc/rc.conf</tt> as root and add '''vboxdrv''' to the MODULES array in order to load the VirtualBox drivers at startup. For example:<br />
MODULES=(loop '''vboxdrv''' fuse ...)<br />
<br />
To load the module manually, run the following in a terminal as root: <br />
# modprobe vboxdrv<br />
<br />
=== Install required QT libraries ===<br />
Currently, VirtualBox relies on qt4 for its graphical interface. If you require a GUI, ensure you have qt4 installed:<br />
# pacman -S qt<br />
<br />
=== Start VirtualBox ===<br />
To start Virtualbox, run the following command in a terminal:<br />
$ VirtualBox<br />
<br />
=== Install VirtualBox 2.1 (another alternative) ===<br />
<br />
VirtualBox.run install can be done using the All Distributions package from the [http://www.virtualbox.org/wiki/Linux_Downloads Linux section] of the VirtualBox Website.<br />
<br />
Make sure the Qt 4.3.0 and SDL 1.2.7 or higher packages are installed:<br />
<br />
# pacman -Sy qt sdl <br />
<br />
Download the appropriate architecture file i386/AMD64. In a terminal window, browse to the download folder and as root run:<br />
<br />
# sh VirtualBox-2.XXXX-Linux_ARCH.run<br />
<br />
This will install the package to the /opt/VirtualBox-2.XXX folder.<br />
<br />
After installation, a desktop entry can be located in ''Applications > System Tools > Sun xVM VirtualBox''<br />
<br />
Now, add the desired username to the '''vboxusers''' group:<br />
# gpasswd -a USERNAME vboxusers<br />
<br />
Lastly, edit <tt>/etc/rc.conf</tt> as root and add '''vboxdrv''' to the MODULES array in order to load the VirtualBox drivers at startup.<br />
<br />
Start the VirtualBox GUI either with the command:<br />
<br />
# VirtualBox <br />
<br />
or using the ''Applications'' desktop entry. In version 2.1.x, an installation wizard should start and take you through the process of setting up a virtual machine. Otherwise, use the help menu to get started. '''Continue reading to see the more advanced options and setups....'''<br />
<br />
== Configuration ==<br />
After we have installed VirtualBox on our system and added ourselves in the vboxusers group we can start configuring our system in order to make all the features of VirtualBox available to us.Create a new virtual machine using the wizard provided by the GUI and then click settings in order to edit the virtual machine settings.<br />
<br />
=== Keyboard and mouse between the host and the guest ===<br />
To capture the keyboard and mouse, click the mouse inside the Virtual Machine display.<br><br />
To uncapture, "Ctrl-Alt Delete".<br />
<br />
If [[Xorg]] freezes mouse and keyboard you will have to disable the [[Xorg#Input_hotplugging_with_xorg-server_1.5| new hot plugging feature of Xorg 1.5]] by adding in /etc/X11/xorg.conf:<br />
<br />
Section "ServerLayout"<br />
. . .<br />
Option "AutoAddDevices" "False"<br />
. . .<br />
EndSection<br />
<br />
This is needed for Linux guests in a Mac OS X or Windows host. Also needed for Linux hosts (tested with Arch64 host and Arch64 guest).<br />
<br />
Also, mouse pointer integration doesn't work out of the box. To fix it, make sure you have the following sections in your xorg.conf:<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "vboxmouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
When generating your xorg.conf with "X -configure", you'll end up with an InputDevice section that uses the "mouse" driver. After installing the Guest Additions, you should replace "mouse" with "vboxmouse" and then restart X or reboot your VM.<br />
<br />
=== Getting network in the guest machine to work ===<br />
First let's get network working in the guest machine. Click the network tab. The not attached option means you'll have "Network cable unplugged" or similar error in the guest computer.<br />
<br />
==== Using NAT network ====<br />
This is the simplest way to get network. Select NAT network and it should be ready to use. Then, the guest operating system can be automatically configured by using DHCP.<br />
<br />
The NAT IP address on the first card is 10.0.2.0, 10.0.3.0 on the second and so on.<br />
<br />
==== Using host interface networking (the VirtualBox way) ====<br />
Since VirtuaBox 2.1.0 it has a native support for host interface networking. Just add '''vboxnetflt''' to your MODULES section in [[rc.conf]] and choose ''Host Interface Networking'' in the virtual machine configuration.<br />
<br />
==== Using host interface networking (the Arch way) ====<br />
You are going to just edit these files and reboot:<br />
<br />
* /etc/conf.d/bridges<br />
* /etc/rc.conf<br />
* /etc/vbox/interfaces<br />
<br />
Ready? Let's go!<br />
<br />
'''/etc/conf.d/bridges:'''<br />
bridge_br0="eth0 vbox0" # Put any interfaces you need.<br />
BRIDGE_INTERFACES=(br0)<br />
<br />
'''/etc/rc.conf:'''<br />
<br />
First add the bridge module to your MODULES line<br />
MODULES=( <your other modules> '''bridge''')<br />
<br />
Then, in your NETWORKING section, make the following changes:<br />
br0="dhcp" # Maybe you have some static configuration... I use DHCP.<br />
INTERFACES=(eth0 br0)<br />
<br />
'''Note''' by gpan:<br />
<br />
'''/etc/rc.conf:'''<br />
<br />
First add the vboxdrv (and [[vboxnetflt]] in case of 2.1.0 version) module to your MODULES line<br />
<br />
MODULES=( <your other modules> vboxdrv vboxnetflt )<br />
<br />
<br />
Next, you should edit your '''/etc/udev/rules.d/60-vboxdrv.rules''' and type:<br />
<br />
KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="vboxusers", MODE="0660"<br />
<br />
Save it and exit.<br />
<br />
Then open terminal and type:<br />
<br />
# pacman -S bridge-utils uml_utilities<br />
<br />
Create a new bridge with this command:<br />
<br />
# brctl addbr br0<br />
<br />
<br />
'''/etc/vbox/interfaces'''<br />
<br />
(You can set up more interfaces if you want. Sky is the limit!):<br />
vbox0 your_user br0 # Be sure that your user is in the vboxusers group.<br />
<br />
Reboot and enjoy!<br />
<br />
'''''Note:''' Remember to set up your virtual machine with proper network configuration.''<br />
<br />
'''''Note:''' If you have any issue, make sure that you have the bridge-utils package installed and vboxnet daemon loaded''<br />
<br />
==== Using host interface networking (generic) ====<br />
This way is a bit harder, but it allows you to see the VirtualMachine as a "real" computer on your local network. You need to get bridge-utils <br />
<br />
# pacman -S bridge-utils uml_utilities<br />
<br />
'''Note''' by Sp1d3rmxn:<br />
:You also need to have the TUN module loaded...in [[rc.conf]] add "tun" (without the :quotes) to your MODULES section. For testing this out right now without rebooting :you can load the module from the command line by "modprobe tun".<br />
:<br />
:Then you MUST set these permissions otherwise you'll never get VBox to init the :interface. The command is "<code>chmod 666 /dev/net/tun</code>" (without the quotes).<br />
<br />
:Now proceed with the rest as it's written below.<br />
<br />
'''Note''' by Dharivs<br />
:As said by Sp1d3rmxn, we must set these permissions, but, instead of using the <br />
:command, we can set them in /etc/udev/rules.d/60-vboxdrv.rules, which will set them <br />
:on boot:<br />
KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="vboxusers", MODE="0660"<br />
KERNEL=="tun", OWNER="root", GROUP="vboxusers", MODE="0660"<br />
<br />
<br />
<b>1.</b> Create a new bridge with this command:<br />
# brctl addbr br0<br />
<br />
<b>2.</b> If you are not using DHCP, run ifconfig and note down the network configuration of your existing network interface (e.g. eth0), which we will need to copy to the bridge in a minute.<br />
<br />
''('''Note: You will need this settings so make sure you don't lose them!!!''')''<br />
<br />
<b>3.</b> Switch your physical network adapter to "promiscuous" mode so that it will accept Ethernet frames for MAC addresses other than its own (replace eth0 with your network interface):<br />
# ifconfig eth0 0.0.0.0 promisc <br />
<br />
''('''Note:''' You will lose network connectivity on eth0 at this point.)''<br />
<br />
<b>4.</b> Add your network adapter to the bridge:<br />
# brctl addif br0 eth0<br />
<br />
<b>5.</b> Transfer the network configuration previously used with your physical ethernet adapter to the new bridge. If you are using DHCP, this should work:<br />
# dhclient br0<br />
<br />
'''Note''' by Sp1d3rmxn:<br />
:Use "dhcpcd -t 30 -h yourhostname br0 &" instead of the above<br />
<br />
Otherwise, run <code>ifconfig br0 x.x.x.x netmask x.x.x.x</code> and use the values that you noted down previously.<br />
<br />
<b>6.</b> To create a permanent host interface called vbox0 (all host interfaces created in this way must be called vbox followed by a number) and add it to the network bridge created above, use the following command:<br />
VBoxAddIF vbox0 vboxuser br0<br />
<br />
Replace vboxuser with the name of the user who is supposed to be able to use the new interface.<br />
<br />
('''Note:''' VboxAddIF is located in /opt/VirtualBox-VERSION OF VIRTUALBOX/VBoxAddIF)<br />
<br />
Alternatively, you can [http://mychael.gotdns.com/blog/2007/05/31/virtualbox-bridging/ setup VirtualBox networking] through your /etc/rc.conf to enable a bridged connection.<br />
<br />
==== Using host interface networking with a wireless device ====<br />
Bridging as described above won't work with a wireless device. Using [http://aur.archlinux.org/packages.php?ID=16356 parprouted] however it can be accomplished.<br />
<br />
# Install parprouted and iproute<br />
# <code># ln -s /usr/sbin/ip /sbin/ip</code><br />
# Make sure IP fowarding is enabled: <code># sysctl net.ipv4.ip_forward=1</code>, and/or edit /etc/sysctl.conf<br />
# <code># VBoxTunctl -b -u <user></code>, to create the tap device<br />
# <code># ip link set tap0 up; ip addr add 192.168.0.X/24 dev tap0</code>, needs to be a manually set IP on the same network your wireless device is.<br />
# <code># parprouted wlan0 tap0</code><br />
<br />
=== Getting USB to work in the guest machine ===<br />
(Only available in the PUEL edition)<br />
<br />
First in order to make usb available for use to the virtual machine you must add this line to your /etc/fstab<br />
none /proc/bus/usb usbfs auto,busgid=108,busmode=0775,devgid=108,devmode=0664 0 0<br />
<br />
108 is is the id of the group which should be allowed to access USB-devices. Change it to the id of your vboxusers group. You can get the id by running:<br />
$ grep vboxusers /etc/group<br />
<br />
If you don't mind a security hole change devmode from 664 to 666.<br />
<br />
Remount /proc/bus/usb:<br />
# mount -o remount /proc/bus/usb/<br />
<br />
'''Note''' by slipper modified by WretchedWinston:<br />
:I had to do ''mount /proc/bus/usb/'' after the above command to get this to work for me.<br />
<br />
Restart Virtualbox and click the USB tab in the settings of the virtual machine and select which devices are available to your pc on boot. If you wish your virtual machine to use device that you have just plugged in (assuming the virtual machine has booted already), go to the VirtualMachine screen go to devices -> USB Devices -> and select the device you wish to plug in the virtual pc.<br />
<br />
=== Installing Guest Additions ===<br />
For VirtualBox (OSE) version 1.6.2 =>, read:<br><br />
[[VirtualBox-HowTo]]<br />
<br />
The Guest Additions make the shared folders feature available, as well as better video (3D available in version 2.1+) and mouse drivers. You will have mouse integration, thus no need to release the mouse after using it in the guest and one can also enable a bidirectional clipboard.<br />
<br />
'''Note:''' The instructions immediately below are for an Archlinux guest on an Archlinux host.<br />
<br />
After you booted the virtual machine, go to menu Devices->Install Guest Additions... Once you've clicked it, VirtualBox loads an ISO into the current CD-ROM, so you won't see anything happen yet ;)<br />
<br />
You will require gcc and make if you don't already have them so install them typing the following as root:<br />
#pacman -S gcc make<br />
<br />
Then do the following as root:<br />
# mount /media/cdrom<br />
for i686 systems (32 bit):<br />
# sh /media/cdrom/VBoxLinuxAdditions-x86.run<br />
for x86-64 systems (64 bit):<br />
# sh /media/cdrom/VBoxLinuxAdditions-amd64.run<br />
<br />
<br />
It will build and install the kernel modules, install the Xorg drivers and create init scripts. It will most probably print out errors about init scripts and run levels and what not. Ignore them. You will find rc.vboxadd in /etc/rc.d which will load them on demand. To have the Guest Additions loaded at boot time, just add those to the DAEMONS array in /etc/rc.conf eg.<br />
<br />
DAEMONS=(syslog-ng network netfs crond alsa '''rc.vboxadd ''')<br />
<br />
Another option is to install one of these packages:<br />
<br />
# pacman -S virtualbox-additions<br />
<br />
or<br />
<br />
# pacman -S virtualbox-ose-additions<br />
<br />
You will then have an ISO to mount as a loop device. Remember to load the loop kernel module before:<br />
<br />
# modprobe loop<br />
# mount /usr/lib/virtualbox/additions/VBoxGuestAdditions.iso /media/cdrom -o loop<br />
<br />
Then execute VBoxLinuxAdditions.run as before. Before adding rc.vboxadd to DAEMONS check /etc/rc.local for commands to load the vboxadd daemons put by the installation script.<br />
<br />
'''Windows Guests'''<br />
<br />
After installing Windows (XP etc.) on your virtual machine, simply select Devices->Install Guest Additions...<br />
<br />
This will mount the iso image and windows should then automatically launch the guest additions installer. Follow the instructions to the end.<br />
<br />
=== Sharing folders between the host and the guest ===<br />
For VirtualBox (OSE) version 1.6.2 =>, read:<br><br />
[[VirtualBox-HowTo]]<br />
<br />
In the settings of the virtual machine go to shared folders tab and add the folders you want to share.<br />
<br />
*NOTE: You need to install Guest Additions in order to use this feature.<br />
In a Linux host, "Devices" --> "Install Guest Additions"<br />
Yes (when asked to download the CD image)<br />
Mount (when asked to register and mount)<br />
<br />
In a Linux host, create one folder for sharing files.<br />
<br />
In a Windows guest, starting with VirtualBox 1.5.0, shared folders are browseable and are therefore visible in Windows Explorer. Open Windows Explorer and look for it under:<br />
<br />
My Networking Places --> Entire Network --> VirtualBox Shared Folders<br />
<br />
Alternatively, on the Windows command line, you can also use the following:<br />
<br />
net use x: \\VBOXSVR\sharename<br />
<br />
While VBOXSVR is a fixed name, replace "x:" with the drive letter that you want to use for the share, and sharename with the share name specified with VBoxManage.<br />
<br />
In a Linux guest, use the following command:<br />
# mount -t vboxsf [-o OPTIONS] sharename mountpoint<br />
<br />
Replace sharename with the share name specified with VBoxManage, and mountpoint with the path where you want the share to be mounted (e.g. /mnt/share). The usual mount rules apply, that is, create this directory first if it does not exist yet.<br />
<br />
Beyond the standard options supplied by the mount command, the following are available:<br />
iocharset=CHARSET<br />
to set the character set used for I/O operations (utf8 by default) and<br />
convertcp=CHARSET<br />
to specify the character set used for the shared folder name (utf8 by default).<br />
<br />
=== Getting audio to work in the guest machine ===<br />
<br />
In the machine settings, go to the audio tab and select the correct driver according to your sound system (ALSA, OSS or PulseAudio).<br />
<br />
=== Setting up the RAM and Video Memory for the virtual PC ===<br />
<br />
You can change the default values by going to settings -> general.<br />
<br />
=== Setting up CDROM for the Virtual PC ===<br />
<br />
You can change the default values by going to settings -> CD/DVD-ROM.<br />
<br />
Check mount cd/dvd drive and select one of the following options.<br />
<br />
'''Note:''' If no CDROM drive is detected, make sure the HAL daemon is running. To start it, run the following command as root:<br />
<br />
# /etc/rc.d/hal start<br />
<br />
==Converting image formats==<br />
<br />
The <code>qemu-img</code> program can be used to convert images from one format to another, or add compression or encryption to an image. <br />
<br />
# pacman -S qemu<br />
<br />
=== Converting from QEMU images ===<br />
<br />
To convert a QEMU image for use with VirtualBox, first convert it to ''raw'' format, then use VirtualBox's conversion utility to convert and compact it in its native format.<br />
<br />
$ qemu-img convert -O raw test.qcow2 test.raw<br />
$ VBoxManage modifyvdi /full/path/to/test.vdi compact<br />
<br />
=== Converting from VMware images ===<br />
Do <br />
<br />
$ qemu-img convert image.vmdk image.bin<br />
$ VBoxManage convertdd image.bin image.vdi<br />
<br />
This may not be needed anymore with recent virtualbox versions (to be confirmed)<br />
<br />
== Maintenance ==<br />
<br />
=== Rebuild the vboxdrv Module ===<br />
Note that any time your kernel version changes (due to upgrade, recompile, etc.) you must also rebuild the VirtualBox kernel. To do this, on versions earlier than 2.1, run the following command:<br />
# vbox_build_module<br />
This binary will be located in one of the following locations: <tt>/sbin</tt>, <tt>/bin</tt>, or <tt>/usr/bin</tt>.<br />
<br />
On versions 2.1+, update the kernel module by running the following command:<br />
# /etc/rc.d/rc.vboxdrv setup<br />
<br />
After rebuilding the module, don't forget to load it with '''<code>modprobe vboxdrv</code>'''<br />
<br />
=== Compact a Disk Image ===<br />
See [http://my.opera.com/locksley90/blog/2008/06/01/how-to-compact-a-virtualbox-virtual-disk-image-vdi How to compact a VirtualBox virtual disk image (VDI)]<br />
<br />
=== Windows Xp and Nokia phones ===<br />
To get working Windows XP and Nokia phones with Pc Suite mode, Virtualbox needs two simple steps:<br />
<br />
1) adding a rule to udev with /etc/udev/rules.d/40-permissions.rules <br />
LABEL=”usb_serial_start”<br />
ATTRS{idVendor}==”0403″, ATTRS{idProduct}==”6001″, \<br />
GROUP="usbfs", MODE=”0660″, GROUP=”dialout”<br />
LABEL=”usb_serial_end”<br />
<br />
2) create the group usbfs and add its user to it<br />
$ sudo groupadd usbfs<br />
$ sudo usermod -a -G usbfs $USER<br />
<br />
After a logout, connect a Nokia phone with Pc Suite mode and start Windows XP to test new rule.<br />
<br />
== External Resources ==<br />
* [http://download.virtualbox.org/virtualbox/2.0.6/UserManual.pdf VirtualBox 2.0.6 User Manual]</div>Daxhttps://wiki.archlinux.org/index.php?title=VirtualBox&diff=68412VirtualBox2009-05-08T00:53:06Z<p>Dax: /* Windows Xp and Nokia phones */</p>
<hr />
<div>[[Category:Emulators (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|:VirtualBox}}<br />
{{i18n_entry|Italiano|:VirtualBox (Italiano)}}<br />
{{i18n_entry|简体中文|:VirtualBox (简体中文)}}<br />
{{i18n_entry|Русский|VirtualBox (Русский)}}<br />
{{i18n_entry|Español|VirtualBox (Español)}}<br />
{{i18n_entry|Português|VirtualBox (Português)}}<br />
{{i18n_links_end}}<br />
<br />
== What is VirtualBox ==<br />
[http://www.virtualbox.org VirtualBox] is a virtual pc emulator like vmware. It has many of the features vmware has, as well as some of its own. It is in constant development and new features are implemented all the time. eg. version 2.2 introduced OpenGL 3D acceleration support for Linux and Solaris guests. It has a nice GUI interface (Qt and/or SDL) or command line tools for managing virtual machines. Headless operation is also supported.<br />
<br />
=== Editions ===<br />
VirtualBox is available in two editions: VirtualBox (OSE) and VirtualBox (Personal Use and Evaluation License (PUEL))<br />
<br />
==== VirtualBox (OSE) ====<br />
VirtualBox (OSE) is the open source version of VirtualBox, which can be found in the community repository. It lacks some features such as USB device support and the built-in RDP server.<br />
<br />
==== VirtualBox (PUEL) ====<br />
VirtualBox PUEL is a binary-only version (free for personal use) which is available from the [http://aur.archlinux.org/packages.php?ID=9753 AUR] or directly from the <br />
[http://www.virtualbox.org/wiki/Downloads VirtualBox] website. The PUEL edition offers the following advantages:<br />
<br />
*'''Remote Display Protocol (RDP) Server''' - a complete RDP server on top of the virtual hardware, allowing users to connect to a virtual machine remotely using any RDP compatible client<br />
<br />
*'''USB support''' - a virtual USB controller which allows USB 1.1 and USB 2.0 devices to be passed through to virtual machines<br />
<br />
*'''USB over RDP''' - a combination of the RDP server and USB support, allowing users to make USB devices available to virtual machines running remotely<br />
<br />
*'''iSCSI initiator''' - a builtin iSCSI initiator making it possible to use iSCSI targets as virtual disks without the guest requiring support for iSCSI<br />
<br />
== Installation ==<br />
<br />
=== Install VirtualBox (OSE) ===<br />
<br />
VirtualBox (OSE) is available from the community repositories :<br />
<br />
# pacman -S virtualbox-ose<br />
<br />
'''Note:''' This package seems not to be in x86_64 Repositories. Version 2.0.4 does not build on x86_64. Version 2.1.0 should have better 64-bit support (to be confirmed).<br />
<br />
This will select by default <tt>virtualbox-ose</tt> and <tt>virtualbox-modules</tt> packages. Once installed, a desktop entry can be located in ''Applications > System Tools > VirtualBox OSE''<br />
<br />
Now, add the desired username to the '''vboxusers''' group:<br />
<br />
# gpasswd -a USERNAME vboxusers<br />
<br />
''('''Note:''' You must logout/login in order for this change to take effect)''<br />
<br />
Lastly, edit <tt>/etc/rc.conf</tt> as root and add '''vboxdrv''' to the MODULES array in order to load the VirtualBox drivers at startup. For example:<br />
<br />
MODULES=(loop '''vboxdrv''' fuse ...)<br />
<br />
To load the module manually, run the following in a terminal as root: <br />
<br />
# modprobe vboxdrv<br />
<br />
'''HowTo:'''<br><br />
[[VirtualBox-HowTo]]<br />
<br />
=== Install VirtualBox PUEL (virtualbox_bin) ===<br />
VirtualBox PUEL is available from the [http://aur.archlinux.org/packages.php?ID=9753 AUR: virtualbox_bin].<br />
<br />
Download the tarball from the [http://aur.archlinux.org/packages.php?ID=9753 AUR: virtualbox_bin] page, unpack, run <tt>makepkg</tt>, and then as root:<br />
<br />
# pacman -U PACKAGE-NAME.pkg.tar.gz<br />
<br />
'''However, there's an alternative way to install the virtualbox_bin package:'''<br />
<br />
Firstly, add as root the followings into /etc/pacman.conf:<br />
[archlinuxfr]<br />
Server = <nowiki>http://repo.archlinux.fr/i686</nowiki><br />
or<br />
[archlinuxfr]<br />
Server = <nowiki>http://repo.archlinux.fr/x86_64</nowiki><br />
depending on your CPU's architecture.<br />
<br />
Then you can install it successfully via:<br />
# pacman -Sy virtualbox_bin<br />
<br />
Now, add the desired username to the '''vboxusers''' group:<br />
# gpasswd -a USERNAME vboxusers<br />
<br />
''('''Note:''' You must logout/login in order for this change to take effect)''<br />
<br />
Lastly, edit <tt>/etc/rc.conf</tt> as root and add '''vboxdrv''' to the MODULES array in order to load the VirtualBox drivers at startup. For example:<br />
MODULES=(loop '''vboxdrv''' fuse ...)<br />
<br />
To load the module manually, run the following in a terminal as root: <br />
# modprobe vboxdrv<br />
<br />
=== Install required QT libraries ===<br />
Currently, VirtualBox relies on qt4 for its graphical interface. If you require a GUI, ensure you have qt4 installed:<br />
# pacman -S qt<br />
<br />
=== Start VirtualBox ===<br />
To start Virtualbox, run the following command in a terminal:<br />
$ VirtualBox<br />
<br />
=== Install VirtualBox 2.1 (another alternative) ===<br />
<br />
VirtualBox.run install can be done using the All Distributions package from the [http://www.virtualbox.org/wiki/Linux_Downloads Linux section] of the VirtualBox Website.<br />
<br />
Make sure the Qt 4.3.0 and SDL 1.2.7 or higher packages are installed:<br />
<br />
# pacman -Sy qt sdl <br />
<br />
Download the appropriate architecture file i386/AMD64. In a terminal window, browse to the download folder and as root run:<br />
<br />
# sh VirtualBox-2.XXXX-Linux_ARCH.run<br />
<br />
This will install the package to the /opt/VirtualBox-2.XXX folder.<br />
<br />
After installation, a desktop entry can be located in ''Applications > System Tools > Sun xVM VirtualBox''<br />
<br />
Now, add the desired username to the '''vboxusers''' group:<br />
# gpasswd -a USERNAME vboxusers<br />
<br />
Lastly, edit <tt>/etc/rc.conf</tt> as root and add '''vboxdrv''' to the MODULES array in order to load the VirtualBox drivers at startup.<br />
<br />
Start the VirtualBox GUI either with the command:<br />
<br />
# VirtualBox <br />
<br />
or using the ''Applications'' desktop entry. In version 2.1.x, an installation wizard should start and take you through the process of setting up a virtual machine. Otherwise, use the help menu to get started. '''Continue reading to see the more advanced options and setups....'''<br />
<br />
== Configuration ==<br />
After we have installed VirtualBox on our system and added ourselves in the vboxusers group we can start configuring our system in order to make all the features of VirtualBox available to us.Create a new virtual machine using the wizard provided by the GUI and then click settings in order to edit the virtual machine settings.<br />
<br />
=== Keyboard and mouse between the host and the guest ===<br />
To capture the keyboard and mouse, click the mouse inside the Virtual Machine display.<br><br />
To uncapture, "Ctrl-Alt Delete".<br />
<br />
If [[Xorg]] freezes mouse and keyboard you will have to disable the [[Xorg#Input_hotplugging_with_xorg-server_1.5| new hot plugging feature of Xorg 1.5]] by adding in /etc/X11/xorg.conf:<br />
<br />
Section "ServerLayout"<br />
. . .<br />
Option "AutoAddDevices" "False"<br />
. . .<br />
EndSection<br />
<br />
This is needed for Linux guests in a Mac OS X or Windows host. Also needed for Linux hosts (tested with Arch64 host and Arch64 guest).<br />
<br />
Also, mouse pointer integration doesn't work out of the box. To fix it, make sure you have the following sections in your xorg.conf:<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "vboxmouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
When generating your xorg.conf with "X -configure", you'll end up with an InputDevice section that uses the "mouse" driver. After installing the Guest Additions, you should replace "mouse" with "vboxmouse" and then restart X or reboot your VM.<br />
<br />
=== Getting network in the guest machine to work ===<br />
First let's get network working in the guest machine. Click the network tab. The not attached option means you'll have "Network cable unplugged" or similar error in the guest computer.<br />
<br />
==== Using NAT network ====<br />
This is the simplest way to get network. Select NAT network and it should be ready to use. Then, the guest operating system can be automatically configured by using DHCP.<br />
<br />
The NAT IP address on the first card is 10.0.2.0, 10.0.3.0 on the second and so on.<br />
<br />
==== Using host interface networking (the VirtualBox way) ====<br />
Since VirtuaBox 2.1.0 it has a native support for host interface networking. Just add '''vboxnetflt''' to your MODULES section in [[rc.conf]] and choose ''Host Interface Networking'' in the virtual machine configuration.<br />
<br />
==== Using host interface networking (the Arch way) ====<br />
You are going to just edit these files and reboot:<br />
<br />
* /etc/conf.d/bridges<br />
* /etc/rc.conf<br />
* /etc/vbox/interfaces<br />
<br />
Ready? Let's go!<br />
<br />
'''/etc/conf.d/bridges:'''<br />
bridge_br0="eth0 vbox0" # Put any interfaces you need.<br />
BRIDGE_INTERFACES=(br0)<br />
<br />
'''/etc/rc.conf:'''<br />
<br />
First add the bridge module to your MODULES line<br />
MODULES=( <your other modules> '''bridge''')<br />
<br />
Then, in your NETWORKING section, make the following changes:<br />
br0="dhcp" # Maybe you have some static configuration... I use DHCP.<br />
INTERFACES=(eth0 br0)<br />
<br />
'''Note''' by gpan:<br />
<br />
'''/etc/rc.conf:'''<br />
<br />
First add the vboxdrv (and [[vboxnetflt]] in case of 2.1.0 version) module to your MODULES line<br />
<br />
MODULES=( <your other modules> vboxdrv vboxnetflt )<br />
<br />
<br />
Next, you should edit your '''/etc/udev/rules.d/60-vboxdrv.rules''' and type:<br />
<br />
KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="vboxusers", MODE="0660"<br />
<br />
Save it and exit.<br />
<br />
Then open terminal and type:<br />
<br />
# pacman -S bridge-utils uml_utilities<br />
<br />
Create a new bridge with this command:<br />
<br />
# brctl addbr br0<br />
<br />
<br />
'''/etc/vbox/interfaces'''<br />
<br />
(You can set up more interfaces if you want. Sky is the limit!):<br />
vbox0 your_user br0 # Be sure that your user is in the vboxusers group.<br />
<br />
Reboot and enjoy!<br />
<br />
'''''Note:''' Remember to set up your virtual machine with proper network configuration.''<br />
<br />
'''''Note:''' If you have any issue, make sure that you have the bridge-utils package installed and vboxnet daemon loaded''<br />
<br />
==== Using host interface networking (generic) ====<br />
This way is a bit harder, but it allows you to see the VirtualMachine as a "real" computer on your local network. You need to get bridge-utils <br />
<br />
# pacman -S bridge-utils uml_utilities<br />
<br />
'''Note''' by Sp1d3rmxn:<br />
:You also need to have the TUN module loaded...in [[rc.conf]] add "tun" (without the :quotes) to your MODULES section. For testing this out right now without rebooting :you can load the module from the command line by "modprobe tun".<br />
:<br />
:Then you MUST set these permissions otherwise you'll never get VBox to init the :interface. The command is "<code>chmod 666 /dev/net/tun</code>" (without the quotes).<br />
<br />
:Now proceed with the rest as it's written below.<br />
<br />
'''Note''' by Dharivs<br />
:As said by Sp1d3rmxn, we must set these permissions, but, instead of using the <br />
:command, we can set them in /etc/udev/rules.d/60-vboxdrv.rules, which will set them <br />
:on boot:<br />
KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="vboxusers", MODE="0660"<br />
KERNEL=="tun", OWNER="root", GROUP="vboxusers", MODE="0660"<br />
<br />
<br />
<b>1.</b> Create a new bridge with this command:<br />
# brctl addbr br0<br />
<br />
<b>2.</b> If you are not using DHCP, run ifconfig and note down the network configuration of your existing network interface (e.g. eth0), which we will need to copy to the bridge in a minute.<br />
<br />
''('''Note: You will need this settings so make sure you don't lose them!!!''')''<br />
<br />
<b>3.</b> Switch your physical network adapter to "promiscuous" mode so that it will accept Ethernet frames for MAC addresses other than its own (replace eth0 with your network interface):<br />
# ifconfig eth0 0.0.0.0 promisc <br />
<br />
''('''Note:''' You will lose network connectivity on eth0 at this point.)''<br />
<br />
<b>4.</b> Add your network adapter to the bridge:<br />
# brctl addif br0 eth0<br />
<br />
<b>5.</b> Transfer the network configuration previously used with your physical ethernet adapter to the new bridge. If you are using DHCP, this should work:<br />
# dhclient br0<br />
<br />
'''Note''' by Sp1d3rmxn:<br />
:Use "dhcpcd -t 30 -h yourhostname br0 &" instead of the above<br />
<br />
Otherwise, run <code>ifconfig br0 x.x.x.x netmask x.x.x.x</code> and use the values that you noted down previously.<br />
<br />
<b>6.</b> To create a permanent host interface called vbox0 (all host interfaces created in this way must be called vbox followed by a number) and add it to the network bridge created above, use the following command:<br />
VBoxAddIF vbox0 vboxuser br0<br />
<br />
Replace vboxuser with the name of the user who is supposed to be able to use the new interface.<br />
<br />
('''Note:''' VboxAddIF is located in /opt/VirtualBox-VERSION OF VIRTUALBOX/VBoxAddIF)<br />
<br />
Alternatively, you can [http://mychael.gotdns.com/blog/2007/05/31/virtualbox-bridging/ setup VirtualBox networking] through your /etc/rc.conf to enable a bridged connection.<br />
<br />
==== Using host interface networking with a wireless device ====<br />
Bridging as described above won't work with a wireless device. Using [http://aur.archlinux.org/packages.php?ID=16356 parprouted] however it can be accomplished.<br />
<br />
# Install parprouted and iproute<br />
# <code># ln -s /usr/sbin/ip /sbin/ip</code><br />
# Make sure IP fowarding is enabled: <code># sysctl net.ipv4.ip_forward=1</code>, and/or edit /etc/sysctl.conf<br />
# <code># VBoxTunctl -b -u <user></code>, to create the tap device<br />
# <code># ip link set tap0 up; ip addr add 192.168.0.X/24 dev tap0</code>, needs to be a manually set IP on the same network your wireless device is.<br />
# <code># parprouted wlan0 tap0</code><br />
<br />
=== Getting USB to work in the guest machine ===<br />
(Only available in the PUEL edition)<br />
<br />
First in order to make usb available for use to the virtual machine you must add this line to your /etc/fstab<br />
none /proc/bus/usb usbfs auto,busgid=108,busmode=0775,devgid=108,devmode=0664 0 0<br />
<br />
108 is is the id of the group which should be allowed to access USB-devices. Change it to the id of your vboxusers group. You can get the id by running:<br />
$ grep vboxusers /etc/group<br />
<br />
If you don't mind a security hole change devmode from 664 to 666.<br />
<br />
Remount /proc/bus/usb:<br />
# mount -o remount /proc/bus/usb/<br />
<br />
'''Note''' by slipper modified by WretchedWinston:<br />
:I had to do ''mount /proc/bus/usb/'' after the above command to get this to work for me.<br />
<br />
Restart Virtualbox and click the USB tab in the settings of the virtual machine and select which devices are available to your pc on boot. If you wish your virtual machine to use device that you have just plugged in (assuming the virtual machine has booted already), go to the VirtualMachine screen go to devices -> USB Devices -> and select the device you wish to plug in the virtual pc.<br />
<br />
=== Installing Guest Additions ===<br />
For VirtualBox (OSE) version 1.6.2 =>, read:<br><br />
[[VirtualBox-HowTo]]<br />
<br />
The Guest Additions make the shared folders feature available, as well as better video (3D available in version 2.1+) and mouse drivers. You will have mouse integration, thus no need to release the mouse after using it in the guest and one can also enable a bidirectional clipboard.<br />
<br />
'''Note:''' The instructions immediately below are for an Archlinux guest on an Archlinux host.<br />
<br />
After you booted the virtual machine, go to menu Devices->Install Guest Additions... Once you've clicked it, VirtualBox loads an ISO into the current CD-ROM, so you won't see anything happen yet ;)<br />
<br />
You will require gcc and make if you don't already have them so install them typing the following as root:<br />
#pacman -S gcc make<br />
<br />
Then do the following as root:<br />
# mount /media/cdrom<br />
for i686 systems (32 bit):<br />
# sh /media/cdrom/VBoxLinuxAdditions-x86.run<br />
for x86-64 systems (64 bit):<br />
# sh /media/cdrom/VBoxLinuxAdditions-amd64.run<br />
<br />
<br />
It will build and install the kernel modules, install the Xorg drivers and create init scripts. It will most probably print out errors about init scripts and run levels and what not. Ignore them. You will find rc.vboxadd in /etc/rc.d which will load them on demand. To have the Guest Additions loaded at boot time, just add those to the DAEMONS array in /etc/rc.conf eg.<br />
<br />
DAEMONS=(syslog-ng network netfs crond alsa '''rc.vboxadd ''')<br />
<br />
Another option is to install one of these packages:<br />
<br />
# pacman -S virtualbox-additions<br />
<br />
or<br />
<br />
# pacman -S virtualbox-ose-additions<br />
<br />
You will then have an ISO to mount as a loop device. Remember to load the loop kernel module before:<br />
<br />
# modprobe loop<br />
# mount /usr/lib/virtualbox/additions/VBoxGuestAdditions.iso /media/cdrom -o loop<br />
<br />
Then execute VBoxLinuxAdditions.run as before. Before adding rc.vboxadd to DAEMONS check /etc/rc.local for commands to load the vboxadd daemons put by the installation script.<br />
<br />
'''Windows Guests'''<br />
<br />
After installing Windows (XP etc.) on your virtual machine, simply select Devices->Install Guest Additions...<br />
<br />
This will mount the iso image and windows should then automatically launch the guest additions installer. Follow the instructions to the end.<br />
<br />
=== Sharing folders between the host and the guest ===<br />
For VirtualBox (OSE) version 1.6.2 =>, read:<br><br />
[[VirtualBox-HowTo]]<br />
<br />
In the settings of the virtual machine go to shared folders tab and add the folders you want to share.<br />
<br />
*NOTE: You need to install Guest Additions in order to use this feature.<br />
In a Linux host, "Devices" --> "Install Guest Additions"<br />
Yes (when asked to download the CD image)<br />
Mount (when asked to register and mount)<br />
<br />
In a Linux host, create one folder for sharing files.<br />
<br />
In a Windows guest, starting with VirtualBox 1.5.0, shared folders are browseable and are therefore visible in Windows Explorer. Open Windows Explorer and look for it under:<br />
<br />
My Networking Places --> Entire Network --> VirtualBox Shared Folders<br />
<br />
Alternatively, on the Windows command line, you can also use the following:<br />
<br />
net use x: \\VBOXSVR\sharename<br />
<br />
While VBOXSVR is a fixed name, replace "x:" with the drive letter that you want to use for the share, and sharename with the share name specified with VBoxManage.<br />
<br />
In a Linux guest, use the following command:<br />
# mount -t vboxsf [-o OPTIONS] sharename mountpoint<br />
<br />
Replace sharename with the share name specified with VBoxManage, and mountpoint with the path where you want the share to be mounted (e.g. /mnt/share). The usual mount rules apply, that is, create this directory first if it does not exist yet.<br />
<br />
Beyond the standard options supplied by the mount command, the following are available:<br />
iocharset=CHARSET<br />
to set the character set used for I/O operations (utf8 by default) and<br />
convertcp=CHARSET<br />
to specify the character set used for the shared folder name (utf8 by default).<br />
<br />
=== Getting audio to work in the guest machine ===<br />
<br />
In the machine settings, go to the audio tab and select the correct driver according to your sound system (ALSA, OSS or PulseAudio).<br />
<br />
=== Setting up the RAM and Video Memory for the virtual PC ===<br />
<br />
You can change the default values by going to settings -> general.<br />
<br />
=== Setting up CDROM for the Virtual PC ===<br />
<br />
You can change the default values by going to settings -> CD/DVD-ROM.<br />
<br />
Check mount cd/dvd drive and select one of the following options.<br />
<br />
'''Note:''' If no CDROM drive is detected, make sure the HAL daemon is running. To start it, run the following command as root:<br />
<br />
# /etc/rc.d/hal start<br />
<br />
==Converting image formats==<br />
<br />
The <code>qemu-img</code> program can be used to convert images from one format to another, or add compression or encryption to an image. <br />
<br />
# pacman -S qemu<br />
<br />
=== Converting from QEMU images ===<br />
<br />
To convert a QEMU image for use with VirtualBox, first convert it to ''raw'' format, then use VirtualBox's conversion utility to convert and compact it in its native format.<br />
<br />
$ qemu-img convert -O raw test.qcow2 test.raw<br />
$ VBoxManage modifyvdi /full/path/to/test.vdi compact<br />
<br />
=== Converting from VMware images ===<br />
Do <br />
<br />
$ qemu-img convert image.vmdk image.bin<br />
$ VBoxManage convertdd image.bin image.vdi<br />
<br />
This may not be needed anymore with recent virtualbox versions (to be confirmed)<br />
<br />
== Maintenance ==<br />
<br />
=== Rebuild the vboxdrv Module ===<br />
Note that any time your kernel version changes (due to upgrade, recompile, etc.) you must also rebuild the VirtualBox kernel. To do this, on versions earlier than 2.1, run the following command:<br />
# vbox_build_module<br />
This binary will be located in one of the following locations: <tt>/sbin</tt>, <tt>/bin</tt>, or <tt>/usr/bin</tt>.<br />
<br />
On versions 2.1+, update the kernel module by running the following command:<br />
# /etc/rc.d/rc.vboxdrv setup<br />
<br />
After rebuilding the module, don't forget to load it with '''<code>modprobe vboxdrv</code>'''<br />
<br />
=== Compact a Disk Image ===<br />
See [http://my.opera.com/locksley90/blog/2008/06/01/how-to-compact-a-virtualbox-virtual-disk-image-vdi How to compact a VirtualBox virtual disk image (VDI)]<br />
<br />
=== Windows Xp and Nokia phones ===<br />
To get working Windows XP and Nokia phones with Pc Suite mode, Virtualbox needs two simple steps:<br />
<br />
1) adding a rule to udev with /etc/udev/rules.d/40-permissions.rules <br />
LABEL=”usb_serial_start”<br />
ATTRS{idVendor}==”0403″, ATTRS{idProduct}==”6001″, \<br />
GROUP="usbfs", MODE=”0660″, GROUP=”dialout”<br />
LABEL=”usb_serial_end”<br />
<br />
2) create the group usbfs and add its user to it<br />
<br />
== External Resources ==<br />
* [http://download.virtualbox.org/virtualbox/2.0.6/UserManual.pdf VirtualBox 2.0.6 User Manual]</div>Daxhttps://wiki.archlinux.org/index.php?title=VirtualBox&diff=68411VirtualBox2009-05-08T00:51:09Z<p>Dax: </p>
<hr />
<div>[[Category:Emulators (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|:VirtualBox}}<br />
{{i18n_entry|Italiano|:VirtualBox (Italiano)}}<br />
{{i18n_entry|简体中文|:VirtualBox (简体中文)}}<br />
{{i18n_entry|Русский|VirtualBox (Русский)}}<br />
{{i18n_entry|Español|VirtualBox (Español)}}<br />
{{i18n_entry|Português|VirtualBox (Português)}}<br />
{{i18n_links_end}}<br />
<br />
== What is VirtualBox ==<br />
[http://www.virtualbox.org VirtualBox] is a virtual pc emulator like vmware. It has many of the features vmware has, as well as some of its own. It is in constant development and new features are implemented all the time. eg. version 2.2 introduced OpenGL 3D acceleration support for Linux and Solaris guests. It has a nice GUI interface (Qt and/or SDL) or command line tools for managing virtual machines. Headless operation is also supported.<br />
<br />
=== Editions ===<br />
VirtualBox is available in two editions: VirtualBox (OSE) and VirtualBox (Personal Use and Evaluation License (PUEL))<br />
<br />
==== VirtualBox (OSE) ====<br />
VirtualBox (OSE) is the open source version of VirtualBox, which can be found in the community repository. It lacks some features such as USB device support and the built-in RDP server.<br />
<br />
==== VirtualBox (PUEL) ====<br />
VirtualBox PUEL is a binary-only version (free for personal use) which is available from the [http://aur.archlinux.org/packages.php?ID=9753 AUR] or directly from the <br />
[http://www.virtualbox.org/wiki/Downloads VirtualBox] website. The PUEL edition offers the following advantages:<br />
<br />
*'''Remote Display Protocol (RDP) Server''' - a complete RDP server on top of the virtual hardware, allowing users to connect to a virtual machine remotely using any RDP compatible client<br />
<br />
*'''USB support''' - a virtual USB controller which allows USB 1.1 and USB 2.0 devices to be passed through to virtual machines<br />
<br />
*'''USB over RDP''' - a combination of the RDP server and USB support, allowing users to make USB devices available to virtual machines running remotely<br />
<br />
*'''iSCSI initiator''' - a builtin iSCSI initiator making it possible to use iSCSI targets as virtual disks without the guest requiring support for iSCSI<br />
<br />
== Installation ==<br />
<br />
=== Install VirtualBox (OSE) ===<br />
<br />
VirtualBox (OSE) is available from the community repositories :<br />
<br />
# pacman -S virtualbox-ose<br />
<br />
'''Note:''' This package seems not to be in x86_64 Repositories. Version 2.0.4 does not build on x86_64. Version 2.1.0 should have better 64-bit support (to be confirmed).<br />
<br />
This will select by default <tt>virtualbox-ose</tt> and <tt>virtualbox-modules</tt> packages. Once installed, a desktop entry can be located in ''Applications > System Tools > VirtualBox OSE''<br />
<br />
Now, add the desired username to the '''vboxusers''' group:<br />
<br />
# gpasswd -a USERNAME vboxusers<br />
<br />
''('''Note:''' You must logout/login in order for this change to take effect)''<br />
<br />
Lastly, edit <tt>/etc/rc.conf</tt> as root and add '''vboxdrv''' to the MODULES array in order to load the VirtualBox drivers at startup. For example:<br />
<br />
MODULES=(loop '''vboxdrv''' fuse ...)<br />
<br />
To load the module manually, run the following in a terminal as root: <br />
<br />
# modprobe vboxdrv<br />
<br />
'''HowTo:'''<br><br />
[[VirtualBox-HowTo]]<br />
<br />
=== Install VirtualBox PUEL (virtualbox_bin) ===<br />
VirtualBox PUEL is available from the [http://aur.archlinux.org/packages.php?ID=9753 AUR: virtualbox_bin].<br />
<br />
Download the tarball from the [http://aur.archlinux.org/packages.php?ID=9753 AUR: virtualbox_bin] page, unpack, run <tt>makepkg</tt>, and then as root:<br />
<br />
# pacman -U PACKAGE-NAME.pkg.tar.gz<br />
<br />
'''However, there's an alternative way to install the virtualbox_bin package:'''<br />
<br />
Firstly, add as root the followings into /etc/pacman.conf:<br />
[archlinuxfr]<br />
Server = <nowiki>http://repo.archlinux.fr/i686</nowiki><br />
or<br />
[archlinuxfr]<br />
Server = <nowiki>http://repo.archlinux.fr/x86_64</nowiki><br />
depending on your CPU's architecture.<br />
<br />
Then you can install it successfully via:<br />
# pacman -Sy virtualbox_bin<br />
<br />
Now, add the desired username to the '''vboxusers''' group:<br />
# gpasswd -a USERNAME vboxusers<br />
<br />
''('''Note:''' You must logout/login in order for this change to take effect)''<br />
<br />
Lastly, edit <tt>/etc/rc.conf</tt> as root and add '''vboxdrv''' to the MODULES array in order to load the VirtualBox drivers at startup. For example:<br />
MODULES=(loop '''vboxdrv''' fuse ...)<br />
<br />
To load the module manually, run the following in a terminal as root: <br />
# modprobe vboxdrv<br />
<br />
=== Install required QT libraries ===<br />
Currently, VirtualBox relies on qt4 for its graphical interface. If you require a GUI, ensure you have qt4 installed:<br />
# pacman -S qt<br />
<br />
=== Start VirtualBox ===<br />
To start Virtualbox, run the following command in a terminal:<br />
$ VirtualBox<br />
<br />
=== Install VirtualBox 2.1 (another alternative) ===<br />
<br />
VirtualBox.run install can be done using the All Distributions package from the [http://www.virtualbox.org/wiki/Linux_Downloads Linux section] of the VirtualBox Website.<br />
<br />
Make sure the Qt 4.3.0 and SDL 1.2.7 or higher packages are installed:<br />
<br />
# pacman -Sy qt sdl <br />
<br />
Download the appropriate architecture file i386/AMD64. In a terminal window, browse to the download folder and as root run:<br />
<br />
# sh VirtualBox-2.XXXX-Linux_ARCH.run<br />
<br />
This will install the package to the /opt/VirtualBox-2.XXX folder.<br />
<br />
After installation, a desktop entry can be located in ''Applications > System Tools > Sun xVM VirtualBox''<br />
<br />
Now, add the desired username to the '''vboxusers''' group:<br />
# gpasswd -a USERNAME vboxusers<br />
<br />
Lastly, edit <tt>/etc/rc.conf</tt> as root and add '''vboxdrv''' to the MODULES array in order to load the VirtualBox drivers at startup.<br />
<br />
Start the VirtualBox GUI either with the command:<br />
<br />
# VirtualBox <br />
<br />
or using the ''Applications'' desktop entry. In version 2.1.x, an installation wizard should start and take you through the process of setting up a virtual machine. Otherwise, use the help menu to get started. '''Continue reading to see the more advanced options and setups....'''<br />
<br />
== Configuration ==<br />
After we have installed VirtualBox on our system and added ourselves in the vboxusers group we can start configuring our system in order to make all the features of VirtualBox available to us.Create a new virtual machine using the wizard provided by the GUI and then click settings in order to edit the virtual machine settings.<br />
<br />
=== Keyboard and mouse between the host and the guest ===<br />
To capture the keyboard and mouse, click the mouse inside the Virtual Machine display.<br><br />
To uncapture, "Ctrl-Alt Delete".<br />
<br />
If [[Xorg]] freezes mouse and keyboard you will have to disable the [[Xorg#Input_hotplugging_with_xorg-server_1.5| new hot plugging feature of Xorg 1.5]] by adding in /etc/X11/xorg.conf:<br />
<br />
Section "ServerLayout"<br />
. . .<br />
Option "AutoAddDevices" "False"<br />
. . .<br />
EndSection<br />
<br />
This is needed for Linux guests in a Mac OS X or Windows host. Also needed for Linux hosts (tested with Arch64 host and Arch64 guest).<br />
<br />
Also, mouse pointer integration doesn't work out of the box. To fix it, make sure you have the following sections in your xorg.conf:<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "vboxmouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
When generating your xorg.conf with "X -configure", you'll end up with an InputDevice section that uses the "mouse" driver. After installing the Guest Additions, you should replace "mouse" with "vboxmouse" and then restart X or reboot your VM.<br />
<br />
=== Getting network in the guest machine to work ===<br />
First let's get network working in the guest machine. Click the network tab. The not attached option means you'll have "Network cable unplugged" or similar error in the guest computer.<br />
<br />
==== Using NAT network ====<br />
This is the simplest way to get network. Select NAT network and it should be ready to use. Then, the guest operating system can be automatically configured by using DHCP.<br />
<br />
The NAT IP address on the first card is 10.0.2.0, 10.0.3.0 on the second and so on.<br />
<br />
==== Using host interface networking (the VirtualBox way) ====<br />
Since VirtuaBox 2.1.0 it has a native support for host interface networking. Just add '''vboxnetflt''' to your MODULES section in [[rc.conf]] and choose ''Host Interface Networking'' in the virtual machine configuration.<br />
<br />
==== Using host interface networking (the Arch way) ====<br />
You are going to just edit these files and reboot:<br />
<br />
* /etc/conf.d/bridges<br />
* /etc/rc.conf<br />
* /etc/vbox/interfaces<br />
<br />
Ready? Let's go!<br />
<br />
'''/etc/conf.d/bridges:'''<br />
bridge_br0="eth0 vbox0" # Put any interfaces you need.<br />
BRIDGE_INTERFACES=(br0)<br />
<br />
'''/etc/rc.conf:'''<br />
<br />
First add the bridge module to your MODULES line<br />
MODULES=( <your other modules> '''bridge''')<br />
<br />
Then, in your NETWORKING section, make the following changes:<br />
br0="dhcp" # Maybe you have some static configuration... I use DHCP.<br />
INTERFACES=(eth0 br0)<br />
<br />
'''Note''' by gpan:<br />
<br />
'''/etc/rc.conf:'''<br />
<br />
First add the vboxdrv (and [[vboxnetflt]] in case of 2.1.0 version) module to your MODULES line<br />
<br />
MODULES=( <your other modules> vboxdrv vboxnetflt )<br />
<br />
<br />
Next, you should edit your '''/etc/udev/rules.d/60-vboxdrv.rules''' and type:<br />
<br />
KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="vboxusers", MODE="0660"<br />
<br />
Save it and exit.<br />
<br />
Then open terminal and type:<br />
<br />
# pacman -S bridge-utils uml_utilities<br />
<br />
Create a new bridge with this command:<br />
<br />
# brctl addbr br0<br />
<br />
<br />
'''/etc/vbox/interfaces'''<br />
<br />
(You can set up more interfaces if you want. Sky is the limit!):<br />
vbox0 your_user br0 # Be sure that your user is in the vboxusers group.<br />
<br />
Reboot and enjoy!<br />
<br />
'''''Note:''' Remember to set up your virtual machine with proper network configuration.''<br />
<br />
'''''Note:''' If you have any issue, make sure that you have the bridge-utils package installed and vboxnet daemon loaded''<br />
<br />
==== Using host interface networking (generic) ====<br />
This way is a bit harder, but it allows you to see the VirtualMachine as a "real" computer on your local network. You need to get bridge-utils <br />
<br />
# pacman -S bridge-utils uml_utilities<br />
<br />
'''Note''' by Sp1d3rmxn:<br />
:You also need to have the TUN module loaded...in [[rc.conf]] add "tun" (without the :quotes) to your MODULES section. For testing this out right now without rebooting :you can load the module from the command line by "modprobe tun".<br />
:<br />
:Then you MUST set these permissions otherwise you'll never get VBox to init the :interface. The command is "<code>chmod 666 /dev/net/tun</code>" (without the quotes).<br />
<br />
:Now proceed with the rest as it's written below.<br />
<br />
'''Note''' by Dharivs<br />
:As said by Sp1d3rmxn, we must set these permissions, but, instead of using the <br />
:command, we can set them in /etc/udev/rules.d/60-vboxdrv.rules, which will set them <br />
:on boot:<br />
KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="vboxusers", MODE="0660"<br />
KERNEL=="tun", OWNER="root", GROUP="vboxusers", MODE="0660"<br />
<br />
<br />
<b>1.</b> Create a new bridge with this command:<br />
# brctl addbr br0<br />
<br />
<b>2.</b> If you are not using DHCP, run ifconfig and note down the network configuration of your existing network interface (e.g. eth0), which we will need to copy to the bridge in a minute.<br />
<br />
''('''Note: You will need this settings so make sure you don't lose them!!!''')''<br />
<br />
<b>3.</b> Switch your physical network adapter to "promiscuous" mode so that it will accept Ethernet frames for MAC addresses other than its own (replace eth0 with your network interface):<br />
# ifconfig eth0 0.0.0.0 promisc <br />
<br />
''('''Note:''' You will lose network connectivity on eth0 at this point.)''<br />
<br />
<b>4.</b> Add your network adapter to the bridge:<br />
# brctl addif br0 eth0<br />
<br />
<b>5.</b> Transfer the network configuration previously used with your physical ethernet adapter to the new bridge. If you are using DHCP, this should work:<br />
# dhclient br0<br />
<br />
'''Note''' by Sp1d3rmxn:<br />
:Use "dhcpcd -t 30 -h yourhostname br0 &" instead of the above<br />
<br />
Otherwise, run <code>ifconfig br0 x.x.x.x netmask x.x.x.x</code> and use the values that you noted down previously.<br />
<br />
<b>6.</b> To create a permanent host interface called vbox0 (all host interfaces created in this way must be called vbox followed by a number) and add it to the network bridge created above, use the following command:<br />
VBoxAddIF vbox0 vboxuser br0<br />
<br />
Replace vboxuser with the name of the user who is supposed to be able to use the new interface.<br />
<br />
('''Note:''' VboxAddIF is located in /opt/VirtualBox-VERSION OF VIRTUALBOX/VBoxAddIF)<br />
<br />
Alternatively, you can [http://mychael.gotdns.com/blog/2007/05/31/virtualbox-bridging/ setup VirtualBox networking] through your /etc/rc.conf to enable a bridged connection.<br />
<br />
==== Using host interface networking with a wireless device ====<br />
Bridging as described above won't work with a wireless device. Using [http://aur.archlinux.org/packages.php?ID=16356 parprouted] however it can be accomplished.<br />
<br />
# Install parprouted and iproute<br />
# <code># ln -s /usr/sbin/ip /sbin/ip</code><br />
# Make sure IP fowarding is enabled: <code># sysctl net.ipv4.ip_forward=1</code>, and/or edit /etc/sysctl.conf<br />
# <code># VBoxTunctl -b -u <user></code>, to create the tap device<br />
# <code># ip link set tap0 up; ip addr add 192.168.0.X/24 dev tap0</code>, needs to be a manually set IP on the same network your wireless device is.<br />
# <code># parprouted wlan0 tap0</code><br />
<br />
=== Getting USB to work in the guest machine ===<br />
(Only available in the PUEL edition)<br />
<br />
First in order to make usb available for use to the virtual machine you must add this line to your /etc/fstab<br />
none /proc/bus/usb usbfs auto,busgid=108,busmode=0775,devgid=108,devmode=0664 0 0<br />
<br />
108 is is the id of the group which should be allowed to access USB-devices. Change it to the id of your vboxusers group. You can get the id by running:<br />
$ grep vboxusers /etc/group<br />
<br />
If you don't mind a security hole change devmode from 664 to 666.<br />
<br />
Remount /proc/bus/usb:<br />
# mount -o remount /proc/bus/usb/<br />
<br />
'''Note''' by slipper modified by WretchedWinston:<br />
:I had to do ''mount /proc/bus/usb/'' after the above command to get this to work for me.<br />
<br />
Restart Virtualbox and click the USB tab in the settings of the virtual machine and select which devices are available to your pc on boot. If you wish your virtual machine to use device that you have just plugged in (assuming the virtual machine has booted already), go to the VirtualMachine screen go to devices -> USB Devices -> and select the device you wish to plug in the virtual pc.<br />
<br />
=== Installing Guest Additions ===<br />
For VirtualBox (OSE) version 1.6.2 =>, read:<br><br />
[[VirtualBox-HowTo]]<br />
<br />
The Guest Additions make the shared folders feature available, as well as better video (3D available in version 2.1+) and mouse drivers. You will have mouse integration, thus no need to release the mouse after using it in the guest and one can also enable a bidirectional clipboard.<br />
<br />
'''Note:''' The instructions immediately below are for an Archlinux guest on an Archlinux host.<br />
<br />
After you booted the virtual machine, go to menu Devices->Install Guest Additions... Once you've clicked it, VirtualBox loads an ISO into the current CD-ROM, so you won't see anything happen yet ;)<br />
<br />
You will require gcc and make if you don't already have them so install them typing the following as root:<br />
#pacman -S gcc make<br />
<br />
Then do the following as root:<br />
# mount /media/cdrom<br />
for i686 systems (32 bit):<br />
# sh /media/cdrom/VBoxLinuxAdditions-x86.run<br />
for x86-64 systems (64 bit):<br />
# sh /media/cdrom/VBoxLinuxAdditions-amd64.run<br />
<br />
<br />
It will build and install the kernel modules, install the Xorg drivers and create init scripts. It will most probably print out errors about init scripts and run levels and what not. Ignore them. You will find rc.vboxadd in /etc/rc.d which will load them on demand. To have the Guest Additions loaded at boot time, just add those to the DAEMONS array in /etc/rc.conf eg.<br />
<br />
DAEMONS=(syslog-ng network netfs crond alsa '''rc.vboxadd ''')<br />
<br />
Another option is to install one of these packages:<br />
<br />
# pacman -S virtualbox-additions<br />
<br />
or<br />
<br />
# pacman -S virtualbox-ose-additions<br />
<br />
You will then have an ISO to mount as a loop device. Remember to load the loop kernel module before:<br />
<br />
# modprobe loop<br />
# mount /usr/lib/virtualbox/additions/VBoxGuestAdditions.iso /media/cdrom -o loop<br />
<br />
Then execute VBoxLinuxAdditions.run as before. Before adding rc.vboxadd to DAEMONS check /etc/rc.local for commands to load the vboxadd daemons put by the installation script.<br />
<br />
'''Windows Guests'''<br />
<br />
After installing Windows (XP etc.) on your virtual machine, simply select Devices->Install Guest Additions...<br />
<br />
This will mount the iso image and windows should then automatically launch the guest additions installer. Follow the instructions to the end.<br />
<br />
=== Sharing folders between the host and the guest ===<br />
For VirtualBox (OSE) version 1.6.2 =>, read:<br><br />
[[VirtualBox-HowTo]]<br />
<br />
In the settings of the virtual machine go to shared folders tab and add the folders you want to share.<br />
<br />
*NOTE: You need to install Guest Additions in order to use this feature.<br />
In a Linux host, "Devices" --> "Install Guest Additions"<br />
Yes (when asked to download the CD image)<br />
Mount (when asked to register and mount)<br />
<br />
In a Linux host, create one folder for sharing files.<br />
<br />
In a Windows guest, starting with VirtualBox 1.5.0, shared folders are browseable and are therefore visible in Windows Explorer. Open Windows Explorer and look for it under:<br />
<br />
My Networking Places --> Entire Network --> VirtualBox Shared Folders<br />
<br />
Alternatively, on the Windows command line, you can also use the following:<br />
<br />
net use x: \\VBOXSVR\sharename<br />
<br />
While VBOXSVR is a fixed name, replace "x:" with the drive letter that you want to use for the share, and sharename with the share name specified with VBoxManage.<br />
<br />
In a Linux guest, use the following command:<br />
# mount -t vboxsf [-o OPTIONS] sharename mountpoint<br />
<br />
Replace sharename with the share name specified with VBoxManage, and mountpoint with the path where you want the share to be mounted (e.g. /mnt/share). The usual mount rules apply, that is, create this directory first if it does not exist yet.<br />
<br />
Beyond the standard options supplied by the mount command, the following are available:<br />
iocharset=CHARSET<br />
to set the character set used for I/O operations (utf8 by default) and<br />
convertcp=CHARSET<br />
to specify the character set used for the shared folder name (utf8 by default).<br />
<br />
=== Getting audio to work in the guest machine ===<br />
<br />
In the machine settings, go to the audio tab and select the correct driver according to your sound system (ALSA, OSS or PulseAudio).<br />
<br />
=== Setting up the RAM and Video Memory for the virtual PC ===<br />
<br />
You can change the default values by going to settings -> general.<br />
<br />
=== Setting up CDROM for the Virtual PC ===<br />
<br />
You can change the default values by going to settings -> CD/DVD-ROM.<br />
<br />
Check mount cd/dvd drive and select one of the following options.<br />
<br />
'''Note:''' If no CDROM drive is detected, make sure the HAL daemon is running. To start it, run the following command as root:<br />
<br />
# /etc/rc.d/hal start<br />
<br />
==Converting image formats==<br />
<br />
The <code>qemu-img</code> program can be used to convert images from one format to another, or add compression or encryption to an image. <br />
<br />
# pacman -S qemu<br />
<br />
=== Converting from QEMU images ===<br />
<br />
To convert a QEMU image for use with VirtualBox, first convert it to ''raw'' format, then use VirtualBox's conversion utility to convert and compact it in its native format.<br />
<br />
$ qemu-img convert -O raw test.qcow2 test.raw<br />
$ VBoxManage modifyvdi /full/path/to/test.vdi compact<br />
<br />
=== Converting from VMware images ===<br />
Do <br />
<br />
$ qemu-img convert image.vmdk image.bin<br />
$ VBoxManage convertdd image.bin image.vdi<br />
<br />
This may not be needed anymore with recent virtualbox versions (to be confirmed)<br />
<br />
== Maintenance ==<br />
<br />
=== Rebuild the vboxdrv Module ===<br />
Note that any time your kernel version changes (due to upgrade, recompile, etc.) you must also rebuild the VirtualBox kernel. To do this, on versions earlier than 2.1, run the following command:<br />
# vbox_build_module<br />
This binary will be located in one of the following locations: <tt>/sbin</tt>, <tt>/bin</tt>, or <tt>/usr/bin</tt>.<br />
<br />
On versions 2.1+, update the kernel module by running the following command:<br />
# /etc/rc.d/rc.vboxdrv setup<br />
<br />
After rebuilding the module, don't forget to load it with '''<code>modprobe vboxdrv</code>'''<br />
<br />
=== Compact a Disk Image ===<br />
See [http://my.opera.com/locksley90/blog/2008/06/01/how-to-compact-a-virtualbox-virtual-disk-image-vdi How to compact a VirtualBox virtual disk image (VDI)]<br />
<br />
=== Windows Xp and Nokia phones ===<br />
To get working Windows XP and Nokia phones with Pc Suite mode, Virtualbox needs two simple steps:<br />
<br />
1) adding a rule to udev with /etc/udev/rules.d/40-permissions.rules <br />
ATTRS{idVendor}==”0403″, ATTRS{idProduct}==”6001″, \<br />
GROUP="usbfs", MODE=”0660″, GROUP=”dialout”<br />
LABEL=”usb_serial_end”<br />
c/udev/rules.d/40-permissions.rules" with this line:<br />
<br />
2) create the group usbfs and add its user to it<br />
<br />
== External Resources ==<br />
* [http://download.virtualbox.org/virtualbox/2.0.6/UserManual.pdf VirtualBox 2.0.6 User Manual]</div>Daxhttps://wiki.archlinux.org/index.php?title=Hardware_Diagnostics_(Italiano)&diff=43183Hardware Diagnostics (Italiano)2008-06-17T10:46:58Z<p>Dax: /* Frontend */</p>
<hr />
<div>[[Category: Hardware (italiano)]]<br />
[[Category: Amministrazione del sistema (italiano)]]<br />
==Introduzione==<br />
<br />
Tra i pacchetti adottabili sulla propria macchina sicuramente non possono mancare quelli relativi alla diagnostica del proprio hardware, per una semplice ragione: se qualche scheda inizia a comportarsi male si è in grado di intervenire tempestivamente.<br />
<br />
Possiamo distinguere e definire due categorie di programmi, per lo meno relativi al contesto in cui siamo, ossia: i programmi agenti e i frontend.<br />
I programmi agenti li consideriamo quella classe di programmi che lavora a basso livello e leggono dall'hardware direttamente.<br />
I frontend sono semplici interfacce fornite di una gui che semplificano l'uso agendo ad alto livello.<br />
<br />
Iniziamo con i programmi agenti.<br />
<br />
==Programmi Agenti==<br />
<br />
===Temperature=== <br />
<br />
Cominciamo dalle temperature: <br />
lm_sensors configurazione:<br />
pacman -S lm_sensors <br />
<br />
sensors-detect (parte il tutorial)<br />
[..]<br />
Seguiamo le domande selezionando tra tutto quello che lo script ci propone ciò che serve alla nostra macchina, fino a giungere al riepilogo: <br />
Now follows a summary of the probes I have just done. <br />
Just press ENTER to continue: <br />
continuo. <br />
in fine:<br />
Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes <br />
<br />
Ora controlliamo che tutto funzioni.<br />
Da root digitare:<br />
modprobe i2c-i801 modprobe eeprom modprobe w83627ehf sensors<br />
<br />
Con l’ultima riga dovremmo avere l’output del programma. Se tutto va bene inseriamo i moduli nell’array MODULES del file /etc/rc.conf .<br />
Ecco il mio array:<br />
MODULES=(8139too mii i2c-i801 eeprom w83627ehf).<br />
<br />
===Pulsanti di Alimentazione===<br />
<br />
pacman -S acpid <br />
migliora la gestione dei pulsanti di accensione del computer.<br />
Se premuto più volte lo stesso, la macchina verrà spenta in modo regolare. <br />
Per il suo funzionamento sarà necessario inserire il denome @acpid in /etc/rc.conf<br />
(consiglio: @ da background). <br />
Dentro /proc/acpi trovate delle statistiche sull’utilizzo della macchina, sono molto utili<br />
<br />
===Ram=== <br />
<br />
Cosa importante è il memtest, ossia un’immagine da boot per avviare un test sulla ram.<br />
pacman -S memtest86+ <br />
<br />
Per il suo funzionamento sarà necessario inserire in /boot/grub/menu.lst queste righe:<br />
<br />
1. Memtest <br />
title Memtest86+ [/boot/memtest86+/memtest.bin]<br />
root (hd0,0) kernel /boot/memtest86+/memtest.bin<br />
<br />
Io uso grub. Se usate lilo dovete editare il file lilo.conf . <br />
<br />
<br />
===Hard Disk ===<br />
<br />
Per l’hd sarà molto utile il supporto S.M.A.R.T. Prima di tutto va abilitato da bios, potrà tenere sotto controllo lo stato dei dischi se gestito da un programma. <br />
Può mostrarsi vitale in certi casi.<br />
pacman -S smartmontools <br />
Per il suo funzionamento sarà necessario inserire il demone in /etc/rc.conf:<br />
@smartd <br />
Una volta che smartd è attivo datevi una lettura a [http://guide.debianizzati.org/index.php/Gestire_gli_HD:_stato_di_salute,_badblocks_e_ripristino_dati questo wiki].<br />
<br />
Io ho usato subito:<br />
smartctl -a /dev/hda smartctl -H /dev/hda<br />
<br />
Normalmente il demone è disattivato, anche se viene caricato. <br />
Per attivarlo sarà necessario farlo attraverso il file dei demoni. <br />
Occorre considerare che arch non è del tutto ordinatissima. <br />
Normalmente i files per i daemons di startup li trovi su /etc/conf.d <br />
Ho detto quasi di proposito non è del tutto ordinata perchè quello di smart si trova su /etc/smartd.conf<br />
Qui andremo a decommentare la riga che ci serve. Io ho decommentato questa:<br />
/dev/hda -a -o on -S on -s (S/../.././02|L/../../6/03)<br />
<br />
==Frontend==<br />
<br />
Parliamo ora dei frontend. <br />
Ci sono 3 modi principali per monitorare quanto installato. <br />
La scelta è tra le applet del pannello del vostro DE scelto, '''conky''' oppure '''gkrellm'''.<br />
<br />
'''gkrellm''' offre una discreta disponibilità di servizi integrati ma è espandibile tramite plugins.<br />
<br />
Alcune utili estensioni per gkrellm:<br />
*'''gkhdplop''': mostra l’attività sui dischi tramite effetti grafici, carino da vedere e rende lo stato dei dischi a colpo d’occhio; <br />
*'''gkleds''': rappresentano dei segnalatori di blockNum capsLock e scrollLock attivabili/disattivabili anche tramite click; <br />
*'''gkx86info''': mostra la velocità attuale della cpu; <br />
*'''gkrelltop''': mostra i top-x processi in esecuzione visualizzando il carico di lavoro corrente tramite una barra colorata, molto utile per vedere se usare ad esempio un browser piuttosto che un altro; <br />
*'''gkrellmpager''': visualizza e naviga tra i desktops virtuali; <br />
*'''gkrellmapcupsd''': tiene sottocontrollo lo stato di un gruppo di continuità APC.<br />
<br />
'''conky''' ....<br />
<br />
Per concludere, propongo un esempio di array modules e daemons presenti in /etc/rc.conf che permettono di usufruire di questi servizi:<br />
MODULES=(8139too mii i2c-i801 eeprom w83627ehf capability thermal)<br />
DAEMONS=(@syslog-ng @network !netfs @crond alsamixer @hal @dbus @acpid @smartd @apcupsd @hddtemp)<br />
<br />
end.</div>Daxhttps://wiki.archlinux.org/index.php?title=Hardware_Diagnostics_(Italiano)&diff=43182Hardware Diagnostics (Italiano)2008-06-17T10:45:36Z<p>Dax: /* Frontend */</p>
<hr />
<div>[[Category: Hardware (italiano)]]<br />
[[Category: Amministrazione del sistema (italiano)]]<br />
==Introduzione==<br />
<br />
Tra i pacchetti adottabili sulla propria macchina sicuramente non possono mancare quelli relativi alla diagnostica del proprio hardware, per una semplice ragione: se qualche scheda inizia a comportarsi male si è in grado di intervenire tempestivamente.<br />
<br />
Possiamo distinguere e definire due categorie di programmi, per lo meno relativi al contesto in cui siamo, ossia: i programmi agenti e i frontend.<br />
I programmi agenti li consideriamo quella classe di programmi che lavora a basso livello e leggono dall'hardware direttamente.<br />
I frontend sono semplici interfacce fornite di una gui che semplificano l'uso agendo ad alto livello.<br />
<br />
Iniziamo con i programmi agenti.<br />
<br />
==Programmi Agenti==<br />
<br />
===Temperature=== <br />
<br />
Cominciamo dalle temperature: <br />
lm_sensors configurazione:<br />
pacman -S lm_sensors <br />
<br />
sensors-detect (parte il tutorial)<br />
[..]<br />
Seguiamo le domande selezionando tra tutto quello che lo script ci propone ciò che serve alla nostra macchina, fino a giungere al riepilogo: <br />
Now follows a summary of the probes I have just done. <br />
Just press ENTER to continue: <br />
continuo. <br />
in fine:<br />
Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes <br />
<br />
Ora controlliamo che tutto funzioni.<br />
Da root digitare:<br />
modprobe i2c-i801 modprobe eeprom modprobe w83627ehf sensors<br />
<br />
Con l’ultima riga dovremmo avere l’output del programma. Se tutto va bene inseriamo i moduli nell’array MODULES del file /etc/rc.conf .<br />
Ecco il mio array:<br />
MODULES=(8139too mii i2c-i801 eeprom w83627ehf).<br />
<br />
===Pulsanti di Alimentazione===<br />
<br />
pacman -S acpid <br />
migliora la gestione dei pulsanti di accensione del computer.<br />
Se premuto più volte lo stesso, la macchina verrà spenta in modo regolare. <br />
Per il suo funzionamento sarà necessario inserire il denome @acpid in /etc/rc.conf<br />
(consiglio: @ da background). <br />
Dentro /proc/acpi trovate delle statistiche sull’utilizzo della macchina, sono molto utili<br />
<br />
===Ram=== <br />
<br />
Cosa importante è il memtest, ossia un’immagine da boot per avviare un test sulla ram.<br />
pacman -S memtest86+ <br />
<br />
Per il suo funzionamento sarà necessario inserire in /boot/grub/menu.lst queste righe:<br />
<br />
1. Memtest <br />
title Memtest86+ [/boot/memtest86+/memtest.bin]<br />
root (hd0,0) kernel /boot/memtest86+/memtest.bin<br />
<br />
Io uso grub. Se usate lilo dovete editare il file lilo.conf . <br />
<br />
<br />
===Hard Disk ===<br />
<br />
Per l’hd sarà molto utile il supporto S.M.A.R.T. Prima di tutto va abilitato da bios, potrà tenere sotto controllo lo stato dei dischi se gestito da un programma. <br />
Può mostrarsi vitale in certi casi.<br />
pacman -S smartmontools <br />
Per il suo funzionamento sarà necessario inserire il demone in /etc/rc.conf:<br />
@smartd <br />
Una volta che smartd è attivo datevi una lettura a [http://guide.debianizzati.org/index.php/Gestire_gli_HD:_stato_di_salute,_badblocks_e_ripristino_dati questo wiki].<br />
<br />
Io ho usato subito:<br />
smartctl -a /dev/hda smartctl -H /dev/hda<br />
<br />
Normalmente il demone è disattivato, anche se viene caricato. <br />
Per attivarlo sarà necessario farlo attraverso il file dei demoni. <br />
Occorre considerare che arch non è del tutto ordinatissima. <br />
Normalmente i files per i daemons di startup li trovi su /etc/conf.d <br />
Ho detto quasi di proposito non è del tutto ordinata perchè quello di smart si trova su /etc/smartd.conf<br />
Qui andremo a decommentare la riga che ci serve. Io ho decommentato questa:<br />
/dev/hda -a -o on -S on -s (S/../.././02|L/../../6/03)<br />
<br />
==Frontend==<br />
<br />
Parliamo ora dei frontend. <br />
Ci sono 3 modi principali per monitorare quanto installato. <br />
La scelta è tra le applet del pannello del vostro DE scelto, '''conky''' oppure '''gkrellm'''.<br />
<br />
'''gkrellm''' offre una discreta disponibilità di servizi integrati ma è espandibile tramite plugins.<br />
<br />
Alcune utili estensioni per gkrellm:<br />
*'''gkhdplop''': mostra l’attività sui dischi tramite effetti grafici, carino da vedere e rende lo stato dei dischi a colpo d’occhio; <br />
*'''gkleds''': rappresentano dei segnalatori di blockNum capsLock e scrollLock attivabili/disattivabili anche tramite click; <br />
*'''gkx86info''': mostra la velocità attuale della cpu; <br />
*'''gkrelltop''': mostra i top-x processi in esecuzione visualizzando il carico di lavoro corrente tramite una barra colorata, molto utile per vedere se usare ad esempio un browser piuttosto che un altro; <br />
*'''gkrellmpager''': visualizza e naviga tra i desktops virtuali; <br />
*'''gkrellmapcupsd''': tiene sottocontrollo lo stato del mio gruppo di continuità apc. Essendo hardware non molto diffuso l'ho omesso da questa guida, ne parlerò prossimamente in un altro articolo.<br />
<br />
'''conky''' ....<br />
<br />
Per concludere, propongo un esempio di array modules e daemons presenti in /etc/rc.conf che permettono di usufruire di questi servizi:<br />
MODULES=(8139too mii i2c-i801 eeprom w83627ehf capability thermal)<br />
DAEMONS=(@syslog-ng @network !netfs @crond alsamixer @hal @dbus @acpid @smartd @apcupsd @hddtemp)<br />
<br />
end.</div>Daxhttps://wiki.archlinux.org/index.php?title=Hardware_Diagnostics_(Italiano)&diff=43181Hardware Diagnostics (Italiano)2008-06-17T10:44:14Z<p>Dax: /* Frontend */</p>
<hr />
<div>[[Category: Hardware (italiano)]]<br />
[[Category: Amministrazione del sistema (italiano)]]<br />
==Introduzione==<br />
<br />
Tra i pacchetti adottabili sulla propria macchina sicuramente non possono mancare quelli relativi alla diagnostica del proprio hardware, per una semplice ragione: se qualche scheda inizia a comportarsi male si è in grado di intervenire tempestivamente.<br />
<br />
Possiamo distinguere e definire due categorie di programmi, per lo meno relativi al contesto in cui siamo, ossia: i programmi agenti e i frontend.<br />
I programmi agenti li consideriamo quella classe di programmi che lavora a basso livello e leggono dall'hardware direttamente.<br />
I frontend sono semplici interfacce fornite di una gui che semplificano l'uso agendo ad alto livello.<br />
<br />
Iniziamo con i programmi agenti.<br />
<br />
==Programmi Agenti==<br />
<br />
===Temperature=== <br />
<br />
Cominciamo dalle temperature: <br />
lm_sensors configurazione:<br />
pacman -S lm_sensors <br />
<br />
sensors-detect (parte il tutorial)<br />
[..]<br />
Seguiamo le domande selezionando tra tutto quello che lo script ci propone ciò che serve alla nostra macchina, fino a giungere al riepilogo: <br />
Now follows a summary of the probes I have just done. <br />
Just press ENTER to continue: <br />
continuo. <br />
in fine:<br />
Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes <br />
<br />
Ora controlliamo che tutto funzioni.<br />
Da root digitare:<br />
modprobe i2c-i801 modprobe eeprom modprobe w83627ehf sensors<br />
<br />
Con l’ultima riga dovremmo avere l’output del programma. Se tutto va bene inseriamo i moduli nell’array MODULES del file /etc/rc.conf .<br />
Ecco il mio array:<br />
MODULES=(8139too mii i2c-i801 eeprom w83627ehf).<br />
<br />
===Pulsanti di Alimentazione===<br />
<br />
pacman -S acpid <br />
migliora la gestione dei pulsanti di accensione del computer.<br />
Se premuto più volte lo stesso, la macchina verrà spenta in modo regolare. <br />
Per il suo funzionamento sarà necessario inserire il denome @acpid in /etc/rc.conf<br />
(consiglio: @ da background). <br />
Dentro /proc/acpi trovate delle statistiche sull’utilizzo della macchina, sono molto utili<br />
<br />
===Ram=== <br />
<br />
Cosa importante è il memtest, ossia un’immagine da boot per avviare un test sulla ram.<br />
pacman -S memtest86+ <br />
<br />
Per il suo funzionamento sarà necessario inserire in /boot/grub/menu.lst queste righe:<br />
<br />
1. Memtest <br />
title Memtest86+ [/boot/memtest86+/memtest.bin]<br />
root (hd0,0) kernel /boot/memtest86+/memtest.bin<br />
<br />
Io uso grub. Se usate lilo dovete editare il file lilo.conf . <br />
<br />
<br />
===Hard Disk ===<br />
<br />
Per l’hd sarà molto utile il supporto S.M.A.R.T. Prima di tutto va abilitato da bios, potrà tenere sotto controllo lo stato dei dischi se gestito da un programma. <br />
Può mostrarsi vitale in certi casi.<br />
pacman -S smartmontools <br />
Per il suo funzionamento sarà necessario inserire il demone in /etc/rc.conf:<br />
@smartd <br />
Una volta che smartd è attivo datevi una lettura a [http://guide.debianizzati.org/index.php/Gestire_gli_HD:_stato_di_salute,_badblocks_e_ripristino_dati questo wiki].<br />
<br />
Io ho usato subito:<br />
smartctl -a /dev/hda smartctl -H /dev/hda<br />
<br />
Normalmente il demone è disattivato, anche se viene caricato. <br />
Per attivarlo sarà necessario farlo attraverso il file dei demoni. <br />
Occorre considerare che arch non è del tutto ordinatissima. <br />
Normalmente i files per i daemons di startup li trovi su /etc/conf.d <br />
Ho detto quasi di proposito non è del tutto ordinata perchè quello di smart si trova su /etc/smartd.conf<br />
Qui andremo a decommentare la riga che ci serve. Io ho decommentato questa:<br />
/dev/hda -a -o on -S on -s (S/../.././02|L/../../6/03)<br />
<br />
==Frontend==<br />
<br />
Parliamo ora dei frontend. <br />
Ci sono 3 modi principali per monitorare quanto installato. <br />
La scelta è tra le applet del pannello del vostro DE scelto, '''conky''' oppure '''gkrellm'''.<br />
<br />
'''gkrellm''' offre una discreta disponibilità di servizi integrati ma è espandibile tramite plugins.<br />
C’è da dire che tra i servizi di base c’è il misuratore della temperatura della gpu ma ho letto che funziona solo con certe schede nvidia, da me funziona quindi posso ritenermi fortunato.<br />
<br />
Alcune utili estensioni per gkrellm:<br />
*'''gkhdplop''': mostra l’attività sui dischi tramite effetti grafici, carino da vedere e rende lo stato dei dischi a colpo d’occhio; <br />
*'''gkleds''': rappresentano dei segnalatori di blockNum capsLock e scrollLock attivabili/disattivabili anche tramite click; <br />
*'''gkx86info''': mostra la velocità attuale della cpu; <br />
*'''gkrelltop''': mostra i top-x processi in esecuzione visualizzando il carico di lavoro corrente tramite una barra colorata, molto utile per vedere se usare ad esempio un browser piuttosto che un altro; <br />
*'''gkrellmpager''': visualizza e naviga tra i desktops virtuali; <br />
*'''gkrellmapcupsd''': tiene sottocontrollo lo stato del mio gruppo di continuità apc. Essendo hardware non molto diffuso l'ho omesso da questa guida, ne parlerò prossimamente in un altro articolo.<br />
<br />
'''conky''' ....<br />
<br />
Per concludere, propongo un esempio di array modules e daemons presenti in /etc/rc.conf che permettono di usufruire di questi servizi:<br />
MODULES=(8139too mii i2c-i801 eeprom w83627ehf capability thermal)<br />
DAEMONS=(@syslog-ng @network !netfs @crond alsamixer @hal @dbus @acpid @smartd @apcupsd @hddtemp)<br />
<br />
end.</div>Daxhttps://wiki.archlinux.org/index.php?title=Hardware_Diagnostics_(Italiano)&diff=43180Hardware Diagnostics (Italiano)2008-06-17T10:42:51Z<p>Dax: /* Frontend */</p>
<hr />
<div>[[Category: Hardware (italiano)]]<br />
[[Category: Amministrazione del sistema (italiano)]]<br />
==Introduzione==<br />
<br />
Tra i pacchetti adottabili sulla propria macchina sicuramente non possono mancare quelli relativi alla diagnostica del proprio hardware, per una semplice ragione: se qualche scheda inizia a comportarsi male si è in grado di intervenire tempestivamente.<br />
<br />
Possiamo distinguere e definire due categorie di programmi, per lo meno relativi al contesto in cui siamo, ossia: i programmi agenti e i frontend.<br />
I programmi agenti li consideriamo quella classe di programmi che lavora a basso livello e leggono dall'hardware direttamente.<br />
I frontend sono semplici interfacce fornite di una gui che semplificano l'uso agendo ad alto livello.<br />
<br />
Iniziamo con i programmi agenti.<br />
<br />
==Programmi Agenti==<br />
<br />
===Temperature=== <br />
<br />
Cominciamo dalle temperature: <br />
lm_sensors configurazione:<br />
pacman -S lm_sensors <br />
<br />
sensors-detect (parte il tutorial)<br />
[..]<br />
Seguiamo le domande selezionando tra tutto quello che lo script ci propone ciò che serve alla nostra macchina, fino a giungere al riepilogo: <br />
Now follows a summary of the probes I have just done. <br />
Just press ENTER to continue: <br />
continuo. <br />
in fine:<br />
Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes <br />
<br />
Ora controlliamo che tutto funzioni.<br />
Da root digitare:<br />
modprobe i2c-i801 modprobe eeprom modprobe w83627ehf sensors<br />
<br />
Con l’ultima riga dovremmo avere l’output del programma. Se tutto va bene inseriamo i moduli nell’array MODULES del file /etc/rc.conf .<br />
Ecco il mio array:<br />
MODULES=(8139too mii i2c-i801 eeprom w83627ehf).<br />
<br />
===Pulsanti di Alimentazione===<br />
<br />
pacman -S acpid <br />
migliora la gestione dei pulsanti di accensione del computer.<br />
Se premuto più volte lo stesso, la macchina verrà spenta in modo regolare. <br />
Per il suo funzionamento sarà necessario inserire il denome @acpid in /etc/rc.conf<br />
(consiglio: @ da background). <br />
Dentro /proc/acpi trovate delle statistiche sull’utilizzo della macchina, sono molto utili<br />
<br />
===Ram=== <br />
<br />
Cosa importante è il memtest, ossia un’immagine da boot per avviare un test sulla ram.<br />
pacman -S memtest86+ <br />
<br />
Per il suo funzionamento sarà necessario inserire in /boot/grub/menu.lst queste righe:<br />
<br />
1. Memtest <br />
title Memtest86+ [/boot/memtest86+/memtest.bin]<br />
root (hd0,0) kernel /boot/memtest86+/memtest.bin<br />
<br />
Io uso grub. Se usate lilo dovete editare il file lilo.conf . <br />
<br />
<br />
===Hard Disk ===<br />
<br />
Per l’hd sarà molto utile il supporto S.M.A.R.T. Prima di tutto va abilitato da bios, potrà tenere sotto controllo lo stato dei dischi se gestito da un programma. <br />
Può mostrarsi vitale in certi casi.<br />
pacman -S smartmontools <br />
Per il suo funzionamento sarà necessario inserire il demone in /etc/rc.conf:<br />
@smartd <br />
Una volta che smartd è attivo datevi una lettura a [http://guide.debianizzati.org/index.php/Gestire_gli_HD:_stato_di_salute,_badblocks_e_ripristino_dati questo wiki].<br />
<br />
Io ho usato subito:<br />
smartctl -a /dev/hda smartctl -H /dev/hda<br />
<br />
Normalmente il demone è disattivato, anche se viene caricato. <br />
Per attivarlo sarà necessario farlo attraverso il file dei demoni. <br />
Occorre considerare che arch non è del tutto ordinatissima. <br />
Normalmente i files per i daemons di startup li trovi su /etc/conf.d <br />
Ho detto quasi di proposito non è del tutto ordinata perchè quello di smart si trova su /etc/smartd.conf<br />
Qui andremo a decommentare la riga che ci serve. Io ho decommentato questa:<br />
/dev/hda -a -o on -S on -s (S/../.././02|L/../../6/03)<br />
<br />
==Frontend==<br />
<br />
Parliamo ora dei frontend. <br />
Ci sono 3 modi principali per monitorare quanto installato. <br />
La scelta è tra le applet del pannello del vostro DE scelto, '''conky''' oppure '''gkrellm'''.<br />
<br />
'''gkrellm''' offre una discreta disponibilità di servizi integrati ma è espandibile tramite plugins.<br />
C’è da dire che tra i servizi di base c’è il misuratore della temperatura della gpu ma ho letto che funziona solo con certe schede nvidia, da me funziona quindi posso ritenermi fortunato.<br />
<br />
Alcune utili estensioni per gkrellm:<br />
*'''gkhdplop''': mostra l’attività sui dischi tramite effetti grafici, carino da vedere e rende lo stato dei dischi a colpo d’occhio; <br />
*'''gkleds''': rappresentano dei segnalatori di blockNum capsLock e scrollLock attivabili/disattivabili anche tramite click; <br />
*'''gkx86info''': mostra la velocità attuale della cpu; <br />
*'''gkrelltop''': mostra i top-x processi in esecuzione visualizzando il carico di lavoro corrente tramite una barra colorata, molto utile per vedere se usare ad esempio un browser piuttosto che un altro; <br />
*'''gkrellmpager''': visualizza e naviga tra i desktops virtuali; <br />
*'''gkrellmapcupsd''': tiene sottocontrollo lo stato del mio gruppo di continuità apc. Essendo hardware non molto diffuso l'ho omesso da questa guida, ne parlerò prossimamente in un altro articolo.<br />
<br />
Per concludere, propongo un esempio di array modules e daemons presenti in /etc/rc.conf che permettono di usufruire di questi servizi:<br />
MODULES=(8139too mii i2c-i801 eeprom w83627ehf capability thermal)<br />
DAEMONS=(@syslog-ng @network !netfs @crond alsamixer @hal @dbus @acpid @smartd @apcupsd @hddtemp)<br />
<br />
end.</div>Daxhttps://wiki.archlinux.org/index.php?title=Hardware_Diagnostics_(Italiano)&diff=43179Hardware Diagnostics (Italiano)2008-06-17T10:39:36Z<p>Dax: /* Frontend */</p>
<hr />
<div>[[Category: Hardware (italiano)]]<br />
[[Category: Amministrazione del sistema (italiano)]]<br />
==Introduzione==<br />
<br />
Tra i pacchetti adottabili sulla propria macchina sicuramente non possono mancare quelli relativi alla diagnostica del proprio hardware, per una semplice ragione: se qualche scheda inizia a comportarsi male si è in grado di intervenire tempestivamente.<br />
<br />
Possiamo distinguere e definire due categorie di programmi, per lo meno relativi al contesto in cui siamo, ossia: i programmi agenti e i frontend.<br />
I programmi agenti li consideriamo quella classe di programmi che lavora a basso livello e leggono dall'hardware direttamente.<br />
I frontend sono semplici interfacce fornite di una gui che semplificano l'uso agendo ad alto livello.<br />
<br />
Iniziamo con i programmi agenti.<br />
<br />
==Programmi Agenti==<br />
<br />
===Temperature=== <br />
<br />
Cominciamo dalle temperature: <br />
lm_sensors configurazione:<br />
pacman -S lm_sensors <br />
<br />
sensors-detect (parte il tutorial)<br />
[..]<br />
Seguiamo le domande selezionando tra tutto quello che lo script ci propone ciò che serve alla nostra macchina, fino a giungere al riepilogo: <br />
Now follows a summary of the probes I have just done. <br />
Just press ENTER to continue: <br />
continuo. <br />
in fine:<br />
Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes <br />
<br />
Ora controlliamo che tutto funzioni.<br />
Da root digitare:<br />
modprobe i2c-i801 modprobe eeprom modprobe w83627ehf sensors<br />
<br />
Con l’ultima riga dovremmo avere l’output del programma. Se tutto va bene inseriamo i moduli nell’array MODULES del file /etc/rc.conf .<br />
Ecco il mio array:<br />
MODULES=(8139too mii i2c-i801 eeprom w83627ehf).<br />
<br />
===Pulsanti di Alimentazione===<br />
<br />
pacman -S acpid <br />
migliora la gestione dei pulsanti di accensione del computer.<br />
Se premuto più volte lo stesso, la macchina verrà spenta in modo regolare. <br />
Per il suo funzionamento sarà necessario inserire il denome @acpid in /etc/rc.conf<br />
(consiglio: @ da background). <br />
Dentro /proc/acpi trovate delle statistiche sull’utilizzo della macchina, sono molto utili<br />
<br />
===Ram=== <br />
<br />
Cosa importante è il memtest, ossia un’immagine da boot per avviare un test sulla ram.<br />
pacman -S memtest86+ <br />
<br />
Per il suo funzionamento sarà necessario inserire in /boot/grub/menu.lst queste righe:<br />
<br />
1. Memtest <br />
title Memtest86+ [/boot/memtest86+/memtest.bin]<br />
root (hd0,0) kernel /boot/memtest86+/memtest.bin<br />
<br />
Io uso grub. Se usate lilo dovete editare il file lilo.conf . <br />
<br />
<br />
===Hard Disk ===<br />
<br />
Per l’hd sarà molto utile il supporto S.M.A.R.T. Prima di tutto va abilitato da bios, potrà tenere sotto controllo lo stato dei dischi se gestito da un programma. <br />
Può mostrarsi vitale in certi casi.<br />
pacman -S smartmontools <br />
Per il suo funzionamento sarà necessario inserire il demone in /etc/rc.conf:<br />
@smartd <br />
Una volta che smartd è attivo datevi una lettura a [http://guide.debianizzati.org/index.php/Gestire_gli_HD:_stato_di_salute,_badblocks_e_ripristino_dati questo wiki].<br />
<br />
Io ho usato subito:<br />
smartctl -a /dev/hda smartctl -H /dev/hda<br />
<br />
Normalmente il demone è disattivato, anche se viene caricato. <br />
Per attivarlo sarà necessario farlo attraverso il file dei demoni. <br />
Occorre considerare che arch non è del tutto ordinatissima. <br />
Normalmente i files per i daemons di startup li trovi su /etc/conf.d <br />
Ho detto quasi di proposito non è del tutto ordinata perchè quello di smart si trova su /etc/smartd.conf<br />
Qui andremo a decommentare la riga che ci serve. Io ho decommentato questa:<br />
/dev/hda -a -o on -S on -s (S/../.././02|L/../../6/03)<br />
<br />
==Frontend==<br />
<br />
Parliamo ora dei frontend. <br />
Ci sono 3 modi principali per monitorare quanto installato. <br />
La scelta è tra le applet del pannello del vostro DE scelto, '''conky''' oppure '''gkrellm'''.<br />
<br />
Personalmente io ho preferito '''gkrellm''' per una semplice ragione: è leggero ed è totalmente trasparente al mio sistema. <br />
Onestamente mi seccava molto l'idea di dover "far spazio sulla cpu" per applicazioni pesanti e conky con il suo triplebuffer per eliminare lo sfarfallio, e le trasparenze e altre particolarità belle da vedere ma poco utili al fine, costituiva una fetta di cpu che in rari casi torna utile utilizzare. <br />
Senza farla lunga, gkrellm è sempre li al lavoro e non lo si sente per nulla.<br />
<br />
'''gkrellm''' offre una discreta disponibilità di servizi integrati ma è espandibile tramite plugins.<br />
C’è da dire che tra i servizi di base c’è il misuratore della temperatura della gpu ma ho letto che funziona solo con certe schede nvidia, da me funziona quindi posso ritenermi fortunato.<br />
<br />
Alcune utili estensioni per gkrellm:<br />
*'''gkhdplop''': mostra l’attività sui dischi tramite effetti grafici, carino da vedere e rende lo stato dei dischi a colpo d’occhio; <br />
*'''gkleds''': rappresentano dei segnalatori di blockNum capsLock e scrollLock attivabili/disattivabili anche tramite click; <br />
*'''gkx86info''': mostra la velocità attuale della cpu; <br />
*'''gkrelltop''': mostra i top-x processi in esecuzione visualizzando il carico di lavoro corrente tramite una barra colorata, molto utile per vedere se usare ad esempio un browser piuttosto che un altro; <br />
*'''gkrellmpager''': visualizza e naviga tra i desktops virtuali; <br />
*'''gkrellmapcupsd''': tiene sottocontrollo lo stato del mio gruppo di continuità apc. Essendo hardware non molto diffuso l'ho omesso da questa guida, ne parlerò prossimamente in un altro articolo.<br />
<br />
Per concludere, propongo un esempio di array modules e daemons presenti in /etc/rc.conf che permettono di usufruire di questi servizi:<br />
MODULES=(8139too mii i2c-i801 eeprom w83627ehf capability thermal)<br />
DAEMONS=(@syslog-ng @network !netfs @crond alsamixer @hal @dbus @acpid @smartd @apcupsd @hddtemp)<br />
<br />
end.</div>Daxhttps://wiki.archlinux.org/index.php?title=Hardware_Diagnostics_(Italiano)&diff=43178Hardware Diagnostics (Italiano)2008-06-17T10:38:38Z<p>Dax: /* Frontend */</p>
<hr />
<div>[[Category: Hardware (italiano)]]<br />
[[Category: Amministrazione del sistema (italiano)]]<br />
==Introduzione==<br />
<br />
Tra i pacchetti adottabili sulla propria macchina sicuramente non possono mancare quelli relativi alla diagnostica del proprio hardware, per una semplice ragione: se qualche scheda inizia a comportarsi male si è in grado di intervenire tempestivamente.<br />
<br />
Possiamo distinguere e definire due categorie di programmi, per lo meno relativi al contesto in cui siamo, ossia: i programmi agenti e i frontend.<br />
I programmi agenti li consideriamo quella classe di programmi che lavora a basso livello e leggono dall'hardware direttamente.<br />
I frontend sono semplici interfacce fornite di una gui che semplificano l'uso agendo ad alto livello.<br />
<br />
Iniziamo con i programmi agenti.<br />
<br />
==Programmi Agenti==<br />
<br />
===Temperature=== <br />
<br />
Cominciamo dalle temperature: <br />
lm_sensors configurazione:<br />
pacman -S lm_sensors <br />
<br />
sensors-detect (parte il tutorial)<br />
[..]<br />
Seguiamo le domande selezionando tra tutto quello che lo script ci propone ciò che serve alla nostra macchina, fino a giungere al riepilogo: <br />
Now follows a summary of the probes I have just done. <br />
Just press ENTER to continue: <br />
continuo. <br />
in fine:<br />
Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes <br />
<br />
Ora controlliamo che tutto funzioni.<br />
Da root digitare:<br />
modprobe i2c-i801 modprobe eeprom modprobe w83627ehf sensors<br />
<br />
Con l’ultima riga dovremmo avere l’output del programma. Se tutto va bene inseriamo i moduli nell’array MODULES del file /etc/rc.conf .<br />
Ecco il mio array:<br />
MODULES=(8139too mii i2c-i801 eeprom w83627ehf).<br />
<br />
===Pulsanti di Alimentazione===<br />
<br />
pacman -S acpid <br />
migliora la gestione dei pulsanti di accensione del computer.<br />
Se premuto più volte lo stesso, la macchina verrà spenta in modo regolare. <br />
Per il suo funzionamento sarà necessario inserire il denome @acpid in /etc/rc.conf<br />
(consiglio: @ da background). <br />
Dentro /proc/acpi trovate delle statistiche sull’utilizzo della macchina, sono molto utili<br />
<br />
===Ram=== <br />
<br />
Cosa importante è il memtest, ossia un’immagine da boot per avviare un test sulla ram.<br />
pacman -S memtest86+ <br />
<br />
Per il suo funzionamento sarà necessario inserire in /boot/grub/menu.lst queste righe:<br />
<br />
1. Memtest <br />
title Memtest86+ [/boot/memtest86+/memtest.bin]<br />
root (hd0,0) kernel /boot/memtest86+/memtest.bin<br />
<br />
Io uso grub. Se usate lilo dovete editare il file lilo.conf . <br />
<br />
<br />
===Hard Disk ===<br />
<br />
Per l’hd sarà molto utile il supporto S.M.A.R.T. Prima di tutto va abilitato da bios, potrà tenere sotto controllo lo stato dei dischi se gestito da un programma. <br />
Può mostrarsi vitale in certi casi.<br />
pacman -S smartmontools <br />
Per il suo funzionamento sarà necessario inserire il demone in /etc/rc.conf:<br />
@smartd <br />
Una volta che smartd è attivo datevi una lettura a [http://guide.debianizzati.org/index.php/Gestire_gli_HD:_stato_di_salute,_badblocks_e_ripristino_dati questo wiki].<br />
<br />
Io ho usato subito:<br />
smartctl -a /dev/hda smartctl -H /dev/hda<br />
<br />
Normalmente il demone è disattivato, anche se viene caricato. <br />
Per attivarlo sarà necessario farlo attraverso il file dei demoni. <br />
Occorre considerare che arch non è del tutto ordinatissima. <br />
Normalmente i files per i daemons di startup li trovi su /etc/conf.d <br />
Ho detto quasi di proposito non è del tutto ordinata perchè quello di smart si trova su /etc/smartd.conf<br />
Qui andremo a decommentare la riga che ci serve. Io ho decommentato questa:<br />
/dev/hda -a -o on -S on -s (S/../.././02|L/../../6/03)<br />
<br />
==Frontend==<br />
<br />
Parliamo ora dei frontend. <br />
Ci sono 3 modi principali per monitorare quanto installato. <br />
La scelta è tra le applet del pannello del vostro DE scelto, '''conky''' oppure '''gkrellm'''.<br />
<br />
Personalmente io ho preferito '''gkrellm''' per una semplice ragione: è leggero ed è totalmente trasparente al mio sistema. <br />
Onestamente mi seccava molto l'idea di dover "far spazio sulla cpu" per applicazioni pesanti e conky con il suo triplebuffer per eliminare lo sfarfallio, e le trasparenze e altre particolarità belle da vedere ma poco utili al fine, costituiva una fetta di cpu che in rari casi torna utile utilizzare. <br />
Senza farla lunga, gkrellm è sempre li al lavoro e non lo si sente per nulla.<br />
<br />
'''gkrellm''' offre una discreta disponibilità di servizi integrati ma è espandibile tramite plugins.<br />
C’è da dire che tra i servizi di base c’è il misuratore della temperatura della gpu ma ho letto che funziona solo con certe schede nvidia, da me funziona quindi posso ritenermi fortunato.<br />
<br />
Alcune utili estensioni per gkrellm:<br />
*'''gkhdplop''': mostra l’attività sui dischi tramite effetti grafici, carino da vedere e rende lo stato dei dischi a colpo d’occhio; <br />
*'''gkleds''': rappresentano dei segnalatori di blockNum capsLock e scrollLock attivabili/disattivabili anche tramite click; <br />
*'''gkx86info''': mostra la velocità attuale della cpu; <br />
*'''gkrelltop''': mostra i top-x processi in esecuzione visualizzando il carico di lavoro corrente tramite una barra colorata, molto utile per vedere se usare ad esempio un browser piuttosto che un altro; <br />
*'''gkrellmpager''': visualizza e naviga tra i desktops virtuali; <br />
*'''gkrellmapcupsd''': tiene sottocontrollo lo stato del mio gruppo di continuità apc. Essendo hardware non molto diffuso l'ho omesso da questa guida, ne parlerò prossimamente in un altro articolo.<br />
<br />
Per concludere, incollo i miei array modules e daemons presenti in /etc/rc.conf che mi permettono di usufruire di questi servizi:<br />
MODULES=(8139too mii i2c-i801 eeprom w83627ehf capability thermal)<br />
DAEMONS=(@syslog-ng @network !netfs @crond alsamixer @hal @dbus @acpid @smartd @apcupsd @hddtemp)<br />
<br />
end.</div>Dax