Packages

In order to use acoc you should start it with

for example, or you can create an alias like this:

For the first initial setup you may want to use our amavisconf utility.

From amavisd-new-2.5.2-1 we no longer use a random uid/gid, but dedicated ones. Because of this amavis service will not start if you have it installed before, so you have to correct this by issuing these commands:

You should chown any other amavis-owned stuff you may have lying around, these are only the default ones.

Setting up Android SDK :

You should open a new shell to have android-sdk/tools/ in the path. After that, just type "adb" (not "./adb") as mentionned in following links.

If you want to use your Android phone as a proxy, see these pages :

Asciidoc has a number of configuration files under /etc/asciidoc and it’s easy to get lost in that directory.

Regarding pdf (dblatex) generation, here are some options you can set:

Also, If you are using iptables, please uncomment this line in /etc/sysconfig/firewall:

After that do not forget to restart iptables with:

After installing this package, please run

to setup B2evolution.

Since version 2.6.24, the bcm43xx driver is deprecated, replaced by the b43 and b43legacy modules.

The module should be loaded automatically, in case it isn’t, you can load it manually:

or:

You must bring the device up with ifconfig before doing any other configuration steps.

Since the channel must be set manually, first do a scan:

Then you can set it:

Finally set your essid:

Ready!

Some tips and trick for use with barpanel:

Then, change the theme in your ~/.barpanel/config.xml configuration file.

Enjoy.

Cairo-Clock requires the Composite option to be enabled in your Xorg configuration. To enable it, add the following lines to /etc/X11/xorg.conf:

After you installed ccache, it won’t be enabled by default.

First, you need to determine who is allowed to use ccache. You have to add each user to the ccache group. If you want to allow using ccache from chrooted builds, then you need to add the fst user:

Second, you need to somehow let the build system to use ccache, and not the compiler directly. If you use makepkg, this is enabled by default (you can disable it with the -B option). If you build manually, then you are on your own, though usually there are two ways to do so:

Configure your hardware specific options under /etc/sysconfig/cpupower. See the man pages for cpupower-frequency-set and cpupower-set for more information. When you are finished configuring, use this command as root to enable it at boot time:

After installing cpuspeed, make sure you edit the configuration file before starting it. The configuration file is located in /etc/cpuspeed.conf.

Set the correct CPUFreq driver name in the confiuration file by setting the DRIVER value. for eg: if you want to use the p4-clockmod driver, your cpuspeed configuration file should contain:

For a list of drivers, check this directory /lib/modules/your_kernel_version/kernel/arch/i386/kernel/cpu/cpufreq

Follow these steps to when using cryptsetup-luks:

First, please note that darcs comes with a very good HTML documentation, which is available under the /usr/share/doc/darcs-*/manual dir. That’s the place where everything is properly documented, not the manpage. Using darcs [subcommand] -h is usable only as a reference, too.

If you’re completely new to darcs, then start at /usr/share/doc/darcs-*/manual/node4.html.

Please also note that in order for the darcs send command to work properly, you must properly configure your mail transport agent to relay outgoing mail. For example, if you are using postfix, you need to edit /etc/postfix/main.cf, see the Using a relay host part of the postfix package documentation for more info.

Please configure /etc/ddclient/ddclient.conf before running ddclient!

Samples for common configurations can be found in: /usr/share/doc/ddclient-$package_version/sample*

Additional details and instructions can be found in: /usr/share/doc/ddclient-$package_version/README

Once you have finished configuring the ddclient.conf file, you can start ddclient as a daemon by running as root, the following command:

If you are in trouble setting up your dhclient, use the following options. These are quite good defaults:

To be able to use this package as intended, you will have to:

To be able to use this package as intended, you will have to:

To populate the DSPAM database, you need to follow several steps.

If you want to use the postgresql, sqlite3 or Berekely DB4 backends you can find instructions in the dspam documentation.

This contains hardware fixups for Efika 5200b so that the hardware can work. It is not necessary to use this if you don’t have this hardware platform. Special thanks to CRUX PPC, which is where this script is from, with some modifications for Frugalware Linux. Instructions for usage:

1) Locate the 2 bootlines at the bottom of the efika.forth script under /boot. The top is setup for booting to the serial port and the bottom is for booting to a framebuffer console.

