https://wiki.archlinux.org/api.php?action=feedcontributions&user=Rh995&feedformat=atomArchWiki - User contributions [en]2024-03-29T14:51:12ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Lenovo_ThinkPad_X250&diff=378133Lenovo ThinkPad X2502015-06-11T03:26:48Z<p>Rh995: /* Mouse */ Updated for recent Linux kernels.</p>
<hr />
<div>[[Category:Lenovo]]<br />
The Lenovo ThinkPad X250 is the successor to the [[Lenovo ThinkPad X240]]. Major differences include the physical TrackPoint buttons above the touchpad mouse as well as the Broadwell line of Intel CPUs. <br />
<br />
==== Tested Configuration ====<br />
{{Tip|Below were the tested configurations at the current time.}}<br />
{| class="wikitable sortable"<br />
! Feature !! Configuration<br />
|-<br />
|System||X250<br />
|-<br />
|CPU||Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz<br />
|-<br />
|Graphics||Intel HD 5400 - Broadwell<br />
|-<br />
|Ram||8 GB <br />
|-<br />
|Disk||180 GB Solid State Drive Opal 2.0 - XCapable<br />
|-<br />
|Display||12.5" IPS FHD (1920x1080) non-touch<br />
|-<br />
|Wireless||Intel Corporation Wireless 7265<br />
|-<br />
|Built-in Battery||9 Cell<br />
|-<br />
|Additional Plugable Battery||6 Cell 19+<br />
|-<br />
|Backlight Keyboard||Yes<br />
|-<br />
|ThinkLight||No<br />
|-<br />
|Fingerprint Scanner||Yes<br />
|-<br />
|Bluetooth||Yes<br />
|-<br />
|Camera||Yes<br />
|}<br />
<br />
=== System Configuration ===<br />
<br />
==== Mouse ====<br />
<br />
The touchpad and TrackPoint work out of the box, but the physical buttons for the trackpoint do not. You will need to install {{Pkg|xf86-input-synaptics}}.<br />
<br />
{{Note|The most recent Linux kernels (at least 4.0.5) support TrackPoint buttons out of the box. The following information pertains only to older versions of the kernel.}}<br />
If you would rather not install a recent kernel, there is a work around for Linux 3.19.2-ARCH. If you add {{ic|1=options psmouse proto=imps}} to {{ic|/etc/modprobe.d/x250.conf}}, you can force the mouse module to use a more basic protocol than the built in one for the TrackPoint, which needs a patch. The effect is that the touchpad and mouse are treated as one device, but synaptics is not supported. If you want two finger scrolling, for example, you will need to either deal with the broken TrackPoint buttons are install the new module.<br />
<br />
==== Fingerprint ====<br />
<br />
The fingerprint reader works out of the box with {{Pkg|fprintd}}.<br />
<br />
==== Backlight and Keyboard ====<br />
<br />
In order to get the backlight to work, I added {{ic|1=options thinkpad_acpi force-load=1}} to {{ic|/etc/modprobe.d/x250.conf}}. This forces the thinkpad_acpi module to load, which is needed for controlling the backlight vPkgia {{Pkg|xorg-xbacklight}} as well as enable some of the extra media keys. <br />
<br />
==== Sound and Volume Control ====<br />
<br />
With {{Pkg|acpid}} and {{Pkg|alsa-utils}} installed, you can map the volume buttons to change the volume. Here are some samples:<br />
<br />
{{ic|/etc/acpi/events/volumemute}}:<br />
<br />
event=button/mute<br />
action=amixer -c 1 sset Master toggle -q<br />
<br />
{{ic|/etc/acpi/events/volumedown}}:<br />
<br />
event=button/volumedown<br />
action=amixer -c 1 sset -M Master 5%%- unmute -q<br />
<br />
{{ic|/etc/acpi/events/volumeup}}:<br />
<br />
event=button/volumeup<br />
action=amixer -c 1 sset -M Master 5%%+ unmute -q<br />
<br />
{{ic|/etc/acpi/events/mutemic}}:<br />
<br />
event=button/f20<br />
action=amixer -c 1 sset Mic toggle -q<br />
<br />
[[PulseAudio]] and {{Pkg|pavucontrol}} are also great tools for fixing volume issues.<br />
<br />
==== Bluetooth ====<br />
<br />
Bluetooth was not tested.</div>Rh995https://wiki.archlinux.org/index.php?title=Talk:Chromium&diff=333506Talk:Chromium2014-09-02T02:29:55Z<p>Rh995: </p>
<hr />
<div>Should the bit about chromium and its pdf plugins be removed, because it appears that in the most recent version, libpdf.so is build in? I am posting here because I don't know if perhaps it should just be edited, rather than removed altogether.<br />
[[User:Rh995|Rh995]] ([[User talk:Rh995|talk]]) 02:29, 2 September 2014 (UTC)</div>Rh995https://wiki.archlinux.org/index.php?title=Octave&diff=297998Octave2014-02-16T06:11:23Z<p>Rh995: /* Plotting */</p>
<hr />
<div>[[Category:Mathematics and science]]<br />
{{Article summary start}}<br />
{{Article summary text|This article contains information about the installation, configuration and use of GNU Octave.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Matlab}}<br />
{{Article summary wiki|Sage-mathematics}}<br />
{{Article summary wiki|Mathematica}}<br />
{{Article summary end}}<br />
From the [http://www.gnu.org/software/octave/ official website]:<br />
<br />
:''GNU Octave is a high-level interpreted language, primarily intended for numerical computations. It provides capabilities for the numerical solution of linear and nonlinear problems, and for performing other numerical experiments. It also provides extensive graphics capabilities for data visualization and manipulation. Octave is normally used through its interactive command line interface, but it can also be used to write non-interactive programs. The Octave language is quite similar to Matlab so that most programs are easily portable.''<br />
<br />
== Installation ==<br />
Octave can be [[Pacman|installed]] with the package {{Pkg|octave}}, available in the [[official repositories]].<br />
<br />
== Octave-Forge ==<br />
<br />
Octave provides a set of packages, similar to Matlab's Toolboxes, through [http://octave.sourceforge.net/index.html Octave-Forge]. The complete list of packages is [http://octave.sourceforge.net/packages.php here].<br />
<br />
Packages can be installed directly in Octave, or from the AUR. See below.<br />
<br />
=== Using Octave's installer ===<br />
<br />
Packages can also be managed using Octave's installer. They are installed to ~/octave, or in a system directory with the -global option. To install a package:<br />
<br />
octave:1> pkg install -forge packagename<br />
<br />
To uninstall a package:<br />
<br />
octave:3> pkg uninstall packagename<br />
<br />
Some packages get loaded automatically by Octave, for those which do not:<br />
<br />
octave:4> pkg load packagename<br />
<br />
or<br />
<br />
octave:5> pkg load all<br />
<br />
To see which packages have been loaded use {{ic|pkg list}}, the packages with an asterisk are the ones that are already loaded.<br />
<br />
<br />
A way to make sure that all packages gets loaded at Octave startup:<br />
<br />
{{hc|/usr/share/octave/site/m/startup/octaverc|<br />
## System-wide startup file for Octave.<br />
##<br />
## This file should contain any commands that should be executed each<br />
## time Octave starts for every user at this site. <br />
pkg load all}}<br />
<br />
=== Using the AUR ===<br />
<br />
Some packages may be found in the AUR ([https://aur.archlinux.org/packages.php?O=0&K=octave-&do_Search=Go search packages]). New Octave-forge packages for Arch can be created semi-automatically using the [https://github.com/drizzd/octave-forge-archlinux#readme Octave-forge helper scripts for Archlinux].<br />
<br />
== Plotting ==<br />
<br />
Octave has two official plotting backends:<br />
* {{App|[[Wikipedia:Gnuplot|Gnuplot]]|A classic Linux plotting utility.|http://www.gnuplot.info/|{{Pkg|gnuplot}}}}<br />
* {{App|FLTK Backend|A new experimental OpenGL backend based on the [[Wikipedia:FLTK|FLTK]] GUI toolkit.|http://www.gnu.org/software/octave/|{{Pkg|octave}}}}<br />
{{Note|To enable the FLTK backend, you need to install the {{Pkg|fltk}} package. This package now comes as a dependency of octave.}}<br />
<br />
FLTK is now the default plotting utility, but due to some serious problems with the experimental interface, you may want to re-enable gnuplot.<br />
<br />
octave:1> graphics_toolkit("gnuplot");<br />
<br />
To make this change permanent add it to your {{ic|~/.octaverc}} file.<br />
<br />
== Graphical interfaces ==<br />
Since Octave 3.8, Octave has it's own (experimental) GUI based on QT. Unfortunately it's not in Arch Linux repos yet. So you have to build it for your own. To start the GUI, run {{ic|octave --force-gui}}<br />
<br />
The following GUIs are unofficial.<br />
* {{App|Cantor|A graphical user interface that delegates its mathematical operations to one of several back ends (Scilab, Maxima, Octave and others).|http://edu.kde.org/cantor/|{{Pkg|kdeedu-cantor}}}}<br />
* {{App|QtOctave|A Qt frontend for Octave.|https://forja.rediris.es/projects/csl-qtoctave/|{{AUR|qtoctave}}}}<br />
<br />
== Reading Microsoft Excel Spreadsheets ==<br />
<br />
There are several ways to read Microsoft Excel files with Octave.<br />
<br />
==== Converting to an open format ====<br />
<br />
The easiest way to use {{ic|.xls}} files in Octave would be to convert them to {{ic|.csv}} or {{ic|.ods}} using Calc (limited to 1024 columns) from [[Libreoffice]] or [http://www.calligra.org/sheets/ Sheets](limited to 32768 columns) from the the [http://www.calligra-suite.org/ Calligra Suite].<br />
<br />
After the conversion is complete you can use the build-in Octave function {{ic|csvread}} for {{ic|.csv}} files:<br />
<br />
octave:1> csvread('myfile.csv');<br />
<br />
For {{ic|.ods}} files the {{AUR|octave-io}} package is necessary which contains the {{ic|odsread}} function:<br />
<br />
octave:1> odsread('myfile.ods');<br />
<br />
For {{ic|.xlsx}} files you can use the {{AUR|xlsx2csv}} package from [[AUR]]:<br />
<br />
xlsx2csv -t /path/to/save/location -x /path/to/myfile.xlsx <br />
<br />
==== Reading xls files directly from Octave ====<br />
<br />
If you must work with XLS files and you cannot convert them to CSV or ODS, for whatever reason, you can use the {{ic|xlsread}} function from the {{AUR|octave-io}} package.<br />
<br />
Since {{AUR|octave-io}} version 1.2.5., an interface called 'OCT' was added, which perform reading .xlsx (not .xls!), ods and .gnumeric without any dependencies. However, the Java-based interface still exist (special for reading .xls files and writing those file formats).<br />
<br />
===== Steps necessary to make Java Interface available =====<br />
<br />
The steps necessary to make it work are:<br />
:1. [[Pacman|Install]] {{Pkg|jdk7-openjdk}}, available in the [[official repositories]].<br />
<br />
{{Note|A common problem is that Octave cannot find the JDK path. To fix this execute the following commands in your shell:<br />
$ export JAVA_HOME&#61;/usr/lib/jvm/java-7-openjdk<br />
You may also want to add this to your {{ic|~/.bashrc}} and append it to your {{ic|PATH}}.}}<br />
<br />
:2. Install a Java XLS library for {{ic|xlsread}}. There are more such libraries available, a comparison can be found at [http://octave.org/wiki/index.php?title=IO_package#Comparison_of_interfaces_.26_usage here]. The recommended library is {{AUR|apache-poi}}, available in the [[AUR]].<br />
<br />
:3. Finally, install the {{AUR|octave-java}} package from [[AUR]].<br />
<br />
To check if Java is working correctly in Octave, see the output of:<br />
<br />
octave:1> javaclasspath <br />
STATIC JAVA PATH<br />
- empty -<br />
DYNAMIC JAVA PATH<br />
- empty -<br />
<br />
To load the selected library in Octave, check if it is in the Java path. If not:<br />
octave:1> javaaddpath path/to/file.jar<br />
In the case you chose {{AUR|apache-poi}}, the relevant JAR files can be found in {{ic|/usr/share/java/apache-poi/poi-3.x.jar}} and {{ic|/usr/share/java/apache-poi/poi-ooxml-3.x.jar}}.<br />
<br />
To check if it works<br />
octave:1> chk_spreadsheet_support <br />
<br />
The output should be > 0:<br />
0 No spreadsheet I/O support found<br />
---------- XLS (Excel) interfaces: ----------<br />
1 = COM (ActiveX / Excel)<br />
2 = POI (Java / Apache POI)<br />
4 = POI+OOXML (Java / Apache POI)<br />
8 = JXL (Java / JExcelAPI)<br />
16 = OXS (Java / OpenXLS)<br />
--- ODS (OpenOffice.org Calc) interfaces ----<br />
32 = OTK (Java/ ODF Toolkit)<br />
64 = JOD (Java / jOpenDocument)<br />
----------------- XLS & ODS: ----------------<br />
128 = UNO (Java / UNO bridge - OpenOffice.org)<br />
<br />
To make this permanent add the {{ic|javaaddpath}} commands to your {{ic|~/.octaverc}} file.</div>Rh995https://wiki.archlinux.org/index.php?title=Ratpoison&diff=295960Ratpoison2014-02-03T03:11:41Z<p>Rh995: I deleted the line that contained rpws -i, because it seems as if it doesn't do anything useful, but instead throws some kind of error.</p>
<hr />
<div>[[Category:Tiling WMs]]<br />
[[uk:Ratpoison]]<br />
<br />
From the project [http://www.nongnu.org/ratpoison/ home page]:<br />
: ''Ratpoison is a simple [[Window Manager]] with no fat library dependencies, no fancy graphics, no window decorations, and no rodent dependence. It is largely modelled after [[GNU Screen]] which has done wonders in the virtual terminal market. The screen can be split into non-overlapping frames. All windows are kept maximized inside their frames to take full advantage of your precious screen real estate. All interaction with the window manager is done through keystrokes. ratpoison has a prefix map to minimize the key clobbering that cripples Emacs and other quality pieces of software.''<br />
<br />
== Installation ==<br />
<br />
Ratpoison can be installed with package {{Pkg|ratpoison}}, available in [[official repositories]].<br />
<br />
== Configuration ==<br />
<br />
To use ratpoison as your windowmanager, you have to create/edit the file {{Ic|~/.xinitrc}}.<br />
<br />
Example .xinitrc:<br />
{{bc|<nowiki><br />
# the black/white grid as background doesn't suit my taste.<br />
xsetroot -solid black &<br />
# ratpoison is compatible with xcompmgr! now you can have real transparency<br />
xcompmgr -c -f -D 5 &<br />
#fire up ratpoison!<br />
exec /usr/bin/ratpoison<br />
</nowiki>}}<br />
<br />
== Using ratpoison ==<br />
<br />
After X11 starts up you will see a black screen and a little textbox on the upper right of it that says "Welcome to Ratpoison".<br />
Now type {{ic|Ctrl+t}} and then {{ic|?}} to get a list of keybindings. If you are used to GNU screen, you will feel at home very soon.<br />
<br />
You are able to define custom keystrokes and even override existing ones in {{Ic|~/.ratpoisonrc}}<br />
<br />
Example:<br />
{{bc|<nowiki><br />
# overriding CTRL+t 'c' to start aterm instead of xterm<br />
bind c exec aterm<br />
<br />
bind f exec firefox<br />
</nowiki>}}<br />
<br />
So, if you type {{ic|Ctrl+t}} and then {{ic|f}}, ratpoison will fire up Firefox.<br />
<br />
Here is another .ratpoisonrc i'm using on my computers:<br />
<br />
{{bc|<nowiki><br />
exec xsetroot -cursor_name left_ptr<br />
startup_message off<br />
<br />
escape C-z<br />
<br />
# make a screenshot<br />
alias sshot exec import -window root ~/screenshot-$(date +%F).jpg<br />
definekey top M-C-Print sshot<br />
<br />
#virtual desks<br />
gnewbg one<br />
gnewbg two<br />
<br />
definekey top M-l exec ratpoison -c "select -" -c "gprev" -c "next"<br />
definekey top M-h exec ratpoison -c "select -" -c "gnext" -c "next"<br />
<br />
#switch between windows<br />
definekey top M-j next<br />
definekey top M-k prev<br />
<br />
#apps<br />
unbind c<br />
bind c exec urxvt -tr<br />
#bind c exec aterm<br />
<br />
bind g exec gftp<br />
bind f exec firefox<br />
</nowiki>}}<br />
<br />
== Tips and tricks ==<br />
<br />
=== Multiple workspaces ===<br />
<br />
By default, ratpoison only has one workspace, but using a script called rpws (installed by default) you can have more.<br />
<br />
Just edit your .ratpoisonrc, and add:<br />
{{hc|~/.ratpoisonrc|<br />
exec /usr/bin/rpws init 6 -k<br />
}}<br />
That creates 6 workspaces. By default, you can access to them by using {{ic|Alt+F1}} to access the first, {{ic|Alt+F2}} to access the second, etc.<br />
<br />
You can also add binds to them, like this:<br />
<br />
bind C-1 exec rpws 1<br />
bind C-2 exec rpws 2<br />
...<br />
That allows to access them with {{ic|Ctrl+t}} {{ic|Ctrl+1}} (assuming {{ic|Ctrl+t}} as your escape key)<br />
<br />
=== urxvt and xterm ===<br />
<br />
Urxvt and xterm would not resize to a fixed number of pixels. Instead, it resize itself to multiples of its font's size, therefore, chances that there are unfilled gaps are high.<br />
To correct this, we can use the xterm/urxvt option internalBorder and set the border of ratpoison to 0. <br />
<br />
A trial and error process must be done to find the exact number of internalBorder for each combination of resolution and font size. (the border of ratpoison must be set to 0 before doing the tests)<br />
The term command line option -b can be used to test for the correct number and then can be saved on the following files.<br />
{{hc|~/.Xresources|<br />
urxvt*internalBorder: 8 #change urxvt to xterm if necessary. Using the font terminus in urxvt at 14px size, 8 is the correct number here.<br />
}}<br />
{{hc|~/.ratpoisonrc|<br />
set border 0<br />
}}<br />
If a combination cannot be found, you could try changing the font size and the font family also. (that changes the required border number)<br />
<br />
=== Launch on startup ===<br />
<br />
Examples for launching programs when ratpoison starts. File {{ic|~/.ratpoisonrc}} is executed by ratpoison on startup.<br />
<br />
{{hc|Launch urxvt with a tmux session|<nowiki><br />
exec urxvt -e bash -c "tmux -q has-session && exec tmux attach-session -d || exec tmux new-session -n$USER -s$USER@$HOSTNAME"<br />
</nowiki>}}<br />
<br />
{{hc|Launch optimized chromium|<nowiki><br />
exec bash -c 'pidof chromium &>/dev/null || exec /usr/bin/chromium --disk-cache-dir=~/tmp/cache'<br />
</nowiki>}}<br />
<br />
=== Wallpaper and transparency ===<br />
<br />
Example for setting transparency using [[xcompmgr]] and nitrogen.<br />
First start nitrogen and set the desired wallpaper. Then use this in your .ratpoisonrc<br />
<br />
{{hc|Wallpaper and transparency|<nowiki><br />
exec xcompmgr -c -f -D 5 &<br />
exec nitrogen --restore</nowiki><br />
}}<br />
<br />
== Some more useful KeyCombos ==<br />
<br />
{{ic|Ctrl+t}} {{ic|!}} <''Program Name''> Start any program<br />
<br />
{{ic|Ctrl+t}} {{ic|q}} Quit ratpoison<br />
<br />
{{ic|Ctrl+t}} {{ic|?}} Show key bindings<br />
<br />
{{ic|Ctrl+t}} {{ic|c}} Start an X terminal<br />
<br />
{{ic|Ctrl+t}} {{ic|n}} Switch to next window<br />
<br />
{{ic|Ctrl+t}} {{ic|p}} Switch to previous window<br />
<br />
{{ic|Ctrl+t}} {{ic|1}}-{{ic|9}} Switch to windows 1-9<br />
<br />
{{ic|Ctrl+t}} {{ic|k}} Close the current window<br />
<br />
{{ic|Ctrl+t}} {{ic|Shift+k}} XKill the current application<br />
<br />
{{ic|Ctrl+t}} {{ic|s}},{{ic|Shift+s}} Split the current frame into two vertical,horizontal ones<br />
<br />
{{ic|Ctrl+t}} {{ic|Tab}}, {{ic|&larr;}}, {{ic|&uarr;}}, {{ic|&rarr;}}, {{ic|&darr;}} Switch to the next, left. top, right, bottom frame.<br />
<br />
{{ic|Ctrl+t}} {{ic|Shift+q}} Make the current frame the only one<br />
<br />
{{ic|Ctrl+t}} {{ic|:}} Execute a ratpoison command<br />
<br />
== Ratpoison and display managers ==<br />
<br />
Many [[display manager|display managers]] (e.g., [[lightdm]]) source the available sessions from {{ic|/usr/share/xsessions/}} and most window managers and desktop environments create .desktop files there. However ratpoison instead creates a {{ic|ratpoison.desktop}} file in {{ic|/etc/X11/sessions/}}. To allow display managers to find ratpoison one may need to copy the ratpoison.desktop file from {{ic|/etc/X11/sessions/ratpoison.desktop}} to {{ic|/usr/share/xsessions/ratpoison.desktop}}. If the {{ic|/usr/share/xsessions}} directory does not exist, create it as root.<br />
<br />
== See also ==<br />
<br />
* [http://ratpoison.wxcvbn.org/ The Ratpoison wiki]<br />
* [http://stumpwm.svkt.org/cgi-bin/ratpoison.pl?action=browse;id=keys X11 Keys in Ratpoison]<br />
* [http://www.ormiret.com/?q=node/11 Ratpoison config sample]<br />
* [https://bbs.archlinux.org/viewtopic.php?id=68622 Share your Ratpoison (experience) forum thread] <br />
* [https://github.com/jbaber/ratpoison_scripts Collection of scripts for the Ratpoison window manager] <br />
* [http://www.nongnu.org/stumpwm/ Stumpwm similar window manager but in Common lisp.]</div>Rh995https://wiki.archlinux.org/index.php?title=Bitcoin&diff=282420Bitcoin2013-11-12T00:59:04Z<p>Rh995: cgminer has removed support for GPU mining. Updated the description to reflect this.</p>
<hr />
<div>[[Category:Internet Applications]]<br />
{{Stub}}<br />
[[Wikipedia:Bitcoin|Bitcoin]] is a decentralized P2P electronic cash system without a central server or trusted parties. Users hold the cryptographic keys to their own money and make transactions directly with each other, with the help of the network to check for double-spending. Bitcoins, usually denoted by BTC (i.e. '144 BTC'), can also be exchanged for traditional currencies like US dollars.<br />
<br />
== Introduction ==<br />
<br />
The Bitcoin network runs on peer-to-peer networking, digital signatures and cryptographic proof to make and verify transactions. Nodes broadcast transactions to the network, which records them in a public record of all transactions, called the block chain. A '''block''' is a record of some or all of the most recent Bitcoin transactions that have not yet been recorded in any prior blocks. In order to preserve the integrity of the block chain, each block in the chain confirms the integrity of the previous one, all the way back to the first one, using hashing.<br />
<br />
New bitcoins are generated by the network through the process of [[#Mining|mining]]. Mining involves inserting a new block into the current block chain, this is difficult because it requires generating a valid hash (in this case a large integer).<br />
<br />
A variation in difficulty is achieved by requiring that this integer is below a certain threshold - the data in the block is perturbed by a [[Wikipedia:Cryptographic nonce|nonce value]], until the data in the block hashes to produce an integer below the threshold - which takes a lot of processing power. The threshold is set by the number of people currently mining for bitcoins so as to achieve a general speed of about 1 block every 10 minutes.<br />
<br />
== Installation ==<br />
<br />
The official Bitcoin application can be installed with the {{Pkg|bitcoin-qt}} and {{Pkg|bitcoin-daemon}} packages, available in the [[official repositories]].<br />
<br />
== How to get Bitcoins? ==<br />
<br />
There are a variety of ways to acquire bitcoins:<br />
* Accept bitcoins as payment for goods or services.<br />
* There are several services where you can trade them for [https://en.bitcoin.it/wiki/Buying_bitcoins traditional currency].<br />
* Find someone to trade cash for bitcoins in-person through a local directory. To find traders near you, you can use [http://www.tradebitcoin.com/ bitcoin.local] or a [http://www.bitcoinmap.com/ bitcoin map].<br />
* Participate in a [https://en.bitcoin.it/wiki/Pooled_mining mining pool].<br />
* If you have very good hardware, you can solo mine and attempt to create a new block (currently yields 25 bitcoins).<br />
<br />
For those who are just getting started, you can visit the [https://freebitcoins.appspot.com/ Bitcoin Faucet] to get some free coins. For more details and other ways of making Bitcoins see [http://www.weusecoins.com/getting-started.php We Use Coins].<br />
<br />
=== Mining ===<br />
<br />
{{Note|Mining is only really commercially viable with decent hardware, for a comparison of hardware and their performance see the [https://en.bitcoin.it/wiki/Mining_hardware_comparison bitcoin.it wiki]. To see if your setup is viable use a [http://bitcoinx.com/profit/ Profit Calculator].}}<br />
<br />
The basic concept of Bitcoin mining is that there's a little chunk of each block that contains meaningless random data. Bitcoin miners take all the data in the current top block, shuffle up that random chunk and calculate the hash of the whole thing, repeating this until they obtain a valid block. While hashes are easy to reproduce, they're impossible to predict and they seem to function completely randomly, so the miner has no way of predicting what chunk of random data will produce what hash.<br />
<br />
Mining requires the use of a ''miner'', which is program used compute the required hashes and thus to create Bitcoins. To learn more about mining please read this [http://www.weusecoins.com/mining-guide.php article].<br />
<br />
There are several Bitcoin miners in the [[AUR]]:<br />
* {{App|Bitcoin CUDA|Version of the official Bitcoin daemon with CUDA support (for Nvidia GPUs).|http://www.bitcoin.org/|{{AUR|bitcoin-daemon-cuda}}}}<br />
* {{App|CGMiner|Multi-threaded multi-pool CPU miner.|https://github.com/ckolivas/cgminer|{{Pkg|cgminer}}}}<br />
{{Tip|you need corresponding opencl package to enable GPU mining, {{Pkg|opencl-nvidia}} for Nvidia, {{Pkg|opencl-catalyst}} for AMD, and {{AUR|intel-opencl-sdk}} in AUR for Intel.}}<br />
* {{App|cpuminer|Multi-threaded CPU Miner.|http://yyz.us/bitcoin/|{{AUR|cpuminer-git}}}}<br />
* {{App|Phoenix Miner|Efficient, fast, modular, python-based, OpenCL GPU miner.|https://github.com/jedi95/Phoenix-Miner|{{AUR|phoenix-miner-svn}}}}<br />
<br />
== Sample config file ==<br />
<br />
An example of a configuration file for '''bitcoin-qt''' can be seen below. Make sure to set the mode of the file to {{ic|600}} using:<br />
# chmod 600 ~/.bitcoin/bitcoin.conf<br />
<br />
{{hc|~/.bitcoin/bitcoin.conf|<nowiki><br />
# bitcoin.conf configuration file. Lines beginning with # are comments.<br />
<br />
# Network-related settings:<br />
<br />
# Run on the test network instead of the real bitcoin network.<br />
#testnet=1<br />
<br />
# Connect via a socks4 proxy<br />
#proxy=127.0.0.1:9050<br />
<br />
# Use as many addnode= settings as you like to connect to specific peers<br />
#addnode=69.164.218.197<br />
#addnode=10.0.0.2:8333<br />
<br />
# … or use as many connect= settings as you like to connect ONLY<br />
# to specific peers:<br />
#connect=69.164.218.197<br />
#connect=10.0.0.1:8333<br />
<br />
# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to<br />
# find other peers.<br />
#noirc=1<br />
<br />
# Maximum number of inbound+outbound connections.<br />
#maxconnections=<br />
<br />
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)<br />
<br />
# server=1 tells Bitcoin to accept JSON-RPC commands.<br />
#server=1<br />
<br />
# You must set rpcuser and rpcpassword to secure the JSON-RPC api<br />
#rpcuser=user<br />
#rpcpassword=password<br />
<br />
# How many seconds bitcoin will wait for a complete RPC HTTP request.<br />
# after the HTTP connection is established.<br />
rpctimeout=30<br />
<br />
# By default, only RPC connections from localhost are allowed. Specify<br />
# as many rpcallowip= settings as you like to allow connections from<br />
# other hosts (and you may use * as a wildcard character):<br />
#rpcallowip=10.1.1.34<br />
#rpcallowip=192.168.1.*<br />
<br />
# Listen for RPC connections on this TCP port:<br />
rpcport=8332<br />
<br />
# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind<br />
# running on another host using this option:<br />
rpcconnect=127.0.0.1<br />
<br />
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate<br />
# with Bitcoin -server or bitcoind<br />
#rpcssl=1<br />
<br />
# OpenSSL settings used when rpcssl=1<br />
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH<br />
rpcsslcertificatechainfile=server.cert<br />
rpcsslprivatekeyfile=server.pem<br />
<br />
# Miscellaneous options<br />
<br />
# Set gen=1 to attempt to generate bitcoins<br />
gen=0<br />
<br />
# Use SSE instructions to try to generate bitcoins faster. For muliple core processors.<br />
#4way=1<br />
<br />
# Pre-generate this many public/private key pairs, so wallet backups will be valid for<br />
# both prior transactions and several dozen future transactions.<br />
keypool=100<br />
<br />
# Pay an optional transaction fee every time you send bitcoins. Transactions with fees<br />
# are more likely than free transactions to be included in generated blocks, so may<br />
# be validated sooner.<br />
paytxfee=0.00<br />
<br />
# Allow direct connections for the ‘pay via IP address’ feature.<br />
#allowreceivebyip=1<br />
<br />
# User interface options<br />
<br />
# Start Bitcoin minimized<br />
#min=1<br />
<br />
# Minimize to the system tray<br />
#minimizetotray=1<br />
</nowiki>}}<br />
<br />
== Other clients ==<br />
<br />
There are other clients available for BitCoin.<br />
<br />
* {{App|Armory|Client with features for advanced users. It uses information from the satoshi client (bitcoin-qt) for communication with the bitcoin network.|https://bitcoinarmory.com/|{{AUR|armory}}}}<br />
* {{App|MultiBit|Light-weight client that focusses on being fast and easy to use.|https://multibit.org|{{AUR|multibit}}}}<br />
* {{App|Electrum|Light-weight client that relies on cloud servers to scan the blockchain.|http://electrum.org/|{{AUR|electrum}}}}<br />
<br />
== See also ==<br />
<br />
* [http://www.bitcoin.org/ Official Bitcoin website]<br />
* [https://en.bitcoin.it/wiki/Main_Page Bitcoin.it wiki]<br />
* [http://forum.bitcoin.org/ Bitcoin forum]<br />
* IRC Channels on Freenode :<br />
** '''#bitcoin''' - (General Bitcoin-related)<br />
** '''#bitcoin-dev''' - (Development and technical)<br />
** '''#bitcoin-otc''' - (Over The Counter exchange)<br />
** '''#bitcoin-market''' - (Live quotes from markets)<br />
** '''#bitcoin-mining''' - (GPU mining related)</div>Rh995https://wiki.archlinux.org/index.php?title=Arch_User_Repository&diff=200063Arch User Repository2012-05-03T04:19:05Z<p>Rh995: fixed a typo in the system update command</p>
<hr />
<div>[[Category:Arch User Repository]]<br />
[[Category:About Arch]]<br />
[[Category:Package development]]<br />
[[Category:Package management]]<br />
[[Category:Arch development]]<br />
[[tr:Arch_Kullanıcı_Deposu]]<br />
{{i18n|Arch User Repository}}<br />
[[fr:AUR]]<br />
{{Article summary start}}<br />
{{Article summary text|The Arch User Repository is a collection of user-submitted [[PKGBUILD]]s that supplement software available from the [[official repositories]]. This article describes how to build ''unsupported'' software packages from the AUR.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Package management overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|AUR Helpers}}<br />
{{Article summary wiki|AUR Trusted User Guidelines}}<br />
{{Article summary heading|Resources}}<br />
{{Article summary link|AUR Web Interface|https://aur.archlinux.org}}<br />
{{Article summary link|AUR Mailing List|http://www.archlinux.org/mailman/listinfo/aur-general}}<br />
{{Article summary end}}<br />
<br />
The Arch User Repository (AUR) is a community-driven repository for Arch users. It contains package descriptions (PKGBUILDs) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]]. The AUR was created to organize and share new packages from the community and to help expedite popular packages' inclusion into the [[#.5Bcommunity.5D|[community]]] repository. This document explains how users can access and utilize the AUR.<br />
<br />
A good number of new packages that enter the official repositories start in the AUR. In the AUR, users are able to contribute their own package builds (PKGBUILD and related files). The AUR community has the ability to vote for or against packages in the AUR. If a package becomes popular enough -- provided it has a compatible license and good packaging technique -- it may be entered into the [community] repository (directly accessible by [[pacman]] or [[ABS|abs]]).<br />
<br />
==Getting started==<br />
Users can search and download PKGBUILDs from the [https://aur.archlinux.org AUR Web Interface]. These PKGBUILDs can be built into installable packages using [[makepkg]], then installed using pacman. <br />
<br />
* Install {{Grp|base-devel}} ({{ic|pacman -S base-devel}}), because members of this group are not explicitly required by AUR packages which may not build without them (more info in [https://bbs.archlinux.org/viewtopic.php?pid=632355 this thread]).<br />
* Read the remainder of this article for more info and a short tutorial on installing AUR packages.<br />
* Visit the [https://aur.archlinux.org AUR Web Interface] to inform yourself on updates and happenings. There you will also find statistics and an up-to-date list of newest available packages available in AUR.<br />
* Glance over the [[#FAQ]] for answers to the most common questions.<br />
* You may wish to adjust {{ic|/etc/makepkg.conf}} to better optimize for your processor prior to building packages from the AUR. A significant improvement in compile times can be realized on systems with multi-core processors by adjusting the MAKEFLAGS variable. Users can also enable hardware-specific optimizations in GCC via the CFLAGS variable. See [[makepkg.conf]] for more information.<br />
<br />
==History==<br />
The following items are listed for historical purposes only. They have since been superseded by the AUR and are no longer available.<br />
<br />
At the beginning, there was {{ic|<nowiki>ftp://ftp.archlinux.org/incoming</nowiki>}}, and people contributed by simply uploading the PKGBUILD, the needed supplementary files, and the built package itself to the server. The package and associated files remained there until a [[Package Maintainer]] saw the program and adopted it.<br />
<br />
Then the Trusted User Repositories were born. Certain individuals in the community were allowed to host their own repositories for anyone to use. The AUR expanded on this basis, with the aim of making it both more flexible and more usable. In fact, the AUR maintainers are still referred to as TUs (Trusted Users).<br />
<br />
==Searching==<br />
The AUR web interface can be found [https://aur.archlinux.org/ here], and an interface suitable for accessing the AUR from a script (for example) can be found [https://aur.archlinux.org/rpc.php here]<br />
<br />
Queries search package names and descriptions via a MySQL LIKE comparison. This allows for more flexible search criteria (e.g. try searching for 'tool%like%grep' instead of 'tool like grep'). If you need to search for a description that contains '%', escape it with '\%'.<br />
<br />
==Installing packages==<br />
Installing packages from the AUR is a relatively simple process. Essentially:<br />
# Acquire the tarball which contains the PKGBUILD and possibly other required files<br />
# Extract the tarball (preferably in a folder set aside just for builds from the AUR)<br />
# Run '''makepkg''' in the directory where the files are saved ("makepkg -s" will auto-resolve dependencies with pacman)<br />
# Install the resulting package with '''pacman''':<br />
<br />
# pacman -U /path/to/pkg.tar.xz<br />
<br />
[[AUR Helpers]] add seamless access to the AUR. They vary in their features, but can ease in searching, fetching, building, and installing from PKGBUILDs found in the AUR. All of these scripts can be found in the AUR.<br />
<br />
{{Note|There is not and will never be an ''official'' mechanism for installing build material from the AUR. All users should be familiar with the build process.}}<br />
<br />
What follows is a detailed example of installation of a package called "foo".<br />
<br />
===Prerequisites===<br />
First ensure that the necessary tools are installed. The package group "base-devel" should be sufficient; it includes ''make'' and other tools needed for compiling from source.<br />
<br />
{{Warning|Packages in the AUR assume "base-devel" is installed, and will not list members of this group as dependencies even if the package cannot be built without them. Please ensure this group is installed before complaining about failed builds.}}<br />
<br />
# pacman -S base-devel<br />
<br />
Next choose an appropriate build directory. A build directory is simply a directory where the package will be made or "built" and can be any directory. Examples of commonly used directories are:<br />
<br />
~/builds<br />
<br />
or if using ABS (the [[Arch Build System]]):<br />
<br />
/var/abs/local<br />
<br />
For more information on ABS read the [[Arch Build System]] article. The example will use {{ic|~/builds}} as the build directory.<br />
<br />
===Acquire build files===<br />
Locate the package in the AUR. This is done using the search feature (text field at the top of the [https://aur.archlinux.org/ AUR home page]). Clicking the application's name in the search list brings up an information page on the package. Read through the description to confirm that this is the desired package, note when the package was last updated, and read any comments.<br />
<br />
Download the necessary build files. From the package's information page download the build files by clicking the "Tarball" link on the left-hand side near the end of the package details. This file should be saved to the build directory or otherwise copied to the directory after downloading. In this example, the file is called "foo.tar.gz" (standard format is ''pkgname''.tar.gz, if it has been properly submitted).<br />
<br />
===Build the package===<br />
Extract the tarball. Change directories to the build directory if not already there and extract the build files.<br />
<br />
$ cd ~/builds<br />
$ tar -xvzf foo.tar.gz<br />
<br />
This should create a new directory called "foo" in the build directory.<br />
<br />
{{Warning|'''Carefully check all files.''' {{ic|cd}} to the newly created directory and carefully check the {{ic|PKGBUILD}} and any {{ic|.install}} file for malicious commands. {{ic|PKGBUILD}}s are bash scripts containing functions to be executed by {{ic|makepkg}}: these functions can contain ''any'' valid commands or bash syntax, so it is totally possible for a {{ic|PKGBUILD}} to contain dangerous commands through malice or ignorance on the part of the author. Since {{ic|makepkg}} uses fakeroot (and should never be run as root), there is some level of protection but you should never count on it. If in doubt, do not build the package and seek advice on the forums or mailing list.}}<br />
<br />
$ cd foo<br />
$ nano PKGBUILD<br />
$ nano foo.install<br />
<br />
Make the package. After manually confirming the integrity of the files, run [[makepkg]] as a normal user in the build directory.<br />
<br />
$ makepkg -s<br />
<br />
The {{ic|-s}} switch will use [[sudo]] to install any needed dependencies. If the use of sudo is undesirable, manually install required dependencies beforehand and exclude the {{ic|-s}} in the above command.<br />
<br />
===Install the package===<br />
Install the package using pacman. A tarball should have been created named:<br />
<br />
<''application name''>-<''application version number''>-<''package revision number''>-<''architecture''>.pkg.tar.xz<br />
<br />
This package can be installed using pacman's "upgrade" command:<br />
<br />
# pacman -U foo-0.1-1-i686.pkg.tar.xz <br />
<br />
These manually-installed packages are called foreign packages - packages which have not originated from any repository known to pacman. To list all foreign packages:<br />
$ pacman -Qm <br />
<br />
{{Note|The above example is only a brief summary of the package building process. A visit to the [[makepkg]] and [[ABS]] pages will provide more detail and is highly recommended (particularly for first-time users).}}<br />
<br />
==Feedback==<br />
The [https://aur.archlinux.org AUR Web Interface] has a comments facility that allows users to provide suggestions and feedback on improvements to the PKGBUILD contributor. Avoid pasting patches or PKGBUILDs into the comments section: they quickly become obsolete and just end up needlessly taking up lots of space. Instead email those files to the maintainer, or even use a [[pastebin Clients|pastebin]].<br />
<br />
One of the easiest activities for '''all''' Arch users is to browse the AUR and '''vote''' for their favourite packages using the online interface. All packages are eligible for adoption by a TU for inclusion in [community], and the vote count is one of the considerations in that process; it is in everyone's interest to vote!<br />
<br />
==Sharing packages==<br />
The user plays an essential role in the AUR, which cannot fulfill its potential without the support, involvement, and contribution of the wider user community. The life-cycle of an AUR package starts and ends with the user and requires the user to contribute in several ways.<br />
<br />
Users can '''share''' PKGBUILDs using the Arch User Repository. It does not contain any binary packages but allows users to upload PKGBUILDs that can be downloaded by others. These PKGBUILDs are completely unofficial and have not been thoroughly vetted, so they should be used at your own risk.<br />
<br />
===Submitting packages===<br />
After logging in to the AUR web interface, a user can [https://aur.archlinux.org/pkgsubmit.php submit] a gzipped tarball ({{ic|.tar.gz}}) of a directory containing build files for a package. The directory inside the tarball should contain a [[PKGBUILD]], any {{ic|.install}} files, patches, etc. ('''absolutely''' no binaries). Examples of what such a directory should look like can be seen inside {{ic|/var/abs}} if the [[Arch Build System]] was installed.<br />
<br />
The tarball can be created with the following command:<br />
$ makepkg --source <br />
<br />
Note that this is a gzipped tarball; assuming you are uploading a package called ''libfoo'', when you create the file it should look similar to this:<br />
<br />
# List contents of tarball.<br />
$ tar tf libfoo-0.1-1.src.tar.gz<br />
libfoo/<br />
libfoo/PKGBUILD<br />
libfoo/libfoo.install<br />
<br />
When submitting a package, observe the following rules: <br />
* Check the [http://www.archlinux.org/packages/ package database] for the package. If it exists, '''do not''' submit the package. If the current package is broken or is lacking an included feature then please file a [https://bugs.archlinux.org/ bug report].<br />
* Check the AUR for the package. If it is currently maintained, changes can be submitted in a comment for the maintainer's attention. If it is unmaintained, the package can be adopted and updated as required. Do not create duplicate packages.<br />
* Verify carefully that what you are uploading is correct. All contributors must read and adhere to the [[Arch Packaging Standards]] when writing PKGBUILDs. This is essential to the smooth running and general success of the AUR. Remember that you are not going to earn any credit or respect from your peers by wasting their time with a bad PKGBUILD.<br />
* Packages that contain binaries or that are very poorly written may be deleted without warning.<br />
* If you are unsure about the package (or the build/submission process) in any way, submit the PKGBUILD to the [https://mailman.archlinux.org/mailman/listinfo/ AUR Mailing List] or the [https://bbs.archlinux.org/viewforum.php?id=4 AUR boards] on the forum for public review before adding it to the AUR.<br />
* Make sure the package is useful. Will anyone else want to use this package? Is it extremely specialized? If more than a few people would find this package useful, it is appropriate for submission.<br />
* Gain some experience before submitting packages. Build a few packages to learn the process and then submit.<br />
* If you submit a {{ic|package.tar.gz}} with a file named '{{ic|package}}' in it you will get an error: 'Could not change to directory {{ic|/home/aur/unsupported/package/package}}'. To resolve this, rename the file named '{{ic|package}}' to something else, for example, '{{ic|package.rc}}'. When it is installed in the {{ic|pkg}} directory you may rename it back to '{{ic|package}}'.<br />
Make sure to also read [[Arch Packaging Standards#Submitting Packages to the AUR]].<br />
<br />
===Maintaining packages===<br />
* If you maintain a package and want to update the PKGBUILD for your package just resubmit it.<br />
* Check for feedback and comments from other users and try to incorporate any improvements they suggest; consider it a learning process!<br />
* Please do not just submit and forget about packages! It is the maintainer's job to maintain the package by checking for updates and improving the PKGBUILD.<br />
* If you do not want to continue to maintain the package for some reason, {{ic|disown}} the package using the AUR web interface and/or post a message to the AUR Mailing List.<br />
<br />
===Other requests===<br />
* Disownment requests and removal requests go to the aur-general mailing list for TUs and other users to decide upon.<br />
* '''Include package name and URL to AUR page''', preferably with a footnote [1].<br />
* Disownment requests will be granted two weeks after the current maintainer has been contacted by email and did not react.<br />
* '''Package merging has been implemented''', users still have to resubmit a package under a new name and may request merging of the old version's comments and votes on the mailing list<br />
* Removal requests require the following information:<br />
** Package name and URL to AUR page<br />
** Reason for deletion, at least a short note <br> '''Notice:''' A package's comments does not sufficiently point out the reasons why a package is up for deletion. Because as soon as a TU takes action, the only place where such information can be obtained is the aur-general mailing list.<br />
** Include supporting details, like when a package is provided by another package, if you are the maintainer yourself, it's renamed and the original owner agreed, etc.<br />
<br />
Removal requests can be disapproved, in which case you'll likely be advised to disown the package for a future packager's reference.<br />
<br />
==[community]==<br />
The [community] repository, maintained by [[Trusted Users]], contains the most popular packages from the AUR. It is enabled by default in {{ic|/etc/pacman.conf}}. If [community] has been disabled or removed, it can be enabled by uncommenting or adding these two lines: <br />
<br />
{{hc|/etc/pacman.conf|<nowiki><br />
...<br />
[community]<br />
Include = /etc/pacman.d/mirrorlist<br />
...<br />
</nowiki>}}<br />
<br />
[community], unlike the AUR, contains binary packages that can be installed directly with [[pacman]] and the build files can also be accessed with the [[Arch Build System|ABS]]. Some of these packages may eventually make the transition to the [core] or [extra] repositories as the developers consider them crucial to the distribution.<br />
<br />
Users can also access the [community] build files by editing {{ic|/etc/abs.conf}} and enabling the [community] repository in the {{ic|REPOS}} array.<br />
<br />
==Git Repo==<br />
A Git Repo of the AUR is maintained by Thomas Dziedzic providing package history among other things. It is updated at least once a day. To clone the repository (several hundred MB):<br />
<br />
$ git clone git://pkgbuild.com/aur-mirror.git<br />
<br />
[http://pkgbuild.com/git/aur-mirror.git/ Web interface], [http://pkgbuild.com/~td123/readme Readme], [http://bbs.archlinux.org/viewtopic.php?id=113099 Forum thread]<br />
<br />
==FAQ==<br />
{{FAQ<br />
|question=What is the AUR?<br />
|answer=The AUR (Arch User Repository) is a place where the Arch Linux community can upload [[PKGBUILD]]s of applications, libraries, etc., and share them with the entire community. Fellow users can then vote for their favorites to be moved into the [community] repository to be shared with Arch Linux users in binary form.}}<br />
<br />
{{FAQ<br />
|question=What kind of packages are permitted on the AUR?<br />
|answer=The packages on the AUR are merely "build scripts", i.e recipes to build binaries for pacman. For most cases, everything is permitted, as long as you are in compliance with the licensing terms of the software. For other cases, where it is mentioned that "you may not link" to downloads, i.e contents that are not redistributable, you may only use the file name itself as the source. This means and requires users to already have the restricted source in the build directory prior to building the package. Piracy is frowned upon, so "warez" is absolutely not permitted. When in doubt, ask.}}<br />
<br />
{{FAQ<br />
|question=What is a TU?<br />
|answer=A [[AUR Trusted User Guidelines|TU (Trusted User)]] is a person who is chosen to oversee AUR and the [community] repository. They're the ones who maintain popular PKGBUILDs in [community], and overall keep the AUR running.}}<br />
<br />
{{FAQ<br />
|question=What's the difference between the Arch User Repository and [community]?<br />
|answer=The Arch User Repository is where all PKGBUILDs that users submit are stored, and must be built manually with [[makepkg]]. When PKGBUILDs receive enough votes, they are moved into the [community] repository, where the TUs maintain binary packages that can be installed with [[pacman]].}}<br />
<br />
{{FAQ<br />
|question=How many votes does it take to get a PKGBUILD into [community]?<br />
|answer=Usually, at least 10 votes are required for something to move into [community]. However, if a TU wants to support a package, it will often be found in the repository.}}<br />
<br />
{{FAQ<br />
|question=How do I make a PKGBUILD?<br />
|answer=The best resource is [[Creating Packages]]. Remember to look in AUR before creating the PKGBUILD as to not duplicate efforts.}}<br />
<br />
{{FAQ<br />
|question=I'm trying to do {{ic|pacman -S foo}}; it isn't working but I know it's in [community]<br />
|answer=You probably haven't enabled [community] in your {{ic|/etc/pacman.conf}}. Just uncomment the relevant lines.<br />
If [community] is enabled in your {{ic|/etc/pacman.conf}} try running {{ic|pacman -S -y}} first to synchronize the pkgcache before trying your package again.}}<br />
<br />
{{FAQ<br />
|question=Foo in AUR is outdated; what do I do?<br />
|answer=For starters, you can flag packages out-of-date. If it stays out-of-date for an extended period of time, the best thing to do is email the maintainer. If there is no response from the maintainer after two weeks, you could send mail to the aur-general mailing list to have a TU orphan the PKGBUILD if you're willing to maintain it yourself.}}<br />
<br />
{{FAQ<br />
|question=I have a PKGBUILD I would like to submit; can someone check it to see if there are any errors?<br />
|answer=If you would like to have your PKGBUILD critiqued, post it on the aur-general mailing list to get feedback from the TUs and fellow AUR members. You could also get help from the [[ArchChannel|IRC channel]], #archlinux on irc.freenode.net. You can also<br />
use [[namcap]] to check your PKGBUILD and the resulting package for errors.}}<br />
<br />
{{FAQ<br />
|question=Foo in AUR doesn't compile when I do {{ic|makepkg}}; what should I do?<br />
|answer=You are probably missing something trivial.<br />
<br />
# Run {{ic|pacman -Syu}} before compiling anything with {{ic|makepkg}} as the problem may be that your system is not up-to-date.<br />
# Ensure you have both "base" and "base-devel" groups installed.<br />
# Try using the "{{ic|-s}}" option with {{ic|makepkg}} to check and install all the dependencies needed before starting the build process.<br />
<br />
Be sure to first read the PKGBUILD and the comments on the AUR page of the package in question.<br />
The reason might not be trivial after all. Custom CFLAGS, LDFLAGS and MAKEFLAGS can cause failures. It's also possible that the PKGBUILD is broken for everyone. If you cannot figure it out on your own, just report it to the maintainer e.g. by posting the errors you are getting in the comments on the AUR page.}}<br />
<br />
{{FAQ<br />
|question=How can I speed up repeated build processes?<br />
|answer=If you frequently compile code that uses gcc - say, a git or SVN package - you may find [[ccache]], short for "compiler cache", useful.}}<br />
<br />
{{FAQ<br />
|question=How do I access unsupported packages?<br />
|answer=See [[#Installing packages]]}}<br />
<br />
{{FAQ<br />
|question=How can I upload to AUR without using the web interface?<br />
|answer=You can use {{AUR|aurploader}}, {{AUR|aurup}} or {{AUR|burp}} -- these are command-line programs.}}</div>Rh995https://wiki.archlinux.org/index.php?title=Partitioning&diff=192892Partitioning2012-04-05T04:39:18Z<p>Rh995: added an option for creating partitions.</p>
<hr />
<div>[[Category:Storage (English)]]<br />
{{i18n|Partitioning}}<br />
{{Article summary start}}<br />
{{Article summary text|An overview of disk partitioning tools, best practices, and additional considerations.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|fstab}}<br />
{{Article summary wiki|LVM}}<br />
{{Article summary wiki|Swap}}<br />
{{Article summary end}}<br />
<br />
''Disk partitioning is the act of dividing a hard disk drive into multiple virtual hard disk drives, referred to as partitions, to treat one physical disk drive as if it were multiple disks.''<br />
<br />
: &mdash; [[Wikipedia:Disk partitioning]]<br />
<br />
{{Tip|[[Beginners' Guide#Prepare hard drive]] gives a detailed instruction on how to set hard disk partition at installation. Also you can get a lot info about file system types.}}<br />
<br />
==Overview==<br />
<br />
''Partitioning'' a hard drive allows one to logically divide the available space into sections that can be accessed independently of one another. Partition information is stored within a hard drive's [[Master Boot Record]].<br />
<br />
An entire hard drive may be allocated to a single partition, or one may divide the available storage space amongst multiple partitions. A number of scenarios require creation multiple partitions: dual- or multi-booting, for example, or maintaining a [[swap]] partition. In other cases, partitioning is used as a means of logically separating data, such as creating separate partitions for audio and video files. Common partitioning schemes are discussed in detail below.<br />
<br />
Users may create up to four ''primary partitions'' per hard drive. If additional partitions are required, a single ''extended partition'' can be created instead (that is, up to three primary partitions and one extended partition). An extended partition can be further divided into an unlimited number of ''logical partitions.''<br />
<br />
==Partitioning schemes==<br />
<br />
=== All-in-one ===<br />
{{Expansion}}<br />
One partition holds everything.<br />
<br />
===Separate /boot===<br />
* Only needed during boot and kernel upgrades (when regenerating the initial ramdisk)<br />
* Not required for normal system operation<br />
* Journaled filesystem not required<br />
* Needed if installing a software RAID0(stripe) system.<br />
<br />
===Separate /home===<br />
* Facilitates backups and multi-booting<br />
* /home often requires the most disk space (for desktop users) and may need to be expanded at a later date<br />
<br />
===Separate /var===<br />
* Frequently read/written (logs, cache)<br />
* Avoid running out of disk space due to flunky logs, etc.<br />
<br />
===Separate /usr===<br />
{{Note|Requires a mkinitcpio hook, as /usr is expected to be available at boot.}}<br />
* Can be shared between multiple systems<br />
<br />
==Considerations==<br />
<br />
* Partition sizes <!-- separate section, or combined with schemes? --><br />
* File systems<br />
* LVM<br />
<br />
==Creating new partitions==<br />
{{Expansion}}<br />
Any of the partitioning tools can be used to create new partitions.<br />
<br />
==Resizing partitions==<br />
{{Expansion}}<br />
<br />
== Partitioning tools ==<br />
<br />
* fdisk & cfdisk<br />
* GNU Parted<br />
* QtParted & GParted</div>Rh995