Карта сайта

Это автоматически сохраненная страница от 08.02.2013. Оригинал был здесь: http://2ch.hk/b/res/43084045.html
Сайт a2ch.ru не связан с авторами и содержимым страницы
жалоба / abuse: admin@a2ch.ru

Птн 08 Фев 2013 09:03:39
Медскиллс-треду быть.
В тред приглашаются фотошоп-куны.
В качестве шаблона пикрелейтед.


Птн 08 Фев 2013 09:25:20
Люблю такие треды больше всего.

Птн 08 Фев 2013 09:27:02
>>43084045
Похороны гуфа version 2.0?

Птн 08 Фев 2013 09:29:36
>>43084045
Соус?

Птн 08 Фев 2013 09:29:59
Сделайте пикчу, где милкис ебёт пянсе. С меня как обычно нихуя.

Птн 08 Фев 2013 09:32:39
>>43084546
Заложница, 1 или 2

Птн 08 Фев 2013 09:35:27
>>43084620
Угадал.

Птн 08 Фев 2013 09:37:34
>>43084496
Годно.
Сделай медскилл!

Птн 08 Фев 2013 09:40:13
>>43084045
ТАКИЕ-ТО ЙОБА ЭФФЕКТЫ НА ВТОРОМ КАДРЕ! пиздец просто

Птн 08 Фев 2013 09:43:22
>>43084764
Лол. И не заметил сразу.

Птн 08 Фев 2013 09:44:12
>>43084045
Никогда не думал, что эта картинка мне пригодится.

Птн 08 Фев 2013 09:45:49
>>43084045
Не вижу логической связи

Птн 08 Фев 2013 09:45:51
>>43084045
Шаблон говно.

Птн 08 Фев 2013 09:48:35
>>43084865
1. Хачи хоронят камни.
2. Спецэффекты.
3. Ржака.

Птн 08 Фев 2013 09:50:01
>>43084911
>1. Хачи хоронят камни.
Камни вокруг могилы, дебил.

Птн 08 Фев 2013 09:50:55
>>43084946
1. Хачи хоронят камни вокруг могилы.
2. Спецэффекты.
3. Ржака.

Птн 08 Фев 2013 09:52:27
>>43084963
Следуя по твое логике, то на похоронах все хоронят землю

Птн 08 Фев 2013 09:54:26
ОП, ты просто 7-ми летний даун какой-то. Понимаешь, суть не в ебанутости самой картинке, а в ебанутости диалогов. А тут ты хуй что построишь. Гори в аду, пидр. Худший мэдскилз иред эвер.

Птн 08 Фев 2013 09:55:21
>>43085046
*тред

Птн 08 Фев 2013 09:58:14
>>43084865
Хиккачую.

Птн 08 Фев 2013 09:58:41
Я хочу поржать с такого треда. Где же вы, бетмены?

Птн 08 Фев 2013 09:59:23
>>43085128
Проиграл! Жутко в голос!

Птн 08 Фев 2013 10:00:11
>>43085142
в мдк пиздуй

Птн 08 Фев 2013 10:00:29
>>43085159
С чего?

Птн 08 Фев 2013 10:01:10
>>43085142
Хотеть ты в туалете будешь, пощекан ёбаный.

Птн 08 Фев 2013 10:02:30
>>43085180
>Вода сдетанировала

Птн 08 Фев 2013 10:07:49
Анон, я настаиваю на своем многократном проигрыше! Где все бэтмены?

Птн 08 Фев 2013 10:09:36
>>43085331
Брагу настаивай. И проигрывай с ней потом.

Птн 08 Фев 2013 10:10:57
>>43085369
Сука! В голос! Аж чаем подавился!

Птн 08 Фев 2013 10:11:43
>>43085072
Очевидно. Хотя я знаю, да, у Шелдона мамка жива.

Птн 08 Фев 2013 10:12:44
>>43084045
МАКСИМУМ УПОРОТОСТИ!