2) Replace hd:1 with the boot device and the partition where the kernel you are booting is located.

3) Replace vmlinuz with the full path to the kernel you wish to boot.

4) Replace the root=/dev/sda3 parameter to the proper device path for where the root partition is located.

5) Append any other kernel parameters you need.

6) You’re done!

To be able to use this package as intended, you will have to:

If you got disconnected from servers and getting some #20004 errors, then run as pbweb AS ROOT!!!

Then try again :)

Regards

To use fbterm, your user needs to be a member of the video group.

To use a background image, install the fbv package and run fbterm-bi.

To test festival, try:

This version comes with a system init script now. You have to run the firestarter executable from the command line (in an X driven console) first to generate the initial start-up scripts.

To add it to startup, run this:

To remove it from startup:

Once you have the .flv file you want to share, you need to symlink flowplayer.controls.swf, flowplayer.min.js and flowplayer.swf from /usr/share/flowplayer and the code sniplet from /usr/share/flowplayer/example/index.html.

This driver is under constant change, therefore no "stable" branch exists. Also, communications with the author led nowhere, that might explain some weirdness of building it, getting the latest stable version number etc. Mail

Fuse is a virtual filesystem "helper" which makes possible to mount unusual things as a filesystem. It is achieved by using a simple program, which runs in user space, to provide data that can be represented by the fuse kernel module as a filesystem. The interpreter program is a less complex one than a kernel-space module, which is much harder to write. In Frugalware, regular users of a given box can mount filesystems by fuse. First as root, let’s install the tools needed:

Then you have to add the fuse service to the startup list and start it manually for now:

Now, having the base of fuse, we need to install the programs for each specific filesystem type. To get a hint on what is available, you can issue the following command:

The two most used (ftp, ssh) plugins can be installed by running the following command. Beware, the ftp fs is a perl module, and it seems a bit memory hungry / buggy / slow so therefore it might be replaced by CurlFtpFS in the future.

Then, you can mount a remote dir with sftp access as a regular user doing:

You can also unmount it as a regular user doing:

For have a full bluetooth support with gnome install obex-data-server # pacman-g2 -S obex-data-server

The most common usage of this applications is something like this:

This app does not have any webserver, SQL server nor IMAP server in its depends, which is intentional. Anyway, if you plan to use it, you should set up a webserver and an IMAP server. The SQL server is optional, but it’s the most easiest-to-use preferences container.

Additionally this app is not configured in any way: there are far too many customizable settings, so the packager cannot know how to set them for your particular needs. Installation instructions can be found in the INSTALL file.

Configuration examples can be found in /etc/hostapd. You must edit the following files located in /etc/hostapd to configure hostapd:

hostapd.allow hostapd.conf hostapd.deny

The daemon script usable via the service command expects you to have configured it properly via these files before it can be used.

Welcome to the README! Thanks for taking the time to find it ;-)

For an introduction to the wonderful world of HylaFAX(tm), please see http://www.hylafax.org/. Beginners should head directly to the docs:

If you have a question which you think relates only to the FPM version of HylaFAX post a bug to the Frugalware BTS:

You should also be aware of the following system modification: FaxMaster is added to /etc/postfix/aliases after installation automatically.

The default configuration files can be found under /var/spool/hylafax/config/defaults/. You can copy these files to the /var/spool/hylafax/etc/ directory and modify them there.

Enjoy!

I have included a custom shell script called icewm-menus, for use with the icewm menu file. An example menus file is also include at /usr/share/icewm/menus. It uses standard shell syntax, so you can easily use shell variables, etc, to create dynamic menus in icewm through my script and the usage of your local $HOME/.icewm/menus file. To use it, use the following syntax in your menu file: menuprog "(folder name)" (icon name) icewm-menus (menu switch to use) If setup correctly, you’ll wind up with menus generated by the output of the shell script. Have fun configuring icewm.

After installing this package, please run /usr/bin/joomlasetup as root to setup Joomla

If you want to rip a video DVD, install the transcode package as well.

If you do not know the keycodes for the keys you wish to remap the joystick events to, then please install the xev program. It will help you to identify them. Moving on, the /etc/kbstick.conf is the system level configuration file the shell script reads from if the user does not have a .kbstickrc in their home directory. Syntax is the same in both cases, and the configuration file has some comments to give you an idea of what each variable does. I have set the default up/down/left/right key mappings to what my laptop uses for them and the buttons will have to be manually defined to their proper keycodes. If you need any further help, please email the maintainer of this package.

