https://wiki.archlinux.org/api.php?action=feedcontributions&user=OKAN&feedformat=atomArchWiki - User contributions [en]2024-03-29T13:02:36ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Initscripts/rc.conf&diff=68064Initscripts/rc.conf2009-05-02T08:30:17Z<p>OKAN: </p>
<hr />
<div>[[Category: System administration (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Rc.conf}}<br />
{{i18n_entry|Italiano|Rc.conf (Italiano)}}<br />
{{i18n_entry|Русский|Rc.conf (Русский)}}<br />
{{i18n_entry|简体中文|Rc.conf (简体中文)}}<br />
{{i18n_entry|Nederlands|Rc.conf (Nederlands)}}<br />
{{i18n_entry|Türkçe|Rc.conf (Türkçe)}}<br />
{{i18n_links_end}}<br />
<br />
=Overview=<br />
The rc.conf file (/etc/rc.conf) is the core system configuration file used in Arch Linux. It puts several commonly edited settings such as timezone, keymap, kernel modules and daemons to load at start-up, etc. into one convenient text file to streamline system administration.<br />
<br />
This is what a typical rc.conf file looks like after a fresh installation.<br />
<br />
<pre><br />
#<br />
# /etc/rc.conf - Main Configuration for Arch Linux<br />
#<br />
<br />
# -----------------------------------------------------------------------<br />
# LOCALIZATION<br />
# -----------------------------------------------------------------------<br />
#<br />
# LOCALE: available languages can be listed with the 'locale -a' command<br />
# HARDWARECLOCK: set to "UTC" or "localtime"<br />
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock<br />
# TIMEZONE: timezones are found in /usr/share/zoneinfo<br />
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps<br />
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)<br />
# CONSOLEMAP: found in /usr/share/kbd/consoletrans<br />
# USECOLOR: use ANSI color sequences in startup messages<br />
#<br />
LOCALE="en_US.utf8"<br />
HARDWARECLOCK="localtime"<br />
USEDIRECTISA="no"<br />
TIMEZONE="Canada/Pacific"<br />
KEYMAP="us"<br />
CONSOLEFONT=<br />
CONSOLEMAP=<br />
USECOLOR="yes"<br />
<br />
# -----------------------------------------------------------------------<br />
# HARDWARE<br />
# -----------------------------------------------------------------------<br />
#<br />
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed<br />
# MOD_BLACKLIST: Prevent udev from loading these modules<br />
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.<br />
#<br />
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.<br />
#<br />
MOD_AUTOLOAD="yes"<br />
#MOD_BLACKLIST=() #deprecated<br />
MODULES=()<br />
<br />
# Scan for LVM volume groups at startup, required if you use LVM<br />
USELVM="no"<br />
<br />
# -----------------------------------------------------------------------<br />
# NETWORKING<br />
# -----------------------------------------------------------------------<br />
#<br />
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts<br />
#<br />
HOSTNAME="myhost"<br />
<br />
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.<br />
#<br />
# Interfaces to start at boot-up (in this order)<br />
# Declare each interface then list in INTERFACES<br />
# - prefix an entry in INTERFACES with a ! to disable it<br />
# - no hyphens in your interface names - Bash doesn't like it<br />
# <br />
# DHCP: Set your interface to "dhcp" (eth0="dhcp")<br />
# Wireless: See network profiles below<br />
#<br />
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"<br />
INTERFACES=(eth0)<br />
<br />
# Routes to start at boot-up (in this order)<br />
# Declare each route then list in ROUTES<br />
# - prefix an entry in ROUTES with a ! to disable it<br />
#<br />
gateway="default gw 192.168.0.1"<br />
ROUTES=(!gateway)<br />
<br />
# Enable these network profiles at boot-up. These are only useful<br />
# if you happen to need multiple network configurations (ie, laptop users)<br />
# - set to 'menu' to present a menu during boot-up (dialog package required)<br />
# - prefix an entry with a ! to disable it<br />
#<br />
# Network profiles are found in /etc/network.d<br />
#<br />
# This now requires the netcfg package<br />
#<br />
#NET_PROFILES=(main)<br />
<br />
# -----------------------------------------------------------------------<br />
# DAEMONS<br />
# -----------------------------------------------------------------------<br />
#<br />
# Daemons to start at boot-up (in this order)<br />
# - prefix a daemon with a ! to disable it<br />
# - prefix a daemon with a @ to start it up in the background<br />
#<br />
DAEMONS=(syslog-ng network netfs crond)<br />
</pre><br />
<br />
= Localization =<br />
* [[Locale|LOCALE]]: This sets your system language, which will be used by all i18n-friendly applications and utilities. You can get a list of the available locales by running locale -a from the command line. This setting's default is fine for US English users.<br />
* HARDWARECLOCK: Specifies whether the hardware clock, which is synchronized from on bootup and to on shutdown, stores UTC time, or the localtime. UTC makes sense because it greatly simplifies changing timezones and daylight savings time. localtime is necessary if you dual boot with an operating system that only stores localtime to the hardware clock, such as Windows.<br />
* [[TIMEZONE]]: Specifies your time zone. Possible time zones are the relative path to a zoneinfo file starting from the directory /usr/share/zoneinfo. For example, a german timezone would be Europe/Berlin, which refers to the file /usr/share/zoneinfo/Europe/Berlin.<br />
* [[KEYMAP]]: The keyboard layout you want to use. If you live in the US, you probably use qwerty, which is referred using us (default). The available keymaps are in /usr/share/kbd/keymaps. Please note that this setting is only valid for your TTYs, not any graphical window managers or X!<br />
* [[CONSOLEFONT]]: Defines the console font to load with the setfont program on bootup. Possible fonts are found in /usr/share/kbd/consolefonts. For more info see: [[Fonts#Fonts_in_virtual_console|Fonts in console]]<br />
* [[CONSOLEMAP]]: Defines the console map to load with the setfont program on bootup. Possible maps are found in /usr/share/kbd/consoletrans. You will want to set this to a map suitable for your locale (8859-1 for Latin1, for example) if you're using an utf8 locale above, and use programs that generate 8-bit output. If you're using X11 for everyday's work, don't bother, as it only affects the output of linux console applications.<br />
* USECOLOR: Enable (or disable) colorized status messages during boot-up.<br />
<br />
=Hardware=<br />
* MOD_AUTOLOAD: If set to "yes", Arch will scan your hardware at bootup and attempt to automatically load the proper modules for your system. This is done with udev.<br />
* MOD_BLACKLIST: Deprecated. Prefix modules with a bang (!) in the MODULES array to blacklist them.<br />
* MODULES: In this array you can list the names of modules you want to load during bootup without the need to bind them to a hardware device as in the modprobe.conf. Simply add the name of the module here, and put any options into the modprobe.conf if need be. Prepending a module with a bang ('!') will blacklist the module during bootup. A benefit of specifying networking modules here is that ethernet cards covered by the listed modules will always be detected in the order the modules are listed. This prevents the dreaded interface confusion where your ethernet hardware is assigned to seemingly random interfaces after each boot. An even better way to handle this is using static interface labels by configuring udev appropriately, though.<br />
* USELVM: Scan for [[LVM]] volume groups at startup, required if you use LVM. Set to "YES" runs a vgchange during sysinit.<br />
<br />
=Networking=<br />
* [[HOSTNAME]]: Set this to the hostname of the machine, without the domain part. This is totally your choice, as long as you stick to letters, digits and a few common special characters like the dash. Don't be too creative here, though, and when in doubt, use the default.<br />
* INTERFACES: Here you define the settings for your networking interfaces. The default lines and the included comments explain the setup well enough. If you do not use DHCP to configure a device, just keep in mind that the value of the variable (whose name must be equal to the name of the device which is supposed to be configured) equals the line which would be appended to the ifconfig command if you were to configure the device manually in the shell.<br />
* ROUTES: You can define your own static network routes with arbitrary names here. Look at the example for a default gateway to get the idea. Basically the quoted part is identical to what you'd pass to a manual route add command, therefore reading man route is recommended if you don't know what to write here, or simply leave this alone.<br />
* NETWORKS:This enables certain network profiles at bootup. Network profiles provide a convenient way of managing multiple network configurations, and are intended to replace the standard INTERFACES/ROUTES setup that is still recommended for systems with only one network configuration. If your computer will be participating in various networks at various times (eg, a laptop) then you should take a look at the '''/etc/network.d/ directory''' to set up some profiles. There are template files included there (/etc/network.d/examples/) that can be used to create new profiles. ( Note: Since the introduction of netcfg v2.0 NET_PROFILES has been changed to this. This new version also contains many revisions, including the path to the stored profiles, please see [[Network Profiles]] for more info. In general the NETWORKS line should work the same way as the NET_PROFILES line, assuming you have the profiles in the new path (/etc/network.d/), and have changes any syntax neccessary to accomadate for the new version. )<br />
<br />
=Daemons=<br />
* [[Daemons|DAEMONS]]: This array simply lists the names of those scripts contained in /etc/rc.d/ which are supposed to be started during the boot process. If a script name is prefixed with a bang (!), it is not executed. If a script is prefixed with an "at" symbol (@), then it will be executed in the background, ie. the startup sequence will not wait for successful completion before continuing. Usually you do not need to change the defaults to get a running system, but you are going to edit this array whenever you install system services like sshd, and want to start these automatically during bootup. This is basically Arch's way of handling what others handle with various symlinks to an init.d directory.<br />
'''Note:''' The order in which the daemons are listed is important as they are loaded in that order.</div>OKANhttps://wiki.archlinux.org/index.php?title=Browser_plugins&diff=66165Browser plugins2009-04-03T14:34:15Z<p>OKAN: </p>
<hr />
<div>[[Category:Internet and Email (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Flash_and_Adobe_Acrobat_browser_plugins}}<br />
{{i18n_entry|简体中文|Flash 和 Adobe Acrobat 浏览器插件}}<br />
{{i18n_entry|Español|Plugins de Flash y Adobe Acrobat para el browser (Español)}}<br />
{{i18n_entry|Français|Plugins Flash et Adobe Acrobat pour le navigateur (Français)}}<br />
{{i18n_entry|Türkçe|Flash ve Adobe Acrobat Eklentileri}}<br />
{{i18n_links_end}}<br />
<br />
= Updated Information for new installations! Use the information in this section =<br />
==Flash and Java plugins==<br />
To install Flash Player and Java, run<br />
# pacman -S flashplugin jre<br />
That should work!<br />
<br />
'''''Note:''' You may need to install ttf-ms-fonts (<code>pacman -S ttf-ms-fonts</code>) for flashplayer to render text properly.''<br />
<br />
'''''Note for Arch64:''' j2re will still not work for your browser - at this point in time (Dec 9 2008), there is still no support in jre-64 for java applets... See http://java.com/en/download/manual.jsp#note''<br />
<br />
=== Troubleshooting ===<br />
If plugins don't work at all in Firefox check the permissions of /usr/lib/mozilla. In my case only root was allowed to read files.<br />
<br />
$ cd /usr/lib/mozilla<br />
cd: permission denied: /usr/lib/mozilla<br />
<br />
# chmod 755 /usr/lib/mozilla<br />
# chmod 755 /usr/lib/mozilla/extensions<br />
<br />
=== OSS ===<br />
If you use OSS, sound may not work with Flash videos (but videos will still play), you may need to download <code>libflashsupport</code><br />
<br />
pacman -S libflashsupport<br />
<br />
This gives OSS support for the Flash plugin; no restarts, even of Firefox are necessary once the library is installed.<br />
<br />
=== Configuration ===<br />
To change your general plugin preferences (especially the privacy settings), you have to go to the Macromedia website. There a flash animation will give you access to your local settings.<br />
<br />
[http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager.html Macromedia Flash Settings]<br />
<br />
== Adobe Reader ==<br />
Due to licensing restrictions, Adobe Reader cannot be distributed from any of the normal Arch repos. There is a version available on the AUR [http://aur.archlinux.org/packages.php?ID=16980 here]. If you use yaourt, run:<br />
# yaourt -S --aur acroread<br />
There are localisations available in many languages, check the AUR for your language.<br />
$ yaourt -Ss --aur acroread-<br />
Due to a missing PATH you have to run:<br />
$ ln -s /usr/share/Adobe/Reader8/bin/acroread /usr/bin<br />
Please note that no matter how many votes it receives, this package will never be included in the community repo. See comment by Snowman [http://aur.archlinux.org/packages.php?ID=16980 here].<br />
<br />
==Fixing Flash in Konqueror==<br />
# pacman -S kmplayer<br />
<br />
Run kmplayer to make sure it creates a config file and then close kmplayer. Open "~/.kde/share/config/kmplayerrc" (or "~/.kde4/share/config/kmplayerrc" if you use KDE4's konqueror) with a text editor of your choice and add this to the ending:<br />
<br />
[application/x-shockwave-flash]<br />
player=npp<br />
plugin=/usr/lib/mozilla/plugins/libflashplayer.so<br />
<br />
Check the plugin line if it is correct by doing:<br />
$ slocate libflashplayer.so<br />
<br />
If it is not correct then change it to the correct filepath. Open Konqueror and go to Settings > Configure Konqueror > File Associations, navigate to "application/x-shockwave-flash" and click on the "Embedding" tab and click "Add.." and select "Embedded MPlayer for KDE" and click "Ok". Make sure "Embedded MPlayer for KDE" is on the top. Click "Ok". Now it should work, if it doesn't you might have to restart konqueror and/or KDE.<br />
<br />
Reference: http://mikearthur.co.uk/?p=171<br />
<br />
----<br />
<br />
= Old information for reference on old installations... Or whatever (OUTDATED) =<br />
<br />
==Using Mozilla==<br />
<br />
===For Adobe Acrobat Reader plugin===<br />
# pacman -S acroread<br />
# ln -s /opt/mozilla-plugins/nppdf.so /opt/mozilla/lib/mozilla/plugins/<br />
<br />
===For Shockwave Flash===<br />
# pacman -S flashplugin<br />
# ln -s /opt/mozilla-plugins/flashplayer.xpt /opt/mozilla/lib/mozilla/plugins/<br />
# ln -s /opt/mozilla-plugins/libflashplayer.so /opt/mozilla/lib/mozilla/plugins/<br />
<br />
Restart Mozilla if it was running.<br />
<br />
'''Note:''' Flash is known to have bad support for Linux.<br />
Flash Player 7 has problems regarding sound output with a lot of people.<br />
Flash versions older than 10 have bad PulseAudio support.<br />
<br />
There is a GNU project going on (Gnash) that should be an open source alternative for showing Flash.<br />
As of 17 may 2006 it is still in development, but it is already able to run a lot of Flash 7 content.<br />
<br />
==Using Mozilla Firefox==<br />
<br />
===For Adobe Acrobat Reader plugin===<br />
# pacman -S acroread<br />
# ln -s /opt/mozilla-plugins/nppdf.so /opt/mozilla/lib/firefox/plugins/<br />
<br />
'''Note:''' acroread has been moved to the AUR. Use [[yaourt]], or download from Adobe (instructions: [http://plugindoc.mozdev.org/faqs/acroread.html#install-linux]).<br />
<br />
'''Note:''' the second (ln -s) step above may be unnecessary.<br />
<br />
===For Shockwave Flash===<br />
# pacman -S flashplugin ttf-ms-fonts<br />
# ln -s /opt/mozilla-plugins/flashplayer.xpt /opt/mozilla/lib/firefox/plugins/<br />
# ln -s /opt/mozilla-plugins/libflashplayer.so /opt/mozilla/lib/firefox/plugins/<br />
<br />
'''Note:''' Flash is known to have bad support for Linux.<br />
Flash Player 7 has problems regarding sound output with a lot of people.<br />
Flash versions older than 10 have bad PulseAudio support.<br />
<br />
'''Note:''' Also works with Firefox3; replace <code>/opt/mozilla/lib/firefox/plugins</code> with <code>/opt/mozilla/lib/firefox-3.0/plugins</code><br />
<br />
There is a GNU project going on (Gnash) that should be an open source alternative for showing Flash.<br />
As of 17 may 2006 it is still in development, but it is already able to run a lot of Flash 7 content.<br />
<br />
====Alternate way====<br />
Visit http://www.adobe.com/products/flashplayer/ and download the Adobe Flash player .tar.gz file. Unpack it and execute the flashplayer-installer as root.<br />
# ./flashplayer-installer<br />
<br />
The script will ask for location of the browser. For Firefox, enter<br />
/usr/lib/firefox<br />
<br />
Note that the target directory must contain a directory called plugins in order for the offical installer to work. An invalid install path error can be solved by executing<br />
mkdir /usr/lib/firefox/plugins<br />
<br />
Restart Firefox. Repeat for any browsers installed.<br />
<br />
===For Java Plugin===<br />
# pacman -S jre<br />
# ln -s /opt/java/jre/plugin/i386/ns7-gcc29/libjavaplugin_oji.so /opt/mozilla/lib/firefox/plugins/<br />
<br />
(For me it's: <code>ln -s /opt/java/jre/plugin/i386/ns7/libjavaplugin_oji.so /opt/mozilla/lib/firefox/plugins/</code>, note the missing gcc29)<br />
<br />
Use the Tab key to navigate easier through the directories.<br />
<br />
=For Arch64 users=<br />
[[Install Flash on Arch64]]</div>OKANhttps://wiki.archlinux.org/index.php?title=Java&diff=66156Java2009-04-03T12:58:19Z<p>OKAN: </p>
<hr />
<div>[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Java}}<br />
{{i18n_entry|Türkçe|Java (Türkçe)}}<br />
{{i18n_links_end}}<br />
<br />
== Introduction ==<br />
<br />
''From [http://en.wikipedia.org/wiki/Java_(programming_language) Wikipedia]:''<br />
<br />
Java is a programming language originally developed by Sun Microsystems and released in 1995 as a core component of Sun Microsystems' Java platform. The language derives much of its syntax from C and C++ but has a simpler object model and fewer low-level facilities. Java applications are typically compiled to bytecode that can run on any Java virtual machine (JVM) regardless of computer architecture.<br />
<br />
== Installation ==<br />
<br />
There are two Java Virtual Machines in the Arch repos that can be installed on your system &mdash; the OpenJDK open source implementation and Sun's closed source implementation. Arch recommends OpenJDK [http://www.archlinux.org/news/418/].<br />
<br />
=== Installing the OpenJDK JVM ===<br />
<br />
To be able to run Java programs, you can install OpenJDK from the ''extra'' repo. This also installs a Java Development Kit.<br />
<br />
pacman -S openjdk6<br />
<br />
{{Box Note | This will also install the Java plugin for Firefox.}}<br />
<br />
=== Installing the Sun JVM ===<br />
<br />
To be able to run Java programs, you can install the Sun JRE from the ''community'' repo:<br />
<br />
pacman -S jre<br />
<br />
{{Box Note | This will also install the Java plugin for Firefox.}}<br />
<br />
To create Java programs, you can install the Sun JDK from the ''community'' repo:<br />
<br />
pacman -S jdk<br />
<br />
== Firefox Symlinks for Arch 64 ==<br />
<br />
As of January 4, 2009, there exists a beta version of the JRE that works natively with 64-bit systems in the aur. (jre_beta).<br />
<br />
After installing it, first check that $HOME/.mozilla/plugins exists as a directory. Then, make a symbolic link from /opt/java/jre/lib/amd64/libnpjp2.so to $HOME/.mozilla/plugins/libnpjp2.so. Restart Firefox, and Java applets should now work.<br />
<br />
<b>NOTE:</b> Java applets seem to work without making this symlink and the plugin appears in the Firefox add-on's as libnpjp2.so <br> <br />
- [[User:ST.x|ST.x]] 13:20, 18 January 2009 (AEST)</div>OKANhttps://wiki.archlinux.org/index.php?title=Java&diff=66155Java2009-04-03T12:57:56Z<p>OKAN: </p>
<hr />
<div>[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Türkçe|Java (Türkçe)}}<br />
{{i18n_entry|English|Java}}<br />
{{i18n_links_end}}<br />
<br />
== Introduction ==<br />
<br />
''From [http://en.wikipedia.org/wiki/Java_(programming_language) Wikipedia]:''<br />
<br />
Java is a programming language originally developed by Sun Microsystems and released in 1995 as a core component of Sun Microsystems' Java platform. The language derives much of its syntax from C and C++ but has a simpler object model and fewer low-level facilities. Java applications are typically compiled to bytecode that can run on any Java virtual machine (JVM) regardless of computer architecture.<br />
<br />
== Installation ==<br />
<br />
There are two Java Virtual Machines in the Arch repos that can be installed on your system &mdash; the OpenJDK open source implementation and Sun's closed source implementation. Arch recommends OpenJDK [http://www.archlinux.org/news/418/].<br />
<br />
=== Installing the OpenJDK JVM ===<br />
<br />
To be able to run Java programs, you can install OpenJDK from the ''extra'' repo. This also installs a Java Development Kit.<br />
<br />
pacman -S openjdk6<br />
<br />
{{Box Note | This will also install the Java plugin for Firefox.}}<br />
<br />
=== Installing the Sun JVM ===<br />
<br />
To be able to run Java programs, you can install the Sun JRE from the ''community'' repo:<br />
<br />
pacman -S jre<br />
<br />
{{Box Note | This will also install the Java plugin for Firefox.}}<br />
<br />
To create Java programs, you can install the Sun JDK from the ''community'' repo:<br />
<br />
pacman -S jdk<br />
<br />
== Firefox Symlinks for Arch 64 ==<br />
<br />
As of January 4, 2009, there exists a beta version of the JRE that works natively with 64-bit systems in the aur. (jre_beta).<br />
<br />
After installing it, first check that $HOME/.mozilla/plugins exists as a directory. Then, make a symbolic link from /opt/java/jre/lib/amd64/libnpjp2.so to $HOME/.mozilla/plugins/libnpjp2.so. Restart Firefox, and Java applets should now work.<br />
<br />
<b>NOTE:</b> Java applets seem to work without making this symlink and the plugin appears in the Firefox add-on's as libnpjp2.so <br> <br />
- [[User:ST.x|ST.x]] 13:20, 18 January 2009 (AEST)</div>OKANhttps://wiki.archlinux.org/index.php?title=USB_flash_installation_medium&diff=66113USB flash installation medium2009-04-02T13:51:50Z<p>OKAN: </p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Install from USB stick}}<br />
{{i18n_entry|Türkçe|USB' den Kurulum (Türkçe)}}<br />
{{i18n_links_end}}<br />
<br />
== The New and Improved Way, on Linux ==<br />
<br />
Beginning from release 2008.06, USB images are provided. Download them from your [http://archlinux.org/download/ local mirror] (they are the .img files). To install, check the device is unmounted and then use the following command:<br />
<br />
dd bs=8M if=image.img of=/dev/sd[x]<br />
<br />
where ''image.img'' is the path to the img file and ''/dev/sd[x]'' is your USB device. Make sure to use /dev/sdx and not /dev/sdx1.<br />
<br />
'''Note:''' This will irrevocably delete all files on your USB stick, so make sure you don't have any important files on the stick before doing this.<br />
<br />
===UNetBootin===<br />
<br />
Another way to make a USB drive bootable, is by using [http://unetbootin.sourceforge.net/ UNetBootin]. This application can download most linux distributions for you and write it to your drive. Or you can provide your own images, which does not have to be a special USB image.<br />
<br />
== The New and Improved Way, on Mac OS X ==<br />
<br />
To be able to use dd on your usb device on a Mac you have to do some special manoveurs. First of all insert your usb device, OS X will automount it, and run<br />
<br />
diskutil list<br />
<br />
in Terminal.app. Figure out what your usb device is called - mine was called /dev/disk1. Now you run<br />
<br />
diskutil unmountDisk /dev/disk1<br />
<br />
to unmount the partitions on the device (i.e., /dev/disk1s1) while keeping the device proper (i.e., /dev/disk1). Now we can continue in accordance with the Linux instructions above.<br />
<br />
== The New and Improved Way, on Windows ==<br />
<br />
To write the USB image on Windows, you will need [http://shounen.ru/soft/flashnul/ flashnul] ([http://translate.google.com/translate?u=http%3A%2F%2Fshounen.ru%2Fsoft%2Fflashnul%2F&hl=en&ie=UTF8&sl=ru&tl=en English version of the page]) or [http://www.cygwin.com/ Cygwin].<br />
<br />
=== The Flashnul Way ===<br />
<br />
From a command prompt, invoke flashnul with -p, and determine which device index is your USB drive. For example, my output looks like this:<br />
<br />
C:\>flashnul -p<br />
<br />
Avaible [sic] physical drives:<br />
0 size = 200048565760 (186 Gb)<br />
1 size = 400088457216 (372 Gb)<br />
2 size = 400088457216 (372 Gb)<br />
3 size = 4060086272 (3872 Mb)<br />
<br />
In my case, with a 4 GB USB drive, it is device index 3.<br />
<br />
When you have determined which device is the correct one, you can write the image to your drive, by invoking flashnul with the device index, -L, and the path to your image. In my case, it would be<br />
<br />
C:\>flashnul 3 -L path/to/arch/usb.img<br />
<br />
As long as you are really sure you want to write the data, type yes, then wait a bit for it to write. If you get an access denied error, unplugging and re-attaching the drive worked for me.<br />
<br />
<b>Note!</b><br />
<i>I had to do "C:\flashnul\flashnul.exe <b>H:</b> -L c:\archlinux-2008.06-core-i686.img" for it to work. I kept getting access denied if i just used the number. -gejr </i><br />
<br />
=== The Cygwin Way ===<br />
<br />
Make sure your cygwin installation contains the dd package.<br />
<br />
Place your image file in your home directory, in my case it is:<br />
<br />
C:\cygwin\home\John\<br />
<br />
Run cygwin as administrator (required for cygwin to access hardware). To write to your USB drive use the following command:<br />
<br />
dd if=image.img of=\\.\[x]:<br />
<br />
where image.img is the path to the img file within the cygwin directory and \\.\[x]: is your USB device where x is the windows designated letter, in my case "\\.\d:".<br />
<br />
'''Note:''' This will irrevocably delete all files on your USB stick, so make sure you don't have any important files on the stick before doing this.<br />
<br />
==Old Method from ISO, deprecated==<br />
*Prepare USB stick:<br />
The arch-ftp.img is about 150 MB, so it should fit on a 256 MB USB stick. The arch-core.img is ~300 MB and should fit on a 512 MB stick.<br />
<br />
1. Partition the USB stick.<br />
Create one partition with FAT16 type, make it bootable. Remember its name, such as /dev/sd[x]1.<br />
<br />
cfdisk /dev/sd[x]<br />
<br />
2. Make a FAT16 filesystem (you need dosfstools)<br />
<br />
mkdosfs /dev/sd[x]1<br />
<br />
3. Get the arch-base install ISO from www.archlinux.org<br />
<br />
4. Mount the iso to an temporary directory<br />
<br />
mkdir -p /mnt/archcd<br />
mount -o loop /Path/to/iso /mnt/archcd<br />
<br />
5. Mount the USB Stick<br />
<br />
mkdir -p /mnt/usb/<br />
mount /dev/sd[x]1 /mnt/usb/<br />
<br />
6. Copy the .iso to the USB Stick<br />
<br />
cp -ra /mnt/archcd/* /mnt/usb/<br />
<br />
<br />
7. Copy the boot data<br />
<br />
cd /mnt/usb/isolinux/<br />
cp vmlinuz /mnt/usb/<br />
cp initrd.img /mnt/usb/<br />
cp boot.* /mnt/usb/<br />
cp isolinux.cfg /mnt/usb/syslinux.cfg<br />
<br />
8. Install MBR and syslinux<sup>(1)</sup><br />
<br />
lilo -M /dev/sd[x] mbr<br />
syslinux -s /dev/sd[x]1<br />
<br />
===After booting from the USB stick:===<br />
<br />
Start the installation by logging in as root and invoke the command "/arch/setup".<br />
<br />
The installer should mount the source media automatically. If it fails you can manually mount the source media on the stick to the /src directory with the following command:<br />
<br />
mount /dev/sd[x] /src<br />
<br />
===Troubleshooting:===<br />
<br />
If you happen to run into "Cluster sizes larger than 16K not supported" error when running syslinux - don't panic, that just means you need to install more recent version of syslinux.<br />
<br />
<sup>(1)</sup> Using lilo is not really needed because syslinux does the "floppy" loading stuff. But if you get some error like "Can't load operating system" you have to perform the lilo command.</div>OKANhttps://wiki.archlinux.org/index.php?title=Wicd_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=65155Wicd (简体中文)2009-03-16T20:57:03Z<p>OKAN: </p>
<hr />
<div>[[Category: 网络]]<br />
[[Category:Internet和Email]]<br />
[[Category: HOWTOs (简体中文)]]<br />
[[Category:简体中文]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Wicd}}<br />
{{i18n_entry|Italiano|Wicd (Italiano)}}<br />
{{i18n_entry|简体中文|Wicd (简体中文)}}<br />
{{i18n_entry|Türkçe|Wicd (Türkçe)}}<br />
{{i18n_links_end}}<br />
<br />
=Introduction简介=<br />
[http://www.wicd.net/ Wicd]是一个既能管理无线网络(如[[Wifi Radar]])又能管理有线网络的网络接入管理器,相似又相冲突于[[NetworkManager]]。Wicd是用Python和[[GTK+]]写成的。现在其对应与i686和x86_64的版本已经是extra源中一部分了。<br />
<br />
=Installation安装=<br />
== Repository 软件源==<br />
首先根据你想要的软件版本,在/etc/pacman.conf打开[extra](默认已打开)或者[testing](默认没有打开)源。(打开就是去除#)<br />
# nano /etc/pacman.conf<br />
pacman.conf中找到类似于如下的这段:<br />
[extra]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
然后就使用以下命令来安装,如果你系统中没有python和gtk相关程序,pacman也会自动检查依赖关系然后安装好的。(废话,本来就是pacman本身的基本功能。)<br />
# pacman -Sy wicd<br />
你很可能还要安装DHCP和[[wpa_supplicant|无线安全管理程序]].<br />
# pacman -S dhclient wpa_supplicant<br />
<br />
== Latest 最新版本==<br />
''注意: 也许下面不能工作 如果包装过程包含一个补丁 (you can use part of the PKGBUILD from AUR or DIY entirely)''<br><br />
<br />
如果你想取得最新的版本为了能更好的工作, 那么编辑 '''$pkgver''' 在[[PKGBUILD]]. 也许你同时需要编辑 '''$pkgrel''' (改变它到 '''1''') 和 '''$md5sums'''.<br />
# abs<br />
$ cd /var/abs/local<br />
$ cp -r ../extra/network/wicd .<br />
$ nano PKGBUILD<br />
然后运行<br />
$ makepkg<br />
如果一切运行顺利, 然后运行.<br />
# pacman -U *pkg.tar.gz<br />
<br />
== AUR ==<br />
There is a package in the [[AUR|users' repository]] which should build the latest ''SVN'' release. You can flag it out-of-date if it does not.<br />
<br />
=Daemons=<br />
因为wicd是一个基本的GNU/LINUX网络脚本前端程序,所以你不再需要在rc.conf中的deamon加载network了。(!network,之前加一个!就可以不加载了。)你当然也不需要networkmanager来干扰wicd了。以下命令就是要手动关闭network、dhcdbd和networkmanager这些守护程序。<br />
# /etc/rc.d/network stop<br />
# /etc/rc.d/dhcdbd stop<br />
# /etc/rc.d/networkmanager stop<br />
在rc.conf你要直接永久地移除网络相关的设置(也可以注释掉),这是因为这些网络设置都会由wicd来生成和管理,如下:<br />
INTERFACES=(!eth0 !wlan0) #这里的lo不再需要了,因为其是由 /etc/rc.sysinit启动的。<br />
...<br />
DAEMONS=(syslog-ng @alsa !network '''dbus''' !dhcdbd !networkmanager '''wicd''' netfs ...)<br />
<br />
确保你帐号是在network组中的。使用如下命令把你帐号加入到network组中。(如何查看netwok组中还有其它什么帐号呢?我还不知道,请教了。)<br />
gpasswd -a $USERNAME network<br />
<br />
安装Hicolo的图标主题,使用如下命令:(估计wicd这个程序要用到这个主题中的图标吧。)<br />
pacman -S hicolor-icon-theme<br />
<br />
如你所见,wicd是必须依赖于dbus的正常工作的。daemon中hal要先于wicd启动,因为hal会自动启动dbus的。现在为了确保wicd的GUI能运行,你首先要让dbus正常运行,再开启wicd这个守护程序,用如下命令实现。<br />
# /etc/rc.d/dbus start<br />
# /etc/rc.d/wicd start<br />
<br />
=Starting启动=<br />
启动wicd的GUI,运行如下命令(不用root权限的):<br />
$ /usr/lib/wicd/gui.py<br />
启动wicd状态栏图标程序,运行如下命令(不用root权限):<br />
$ /usr/lib/wicd/tray.py<br />
为了在你登入系统时wicdGUI程序自启动,请在会话(gnome系统菜单中有)中加入/usr/lib/wicd/tray.py。<br />
<br />
=Troubleshooting发现与解决问题=<br />
== D-BUS ==<br />
如果dbus这个守护程序(相当于WIN中看服务)已经运行了,但是某些原因下wicd还是提示说dbus有问题,那么你就先关闭dbus和wicd,然后再启动dbus和wicd。(我没有遇到这个问题。)<br />
# /etc/rc.d/dbus stop # we are stopping manually instead of restarting to eliminate possible errors<br />
# /etc/rc.d/wicd stop<br />
# /etc/rc.d/dbus start<br />
# /etc/rc.d/wicd start<br />
== GUI ==<br />
如果在你点击了wicd的状态栏图标后,wicd的GUI没有出现,那么请你确保你是单击了图标而不是双击,因为单击一下图标是显示GUI,再单击一个图标就是关闭GUI,双击正好被程序误认为是开了又关了。哈哈。<br />
<br />
== Tray Icon 状态栏图标==<br />
If you had Wicd autostart, and you get a white box instead of the icon after a reboot, create a desktop entry instead of symlinking. This apparently occurs in a KDE environment where a desktop file is always a good idea.<br />
<br />
First, make sure there are no existing symbolic links/shortcuts.<br />
# for i in `find /{opt,usr/share,home} -type l -print0 | xargs -r0 file | grep wicd/tray*.py | sed -e 's/^\|:.*//g'`; do rm -iv $i; done<br />
That searches for symbolic links to a ''wicd'' directory containing any rendition of ''tray.py'' under ''/opt'', ''/usr/share'' and ''/home'', then asks whether you want to delete them. You can do this yourself manually.<br />
<br />
Now create the desktop file. In KDE, you can place it globally in ''/opt/kde/share/autostart'' or locally in ''~/.kde/Autostart:''<br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Name=Wicd<br />
Exec=/usr/lib/wicd/tray.py<br />
Icon=<br />
Type=Application<br />
StartupNotify=false<br />
<br />
=Related links相关链接=<br />
*[http://bbs.archlinux.org/viewtopic.php?id=40337 Note on the network daemon and interfaces]<br />
*[http://www.wicd.net/download.php Note on interfaces at the official site]<br />
*[http://www.wicd.net/phpbb/viewtopic.php?p=1420 KDE Autostart Issue]<br />
*[http://www.wicd.net/phpbb/viewtopic.php?f=5&t=263&sid=90b13d4cec6ce6109515532267d39ae0&p=2005 Common Bugs]</div>OKANhttps://wiki.archlinux.org/index.php?title=Wicd_(Italiano)&diff=65154Wicd (Italiano)2009-03-16T20:56:48Z<p>OKAN: </p>
<hr />
<div>[[Category: Networking (Italiano)]]<br />
[[Category: HOWTOs (Italiano)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Wicd}}<br />
{{i18n_entry|Italiano|Wicd (Italiano)}}<br />
{{i18n_entry|简体中文|Wicd (简体中文)}}<br />
{{i18n_entry|Türkçe|Wicd (Türkçe)}}<br />
{{i18n_links_end}}<br />
<br />
=Introduzione=<br />
[http://www.wicd.net/ Wicd] è un gestore di connessioni di rete utile alla gestione e cofigurazione di schede wireless (come [[Wifi Radar]]) o ethernet, simile e alternativo a [[NetworkManager]]. Wicd è scritto in Python e [[GTK+]]. E' presente nel repository ''extra'' per architettura ''i686'' e ''x86_64.''<br />
<br />
=Installazione=<br />
== Versione Ufficiale ==<br />
Dovete avere il repository '''[extra]''' (e/o '''[testing]''' a seconda della versione desiderata) abilitato in ''/etc/pacman.conf,''.<br />
# nano /etc/pacman.conf<br />
Dovreste trovare qualcosa di simile a:<br />
[extra]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
Ora scaricate il pacchetto (verranno automaticamente installate le dipendeze relative a python e gtk se non sono già installate).<br />
# pacman -Sy wicd<br />
Potrebbe essere utile intstallare anche DHCP e [[wpa_supplicant|secure wireless management]].<br />
# pacman -S dhclient wpa_supplicant<br />
<br />
== AUR ==<br />
E' presente un PKGBUILD in [[AUR|users' repository]] per installare la versione ''SVN''. Potete segnalarla come out-of-date se non viene installata correttamente.<br />
<br />
=Configurazione=<br />
Dato che Wicd è una applicazione front-end per la gestione degli script di base GNU/Linux di gestione della rete, dovete disabilitare il demone ''network''. Inoltre è necessario fermare ulteriori gestori quali ad esempio ''networkmanager''.<br />
# /etc/rc.d/network stop<br />
# /etc/rc.d/dhcdbd stop<br />
# /etc/rc.d/networkmanager stop<br />
Potete disabilitarli/rimuoverli permanentemente, disabilitando in [[rc.conf]] anche le interfacce di rete che dovranno essere gestite direttamente da Wicd:<br />
INTERFACES=(!eth0 !wlan0) # lo non è più necessaria qui, viene impostata da /etc/rc.sysinit<br />
...<br />
DAEMONS=(syslog-ng @alsa !network '''dbus''' !dhcdbd !networkmanager '''wicd''' netfs ...)<br />
<br />
Assicuratevi di aggiungere il vostro utente al gruppo network<br />
# gpasswd -a $USERNAME network<br />
<br />
Installate il tema di icone Hicolor:<br />
# pacman -S hicolor-icon-theme<br />
<br />
E' necessario inoltre avviare il demone ''dbus'' perchè Wicd funzioni correttamente. Tenete presente comunque che ''dbus'' viene avviato automaticamente dal demone ''hal''. Ora assicuratevi che tutto funzioni come dovrebbe; avete bisogno del demone ''wicd'' avviato prima di far partire l'applicazione.<br />
# /etc/rc.d/dbus start<br />
# /etc/rc.d/wicd start<br />
<br />
=Avvio=<br />
Per avviare l'applicazione grafica digitare come utente semplice:<br />
$ /usr/lib/wicd/gui.py<br />
Per avviare l'icone nel system tray digitare come utente semplice:<br />
$ /usr/lib/wicd/tray.py<br />
Potete aggiungere ''/usr/lib/wicd/tray.py'' all'avvio automatico del vostro DE/WM per avviare l'applicazione iconificata ad ogni login.<br />
<br />
=Possibili problemi=<br />
== D-BUS ==<br />
Se il demone ''dbus'' è già avviato, ma ''wicd'' non riesce ad interagirvi, riavviate entrambi.<br />
'''Attenzione:''' è consigliabile stoppare dbus da una console, non fatelo con ancora il server X attivo. Prima di stoppare il server dbus, entrate in una console con CTRL+ALT+F1, loggatevi come root (o come utente, usando poi sudo) e stoppate prima il server grafico con<br />
<br />
/etc/rc.d/gdm stop<br />
<br />
(mettete kdm al posto di gdm se siete utenti kde)<br />
<br />
assicuratevi poi che il comando<br />
<br />
ps -A | grep Xorg<br />
<br />
non restituisca niente a video (sarete così certi che il server grafico è stato disattivato)<br />
procedete poi con<br />
<br />
# /etc/rc.d/dbus stop<br />
# /etc/rc.d/wicd stop<br />
# /etc/rc.d/dbus start<br />
# /etc/rc.d/wicd start<br />
<br />
e infine riavviate il server grafico col comando usato per disattivarlo, mettendo però start al posto di stop.<br />
<br />
== GUI ==<br />
Se l'applicazione non si avvia premendo sull'icona presente nel system tray, assicuratevi di premere solo una volta col mouse (single-click). Il doppio click non funziona; apre e chiude istantaneamente l'applicazione.<br />
<br />
== Tray Icon ==<br />
Se avete impostato ''wicd'' per avviarsi automaticamente, e notate un quadratino bianco al posto dell'icona nel system tray, create un collegamento sul desktop al posto di un link simbolico. Questo sembra succedere in KDE dove un file .desktop è sempre una buona idea..<br />
<br />
Inanzitutto, assicuratevi che non siano già presenti link simbolici/shortcuts.<br />
# for i in `find /{opt,usr/share,home} -type l -print0 | xargs -r0 file | grep wicd/tray*.py | sed -e 's/^\|:.*//g'`; do rm -iv $i; done<br />
Questo comando cerca link simbolici che puntano a una directory''wicd''contenente ''tray.py'' in ''/opt'', ''/usr/share'' e ''/home'', dopodichè vi chiede conferma per eliminarli. E' ovviamente possibile fare questo manualmente.<br />
<br />
Ora create il desktop file. In KDE, potete posizionarlo globalmente in ''/opt/kde/share/autostart'' o localmente in ''~/.kde/Autostart:''<br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Name=Wicd<br />
Exec=/usr/lib/wicd/tray.py<br />
Icon=<br />
Type=Application<br />
StartupNotify=false<br />
<br />
=Link Collegati=<br />
*[http://bbs.archlinux.org/viewtopic.php?id=40337 Nota sul demone network e le interfacce] -- in inglese<br />
*[http://www.wicd.net/download.php Nota sulle interfacce nel sito ufficiale] -- in inglese<br />
*[http://www.wicd.net/phpbb/viewtopic.php?p=1420 Problema con KDE Autostart] -- in inglese<br />
*[http://www.wicd.net/phpbb/viewtopic.php?f=5&t=263&sid=90b13d4cec6ce6109515532267d39ae0&p=2005 Bugs Conosciuti] -- in inglese</div>OKANhttps://wiki.archlinux.org/index.php?title=Wicd&diff=65153Wicd2009-03-16T20:56:18Z<p>OKAN: </p>
<hr />
<div>[[Category: Networking (English)]]<br />
[[Category: HOWTOs (English)]]<br />
[[Category: Internet and Email (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Wicd}}<br />
{{i18n_entry|Italiano|Wicd (Italiano)}}<br />
{{i18n_entry|简体中文|Wicd (简体中文)}}<br />
{{i18n_entry|Türkçe|Wicd (Türkçe)}}<br />
{{i18n_links_end}}<br />
<br />
=Introduction=<br />
[http://www.wicd.net/ Wicd] is a network connection manager that can manage wireless (a la [[Wifi Radar]]) and wired interfaces, similar and an alternative to [[NetworkManager]]. Wicd is written in Python and [[GTK+]], requiring less dependencies than other network managers.<br />
<br />
=Installation=<br />
== Standard Installation ==<br />
Wicd is available from the standard repositories:<br />
# pacman -S wicd<br />
This will install Wicd and all the necessary dependencies, including <tt>dbus</tt>, <tt>python</tt> and <tt>gtk2</tt>.<br />
<br />
You will likely want DHCP, [[wpa_supplicant|secure wireless management]], and GUI icons as well:<br />
# pacman -S dhclient wpa_supplicant hicolor-icon-theme<br />
<br />
== Other Packages ==<br />
The [http://aur.archlinux.org/packages.php?ID=22923 wicd-bzr] buildscript is available from [[AUR]], which should build the latest development branch.<br />
<br />
If you need an alternative version or you just want to roll your own package, you can easily (re)build it using [[ABS]].<br />
<br />
=Getting Started=<br />
==Initial Setup==<br />
Wicd provides a daemon that must be started before the tool can be used. Also, running multiple network managers ''will'' cause problems, so it is important to ''disable all other network management daemons''.<br />
<br />
First, stop all previously running network daemons:<br />
# /etc/rc.d/network stop<br />
# /etc/rc.d/dhcdbd stop<br />
# /etc/rc.d/networkmanager stop<br />
<br />
Now, edit <tt>/etc/rc.conf</tt> as root:<br />
# nano /etc/rc.conf<br />
<br />
Disable (!) any devices in the INTERFACES array that you wish to manage with Wicd. For example:<br />
INTERFACES=(!eth0 !wlan0)<br />
<br />
Disable (!) any existing network management daemons in the DAEMONS array, including '''network''', '''dhcdbd''', and '''networkmanager'''.<br />
<br />
Now, add '''dbus''' (if not already present) and '''wicd''' to the DAEMONS array, in that order. The DAEMONS array should now look something like this:<br />
DAEMONS=(syslog-ng '''dbus''' !network !dhcdbd !networkmanager '''wicd''' ...)<br />
'''''Note:''' If you use '''hal''', replace '''dbus''' with '''hal''' in DAEMONS array, as the hal daemon will automatically start dbus.''<br />
<br />
Save and close. <br />
<br />
Add your account to <tt>network</tt> group:<br />
# gpasswd -a USERNAME network<br />
<br />
Lastly, start the '''dbus''' and '''wicd''' daemons:<br />
# /etc/rc.d/dbus start<br />
# /etc/rc.d/wicd start<br />
<br />
==Running Wicd==<br />
To load Wicd, run:<br />
$ wicd-client<br />
Or if your desktop environment does not have a notification area, run:<br />
$ wicd-client -n<br />
You can add '''wicd-client''' to your DE/WM startup to have the application start when you log in.<br />
<br />
=Troubleshooting=<br />
== D-BUS ==<br />
If you had ''dbus'' already running, but for some reason ''wicd'' complains about it, restart both.<br />
# /etc/rc.d/dbus stop # we are stopping manually instead of restarting to eliminate possible errors<br />
# /etc/rc.d/wicd stop<br />
# /etc/rc.d/dbus start<br />
# /etc/rc.d/wicd start<br />
== Hidden Wireless Networks and Autoconnection HACK ==<br />
I had problems with my hidden network and the autoconnection function of wicd. It seems that the essid of my hidden network is not "<hidden>", but an empty string. Connect manually to the network and run:<br />
$ iwlist scan<br />
Output of my hidden network:<br />
...<br />
wlan0 Scan completed :<br />
Cell 01 - Address: xx:xx:xx:xx:xx:xx<br />
ESSID:""<br />
Mode:Master<br />
Channel:11<br />
...<br />
If you have the same problems and your iwlist output shows ESSID:"", change /usr/lib/wicd/networking.py:<br />
cd /usr/lib/wicd<br />
sed -i.orig -e 's/if CurrentNetwork\["essid"\] == "<hidden>":/if CurrentNetwork\["essid"\] == "<hidden>" or CurrentNetwork\["essid"\] == "":/' networking.py<br />
This changes /usr/lib/wicd/networking.py and saves a backup of the original file to /usr/lib/wicd/networking.py.orig.<br />
<br />
Based on wicd version 1.4.1-4<br />
<br />
=Related links=<br />
*[http://bbs.archlinux.org/viewtopic.php?id=40337 Note on the network daemon and interfaces]<br />
*[http://www.wicd.net/download.php Note on interfaces at the official site]<br />
*[http://www.wicd.net/phpbb/viewtopic.php?f=5&t=263&sid=90b13d4cec6ce6109515532267d39ae0&p=2005 Common Bugs]</div>OKANhttps://wiki.archlinux.org/index.php?title=Conky_(Italiano)&diff=64706Conky (Italiano)2009-03-09T20:37:34Z<p>OKAN: </p>
<hr />
<div>[[Category:System Monitor]]<br />
[[Category:HOWTOs (Italiano)]]<br />
[[Category:Eye candy (Italiano)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Conky}}<br />
{{i18n_entry|Italiano|Conky (Italiano)}}<br />
{{i18n_entry|Türkçe|Conky (Türkçe)}}<br />
{{i18n_links_end}}<br />
==Introduzione==<br />
Conky è un monitor di sistema per X. É disponibile per Linux e FreeBSD. É un software rilasciato sotto i termini della licenza BSD. Conky è in grado di monitorare molte variabili di sistena come CPU, memoria, swap, spazio su disco, temperatura, top, upload, download, messaggi di sistema, e molto altro (tramite script aggiuntivi per es.). É estramamente configurabile, comunque, la configurazione può essere un pò difficile da capire.Conky è un fork di torsmo.<br />
==Installazione & Configurazione==<br />
*Conky è fornito dal repo extra di pacman<br />
# pacman -S conky<br />
*Editare il file di configurazione usandone uno di esempio preso dagli [http://conky.sourceforge.net/screenshots.html homeproject-screenshots]<br />
$ nano ~/.conkyrc<br />
<br />
==Come prevenire lo sfarfallio==<br />
Conky necessita del supporto Double Buffer Extension (DBE) dal X server per prevenire lo sfarfallio, perchè non può aggiornarsi abbastanza velocemente senza di esso. Può essere abilitato in /etc/X11/xorg.conf aggiungendo Load "dbe" nella Section "Module". Per abilitare anche in conky il double-buffer controlla di avere in ~/.conkyrc<br />
double_buffer yes<br />
==Integrazione con Kdesktop==<br />
Conky con la configurazione screenshot di default causa problemi con la visualizzazione delle icone sul desktop. Per evitarlo basta seguire questi semplici passi<br />
*Aggiungere queste righe a ~/.conkyrc<br />
own_window yes<br />
own_window_type normal<br />
own_window_transparent yes<br />
own_window_hints undecorated,below,sticky,skip_taskbar,skip_page<br />
*Controllare di non avere questa impostazione cancellando la linea o commentandola con #<br />
minimum_size<br />
*Creare questo link simbolico per avere conky al login<br />
$ ln -s /usr/bin/conky ~/.kde/Autostart/conkylink<br />
*Installare feh<br />
# pacman -S feh<br />
*creare questo script per avere trasparenza con feh<br />
$ nano -w ~/.kde/Autostart/fehconky <br />
<br />
#!/bin/bash<br />
feh --bg-scale `dcop kdesktop KBackgroundIface currentWallpaper 1`<br />
usare --bg-center se l'immagine di sfondo è centrata<br />
*Renderlo eseguibile<br />
$ chmod +x ~/.kde/Autostart/fehconky<br />
*Invece di usare uno script potete eventualmente aggiungere queste righe al fondo di .conkyrc<br />
$ nano ~/.conkyrc<br />
<br />
${exec feh --bg-scale `dcop kdesktop KBackgroundIface currentWallpaper 1`}<br />
== Riferimenti Esterni ==<br />
*[http://conky.sourceforge.net/ Official website]<br />
*[http://freshmeat.net/projects/conky/ Conky] on [[wikipedia:Freshmeat|Freshmeat]]<br />
*[http://sourceforge.net/projects/conky/ Conky] on [[wikipedia:sourceforge.net|SourceForge]]<br />
*[irc://chat.freenode.org/conky #conky] IRC chat channel on [[wikipedia:freenode|freenode]]<br />
*[http://novel.evilcoder.org/wiki/index.php/ConkyFAQ FAQ]<br />
<br />
[[User:Wolfanger|Wolfanger]] 03:12, 9 January 2008 (EST)</div>OKANhttps://wiki.archlinux.org/index.php?title=Conky&diff=64705Conky2009-03-09T20:37:19Z<p>OKAN: </p>
<hr />
<div>[[Category:System Monitor]]<br />
[[Category:HOWTOs (English)]]<br />
[[Category:Eye candy (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Conky}}<br />
{{i18n_entry|Italiano|Conky (Italiano)}}<br />
{{i18n_entry|Türkçe|Conky (Türkçe)}}<br />
{{i18n_links_end}}<br />
==Introduction==<br />
Conky is a system monitor software for the X Window System. It is available for Linux and FreeBSD. It is free software released under the terms of the BSD license. Conky is able to monitor many systems variables including CPU, memory, swap, disk space, temperature, top, upload, download, system messages, and much more. It is extremely configurable, however, the configuration can be a little hard to understand. Conky is a fork of torsmo.<br />
<br />
==Installation & Configuration==<br />
*Conky is available in the Extra repository<br />
# pacman -S conky<br />
*Edit config file using an example configuration file from [http://conky.sourceforge.net/screenshots.html homeproject-screenshot]<br />
$ nano ~/.conkyrc<br />
*Alternatively, you can use the default config at '''/etc/xdg/conky/conky.conf'''<br />
$ cp /etc/xdg/conky/conky.conf ~/.conkyrc<br />
<br />
==How to prevent flickering==<br />
Conky needs Double Buffer Extension (DBE) support from X server to prevent flickering, because it can't update window fast enough without it. It can be enabled in /etc/X11/xorg.conf with Load "dbe" line in Section "Module". To enable double-buffer check to have in ~/.conkyrc<br />
double_buffer yes<br />
==Integration with Kdesktop==<br />
Conky with screenshot configuration generate problems with icons visualization. So there are some steps to follow.<br />
*Add these lines to ~/.conkyrc<br />
own_window yes<br />
own_window_type normal<br />
own_window_transparent yes<br />
own_window_hints undecorated,below,sticky,skip_taskbar,skip_page<br />
*if this setting is on, comment it out or delete the line<br />
minimum_size<br />
*To autostart conky create this link<br />
$ ln -s /usr/bin/conky ~/.kde/share/autostart/conkylink<br />
*Install feh<br />
# pacman -S feh<br />
*Make a script to allow transparency with the desktop<br />
For KDE3 users<br />
$ nano -w ~/.kde/share/autostart/fehconky <br />
<br />
#!/bin/bash<br />
feh --bg-scale `dcop kdesktop KBackgroundIface currentWallpaper 1`<br />
For KDE4 users<br />
$ nano -w ~/.kde4/share/autostart/fehconky<br />
<br />
#!/bin/bash<br />
feh --bg-scale "`grep 'wallpaper=' ~/.kde4/share/config/plasma-appletsrc | tail --lines=1 | sed 's/wallpaper=//'`"<br />
use --bg-center if you use a centered wallpaper<br />
*Make it executable<br />
$ chmod +x ~/.kde/share/autostart/fehconky<br />
*Optionally instead using a script you can add the corresponding line to the bottom of .conkyrc<br />
$ nano ~/.conkyrc<br />
For KDE3<br />
${exec feh --bg-scale `dcop kdesktop KBackgroundIface currentWallpaper 1`}<br />
For KDE4<br />
${exec feh --bg-scale "`grep 'wallpaper=' ~/.kde4/share/config/plasma-appletsrc | tail --lines=1 | sed 's/wallpaper=//'`"}<br />
<br />
==How To Display Information About Available Package Updates in Conky==<br />
Take a look at the following threads for scripts to display information about available updates in conky:<br />
*[http://bbs.archlinux.org/viewtopic.php?id=57291 Script to display the number of packages waiting for update.]<br />
*[http://bbs.archlinux.org/viewtopic.php?id=37284 Update notifier in python]<br />
*[http://bbs.archlinux.org/viewtopic.php?id=53761 Scrolling package update notifier]<br />
*[http://bbs.archlinux.org/viewtopic.php?pid=483742#p483742 bash script for users that have enabled ShowSize]<br />
<br />
==How to display a weather forecast in Conky==<br />
See [http://bbs.archlinux.org/viewtopic.php?id=37381 this thread].<br />
<br />
==How To display RSS feeds in Conky==<br />
Conky has the ability to display RSS feeds natively without the need for an outside script to run and output into conky. For example, to display the titles of the ten most recent Planet Arch updates and refresh the feed every minute you would put this into your .conkyrc:<br />
<br />
${rss http://planet.archlinux.org/rss20.xml 1 item_titles 10 }<br />
<br />
== External links ==<br />
*[http://bbs.archlinux.org/viewtopic.php?id=39906 Conky Configs on arch forums]<br />
*[http://conky.sourceforge.net/ Official website]<br />
*[http://freshmeat.net/projects/conky/ Conky] on [[wikipedia:Freshmeat|Freshmeat]]<br />
*[http://sourceforge.net/projects/conky/ Conky] on [[wikipedia:sourceforge.net|SourceForge]]<br />
*[irc://chat.freenode.org/conky #conky] IRC chat channel on [[wikipedia:Freenode|freenode]]<br />
*[http://novel.evilcoder.org/wiki/index.php/ConkyFAQ FAQ]</div>OKANhttps://wiki.archlinux.org/index.php?title=Codecs_(%E6%97%A5%E6%9C%AC%E8%AA%9E)&diff=57816Codecs (日本語)2009-01-14T19:08:16Z<p>OKAN: </p>
<hr />
<div>[[Category:日本語]]<br />
[[Category:Audio/Video (日本語)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Common codecs}}<br />
{{i18n_entry|Ελληνικά|Common codecs (Ελληνικά)}}<br />
{{i18n_entry|简体中文|通用编码解码器}}<br />
{{i18n_entry|Italiano|Common codecs (Italiano)}}<br />
{{i18n_entry|Türkçe|Kodekler}}<br />
{{i18n_links_end}}<br />
<br />
もしも一般的なオーディオ(MP3など)やビデオファイルが再生できないのなら、必要なコーデックがインストールされていないかもしれません。Totem など、'''gstreamer''' を背景とするプレイヤーは種々のコーデックをインストールすることで多くのマルチメディアファイルを再生できます:<br />
<br />
pacman -S codecs gstreamer0.10-bad gstreamer0.10-ugly gstreamer0.10-ffmpeg gstreamer0.10-mad gstreamer0.10-mpeg2dec<br />
<br />
gstreamer のすべてのコーデックをインストールする場合は以下のコマンドを実行します:<br />
pacman -Sy codecs `pacman -Ss gstreamer | grep -e '^extra/gstreamer0.10' | awk '{print $1}'`<br />
<br />
Totem で再生できないファイルに対応するには '''VLC''' というプレイヤーをインストールしてください。<br />
<br />
pacman -S vlc<br />
<br />
'''Mplayer''' も多くのファイルが再生可能です。VLC で再生できないファイルに対応している場合もあります。<br />
<br />
pacman -S mplayer<br />
<br />
Mplayer にはブラウザのプラグインが在ります:<br />
<br />
pacman -S mplayer-plugin</div>OKANhttps://wiki.archlinux.org/index.php?title=Codecs_and_containers_(Italiano)&diff=57815Codecs and containers (Italiano)2009-01-14T19:07:59Z<p>OKAN: </p>
<hr />
<div>[[Category:Audio/Video (Italiano)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Common codecs}}<br />
{{i18n_entry|简体中文|通用编码解码器}}<br />
{{i18n_entry|Italiano|Common codecs (Italiano)}}<br />
{{i18n_entry|Türkçe|Kodekler}}<br />
{{i18n_links_end}}<br />
<br />
=Codecs=<br />
Se si riscontrano problemi nell'apertura di file audio (es. mp3) o video, la causa più probabile è l'assenza nel vostro sistema dei codecs che servono per l'apertura dei suddetti file. I player che utilizzano '''gstreamer''' (come Totem) saranno in grado di funzionare correttamente, con i file multimediali più comuni, dopo aver installato:<br />
<br />
<pre><br />
# pacman -Sy codecs gstreamer0.10-bad gstreamer0.10-ugly gstreamer0.10-ffmpeg gstreamer0.10-ugly-plugins<br />
</pre><br />
<br />
Se si vogliono invece installare tutti i codec '''gstreamer''', si può utilizzare il seguente comando (è necessario avere il pacchetto awk installato):<br />
<br />
<pre><br />
# pacman -Sy codecs `pacman -Ss gstreamer | grep -e '^extra/gstreamer0.10' | awk '{print $1}'`<br />
</pre><br />
<br />
=Players=<br />
E' ancora possibile che qualche file (specialmente file video Windows) non sia mostrato correttamente da Totem. In tal caso '''VLC''' è una buona soluzione, in quanto utilizza i propri codecs che spesso funzionano anche per file meno comuni, o per DVD video con menu.<br />
Per installarlo e sufficiente eseguire:<br />
<br />
<pre><br />
# pacman -Sy vlc<br />
</pre><br />
<br />
In alternativa, un altro programma interessante è mplayer (personalmente lo ritengo il miglior player a disposizione su linux). Spesso capita che mplayer riesca a leggere file che ancheper VLC sono inleggibili. E' inoltre disponibile un utilissimo plugin per browser.<br />
Per installare mplayer e il relativo plugin:<br />
<br />
<pre><br />
# pacman -Sy mplayer mplayer-plugin<br />
</pre></div>OKANhttps://wiki.archlinux.org/index.php?title=Codecs_and_containers_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=57814Codecs and containers (简体中文)2009-01-14T19:07:50Z<p>OKAN: </p>
<hr />
<div>[[Category:音频/视频|TYJMQ]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Common codecs}}<br />
{{i18n_entry|简体中文|通用编码解码器}}<br />
{{i18n_entry|Italiano|Common codecs (Italiano)}}<br />
{{i18n_entry|Türkçe|Kodekler}}<br />
{{i18n_links_end}}<br />
<br />
<br />
如果你发现你不能播放常用的音频(比如MP3)或者视频文件,你可能没有安装正确的解码器来播放。媒体播放器使用 '''gstreamer''' 作为后端(比如Totem) 可以播放绝大部分多媒体文件,安装如下解码器后:<br />
<br />
pacman -S codecs gstreamer0.10-bad gstreamer0.10-ugly gstreamer0.10-ffmpeg gstreamer0.10-mad gstreamer0.10-mpeg2dec<br />
<br />
如果你想要安装所有的gstreamer解码器,你可以使用以下命令(假设你已经安装了awk):<br />
<br />
pacman -Sy codecs `pacman -Ss gstreamer | grep -e '^extra/gstreamer0.10' | awk '{print $1}'`<br />
<br />
你可能发现Totem不能正常播放一些文件(尤其是Windows视频文件) 。 '''VLC''' 是一个多功能的拥有很多自己的解码器的媒体播放器,能够很好的播放一些不常见的视频文件,或者带有菜单的DVD电影。<br />
<br />
pacman -S vlc<br />
<br />
Mplayer 也能够播放很多文件。它甚至能播放VLC不能播放的文件。<br />
<br />
pacman -S mplayer <br />
<br />
网页上音频视频播放请安装mplayer-plugin。<br />
<br />
pacman -S mplayer-plugin</div>OKANhttps://wiki.archlinux.org/index.php?title=Codecs_and_containers_(%CE%95%CE%BB%CE%BB%CE%B7%CE%BD%CE%B9%CE%BA%CE%AC)&diff=57813Codecs and containers (Ελληνικά)2009-01-14T19:07:39Z<p>OKAN: </p>
<hr />
<div>[[Category:Ήχος/Βίντεο (Ελληνικά)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Common codecs}}<br />
{{i18n_entry|Ελληνικά|Common codecs (Ελληνικά)}}<br />
{{i18n_entry|简体中文|通用编码解码器}}<br />
{{i18n_entry|Italiano|Common codecs (Italiano)}}<br />
{{i18n_entry|Türkçe|Kodekler}}<br />
{{i18n_links_end}}<br />
<br />
Αν δεν μπορείτε να παίξετε ένα συνηθισμένο αρχείο μουσικής (όπως το MP3) ή ακόμη και αρχεία βίντεο, μπορεί να μην έχετε τους κατάλληλους codecs εγκατεστημένους.Πολλοί media players που χρησιμοποιούν το '''gstreamer''' (όπως ο Totem) θα μπορέσουν να αναπαραγάγουν κάθε αρχείο πολυμέσων με τους παρακάτω codecs:<br />
<br />
pacman -S codecs gstreamer0.10-bad gstreamer0.10-ugly gstreamer0.10-ffmpeg gstreamer0.10-mad gstreamer0.10-mpeg2dec<br />
<br />
Αν θέλετε να εγκαταστήσετε όλους τους gstreamer codecs, μπορείτε να χρησιμοποιήσετε την παρακάτω εντολή (δεδομένου ότι έχετε εγκαταστήσει το awk στον υπολογιστή σας):<br />
<br />
pacman -Sy codecs `pacman -Ss gstreamer | grep -e '^extra/gstreamer0.10' | awk '{print $1}'`<br />
<br />
Μερικά όμως αρχεία (ειδικά τα αρχεία βίντεο των windows) δεν παίζουν στον Totem. O '''VLC''' είναι ικανός να κάνει αναπαραγωγή αυτών των βίντεο χάρη στους codecs που ενσωματώνει,καθώς και πολλές ταινίες DVD.<br />
<br />
pacman -S vlc<br />
<br />
Ο Mplayer αναπαραγάγει αρκετά αρχεία. Επίσης μερικές φορές παίζει και αρχεία που δεν μπορούν να αναπαραχθούν από τον VLC.<br />
<br />
pacman -S mplayer<br />
<br />
Υπάρχει επίσης μια πρόσθετη λειτουργία του mplayer το mplayer-plugin κατάλληλο για αναπαραγωγή πολυμέσων μέσα από τους browsers,μπορείτε να το κάνετε εγκατάσταση με:<br />
<br />
pacman -S mplayer-plugin</div>OKANhttps://wiki.archlinux.org/index.php?title=Codecs_and_containers_(Espa%C3%B1ol)&diff=57812Codecs and containers (Español)2009-01-14T19:07:26Z<p>OKAN: </p>
<hr />
<div>[[Category:Audio/Video (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Common codecs}}<br />
{{i18n_entry|Español|Common codecs (Español)}}<br />
{{i18n_entry|Ελληνικά|Common codecs (Ελληνικά)}}<br />
{{i18n_entry|简体中文|通用编码解码器}}<br />
{{i18n_entry|Italiano|Common codecs (Italiano)}}<br />
{{i18n_entry|日本語|一般的なコーデック (日本語)}}<br />
{{i18n_entry|Türkçe|Kodekler}}<br />
{{i18n_links_end}}<br />
<br />
<br />
Si no puedes reproducir archivos de audio comunes (como MP3) o videos, podrias no tener los codecs instalados para reproducirlos. Los reproductores que usan '''gstreamer''' como backend (por ejemplo Totem) seran capaces de reproducir la mayoria de los archivos multimedia despues de instalar los siguientes codecs:<br />
<br />
pacman -S codecs gstreamer0.10-bad gstreamer0.10-ugly gstreamer0.10-ffmpeg gstreamer0.10-ugly-plugins<br />
<br />
Si quieres instalar todos los codecs gstreamer, puedes usar el siguiente comando (asumiendo que tienes awk instalado):<br />
<br />
pacman -Sy codecs `pacman -Ss gstreamer | grep -e '^extra/gstreamer0.10' | awk '{print $1}'`<br />
<br />
Podrias aun tener algunos problemas reproduciendo otra clase de media (especialmente archivos de video de Windows) con Totem. '''VLC''' es una gran alternativa que incluye sus propios codecs, y puede reproducir casi cualqueir cosa, asi como peliculas en DVD con menus.<br />
<br />
pacman -S vlc<br />
<br />
Mplayer tambien reproduce varios tipos de archivo.<br />
<br />
pacman -S mplayer<br />
<br />
Incluso podrias instalar un util plugin de Mplayer que te permitira integrarlo en los navegadores web, instalalo asi:<br />
<br />
pacman -S mplayer-plugin</div>OKANhttps://wiki.archlinux.org/index.php?title=Codecs_and_containers&diff=57811Codecs and containers2009-01-14T19:07:12Z<p>OKAN: </p>
<hr />
<div>[[Category:Audio/Video (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Common codecs}}<br />
{{i18n_entry|Español|Common codecs (Español)}}<br />
{{i18n_entry|Ελληνικά|Common codecs (Ελληνικά)}}<br />
{{i18n_entry|简体中文|通用编码解码器}}<br />
{{i18n_entry|Italiano|Common codecs (Italiano)}}<br />
{{i18n_entry|日本語|一般的なコーデック (日本語)}}<br />
{{i18n_entry|Türkçe|Kodekler}}<br />
{{i18n_links_end}}<br />
<br />
<br />
If you find that you cannot play common audio (such as MP3) or video files, you might not have the correct codecs installed to play them. Media players using the '''gstreamer''' backend (such as Totem) will be able to play most multimedia files after installing these codecs:<br />
<br />
pacman -S codecs gstreamer0.10-bad gstreamer0.10-ugly gstreamer0.10-ffmpeg gstreamer0.10-ugly-plugins<br />
<br />
If you want to install ALL gstreamer codecs, you can you use the following command (assuming that you have awk installed):<br />
<br />
pacman -Sy codecs `pacman -Ss gstreamer | grep -e '^extra/gstreamer0.10' | awk '{print $1}'`<br />
<br />
You may still find that some files (especially Windows video files) won't play properly in Totem. '''VLC''' is a multipurpose media player which has many of its own codecs and can handle the tricky video files, as well as DVD movies with menus.<br />
<br />
pacman -S vlc<br />
<br />
Mplayer also plays many files. I have found that sometimes it will play things that won't play in VLC.<br />
<br />
pacman -S mplayer<br />
<br />
There also is a usefull mplayer plugin to integrate mplayer into browsers, install it with:<br />
<br />
pacman -S mplayer-plugin</div>OKANhttps://wiki.archlinux.org/index.php?title=SLiM_(Italiano)&diff=57810SLiM (Italiano)2009-01-14T19:06:32Z<p>OKAN: </p>
<hr />
<div>[[Category:Display managers (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|SLiM}}<br />
{{i18n_entry|简体中文|SLIM (简体中文)}}<br />
{{i18n_entry|Italiano|SLiM (Italiano)}}<br />
{{i18n_entry|Türkçe|SLIM(Türkçe)}}<br />
{{i18n_links_end}}<br />
<br />
=Introduzione=<br />
SLiM è l'acronimo di Simple Login Manager (semplice gestore di login). SLiM è un login manager semplice, leggero e facilmente configurabile, adatto per essere usato su piattaforme con poche risorse. SLiM è molto utile anche a chi vuole un login manager che non dipenda da gnome o kde, ed è perfetto per chi usa xfce, openbox fluxboc ecc.<br />
<br />
=Installazione=<br />
SLiM è installabile dai repo /extra:<br />
# pacman -S slim<br />
E c'è anche un pacchetto per i temi<br />
# pacman -S slim-themes<br />
<br />
=Configurazione=<br />
<br />
==Abilitare SLiM==<br />
Vedi [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]].<br />
<br />
==Singolo ambiente desktop==<br />
<br />
Per configurare SLiM per caricare un particolare ambiente, basta semplicemente editare il file ~./xinitrc, in modo che sia simile al seguente:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
exec [session-command]<br />
</pre><br />
<br />
*Nota: se non hai un file ~./xinitrc, ne puoi creare uno (per esempio con nano)<br />
<br />
Sostituisci '''''[session-command]''''' con il comando appropriato. Per esempio:<br />
<br />
Per lanciare Openbox:<br />
# Openbox<br />
exec openbox-session<br />
Per lanciare Fluxbox:<br />
# Fluxbox<br />
exec fluxbox<br />
# Either fluxbox or startfluxbox is acceptable<br />
Per lanciare Xfce:<br />
# Xfce<br />
exec startxfce4<br />
Per lanciare GNOME:<br />
# GNOME<br />
exec gnome-session<br />
Per lanciare KDE:<br />
# KDE<br />
exec startkde<br />
Se l'ambiente utilizzato non è elencato qui, fare riferimento alla documentazione del software.<br />
<br />
==Ambienti multipli==<br />
Se si ha il bisogno di caricare più ambienti desktop, SLiM può essere configurato in modo da poter scegliere quale.<br />
<br />
Put a case statement similar to this one in your /etc/X11/xinit/xinitrc file and edit the sessions variable in /etc/slim.conf. <br />
You can choose the session at login time by pressing F1. Note that this feature is experimental<br />
<br />
<pre><br />
# The following variable defines the session which is started if the user doesn't explicitly select a session<br />
<br />
DEFAULT_SESSION=twm<br />
<br />
case $1 in<br />
kde)<br />
exec startkde<br />
;;<br />
xfce4)<br />
exec startxfce4<br />
;;<br />
icewm)<br />
icewmbg &<br />
icewmtray &<br />
exec icewm<br />
;;<br />
wmaker)<br />
exec wmaker<br />
;;<br />
blackbox)<br />
exec blackbox<br />
;;<br />
*)<br />
exec $DEFAULT_SESSION<br />
;;<br />
esac<br />
</pre><br />
<br />
Source for sample: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample<br />
<br />
Slim documentation: http://slim.berlios.de/manual.php<br />
<br />
==Themes==<br />
<br />
Install the slim-themes package:<br />
<br />
pacman -S slim-themes archlinux-themes-slim<br />
<br />
Edit the current_theme line in /etc/slim.conf from "default" to one of your choice: <br />
nano /etc/slim.conf<br />
<br />
#current_theme default<br />
current_theme archlinux<br />
(Slim-themes located in /usr/share/slim/themes)<br />
<br />
To preview a theme, run:<br />
<br />
slim -p /usr/share/slim/themes/<theme name><br />
<br />
= Tips & Tricks =<br />
==Slim and Desktop share a theme==<br />
A simple way of sharing wallpaper between Slim and your desktop is to create a symbolic link from your desktop wallpaper file to the default Slim theme:<br />
mv /usr/share/slim/themes/default/background.jpg /usr/share/slim/themes/default/background.old.jpg<br />
ln -s /path/to/mywallpaper.jpg /usr/share/slim/themes/default/background.jpg<br />
Now your Slim theme and desktop wallpaper will be the same, smoothing the transition while loading the desktop. (Obviously you must keep the default theme setting in /etc/slim.conf for the above trick to work.)<br />
<br />
==Shutdown, Reboot, Suspend, Exit, Launch Terminal from SLiM==<br />
You may shutdown, reboot, suspend, exit or even launch a terminal from the SLiM login screen. To do so, enter the appropriate value in the username field, and the root password in the password field:<br />
<br />
*To launch a terminal, enter '''console''' as the username (defaults to xterm which must be installed separately... edit <tt>/etc/slim.conf</tt> to change terminal preference)<br />
<br />
*For shutdown, enter '''halt''' as the username<br />
<br />
*For reboot, enter '''reboot''' as the username<br />
<br />
*To exit to bash, enter '''exit''' as the username<br />
<br />
*For suspend, enter '''suspend''' as the username (Suspend is disabled by default, edit <tt>/etc/slim.conf</tt> as root to uncomment the <tt>suspend_cmd</tt> line and, if necessary modify the suspend command itself (e.g. change '''''/usr/sbin/suspend''''' to '''''sudo /usr/sbin/pm-suspend'''''))<br />
<br />
= Weblinks =<br />
[http://slim.berlios.de/ SLiM homepage]</div>OKANhttps://wiki.archlinux.org/index.php?title=SLiM_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=57809SLiM (简体中文)2009-01-14T19:02:25Z<p>OKAN: </p>
<hr />
<div>[[Category:简体中文]]<br />
[[Category:显示管理器]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|SLIM}}<br />
{{i18n_entry|简体中文|SLIM (简体中文)}}<br />
{{i18n_entry|Türkçe|SLIM(Türkçe)}}<br />
{{i18n_links_end}}<br />
<br />
=介绍=<br />
SLiM是'''S'''imple '''L'''og'''i'''n '''M'''anager(简单登录管理器)的缩写。SLiM是简单、轻量级和容易配置的,相对较易在低端和高端的系统中使用。对于那些希望寻找一个不依赖于GNOME或者KDE,可以在Xfce、Openbox、Fluxbox等环境下使用的登录管理器的人来说,SLiM也是非常合适的。<br />
<br />
=安装=<br />
可以在extra软件仓库中找到SLiM:<br />
# pacman -S slim<br />
同时还可以安装主题包:<br />
# pacman -S slim-themes archlinux-themes-slim<br />
<br />
=配置=<br />
<br />
==启用SLiM==<br />
请参考[[在启动时自动启动一个登录管理器(KDM, GDM, or XDM)]].<br />
<br />
==单用户环境==<br />
<br />
要将SLiM配置为加载某个特定的环境,只需编辑'''~/.xinitrc'''如下:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
exec [session-command]<br />
</pre><br />
<br />
*注意:如果你没有~/.xinitrc文件,可以用nano之类的编辑器创建一个。<br />
<br />
将'''''[session-command]'''''替换为适当的会话命令。例如:<br />
<br />
要启动Openbox:<br />
# Openbox<br />
exec openbox-session<br />
要启动Fluxbox:<br />
# Fluxbox<br />
exec fluxbox<br />
# Either fluxbox or startfluxbox is acceptable<br />
要启动Xfce:<br />
# Xfce<br />
exec startxfce4<br />
要启动GNOME:<br />
# GNOME<br />
exec gnome-session<br />
要启动KDE:<br />
# KDE<br />
exec startkde<br />
如果你的桌面环境不在上述列表中,请参考你的软件文档。<br />
<br />
==多用户环境==<br />
如果你希望可以加载多个不同的桌面环境,SLiM可以设置为登录到你指定的任何一个桌面环境。<br />
<br />
在你的/etc/X11/xinit/xinitrc文件中加入一段类似下面内容的case语句,并且编辑/etc/slim.conf中的sessions变量。 <br />
你可以在登录界面上按F1选择会话。请注意这个特性仍处于实验阶段。<br />
<br />
<pre><br />
# The following variable defines the session which is started if the user doesn't explicitly select a session<br />
<br />
DEFAULT_SESSION=twm<br />
<br />
case $1 in<br />
kde)<br />
exec startkde<br />
;;<br />
xfce4)<br />
exec startxfce4<br />
;;<br />
icewm)<br />
icewmbg &<br />
icewmtray &<br />
exec icewm<br />
;;<br />
wmaker)<br />
exec wmaker<br />
;;<br />
blackbox)<br />
exec blackbox<br />
;;<br />
*)<br />
exec $DEFAULT_SESSION<br />
;;<br />
esac<br />
</pre><br />
<br />
范例源码: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample<br />
<br />
SLiM的文档: http://slim.berlios.de/manual.php<br />
<br />
==主题==<br />
<br />
安装slim-themes软件包:<br />
<br />
pacman -S slim-themes<br />
<br />
编辑/etc/slim.conf中的current_theme那行,将"default"改为你想要的主题名: <br />
nano /etc/slim.conf<br />
<br />
#current_theme default<br />
current_theme archlinux<br />
(Slim-themes位于/usr/share/slim/themes)<br />
<br />
要预览一个主题,可以运行<br />
<br />
slim -p /usr/share/slim/themes/<theme name><br />
<br />
= 技巧 =<br />
==在SLiM里关机、重启、挂起、退出、执行终端程序==<br />
你也可以在SLiM登录界面里关闭、重启、挂起、退出甚至执行终端程序。要做的是:在在username区域输入恰当命令,然后在password区域输入root的密码:<br />
<br />
*要执行终端程序,输入'''console'''作为用户名(缺省执行的是xterm,它必须要单独安装...编辑<tt>/etc/slim.conf</tt>可以修改终端参数)<br />
<br />
*要关机,可以输入'''halt'''作为用户名。<br />
<br />
*要重启,可以输入'''reboot'''作为用户名。<br />
<br />
*要退回到bash,可以输入'''exit'''作为用户名。<br />
<br />
*要挂起,可以输入'''suspend'''作为用户名(挂起功能缺省是关闭的,以root身份编辑<tt>/etc/slim.conf</tt>,取消<tt>suspend_cmd</tt>行的注释,如果需要的话还可以修改挂起所用的命令(例如将'''''/usr/sbin/suspend'''''改为'''''sudo /usr/sbin/pm-suspend''''')。</div>OKANhttps://wiki.archlinux.org/index.php?title=SLiM&diff=57808SLiM2009-01-14T19:02:06Z<p>OKAN: </p>
<hr />
<div>[[Category:Display managers (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|SLIM}}<br />
{{i18n_entry|简体中文|SLIM (简体中文)}}<br />
{{i18n_entry|Italiano|SLiM (Italiano)}}<br />
{{i18n_entry|Türkçe|SLIM(Türkçe)}}<br />
{{i18n_links_end}}<br />
<br />
=Introduction=<br />
'''SLiM''' is an acronym for Simple Login Manager (SLiM). SLiM is simple, lightweight and easily configurable allowing it be used on low and high end systems with relative ease. SLiM is also very convenient for those who want a login manager without the dependencies of Gnome or KDE making it perfect for users running Xfce, Openbox, Fluxbox, etc. <br />
<br />
=Installation=<br />
SLiM is available from the /extra repositories:<br />
# pacman -S slim<br />
There is also a themes package:<br />
# pacman -S slim-themes<br />
<br />
=Configuration=<br />
<br />
==Enabling SLiM==<br />
Refer to [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]].<br />
<br />
==Single Environments==<br />
<br />
To configure SLiM to load a particular environment, simply edit '''~/.xinitrc''' to look like the following:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
exec [session-command]<br />
</pre><br />
<br />
*Note: If you do not have have a ~/.xinitrc file, you can create one (with, for example, nano).<br />
<br />
Replace '''''[session-command]''''' with the appropriate session command. For example:<br />
*To launch Openbox: "<code>exec openbox-session</code>"<br />
*To launch Fluxbox: either "<code>exec fluxbox</code>" or "<code>exec startfluxbox</code>"<br />
*To launch Xfce: "<code>exec startxfce4</code>"<br />
*To launch GNOME: "<code>exec gnome-session</code>"<br />
*To launch KDE: "<code>exec startkde</code>"<br />
<br />
If your environment is not listed here, refer to the documentation provided by your software.<br />
<br />
==Multiple Environments==<br />
If you require the ability to load multiple desktop environments, SLiM can be setup to log you into whichever you choose.<br />
<br />
Put a case statement similar to this one in your ~/.xinitrc file and edit the sessions variable in /etc/slim.conf to match the names that trigger the case statement. <br />
You can choose the session at login time by pressing F1. Note that this feature is experimental.<br />
<br />
<pre><br />
# The following variable defines the session which is started if the user doesn't explicitly select a session<br />
<br />
DEFAULT_SESSION=twm<br />
<br />
case $1 in<br />
kde)<br />
exec startkde<br />
;;<br />
xfce4)<br />
exec startxfce4<br />
;;<br />
icewm)<br />
icewmbg &<br />
icewmtray &<br />
exec icewm<br />
;;<br />
wmaker)<br />
exec wmaker<br />
;;<br />
blackbox)<br />
exec blackbox<br />
;;<br />
*)<br />
exec $DEFAULT_SESSION<br />
;;<br />
esac<br />
</pre><br />
<br />
Source for sample: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample<br />
<br />
Slim documentation: http://slim.berlios.de/manual.php<br />
<br />
==Themes==<br />
Install the slim-themes package:<br />
# pacman -S slim-themes archlinux-themes-slim<br />
<br />
The <tt>archlinux-themes-slim</tt> packages contains several different themes. Check <tt>/usr/share/slim/themes</tt> to see the available variations and other themes available.<br />
<br />
Edit the current_theme line in /etc/slim.conf from "default" to one of your choice: <br />
# nano /etc/slim.conf<br />
<br />
#current_theme default<br />
current_theme archlinux-simplyblack<br />
<br />
To preview a theme, run:<br />
slim -p /usr/share/slim/themes/<theme name><br />
<br />
= Tips & Tricks =<br />
==Changing the cursor==<br />
If you don't like the "X" cursor and you want to change it to, for example, an arrow, use the [http://aur.archlinux.org/packages.php?ID=21053 slim-cursor package from AUR].<br />
<br />
After installing, edit /etc/slim.conf and uncomment the line:<br />
cursor left_ptr<br />
This will give you a normal arrow instead. This setting is forwarded to xsetroot -cursor_name. You can look up the possible cursor names [http://cvsweb.xfree86.org/cvsweb/*checkout*/xc/lib/X11/cursorfont.h?rev=HEAD&content-type=text/plain here] or in /usr/share/icons/<your-cursor-theme>/cursors/.<br />
<br />
To change the cursor theme being used at the login screen, make a file named /usr/share/icons/default/index.theme with this content:<br />
[Icon Theme]<br />
Inherits=<your-cursor-theme><br />
Replace <your-cursor-theme> with the name of the cursor theme you want to use, e.g. whiteglass.<br />
<br />
==Slim and Desktop share a theme==<br />
A simple way of sharing wallpaper between Slim and your desktop is to create a symbolic link from your desktop wallpaper file to the default Slim theme:<br />
# mv /usr/share/slim/themes/default/background.jpg /usr/share/slim/themes/default/background.old.jpg<br />
# ln -s /path/to/mywallpaper.jpg /usr/share/slim/themes/default/background.jpg<br />
Now your Slim theme and desktop wallpaper will be the same, smoothing the transition while loading the desktop. (Obviously you must keep the default theme setting in /etc/slim.conf for the above trick to work.)<br />
<br />
==Shutdown, Reboot, Suspend, Exit, Launch Terminal from SLiM==<br />
You may shutdown, reboot, suspend, exit or even launch a terminal from the SLiM login screen. To do so, enter the appropriate value in the username field, and the root password in the password field:<br />
<br />
* To launch a terminal, enter '''console''' as the username (defaults to xterm which must be installed separately... edit <tt>/etc/slim.conf</tt> to change terminal preference)<br />
* For shutdown, enter '''halt''' as the username<br />
* For reboot, enter '''reboot''' as the username<br />
* To exit to bash, enter '''exit''' as the username<br />
* For suspend, enter '''suspend''' as the username (Suspend is disabled by default, edit <tt>/etc/slim.conf</tt> as root to uncomment the <tt>suspend_cmd</tt> line and, if necessary modify the suspend command itself (e.g. change '''''/usr/sbin/suspend''''' to '''''sudo /usr/sbin/pm-suspend'''''))<br />
<br />
==Setting DPI with Slim==<br />
If you set the DPI with the argument -dpi 96 in /etc/X11/xinit/xserverrc it will not work with slim. To fix this edit your slim.conf from:<br />
xserver_arguments -nolisten tcp vt07 <br />
to<br />
xserver_arguments -nolisten tcp vt07 -dpi 96<br />
<br />
= Weblinks =<br />
*[http://slim.berlios.de/ SLiM homepage]</div>OKAN