Птн 08 Фев 2013 10:14:08
>>43085426
Лол!

Птн 08 Фев 2013 10:28:10
Блядь, Двач иногда умеет удивить. Как вы смогли с такого ебанутого шаблона такие действительно смешные пикчи сделать?

Птн 08 Фев 2013 10:33:09
>>43085934
двач умер давно

Птн 08 Фев 2013 10:33:13
>>43085934
Ебанутость вообще-то основа юмора.

Птн 08 Фев 2013 10:38:46
>>43084045
Это анекдотов тред?

Птн 08 Фев 2013 10:42:36
>>43086190
Ты тупее, чем предыдущее аноны.

Птн 08 Фев 2013 10:43:50
>>43086222
Опять ты?

Птн 08 Фев 2013 10:48:43
>>43086267
Такие как ты, тоже новое веяние двача и проявление рака.

Птн 08 Фев 2013 10:48:49
Вайпер, мне похуй на тред, но не кажется ли тебе, что в /b/ куда больше заслуживающих вайпа? Еоты, рулеточки, попрошайки, камхоры - займись делом.

Птн 08 Фев 2013 10:49:06
>>43086376
Да иди ты нахуй, гик ёбаный. Пиздец, тебе ли не похуй, куда пойдёт контент? Не ты его пилил. Что ты за свою жизнь сраную сделал? Пиздуй уже нахуй.

Птн 08 Фев 2013 10:50:43
>>43086424
Школьник, ты чего не в школе?

Птн 08 Фев 2013 10:51:47
Нахуя вайп? Совсем ебанутый?

Птн 08 Фев 2013 10:52:20
>>43086495
Школьник без мозга же.

Птн 08 Фев 2013 10:53:47
Вайпер окстись, ты творишь хуйню.

Птн 08 Фев 2013 10:56:48
Лолирую с попыток запилить ориджинал контент. Дважды лолирую со школьного вайпера. You're doing it right.

Птн 08 Фев 2013 10:59:19
>>43086232
Как два.

Птн 08 Фев 2013 11:03:47
>>43084045
Вафля какая-то. Хреновый шаблон, очень хреновый, я думал намного лучше бует это все.

Птн 08 Фев 2013 11:12:47
Уёбок, сука, пидор!

Анон, ты же всегда баттхертишь от того, что нет ориджинал контента.
И вот создается, пускай тупой, но тред направленный на это тред. Мне, как участвующему в создании, похуй куда эти мэскилзы потом попадут, на мдк или ещё куда, я делаю это для других анонов, которые когда-то веселили меня своими поделками.

Пиздец, вайпер - ты просто уёбок. Рака яичек тебе, пидр.

Птн 08 Фев 2013 11:13:57
>>43087150
>но тред направленный на это тред.

Даже разволновался весь, сука.

Птн 08 Фев 2013 11:15:25
>>43087150
Двачую. Я сам редко пилю. Но всякий раз прихожу в подобные треды за хорошим настроением. Т.к. засмеялся-проиграл зашквар, а "анекдоты" тупо.

Птн 08 Фев 2013 11:18:18
>>43087305
Анус себе апни, пёс.

Птн 08 Фев 2013 11:18:44
>>43087320
Кисло-сладкий.

Птн 08 Фев 2013 11:19:22
>>43087332
Анус себе мэдскилл, пёс.

Птн 08 Фев 2013 11:20:31
Этот вайпер порвался. Давайте следующего

Птн 08 Фев 2013 11:21:11
Вайп по принципу 2 анона отписываются в треде?

Птн 08 Фев 2013 11:22:24
>>43087403
Забавно, но поделка моя, но чаем я не давился.

Птн 08 Фев 2013 11:22:42
>>43087403
Какого семена, еблан? Один постит, другой проигрывает.

Птн 08 Фев 2013 11:23:17
Хуй с ним. Забирай этот тред себе, вайпер.