Loading the new kernel:

Booting it:

First of all, we have to install package called keychain. (pacman-g2 -S keychain)

In the next step we have to create a new key. A key stands from two parts, a public and a private part. It means two different files in your ~/.ssh/ directory.

Your key is generated by a program called ssh-keygen. It’s a part of openssh package. Run ssh-keygen -t dsa! You’ll see something like this:

It’ll generate for us the two parts of the key. The program asks where do you want to save the keys, it’s good to simply push an enter. After that You have to type in the passphrase of the key two times. It’s really important to chose a hard passphrase. It should contain lower-/uppercase characters, digits, possibly special characters too. The length must be at least 10 characters! We have to type in this passphrase only once after every restart we shouldn’t choose an easy one.

If everything works fine, then we have an id_dsa and an id_dsa.pub file in our ~/.ssh/ directory.

Now, we would like to use our newly generated key. We have to do the following:

Good to know, that this time(I mean when we run scp and ssh commands) we can’t use our key’s passphrase, so we have to use our password on the remore_machine. If it’s done without any mistake on next login the remote_machine will ask for our key’s passphrase.

And here comes keychain. In openssh package there is a program called ssh-agent. You can store keys in ssh-agent. Keychain just makes easier using of ssh-agent and adds some new features.

This time i assume that we use bash. If we would like to use keychain with an other shell, then we can use man keychain:-) So, let’s take out favourite editor and add the following lines to ~/.bash_profile file:

ksplice is handy in case there is a serious security fix and you don’t want or can’t afford rebooting your system immediately.

Let’s pick an example, the kernel-2.6.28-6anacreon3 update, which added CVE-2009-2692.patch.

First update FST so that you will have the patch:

Now create a working dir:

Now create the ksplice update:

Then apply it:

To view all applies updates, or a specific one:

To revert one:

Howto setup KVpnc for use without root password - sudo

So, you feel like using lilo, do you? Well, here you will find instructions for configuring lilo to work with Frugalware. Some things to keep in mind:

You will find an example lilo.conf in /etc/lilo.conf already. You will need to tweak it in order for it to match your system’s booting setup. The default structure is designed to reflect the most common setup I know of, but may still require a lot of modifications. For more information on lilo, please refer to man lilo and man lilo.conf.

After installing lineakd, make sure you create a configuration file before starting it.

Example configuration files are located in /usr/share/doc/lineakd-*/.

Don’t forget to copy the configuration file to /etc/lineakd after you create it.

You can then start the lineak daemon by running the following command:

After installing lirc you need to take the following steps:

Lmsensors is a hardware monitoring tool which is able to read thermal and voltage values and fan speeds from the sensor chips of your motherboard. Before running sensors you have to run sensors-detect as root to initialize them. It will autodetect your hardware and define which kernel modules you need to get it working properly, and tell you how to autoload them during boot.

So if you want to use lmsensors try to run

and say YES at end of sensors-detect to write /etc/sysconfig/lm_sensors.

Then issue:

There is no any kind of http server in mailman’s depends. It’s because they are not needed to get a working mailman. Of cource if you want to provide archives and so don’t forget to install a http server.

If you like coloured man-pages then you can enable that feature by issuing

It is handled as a configuration file, so feel free to edit the colors in that file if you want.

You have to GRANT some privileges (at least for the operating user) to be able to use this package, as the installer does not GRANT them. The operating user requires ALTER, SELECT, INSERT, UPDATE and even DELETE privileges, regardless that the latter is not mentioned by upstream. For installation, INDEX, CREATE, DELETE, and DROP privileges are also required - this can be carried out if you provide the (MySQL) superuser’s credentials to the installer.

Do not forget to rm -rf /var/www/mantis/admin after a successful install to prevent hijacking your bugtracker, and change the default administrator’s password.

The MediaTomb Web UI can be reached at: http://localhost:49152/ To start MediaTomb: # service mediatomb start To start MediaTomb at boot: # service mediatomb add

After installing this package, please run /usr/bin/mediawikisetup as root to setup MediaWiki

