https://wiki.archlinux.org/api.php?action=feedcontributions&user=Ispyhumanfly&feedformat=atomArchWiki - User contributions [en]2024-03-29T09:53:30ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=ProFTPD&diff=27770ProFTPD2007-08-14T19:42:12Z<p>Ispyhumanfly: ProFTPD server installation</p>
<hr />
<div>= ProFTPD Installation =<br />
pacman -Sy proftpd<br />
<br />
= Daemon Configuration =<br />
nano /etc/rc.conf ( add 'proftpd' to the DAEMONS list )<br />
<br />
= More to Follow =<br />
A more in depth installation & configuration tutorial we'll come about shortly...</div>Ispyhumanflyhttps://wiki.archlinux.org/index.php?title=ProFTPD&diff=27769ProFTPD2007-08-14T18:28:48Z<p>Ispyhumanfly: New page: === ProFTPD Installation === By using pacman... pacman -Sy proftpd</p>
<hr />
<div>=== ProFTPD Installation ===<br />
By using pacman...<br />
<br />
pacman -Sy proftpd</div>Ispyhumanflyhttps://wiki.archlinux.org/index.php?title=Fluxbox&diff=27598Fluxbox2007-08-08T06:15:15Z<p>Ispyhumanfly: /* Menumaker */</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
===Installing Fluxbox===<br />
Install fluxbox from the repositories. New users may want to also install menumaker and/or fluxconf.<br />
pacman -Sy fluxbox fluxconf<br />
<br />
Menumaker was moved to unsupported, to install you need download tarball from aur.<br />
wget http://aur.archlinux.org/packages/menumaker/menumaker.tar.gz<br />
tar xvf menumaker.tar.gz<br />
cd menumaker<br />
makepkg<br />
Install it with:<br />
pacman -U menumaker-0.99.7-2-i686.pkg.tar.gz<br />
Modify if necessary.<br />
<br />
Remove fluxconf and menumaker if you want a more minimal install, usage of each will be covered but not required<br />
<br />
===Starting Fluxbox===<br />
====Method 1: kdm/gdm====<br />
This will automaticly be added to the session types. Select fluxbox from the menu.<br />
<br />
''Note:'' you will have to have '''login manager''' enabled at first. For instructions how to do that, look [[Adding_a_login_manager_(KDM%2C_GDM%2C_or_XDM)_to_automatically_boot_on_startup|here]].<br />
<br />
====Method 2: xinitrc====<br />
In your home folder add the code below to your .xinitrc file<br />
exec fluxbox <br />
or if you like to use the 'startfluxbox' file use :<br />
exec startfluxbox <br />
It is beter to use 'startfluxbox', because only then file ~/.fluxbox/startup file is used.<br />
Remember: there can only be one exec line in your .xinitrc file<br />
<br />
''Note'' : if it crashes on startup, it may be a locale problem.. Setting LC_ALL to the default "C" locale, may avoid this crash. [http://bbs.archlinux.org/viewtopic.php?t=25797 1]<br />
Then you can start fluxbox with startx command.<br />
<br />
===Configuring Fluxbox===<br />
====Menus====<br />
=====Fast method:=====<br />
build in command :<br />
fluxbox-generate_menu<br />
this command will generate a .fluxbox/menu/ file based on your installed programms. There is also "helper / regenerate menu" in the fluxbox menu.<br />
<br />
<br />
<br />
======Archlinux xdg menu======<br />
Requires [http://aur.archlinux.org/packages.php?do_Details=1&ID=10535&O=0&L=0&C=0&K=archlinux-xdg-menu&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=ndarchlinux-xdg-menu Archlinux xdg menu] <br><br />
xdg_menu --fullmenu --format fluxbox --root-menu /etc/xdg/menus/arch-applications.menu >~/.fluxbox/menu<br />
Tip: replace default xterm/urxvt<br />
sed -i 's/xterm/urxvt/g' ~/.fluxbox/menu<br />
More info<br />
xdg_menu --help<br />
See also: <br />
[[XdgMenu|Archlinux xdg menu]]<br />
<br />
<br />
=====Creating a custom menu with fluxconf=====<br />
To start the menu section of fluxconf run:<br />
fluxmenu<br />
In the window you will see three columns: Type, Title, & Command/Comment.<br><br />
Clicking on an entry in this will allow you to edit it.<br><br />
Clicking on "Add sub" will add a submenu.<br><br />
Clicking on "Add exec" will add a command.<br><br />
<br />
the type column has several valid options:<br />
#begin, required to start the menu file. The title option is the menu header.<br><br />
#submenu, a "folder" inside the menu. Title is the name of the submenu.<br><br />
#exec, a command line. Title is what is shown and Command/Comment is the command to be executed.<br />
#separator, a divider in the menu. No arguments to this one.<br />
#workspaces, a list of workspaces and what applications are running on each. Title is what will be shown to the user.<br />
#stylesdir, a directory containing styles. Title is the path to the dir. Recommended that you put this into its own subdirectory as it can get quite large. directories to use: /usr/share/fluxbox/styles ~/.fluxbox/styles .<br />
#config, a menu with many options for configuring behavior of fluxbox. Title is the name of the menu shown to the user.<br />
#reconfig, reloads the config file. Title is the title shown to the user.<br />
#restart, restarts fluxbox. Title is the title shown to the user.<br />
#exit, exit fluxbox, will drop back to the desktop manager or exit X depending on the startup method you used. Title is the title shown to the user.<br />
<br />
Remember to hit save before closing<br />
=====Manualy=====<br />
Use comand:<br />
nano ~/.fluxbox/menu<br />
Then write lines in this style:<br />
[exec] (name) {command}<br />
If you want to make submenu write:<br />
[submenu] (Name)<br />
...<br />
...<br />
[end]<br />
Then done save and exit. There is no need to restart fluxbox.<br />
<br />
====Hotkeys====<br />
Fluxbox offers a basic hotkeys functionality. fluxbox key file is:<br />
~/.fluxbox/keys<br />
fluxconf offers a method of editing this in GUI with the command:<br />
fluxkeys<br />
The Mod1 button corresponds to Alt and Mod4 corresponds to Meta (not a standard key but many map meta to the win key)<br><br />
The First text box is for a button and the second is for an action. select execCommand to set a command and put the name of the command into the 3rd text box.<br />
<br />
More functions of this can be used from the 2nd text box (A drop down menu is available) <br />
====Workspaces====<br />
Fluxbox defaults to having four workspaces available to the user. available with the alt+F1-4 keys or the arrows on the toolbar next to where it says "one"<br><br />
Right clicking on desktop and going to your Workspaces menu (menumaker users: FluxBox>Workspaces, fluxconf users: the workspaces title) will let you interact with the workspaces.<br />
Workspaces Menu:<br />
Icons - shows minimized applications<br />
--separator--<br />
Workspaces names (default: one,two,three,four) - Shows all the applications on that desktop<br />
--separator--<br />
New Workspace - Adds a workspace<br />
Edit Current workspace name - lets you title your workspace whatever you want. Will show up on the left side of the toolbar <br />
Remove Last - Removes the last workspace on the list, dumps all of the applications running on that desktop into the one before it<br />
====Background====<br />
Setting the background requires a background setter you will need to install one of these packages:<br />
*eterm (recommended)<br />
*feh (lacks menu transparency)<br />
there are others but these are the most recommended two, to see others check out the fbsetbg documentation in the "Additional Links section"<br />
To set the background:<br />
fbsetbg /path/to/background.image<br />
Fluxbox however does not set your background on bootup however you can make it do so by adding the below code to a bootup script, covered below:<br />
fbsetbg -l<br />
<br />
(It is of use only if you have previously issued the command with a valid image)<br />
<br />
You can also add (or modify) the following line to the file ~/.fluxbox/init to something like this:<br />
session.screen0.rootCommand: fbsetbg /path/to/wallpaper<br />
<br />
Or simply:<br />
session.screen0.rootCommand: fbsetbg -l<br />
<br />
<br />
Additional notes for people who like to change wallpaper a lot.<br />
<br />
Place the following submenu in your fluxbox menu<br />
<br />
[submenu] (Backgrounds)<br />
[wallpapers] (~/.fluxbox/backgrounds)<br />
[wallpapers] (/usr/share/fluxbox/backgrounds)<br />
[end]<br />
<br />
Then put your background images into ~/.fluxbox/backgrounds or any other folder you specify, they will then appear in the same fashion as your styles.<br />
<br />
====Theming====<br />
Links to some theme sites are provided below.<br><br />
To install a theme extract the archive to a stylesdir the default ones are:<br />
*global - /usr/share/fluxbox/styles <br />
*user only - ~/.fluxbox/styles <br />
====Autostarting Applications====<br />
xinitrc users should put all code into thier .xinitrc. However, fluxbox provides functionality to autostart applications on its own.<br><br />
The ~/.fluxbox/startup file is a script for autostarting applications as well as starting fluxbox itself.<br><br />
The <nowiki>#</nowiki> symbol denotes a comment.<br><br />
<br />
a sample file:<br />
fbsetbg -l <nowiki>#</nowiki> sets the last background set, very useful and recommended.<br />
<nowiki>#</nowiki> In the below commands the ampersand symbol (&) is required on all applications that do not terminate immediately. <br />
<nowiki>#</nowiki> failure to provide them will cause fluxbox not to start.<br />
idesk & <br />
xterm &<br />
<nowiki>#</nowiki> exec is for starting fluxbox itself, don't put an ampersand (&) after this or fluxbox will exit immediately<br />
exec /usr/bin/fluxbox<br />
<nowiki>#</nowiki> or if you want to keep a log, uncomment the below command and comment out the above command:<br />
<nowiki>#</nowiki> exec /usr/bin/fluxbox -log ~/.fluxbox/log<br />
===Additional Links===<br />
<br />
[http://fluxbox.sourceforge.net/ Fluxbox Homepage]<br><br />
[http://gentoo-wiki.com/HOWTO_Fluxbox gentoo-wiki Fluxbox HowTo]<br><br />
[http://www.gentoo.org/doc/en/fluxbox-config.xml gentoo Fluxbox Documentation]<br><br />
[http://box-look.org/ Themes for Fluxbox]<br><br />
[http://fluxbox-wiki.org/ Fluxbox Wiki]<br><br />
[http://www.xs4all.nl/~hanb/software/fbsetbg/fbsetbg.html fbsetbg documentation]<br></div>Ispyhumanflyhttps://wiki.archlinux.org/index.php?title=Pacman&diff=27156Pacman2007-07-23T06:04:15Z<p>Ispyhumanfly: /* Querying the Package Database */</p>
<hr />
<div>[[Category:Package management (English)]]<br />
[[Category:Utilities (English)]]<br />
[[Category:Tutorials (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Česky|:Pacman (Česky)}}<br />
{{i18n_entry|Deutsch|:Pacman (Deutsch)}}<br />
{{i18n_entry|English|:Pacman}}<br />
{{i18n_entry|Nederlands|:Pacman (Nederlands)}}<br />
{{i18n_entry|Español|:Pacman (Español)}}<br />
{{i18n_entry|Français|:Pacman (Français)}}<br />
{{i18n_entry|Polski|:Pacman (Polski)}}<br />
{{i18n_entry|Русский|:Pacman (Русский)}}<br />
{{i18n_entry|简体中文|:Pacman (简体中文)}}<br />
{{i18n_links_end}}<br />
<br />
==Overview==<br />
The '''Pacman''' package manager is one of the great highlights of Arch Linux. It combines a simple binary package format with an easy-to-use build system (see [[makepkg]] and [[ABS]]). '''Pacman''' makes it possible to easily manage packages, whether they be from the official Arch repositories or the user's own builds.<br />
<br />
'''Pacman''' can keep a system up to date by synchronizing package lists with the master server. This server/client model also allows you to download/install packages with a simple command, complete with all required dependencies (similar to Debian's apt-get).<br />
<br />
==Usage==<br />
<br />
To really learn what pacman can do, read <code>man pacman</code>. The below is just a small sample of operations that can be performed.<br />
<br />
===Installing and Removing Packages===<br />
Before installing and upgrading packages, it is a good idea to synchronize the local package database with the remote repositories.<br />
<br />
pacman -Sy<br />
or<br />
pacman --sync --refresh<br />
<br />
To install or upgrade a single package or list of packages (including dependencies), issue the following command:<br />
<br />
pacman -S package_name1 package_name2<br />
<br />
Sometimes there are more versions of a package in different repositories (e.g. extra and testing). You can specify which one to install:<br />
<br />
pacman -S extra/package_name<br />
pacman -S testing/package_name<br />
<br />
You can also refresh the package database before installing a package in one command:<br />
<br />
pacman -Sy package_name<br />
<br />
To remove a single package, leaving all of its dependencies installed:<br />
<br />
pacman -R package_name<br />
<br />
To remove all of the packages dependencies which aren't used by any other installed package:<br />
<br />
pacman -Rs package_name<br />
<br />
To remove a package without checking dependencies:<br />
<br />
pacman -Rd package_name<br />
<br />
===Upgrading the System===<br />
<br />
'''Pacman''' can update all packages on the system with just one command. This could take quite a while depending on how up-to-date your system is.<br />
<br />
pacman -Su<br />
<br />
However, the best option is to synchronize the repository databases AND update your system in one go with the following:<br />
<br />
pacman -Syu<br />
<br />
===Querying the Package Database===<br />
<br />
'''Pacman''' can search the package database for a list of packages, you can enter part of the package name to search for all packages matching the string:<br />
<br />
pacman -Ss package<br />
<br />
To search installed packages only:<br />
<br />
pacman -Qs package<br />
<br />
Once you know the name of the package you are looking for, you can display some information on the package. Note that ''query info'' (-Qi) will show more info than ''sync info'' (-Si), as long as the package is installed.<br />
<br />
pacman -Si package <br />
pacman -Qi package<br />
<br />
For a list of files contained in a package:<br />
<br />
pacman -Ql package<br />
<br />
For a list of files no longer in use by any currently installed packages:<br />
<br />
pacman -Qe <br />
<br />
You can also query what package a file on your system belongs to.<br />
<br />
pacman -Qo /path/to/file<br />
<br />
===Other Usage===<br />
<br />
'''Pacman''' is quite an extensive package management tool, here is just a brief collection of other features.<br />
<br />
* Download a package without installing it:<br />
pacman -Sw package_name<br />
<br />
* Install a local package (not from a repository):<br />
pacman -U /path/to/package/package_name-version.pkg.tar.gz<br />
<br />
* Fully clean the package cache (/var/cache/pacman/pkg):<br />
pacman -Scc<br />
<br />
For a more detailed list of switches please refer to <code>pacman --help</code> or <code>man pacman</code>.<br />
<br />
<br />
==Configuration==<br />
Pacman configuration is located in <code>/etc/pacman.conf</code>. In depth information about the configuration file can be found in <code>man pacman.conf</code>.<br />
<br />
===General options===<br />
General options are in [options] section. Read the man page or look in the default pacman.conf for information on what can be done here.<br />
<br />
===Repositories===<br />
In this section you define which repositories to use, as referred to in /etc/pacman.conf, and then listed in /etc/pacman.d/. They can be defined directly there or you can include them from another file. The latter is useful for the official repositories which have a lot of [[mirrors]]. Avoid using ftp.archlinux.org as it is [http://www.archlinux.org/news/302/ throttled].<br />
<br />
<pre><br />
[repository-name]<br />
Server = ftp://server.net/repo<br />
</pre><br />
<br />
<pre><br />
[current]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/current<br />
</pre><br />
<br />
==Related links==<br />
[[Improve Pacman Performance]]<br><br />
[[Colored Pacman output]]<br><br />
[[Downgrade packages]]<br><br />
[[Redownloading all installed packages]]<br><br />
[[Server_configuration|Server configuration in pacman.conf]]<br><br />
[[ArchLinux User-community Repository (AUR)]]<br><br />
[[Local repository HOW-TO]]<br><br />
[[Custom local repository with ABS and gensync]]<br><br />
[[Howto Upgrade via Home Network]] (Network Shared Pacman Cache)<br><br />
[[rucksack]]<br><br />
[[Pacman GUI Frontends]]<br><br />
[[Pacman_Aliases|Pacman Aliases (for bash)]]</div>Ispyhumanflyhttps://wiki.archlinux.org/index.php?title=Gnome_Menu_tweaking&diff=27104Gnome Menu tweaking2007-07-20T15:52:33Z<p>Ispyhumanfly: /* User menus */</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
Most Gnome users complain about the menu. Changing menu entries system-wide or for one or several users alone is poorly documentated.<br />
<br />
===User menus===<br />
(Note: It was believed that this article was obsolete. gnome 2.14 has its own menu editor (half functional). Half-functional indeed, so using this<br />
manual method is still effective until the new gnome menu editor is fully functional.)<br />
<br />
As a user, you may add starters for applications to your desktop. Once you have created and tested one, start nautilus and type <code>applications:///</code> in the location bar. Take the menu group you want, and place your starter there. You now have a new entry in your Gnome menu.<br />
<br />
===Group menus, System menus===<br />
You find common gnome menu entries as 'appname.desktop' objects inside /opt/gnome/share/applications. <br />
* Edit one of them to fit your needs for a new application, then save it.<br />
* Save it as a menu entry for all users <br> In common, you will set this files permissions to 644 (root: rw group: r others: r), so all users can see it.<br />
* Save it as a menu entry for a group or user alone <br> You may also have different user permissions; for example, some menu entries should only be available for a group or for one user.<br />
<br />
Here is an example how a Scite menu entry definition file could look:<br />
<br />
<pre><br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Name=SciTE<br />
Comment=SciTE editor<br />
Type=Application<br />
Exec=/usr/bin/scite<br />
Icon=/usr/share/pixmaps/scite_48x48.png<br />
Terminal=false<br />
Categories=GNOME;Application;Development;<br />
StartupNotify=true<br />
</pre><br />
<br />
Hint: Folders in Gnome menu:<br />
<br />
When you create a folder in applications:/// and want to change the icon - Right click, and choose "edit launcher" then change icon. If you right click and choose "Properties" and change the icon the icon will not change in menu.<br />
<br />
==See also==<br />
* [[Gnome]]<br />
* [[Gnome Tips]]</div>Ispyhumanflyhttps://wiki.archlinux.org/index.php?title=Gnome_Menu_tweaking&diff=27103Gnome Menu tweaking2007-07-20T15:51:43Z<p>Ispyhumanfly: /* User menus */</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
Most Gnome users complain about the menu. Changing menu entries system-wide or for one or several users alone is poorly documentated.<br />
<br />
===User menus===<br />
(Note: It was believed that this article was obsole. gnome 2.14 has its own menu editor (half functional). Half-functional is right, so using this<br />
manual method is still effective until the new gnome menu editor is fully functional.)<br />
<br />
As a user, you may add starters for applications to your desktop. Once you have created and tested one, start nautilus and type <code>applications:///</code> in the location bar. Take the menu group you want, and place your starter there. You now have a new entry in your Gnome menu.<br />
<br />
===Group menus, System menus===<br />
You find common gnome menu entries as 'appname.desktop' objects inside /opt/gnome/share/applications. <br />
* Edit one of them to fit your needs for a new application, then save it.<br />
* Save it as a menu entry for all users <br> In common, you will set this files permissions to 644 (root: rw group: r others: r), so all users can see it.<br />
* Save it as a menu entry for a group or user alone <br> You may also have different user permissions; for example, some menu entries should only be available for a group or for one user.<br />
<br />
Here is an example how a Scite menu entry definition file could look:<br />
<br />
<pre><br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Name=SciTE<br />
Comment=SciTE editor<br />
Type=Application<br />
Exec=/usr/bin/scite<br />
Icon=/usr/share/pixmaps/scite_48x48.png<br />
Terminal=false<br />
Categories=GNOME;Application;Development;<br />
StartupNotify=true<br />
</pre><br />
<br />
Hint: Folders in Gnome menu:<br />
<br />
When you create a folder in applications:/// and want to change the icon - Right click, and choose "edit launcher" then change icon. If you right click and choose "Properties" and change the icon the icon will not change in menu.<br />
<br />
==See also==<br />
* [[Gnome]]<br />
* [[Gnome Tips]]</div>Ispyhumanflyhttps://wiki.archlinux.org/index.php?title=MEncoder&diff=25168MEncoder2007-06-02T02:05:36Z<p>Ispyhumanfly: </p>
<hr />
<div>A both complete and comprehensive article regarding mencoder is presently under development. Please check back to this page within the next several days for an update. This article will include an advanced Perl script that will assist in automating the encoding process. For information concerning this article and it's status, please send me ( ispyhumanfly ) a message via the wiki.</div>Ispyhumanflyhttps://wiki.archlinux.org/index.php?title=MEncoder&diff=25167MEncoder2007-06-02T02:03:46Z<p>Ispyhumanfly: A comprehensive mencoder encoding guide.</p>
<hr />
<div>A both complete and comprehensive article regarding mencoder is presently under development. Please check back to this page within the next several days for an update. This article will include an advanced Perl script that will assist in automating the encoding process. For information concerning this article and it's status, please send me a message via the wiki.</div>Ispyhumanfly