Наверное, у тебя есть вески основания для вайпа.

Птн 08 Фев 2013 11:24:25
>>43087472
Я не умею. Давай ты.

Птн 08 Фев 2013 11:24:49
>>43084839
Можно сделать ещё уёбищней. Давай, ты сможешь.

Птн 08 Фев 2013 11:24:58
>>43087507
Ну охуеть теперь. Доебался до не дописанной буквы.

Птн 08 Фев 2013 11:27:22
>>43084045
Демоны гильотины врываются кровавым месивом душных смертей в этот ИТТ.

Птн 08 Фев 2013 11:28:05
Очень плюшевый взрыв машины, я думал, намного лучше будет это все. Сколько смотрел боевики, взрывы были как настоящие. А тут говно в Афтер Эффектс отдельным слоем прилепили. И освещение какое-то ненатуральное у машины от взрыва, тупо сделали.

Птн 08 Фев 2013 11:28:44
>>43087606
Остервенело серанул!

Птн 08 Фев 2013 11:29:48
Ой, да ладно вам, ну потроллил я вас, ну что? Бегите скорее за льдом, пока сстул не сгорел доконца.

Птн 08 Фев 2013 11:31:25
>>43087684
>сстул
Попизди мне тут ещё, жалкий заика.

Птн 08 Фев 2013 11:33:16
>>43087678
Тебе мерещатся семены или что? Мои посты (я не ОП) везде, где проиграл в разной форме. Больше я ничего не писал, кроме того, что вайпер поехал.

Птн 08 Фев 2013 11:40:26
>>43087930
Неистово рассешил!

Птн 08 Фев 2013 11:42:32
>>43088008
Ты ебешь сам себя в жопу, долбоеб.

Птн 08 Фев 2013 11:44:12
>>43088146
You should probably run the script twice, because many packages fail to run their post-install scripts first time. This is due to sed, grep, perl, etc. being of the wrong architecture.
You might also need to update the initrd, chroot into /mnt and run mkinitcpio -p linux.
#!/bin/bash

MOUNTED_INSTALL='/mnt'
TEMP_FILE='/tmp/packages.list'

pacman --root $MOUNTED_INSTALL -Sy
pacman --root $MOUNTED_INSTALL --cachedir $MOUNTED_INSTALL/var/cache/pacman/pkg --noconfirm -Sg base base-devel
pacman --root $MOUNTED_INSTALL -Qq > $TEMP_FILE
for PKG in $(cat $TEMP_FILE) ; do
pacman --root $MOUNTED_INSTALL --cachedir $MOUNTED_INSTALL/var/cache/pacman/pkg --noconfirm -S $PKG
done

exit 0

After rebooting to your new 64-bit system, run this command to find out what 32-bit binaries you still have and reinstall them:
find /usr/bin -type f -exec bash -c 'file {} grep 32-bit' \;
Method 2: From a running system

Ensure that your system is fully updated and functioning before proceeding.
# pacman -Syu
Package preparation
Cache old packages
Note: If you have any packages installed from the AUR or third-party repositories without new architecture availability, pacman will let you know it cannot find a suitable replacement. Make a list of these packages so you may re-install them after the update process and then remove them using pacman -Rsn package_name.

If you do not have all your installed packa

Птн 08 Фев 2013 11:57:36
>>43088505
>:)
Пиздуй отсюда.

Птн 08 Фев 2013 12:12:25
>>43088389
Мамку он твою пидорнул. Тред опять на нулевой. No way.

Птн 08 Фев 2013 12:12:41
>>43089093
И похуй/тхреад

Птн 08 Фев 2013 12:13:23
This article or section is out of date.
Reason: please use the first argument of the template to provide a brief explanation. (Discuss)
Summary
Describes the standard filesystem layout (that is, the placement of files and directories) employed by many GNU/Linux distributions -- including Arch Linux. Includes Arch-specific deviations and notes.