For enable mod_mono module apache don’t forget to define the User/Group directives into /etc/httpd/conf/httpd.conf. For test the configuration of mod_mono into /etc/httpd/conf/httpd.conf : #mono settings Alias /demo /usr/lib/xsp/test MonoApplications "/demo:/usr/lib/xsp/test" MonoServerPath /usr/lib/mono/2.0/mod-mono-server2.exe <Directory /usr/lib/xsp/test> SetHandler mono </Directory> and check the result : http://localhost/demo/

You may want to forge a config file for yourself as /etc/monit/monitrc to be able to properly use Monit. Consult the online docs for details:

http://mmonit.com/monit/documentation/monit.html

After doing so you should issue a systemctl enable monit.service command to make use of this service.

You should edit the settings: videodevice, input, norm, frequency, width, height and target_dir in /etc/motion.conf

If the file already exists, it wont be overwritten by the package while upgrading. You can refer /etc/motion-dist.conf for configuring motion.

From munin-1.2.5-2 we no longer use a random uid/gid, but dedicated ones. Because of this munin service will not start if you have it installed before, so you have to correct this by issuing these commands:

You should chown any other munin-owned stuff you may have lying around, these are only the default ones.

You can configure MythTV this way:

For more information see MythTV documentation.

Ndiswrapper requires .inf and .sys files from a Windows(tm) driver to function. Download these to /root for example, then run:

After that you can delete them. They will be copied to the proper location. Once done, please run:

Check this list of drivers. You can get your possible hadware with:

Look for that on the above page for your driver.

Please have a look at the wiki for the FAQ, HowTos, Tips, Configuration, and installation information.

To enable IPv4 multicast DNS lookups, append mdns4 to the hosts line in /etc/nsswitch.conf. Use mdns6 for IPv6 or mdns for both.

Copy /etc/pawm.conf to $HOME/.pawm for your own local changes. If you want icons on your desktop, add a file to your $HOME/.pawm directory that starts with "app" and append an alphanumerical phrase of your choice to it. Then, write the file structure as follows:

<icon name> <x position> <y position> <name to display> <command>

Example:

firefox.xpm 40 40 firefox firefox

Other things to remember, you can only use xpm files for this method, and it takes the files from /usr/share/pixmaps. If I knew how to change this path to a directory the user has, I would.

Be sure to make your own file at $HOME/.pekwm/autostart if you use pekwm-session to auto-launch commands when you startup. I know pekwm has a start file for this, but my method launches it only at the start of your session, while the method pekwm uses starts everytime you restart/start pekwm. Use it well. You can find an example below:

dbus-session --exit-with-session --sh-syntax & feh --bg-scale "$HOME/.foo/bar" &

I have purposely left out a few perl modules from the dependencies array, because they are not needed to run perlpanel and drag in a lot of GNOME or other stuff you may not want. Below, you will find a list of these modules and what they do. If you find errors in this documentation, then please report it and I will look into it.

perl-xmms - perlpanel plugin interface to xmms perl-gnome2-vfs - various gnome plugin interfaces for perlpanel libgnomeui - for full libglade support in perlpanel

You should set

in /etc/php.ini in order to use php-cgi.

After installing this package, please run /usr/bin/phpbbsetup as root to setup phpBB

After upgrading, make sure to run the database update script

For use plymouth Just add kernel parameter : splash

In most cases you want to use pootle with mysql and apache. See here on how to configure them:

Also read these pages if you’re upgrading from Pootle 1.x:

This package relies on correct install of postfix’s virtual tables and it needs to be configured before usage. Be sure to read upstream’s /var/www/postfixadmin/INSTALL.TXT in order to accomplish the setup or upgrade. You should also take care of configuring apache to be able to use the web-based interface.

Should you want to make use of the autoreply (vacation) feature, install these packages as well: perl-mail-sender, perl-email-valid, perl-mime-charset, perl-log-dispatch, perl-mime-encwords, perl-params-validate and read upstream’s /var/www/postfixadmin/VIRTUAL_VACATION/INSTALL.TXT in order to setup autoreply (vacation) properly. Don’t forget to enable it in config.inc.php as well!

To use postgrey, put something along the lines of

in your /etc/postfix/main.cf (postfix 2.1 or newer is required.)

Don’t forget to change /etc/prosody.cfg.lua when needed For more informations about prosody’s configurtion, please take a look at : http://prosody.im/doc

