SaruWiki - User contributions [en]

Apache2 and PHP5

2010-10-15T13:25:06Z

82.161.20.132: /* Configuring WebDAV and LDAP for your SSL-enabled Virtual Host */

==Apache2==

===Installation of Apache2===
Installation of Apache2 is quite simple:
apt-get install apache2
This brings a slew of packages, a.o. ''apache2-mpm-worker'', ''apache2-utils'', ''libapr1'' et cetera. When you want a different worker (e.g. , you should use ''aptitude'' to select that different worker (prefork etc.).

===Configuration of Apache2===
Once Apache2 is in place, you might want to [[Enabling SSL for Apache2 | enable SSL]] for it. And if you want to keep track of any visitor to your website(s), you might want to install [[Apache2 and Visitor|Visitor]].

Furthermore, you have to realise that mail sent by your webserver, or any PHP program running under it (e.g. MediaWiki) will have the envelope sender address of www-data@<your.maildomain>. To make sure that your maildomain is actually a real mail domain (necessary for reverse lookup, which is something that real mail servers do), you have to take care to put the right mail domain in ''/etc/mailname'' (e.g. "saruman.biz"). Furthermore, at the top of your Postfix ''main.cf'' you might like to add
myorigin = /etc/mailname
If you now restart Postfix, outgoing mail from user ''www-data'' will have an envelope sender address of ''www-data@saruman.biz''

==Installation of PHP5==
Installing PHP5 is as easy as
sudo apt-get install php5 php5-cli
Note that if you had installed Apache2 module ''apache2-mpm-worker'', it will get replaced with ''apache2-mpm-prefork''. Furthermore, note that ''php5-cli'' is only needed if you want to run PHP commands at the prompt - but our guess is that you want it (e.g. to perform maintenance tasks for your [[Mediawiki_Installation|MediaWiki wikiserver]].

==Adding WebDAV to your Apache2==

===Thoughts about WebDAV and your configuration===
Out of the box, your Debian Apache2 is prepared to start using WebDAV. All you need is to enable two modules: one for WebDAV itself, one for the authentication that you want to use. Since our server mainly uses LDAP, we'll describe WebDAV+LDAP here.

Furthermore, because WebDAV allows editing files on your server, security is paramount (well, it always is, of course. What we mean is that it's even '''more''' important now). The Apache project recommends: 
''The use of HTTP Basic Authentication is not recommended. You should use at least HTTP Digest Authentication, which is provided by the mod_auth_digest module. Nearly all WebDAV clients support this authentication method. An alternative is Basic Authentication over an SSL enabled connection.'' 
Thus you should not using Basic Authentication (which is pretty simple to set up) unless you run it over SSL - so we do that as well. We choose the Virtual Host that defines our SSL-site, and extend it with WebDAV functionality. If this is not what you want, consider stepping your authentication up to Digest Authentication.

===Configuring WebDAV and LDAP for your SSL-enabled Virtual Host===
First, enable the WebDAV and authnz_ldap modules:
a2enmod dav
a2enmod dav_fs
a2enmod authnz_ldap
Do not restart Apache2 just yet, because we haven't configured either the WebDAV site or its authentication!

Furthermore, a location for the DAV lock database must be specified in the global section of your Apache2 configuration file using the [http://httpd.apache.org/docs/2.2/mod/mod_dav_fs.html#davlockdb DavLockDB directive]. To this end, create a file under ''/etc/apache2/conf.d'' named ''webdav'' containing this single line:
DavLockDB /var/run/apache2/DavLock
This will act as the (global) lock database for WebDAV; we don't need to specify it in any other configuration file (like the Virtual Host configuration files). Of course, your server should have a directory ''/var/run/apache2'', and it must be writable for the user ''www-data'' under which Apache2 runs.

Next, adapt the virtual host that may employ WebDAV and LDAP authentication. The virtual host file needs a section that enables WebDAV (using the directive ''Dav On''), and some directives on how to authorize users within this section. Suppose we want to enable WebDAV only for subdirectory ''webdav'' within virtual host ''<nowiki>http://www.saruman.biz/</nowiki>''. Then in the correspondig Virtual Host file (something like ''/etc/apache2/sites-available/000-saruman.biz'') we need to include the following section:
<Location /webdav>
Order Allow,Deny
Allow from all
Dav On
These lines turn on WebDAV for the location ''/webdav''. This of course means that there should ''be'' a directory in your server's filesystem named ''webdav'' and located under the root of this virtual host, e.g. ''/var/www/saruman.biz/webdav''
AuthType Basic
AuthBasicProvider ldap
AuthzLDAPAuthoritative On
This section sets up the authentication as HTTP Basic, with LDAP as the provider, and NOT allowing the authorization phase to fall back to other providers if LDAP cannot provide the required answer. If you want to use "require" statements from some other authorization provider, then you must set ''AuthzLDAPAuthoritative'' to "off".
AuthName "Enter your Saruman.biz login"
AuthLDAPURL "ldap://myserver.saruman.biz/ou=people,dc=saruman,dc=biz?mail" NONE
AuthLDAPBindDN "cn=admin,dc=saruman,dc=biz"
AuthLDAPBindPassword "mypassword"
The ''AuthName'' directive "sets the name of the authorization realm". The string provided for the AuthName is what will appear in the password dialog provided by most browsers. 
The ''AuthLDAPURL'' should point to your server, and the word behind the question mark should be the LDAP field that you want to use as login. We use ''mail'' so that we can log in with our mail address. 
The ''AuthLDAPBindDN'' should be of a user with the right to view the passwords of the users that will be using the WebDAV server, and the ''AuthLDAPBindPassword'' should be that user's password. 
require valid-user
</Location>
This last directive means that any user who has authenticated is granted access. Since only LDAP users can authenticate, this is just fine.
If you want to autenticate against a ldap group "webdav" use the folowing
Order deny,allow
Deny from All
AuthName "Enter your Saruman.biz login"
AuthType Basic
AuthBasicProvider ldap
AuthzLDAPAuthoritative on
AuthLDAPUrl ldap://myserver.saruman.biz/ou=people,dc=saruman,dc=biz?uid
AuthLDAPBindDN "cn=admin,dc=saruman,dc=biz"
AuthLDAPBindPassword "mypassword"
AuthLDAPGroupAttribute memberUid
AuthLDAPGroupAttributeIsDN off
Require ldap-group cn=webdav,ou=groups,dc=saruman,dc=biz
Require ldap-attribute gidNumber=420

Require ldap-attribute gidNumber=420 handles the primary users of group 420, the "webdav" group. Without this condition, primary users would be denied access. For multiple groups, add an additional directive for each.

Next up, you need to create folder ''webdav'' under the root of your Virtual Host. Do not forget to make that folder owned by ''www-data:www-data'' and readable/writable only by that user:
cd /data/wwwroot/yoursite
mkdir webdav
chown www-data:www-data webdav
chmod 660 webdav

Now you can restart Apache2, see if it restarts ok, and then test your new WebDAV folder.

===Testing WebDAV===
To test WebDAV, you can most easily install the ''cadaver'' WebDAV client:
apt-get install cadaver
After that, you can start cadaver, and have it write a file in your WebDAV environment:
localhost:/data/wwwroot/yoursite/webdav# '''cadaver https://www.saruman.biz/webdav'''
WARNING: Untrusted server certificate presented for `*.saruman.biz':
Issued to: Internet Dept., Saruman.biz, Utrecht, NL
Issued by: Saruman.biz, Utrecht, NL
Certificate is valid from Tue, 28 Oct 2008 07:34:41 GMT to Mon, 02 Nov 2009 07:34:41 GMT
Do you wish to accept the certificate? (y/n) y
Authentication required for Enter your Saruman.biz login on server `www.saruman.biz':
Username: sixpacjo
Password:
dav:/webdav/> _
When presented with the cadaver prompt, you can use the following commands:
* ''edit <filename>'': this causes cadaver to open an existing file named ''<filename>''; or, failing that, to create a new file. Your default text editor is used.
* ''lock <filename>'' or ''unlock <filename>'': set or remove a lock on a WebDAV published file. He who owns the lock can edit the file, others can only read it.
* ''discover <filename>'': see the lock status of the file
* ''quit'': well that one's easy...
Use ''man cadaver'' for the full description.

Errors that might occur if you have a problem in your WebDAV setup include:
* Lock problems: if you fail to provide a webserver-writable place for the lock file, you will encounter HTTP 500 errors. In ''cadaver'':
dav:/webdav/> edit test.html
Locking `test.html': failed:
500 Internal Server Error
dav:/webdav/> discover test.html
Discovering locks on `test.html': no locks found.
dav:/webdav/>

Nfs

2010-05-30T16:50:24Z

82.161.20.132: Created page with 'There are two implimentations of NFS one runs in kernel space (nfs-kernel-server) the other in user space (nfs-user-server). The kernel space implimentation is faster and more st…'

There are two implimentations of NFS one runs in kernel space (nfs-kernel-server) the other in user space (nfs-user-server). The kernel space implimentation is faster and more stable but if something goes wrong it could bring your box down. In reality the kernel space NFS implimentation very rarely fails

Make sure you have the kernel modules selected in you're kernel
file systems -> Network File Systems -> NFS server support

On the server:
apt-get install nfs-kernel-server nfs-common portmap

On the client:
#pt-get install nfs-common portmap

== Export Directories ==

#vi /etc/exports

/data 192.168.0.0/24(rw,sync)
/home 192.168.0.0/24(rw,sync)

== Mount ==

To mount the directories on the client nd make it persistent edit /etc/fstab
# vi /etc/fstab

192.168.0.1:/data /data nfs rw,sync,hard,intr 0 0
192.168.0.1:/home /home nfs rw,sync,hard,intr 0 0

Mythtv

2010-03-28T18:13:24Z

82.161.20.132: /* Metadata */

== lirc ==
LIRC CVS is hosted at SourceForge. You can get a copy of the current CVS tree using anonymous CVS login. First log in to the cvs server (press <enter> for password):
cvs -d:pserver:anonymous@lirc.cvs.sourceforge.net:/cvsroot/lirc login
Get the sources:
cvs -z8 -d:pserver:anonymous@lirc.cvs.sourceforge.net:/cvsroot/lirc co lirc
After initial checkout, you can change into this directory and execute cvs commands without the -d option. For example:
cvs update
Compile:
cd lirc
./autogen.sh
./setup.sh
make

/etc/lirc/hardware.conf

# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS=""

#Don't start lircmd even if there seems to be a good config file
START_LIRCMD=false

#Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
#DRIVER="pinsys"
# If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be
# automatically used instead
DEVICE="/dev/lirc0"
MODULES="lirc_mceusb"
TRANSMITTER_DEVICE="/dev/lirc0"

# Default configuration files for your hardware if any
LIRCD_CONF=""
LIRCMD_CONF=""

/etc/lirc/lircd.conf

################################################################################
# lircd.conf file for the new Microsoft Media Center remote using a new
# Microsoft Media Center receiver.
################################################################################
begin remote

name mceusb
bits 16
flags RC6|CONST_LENGTH
eps 30
aeps 100

header 2667 889
one 444 444
zero 444 444
pre_data_bits 21
pre_data 0x37FF0
gap 105000
toggle_bit 22
rc6_mask 0x100000000

begin codes

# starts at A1
BLUE 0x00007BA1
YELLOW 0x00007BA2
GREEN 0x00007BA3
RED 0x00007BA4
TELETEXT 0x00007BA5
RADIO 0x00007BAF
PRINT 0x00007BB1
VIDEO 0x00007BB5 # VIDEOS button
IMAGE 0x00007BB6 # PICTURES button
PVR 0x00007BB7 # RECORDED TV button
AUDIO 0x00007BB8 # MUSIC button
TV 0x00007BB9
# no BA - D8
Guide 0x00007BD9
TV 0x00007BDA # LIVE TV button
Dvd 0x00007BDB
Back 0x00007BDC
OK 0x00007BDD
Right 0x00007BDE
Left 0x00007BDF
Down 0x00007BE0
Up 0x00007BE1
STAR 0x00007BE2
Hash 0x00007BE3
PREVIOUS 0x00007BE4 # REPLAY button
Next 0x00007BE5 # SKIP button
Stop 0x00007BE6
Pause 0x00007BE7
Record 0x00007BE8
Play 0x00007BE9
Rewind 0x00007BEA
Forward 0x00007BEB
CHANNELDOWN 0x00007BEC
CHANNELUP 0x00007BED
Volumedown 0x00007BEE
Volumeup 0x00007BEF
INFO 0x00007BF0 # MORE (i) button
Mute 0x00007BF1
MENU 0x00007BF2 # START (Windows) button
POWER 0x00007BF3
ENTER 0x00007BF4
CLEAR 0x00007BF5
9 0x00007BF6
8 0x00007BF7
7 0x00007BF8
6 0x00007BF9
5 0x00007BFA
4 0x00007BFB
3 0x00007BFC
2 0x00007BFD
1 0x00007BFE
0 0x00007BFF
end codes

end remote

~/.lircrc
begin
prog = mythtv
button = Two
config = 2
end

begin
prog = mythtv
button = Three
config = 3
end

begin
prog = mythtv
button = Four
config = 4
end

begin
prog = mythtv
button = Five
config = 5
end

begin
prog = mythtv
button = Six
config = 6
end

begin
prog = mythtv
button = Seven
config = 7
end

begin
prog = mythtv
button = Eight
config = 8
end

begin
prog = mythtv
button = Nine
config = 9
end

== IRblaster ==

To get the right codes from youre remote you can record it with irrecord. This will provide a configuration file which you can use in lirc
#irrecord /tmp/remote.conf
Now follow the instructions
To get the raw codes
#irrecord -f /tmp/remoteraw.conf

You wil get this file for a topfield tf6000cok remote
# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.8.6(default) on Wed Mar 24 20:58:54 2010
#
# contributed by
#
# brand:Topfield
# model no. of remote control: TP-014
# devices being controlled by this remote: Topfield TF6000COK
#

begin remote

name topfield
flags RAW_CODES|CONST_LENGTH
eps 30
aeps 100

gap 107620

begin raw_codes

name KEY_1
9000 4450 600 500 650 450
650 1650 600 500 600 500
650 500 600 500 600 500
650 1600 650 1600 600 1650
600 1650 600 1650 600 1650
600 1600 650 1600 600 1650
600 550 600 500 600 500
600 1650 600 550 550 550
600 500 650 500 600 1650
600 1650 600 1600 600 550
600 1650 550 1650 650 1650
550

name KEY_2
9050 4400 600 500 650 500
600 1650 600 500 600 500
650 500 600 500 600 500
650 1650 600 1600 600 1650
600 1650 600 1650 600 1650
600 1650 600 1600 600 550
600 1650 600 500 600 500
650 1600 600 550 600 500
600 550 600 1600 600 550
600 1650 550 1650 650 500
600 1650 600 1650 600 1600
600

name KEY_3
9000 4450 600 500 650 500
600 1600 650 500 600 500
600 550 600 500 600 550
600 1600 600 1650 650 1600
600 1650 600 1650 600 1650
600 1600 600 1650 600 1650
600 1650 600 500 600 550
600 1650 600 500 600 500
600 550 600 500 600 550
600 1600 650 1650 550 550
600 1650 600 1600 600 1650
600

name KEY_4
9050 4450 600 500 600 500
650 1600 600 500 650 500
600 500 650 500 600 500
600 1650 600 1650 600 1650
600 1600 650 1600 650 1600
600 1650 600 1650 600 500
600 550 600 1650 550 550
600 1650 600 500 600 500
650 500 600 1650 600 1650
600 500 600 1650 600 500
650 1600 600 1650 600 1650
600

name KEY_5
9050 4400 650 450 650 500
600 1650 600 500 650 500
600 500 600 500 650 500
600 1650 600 1600 650 1650
600 1600 600 1650 600 1650
600 1650 600 1650 600 1650
600 500 600 1650 600 500
600 1650 600 500 650 500
600 500 600 550 600 1650
600 500 600 1650 600 500
600 1650 600 1650 600 1650
600

name KEY_6
9050 4400 650 500 600 500
600 1650 600 500 650 500
600 500 600 500 650 500
600 1650 600 1650 600 1600
600 1650 600 1650 600 1650
600 1650 600 1650 600 500
600 1650 600 1650 600 500
600 1650 600 550 550 550
600 500 600 1650 600 500
600 550 600 1650 600 500
600 1650 600 1650 600 1650
600

name KEY_7
9000 4450 600 500 600 500
650 1600 650 450 650 500
600 500 650 500 600 500
600 1650 600 1650 600 1650
600 1650 600 1600 650 1600
600 1650 600 1650 600 1650
600 1650 550 1650 650 500
600 1650 600 500 600 550
600 500 600 500 600 550
600 500 600 1650 600 500
650 1600 600 1650 600 1650
600

name KEY_8
9050 4400 650 450 650 500
600 1650 600 500 650 500
600 500 600 500 650 500
600 1650 600 1600 650 1650
550 1650 600 1650 600 1650
600 1650 600 1600 650 500
600 550 550 550 600 1650
600 1650 550 550 600 500
650 500 600 1600 650 1650
550 1650 600 550 600 500
600 1650 600 1650 600 1650
600

name KEY_9
9050 4400 650 500 600 500
600 1650 600 500 650 500
600 500 600 500 650 500
600 1650 600 1650 600 1600
600 1650 650 1600 600 1650
600 1650 600 1650 600 1600
600 550 600 500 600 1650
600 1650 600 550 550 550
600 500 600 550 600 1600
600 1650 600 550 600 500
600 1650 600 1650 600 1650
600

name KEY_0
9000 4450 600 500 650 450
650 1600 650 500 600 500
600 500 650 500 600 550
600 1600 600 1650 600 1650
600 1650 600 1650 600 1650
600 1600 600 1650 600 550
600 500 600 500 650 500
600 1650 600 500 600 550
600 500 600 1650 600 1650
600 1600 650 1650 550 550
600 1650 600 1600 600 1650
600

name KEY_CHANNELUP
9050 4400 650 500 600 500
650 1600 650 500 600 500
600 500 650 500 600 500
650 1600 600 1650 600 1650
600 1650 600 1600 600 1650
650 1600 600 1650 600 1650
600 500 600 1650 600 500
600 1650 650 500 600 1600
650 500 600 550 550 1650
600 550 600 1650 550 550
600 1650 600 500 600 1650
600

name KEY_CHANNELDOWN
9050 4400 650 500 600 500
650 1600 600 500 650 500
600 550 600 500 600 500
600 1650 600 1650 600 1650
600 1600 650 1650 600 1600
600 1650 600 1650 600 500
650 1600 600 1650 600 550
600 1600 600 550 600 1650
550 550 600 1650 600 500
600 550 600 1650 550 550
600 1650 600 500 600 1650
600

name KEY_VOLUMEUP
9050 4400 650 500 600 500
600 1650 600 500 650 500
600 500 600 500 650 500
600 1650 600 1650 600 1600
600 1650 650 1600 600 1650
600 1650 600 1650 600 1600
600 1650 650 1600 600 500
650 1650 550 550 600 1650
600 500 600 500 600 550
600 500 650 1600 600 500
650 1650 550 550 600 1650
600

name KEY_VOLUMEDOWN
9050 4400 650 500 600 550
600 1600 650 500 600 500
600 500 650 500 600 500
650 1600 600 1650 600 1650
600 1650 600 1650 600 1600
650 1600 600 1650 600 550
600 500 600 500 600 1650
600 1650 600 500 650 1600
600 550 600 1650 600 1600
600 1650 600 550 550 550
600 1650 600 500 600 1650
600

end raw_codes

end remote

Now save this file in /etc/lirc and edit /etc/lirc/lircd.conf
include "/etc/lirc/remote.conf"

Now we can test irblaster
#irsend SEND_ONCE remote KEY_1
The channel on the topfield DVB must jump to channel 1

== EPG ==

To use the epg we want to grad the data from a source. In this case we use tv_grab_nl_py. This script will grab all data from www.tvgids.nl

XMLTV-configuratiebestand aanmaken

* Start MythTV Setup
* Choose for Video Sources.
* Choose for existing or a new video source
* Listings grabber: The Netherlands (tv_grab_nl_py...)
* Klick Finish

On the prompt
# tv_grab_nl_py --configure
This will create a config file in /homedir/.xmltv/tv_grab_nl_py.conf
Edit this config file and clear out all channels you don want (or edit them out)
To see is something is happening
#mythfilldatabase -v all --refresh-today
To see what's in the database
*mysql -u mythtv -p mythconverg -e "select chanid, callsign, name, xmltvid from channel;"

== Metadata ==

Make sure you have set the filepaths right. Go to Mythtv setup - 6. Storage Directories
Choose (create Fanart group) and choose the right directory

Now go to the mythfrontend and choose to watch a video. Select the video and press W. Based on the filename [http://www.mythtv.org/wiki/MythVideo_File_Parsing] the right data will be searched.

To configure the metadata yourself you can select the video and press I. Now configure the metadata.

Ubuntu

2010-02-07T23:35:01Z

82.161.20.132: /* Make DVD */

== NDISwrapper ==

NDISwrapper is a free software driver wrapper that enables the use of Microsoft Windows drivers for wireless network devices.

Download the windows driver wich contains the .inf file 
Install with ndiswrapper -i drivername.inf 
check the device id with lsusb or lspci -n 
Now execute with ndiswrapper -a deviceid driver
ndiswrapper -a 0bda:8197 net8187b
check the installed drivers
ndiswrapper -l
Write the configuration for modprobe
ndiswrapper -m
And use the module
modprobe ndiswrapper

== Compiz ==

To enable compiz install the Nvidia drivers and install CompizConfig Settings Manager
sudo apt-get install simple-ccsm
Now navigate to system > preferences > Appereance And go to the Visual effects tab. Choose custum there

On Kubuntu change the default windows manager

System Settings -> Default Applications -> Windows manager

{| class="wikitable" style="text-align:center" border="1" cellspacing="0" cellpadding="5"
!style="background:#ffdead;"|Desktop Effects
!style="background:#ffdead;"|Keyboard Shortcuts
|-
|Rotate Cube Manually
|Ctrl + Alt + Left Mouse Button
|-
|Expo
|Super + E (toggle)
|-
|Rotate Cube
|Mousewheel on Desktop
|-
|Film Effect
|Ctrl + Alt + Down Arrow
|-
|Scale Windows
|Alt + Shift + Up Arrow
|-
|Ring Switcher
|Super + Tab - overrides Shift Switcher
|}
Super key is the windows key :-)

== Mount Network Share ==

First install smbfs
apt-get install smbfs
Then create a folder inside of the /media directory to mount the share on or choose you're own directory
sudo mkdir /media/Storage
Create a credentials file in /root so that you can save your password and have it protected by the root account:
sudo gedit /root/.cifscredentials
Add this to the file
username=Guest
password=

sudo vi /etc/fstab
Add the following line
//192.168.0.10/SHARENAME /media/Storage cifs auto,iocharset=utf8,uid=USER,gid=users,credentials=/root/.cifscredentials,file_mode=0775,dir_mode=0775 0 0

To check if the file works
sudo mount -a
And you should see you're drives on the desktop

Ik you get error when you shut down the pc ''CIFS VFS: server not responding'' then you have to unmount first. Do this with the following

ln -s /etc/init.d/umountnfs.sh /etc/rc0.d/K15umountnfs.sh
ln -s /etc/init.d/umountnfs.sh /etc/rc6.d/K15umountnfs.sh

== Citrix Ica client ==

Download the Linux citrix ica client from Citrix
http://citrix.com/English/SS/downloads/details.asp?downloadID=3323&productID=-1

Install the 32bits libraries if youŕe working on a 64bits platform

apt-get install ia32-libs

Install the Open-motif libraries

apt-get install libmotif3

citrix 11 requires openmotif 2.3.1 Download the rpm package for openmotif 2.3.1, I used:

ftp://ftp.ics.com/openmotif/2.3/2.3.1/openmotif-2.3.1-1.RHEL3.0.i386.rpm

To convert a rpm package to a debian package. Use alien to convert the rpm to a deb package

alien -d openmotif-2.3.1-1.RHEL3.0.i386.rpm

Then install the package in the usual way. Note, before installing the alien'ed package it is best to uninstall the previous version of motif, as this will not update the existing motif package.

dpkg -i openmotif_2.3.1-2_i386.deb

Unpack the package and execute the installation script
./setupwfc
Find the plugin directory of firefox. Probably is /usr/lib/firefox/plugins/ otherwise use
find / -name plugins | grep -i "netscape\|firefox\|mozilla"
Create a symlink to the citrix ica library
ln –s /usr/lib/ICAClient/npica.so npica.so

If you open a connection to your citrix server. The browser will ask you if you want to open or save the session. Browse to the ica client
/usr/lib/ICAClient/wfica
and tell it to use it for all applications.

When you get a ssl error "you have not chosen to thrust....." Then copy the certificate in this location.
/usr/lib/ICAClient/keystore/cacerts/

For 64Bits OS

Install Needed 32-bit Open Motif libraries to /usr/lib32

Setup a temporary environment

mkdir -p ~/tmp/Citrix
cd ~/tmp/Citrix

Download a recent i386 libmotif3 .deb package to the above folder

wget http://mirrors.kernel.org/ubuntu/pool/multiverse/o/openmotif/libmotif3_2.2.3-1.4_i386.deb

Use dpkg to extract the package

dpkg -x libmotif3*i386.deb libmotif

Copy the libraries to /usr/lib32

sudo cp libmotif/usr/lib/*.so.* /usr/lib32/
sudo cp -r libmotif/usr/lib/X11/bindings /usr/lib32/X11/

== Make DVD ==

To make a video DVD you can burn you're image on the dvd. If you just have the VIDEO_TS files then the easiest way is to convert these into a iso.

mkisofs -dvd-video -o ~/moviename.iso /path/to/the/VIDEO_TS

/path/to/the/VIDEO_TS path is for example /moviename not /moviename/VIDEO_TS

== FFMPEG ==

Is a video converter tool

#>/usr/bin/ffmpeg -i "00059.MTS" -vcodec flv -f flv -r 25 -s 356x200 -aspect 16:9 -b 2000k -g 160 -cmp 2 -subcmp 2 -mbd 2 -flags +aic+cbp+mv0+mv4 -trellis 2 -acodec libmp3lame -ac 2 -ar 44100 -ab 256k "stacaravan1.flv"

Mythtv

2010-01-06T22:07:32Z

82.161.20.132: /* lirc */

Mythtv

2010-01-06T20:12:07Z

82.161.20.132: /* lirc */

Horde3

2009-08-29T20:23:02Z

82.161.20.132: /* Database */

apt-get install horde3

Now make the site available
In etc/apache2-sites-available there is already a file horde3
Alias /horde3 /usr/share/horde3
<Directory /usr/share/horde3>
Options FollowSymLinks
AllowOverride Limit
deny from all
allow from all 192.168 127.0.0
</Directory>
<Location /horde3>
SSLCipherSuite HIGH:MEDIUM
</Location>

And make the site enabled
ln -s /etc/apache2/sites-available/horde3 00X-horde3

== Database ==

To make the database there are several scripts in /usr/share/doc/horde3/examples/scripts/. We use MYsql:
gunzip /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql.gz

and change the password in the script for the user horde
Run the script
mysql -u root -p
source /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql

== Configure ==

To use the web configuration wizard we need to change the following
chgrp -R www-data /etc/horde/horde3/
chmod -R 750 /etc/horde/horde3
chmod 777 /etc/horde/horde3/conf.php
cp /etc/horde/horde3/conf.php /etc/horde/horde3/conf.php.bak
chmod 777 /etc/horde/horde3/conf.php.bak

Prepare log file:
touch /var/log/horde/horde3.log
chown root.www-data /var/log/horde/horde3.log
chmod 770 /var/log/horde/horde3.log

Now we can browse to the site
http://192.168.70.9/horde3/

This will give us the following
Horde3 configuration disabled by default because the administration/install wizard gives the whole world too much access to the system. Read /usr/share /doc/horde3/README.Debian.gz on how to allow access.

Change /var/log/horde/horde3/conf.php and comment line 2 and 3 leave the first line as is.

Klik op setup en klik 'horde setup'
- edit database -> username en WW - connect to database = tcp/ip - localhost - naam database
- edit preference system -> SQL database
- edit authentication -> Administrator,user@sample.com - SQL authentication

klik generate Horde Configurtion
Could not save the backup configuration file /usr/share/horde3/config/conf.bak.php
Not solved yet

- edit users -> root

Installing SaMBa with OpenLDAP support

2009-08-23T16:55:15Z

82.161.20.132: /* OpenLDAP adaptation */

== The Samba Section==

== Preparations ==
First off, get yourself [http://oreilly.com/catalog/9780596007690/index.html this wonderful book] - and READ IT. Next, make sure our user backend of choice, OpenLDAP, is properly installed and can be used to authenticate users. If you haven't yet installed OpenLDAP, go to [[OpenLDAP | the relevant section]] of this wiki, and get going. Make sure your OpenLDAP is running well.

=== Software installation ===
This is easy: using ''aptitude'', install the following packages:
* ''samba'', the actual server.
* ''samba-tools'', a set of utilities.
* ''samba-doc'' - note that we NEED ''samba-doc'', as this package contains a configuration file that we need (the LDAP schema file).
* ''smbclient'', that can make your Linux server work with a Windows or SaMBa server; we need this to test our own server.

As usual, Debian is asking us for the configuration details. For SaMBa 3.2, there are only two simple questions:
* What do you want to be your Windows workgroup name? (we provide the name "AMBER")
* Do you want to modify ''smb.conf'' to use WINS setting from DHCP? (we provide "no")
Now we have our SaMBa configuration file as ''/etc/samba/smb.conf'', but we're going to follow two time-honoured tradions: we're going to save the original configuration file for future reference, and we're going to rename our configuration file to ''smb.conf.master'', while providing SaMBa with a comment-stripped version of it:
cd /etc/samba
cp smb.conf smb.conf.sample
mv smb.conf smb.conf.master
testparm smb.conf.master
testparm -s smb.conf.master > smb.conf
Now remember: when we want to change our SaMBa configuration, we edit ''smb.conf.master''. Once we're ready with that, we ALWAYS need to run those last two lines; the first of those will check our updated configuration, to see if we haven't made some silly typo that renders the configuration wholly or partially crippled, and the second one creates a comment-stripped version of it that SaMBa will actually be using.

=== WINS configuration ===
To enable WINS, we add the following lines to ''smb.conf.master'':
## Browsing/Identification ###
workgroup = AMBER
netbios name = DWORKIN

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
wins support = yes
os level = 33
domain master = yes
local master = yes
preferred master = yes
name resolve order = wins lmhosts hosts bcast
dns proxy = yes
Now this does a whole lot of things with the SaMBa ''nmbd'' daemon - at least when you remember to save the master config file, test it with ''testparm'' and write the actual ''smb.conf'' as desribed previously, AND then restart your ''nmbd'' daemon:
/etc/init.d/samba restart
OK so what do the configuration lines mean?
* ''workgroup = AMBER'' - this line makes the SaMBa server a member of workgroup AMBER.
* ''netbios name = DWORKIN'' - here we define the server NetBIOS name to be "dworkin".
* ''wins support = yes'' - this line actually turns on the WINS support, so it instructs the ''nmbd'' daemon to start acting as a WINS server.
* ''os level = 33'' - this gives our WINS server a "rank" of 33, meaning that it will be sure to become the WINS master browser, even if there are Windows servers on the network tat act as domain controllers.
* ''domain master = yes'' - this will tell our server that it will not be just any master browser, but a '''domain''' master browser, so that our server will be the master browser on each and every subnet that it is connected to.
* ''local master = yes'' - this setting is vital to being a domain master browser, as it ensures that our WINS server is also the local master browser.
* ''preferred master = yes'' - adding this line makes the ''nmbd'' daemon initiate a browser election as soon as it starts up, so that it essentially gets the master browser role as fast as possible.
* ''name resolve order = wins lmhosts hosts bcast'' - this ensures that for a WINS request, the ''nmbd'' daemon not only checks its WINS database, but also the local ''lmhosts'' file (if it exists), the Linux ''/etc/hosts'' file, and finally, to revert to a broadcast to see if it can locate the requested name by shouting out for it.
* ''dns proxy = yes'' - this makes ''nmbd'' to check a requested name with the DNS server, if it cannot be found in the WINS database itself.
After restarting, we can see if our Linux server is now a WINS master browser by inspecting the SaMBa log file, by default ''/var/log/samba/nmbd.log''. It should show something like
[2008/11/21 16:18:03, 0] nmbd/nmbd.c:main(849)
nmbd version 3.2.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2008/11/21 16:18:03, 0] nmbd/asyncdns.c:start_async_dns(155)
started asyncdns process 25707
[2008/11/21 16:18:03, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(336)
become_domain_master_browser_wins:
Attempting to become domain master browser on workgroup AMBER, subnet UNICAST_SUBNET.
[2008/11/21 16:18:03, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(350)
become_domain_master_browser_wins: querying WINS server from IP 192.168.67.10 for domain master browser name AMBER<1b> on workgroup AMBER
[2008/11/21 16:18:03, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(110)
*****

Samba server DWORKIN is now a domain master browser for workgroup AMBER on subnet UNICAST_SUBNET

*****
[2008/11/21 16:18:03, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(291)
become_domain_master_browser_bcast:
Attempting to become domain master browser on workgroup AMBER on subnet 192.168.67.10
[2008/11/21 16:18:03, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(304)
become_domain_master_browser_bcast: querying subnet 192.168.67.9 for domain master browser on workgroup AMBER
[2008/11/21 16:18:11, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(110)
*****

Samba server DWORKIN is now a domain master browser for workgroup AMBER on subnet 192.168.67.10

*****
[2008/11/21 16:18:26, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(395)
*****

Samba name server DWORKIN is now a local master browser for workgroup AMBER on subnet 192.168.67.10

*****

Furthermore, we can test on the server itself if a WINS lookup succeeds:
dworkin:# nmblookup -M amber
querying amber on 127.255.255.255
192.168.67.10 amber<1d>

Finally, we tell our DHCP server to provide clients with the IP address of our WINS server. We do this by adding the following line to ''/etc/dhcp3-server/dhcpd.conf'':
option netbios-name-servers 192.168.67.10;
This line can either be added to the global section, or within the ''subnet'' declaration for each individual subnet that you want to inform of this WINS server.

=== OpenLDAP adaptation ===
In order for our OpenLDAP server to recognise the SaMBa-specific attributes that we're going to use, we need to add the "samba" schema to the OpenLDAP server. After installation of ''samba-doc'', we can find this schema in ''/usr/share/doc/samba-doc/examples/LDAP'', where it sits gzipped between some other schema files; as the README explains, what we need is ''samba.schema.gz'', so we unzip it and copy it to our OpenLDAP schema directory
cd /usr/share/doc/samba-doc/examples/LDAP
gunzip samba.schema.gz
cp samba.schema /etc/ldap/schema
Next up, we include this schema into our LDAP configuration, by adding the following line to ''/etc/ldap/slapd.conf'' under # Schema and objectClass definitions:
include /etc/ldap/schema/samba.schema
Not only do we need schema updates, we could also do with some more indices. Thus, we change the relevant section of ''/etc/ldap/slapd.conf'' to read:
# Indexing options for database #1
index objectClass,uidNumber,gidNumber eq
index cn,sn,uid,displayName pres,sub,eq
index memberUid,mail,givenname eq,subinitial
index sambaSID,sambaPrimaryGroupSID,sambaDomainName eq
Ofcourse, it's not just enough to add these parameters, we also need to generate the indices, and restart our LDAP server:
sudo invoke-rc.d slapd stop
sudo -u openldap slapindex
sudo invoke-rc.d slapd start
Check to see if the Samba objects are now usable in your LDAP server, e.g. by opening your LDAP Account Manager, and go to tools > schema browser; you should have objects like "sambaConfig" and "sambaDomain".

=== Feed OpenLDAP with Samba information===
Now we can add the Samba3 account information to our LDAP server. There are two ways of doing that: create an LDAP ldif file with the necessary information, or use the graphic LDAP manager to add it. For small amounts of users, the last way is quickest. What you need is to take two steps:

'''Add the SaMBa domain to the LDAP tree''' 
For this step, as root you perform the following command
net getlocalsid
This will a string like "SID for domain DWORKIN is: S-1-5-21-2406862431-3150385097-213705319". With this SID, we can create the LDAP object that represents the SaMBa domain. To that end we log into our LDAP account manager, go to "Samba domains", and create our domain. There are only three pieces of information that are mandatory:
* the domain name, in our example "amber"
* the forementioned SID, in our example "S-1-5-21-2406862431-3150385097-213705319".
* the RID base; this has a default of 1000, which you should not change unless you know exactly what you're doing.
However, there are other options that you might find it worth setting, like the minimal password length, password history length, if users should be disconnected "outside logon hours" etcetera. We would advise you to not set too many options until you've finished testing all basic functionality of your SaMBa server.

In case you're curious, the LDAP ldif file for such an account could look like this:
dn: sambaDomainName=amber,ou=domains,dc=saruman,dc=biz
objectClass: sambaDomain
sambaDomainName: amber
sambaSID: S-1-5-21-2476862421-3150885297-210706319
sambaAlgorithmicRidBase: 1000
sambaMinPwdLength: 7
sambaPwdHistoryLength: 5
sambaLogonToChgPwd: 0
sambaForceLogoff: -1
sambaRefuseMachinePwdChange: 1

dn: sambaDomainName=DWORKIN,dc=saruman,dc=biz
objectClass: sambaDomain
sambaDomainName: DWORKIN
sambaSID: S-1-5-21-2476862421-3150885297-210706319
sambaAlgorithmicRidBase: 1000
sambaNextUserRid: 1000
sambaMinPwdLength: 5
sambaPwdHistoryLength: 0
sambaLogonToChgPwd: 0
sambaMaxPwdAge: -1
sambaMinPwdAge: 0
sambaLockoutDuration: 30
sambaLockoutObservationWindow: 30
sambaLockoutThreshold: 0
sambaForceLogoff: -1
sambaRefuseMachinePwdChange: 0

'''Add the SaMBa account information to LDAP user accounts''' 
Again we use our LDAP account manager, and we now go to a user that we want to provide access to SaMBa. When you choose to edit the user, there should be a tab "Samba 3". In this tab, you can click the button "Add Samba 3 account"; until you've done that, this user has no access at all to the Samba server. 
When adding (or changing) a users Samba account information, there is actually only one mandatory field:
* "Domain": from this pulldown list you can choose the SaMBa/Windows domain that the user will belong to. When you have only your one SaMBa domain entered in your LDAP, this field will show the name of that domain.
Furthermore, there are a few more fields that you might want to fill. They are:
* "Display name": the name that Windows shows for a user
* "Samba password": this may be a different password from a Unix account that the user may have
* Windows group: this is the primary group that the user belongs to, from a SaMBa perspective instead of a Unix perspective.
Having added the necessary information, the user should be able from a Windows machine to browse the SaMBa server, and see all non-hidden shares that are available to him. Furthermore, from a Linux prompt, you could use ''smbclient'' to verify that SaMBa honours the users name and password:
smbclient //192.168.67.10/Data -U jan
If the Data share has been made (for that: see further down), and if user "jan" has a Samba account in LDAP, and if you type the correct password, then you're greeted with an SMB client prompt:
smb: \>
Here you can type commands like "dir", "del" and "mkdir"; type "help" to see all available commands.

== Samba configuration for LDAP authentication==
To get SaMBA to use OpenLDAP as a backend is actually quite straightforward. The main work is done in ''smb.conf.master'', where we add the following section:
passdb backend = ldapsam:ldap://127.0.0.1
ldap suffix = dc=saruman,dc=biz
ldap machine suffix = ou=hosts
ldap user suffix = ou=people
ldap group suffix = ou=groups
ldap admin dn = cn=admin,dc=saruman,dc=biz
ldap delete dn = no
# allow user privileges
enable privileges = yes
One note: if you use ''testparm -s'' to test and convert ''smb.conf.master'', then it's possible that your ''ldap suffix'' statement gets lower than one or more than the other ''ldap'' statements; you should rectify that before starting SaMBa, because otherwise SaMBa gets mighty confused, and cannot find the right LDAP OU's.

Now the above declares the LDAP account ''admin,saruman,biz'' to be the LDAP admin account - but SaMBa hasn't got the admin password yet, so it can't do much. To this end, we let SaMBa store the password for this admin account in its own little secret file ''/etc/samba/secrets.tdb''. We do this by running
smbpasswd -W
Setting stored password for "cn=admin,dc=saruman,dc=biz" in secrets.tdb
New SMB password:
Retype new SMB password:
If we used a lowercase ''-w'', then we could have specified the password on the command line (''smbpasswd -w SuperSecret'').

= Samba share configuration =
With the above configuration, we should now be able to create a share, and make it available to our LDAP accounts. To this end, we create a directory that we're going to share, and give it a workable set of permissions. Suppose we have an LDAP user "jan" and an LDAP group "networkusers". We could then, as root, do this:
cd /data/samba
mkdir Data
chown jan:networkusers Data
chmod g+rwxs,o-rwx Data
This ensures that user "jan", as well as every user that's a member of "networkusers", is allowed to read and write in this share. However, thanks to the "sticky bit" set for the group with the ''chmod'' command, files that are written to this directory are automatically owned by the group "networkusers", who have read & write rights.

Next step would be to share this directory, by adding the following section to ''smb.conf.master'':
[Data]
comment = Data directory for us all
browseable = yes
path = /data/samba/Data
guest ok = no
read only = no
create mask = 0770
create directory mask = 0770
This makes the directory usable via the share "Data". Notice that we do not allow unauthenticated users ("guest ok = no"), that we allow writing in this share ("read only = no", although we could also have used "writeable = yes", which is the same), and that we mask every create operation (for both files and directories) so that they can set any right under "user" and "group", but cannot set any rights under "other". This prevents anyone other than the "networkusers" to read (let alone write) the files in this share.

Asterisk basic configuration

2009-07-13T17:07:40Z

82.161.20.132: /* DAHDI */ Problem solving

= Asterisk basic configuration principles =
In this section we'll have a look at the basic configuration of an Asterisk PBX. Contrary to the TFOT-book, we'll be looking at it from the theory side, and from there go to an example configuration. For this example configuration, we'll start from a server with on the "outside" a POTS line and a SIP account with an Internet provider, and on the "inside" two analogue telephones and a SIP softphone. Our goal is to let the PBX behave as if we don't even have a PBX, but a standard home situation: for an incoming call, all phones ring; and every internal phone can make calls to the outside.

= Asterisk channel configuration basics =
The first thing to realise is that Asterisk sees each connected telephony device as a "channel". But what is a Channel? To Asterisk, a channel is a connection which brings in a call to the Asterisk PBX. A channel could be a connection to an ordinary telephone handset or an ordinary telephone line, or to a logical call (like an Internet phone call). Asterisk makes no distinction between "FXO" and "FXS" style channels (that is, it doesn't distinguish between telephone lines and telephones). Every call is placed or received on a distinct channel.

The second thing to realise, is that every type of device attached to the Asterisk PBX have their own specific configuration files. Correctly setting up each (set of) telephony devices makes them available in our Asterisk PBX as channels. Thus, the device configuration files serve as a kind of abstraction layer, and simplify our final Asterisk configuration by putting "channel-specific" information in separate files.

If you've followed the previous Asterisk sections in this Wiki, or followed the first four chapters of the TFOT-book, then you've encountered the following configuration files:
* ''zaptel.conf'' - in this file, you can set up the most basic parameters for your Zap-type hardware channels, most notably Digium telephony cards. You're configuring the hardware itself, via its driver. You could think of this file as belonging to the hardware, not Asterisk. If you'd have other software on your machine besides Asterisk that could make use of your telephony hardware, then that'd be influenced as well when you change ''zaptel.conf''.
* ''zapata.conf'' (and possibly ''zapata-channels.conf'' if you're on Debian) - this file handles the Asterisk-specific configuration of the hardware telephony channels. It thus "sets up the Zap channels" that Asterisk sees - for incoming and outgoing calls. All parameters that set up the channel are specified here.
* ''vpb.conf'' - this file is used to configure [http://www.voicetronix.com/ Voicetronix] cards with Asterisk. If you've a Voicetronix card in use, then you've also installed the Voicetronix drivers. This makes the card(s) useable under Linux. But to have Asterisk use the card(s), you need this ''vpb.conf'' file. It thus serves the same purpose as ''zapata.conf''.
* ''sip.conf'' - this file contains all information on all SIP devices that we want to connect to our Asterisk server; be it one or more SIP accounts with Internet providers, or SIP capable telephones (hardware or software). When ''sip.conf'' has been set up correctly, we can refer to a SIP device by a friendly name like [1000] or [Jane].
* ''iax.conf'' - this file is just the same as the ''sip.conf'' file, only it handles devices that talk IAX2 protocol instead of the SIP protocol.
These five files define all channels that our basic Asterisk PBX might handle (well, it won't even handle the last one, since we're not connecting any other Asterisk boxes or IAX-(soft)phones to our PBX, and it won't handle the third one if you don't have a Voicetronix card).

As a reference, we're going to list the contents of four example files, and explain what they do in the way of preparing channels for our simple Asterisk server.:
==zaptel.conf==
# Autogenerated by ./genzaptelconf -- do not hand edit
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#

# It must be in the module loading order

# Span 1: WCTDM/0 "Wildcard TDM410P Board 1" (MASTER)
fxoks=1
fxoks=2
fxsks=3
# channel 4, WCTDM, no module.

# Global data

loadzone = nl
defaultzone = nl
This is a relatively simple file, configuring three Digium modules. As you can see, the ''genzaptelconf'' command has generated it for us. It belongs with a Digium TDM410P card, which has two FXS modules in positions 1 and 2, and one FXO module in position 3. The first two non-commented lines define the protocol that the FXS modules must "talk" with the attached devices, which "naturally" is the FXO protocol (yes, FXS talks FXO, and FXO talks FXS... a bit like electric current flowing from negative to positive. It's just a matter of definitions). 
The third line defines that the FXO module talks FXS protocol. 
The fourth line configures a set of indications to use for the defined channels. Since we're loading "nl", we're configuring Dutch dialtones etcetera for the channels. 
Finally, the last line tell the server that any channel that does not have a zone assigned to it, should have the specified default zone configured - Dutch as well in this example. 
With this simple file, the driver for our example card (''wctdm24xxp'', by the way) can set up the hardware just as we want it. Now to tell Asterisk how to use it...
==zapata-channels.conf==
; Autogenerated by ./genzaptelconf -- do not hand edit
; Zaptel Channels Configurations (zapata.conf)
;
; This is not intended to be a complete zapata.conf. Rather, it is intended
; to be #include-d by /etc/zapata.conf that will include the global settings
;

; Span 1: WCTDM/0 "Wildcard TDM410P Board 1" (MASTER)
;;; line="1 WCTDM/0/0"
signalling=fxo_ks
callerid="Channel 1" <6001>
mailbox=6001
group=5
context=from-internal
channel => 1
callerid=
mailbox=
group=
context=default

;;; line="2 WCTDM/0/1"
signalling=fxo_ks
callerid="Channel 2" <6002>
mailbox=6002
group=5
context=from-internal
channel => 2
callerid=
mailbox=
group=
context=default

;;; line="3 WCTDM/0/2"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 3
context=default
This second file is also auto-generated. It sets up three channels, associated with the three Digium hardware modules that we've configured with ''zaptel.conf''. Here, we also see how the channel numbers get assigned to the physical ports. The first module gets to be Zap channel 1 ('''Zap/1'''), the second '''Zap/2''' and so on. So if we would like our FXO module to be channel 1, and our FXS modules 2 and three, we could rotate the three channel numbers in this file. Probably we'd then also want to rotate the ''callerid''`s though... Furthermore, we don't think it's a good idea to assign channels to Zap devices in a different order than the devices are found in the system - meaning "stick with the default numbering as much as possible".

Note that the way ''zapata-channels.conf'' is interpreted, means that any statement like ''signalling=fxs_ks'' actually ''sets'' the ''signalling'' parameter; when the ''channel => 1'' line is reached, then all preceding parameter assignments are applied to that particular channel. This also means that if you somewhere have set a channel to belong to context "foo", and then never set a context again, then every next channel also gets assigned to "foo". So remember: if you don't see a parameter being set with a specific channel, you CANNOT assume that it then has it's default value; if a preceding channel has set that parameter to value "bar", then for your specific channel, it is "bar" also.

An interesting thing to see here is how ''genzaptelconf'' deals with the above concept. After defining each channel, it resets the most important parameters (a.o. the ones that should be unique with a channel) to empty or "default". This means that if you yourself are very meticulous, you could do without that safety net, and rewrite the above configuration file as:
signalling=fxo_ks
callerid="Channel 1" <6001>
mailbox=6001
group=5
context=from-internal
channel => 1

signalling=fxo_ks
callerid="Channel 2" <6002>
mailbox=6002
group=5
context=from-internal
channel => 2

signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 3
Note: we like the thoroughnes of the ''genzaptelconf'' configuration, but we like the readability of the second file more.

==zapata.conf==
[trunkgroups]

[channels]
switchtype=national
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
callgroup=1
pickupgroup=1
immediate=no
#include zapata-channels.conf
Under Debian,

==sip.conf==

This is a sample configuration for VOIP with XS4ALL

;;/etc/asterisk/sip.conf;;
[general]
context=default
externip=setyoureiphere
dtfmmode=inband
localnet=192.168.70.0/24
port=5060
bindaddr=0.0.0.0
disallow=all
allow=alaw
allow=ulaw
registerattempts=0
defaultexpiry=7200
register => 08787XXXXX:PASSWORD@sip.xs4all.nl/08787XXXXX

[xs4all]
type=friend
username=08787XXXXX
fromuser=08787XXXXX
fromdomain=sip.xs4all.nl
secret=PASSWORD
host=sip.xs4all.nl
insecure=invite
context=fromxs4all
canreinvite=no
dtmfmode=inband
disallow=all
allow=alaw
allow=ulaw

== DAHDI ==

From asterisk version 1.4 zaptel is renamed in DAHDI witch stands for Digium Asterisk Hardware Device Interface.
If you installed the dahdi-tools (highly recommended) then you can configure you're hardware

Conversion from zaptel
/etc/zaptel.conf Becomes /etc/dahdi/system.conf
/etc/asterisk/zapata.conf Becomes /etc/asterisk/chan_dahdi.conf

Lets look at what we have
#dahdi_tool
This will give a overview of the hardware and if it is configured or not. It will all so show alarms on the hardware.

Now lets configure the card. First edit /etc/dadi/genconf_parameters. This file is used with dahdi_genconf and will produce /etc/dahdi-system.conf
*lc_country nl
You can also set the echo cancelation here MG2 is default
#dahdi_genconf

#dahdi_cfg -vv

DAHDI Tools Version - 2.2.0
DAHDI Version: 2.2.0.1
Echo Canceller(s): MG2
Configuration
======================
Channel map:

Channel 01: FXO Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01)
Channel 02: FXO Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 02)

2 channels to configure.

Setting echocan for channel 1 to mg2
Setting echocan for channel 2 to mg2

Check if the right module is loaded.
#cat /etc/dahdi/modules

You can configure the options of dahdi in /etc/asterisk/chan_dahdi.conf
for example turn off the echo cancelation

You can also check teh channels in asterisk
#asterisk -r
#server*CLI> dahdi show channels
Or set the verbose level on asterisk to see more output
#server*CLI> core set verbose 10

I had some trouble with the sounds. When asterisk plays hello-world.gsm it sounded stutterd.
I did a
#dahdi_test
This gives a readout from the timinsettings in asterisk. Mine was -133% and it should give a reading close to 100%.I did a
#dahdi destroy channel 1
#dahdi destroy channel 2
#dahdi restart
Now i have 2 channels and no Pseudo channel (not shure were it's for)
Dahdi_test gives me 99,6% and the spound is good

= Asterisk dialplans - contexts =

A dial plan consists of a number of extensions. Each extensions consists of a number of priorities. Extensions are grouped in contexts. For each priority, an application is called.
[context]
exten => id, priority, command

When Asterisk receives an incoming connection on a channel, Asterisk looks at the context defined for that channel for commands telling Asterisk what it should do. The context defines different sets of commands depending on what extension the user has dialed. For example, a context might provide one set of commands for what to do if the user dials "123", and another set of commands for what to do if the user dials "9", and another set of commands for what to do if the user dials any number beginning with "555".

For some kinds of connections — such incoming calls from an outside telephone line — the user has not dialed an extension. In that case, Asterisk behaves as if the user had dialed a special extension named "s" (for Start). Asterisk will look for an extension "number" s in the definition of the context for that channel for instructions about what it should do to handle the call.

Let's say, for example, that you have a channel "Zap/1" which is a connection to a telephone handset in your building. And let's say that in the configuration file for Zap channels (zapata.conf), you have defined context=john for Zap channel 1. So when you use that handset to dial a number, Asterisk looks for a context with the name "john" in extensions.conf to find out what it should do. You begin the definition of a context in extensions.conf by putting the name of the context in square brackets on a line by itself, like this:
[john]

== extensions.conf ==

[globals]

[general]
autofallthrough=yes

[default]
include => fromxs4all

[fromxs4all]
exten => 08787XXXXX,1,Dial(DAHDI/2)
exten => 08787XXXXX,n,Hangup()

[outgoing]
exten => _X.,1,Dial(sip/xs4all/${EXTEN},60,r)

[internal]
exten => 6004,1,Dial(sip/6004)
exten => 6003,1,Dial(sip/6003)
exten => 6005,1,Dial(DAHDI/2)
exten => 6006,1,Answer()
exten => 6006,n,Playback(hello-world)
exten => 6006,n,Hangup()

[phones]
include => internal
include => fromxs4all
include => outgoing

Install Asterisk under Debian

2009-01-10T15:26:53Z

82.161.20.132: /* Installing Asterisk */

=Installing Asterisk=
Once the hardware configuration part is completed, we can start the installation of Asterisk itself. Using ''aptitude'' or ''apt-get'', install package ''asterisk''. On Debian 5.0 "Lenny", it should be Asterisk 1.4.21.2. With ''apt-get'', the command is simply
apt-get install asterisk
Note: many, many dependencies bring a lot of extra packages to your server when you install Asterisk. On a test machine, I counted 24 extra packages (for a total of 11.4MB to be downloaded).

If you have telephony hardware, you've likely already configured it in the preceding sections. However, when Asterisk itself is installed, you can run the ''genzaptelconf'' command again, and it will not only re-configure your ''zaptel.conf'', but also it will generate ''/etc/asterisk/zapata-channels.conf''
genzaptelconf -svdM -c nl
Now, as the command suggests, include the ''zapata-channels.conf'' file in ''/etc/asterisk/zapata.conf'', either by running
echo '#include zapata-channels.conf' >>/etc/asterisk/zapata.conf
or by opening zapata.conf in your favourite [[vim | text editor]] and pasting the line "#include zapata-channels.conf" (including the hash sign) somewhere near the end of the file.

Another measure that you might wish to implement in advance is the addition of two lines for [http://www.voip-info.org/wiki/view/Asterisk+echo+cancellation echo cancellation]:
echocancel=yes
echocancelwhenbridged=no
echotraining=800
When echo cancellation has been turned on, you can also tune two other parameters: the [http://wiki.ljackson.us/Asterisk_Echo rx gain and tx gain].

When you've rerun ''genzaptelconf'', Asterisk will have started at the end of the command. Your adaptation of ''zapata.conf'' is not yet noticed by Asterisk. Please reload or restart asterisk, e.g. by running
/etc/init.d/asterisk restart

=Installing Asterisk-GUI=
Asterisk-GUI is not an essential part of an Asterisk installation, but in some respects it can make life much easier for you. On the other hand, installing it is NOT as easy as with other Debian packages - because it's not available as a Debian package. Thus, we'll have to compile the Asterisk-GUI from source.

First obtain the latest version of the ''asterisk-gui'' package; it can be downloaded from the download section of [http://www.asterisk.org/ the Asterisk site]; most likely at [http://downloads.digium.com/pub/telephony/asterisk-gui/releases/ this place]. Then extract it in some logical place, like ''/usr/src/'':
tar xzvf asterisk-gui-2.0.2.tar.gz /usr/src
This creates the directory ''/usr/src/asterisk-gui-2.0.2'', in which the source for Asterisk-GUI can be found. ''cd'' to this directory, confiure, and compile the software:
cd /usr/src/asterisk-gui-2.0.2
./configure
make
make install
These three commands should complete successfully. They all give pretty clear output when everything runs fine (we haven't seen them fail, so we can't tell what that would look like, or what to do then). 
OK, so we now need to do some configuration on Asterisk-GUI. It's main configuration files are ''/etc/asterisk/http.conf'', where the Asterisk-GUI itself is configured, and ''/etc/asterisk/manager.conf'', which is part of the Asterisk Manager Interface (AMI), over which Asterisk-GUI makes its moves. So first we put the necessary extra info in ''manager.conf''. The Debian setup for AMI has a line that includes all *.conf files in ''/etc/asterisk/manager.d'', so we only need to include manager-specific information in ''manager.conf''. This means only the following line in the section ''[general]'':
webenabled = yes
Now we go to ''/etc/asterisk/manager.d'', and create ''asterisk-gui.conf''. In this, we can put the Asterisk-GUI specific lines - which really only define Asterisk-GUI users, with their passwords and their rights:
[asterisk-admin]
secret = nOguess1ng
read = system,call,log,verbose,command,agent,user,config
write = system,call,log,verbose,command,agent,user,config
Note that this file contains user information (well, it contains Asterisk-GUI user info) with a password, so you might want to secure this file ''/etc/asterisk/manager.d/asterisk-gui.conf'' by changing the owner to asterisk:asterisk, and remove the world-readable attribute
chown asterisk:asterisk /etc/asterisk/manager.d/asterisk-gui.conf
chmod o= /etc/asterisk/manager.d/asterisk-gui.conf

Furthermore, we need to edit the ''/etc/asterisk/http.conf'' file that our Asterisk-GUI installation has created, so that it contains at least the following information (comments stripped):
[general]
enabled=yes
enablestatic=yes
bindaddr=127.0.0.1
bindport=8088
prefix=asterisk
This enables Asterisk-GUI, so that ''asterisk-admin'' can both issue AMI commands and view HTML pages, as long as a browser on the server itself is used. You could also change the bind address to that of an internal NIC on your server, which is convenient for admins, but less secure. Keep in mind though, that you can also use the [[Firewall section | iceditch firewall]] to limit access to port 8088 to certain subnets and/or IP numbers.

Finally, we must work around a little Asterisk-GUI bug, by removing the (empty) directory ''static-http'' from ''/usr/share/asterisk'', and create a link there to the (non-empty) directory ''/var/lib/asterisk/static-http'':
cd /usr/share/asterisk
rmdir static-http
ln -s /var/lib/asterisk/static-http static-http
When all is said and done (well, '''done''', specifically), restart Asterisk. Asterisk-GUI should now be reachable on http://127.0.0.1:8088/asterisk/config/cfgbasic.html. Logging in there will make Asterisk-GUI configure itself ''and'' Asterisk.

=Configuring and testing Asterisk=
If you've done nothing more than the [[Installing and configuring Zaptel | previously described]] hardware installation and configuration, and the default Asterisk installation given above, then you can already do one very simple test: plug a standard analogue telephone in one of your FXS-ports, and see if you get a dialtone. (Ofcourse, if you've only got FXO-ports or no hardware at all, then this won't help you.) 
Furthermore, you could just look at the back of your Linux machine; the small LEDs next to all ports should be lit green (not including those ports for which you haven't installed a module, ofcourse). A port with a module installed, but without a burning LED, signifies no driver loaded. 
Other tests and status reports can be obtained from the following commands:
* ''lszaptel'' should show your hardware, with all installed ports (all denoted "in use"); non-installed ports may be shown as FXO-ports. Note: be aware of the neverending confusion surrounding the port name (e.g. FXS) and what signalling it runs (e.g. FXO); remember that those two are always opposed: FXO-ports run FXS signaling, FXS-ports run FXO-signaling. Thus, a non-installed port is shown as running FXS-signaling.
* ''ztcfg -vv'' should show a channel map, with for each hardware channel the channel number and the signaling protocol.
* ''asterisk -r'' should give you an Asterisk console (if Asterisk is in fact running).
If the above tests succeed, then it's time for our initial Asterisk configuration.

In the first configuration test, we'll configure both an FXS and an FXO channel - since that's what's in [http://downloads.oreilly.com/books/9780596510480.pdf asterisk, TFOTF]. This configuration comes in three parts: 
First, we make sure our FXS and FXO channels are defined in ''/etc/zaptel.conf'' - as we've already ensured previously. For this configuration test, we confirm that ''zaptel.conf'' contains something like
# Span 1: WCTDM/0 "Wildcard TDM410P Board 1" (MASTER)
fxoks=1
fxsks=3
# Global data
loadzone = nl
defaultzone = nl
Next up, we check ''/etc/asterisk/zapata.conf''. When we filter that file through ''grep -v ^\; | grep -v ^$'' (thus removing lines beginning with ";" and empty lines), '''AND''' we insert the contents of ''zapata-channels.conf'' at the place of the insert statement, then we get something like
[trunkgroups]
[channels]
context=default
switchtype=national
signalling=fxo_ls
rxwink=300
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
; from here it's all zapata_channel.conf:
signalling=fxo_ks
callerid="Channel 1" <6001>
mailbox=6001
group=5
context=from-internal
channel => 1
callerid=
mailbox=
group=
context=default
signalling=fxo_ks
callerid="Channel 2" <6002>
mailbox=6002
group=5
context=from-internal
channel => 2
callerid=
mailbox=
group=
context=default
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 3
context=default
Well that's all nice and dandy, but for testing we'll temporarily replace this ''zapata.conf'' with a much more dressed down one:
[trunkgroups]
[channels]
usecallerid=yes
hidecallerid=no
callwaiting=no
threewaycalling=yes
transfer=yes
echocancel=yes
echotraining=yes
switchtype=national
; from here it's all zapata_channel.conf:
; the internal phone on module 1/port 1
context=phones
signalling=fxo_ks
channel => 1
; the incoming line on module 3/port 3
context=incoming
signalling=fxs_ks
channel => 3
The third configuration file we're going to change, is the file containing the "dialplan", which is ''/etc/asterisk/extensions.conf''. We'll use the example from the TFOTF book:
[globals]

[general]

[default]
exten => s,1,Verbose(1|Unrouted call handler)
exten => s,n,Answer()
exten => s,n,Wait(1)
exten => s,n,Playback(tt-weasels)
exten => s,n,Hangup()

[incoming_calls]

[internal]
exten => 500,1,Verbose(1|Echo test application)
exten => 500,n,Echo()
exten => 500,n,Hangup()

[phones]
include => internal

[incoming]
exten => s,1,Answer()
exten => s,n,Echo()
With all config files changed (and their owner still ''asterisk:asterisk''), we can reload the necessary files. First we connect an outside line to the FXO port. Now we stop asterisk, then unload the Zaptel drivers, then reload them all (so they'll definately read their config files) (note: our example is for a Digium TDM410P, with driver wctdm24xxp; adapt to your own driver):
/etc/init.d/asterisk stop
rmmod wctdm24xxp
rmmod zaptel
modprobe zaptel
modprobe wctdm24xxp
/etc/init.d/asterisk start
For demonstration purposes, start up an Asterisk console (''asterisk -f''). Now we can call the outside line attached to the FXO port (e.g. with a cell phone), and we should see in our Asterisk console something like
[Oct 8 09:06:12] NOTICE[5640]: chan_zap.c:6562 ss_thread: Got event 18 (Ring Begin)...
[Oct 8 09:06:14] NOTICE[5640]: chan_zap.c:6562 ss_thread: Got event 2 (Ring/Answered)...
Furthermore, if you speak into your phone, you should hear an echo. The other test is grabbing the phone that's connected to the FXS port, and dial 500. This also should deliver an echo, albeit much quicker.

Ubuntu

2008-11-11T17:05:49Z

82.161.20.132: Convert video_ts to iso

Ubuntu

2008-11-05T20:43:49Z

82.161.20.132: /* Compiz */

Ubuntu

2008-11-05T20:42:59Z

82.161.20.132: /* Compiz */ added table

Documentation project

2008-10-27T21:06:31Z

82.161.20.132: Undo revision 1946 by 82.161.20.132 (Talk)

== The Documentation Project==
spamerdespam [[www.linuz.nl]]

Documentation in ICT projects is a tough cookie (maybe outside of ICT as well, but that's no concern of ours at this moment). What the ICT profession seems to lack is
* a thorough understanding of the fundamental problems that surround ICT documentation
* taxonomies of the different documentation purposes, target audiences (with their experience levels), and document types
* a methodology to create, review and maintain ICT documentation of sufficient quality, against reasonable cost
* templates, guidelines and best practices to assist such a methodology
* some sort of overview of the different documentation management solutions that exist, ranging from the venerable binders with photocopies and printouts, through fileshares full of text documents, through the anarchistic wiki system, all the way to Enterprise Content Management (ECM) systems with integrated document scanners, archivers, ILM-components and what have you not
* an appreciation for the specific skills that are needed in the so-called "technical writers"
* an embedded process for documentation in the business processes; if not in projects, then most surely in day-to-day system administration.

What we'll attempt to do here is to systematically address all issues surrounding ICT documentation, and develop the lacking taxonomies, methodologies etcetera.

Documentation project

2008-10-27T21:04:21Z

82.161.20.132:

== The Documentation Project==
spamerdespam [http://www.linuz.nl]

Documentation in ICT projects is a tough cookie (maybe outside of ICT as well, but that's no concern of ours at this moment). What the ICT profession seems to lack is
* a thorough understanding of the fundamental problems that surround ICT documentation
* taxonomies of the different documentation purposes, target audiences (with their experience levels), and document types
* a methodology to create, review and maintain ICT documentation of sufficient quality, against reasonable cost
* templates, guidelines and best practices to assist such a methodology
* some sort of overview of the different documentation management solutions that exist, ranging from the venerable binders with photocopies and printouts, through fileshares full of text documents, through the anarchistic wiki system, all the way to Enterprise Content Management (ECM) systems with integrated document scanners, archivers, ILM-components and what have you not
* an appreciation for the specific skills that are needed in the so-called "technical writers"
* an embedded process for documentation in the business processes; if not in projects, then most surely in day-to-day system administration.

What we'll attempt to do here is to systematically address all issues surrounding ICT documentation, and develop the lacking taxonomies, methodologies etcetera.

Documentation project

2008-10-27T21:02:19Z

82.161.20.132:

Documentation project

2008-10-27T21:01:46Z

82.161.20.132:

== The Documentation Project==
spamerdespam [www.linuz.nl]

Documentation in ICT projects is a tough cookie (maybe outside of ICT as well, but that's no concern of ours at this moment). What the ICT profession seems to lack is
* a thorough understanding of the fundamental problems that surround ICT documentation
* taxonomies of the different documentation purposes, target audiences (with their experience levels), and document types
* a methodology to create, review and maintain ICT documentation of sufficient quality, against reasonable cost
* templates, guidelines and best practices to assist such a methodology
* some sort of overview of the different documentation management solutions that exist, ranging from the venerable binders with photocopies and printouts, through fileshares full of text documents, through the anarchistic wiki system, all the way to Enterprise Content Management (ECM) systems with integrated document scanners, archivers, ILM-components and what have you not
* an appreciation for the specific skills that are needed in the so-called "technical writers"
* an embedded process for documentation in the business processes; if not in projects, then most surely in day-to-day system administration.

What we'll attempt to do here is to systematically address all issues surrounding ICT documentation, and develop the lacking taxonomies, methodologies etcetera.

VSFTPD

2008-10-26T15:38:14Z

82.161.20.132: VSFTPD

Very secure ftp server.

To install
apt-get install vsftpd

To configure got to
/etc/vsftpd.conf
vi /etc/vsftpd.conf

[Optional] Disable Anonymous account by finding the line that says anonymous_enable=YES and make it

anonymous_enable=NO

[Optional] Turn off or on write access (upload access). Find and uncomment the following line:

write_enable=YES

[Optional] Add you banner when people log in. Find and uncomment this #ftpd_banner=Welcome to blah FTP service. line and make it:

ftpd_banner=Welcome to Insomnia FTP service. Enjoy.

[Optional] Allow local users to log in. Uncomment the following line:

local_enable=YES

Smart Daemon

2008-10-16T19:06:15Z

82.161.20.132: /* Format */

== '''SMART''' ==

If you want to read out the smart status of your hard disk you can use smartmontools.

>apt-get install smartmontools

Now you have 2 utility program's (smartctl and smartd). With smartctl you can read out your hard disks

>smartctl -a /dev/hda

This will give you all info of your hard disk. For sata disk you will have to give the -d option

>smartctl -d ata -a /dev/hda

Fore more options on smartctl use -h

Now we can configure the smart daemon in /etc/smartd.conf. This daemon will monitor your hard disks.
This config file gives you a good explination of the different options you can use

I use the following options

/dev/sda -d ata -a -o on -S on -s (S/../.././02|L/../../6/03)
/dev/sda -d ata -H -m admin@linuz.nl

== Format ==

To see you're current disk partitioning
darktower:~# fdisk -l

Disk /dev/hda: 120.0 GB, 120060444672 bytes
255 heads, 63 sectors/track, 14596 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 14596 117242338+ 83 Linux

To see more info on you're drive you can use ''smartctl'' This is a command provided by the smartmontools package.
smartctl -i /dev/hda

Also ''hdparm'' can be used to get or set the drive parameters.
hdparm -d /dev/hda

Now to partition the disk
cfdisk /dev/hda
.
Now that we have 1 or more partitions, we have to format it with a filesystem. The most commonly used filesystem is ext3 (in unix that is)
mkfs.ext3 /dev/hda1

Smart Daemon

2008-10-16T18:54:21Z

82.161.20.132: /* '''SMART''' */

Asterisk basic configuration

2008-10-14T19:30:16Z

82.161.20.132: /* Asterisk dialplans - handling incoming calls */

Vim

2008-05-25T15:49:33Z

82.161.20.132: add tabel

==Introduction==
The screen-oriented text editor ''vim'' stems from ''vi'', written in '76 for an early BSD Unix release by [http://www.engin.umich.edu/alumni/engineer/04SS/achievements/advances.html#joy Bill Joy]. ''vi'' is old, nonintuitive, and complex. ''[http://en.wikipedia.org/wiki/Vim_%28text_editor%29 vim]'' stems from 1991, and stands for '''''V'''i '''IM'''proved'', but its improvements do not lessen it's nonintuitivity or complexity.

So why do we feel that ''vim'' is an essential system tool? Well, it's because
* vi can be found on just about any Linux and Unix system
* vi is very powerful
* with some practice, it's even usable.

==Installation and configuration==
When you install ''vim'', you also get ''xxd'', a tool to make a hexdump, or convert a hex dump back to it's original binary form.

==Using VIM==

Vim operates in 2 modus. A command mode and a insert mode. You start in command mode so almost every key is a command. You can switch to insert mode with ''i'' to return in command mode press ''esc'' or ( ''ctrl ['' )
Start in insert mode and typ some text. To save your progress return in command mode with ''esc'' Now we can use the ''ex-commands'' typ '':w'' to save the document. or use these commands.

{| class="wikitable" style="text-align:center" border="1" cellspacing="0" cellpadding="5"
!style="background:#ffdead;"|Command
!style="background:#ffdead;"|Output
|-
|:w
|Save
|-
|:w
|'filename' Save with this filename
|-
|:q
|quit vim
|-
|:q!
|quit without save
|-
|:wq
|save and quit
|}
==About modal editors==

==Cursor positioning==
{| class="wikitable" style="text-align:center" border="1" cellspacing="0" cellpadding="5"
!style="background:#ffdead;"|Key(s)
!style="background:#ffdead;"|Movement
|-
|j
|down one line, same column
|-
|k
|up one line, same column
|-
|h
|one character back
|-
|l,<space>
|one character forward
|-
|b
|one word back (to beginning of previous word)
|-
|e
|one word back (to end of previous word)
|-
|w
|one word forward
|-
|<enter>
|beginning of next line
|-
|0 (zero)
|beginning of line
|-
|$
|end of line
|-
|''n''G
|to beginning of line ''n''; if no number given, the last line of the file
|-
|:''n''
|also to beginning of line ''n'' (but this is visible as command)
|-
|}

==Searching==
{| class="wikitable" style="text-align:center" border="1" cellspacing="0" cellpadding="5"
!style="background:#ffdead;"|Key(s)
!style="background:#ffdead;"|Movement
|-
|/''pattern''
|Moves the cursor to the next occurrence of ''pattern''; will wrap around to the beginning of the file from the last occurence
|-
|?''pattern''
|Moves the cursor backward to the previous occurrence of ''pattern''; will wrap around to the end of the file from the first occurence
|-
|n
|repeats last pattern search (either / or ?)
|}

==Text insertion==
a Appends text after cursor. Terminated by escape key.
A Appends text at the end of the line. Terminated the escape key.
i Inserts text before cursor. Terminated by the escape key.
I Inserts text at the beginning of the line. Terminated by the escape key.
o Opens new line below the current line for text insertion. Terminated by the escape key.
O Opens new line above the current line for text insertion. Terminated by the escape key.
DEL Overwrites last character during text insertion.
ESC Stops text insertion. The escape key on the DECstations is the F11 key

==Notes==
In Debian Etch, the default editor is nano instead of vim. This can be changed in the following way:
sudo update-alternatives --set editor /usr/bin/vim.tiny
Now '''all''' commands that invoke an editor will use ''vi'' instead of ''vim''. Is that a good thing? We're not sure, but we do want to keep our ''vi'' skills up to par, so we do this.

Smart Daemon

2008-05-17T23:16:19Z

82.161.20.132:

== '''SMART''' ==

Install smartmontools

>apt-get install smartmontools

Now you have 2 utility program's (smartctl and smartd). With smartctl you can read out your hard disks

>smartctl -a /dev/hda

This will give you all info of your hard disk. For sata disk you will have to give the -d option

>smartctl -d ata -a /dev/hda

Fore more options on smartctl use -h

Now we can configure the smart daemon in /etc/smartd.conf
This config file gives you a good explination of the different options you can use

I use the following options

/dev/sda -d ata -a -o on -S on -s (S/../.././02|L/../../6/03)
/dev/sda -d ata -H -m admin@linuz.nl

Crontab

2008-05-17T18:40:32Z

82.161.20.132: /* Crontab */

==Crontab==

To schedule a task you can use cron. Every user has it's own crontab.
Also system has a crontab witch has 3 default entry's in /etc/crontab

# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# m h dom mon dow user command
17 * * * * root cd / && run-parts --report /etc/cron.hourly
25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#

you can schedule tasks directly in the 3 folders.

To see the current users crontab

>crontab -l

To see a users crontab

>crontab -u 'username' -l

To edit the current users crontab

>crontab -e

Now you can schedule your task
# +---------------- minute (0 - 59)
# | +------------- hour (0 - 23)
# | | +---------- day of month (1 - 31)
# | | | +------- month (1 - 12)
# | | | | +---- day of week (0 - 6) (Sunday=0 or 7)
# | | | | |
* * * * * command to be executed (full path to command/script)