From the home of the Filesystem Hierarchy Standard (FHS):
"The filesystem standard has been designed to be used by Unix distribution developers, package developers, and system implementors. However, it is primarily intended to be a reference and is not a tutorial on how to manage a Unix filesystem or directory hierarchy."

Arch Linux is among the many distributions that follow the filesystem hierarchy standard. In addition to explaining each directory along with their designations, this article also covers Arch-specific modifications. Contents [hide]
1 FHS
1.1 Shareable and unsharable files
1.2 The root filesystem(Корневая файловая система)
1.3 /bin: Essential command binaries
1.4 /boot: Static bootloader files
1.5 /dev: Файлы устройств
1.6 /etc: Host-specific configuration
1.6.1 /etc/conf.d
1.6.2 /etc/rc.d
1.6.3 /etc/X11
1.6.3.1 /etc/X11/xinit
1.6.3.2 /etc/X11/xinit/xinitrc
1.7 /home: Пользовательские директории
1.8 /lib: Essential shared libraries and kernel modules
1.9 /lost+found: Filesystem-specific recoverable data
1.10 /media: Mount points for removable media
1.11 /mnt: Temporary mount points
1.12 /opt: Problematic packages
1.13 /proc: Process information
1.14 /root: Administrator directory
1.15 /sbin: System binaries
1.16 /srv: Service data
1.17 /tmp: Temporary files
1.18 /usr: Shareable, read-only data

Птн 08 Фев 2013 12:13:40
>>43089189

1.18.1 /usr/bin: Binaries
1.18.2 /usr/include: Header files
1.18.3 /usr/lib: Libraries
1.18.4 /usr/sbin: System binaries
1.18.5 /usr/share: Architecture independent data
1.18.6 /usr/src: Source code
1.18.7 /usr/local: Local hierarchy
1.19 /var: Variable files
1.19.1 /var/abs
1.19.2 /var/cache/pacman/pkg
1.19.3 /var/lib: State information
1.19.4 /var/lock: Unsharable lock data
1.19.5 /var/log: Log files
1.19.6 /var/mail: User mail
1.19.7 /var/run: State information
1.19.8 /var/spool: Queues
1.19.8.1 /var/spool/mail
1.19.9 /var/tmp: Preservable temporary files

FHS
Shareable and unsharable files

Shareable files are defined as those that can be stored on one host and used on others. Unshareable files are those that are not shareable. For example, the files in user home directories are shareable whereas device lock files are not.

Static files include binaries, libraries, documentation files and other files that do not change without system administrator intervention. Variable files are defined as files that are not static.
The root filesystem(Корневая файловая система)

The root filesystem, represented by the slash symbol by itself (/), is the primary filesystem from which all other filesystems stem; the top of the hierarchy. All files and directories appear under the root directory "/", even if they are stored on different physical devices. The contents of the root filesystem must be adequate to boot, restore, recover, and/or repair the system.
/bin: Essential command binaries

The place for binaries that must be available in single user mode and accessible by all users (e.g., cat, ls, cp). /bin/ provides programs that must be available even if only the partition containing / is mounted. This situation may arise should one need to repair other partitions but have no access to shared directories (i.e. you are in single user mode and therefore have no network access). Unlike /sbin, the /bin directory contains several useful commands that are of use to both the root user as well as non-root users.
/boot: Static bootloader files

Unsharable, static directory containing the kernel and ramdisk images as well as the bootloader configuration file, and bootloader stages. /boot also stores data that is used before the kernel begins executing userspace programs. This may include saved master boot sectors and sec

Птн 08 Фев 2013 12:14:20
>>43089202
boot sectors and sector map files.
/dev: Файлы устройств