If you want to add or delete JIDs you have to be in the prosody group You can do it with this command : usermod -aG prosody LOGIN_NAME

To start the daemon, type service prosody start To automaticly start the daemon at boot time, type service prosody add Please do NOT use prosodyctl start and stop

Note: You must find a PSX bios on your own, and place it in ~/.pSX/bios.

Because PulseAudio can be used as drop-in replacement for ESD you can fool GNOME into loading the PulseAudio daemon just like the traditional ESD daemon. To achieve this use the esdcompat script shipped with PulseAudio. Install pulseaudio-esd : pacman-g2 -S pulseaudio-esd Create a symlink from /usr/bin/esd to /usr/bin/esdcompat For more information on pulseaudio, please refer to http://www.pulseaudio.org/wiki/PerfectSetup

You’ll find pyro’s scripts in /usr/lib/python2.5/site-packages/Pyro/bin

The config files have to be in the /etc/quagga dir and have to be writeable by the quagga user (to be able to save config from the daemon’s shell).

Neither of the daemons will start till you edit the config files and rename/move them from *.conf.sample to *.conf (be careful to the uid/gid).

You have to enable explicitly the routing daemons to get started from the init script. The config file is /etc/sysconfig/quagga

If you have a working firewall, the OSPF daemon will not get working, you have to enable it in the firewall with this rule (maybe other routing daemons also have to be enabled, if you use it, but i could not find anything about that):

iptables -A INPUT -p 89 -m state --state NEW -j ACCEPT

To really activate quotas, you’ll need to add usrquota to the appropriate partitions as listed in /etc/fstab. Here’s an example:

When you want quota support for a given partition, some special files have to be created boot-time. This is not done by default. To do so, you need to

then, reboot to create those files.

To edit user quotas, use edquota. See man edquota.

Post Installation :

Create an empty database and accompanying user named redmine for example.

For Mysql: create database redmine character set utf8; create user redmine@localhost identified by my_password; grant all privileges on redmine.* to redmine@localhost;

For PostegreSQL: create database redmine character set utf8; create user redmine@localhost identified by my_password; grant all privileges on redmine.* to redmine@localhost;

Edit config/database.yml

Generate a session store secret: cd /var/www/html/redmine/ rake config/initializers/session_store.rb

Create the database structure, by running the following command under the application root directory: RAILS_ENV=production rake db:migrate It will create tables and an administrator account.

Insert default configuration data in database, by running the following command: RAILS_ENV=production rake redmine:load_default_data

Fix permissions mkdir tmp public/plugin_assets chown -R redmine:redmine files log tmp public/plugin_assets chmod -R 755 files log tmp public/plugin_assets

Test the installation by running WEBrick web server: ruby script/server webrick -e production see the result : http://localhost:3000/

SMTP Configuration : Copy config/email.yml.example to config/email.yml and edit this file to adjust your SMTP settings.

see http://www.redmine.org/wiki/redmine/RedmineInstall

For use Apache : http://www.redmine.org/wiki/redmine/HowTo_configure_Apache_to_run_Redmine

I have included a simple script called sawfish-session which sources $HOME/.sawfish/startup, if it exists. It is setup so you can easily run your own commands before sawfish is launched. You can find an example file at /usr/share/sawfish/startup. Also, there is a sawfish-aplay script as well, which is a wrapper to aplay with the -q argument so your logs aren’t spammed by a bunch of useless messages if you choose to use sound events. To use sound events in sawfish, run sawfish-ui and goto the Sound tab, and enable sounds. Then, close the program, run it again, and there should a greyed out box at the bottom for entering a command to for playing sounds. I have disabled ESD support in favor of this. Check the box to enable it, and enter either sawfish-aplay or another program of your choice. However, keep in mind this box cannot accept arguments, it can only accept the path to an executable of some sort, which is the whole reason I included an aplay wrapper. Also, be sure to visit http://sawfish.wikia.com if you want to find stuff to supplement sawfish, like scripts, themes, etc. And, finally, you will an example piece of lisp code you can put in your $HOME/.sawfishrc and edit to your heart’s content to get the right root menu for you. This is also where you put lisp code that you want to become active every time you restart sawfish. Use sawfish-client if you want to test it, and remember to put it in your rc file if you wish to retain it. Happy hacking!

