https://wiki.archlinux.org/api.php?action=feedcontributions&user=Brendan&feedformat=atomArchWiki - User contributions [en]2024-03-29T08:41:11ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Openbox&diff=114453Openbox2010-08-20T09:14:09Z<p>Brendan: /* Desktop wallpaper */</p>
<hr />
<div>[[Category:Stacking WMs (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|Openbox}}<br />
<br />
Openbox is a lightweight and highly configurable window manager with extensive standards support. Its features are well-documented at the [http://openbox.org/ official website]. This article will pertain to running Openbox under Arch Linux.<br />
<br />
== Installation ==<br />
<br />
Openbox is available from the standard repositories:<br />
# pacman -S openbox<br />
<br />
Once installed, pacman will direct you to copy the default {{Filename|menu.xml}} and {{Filename|rc.xml}} configuration files to {{Filename|~/.config/openbox}}, for example:<br />
<br />
{{Note | Do this as a regular user, not as root.}}<br />
<br />
$ mkdir -p ~/.config/openbox<br />
$ cp /etc/xdg/openbox/rc.xml ~/.config/openbox<br />
$ cp /etc/xdg/openbox/menu.xml ~/.config/openbox<br />
$ cp /etc/xdg/openbox/autostart.sh ~/.config/openbox<br />
<br />
{{Filename|rc.xml}} is the core configuration file for Openbox. It is used to manage keyboard shortcuts, themes, virtual desktops and other features.<br />
<br />
{{Filename|menu.xml}} controls the Openbox application menu that appears when you click on your desktop. The default items are pretty sparse, but it's very easy to modify the menu structure to suit your needs. See the menu section below for more details, or visit the [http://icculus.org/openbox/ Openbox website].<br />
<br />
{{Filename|autostart.sh}} The default autostart file sets up a number of things for you. You can use this script to launch a panel, to set your desktop wallpaper, or anything else. Visit the [http://openbox.org/wiki/Help:Autostart Openbox Wiki website].<br />
<br />
== Stand-alone window manager ==<br />
<br />
To run Openbox on its own, simply add the following to the bottom of {{Filename|~/.xinitrc}}:<br />
exec openbox-session<br />
<br />
If you have used another window manager before, such as Xfwm, and Openbox won't start after logging out of X, try moving the autostart folder:<br />
mv ~/.config/autostart ~/.config/autostart-bak<br />
<br />
Using D-Bus/HAL or similar, use this instead:<br />
exec ck-launch-session openbox-session<br />
<br />
If you also use '''polkit''' and '''D-Bus''' (e.g. for automount drivers in nautilus from Gnome 2.28 / 2.30) use:<br />
exec ck-launch-session dbus-launch openbox-session<br />
<br />
{{Note | [http://www.archlinux.org/packages/extra/i686/pyxdg/ pyxdg] is required for Openbox's xdg-autostart}}<br />
<br />
== Window manager for Desktop Environments ==<br />
<br />
=== GNOME ===<br />
==== GNOME 2.26 ====<br />
'''''Follow the next guide for GNOME 2.24. If it fails try this:'''''<br />
<br />
If after installing openbox and trying to log into the 'Gnome/openbox' session but it always fails then you can do the following as one way to achieve running openbox as your window manager every time you log into the 'Gnome' session from your login manager (xdm, gdm, kdm, entrance, slim, etc.)<br />
<br />
#Log into your Gnome only session (which would still be using metacity as its window manager) if you aren't already.<br />
#Install openbox if you have not done so already<br />
#Explore your menus to ''System &rarr; Preferences &rarr; Startup Applications'' (possibly named 'Session' for older versions of Gnome)<br />
#Open Startup Application, select '+ Add' and enter the text as seen in the box below whilst omitting the text behind the #.<br />
#Now hit the 'Add' button for that data entry window and make sure the checkbox beside your new entry is selected.<br />
#Thus log out of your gnome session and log back in and you should be running openbox as your window manager.<br />
#Enjoy!<br />
<br />
Name: Openbox Windox Manager # Can be changed<br />
Command: openbox --replace # Text should not be removed from this line, but possibly added to it<br />
Comment: Replaces metacity with openbox # Can be changed<br />
<br />
This creates an entry in a startup list which is executed by gnome everytime that particular user's gnome-session is started.<br />
<br />
==== GNOME 2.24 ====<br />
First, create {{Filename|/usr/share/applications/openbox.desktop}} containing the following:<br />
[Desktop Entry]<br />
Type=Application<br />
Encoding=UTF-8<br />
Name=OpenBox<br />
Exec=openbox<br />
NoDisplay=true<br />
# name of loadable control center module<br />
X-GNOME-WMSettingsModule=openbox<br />
# name we put on the WM spec check window<br />
X-GNOME-WMName=OpenBox<br />
Then, in gconf, set {{Codeline|/desktop/gnome/session/required_components/windowmanager}} to {{Codeline|openbox}}:<br />
$ gconftool-2 -s -t string /desktop/gnome/session/required_components/windowmanager openbox<br />
Finally, choose the '''GNOME''' session in the GDM sessions menu.<br />
<br />
==== GNOME 2.22 and previous ====<br />
# If you use GDM, select the "GNOME/Openbox" login option<br />
# If you use {{Codeline|startx}}, add {{Codeline|exec openbox-gnome-session}} to {{Filename|~/.xinitrc}}<br />
# From the shell:<br />
$ xinit /usr/bin/openbox-gnome-session<br />
<br />
=== KDE ===<br />
# If you use KDM, select the "KDE/Openbox" login option<br />
# If you use startx, add {{Codeline|exec openbox-kde-session}} to {{Filename|~/.xinitrc}}<br />
# From the shell:<br />
$ xinit /usr/bin/openbox-kde-session<br />
<br />
=== Xfce4 ===<br />
Log into a normal Xfce4 session. From your terminal of choice, do:<br />
$ killall xfwm4 ; openbox & exit<br />
<br />
This will kill xfwm4, run Openbox, and close the terminal. <br />
<br />
Log out, making sure to check the "Save session for future logins" checkbox. On next login, Xfce4 will use Openbox as its WM. To be able to exit the session using xfce4-session, open your file {{Filename|~/.config/openbox/menu.xml}} (if it isn't there, copy it from {{Filename|/etc/xdg/openbox/menu.xml}}). <br />
<br />
Look for the entry:<br />
<br />
<item label="Exit Openbox"><br />
<action name="Exit"><br />
<prompt>yes</prompt><br />
</action><br />
</item><br />
<br />
and change it to:<br />
<br />
<item label="Exit Openbox"><br />
<action name="Execute"><br />
<prompt>yes</prompt><br />
<command>xfce4-session-logout</command><br />
</action><br />
</item><br />
<br />
Otherwise, using the "Exit" entry of the root-menu will cause Openbox to terminate its execution, leaving you without a window manager.<br />
<br />
If you have an issue changing between virtual desktops with the mouse wheel skipping over virtual desktops, open your {{Filename|~/.config/openbox/rc.xml}} file and move the mouse binds with actions "DesktopPrevious" and "DesktopNext" from the context "Desktop" to the context "Root" (you may need to define the Root context).<br />
<br />
If you want to use the Openbox root-menu instead of Xfce's, you may terminate Xfdesktop by running the following command in a terminal:<br />
$ xfdesktop --quit<br />
<br />
However, Xfdesktop manages the wallpaper and desktop icons, requiring you to use other utilities, such as ROX, for these functions.<br />
<br />
(When terminating Xfdesktop, the above issue with the virtual desktops is no longer a problem.)<br />
<br />
== Preferences ==<br />
<br />
Currently, there are two options for configuring the core Openbox preferences; manually edit the {{Filename|rc.xml}}, or use the ObConf tool.<br />
<br />
=== Manual configuration ===<br />
<br />
To configure Openbox manually, simply edit {{Filename|~/.config/openbox/rc.xml}} with your favorite text editor. The config file provides plenty of comments throughout, and [http://openbox.org/wiki/Configuration full documentation] is available at the official website.<br />
<br />
=== ObConf ===<br />
<br />
[http://icculus.org/openbox/index.php/ObConf:About ObConf] is GUI-based Openbox configuration tool, which can be used to set most preferences including themes, virtual desktops, window properties and desktop margins.<br />
<br />
To install ObConf, run:<br />
# pacman -S obconf<br />
<br />
{{Note | ObConf cannot be used to configure keyboard shortcuts and some other advanced features. For these modifications, you must edit {{Filename|rc.xml}} manually (see above). Other option is [http://code.google.com/p/obkey/ ObKey] application (available in [[AUR]]).}}<br />
<br />
=== Application configuration ===<br />
<br />
Openbox features per-application settings, allowing you to define rules for your programs. For example, you can:<br />
* load your web browser on a certain desktop<br />
* load your terminal without a window border<br />
* load your torrent client at a certain position on your screen<br />
<br />
These are defined in {{Filename|~/.config/openbox/rc.xml}}. As you might expect, the instructions are well-documented within the file itself. Full details can also be found here: http://openbox.org/wiki/Help:Applications<br />
<br />
== Menus ==<br />
<br />
The default Openbox menu includes a variety of applications to get you started, but you'll probably want to customize this at some point. There are a number of ways to do so:<br />
<br />
=== Manual configuration ===<br />
<br />
Similar to the {{Filename|rc.xml}} file, you can edit {{Filename|~/.config/openbox/menu.xml}} with your favourite text editor. Although many of the settings are self-explanatory, [http://openbox.org/wiki/Help:Menus full documentation] is available.<br />
<br />
=== MenuMaker ===<br />
<br />
[http://menumaker.sourceforge.net/ MenuMaker] is a powerful tool that creates XML-based menus for a variety of Window Managers, including Openbox. MenuMaker will search your computer for executable programs and create an XML menu based on the results. It can be configured to exclude Legacy X, GNOME, KDE, or Xfce applications if the user desires.<br />
<br />
MenuMaker is available in the community repository:<br />
# pacman -S menumaker<br />
<br />
Once installed, you can generate a complete menu by running:<br />
$ mmaker -v OpenBox3<br />
<br />
By default, MenuMaker will not overwrite an existing menu.xml. To do so, run it with the -f (force) argument:<br />
<br />
$ mmaker -vf OpenBox3<br />
<br />
To see a full list of options, run {{Codeline|mmaker --help}}.<br />
<br />
This will give you a pretty thorough menu. Now you can modify the menu.xml by hand, or simply regenerate the list whenever you install new software.<br />
<br />
=== Obmenu ===<br />
<br />
Obmenu is a GUI-based menu editor for Openbox. For those who don't enjoy editing XML source code, this is probably the best option for you.<br />
<br />
It is available in the community repository:<br />
# pacman -S obmenu<br />
<br />
Once installed, simply run {{Codeline|obmenu}} and add or remove the desired applications.<br />
<br />
==== Obm-xdg ====<br />
<br />
<tt>obm-xdg</tt> is a command-line tool that comes with Obmenu. It can generate a categorized sub-menu of installed GTK/GNOME applications.<br />
<br />
To use obm-xdg, add the following line to {{Filename|~/.config/openbox/menu.xml}}:<br />
<menu execute="obm-xdg" id="xdg-menu" label="xdg"/><br />
<br />
Then run {{Codeline|openbox --reconfigure}} to refresh the Openbox menu. You should now see a sub-menu labeled '''xdg''' in your menu.<br />
<br />
{{Note | If you do not have GNOME installed, then you need to install '''gnome-menus''' package for obm-xdg to work.}}<br />
<br />
=== Python based xdg menu script ===<br />
<br />
This script can be found in Fedora's Openbox package. You will only have to put the script somewhere and add a menu entry.<br />
<br />
Here is my paste: http://pastebin.com/f2f827625<br />
And here is the head: http://cvs.fedoraproject.org/viewvc/devel/openbox/xdg-menu?view=markup<br />
<br />
Download the one you like (maybe you'll prefer the head version of course). You can put the file anywhere, I used ~/Documents/build/xdg-menu (just modify the menu entry later according to YOUR filename/path.)<br />
<br />
Then open your menu.xml with your favourite text editor and add the following entry where you want the new menu (of course, you can modify the label however you want):<br />
<menu id="apps-menu" label="xdgmenu" execute="python /home/shiki/Documents/build/xdg-menu"/><br />
<br />
Save the file, and run: {{Codeline|openbox --reconfigure}}.<br />
<br />
=== Pipe menus ===<br />
<br />
Openbox (and other WMs like WindowMaker and PekWM) allow you to write scripts that dynamically build menus on the fly. Some examples are system monitors, media player controls, and weather forecasts. Many examples can be found on the openbox [http://openbox.org/wiki/Openbox:Pipemenus site].<br />
<br />
Xyne has also created a file browser and brisbin33 has one for scanning for / connecting to wireless hot spots (requires netcfg). The relevant forum posts for these utilities are [http://bbs.archlinux.org/viewtopic.php?id=77197&p=1 here] and [http://bbs.archlinux.org/viewtopic.php?id=78290 here]<br />
<br />
== Startup programs ==<br />
<br />
Openbox features support for running programs at startup. This is provided by the "openbox-session" command.<br />
<br />
There are two ways to enable autostart:<br />
# If you use startx/xinit to log into your X session, edit {{Filename|~/.xinitrc}} and change the line that executes ''openbox'' to execute '''openbox-session''' instead.<br />
# If you log in with GDM/KDM, then select the ''Openbox'' session and it will automatically use autostart.<br />
<br />
Startup programs are managed in {{Filename|~/.config/openbox/autostart.sh}}. Full instructions and best practices for how to do this are available at the [http://openbox.org/wiki/Help:Autostart Openbox website].<br />
<br />
== Themes and appearance ==<br />
<br />
With the exception of the Openbox Themes topic, the following section is intended for users who have configured Openbox to run as a standalone desktop, without the assistance of GNOME, KDE or Xfce.<br />
<br />
=== Openbox themes ===<br />
<br />
Openbox themes control the appearance of window borders, including the titlebar and titlebar buttons. They also determine the appearance of the application menu and on-screen display (OSD). <br />
<br />
Additional themes are available from the standard repositories:<br />
<br />
# pacman -S openbox-themes<br />
<br />
This package is by no means definitive. You can download more themes at websites such as:<br />
*[http://www.box-look.org/index.php?xcontentmode=7402 box-look.org]<br />
*[http://customize.org/browse/tags/openbox customize.org]<br />
*http://www.minuslab.net/themes/<br />
*http://celo.wordpress.com/themes/<br />
*http://vault.openmonkey.com/pages/openbox<br />
*http://hewphoria.com/?p=submission&type=theme&cat=7<br />
<br />
Downloaded themes should be extracted to <tt>~/.themes</tt> and can be installed or selected with the [[Openbox#Preferences|ObConf]] tool.<br />
<br />
Creating new themes is fairly easy and again [http://openbox.org/wiki/Help:Themes well-documented].<br />
<br />
For a GUI theme editor, take a look at [http://xyne.archlinux.ca/info/obtheme ObTheme].<br />
<br />
=== X11 Appearance ===<br />
<br />
If you are running Openbox as a standalone, you will need to configure .Xdefaults file.<br />
Save a copy to ~/.Xdefaults and /home/root/.Xdefaults for windows opened as Root.<br />
<br />
Xdefaults is a user-level configuration dotfile, typically located at ~/.Xdefaults. When present, it is parsed by the xrdb (Xorg resource database) program automatically when Xorg is started, and can be used to set or override preferences for X and X applications. It can do many operations, including:<br />
<br />
- defining terminal colours<br />
- configuring terminal preferences<br />
- setting DPI, antialiasing, hinting and other X font settings<br />
- changing the Xcursor theme<br />
- theming xscreensaver<br />
- altering preferences on low-level X applications (xclock, xpdf, etc.) <br />
<br />
Xdefaults Arch WiKi<br />
http://wiki.archlinux.org/index.php/Xdefaults<br />
<br />
=== X11 Mouse cursors ===<br />
<br />
Extract the desired Xcursor theme to either <tt>/usr/share/icons</tt> (system-wide access) or <tt>~/.icons</tt> (local user access). There are also a limited amount of themes available in the community repository that can be installed using pacman.<br />
<br />
Add this to {{Filename|~/.Xdefaults}}:<br />
Xcursor.theme: [name-of-cursor-theme]<br />
where {{Codeline|[name-of-cursor-theme]}} is the name of the cursor theme directory. For example:<br />
Xcursor.theme: Vanilla-DMZ-AA<br />
To change the size:<br />
Xcursor.size: [size]<br />
Sometimes it is required to symlink the icon directory into each user directory to make the window manager use them:<br />
$ mkdir ~/.icons<br />
$ ln -s /usr/share/icons/[name-of-cursor-theme] ~/.icons/default<br />
<br />
For more information read the Arch WiKi<br />
http://wiki.archlinux.org/index.php/X11_Cursors<br />
<br />
=== GTK Themes ===<br />
<br />
==== GTK2/GTK+ ====<br />
<br />
First, extract the desired theme to <tt>/usr/share/themes</tt> (system-wide access) or <tt>~/.themes</tt> (local user access), then:<br />
<br />
GTK+ themes can be managed easily with the '''[[LXDE | lxappearance]]''', '''gtk-chtheme''', or '''switch2''' utilities. To install, run:<br />
# pacman -S lxappearance<br />
and/or<br />
# pacman -S gtk-chtheme<br />
and/or<br />
# pacman -S gtk-theme-switch2<br />
<br />
Now you can simply run {{Codeline|lxappearance}}, {{Codeline|gtk-chtheme}} or {{Codeline|switch2}} to set the desired theme.<br />
<br />
==== GTK1 ====<br />
For legacy GTK1 themes, install the '''gtk-theme-switch''' package:<br />
# pacman -S gtk-theme-switch<br />
Then run {{Codeline|switch}} to select a desired theme.<br />
<br />
==== GTK fonts ====<br />
<br />
To manually change the type and size of your fonts, add the following to {{Filename|~/.gtkrc.mine}}:<br />
style "user-font"<br />
{<br />
font_name = "[font-name] [size]"<br />
}<br />
widget_class "*" style "user-font"<br />
gtk-font-name = "[font-name] [size]"<br />
<br />
where {{Codeline|[font-name] [size]}} is the desired font and point size. For example:<br />
style "user-font"<br />
{<br />
font_name = "DejaVu Sans 8"<br />
}<br />
widget_class "*" style "user-font"<br />
gtk-font-name = "DejaVu Sans 8"<br />
<br />
Both {{Codeline|font_name}} and {{Codeline|gtk-font-name}} fields are required for backwards compatibility.<br />
<br />
You can also use '''gtk-chtheme''' or '''lxappearance''' to set GTK font settings. Please refer to the above section.<br />
<br />
==== GTK Icons ====<br />
<br />
First, extract the desired icon theme to <tt>/usr/share/icons</tt> (system-wide access) or <tt>~/.icons</tt> (local user access), then:<br />
<br />
Add the following to {{Filename|~/.gtkrc.mine}}: <br />
gtk-icon-theme-name = "[name-of-icon-theme]"<br />
<br />
where {{Codeline|[name-of-icon-theme]}} is the name of the icon theme directory. For example:<br />
gtk-icon-theme-name = "Tango"<br />
<br />
Ensure {{Filename|~/.gtkrc-2.0}} is configured to parse {{Filename|~/.gtkrc.mine}}:<br />
<br />
# ~/.gtkrc-2.0<br />
# -- THEME AUTO-WRITTEN DO NOT EDIT<br />
include "/usr/share/themes/Rezlooks-Gilouche/gtk-2.0/gtkrc"<br />
include "/home/username/.gtkrc.mine"<br />
# -- THEME AUTO-WRITTEN DO NOT EDIT<br />
<br />
You can use '''lxappearance''' to choose GTK icon themes. Please refer to the above section.<br />
<br />
=== Desktop icons ===<br />
Openbox does not provide a means to display icons on the desktop. Xfdesktop, PcmanFM, [http://rox.sourceforge.net ROX], [http://idesk.sourceforge.net iDesk], or even Nautilus (and the gnome-settings-daemon) can provide this function. <br />
<br />
ROX and PCmanFM have the additional advantage of being lightweight file managers.<br />
<br />
=== Desktop wallpaper ===<br />
<br />
Openbox itself does not include a way to change the wallpaper. This can be done easily with programs like [[Feh]] or [[Nitrogen]]. Other options include ImageMagick, hsetroot and xsetbg. Or Pcmanfm and Xfdesktop can do it too.<br />
<br />
You can disable the wallpaper loading in gnome-settings-daemon like this:<br />
$ gconftool-2 --set /apps/gnome_settings_daemon/plugins/background/active --type bool False<br />
<br />
== Recommended programs ==<br />
<br />
There is a [[Lightweight Applications|list of Lightweight Software]] at Arch's wiki; most of it nicely fits with Openbox.<br />
<br />
=== Login managers ===<br />
<br />
[http://slim.berlios.de/ SLiM] provides a lightweight and elegant graphical login solution for standalone Openbox configurations. Refer to Arch's [[SLiM]] wiki for detailed instructions.<br />
<br />
[http://qingy.sourceforge.net/ Qingy] is ultralight and very configurable graphical login. It support login to both console and X Windows sessions. It uses [http://www.directfb.org DirectFB], therefore it does not start X Windows unless you choose X Windows session. See article about [[Qingy]] at Arch's wiki.<br />
<br />
=== Composite desktop ===<br />
<br />
[[Xcompmgr]] is a lightweight composite manager capable of rendering drop shadows, fading and simple window transparency within Openbox and other window managers.<br />
(It's worth noting that xcompmgr is no longer developed, and so any issues are unlikely to be fixed)<br />
(Developed an issue with tint2 0.9, the systray icons have a tendency to corrupt)<br />
<br />
[[Cairo Compmgr | Cairo Composite Manager]] -- A versatile and extensible composite manager which uses cairo for rendering, is an alternative.<br />
<br />
=== Panels, trays, and pagers ===<br />
<br />
There are quite a lot of utilities available that provide a panel (taskbar), system tray, and pager to Openbox. The most common are:<br />
<br />
==== Panels ====<br />
* [[PyPanel]]<br />
* [http://nsf.110mb.com/bmpanel/ BMPanel]<br />
* [[tint2]]<br />
* [http://www.gnomefiles.org/app.php/LXPanel LXPanel]<br />
* [http://fbpanel.sourceforge.net fbpanel]<br />
* [http://freshmeat.net/projects/perlpanel/ PerlPanel]<br />
* [http://www.chatjunkies.org/fspanel/ fspanel]<br />
* [http://www.xfce.org/projects/xfce4-panel/ Xfce4-panel]<br />
* [http://live.gnome.org/GnomePanel/ GnomePanel]<br />
* [https://launchpad.net/awn avant-window-navigator]<br />
* [http://developer.berlios.de/projects/cairo-dock/ cairo-dock]<br />
* [http://code.google.com/p/wbar/ wbar]<br />
* [http://www.screenlets.org/ screenlets]<br />
* [http://www.failedprojects.de/pancake/ pancake]<br />
<br />
==== Trays ====<br />
* [http://stalonetray.sourceforge.net/ Stalonetray]<br />
* [http://download.gna.org/fvwm-crystal/trayer/1.0/ Trayer]<br />
<br />
==== Pagers ====<br />
* [http://projects.l3ib.org/trac/visibility Visibility]<br />
* [http://bbtools.sourceforge.net/ bbpager]<br />
* [http://aur.archlinux.org/packages.php?ID=17563 netwmpager]<br />
* [http://useperl.ru/ipager/index.en.html IPager]<br />
* [http://code.google.com/p/neap/ neap]<br />
<br />
Make your choice and add it to your startup file. If you wish to set the desktop layout without using a pager, you can use [http://aur.archlinux.org/packages.php?ID=34376 obsetlayout], which is a packaged version of the setlayout tool from the Openbox wiki.<br />
<br />
=== File managers ===<br />
<br />
There are many possibilities, but the most popular lightweight file managers are:<br />
* [[Thunar]]. Thunar supports auto-mount features and other plugins. <br />
* [http://rox.sourceforge.net ROX] (ROX provides desktop icons)<br />
# pacman -S rox<br />
* [http://pcmanfm.sourceforge.net PCManFM] (pcmanfm also provides desktop icons)<br />
# pacman -S pcmanfm<br />
To access NTFS drives with PCManFM, install ntfs-3g:<br />
# pacman -S ntfs-3g<br />
and make sure you're added to group hal:<br />
# gpasswd -a username hal<br />
For even lighter options, consider [http://www.obsession.se/gentoo/ Gentoo] or [http://emelfm2.net/ emelFM2], both of which use the familiar 'Midnight Commander' two pane layout.<br />
<br />
Others:<br />
Xfe<br />
muCommander<br />
''(Will edit it later after I have tried them both.)''<br />
<br />
Of course, you can also use GNOME's Nautilus. Although slower than the above solutions, it has the additional advantage of VFS support (e.g. remote SSH, FTP and Samba connections)<br />
<br />
=== Application launchers ===<br />
<br />
==== dmenu ====<br />
<br />
Set-up dmenu as described in the [[dmenu]] wiki article. Then, add the following entry to the <keyboard> section {{Filename|~/.config/openbox/rc.xml}} to enable a shortcut to launch dmenu:<br />
<keybind key="W-space"><br />
<action name="Execute"><br />
<execute>dmenu_run</execute><br />
</action><br />
</keybind><br />
<br />
==== Gmrun ====<br />
<br />
[http://sourceforge.net/projects/gmrun gmrun] provides an excellent Run dialog box, similar to the Alt+F2 features found in Gnome and KDE:<br />
# pacman -S gmrun<br />
Add the following entry to the <keyboard> section {{Filename|~/.config/openbox/rc.xml}} to enable Alt+F2 functionality:<br />
<keybind key="A-F2"><br />
<action name="execute"><execute>gmrun</execute></action><br />
</keybind><br />
<br />
==== Bashrun ====<br />
<br />
[http://bashrun.sourceforge.net bashrun] provides a different, barebones approach to a run dialog, using a specialized bash session within a small xterm window. It is available in the community repository and can be launched through the Alt+F2 style approach mentioned previously. To make bashrun act more like a traditional run dialog, add the following entry to the <applications> section {{Filename|~/.config/openbox/rc.xml}}:<br />
<application name="bashrun"><br />
<desktop>all</desktop><br />
<decor>no</decor> # switch to yes if you prefer a bordered window<br />
<focus>yes</focus><br />
<skip_pager>yes</skip_pager><br />
<layer>above</layer><br />
</application><br />
<br />
==== Launchy ====<br />
<br />
[http://www.launchy.net/ Launchy] is a less minimalistic approach; it is skinnable and offers more functionality such as a calculator, checking the weather, etc. Originally for Windows, similar to Gnome Do.<br />
# pacman -S launchy<br />
It is launched by Ctrl+Space key combination.<br />
<br />
==== LXPanel ====<br />
<br />
The LXPanel run dialog can be executed with <br />
lxpanelctl run<br />
<br />
==== gnome-panel ====<br />
<br />
The gnome-panel run dialog can be executed with <br />
gnome-panel-control --run-dialog<br />
<br />
=== Clipboard managers ===<br />
<br />
You may wish to install a clipboard manager for feature rich copy/paste ability. '''xfce4-clipman-plugin, parcellite,''' or '''glipper-old''' may be installed via pacman. Add your choice to autostart.sh. From the terminal, Ctrl+Insert as copy and Shift+Insert as paste generally works as well. You may also copy from terminal with Ctrl+Shift+C, and paste with mouse middle click.<br />
<br />
=== Volume managers ===<br />
<br />
==== gvolwheel ====<br />
<br />
a lightweight audio mixer which lets you control the audio volume through a tray icon [http://aur.archlinux.org/packages.php?ID=25502] <br />
<br />
==== gvtray ====<br />
<br />
A master volume mixer in the system tray [http://aur.archlinux.org/packages.php?ID=6362]<br />
<br />
==== obmixer ====<br />
<br />
Obmixer is a mixer appplet written in C which is intended to be a lightweight alternative to gnome volume control [http://aur.archlinux.org/packages.php?ID=31131]<br />
<br />
==== volti ====<br />
<br />
GTK+ application for controlling audio volume from system tray/notification area [http://aur.archlinux.org/packages.php?ID=33525]<br />
<br />
==== volumeicon ====<br />
<br />
Volume control for your system tray [http://aur.archlinux.org/packages.php?ID=35793]<br />
<br />
==== volwheel ====<br />
<br />
Tray icon to change volume with the mouse [http://www.archlinux.org/packages/community/i686/volwheel/]<br />
<br />
=== Keyboard layout switchers ===<br />
<br />
==== fbxkb ====<br />
<br />
Keyboard indicator and switcher [http://aur.archlinux.org/packages.php?ID=3458]<br />
<br />
==== xxkb ====<br />
<br />
keyboard layout switcher/indicator [http://www.archlinux.org/packages/community/i686/xxkb/]<br />
<br />
==== axkb ====<br />
<br />
QT4 keyboard layout switcher [http://aur.archlinux.org/packages.php?ID=25555]<br />
<br />
==== xneur ====<br />
<br />
X Neural Switcher is a text analyser, it detects the language of input and corrects it if needed [http://aur.archlinux.org/packages.php?ID=9750]<br />
<br />
== Tips and tricks ==<br />
<br />
=== File associations ===<br />
Since Openbox and the applications you are going to use with it are not very well integrated you might run into the issue that your browser does not know which programm it is supposed to use for certain types of files. The package in the AUR [http://aur.archlinux.org/packages.php?ID=23170 gnome-defaults-list] contains a list of file-types and programms specific to the gnome desktop. It will be installed to<br />
/etc/gnome/defaults.list<br />
Open it with your text-editor and now you can search&replace everything with your appropriate programms. Like totem<=>vlc or eog<=>mirage. Save the file to:<br />
~/.local/share/applications/defaults.list<br />
<br />
Another way is to use the package ''perl-file-mimeinfo'' from the repositories, and invoke the mimeopen command like this:<br />
mimeopen -d /path/to/file<br />
You will then be asked what application to use when opening /path/to/file:<br />
Please choose a default application for files of type text/plain<br />
1) notepad (wine-extension-txt)<br />
2) Leafpad (leafpad)<br />
3) OpenOffice.org Writer (writer)<br />
4) gVim (gvim)<br />
5) Other...<br />
Your answer will be set as the default handler for that type of file.<br />
<br />
=== Copy and paste ===<br />
<br />
From the terminal, Ctrl+Insert as copy and Shift+Insert as paste generally works as well. You may also copy from terminal with Ctrl+Shift+C, and paste with mouse middle click.<br />
<br />
=== Transparency ===<br />
<br />
By using the program transset-df, it is virtually the same as [[transset]], (available by: pacman -S transset-df) you can enable transparancy of windows on the fly. For instance by editing the following in {{Filename|~/.config/openbox/rc.xml}} you can have your middle mouse scroll enable and disable transparency by scrolling down and up on the scroll button, respectively, while over the title bar (it is in the <mouse> section):<br />
<context name="Titlebar"><br />
<mousebind button="Left" action="Press"><br />
<action name="Focus"/><br />
<action name="Raise"/><br />
</mousebind><br />
<mousebind button="Left" action="Drag"><br />
<action name="Move"/><br />
</mousebind><br />
<mousebind button="Left" action="DoubleClick"><br />
<action name="ToggleMaximizeFull"/><br />
</mousebind><br />
<mousebind button="Middle" action="Press"><br />
<action name="Lower"/> <br />
<action name="FocusToBottom"/><br />
<action name="Unfocus"/><br />
</mousebind><br />
<mousebind button="Up" action="Click"><br />
<action name= "Execute" ><br />
<execute>transset-df -p .2 --inc </execute><br />
</action><br />
</mousebind><br />
<mousebind button="Down" action="Click"><br />
<action name= "Execute" ><br />
<execute>transset-df -p .2 --dec </execute><br />
</action><br />
</mousebind><br />
<mousebind button="Right" action="Press"><br />
<action name="Focus"/><br />
<action name="Raise"/><br />
<action name="ShowMenu"><br />
<menu>client-menu</menu><br />
</action><br />
</mousebind><br />
</context><br />
As of now, it only appears to work when no other actions are taken.<br />
<br />
=== Xprop values for applications ===<br />
If you use per-application settings frequently, you might find this bash alias handy:<br />
<br />
alias xp='xprop | grep "WM_WINDOW_ROLE\|WM_CLASS" && echo "WM_CLASS(STRING) = \"NAME\", \"CLASS\""'<br />
<br />
To use, run '''{{Codeline|xp}}''' and click on the running program that you'd like to define with per-app settings. The result will display only the info that Openbox requires, namely the WM_WINDOW_ROLE and WM_CLASS (name and class) values:<br />
<br />
[thayer@dublin:~] $ xp<br />
WM_WINDOW_ROLE(STRING) = "roster"<br />
WM_CLASS(STRING) = "gajim.py", "Gajim.py"<br />
WM_CLASS(STRING) = "NAME", "CLASS"<br />
<br />
==== Xprop for Firefox ====<br />
<br />
For whatever reason, Firefox and its open source equivalents will ignore application rules (e.g. <desktop>) unless {{Codeline|class&#61;"Firefox*"}} is used, regardless of what xprop reports as the actual WM_CLASS values.<br />
<br />
=== Linking the menu to a command ===<br />
<br />
Some people would want to link the Openbox main menu, or any other, to a command. This is useful for creating a menu button in a panel, for example. Although Openbox doesn't support this, a very simple script, xdotool, can simulate a keypress by running a command. Xdotool is [http://aur.archlinux.org/packages.php?do_Details=1&ID=14789&O=0&L=0&C=0&K=xdotool&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd available on AUR]. To use it, simply add the following code to the <keyboard> section of your {{Filename|rc.xml}}:<br />
<keybind key="A-C-q"><br />
<action name="ShowMenu"><br />
<menu>root-menu</menu><br />
</action><br />
</keybind><br />
Restart/reconfigure Openbox. You can now magically summon your menu at your cursor position by running the following command:<br />
# xdotool key ctrl+alt+q<br />
Of course, you can change the shortcut to your liking.<br />
<br />
=== Urxvt in the background ===<br />
<br />
With Openbox, running a terminal as desktop background is easy. You won't need '''devilspie''' here.<br />
<br />
First you must enable transparency, open your {{Filename|.Xdefaults}} file (if it doesn't exist yet, create it in your home folder).<br />
URxvt*transparent:true<br />
URxvt*scrollBar:false<br />
URxvt*geometry:124x24 #I don't use the whole screen, if you want a full screen term don't bother with this and see below.<br />
URxvt*borderLess:true<br />
URxvt*foreground:Black #Font color. My wallpaper is White, you may wish to change this to White.<br />
<br />
Then edit your {{Filename|.config/openbox/rc.xml}} file:<br />
<application name="URxvt"><br />
<decor>no</decor><br />
<focus>yes</focus><br />
<position><br />
<x>center</x><br />
<y>20</y><br />
</position><br />
<layer>below</layer><br />
<desktop>all</desktop><br />
<maximized>true</maximized> #Only if you want a full size terminal.<br />
</application><br />
<br />
The ''magic'' comes from the {{Codeline|<layer>below</layer>}} line, which place the application under all others. Here Urxvt is displayed on all desktops, change it to your convenience.<br />
<br />
Note: Instead of using <application name="URxvt">, you can use another name ("URxvt-bg" for example), and use the -name option when starting uxrvt. That way, only the urxvt terminals which you choose to name URxvt-bg would be captured and modified by the application rule in rc.xml. For example: urxvt -name URxvt-bg (case sensitive)<br />
<br />
=== Keyboard Volume Control ===<br />
If you use ALSA for sound, you can use the amixer program to adjust the volume of sound. You can use Openbox's keybindings to act like multimedia keys. (Alternatively, you can probably find out the names of your real multimedia keys and map them.) For example, in the <keyboard> section of rc.xml:<br />
<br />
<keybind key="W-Up"><br />
<action name="Execute"><br />
<command>amixer set Master 5%+</command><br />
</action><br />
</keybind><br />
<br />
This binds Windows key + Up arrow to increase your master ALSA volume by 5%. Corresponding binding for volume down:<br />
<br />
<keybind key="W-Down"><br />
<action name="Execute"><br />
<command>amixer set Master 5%-</command><br />
</action><br />
</keybind><br />
<br />
As another example you can also use the XF86Audio keybindings:<br />
<br />
<keybind key="XF86AudioRaiseVolume"><br />
<action name="Execute"><br />
<command>amixer set Master 5%+ unmute</command><br />
</action><br />
</keybind><br />
<keybind key="XF86AudioLowerVolume"><br />
<action name="Execute"><br />
<command>amixer set Master 5%- unmute</command><br />
</action><br />
</keybind><br />
<keybind key="XF86AudioMute"><br />
<action name="Execute"><br />
<command>amixer set Master toggle</command><br />
</action><br />
</keybind><br />
<br />
The above example should work for the majority of multimedia keyboards. It should enable to raise, lower and mute the Master control of your audio device by using the respective multimedia keyboard keys. Notice also that in this example:<br />
<br />
* The "Mute" key should unmute the Master control if it is already in mute mode.<br />
* The "Raise" and "Lower" keys should unmute the Master control if it is in mute mode.<br />
<br />
== Resources ==<br />
<br />
* [http://openbox.org/ Openbox Website] &ndash; The official website<br />
* [http://planetob.openmonkey.com/ Planet Openbox] &ndash; Openbox news portal<br />
* [http://www.box-look.org/ Box-Look.org] &ndash; A good resource for themes and related artwork<br />
* [https://bbs.archlinux.org/viewtopic.php?id=93126 Openbox Hacks and Configs Thread] @ Arch Linux Forums<br />
* [https://bbs.archlinux.org/viewtopic.php?id=45692 Openbox Screenshots Thread] @ Arch Linux Forums<br />
<!-- vim: set ft=Wikipedia: --></div>Brendanhttps://wiki.archlinux.org/index.php?title=KDE_Wallet&diff=100858KDE Wallet2010-03-21T11:48:25Z<p>Brendan: added hint for autostart</p>
<hr />
<div>[[Category:Daemons_and_system_services (English)]]<br />
[[Category:Desktop environments (English)]]<br />
[http://utils.kde.org/projects/kwalletmanager/ KDE Wallet Manager] is a tool to manage the passwords on your KDE system. By using the KDE wallet subsystem it not only allows you to keep your own secrets but also to access and manage the passwords of every application that integrates with the KDE wallet.<br />
<br />
== Using the KDE Wallet to store ssh keys ==<br />
<br />
Install Kssaskpass from it's [http://aur.archlinux.org/packages.php?ID=22013 AUR page].<br />
<br />
Create the file <br />
<pre> ~/.kde/Autostart/ssh-add.sh</pre> <br />
<br />
Add this content<br />
<pre> #!/bin/sh<br />
export SSH_ASKPASS=/usr/bin/ksshaskpass<br />
ssh-add </dev/null<br />
</pre> <br />
<br />
Make it executable and run<br />
<pre>chmod +x ~/.kde/Autostart/ssh-add.sh<br />
~/.kde/Autostart/ssh-add.sh<br />
</pre> <br />
<br />
It will ask for your password and unlock the your ssh keys.<br />
<br />
You may need to go to system settings -> advanced -> Autostart -> add script in newer version of KDE.<br />
<br />
== KDE Wallet for firefox ==<br />
<br />
There is an addon to make firefox store passwords with firefox. Currently Firefox 3.5 is supported, but disabling addon checks means it can be made to work for Firefox 3.6.<br />
<br />
https://addons.mozilla.org/en-US/firefox/addon/49357</div>Brendanhttps://wiki.archlinux.org/index.php?title=Talk:Makepkg.conf&diff=95864Talk:Makepkg.conf2010-02-10T08:39:07Z<p>Brendan: /* Mistakes and Confusion */</p>
<hr />
<div>New versions of gcc support -mrach=native which detects which architecture to use at build time. This seems to be the best solution since users may be confused about their hardware or new architecture types are added to gcc for new processers march will continue to work. I am not an expert about gcc and wondering if there is a reason not to replace the whole discussion of architecture with -march=native and be done with it.<br />
<br />
Why does not x86-64 + "Core 2 Duo/Quad/Xeon/Pentium 4 P6xx" have -fomit-frame-pointer?<br />
<br />
---<br />
<br />
I have a 64-bit quad core xeon (x3360). Should I use nocona or core2? This wiki tells me I should use both - I'm confused:<br />
<br />
Core 2 Duo/Quad/Xeon/Pentium 4 P6xx<br />
* x86-64 <br />
CHOST="x86_64-pc-linux-gnu"<br />
CFLAGS="-march=nocona -O2 -pipe"<br />
CXXFLAGS="${CFLAGS}"<br />
[...]<br />
Note: for gcc 4.3.0 for Core2Duo (or Core2Quad) and x86_64 set CFLAGS="-march=core2 -O2 -pipe"<br />
<br />
Which part of the text should I listen to? I think a rewrite of that part would be great.<br><br />
--[[User:Trontonic|Trontonic]] 08:25, 26 March 2009 (EDT)<br />
<br />
== AMD Turion 64 Mobile? ==<br />
cat /proc/cpuinfo | grep "model name"<br />
<br />
model name : AMD Turion(tm) 64 Mobile Technology MK-36<br />
<br />
Should I use the Athlon 64 settings? --[[User:Matthewbauer|Matthewbauer]] 23:17, 27 July 2009 (EDT)<br />
:According to [http://en.gentoo-wiki.com/wiki/Safe_Cflags/AMD#Turion64_.2F_X2_.2F_Ultra Gentoo wiki], Turion setting is as follows (not same as Athlon 64):<br />
<br />
:32 bit:<br />
<pre><br />
CHOST="i686-pc-linux-gnu"<br />
CFLAGS="-march=athlon-xp -msse3 -O2 -pipe -fomit-frame-pointer"<br />
CXXFLAGS="${CFLAGS}"<br />
</pre><br />
<br />
:64 bit:<br />
<pre><br />
CHOST="x86_64-pc-linux-gnu"<br />
CFLAGS="-march=k8 -msse3 -O2 -pipe"<br />
CXXFLAGS="${CFLAGS}"<br />
</pre><br />
:--[[User:Blowback|Blowback]] 04:16, 28 July 2009 (EDT)<br />
<br />
== Mistakes and Confusion ==<br />
I'd almost say we should copy the gentoo wiki in this area, it is much more complete in this area and it does a much better job of avoiding confusion. <br />
--[[User:JonimusPrime|JonimusPrime]] 10:17, 30 October 2009 (EDT)<br />
<br />
:I'm not sure which site to trust. Gentoo's article says "prescott" should be used for atom, which is false (atom should use core2). This leads me to believe that they might have other stuff wrong.<br />
:To be honest I much rather delete this article and place a mention of "-march=native" in the main makepkg article. It has been working with Arch's gcc for a long time, and it's a whole lot simpler. This article is unnecessary... it might be useful for cross compilation but that's a corner case and it doesn't fit the intended wiki audience.<br />
:--[[User:Pacmanz|Pacmanz]] 11:11, 30 October 2009 (EDT)<br />
<br />
:: I agree; {{Codeline|1=-march=native}} should be sufficient. Anyone looking to really waste time should simply be directed to the GCC manpage for a full list of options, or specific optimizations should be split off into a separate "Wasting Time in Arch" article, along with recompiling all packages...<br />
<br />
:: -- [[User:Pointone|pointone]] 16:54, 30 October 2009 (EDT)<br />
<br />
If no one objects, I plan to remove the processor-specific optimizations in favour of links to the following Gentoo articles:<br />
<br />
* http://www.gentoo.org/doc/en/gcc-optimization.xml<br />
* http://en.gentoo-wiki.com/wiki/Safe_Cflags<br />
<br />
-- [[User:Pointone|pointone]] 12:04, 5 December 2009 (EST)<br />
<br />
That sounds like a good idea to me. It's confusing and well pointless with --march=native. --[[User:Brendan|Brendan]] 03:39, 10 February 2010 (EST)</div>Brendanhttps://wiki.archlinux.org/index.php?title=KDE_Wallet&diff=95523KDE Wallet2010-02-09T11:21:30Z<p>Brendan: removed white space</p>
<hr />
<div>[[Category:Daemons_and_system_services (English)]]<br />
[[Category:Desktop environments (English)]]<br />
[http://utils.kde.org/projects/kwalletmanager/ KDE Wallet Manager] is a tool to manage the passwords on your KDE system. By using the KDE wallet subsystem it not only allows you to keep your own secrets but also to access and manage the passwords of every application that integrates with the KDE wallet.<br />
<br />
== Using the KDE Wallet to store ssh keys ==<br />
<br />
Install Kssaskpass from it's [http://aur.archlinux.org/packages.php?ID=22013 AUR page].<br />
<br />
Create the file <br />
<pre> ~/.kde/Autostart/ssh-add.sh</pre> <br />
<br />
Add this content<br />
<pre> #!/bin/sh<br />
export SSH_ASKPASS=/usr/bin/ksshaskpass<br />
ssh-add </dev/null<br />
</pre> <br />
<br />
Make it executable and run<br />
<pre>chmod +x ~/.kde/Autostart/ssh-add.sh<br />
~/.kde/Autostart/ssh-add.sh<br />
</pre> <br />
<br />
It will ask for your password and unlock the your ssh keys.<br />
<br />
== KDE Wallet for firefox ==<br />
<br />
There is an addon to make firefox store passwords with firefox. Currently Firefox 3.5 is supported, but disabling addon checks means it can be made to work for Firefox 3.6.<br />
<br />
https://addons.mozilla.org/en-US/firefox/addon/49357</div>Brendanhttps://wiki.archlinux.org/index.php?title=KDE_Wallet&diff=95522KDE Wallet2010-02-09T11:21:15Z<p>Brendan: Title error</p>
<hr />
<div>[[Category:Daemons_and_system_services (English)]]<br />
[[Category:Desktop environments (English)]]<br />
<br />
[http://utils.kde.org/projects/kwalletmanager/ KDE Wallet Manager] is a tool to manage the passwords on your KDE system. By using the KDE wallet subsystem it not only allows you to keep your own secrets but also to access and manage the passwords of every application that integrates with the KDE wallet.<br />
<br />
== Using the KDE Wallet to store ssh keys ==<br />
<br />
Install Kssaskpass from it's [http://aur.archlinux.org/packages.php?ID=22013 AUR page].<br />
<br />
Create the file <br />
<pre> ~/.kde/Autostart/ssh-add.sh</pre> <br />
<br />
Add this content<br />
<pre> #!/bin/sh<br />
export SSH_ASKPASS=/usr/bin/ksshaskpass<br />
ssh-add </dev/null<br />
</pre> <br />
<br />
Make it executable and run<br />
<pre>chmod +x ~/.kde/Autostart/ssh-add.sh<br />
~/.kde/Autostart/ssh-add.sh<br />
</pre> <br />
<br />
It will ask for your password and unlock the your ssh keys.<br />
<br />
== KDE Wallet for firefox ==<br />
<br />
There is an addon to make firefox store passwords with firefox. Currently Firefox 3.5 is supported, but disabling addon checks means it can be made to work for Firefox 3.6.<br />
<br />
https://addons.mozilla.org/en-US/firefox/addon/49357</div>Brendanhttps://wiki.archlinux.org/index.php?title=KDE_Wallet&diff=95521KDE Wallet2010-02-09T11:20:39Z<p>Brendan: KDE wallet page created.</p>
<hr />
<div>[[Category:Daemons_and_system_services (English)]]<br />
[[Category:Desktop environments (English)]]<br />
= KDE Wallet =<br />
<br />
[http://utils.kde.org/projects/kwalletmanager/ KDE Wallet Manager] is a tool to manage the passwords on your KDE system. By using the KDE wallet subsystem it not only allows you to keep your own secrets but also to access and manage the passwords of every application that integrates with the KDE wallet.<br />
<br />
== Using the KDE Wallet to store ssh keys ==<br />
<br />
Install Kssaskpass from it's [http://aur.archlinux.org/packages.php?ID=22013 AUR page].<br />
<br />
Create the file <br />
<pre> ~/.kde/Autostart/ssh-add.sh</pre> <br />
<br />
Add this content<br />
<pre> #!/bin/sh<br />
export SSH_ASKPASS=/usr/bin/ksshaskpass<br />
ssh-add </dev/null<br />
</pre> <br />
<br />
Make it executable and run<br />
<pre>chmod +x ~/.kde/Autostart/ssh-add.sh<br />
~/.kde/Autostart/ssh-add.sh<br />
</pre> <br />
<br />
It will ask for your password and unlock the your ssh keys.<br />
<br />
== KDE Wallet for firefox ==<br />
<br />
There is an addon to make firefox store passwords with firefox. Currently Firefox 3.5 is supported, but disabling addon checks means it can be made to work for Firefox 3.6.<br />
<br />
https://addons.mozilla.org/en-US/firefox/addon/49357</div>Brendanhttps://wiki.archlinux.org/index.php?title=Talk:VMware&diff=95257Talk:VMware2010-02-06T19:45:37Z<p>Brendan: </p>
<hr />
<div>If you want a easy installation of '''Vmware Workstation on Arch64''' follow these steps:<br />
<br />
- Install and run '''xinetd'''<br />
<br />
- Download the '''tar.gz''' version of '''Vmware-Workstation-64bits''' (you need to register before)<br />
<br />
<br />
(The next steps are taken from the '''original article''')<br />
<br />
- mkdir -p /etc/rc.d/vmware.d/rc{0,1,2,3,4,5,6}.d<br />
<br />
- ln -s /bin/lsmod /sbin/lsmod<br />
<br />
- run vmware-install.pl<br />
<br />
- when it asks where the directories for rc0.d thru rc6.d are, use /etc/rc.d/vmware.d.<br />
<br />
- when it asks where the init directory is, use /etc/rc.d.<br />
<br />
- run vmware-config.pl<br />
<br />
<br />
- Install '''emul32-xlibs''' from aur (remember change arch parameter from PKGBUILD)<br />
<br />
- Add this lines to '''/etc/ld.so.conf'''<br />
/opt/lib32/lib<br />
/opt/lib32/usr/lib<br />
/emul/linux/x86/lib<br />
/emul/linux/x86/usr/lib<br />
/emul/linux/x86/usr/qt/3/lib<br />
- Run '''ldconfig'''<br />
<br />
<br />
- RUN IT!!<br />
<br />
--[[User:Nak|Nak]] 17:45, 30 May 2007 (GMT+1)<br />
<br />
<hr><br />
<br />
Is this wiki still current for Noodle (0.7.1)? Do these same instructions apply for installing VMPlayer by itself?<BR><br />
Thanks<BR><br />
[[User:Hackmeister|Hackmeister]] 11:07, 12 January 2006 (EST)<br />
<br />
yes, still current for Noodle 0.7.1. Still not too sure about the requirement for 'chmod 660 /dev/vmmon', though. What's the reason for that, as opposed to the 'chmod 600' for the rest of the nodes created by the script in /dev?<br><br />
[[User:jf|-jf]] 05:51, 20 February 2006 (UTC)<br />
<br />
Maybe chmod 660 is needed for allowing adding some user who will monitor /dev/vmmon to vmware group.<br><br />
[[User:Romashka|Romashka]] 09:32, 20 February 2006 (EET)<br />
<br />
<br><br />
<hr><br />
<br><br />
I had problems compiling kernel modules for vmware 5.0.5 (i think was gcc guilty there - i had 4.0.3 instead 3.x) - It complained about network modules - could not compile due some error.<br />
After upgraded to latest version - all went smooth - without installing other gcc version - (gcc 4.0.3-3)<br><br />
[[User:Suw|Suw]] Wed Mar 29 02:07:31 EEST 2006<br />
<br />
== Cannot compile modules for 2.6.20 ==<br />
<br />
'''* Solved with ABS's PKGBUILD. Thanks to all.'''<br />
<br />
I cannot compile VMware-workstation-5.5.3-34685 modules for 2.6.20 ARCH kernel, with the vmware-any-any-update101.tar.gz and executing runme.pl:<br />
<br />
Building for VMware Workstation 5.5.x.<br />
Using 2.6.x kernel build system.<br />
make: se ingresa al directorio `/tmp/vmware-config3/vmmon-only'<br />
make -C /lib/modules/2.6.20-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules<br />
make[1]: se ingresa al directorio `/usr/src/linux-2.6.20-ARCH'<br />
CC [M] /tmp/vmware-config3/vmmon-only/linux/driver.o<br />
In file included from /tmp/vmware-config3/vmmon-only/linux/driver.c:85:<br />
/tmp/vmware-config3/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ‘...’ before ‘compat_exit’<br />
/tmp/vmware-config3/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ‘...’ before ‘exit_code’<br />
/tmp/vmware-config3/vmmon-only/./include/compat_kernel.h:21: aviso: el tipo de dato por defecto es ‘int’ en la declaración de ‘_syscall1’<br />
make[2]: *** [/tmp/vmware-config3/vmmon-only/linux/driver.o] Error 1<br />
make[1]: *** [_module_/tmp/vmware-config3/vmmon-only] Error 2<br />
make[1]: se sale del directorio `/usr/src/linux-2.6.20-ARCH'<br />
make: *** [vmmon.ko] Error 2<br />
make: se sale del directorio `/tmp/vmware-config3/vmmon-only'<br />
Unable to build the vmmon module.<br />
<br />
For more information on how to troubleshoot module-related problems, please<br />
visit our Web site at "http://www.vmware.com/download/modules/modules.html" and<br />
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".<br />
<br />
Execution aborted.<br />
<br />
<br />
Any ideas? Thanks in advance.<br />
<br />
== Article rename ==<br />
<br />
Shouldn't this article be named just vmware? Or maybe one for vmware server and one for vmware workstation? --[[User:Brendan|Brendan]] 14:45, 6 February 2010 (EST)</div>Brendan