Essential device nodes created by udev during the boot process and as machine hardware is discovered by events. This directory highlights one important aspect of the UNIX filesystem - everything is a file or a directory. Exploring this directory will reveal many files, each representing a hardware component of the system. The majority of devices are either block or character devices; however other types of devices exist and can be created. In general, 'block devices' are devices that store or hold data, whereas 'character devices' can be thought of as devices that transmit or transfer data. For example, hard disk drives and optical drives are categorized as block devices while serial ports, mice and USB ports are all character devices.
/etc: Host-specific configuration

Host-specific, unsharable configuration files shall be placed in the /etc directory. If more than one configuration file is required for an application, it is customary to use a subdirectory in order to keep the /etc/ area as clean as possible. It is considered good practice to make frequent backups of this directory as it contains all system related configuration files.
/etc/conf.d

Some daemon scripts will have a matching configuration file in this directory that contains some useful default values. When a daemon is started, it will first source the settings from its configuration file within this directory, and then source /etc/rc.conf. Arch's simple, transparent scripting approach means you can easily centralize all your daemon configuration options in your /etc/rc.conf simply by setting an appropriate variable value, or, split up your configuration over multiple files if you prefer a decentralized approach to this issue.
/etc/rc.d

All Arch daemons reside here. Custom scripts may also be placed here and invoked from the DAEMONS= array in /etc/rc.conf
/etc/X11

Configuration files for the X Window System
/etc/X11/xinit

xinit configuration files. 'xinit' is a configuration method of starting up an X session that is designed to be used as part of a script.
/etc/X11/xinit/xinitrc

Global xinitrc file, used by all X sessions started by xinit (startx). Its usage is of course overridden by a .xinitrc file located in the home directory of a user.
/home: Пользовательские директории

UNIX is a multi-user environment. Therefore, each user is also assigned a specific directory that is accessible only to them and to the root user. These are the user home directories, which can be found under '/home/$USER' (~/). Within their home directory, a user can write files, delete them, install programs, etc. Users' home directories contain their data and personal configuration files, the so-called 'dot files' (their name is preceded by a dot), which are 'hidden'. To view dotfiles, enable the appropriate option in your file manager or run ls with the -a switch. If there is a conflict between personal and system wide configuration files, the settings in the personal file will prevail. Dotfiles most likely to be altered by the end user include .xinitrc and .bashrc files. The configuration files for xinit and Bash respectively. They allow the user the ability to change the window manager to be started upon login and also aliases, user-specified commands and environment variables respectively. When a user is created, their dotfiles shall be taken from the /etc/skel directory where system sample files reside.

Directory /home can become quite large as it is typically used for storing downloads, compiling, installing

Птн 08 Фев 2013 12:14:37
>>43089225
Directory /home can become quite large as it is typically used for storing downloads, compiling, installing and running programs, mail, collections of multimedia files etc.
/lib: Essential shared libraries and kernel modules

Contains kernel modules and essential shared library images (the C programming code library) needed to boot the system and run the commands under /bin/ and /sbin/. Libraries are collections of frequently used program routines and are readily identifiable through their filename extension of *.so. They are essential for basic system functionality. Kernel modules (drivers) are in the subdirectory /lib/modules/<kernel-version>.
/lost+found: Filesystem-specific recoverable data

UNIX-like operating systems must execute a proper shutdown sequence. At times, a system might crash or a power failure might take the machine down. Either way, at the next boot, a filesystem check using the fsck program shall be performed. Fsck will go through the system and try to recover any corrupt files that it finds. The result of this recovery operation will be placed in this directory. The files recovered are not likely to be complete or make much sense but there always is a chance that something worthwhile is recovered.
/media: Mount points for removable media

CDROMs, DVD&amp;#39;s, and USB sticks shall have an appropriate mount point under /media/. The motivation for the creation of this directory has been that historically there have been a number of other different places used to mount removable media such as /cdrom, /mnt or /mnt/cdrom. Placing the mount points for all removable media directly in the root directory would potentially result in a large number of extra directories in /. Although the use of subdirectories in /mnt as a mount point has recently been common, it conflicts with a much older tradition of using /mnt directly as a temporary mount point. Therefore, Arch allocates /media as the mount point for removable media. On systems where more than one device exists for mounting a certain type of media, mount directories shall be created by appending a digit to the name of those available above starting with &amp;#39;0&amp;#39;, but the unqualified name must also exist.