(setq root-menu '( ("Editors" ("Abiword" (system "abiword &")) ("Leafpad" (system "leafpad &")) ) ("Terminals" ("Sakura" (system "sakura &")) ("xterm" (system "xterm &")) ) ("Multimedia" ("Audacious" (system "audacious &")) ("VLC" (system "vlc &")) ) ("Network" ("Firefox" (system "firefox &")) ("Pidgin" (system "pidgin &")) ) ("Restart" restart) ("Quit" quit) ))

You need to complete the install, running:

Do not forget to create a scratchbox user:

For further documentation about how to setup scratchbox for your development needs have a look at scratchbox documentation.

Also note that when you reboot and before trying to run scratchbox, you should run:

You can also add it to the default runlevel:

Then to start scratchbox, run:

Once the installation is complete, make sure you load the kernel modules:

# modprobe videodev # modprobe smartcam

Driver for the SpeedTouch USB and SpeedTouch 330

The binaries (modem_run and pppoax) have been installed in /usr/sbin.

You will find the documentation and example script files in: /usr/share/doc/speedtouch-pkgver

You can start configuring your modem by running

In order to use spring properly, you need non-free data files (maps, AI, games mods…).

Download the data files tarball spring_data_pack (270mo)

Then untar it to your home!

Enjoy !

Please start the configure script in the /var/www/squirrelmail directory!

You have to install this plugin with squirrelmail’s own ./configure tool.

You have to install this plugin with squirrelmail’s own ./configure tool.

You need some additional configuration before stunnel will be functional:

Adjust the configuration file:

Genrate your certificate:

Hide the certificate from users:

Now you can enable and start the service:

In order to use the sugarcrm, you have to symlink it to somewhere. For example, if you want to use it under http://localhost/sugarcrm, then use:

After installing this package, please run in a browser http://localhost/sugarcrm/install.php to setup SugarSuite (sugarcrm).

All the configurable defaults in SYSLINUX can be changed by putting a file called syslinux.cfg.

SYSLINUX searches for the SYSLINUX.CFG file in the following order:

/boot/syslinux/syslinux.cfg /syslinux/syslinux.cfg /syslinux.cfg

Here is a simple example syslinux.cfg file, with one entry to boot a Linux kernel:

DEFAULT linux LABEL linux SAY Now booting the kernel from SYSLINUX… KERNEL vmlinuz.img APPEND ro root=/dev/sda1

see http://syslinux.zytor.com/wiki/index.php/SYSLINUX for the complete documentation.

After installing trac you need a few steps to set it up. First of all do not forget to install postgresql/mysql/sqlite according to which database backend you want to use.

To create a new trac project, just use the command:

You can check the result with:

Then, fire up a browser and visit http://localhost:8000

For further documentation on trac, how to set up with different HTTP daemons see TracGuide

Follow this as user:

1) Copy the Tremulous pk3s (data-1.1.0.pk3, vms-1.1.0.pk3, map-atcs-1.1.0.pk3, etc) from their installation directory to /home/<user>/.tremulous/base/"

(Use slocate data-1.1.0.pk3 to find it)

2) Copy z-tremfusion-menu-0.99r3.pk3 to /home/<user>/.tremulous/tremfusion/

(Create the directory if it doesn’t exist)

3) Copy gamex86.so to /home/<user>/.tremulous/base/

/lib/udev/devices is the directory where packages or you can place real device nodes, which get copied over to /dev at every boot.

If you want to enable spell check support, you need to:

where xx is code of the requested language.

Some languages need correctly set encoding. If you get a message like:

then you need to set your encoding as well:

The incorrect words are coloured red by default. You can reach a list of suggested words by pressing z= when the cursor is at the given word.

If you want to disable the spell check support, type:

It may be handy to have map function keys in ~/.vimrc to enable / disable the spell check support:

See the upstream documentation for more info about spell check support:

If you want to be able to use the VirtualBox guest additions, run this command as root to get the Additions ISO (requires an active Internet connection):

Don’t forget to change the wifi interface name in /etc/wifi-radar.conf!

Running x11vnc without a password is not recommended. To create one, type:

Then you can start the VNC server using

if are logged in on :0.

To use this theme, please add -config /etc/X11/xdm/frugalware/xdm-config to your xdm environmental variable in /etc/sysconfig/desktop and restart xdm.