The "hal" (Hardware Abstraction Layer) daemon mounts removable media to /media as /media/<name_of_removable_filesystem>
/mnt: Temporary mount points

This is a generic mount point for temporary filesystems or devices. Mounting is the process of making a filesystem available to the system. After mounting, files will be accessible under the mount-point. Additional mount-points (subdirectories) may be created under /mnt/. There is no limitation to creating a mount-point anywhere on the system, but by convention and for practicality, littering a file system with mount-points should be avoided.
/opt: Problematic packages

Packages and large static files that do not fit cleanly into the above GNU filesystem layout can be placed in /opt. A package placing files in the /opt/ directory creates a directory bearing the same name as the package. This directory in turn holds files that otherwise would be scattered throughout the file system. For example, the acrobat package has Browser, Reader, and Resource directories sitting at the same level as the bin directory. This doesn&amp;#39;t fit into a normal GNU filesystem layout, so Arch places all the files in a subdirectory of /opt.

Птн 08 Фев 2013 12:15:07
>>43089235
proc: Process information

Directory /proc is very special in that it is also a virtual filesystem. It is sometimes referred to as the process information pseudo-file system. It doesn&amp;#39;t contain &amp;#39;real&amp;#39; files, but rather, runtime system information (e.g. system memory, devices mounted, hardware configuration, etc). For this reason it can be regarded as a control and information center for the kernel. In fact, quite a lot of system utilities are simply calls to files in this directory. For example, &amp;#39;lsmod&amp;#39; is the same as &amp;#39;cat /proc/modules&amp;#39; while &amp;#39;lspci&amp;#39; is a synonym for &amp;#39;cat /proc/pci&amp;#39;. By altering files located in this directory, kernel parameters may be read/changed (sysctl) while the system is running.

The most distinctive facet about files in this directory is the fact that all of them have a file size of 0, with the exception of kcore, mounts and self.
/root: Administrator directory

Home directory of the System Administrator, &amp;#39;root&amp;#39;. This may be somewhat confusing, (&amp;#39;/root under root&amp;#39;) but historically, &amp;#39;/&amp;#39; was root&amp;#39;s home directory (hence the name of the Administrator account). To keep things tidier, &amp;#39;root&amp;#39; eventually got his own home directory. Why not in &amp;#39;/home&amp;#39;? Because &amp;#39;/home&amp;#39; is often located on a different partition or even on another system and would thus be inaccessible to &amp;#39;root&amp;#39; when - for some reason - only &amp;#39;/&amp;#39; is mounted.
/sbin: System binaries

UNIX discriminates between &amp;#39;normal&amp;#39; executables and those used for system maintenance and/or administrative tasks. The latter reside either here or - the less important ones - in /usr/sbin. Programs executed after /usr is known to be mounted (when there are no problems) are generally placed into /usr/sbin. This directory contains binaries that are essential to the working of the system. These include system administration as well as maintenance and hardware configuration programs. GRUB (the command), fdisk, init, route, ifconfig, etc., all reside here.
/srv: Service data

Site-specific data which is served by the system. The main purpose of specifying this is so that users may find the location of the data files for a particular service, and so that services which require a single tree for read-only data, writable data and scripts (such as CGI scripts) can be reasonably placed. Data of interest to a specific user shall be placed in that user&amp;#39;s home directory.
/tmp: Temporary files

This directory contains files that are required temporarily. Many programs use this to create lock files and for temporary storage of data. Do not remove files from this directory unless you know exactly what you are doing! Many of these files are important for currently running programs and deleting them may result in a system crash. On most systems, this directory is cleared out at boot or at shutdown by the local system. The basis for this was historical precedent and common practice.
/usr: Shareable, read-only data

While root is the primary filesystem, /usr is the secondary hierarchy, for user data, containing the majority of (multi-)user utilities and applications. /usr is shareable, read-only data. This means that /usr shall be shareable between various hosts and must not be written to, except in the case of system administrator intervention (installation, update, upgrade). Any information that is host-specific or varies with time is stored elsewhere.

Aside from /home/, /usr/ usually contains by far the largest share of data on a system. Hence, this is one of the most important directories in the system as it contains all the user binaries, their documentation, libraries, header files, etc. X and its supporting libraries can be found here. User programs like telnet, ftp, etc., are al

Птн 08 Фев 2013 12:17:04
>>43089327
Header files needed for compiling userspace source code..
/usr/lib: Libraries

Libraries for the binaries in /usr/bin/ and /usr/sbin/.
/usr/sbin: System binaries

Non-essential system binaries of use to the system administrator. This is where the network daemons for the system reside, along with other binaries that (generally) only the system administrator has access to, but which are not required for system maintenance and repair. Normally, these directories are never part of normal user&amp;#39;s $PATHs, only of root&amp;#39;s (PATH is an environment variable that controls the sequence of locations that the system will attempt to look in for commands).
/usr/share: Architecture independent data

This directory contains &amp;#39;shareable&amp;#39;, architecture-independent files (docs, icons, fonts etc). Note, however, that &amp;#39;/usr/share&amp;#39; is generally not intended to be shared by different operating systems or by different releases of the same operating system. Any program or package which contains or requires data that do not need to be modified should store these data in &amp;#39;/usr/share/&amp;#39; (or &amp;#39;/usr/local/share/&amp;#39;, if manually installed - see below). It is recommended that a subdirectory be used in /usr/share for this purpose.
/usr/src: Source code

The &amp;#39;linux&amp;#39; sub-directory holds the Linux kernel sources, and header-files.
/usr/local: Local hierarchy

Optional tertiary hierarchy for local data. The original idea behind &amp;#39;/usr/local&amp;#39; was to have a separate (&amp;#39;local&amp;#39;) &amp;#39;/usr/&amp;#39; directory on every machine besides &amp;#39;/usr/&amp;#39;, which might be mounted read-only from somewhere else. It copies the structure of &amp;#39;/usr/&amp;#39;. These days, &amp;#39;/usr/local/&amp;#39; is widely regarded as a good place in which to keep self-compiled or third-party programs. This directory is empty by default in Arch Linux. It may be used for manually compiled software installations if desired. pacman installs to /usr/, therefore, manually compiled/installed software installed to /usr/local/ may peacefully co-exist with pacman-tracked system software.
/var: Variable files

Variable files, such as logs, spool files, and temporary e-mail files. On Arch, the ABS tree and pacman cache also reside here. Why not put the variable and transient data into /usr/? Because there might be circumstances when /usr/ is mounted as read-only, e.g. if it is on a CD or on another computer. &amp;#39;/var/&amp;#39; contains variable data, i.e. files and directories the system must be able to write to during operation, whereas /usr/ shall only contain static data. Some directories can be put onto separate partitions or systems, e.g. for easier backups, due to network topology or security concerns. Other directories have to be on the root partition, because they are vital for the boot process. &amp;#39;Mountable&amp;#39; directories are: &amp;#39;/home&amp;#39;, &amp;#39;/mnt&amp;#39;, &amp;#39;/tmp&amp;#39;, &amp;#39;/usr&amp;#39; and &amp;#39;/var&amp;#39;. Essential for booting are: &amp;#39;/bin&amp;#39;, &amp;#39;/boot&amp;#39;, &amp;#39;/dev&amp;#39;, &amp;#39;/etc&amp;#39;, &amp;#39;/lib&amp;#39;, &amp;#39;/proc&amp;#39; and &amp;#39;/sbin&amp;#39;.
/var/abs

The ABS tree. A ports-like package build system hierarchy containing build scripts within subdirectories corresponding to all installable Arch software.
/var/cache/pacman/pkg

The pacman package cache.
/var/lib: State information

Птн 08 Фев 2013 12:18:53
>>43089371
/var: Variable files

Variable files, such as logs, spool files, and temporary e-mail files. On Arch, the ABS tree and pacman cache also reside here. Why not put the variable and transient data into /usr/? Because there might be circumstances when /usr/ is mounted as read-only, e.g. if it is on a CD or on another computer. &amp;#39;/var/&amp;#39; contains variable data, i.e. files and directories the system must be able to write to during operation, whereas /usr/ shall only contain static data. Some directories can be put onto separate partitions or systems, e.g. for easier backups, due to network topology or security concerns. Other directories have to be on the root partition, because they are vital for the boot process. &amp;#39;Mountable&amp;#39; directories are: &amp;#39;/home&amp;#39;, &amp;#39;/mnt&amp;#39;, &amp;#39;/tmp&amp;#39;, &amp;#39;/usr&amp;#39; and &amp;#39;/var&amp;#39;. Essential for booting are: &amp;#39;/bin&amp;#39;, &amp;#39;/boot&amp;#39;, &amp;#39;/dev&amp;#39;, &amp;#39;/etc&amp;#39;, &amp;#39;/lib&amp;#39;, &amp;#39;/proc&amp;#39; and &amp;#39;/sbin&amp;#39;.
/var/abs

The ABS tree. A ports-like package build system hierarchy containing build scripts within subdirectories corresponding to all installable Arch software.
/var/cache/pacman/pkg

The pacman package cache.
/var/lib: State information

Persistent data modified by programs as they run (e.g. databases, packaging system metadata etc.).
/var/lock: Unsharable lock data

Files keeping track of resources currently in use.
/var/log: Log files

Log files.
/var/mail: User mail

Shareable directory for users&amp;#39; mailboxes.
/var/run: State information

Unshareable data about the running system since last boot (e.g. currently logged-in users and running daemons).
/var/spool: Queues

Spool for tasks waiting to be processed (e.g. print queues and unread mail).
/var/spool/mail

Deprecated location for users&amp;#39; mailboxes.
/var/tmp: Preservable temporary files

Temporary files to be preserved between reboots.

Птн 08 Фев 2013 12:25:13
>>43089145
Лол. Проигрываю с этого вайпера-недоделка.

Птн 08 Фев 2013 12:26:00
>>43087150
в пакете тред в пакете.жпг

Птн 08 Фев 2013 12:28:39
>>43089600


The ABS tree. A ports-like package build system hierarchy containing build scripts within subdirectories corresponding to all installable Arch software.
/var/cache/pacman/pkg

The pacman package cache.
/var/lib: State information

Persistent data modified by programs as they run (e.g. databases, packaging system metadata etc.).
/var/lock: Unsharable lock data

Files keeping track of resources currently in use.
/var/log: Log files

Log files.
/var/mail: User mail

Shareable directory for users&amp;#39; mailboxes.
/var/run: State information

Unshareable data about the running system since last boot (e.g. currently logged-in users and running daemons).
/var/spool: Queues

Spool for tasks waiting to be processed (e.g. print queues and unread mail).
/var/spool/mail

Deprecated location for users&amp;#39; mailboxes.
/var/tmp: Preservable temporary files

Птн 08 Фев 2013 12:28:58
>>43089693
X.org
2.1 KDM
2.2 KDE4
2.2.1 Metodo alternativo
2.3 GDM
2.4 SLiM

TTY (Teletype) Console 1-6

Per attivare il NumLock durante il normale avvio dalle console 1-6 (tty1 tty6), aggiungere la seguente linea al file /etc/rc.local:
for tty in /dev/tty?; do /usr/bin/setleds -D +num < "$tty"; done

Se si verificano comportamenti strani (il led del NumLock
← К списку тредов