Tricks, Licks & Harmonix

Installing Apache 2.2 from source on Ubuntu

2007-12-23T03:53:00.000-08:00

Two reasons you might want to do this.

You want to host a Rails application using Mongrel via Apache and mod_proxy_balancer.

You’re studying in a Website administration module for your 3rd year Software Engineering degree :)

Seriously though, if you don’t want to use mod_proxy_balancer, just do a normal apt-get install of Apache 2 and you’ll be fine. mod_proxy_balancer is only available for Apache 2.2, and currently, that’s not available from the Ubuntu repositories via apt-get.

This article only covers installing Apache 2.2 - I’ll write another one for getting Subversion and PHP working shortly afterwards.

Workspace
If you’ve not got the build-essential package installed yet:

sudo apt-get install build-essential

It’s best to keep all of the source files in a seperate directory so they don’t mess up your home
directory.

cd
mkdir src
cd src

Zlib
So that Apache can compress output to browsers that support it, we’re going to install Zlib first of all:

wget http://www.zlib.net/zlib-1.2.3.tar.gz
tar xvfz zlib-1.2.3.tar.gz
cd zlib-1.2.3/
./configure --prefix=/usr/local
make
sudo make install

Apache 2.2
Now download the Apache 2.2 source files:

cd ..
wget http://apache.rmplc.co.uk/httpd/httpd-2.2.3.tar.gz

Extract and move into the directory:

tar xvfz httpd-2.2.3.tar.gz
cd httpd-2.2.3/

Now to configure the build of Apache 2.2 that we want:

./configure --prefix=/usr/local/apache2 --enable-mods-shared=all --enable-deflate --enable-proxy --enable-proxy-balancer --enable-proxy-http

Besides setting the modules we’d like installed, and the location of the install, this paramater --enable-mods-shared=all is telling Apache 2.2 to build modules so that they can be dynamically loaded when it is started. This means, we can add further modules to our Apache 2.2 install when we like - as we will do with the Subversion modules and PHP.

Once the configuration is complete:

make
sudo make install

Let’s test that it’s working:

sudo /usr/local/apache2/bin/apachectl start

Now navigate to http://localhost/ and you should see a message saying “It works!”.

Stop Apache:

sudo /usr/local/apache2/bin/apachectl stop

Apache at start-up
Now let’s get Apache to start at boot time automatically:

sudo cp /usr/local/apache2/bin/apachectl /etc/init.d/apachectlsudo chmod +x /etc/init.d/apachectl

What we’re doing here is copying the Apache Control script into the start-up directory.
We just need to add a few lines to the file for it to work nicely:sudo nano /etc/init.d/apachectl
Add the followinig, so the top of the file looks like:

#!/bin/sh
#
# chkconfig: - 85 15
# description: Apache is a web server.

Save the file.

Now we need to register it with the start-up manager:

sudo /usr/sbin/update-rc.d apachectl defaults

Securing Apache
It’s also a good idea to create a dedicate Apache system user account. It’ll make your install much more secure.

sudo adduser --system apache

Now we just need to make sure that Apache runs under this user. We do that by editting the configuration file:

sudo nano /usr/local/apache2/conf/httpd.conf

You need to find the lines that say:

User daemon
Group daemon

And change them so they look like:

User apache
Group nogroup

Save the file.
Now, let’s start Apache:

sudo /usr/local/apache2/bin/apachectl start

Now to check it’s running under the new user, apache:

ps -aux grep httpd

If you see the word apache in there, it’s working.

Check it’s all working
Now just reboot the system and before logging in, check on another machine by visiting the servers IP in the web browser and you should see the “It works!” message. This means Apache started up correctly automatically.

Building Apache 2.2 from source. Done.

Verifying Which Ports Are Listening with Nmap

2007-09-13T05:15:00.000-07:00

Once you have configured services on the network, it is important to keep tabs on which ports are actually listening on the system's network interfaces. Any open ports can be evidence of an intrusion.

There are two basic approaches for listing the ports that are listening on the network. The less reliable approach is to query the network stack by typing commands such as:

netstat -an

or

lsof -i

This method is less reliable since these programs do not connect to the machine from the network, but rather check to see what is running on the system. For this reason, these applications are frequent targets for replacement by attackers. In this way, crackers attempt to cover their tracks if they open unauthorized network ports.
A more reliable way to check which ports are listening on the network is to use a port scanner such as nmap.

First install Nmap with:

apt-get install nmap

The following command issued from the console determines which ports are listening for TCP connections from the network:

nmap -sT -O localhost

The output of this command looks like the following:
Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
Interesting ports on localhost.localdomain (127.0.0.1):
(The 1596 ports scanned but not shown below are in state: closed)
Port State Service
22/tcp open ssh
111/tcp open sunrpc
515/tcp open printer
834/tcp open unknown
6000/tcp open X11
Remote OS guesses: Linux Kernel 2.4.0 or Gentoo 1.2 Linux 2.4.19 rc1-rc7)
Nmap run completed -- 1 IP address (1 host up) scanned in 5 seconds

This output shows the system is running portmap due to the presence of the sunrpc service. However, there is also a mystery service on port 834. To check if the port is associated with the official list of known services, type:

cat /etc/services grep 834

This command returns no output. This indicates that while the port is in the reserved range (meaning 0 through 1023) and requires root access to open, it is not associated with a known service.

Next, you can check for information about the port using netstat or lsof. To check for port 834 using netstat, use the following command:

netstat -anp grep 834

The command returns the following output:

tcp 0 0 0.0.0.0:834 0.0.0.0:* LISTEN 653/ypbind

The presence of the open port in netstat is reassuring because a cracker opening a port surreptitiously on a hacked system would likely not allow it to be revealed through this command. Also, the [p] option reveals the process id (PID) of the service which opened the port. In this case the open port belongs to ypbind (NIS), which is an RPC service handled in conjunction with the portmap service.

The lsof command reveals similar information since it is also capable of linking open ports to services:

lsof -i grep 834

Below is the relevant portion of the output for this command:

ypbind 653 0 7u IPv4 1319 TCP *:834 (LISTEN)
ypbind 655 0 7u IPv4 1319 TCP *:834 (LISTEN)
ypbind 656 0 7u IPv4 1319 TCP *:834 (LISTEN)
ypbind 657 0 7u IPv4 1319 TCP *:834 (LISTEN)

As you can see, these tools can reveal a great about the status of the services running on a machine. These tools are flexible and can provide a wealth of information about network services and configuration. Consulting the man pages for lsof, netstat, nmap, and services is therefore highly recommended.

Test an MX record

2007-09-09T01:07:00.000-07:00

Test an MX record by typing the following in a Dos prompt:

nslookup -q=mx server.domain.dk

The reply should look like this:

server.domain.dk MX preference = 10, mail exchanger = server.domain.dk

To start or stop services under any debian based distro

2007-08-21T03:45:00.000-07:00

Get the name of the service you want to start or stop

ls /etc/init.d

then

sudo invoke-rc.d servicename startstop

Which is only a shortcut to

sudo /etc/init.d/servicename startstop

The easiest way (my opinion) to do all this is to use this nice little app here:

apt-get install sysv-rc-conf

sysv-rc-conf

WordPress Installation on Ubuntu

2007-08-20T23:37:00.000-07:00

First check that Apache, Mysql and Phpmyadmin is installed and working (sort of an AMP server?;-)
Download WordPress (in my case in DK version): http://svn.automattic.com/wordpress-i18n/da_DK/tags/2.2.2/wordpress-2.2.2-da_DK.zip
Extract your WordPress archieve into your server directory.

sudo tar zxvf wordpress-x.x.x.tar.gz --directory=/var/www/
Create a database for WordPress on your Ubuntu, as well as a MySQL user who has all privileges for accessing and modifying it. You can use phpMyAdmin to make it easier (http://localhost)
First create database: wordpress
Then create a new user: wordpress with password: wordpresspassword
Write down the values you used for databasename, wordpressusername, hostname, and password for future purpose.
Rename the wp-config-sample.php file to wp-config.php. Open and edit wp-config.php file to:

// ** MySQL settings ** //
define('DB_NAME', 'wordpress');

define('DB_USER', 'wordpress');

define('DB_PASSWORD', 'wordpresspassword');

define('DB_HOST', 'localhost');

Run the Install Script by browsing to wp-admin/install.php within the directory into which you just installed WordPress. For example: point your browser to http://localhost/wordpress/wp-admin/install.php.
To test: Point your browser to http://localhost/wordpress.

Installing AlienBBC on Linux

2007-08-15T11:34:00.000-07:00

AlienBBC is a plugin for slimserver, the software platform used by the Slim Devices line of networked music players.

It is primarily designed to allow the user to listen to BBC Radio streams but also adds the ability to listen to any RealAudio stream. Currently, it is capable of parsing and playing the following resources:

All the main BBC Radio 'Live' streams
The BBC 'Listen Again' Audio on Demand content
All Available BBC Radio 2 Content
All Available BBC Radio 4 Content
The BBC7 Audio Archive
The Available BBC Local Radio Stations
Radio 5 Live Audio Archive
Some of the ABC Content (Australian Broadcasting Corporation)
A number of other streams, suggested by AlienBBC Users
For a complete list of stations see here

These instructions assume you are installing on to SlimServer V6.2 or later.

Download the linux archive http://www.x2systems.com/alienbbc/alienbbc-linux-v1.06_6.2-3.tar.gz.
Extract this tar file into the main slimserver directory. This is usually: /usr/local/slimserver.
Ensure that /usr/local/slimserver/Bin/mplayer.sh is executable by the user 'slimserver'.
Ensure that mplayer is installed and available on the path for slimserver (as for previous AlienBBC versions) and has the relevant codecs available.If you need help with installing mplayer this may help: http://forums.slimdevices.com/showthread.php?t=17015.
If using mplayer pre7 or later edit slimserver-convert.conf to comment out the lines that follow "# Default mplayer up to pre6". Then uncomment the lines that follow "# Alternative for mplayer pre7 or later".
Restart slimserver and see if AlienBBC appears on the web page.
If you have trouble, Run './slimserver.pl -d_plugin' in a shell from /usr/local/slimserver to check for error messages at startup.

Extra Information

For detailed instructions on installing on linux see ripcaster's website http://www.ripcaster.co.uk/node

Instructions for installing Slimserver Ubuntu (Debian)

2007-08-14T14:09:00.000-07:00

/* install as su */
sudo su

/* setup slimserver user */
addgroup slimserver
adduser --ingroup slimserver slimserver

/* unpack slimserver code */
cd /usr/local
tar -xzvf ....SlimServer_v2005-08-02.tar.gz
ln -s SlimServer_v2005-08-0 slimserver (link or rename directory as required)
chown -Rf slimserver:slimserver /usr/local/slimserver

/* create pref file with write permissions for slimserver */
nano /etc/slimserver.pref
(save as empty file)
chmod 666 /etc/slimserver.pref

/* create startup script */
nano /etc/init.d/slimserver
cut & paste:

#!/bin/sh

# slimserver init script for Debian Linux
#
# This script expects slimserver to be installed in
# /usr/local/slimserver
#
# logfile will be written to
# /tmp/slimserver.log
#

DAEMON=/usr/local/slimserver/slimserver.pl
PIDFILE=/var/tmp/slimserver.pid
LOGFILE=/tmp/slimserver.log
USER=slimserver
SLIMSERVER_OPTS=""

test -x ${DAEMON} || exit 0

case "$1" in
start) echo -n "Starting Slimserver: "
HOME=/home/$USER
start-stop-daemon --start --quiet --exec $DAEMON \
--chuid ${USER} -- --daemon \
--prefsfile=/etc/slimserver.pref --pidfile=${PIDFILE} \
--logfile=${LOGFILE} ${SLIMSERVER_OPTS}
echo "slimserver"
;;

stop) echo -n "Stopping Slimserver: "
start-stop-daemon --stop --quiet --user ${USER} --pidfile ${PIDFILE} --retry 5
echo "done"
;;

force-reload|restart) $0 stop
$0 start
;;

*) echo "Usage: $0 {start|stop|restart|force-reload}"
exit 1;
;;

esac

exit 0

(save file)
chmod chmod 755 /etc/init.d/slimserver

/* start slimserver */
/etc/init.d/slimserver start

/* add to init */
update-rc.d slimserver defaults

/* kill su */
exit

Installing Slimserver on Ubuntu Feisty 7.04

2007-08-14T07:14:00.000-07:00

I had to type this to get it installed to fix the size mismatch error. It would just come back with size mismatch on these two libclass files. Here are the commands I did and it worked:

wget http://mirror.internode.on.net/pub/ubuntu/ubuntu/pool/universe/libc/libclass-data-accessor-perl/libclass-data-accessor-perl_0.03-1_all.deb

dpkg -i libclass-data-accessor-perl_0.03-1_all.deb

wget http://mirror.internode.on.net/pub/ubuntu/ubuntu/pool/universe/libc/libclass-inspector-perl/libclass-inspector-perl_1.16-1_all.deb

dpkg -i libclass-inspector-perl_1.16-1_all.deb

apt-get install slimserver

I can then go to port 127.0.0.1:9000 and set up slimserver. !

X-Forwarding mythtv-setup

2007-07-13T05:14:00.000-07:00

If the backend machine that is being setup doesn't have an X server, mythtv-setup can be launched remotely through a ssh connection that has X forwarded over it.

It can be run on windows machine running Cygwin/X, a linux/unix machine running xorg-x11, or a MacOS machine running Apple/X11.

The connection is generally forwarded by running the following command on a client machine:

ssh USER@MACHINE -X

MACHINE is the ip address or hostname of the machine that you are ssh'ing into
USER is the username normally used for configuring things on this machine.

Once connected to the remote machine, apps can be launched as though they are being run locally.

Installere Imon VDF

2007-07-07T16:02:00.000-07:00

Mit media Center projekt er bygget ind i et kabinet af mærket Silverstone LC11. Et pænt stuekabinet med en nogenlunde WAF-faktor (Wife-Acceptance-Factor). Det har et VDF display af mærket Soundgraph Imon indbygget som samtidigt også fungerer som IR med den medfølgende remote. En eller anden har hacket modulet og skrevet drivere som er med i de nyeste Lirc pakker så hvorfor ikke se om vi kan få det til at spille med mythtv.

1: INSTAL LCDPROC

Brug Synaptics til at hentet lcdproc:

apt-get install lcdproc

ow if that install was doing everything right we could jump to the next step, but there's a few problems with it which we must fix manually.Do the following:

Code:

gksudo gedit /etc/LCDd.conf

Search for the section [server] and comment out the Driver=CFontzPacket.

Uncomment the line Driver=imon

Search for DriverPath and change it to read

Code:

DriverPath=/usr/lib/lcdproc/

Save the file.

Now edit the following file:

Code:
gksudo gedit /etc/init.d/LCDd

Change the line DAEMON_OPTS to read:

Code:
DAEMON_OPTS="-s true -f true -c /etc/LCDd.conf"

Yes, eventhough the MAN pages for LCDd don't mention this, it really needs the "true" arguments.

STEP 2: INSTALL IMON_VFD

Now download the file from Venky for the standalone Imon VFD Driver:http://venky.ws/projects/imon/#standalone

Untar it:

Code:
tar xvzf imon_vfd.tgz

cd imon

Donwload the following patch from Garth Dahlstrom's web site and put it in the imon directory:

http://stacktrace.org/index_html/200...imon-2.6.patch

Then apply the patch and compile:

Code:
cat imon-2.6.patch | patch

make -C /usr/src/linux-headers-2.6.17-10-generic/ SUBDIRS=$PWD modules

sudo make install

This will have created the /dev/lcd0 device that you need to talk to the LCD.

STEP 3: LOAD EVERYTHING

Now let's do the final steps: loading the drivers and testing if everything works.

Code:
modprobe imon_vfd

# Run /usr/sbin/LCDd manually to check all is good.

sudo /usr/sbin/LCDd

If it worked without error you should see something on your VFD. We can now kill LCDd:

Code:
sudo killall LCDd

And start it like it should be started, in the background:

Code:
sudo /etc/init.d/LCDd start

Now we need to make sure all this gets loaded properly when rebooting.

Edit /etc/modules and add the following line at the end:

gedit /etc/modules

Code:
imon_vfd

That's it! All you have to do is reboot.

STEP 4: ACTIVATE LCD IN MYTHTV

Now start MythTV front-end and go to the Setup/Appearance section.

In there you will find the "Enable LCD device" option. By setting it ON, the mythlcdserver be started and it will communicate with LCDd and display info on the LCD during various MythTV operations.

Enjoy !

Troubleshooting: If you cannot find the module LCDd when you do a "ps ax grep LCDd" then you may have to:

Code:
sudo update-rc.d LCDd defaults

If you want to figure out what is happening, you will find the LCDd error messages in /var/log/syslog

Folderen “linux-headers-2.6.17-10-generic” skal eksakt modsvare det der ligger /usr/src/!

The Perfect Setup - Ubuntu 7.04 LAMP

2007-07-03T07:04:00.000-07:00

This tutorial shows how to set up a Ubuntu
Feisty Fawn (Ubuntu 7.04) based server that offers all services needed by ISPs
and hosters: Apache web server (SSL-capable), Postfix mail server with
SMTP-AUTH and TLS, BIND DNS server, Proftpd FTP server, MySQL server, Courier
POP3/IMAP, Quota, Firewall, etc. This tutorial is written for the 32-bit
version of Ubuntu Feisty Fawn, but should apply to the 64-bit version with very
little modifications as well.

I will use the following software:

Web Server: Apache 2.2
Database Server: MySQL 5.0
Mail Server: Postfix
DNS Server: BIND9
FTP Server: proftpd POP3/IMAP: I will use Maildir format and therefore
install Courier-POP3/Courier-IMAP.
Webalizer for web site statistics

In the end you should have a system that
works reliably, and if you like you can install the free webhosting control
panel ISPConfig (i.e., ISPConfig runs on it out of
the box).

1 Enable The root Account

After the reboot you can login with your pregeditously
created username (e.g. administrator). Because we must run all
the steps from this tutorial as root user, we must enable the root account now.

Run

sudo passwd root

and give root a password. Afterwards we
become root by running

2 Install The SSH Server

Ubuntu does not install OpenSSH by default,
therefore we do it now. Run

apt-get install ssh openssh-server

You will be prompted to insert the
installation CD again.

3 Configure The Network

Because the Ubuntu installer has configured
our system to get its network settings gedita DHCP, we have to change that now
because a server should have a static IP address. Edit /etc/network/interfaces
and adjust it to your needs (in this example setup I will use
the IP address 192.168.0.100):

gedit /etc/network/interfaces

# This file describes the network interfaces available on your system

# and how to activate them. For more information, see interfaces(5).

# The loopback network interface

auto lo

iface lo inet loopback

# The primary network interface

auto eth0

iface eth0 inet static

        address 192.168.0.100

        netmask 255.255.255.0

        network 192.168.0.0

        broadcast 192.168.0.255

        gateway 192.168.0.1

Then restart your network:

/etc/init.d/networking restart

Then edit /etc/hosts.
Make it look like this:

gedit /etc/hosts

127.0.0.1       localhost.localdomain   localhost

192.168.0.100   server1.example.com     server1

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback

fe00::0 ip6-localnet

ff00::0 ip6-mcastprefix

ff02::1 ip6-allnodes

ff02::2 ip6-allrouters

ff02::3 ip6-allhosts

Now run

echo server1.example.com > /etc/hostname

and reboot the system:

shutdown -r now

Afterwards, run

hostname

hostname -f

Both should show server1.example.com.

From now on you can use an SSH client such
as PuTTY and connect from
your workstation to your Ubuntu Feisty Fawn server and follow the remaining
steps from this tutorial.

4 Edit /etc/apt/sources.list And Update Your Linux Installation

Edit /etc/apt/sources.list.
Comment out or remove the installation CD from the file and make sure that the universe
and multiverse repositories
are enabled. It should look like this:

gedit /etc/apt/sources.list

deb http://de.archive.ubuntu.com/ubuntu/ feisty main restricted

deb-src http://de.archive.ubuntu.com/ubuntu/ feisty main restricted

## Major bug fix updates produced after the final release of the

## distribution.

deb http://de.archive.ubuntu.com/ubuntu/ feisty-updates main restricted

deb-src http://de.archive.ubuntu.com/ubuntu/ feisty-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu

## team, and may not be under a free licence. Please satisfy yourself as to

## your rights to use the software. Also, please note that software in

## universe WILL NOT receive any regeditew or updates from the Ubuntu security

## team.

deb http://de.archive.ubuntu.com/ubuntu/ feisty universe

deb-src http://de.archive.ubuntu.com/ubuntu/ feisty universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu

## team, and may not be under a free licence. Please satisfy yourself as to

## your rights to use the software. Also, please note that software in

## multiverse WILL NOT receive any regeditew or updates from the Ubuntu

## security team.

deb http://de.archive.ubuntu.com/ubuntu/ feisty multiverse

deb-src http://de.archive.ubuntu.com/ubuntu/ feisty multiverse

## Uncomment the following two lines to add software from the 'backports'

## repository.

## N.B. software from this repository may not have been tested as

## extensively as that contained in the main release, although it includes

## newer versions of some applications which may progeditde useful features.

## Also, please note that software in backports WILL NOT receive any regeditew

## or updates from the Ubuntu security team.

# deb http://de.archive.ubuntu.com/ubuntu/ feisty-backports main restricted universe multiverse

# deb-src http://de.archive.ubuntu.com/ubuntu/ feisty-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu feisty-security main restricted

deb-src http://security.ubuntu.com/ubuntu feisty-security main restricted

deb http://security.ubuntu.com/ubuntu feisty-security universe

deb-src http://security.ubuntu.com/ubuntu feisty-security universe

deb http://security.ubuntu.com/ubuntu feisty-security multiverse

deb-src http://security.ubuntu.com/ubuntu feisty-security multiverse

Then run

apt-get update

to update the apt package database and

apt-get upgrade

to install the latest updates (if there are
any).

5 Change The Default Shell

/bin/sh is a symlink to /bin/dash,
however we need /bin/bash, not /bin/dash.
Therefore we do this:

rm -f /bin/sh

ln -s /bin/bash /bin/sh

If you don't do this, the ISPConfig
installation will fail.

6 Install Some Software

Now we install a few packages that are
needed later on. Run

apt-get install binutils cpp fetchmail flex gcc
libarchive-zip-perl libc6-dev libcompress-zlib-perl libdb4.3-dev libpcre3
libpopt-dev linux-kernel-headers lynx m4 make ncftp nmap openssl perl
perl-modules unzip zip zlib1g-dev autoconf automake1.9 libtool bison
autotools-dev g++

(This command should go into one line!)

8 Quota

(If you have chosen a different partitioning scheme than I
did, you must adjust this chapter so that quota applies to the partitions where
you need it.)

To install quota, run

apt-get install quota

Edit /etc/fstab.
Mine looks like this (I added ,usrquota,grpquota to
the partition with the mount point /):

gedit /etc/fstab

# /etc/fstab: static file system information.

# <file system> <mount point>   <type>  <options>       <dump>  <pass>

proc            /proc           proc    defaults        0       0

# /dev/sda1

UUID=4e83bdf2-ea2b-416c-85b0-ed2c56a19433 /               ext3    defaults,errors=remount-ro,usrquota,grpquota 0       1

# /dev/sda5

UUID=2ded13c4-6693-47ca-b1c8-18ebd32dbce9 none            swap    sw              0       0

/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0

/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

To enable quota, run these commands:

touch /quota.user /quota.group

chmod 600 /quota.*

mount -o remount /

quotacheck -avugm

quotaon -avug

9 DNS Server

Run

apt-get install bind9

For security reasons we want to run BIND
chrooted so we have to do the following steps:

/etc/init.d/bind9 stop

Edit the file /etc/default/bind9 so
that the daemon will run as the unprigeditleged user bind,
chrooted to /var/lib/named. Modify the line: OPTIONS="-u
bind" so that it reads OPTIONS="-u
bind -t /var/lib/named":

gedit /etc/default/bind9

OPTIONS="-u bind  -t /var/lib/named"

# Set RESOLVCONF=no to not run resolvconf

RESOLVCONF=yes

Create the necessary directories under /var/lib:

mkdir -p /var/lib/named/etc

mkdir /var/lib/named/dev

mkdir -p /var/lib/named/var/cache/bind

mkdir -p /var/lib/named/var/run/bind/run

Then move the config directory from /etc to
/var/lib/named/etc:

mv /etc/bind /var/lib/named/etc

Create a symlink to the new config directory
from the old location (to avoid problems when bind gets updated in the future):

ln -s /var/lib/named/etc/bind /etc/bind

Make null and random degeditces, and fix
permissions of the directories:

mknod /var/lib/named/dev/null c 1 3

mknod /var/lib/named/dev/random c 1 8

chmod 666 /var/lib/named/dev/null /var/lib/named/dev/random

chown -R bind:bind /var/lib/named/var/*

chown -R bind:bind /var/lib/named/etc/bind

We need to modify /etc/default/syslogd so
that we can still get important messages logged to the system logs. Modify the
line: SYSLOGD="" so that it reads: SYSLOGD="-a
/var/lib/named/dev/log":

gedit /etc/default/syslogd

# Top configuration file for syslogd

# Full documentation of possible arguments are found in the manpage

# syslogd(8).

# For remote UDP logging use SYSLOGD="-r"

SYSLOGD="-a /var/lib/named/dev/log"

Restart the logging daemon:

/etc/init.d/sysklogd restart

Start up BIND, and check /var/log/syslog
for errors:

/etc/init.d/bind9 start

10 MySQL

In order to install MySQL, we run

apt-get install mysql-server mysql-client
libmysqlclient15-dev

We want MySQL to listen on all interfaces,
not just localhost, therefore we edit /etc/mysql/my.cnf
and comment out the line bind-address = 127.0.0.1:

gedit /etc/mysql/my.cnf

[...]

#bind-address           = 127.0.0.1

[...]

Then we restart MySQL:

/etc/init.d/mysql restart

Now check that networking is enabled. Run

netstat -tap

In the output you should see a line like
this one:

tcp 0 0 *:mysql *:* LISTEN 22565/mysqld

Run

mysqladmin -u root password yourrootsqlpassword

mysqladmin -h server1.example.com -u root password yourrootsqlpassword

to set a password for the user root
(otherwise anybody can access your MySQL database!).

11 Postfix With SMTP-AUTH And TLS

In order to install Postfix with SMTP-AUTH
and TLS do the following steps:

apt-get install postfix libsasl2 sasl2-bin
libsasl2-modules libdb3-util procmail

You will be asked two questions. Answer as
follows:

General type of configuration? <--
Internet Site

Mail
name? <-- server1.example.com

Then run

dpkg-reconfigure postfix

Again, you'll be asked some questions:

General type of configuration? <-- Internet
Site

Where
should mail for root go <-- [blank]

Mail
name? <-- server1.example.com

Other
destinations to accept mail for? (blank for none) <--
server1.example.com, localhost.example.com, localhost.localdomain, localhost

Force
synchronous updates on mail queue? <-- No

Local
networks? <-- 127.0.0.0/8

Use
procmail for local delivery? <-- Yes

Mailbox
size limit <-- 0

Local
address extension character? <-- +

Internet
protocols to use? <-- all

Next, do this:

postconf -e 'smtpd_sasl_local_domain ='

postconf -e 'smtpd_sasl_auth_enable = yes'

postconf -e 'smtpd_sasl_security_options = noanonymous'

postconf -e 'broken_sasl_auth_clients = yes'

postconf -e 'smtpd_recipient_restrictions =
permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination'

postconf -e 'inet_interfaces = all'

echo 'pwcheck_method: saslauthd' >> /etc/postfix/sasl/smtpd.conf

echo 'mech_list: plain login' >> /etc/postfix/sasl/smtpd.conf

Afterwards we create the certificates for
TLS:

mkdir /etc/postfix/ssl

cd /etc/postfix/ssl/

openssl genrsa -des3 -rand /etc/hosts -out smtpd.key 1024

chmod 600 smtpd.key

openssl req -new -key smtpd.key -out smtpd.csr

openssl x509 -req -days 3650 -in smtpd.csr -signkey
smtpd.key -out smtpd.crt

openssl rsa -in smtpd.key -out smtpd.key.unencrypted

mv -f smtpd.key.unencrypted smtpd.key

openssl req -new -x509 -extensions v3_ca -keyout cakey.pem -out cacert.pem
-days 3650

Next we configure Postfix for TLS:

postconf -e 'smtpd_tls_auth_only = no'

postconf -e 'smtp_use_tls = yes'

postconf -e 'smtpd_use_tls = yes'

postconf -e 'smtp_tls_note_starttls_offer = yes'

postconf -e 'smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key'

postconf -e 'smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt'

postconf -e 'smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem'

postconf -e 'smtpd_tls_loglevel = 1'

postconf -e 'smtpd_tls_received_header = yes'

postconf -e 'smtpd_tls_session_cache_timeout = 3600s'

postconf -e 'tls_random_source = dev:/dev/urandom'

postconf -e 'myhostname = server1.example.com'

The file /etc/postfix/main.cf
should now look like this:

cat /etc/postfix/main.cf

# See /usr/share/postfix/main.cf.dist for a commented, more complete version

# Debian specific:  Specifying a file name will cause the first

# line of that file to be used as the name.  The Debian default

# is /etc/mailname.

#myorigin = /etc/mailname

smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)

biff = no

# appending .domain is the MUA's job.

append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings

#delay_warning_time = 4h

# TLS parameters

smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt

smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key

smtpd_use_tls = yes

smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache

smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for

# information on enabling SSL in the smtp client.

myhostname = server1.example.com

alias_maps = hash:/etc/aliases

alias_database = hash:/etc/aliases

myorigin = /etc/mailname

mydestination = server1.example.com, localhost.example.com, localhost.localdomain, localhost

relayhost =

mynetworks = 127.0.0.0/8

mailbox_command = procmail -a "$EXTENSION"

mailbox_size_limit = 0

recipient_delimiter = +

inet_interfaces = all

inet_protocols = all

smtpd_sasl_local_domain =

smtpd_sasl_auth_enable = yes

smtpd_sasl_security_options = noanonymous

broken_sasl_auth_clients = yes

smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination

smtpd_tls_auth_only = no

smtp_use_tls = yes

smtp_tls_note_starttls_offer = yes

smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem

smtpd_tls_loglevel = 1

smtpd_tls_received_header = yes

smtpd_tls_session_cache_timeout = 3600s

tls_random_source = dev:/dev/urandom

Restart Postfix:

/etc/init.d/postfix restart

Authentication will be done by saslauthd.
We have to change a few things to make it work properly. Because Postfix runs
chrooted in /var/spool/postfix we have to do the
following:

mkdir -p /var/spool/postfix/var/run/saslauthd

Now we have to edit /etc/default/saslauthd in
order to activate saslauthd. Set START to yes
and change the line OPTIONS="-c" to OPTIONS="-c
-m /var/spool/postfix/var/run/saslauthd -r":

gedit /etc/default/saslauthd

# Settings for saslauthd daemon

# Should saslauthd run automatically on startup? (default: no)

START=yes

# Which authentication mechanisms should saslauthd use? (default: pam)

# Available options in this Debian package:

# getpwent  -- use the getpwent() library function

# kerberos5 -- use Kerberos 5

# pam       -- use PAM

# rimap     -- use a remote IMAP server

# shadow    -- use the local shadow password file

# sasldb    -- use the local sasldb database file

# ldap      -- use LDAP (configuration is in /etc/saslauthd.conf)

# Only one option may be used at a time. See the saslauthd man page

# for more information.

# Example: MECHANISMS="pam"

MECHANISMS="pam"

# Additional options for this mechanism. (default: none)

# See the saslauthd man page for information about mech-specific options.

MECH_OPTIONS=""

# How many saslauthd processes should we run? (default: 5)

# A value of 0 will fork a new process for each connection.

THREADS=5

# Other options (default: -c)

# See the saslauthd man page for information about these options.

# Example for postfix users: "-c -m /var/spool/postfix/var/run/saslauthd"

# Note: See /usr/share/doc/sasl2-bin/README.Debian

OPTIONS="-c  -m /var/spool/postfix/var/run/saslauthd -r"

Now start saslauthd:

/etc/init.d/saslauthd start

To see if SMTP-AUTH and TLS work properly
now run the following command:

telnet localhost 25

After you have established the connection to
your Postfix mail server type

ehlo localhost

If you see the lines

250-STARTTLS

and

250-AUTH PLAIN LOGIN

everything is fine.

The output on my system looks like this:

root@server1:/etc/postfix/ssl# telnet localhost 25

Trying 127.0.0.1...

Connected to localhost.localdomain.

Escape character is '^]'.

220 server1.example.com ESMTP Postfix (Ubuntu)

ehlo localhost

250-server1.example.com

250-PIPELINING

250-SIZE 10240000

250-VRFY

250-ETRN

250-STARTTLS

250-AUTH PLAIN LOGIN

250-AUTH=PLAIN LOGIN

250-ENHANCEDSTATUSCODES

250-8BITMIME

250 DSN

quit

221 2.0.0 Bye

Connection closed by foreign host.

Type

quit

to return to the system's shell.

12 Courier-IMAP/Courier-POP3

Run this to install
Courier-IMAP/Courier-IMAP-SSL (for IMAPs on port 993) and
Courier-POP3/Courier-POP3-SSL (for POP3s on port 995):

apt-get install courier-authdaemon courier-base
courier-imap courier-imap-ssl courier-pop courier-pop-ssl courier-ssl gamin
libgamin0 libglib2.0-0

You will be asked two questions:

Create directories for web-based administration ? <-- No

SSL
certificate required <-- Ok

If you do not want to use ISPConfig,
configure Postfix to deliver emails to a user's Maildir*:

postconf -e 'home_mailbox = Maildir/'

postconf -e 'mailbox_command ='

/etc/init.d/postfix restart

*Please note:
You do not have to do this if you intend to use ISPConfig
on your system as ISPConfig does the necessary configuration using procmail
recipes. But please go sure to enable Maildir
under Management -> Server -> Settings -> EMail in
the ISPConfig web interface.

13 Apache/PHP5

Now we install Apache:

apt-get install apache2 apache2-doc apache2-mpm-prefork
apache2-utils libexpat1 ssl-cert

Next we install PHP5:

apt-get install libapache2-mod-php5 php5 php5-common
php5-curl php5-dev php5-gd php5-idn php-pear php5-imagick php5-imap php5-json
php5-mcrypt php5-memcache php5-mhash php5-ming php5-mysql php5-ps php5-pspell
php5-recode php5-snmp php5-sqlite php5-tidy php5-xmlrpc php5-xsl

You will be asked the following question:

Continue installing libc-client without Maildir support? <-- Yes

Next we edit /etc/apache2/mods-available/dir.conf:

gedit /etc/apache2/mods-available/dir.conf

and change the DirectoryIndex
line:

<IfModule mod_dir.c>

          #DirectoryIndex index.html index.cgi index.pl index.php index.xhtml

          DirectoryIndex index.html index.htm index.shtml index.cgi index.php index.php3 index.pl index.xhtml

</IfModule>

Edit /etc/apache2/ports.conf
and add Listen 443:

gedit /etc/apache2/ports.conf

Listen 80

Listen 443

Now we have to enable some Apache modules (SSL, rewrite, suexec,
and include):

a2enmod ssl

a2enmod rewrite

a2enmod suexec

a2enmod include

Reload the Apache configuration:

/etc/init.d/apache2 force-reload

13.1 Disable PHP Globally

(If you do not plan to install ISPConfig on
this server, please skip this section!)

In ISPConfig you will configure PHP on a
per-website basis, i.e. you can specify which website can run PHP scripts and
which one cannot. This can only work if PHP is disabled globally because
otherwise all websites would be able to run PHP scripts, no matter what you
specify in ISPConfig.

To disable PHP globally, we edit /etc/mime.types
and comment out the application/x-httpd-php lines:

gedit /etc/mime.types

[...]

#application/x-httpd-php                                phtml pht php

#application/x-httpd-php-source                 phps

#application/x-httpd-php3                       php3

#application/x-httpd-php3-preprocessed          php3p

#application/x-httpd-php4                       php4

[...]

Edit /etc/apache2/mods-enabled/php5.conf
and comment out the following lines:

gedit /etc/apache2/mods-enabled/php5.conf

<IfModule mod_php5.c>

#  AddType application/x-httpd-php .php .phtml .php3

#  AddType application/x-httpd-php-source .phps

</IfModule>

Then restart Apache:

/etc/init.d/apache2 restart

14 Proftpd

In order to install Proftpd, run

apt-get install proftpd ucf

You will be asked a question:

Run proftpd from inetd or standalone? <--
standalone

Then open /etc/proftpd/proftpd.conf
and change UseIPv6 from on to
off;
otherwise you'll get a warning like this when you start Proftpd:

- IPv6 getaddrinfo 'server1.example.com' error: Name or sergeditce
not known

gedit /etc/proftpd/proftpd.conf

[...]

UseIPv6                         off

[...]

For security reasons you can also add the
following lines to /etc/proftpd/proftpd.conf
(thanks to Reinaldo Carvalho; more information can be found here: http://proftpd.org/localsite/Userguide/linked/userguide.html):

gedit /etc/proftpd/proftpd.conf

[...]

DefaultRoot ~

IdentLookups off

ServerIdent on "FTP Server ready."

[...]

ISPConfig expects the configuration to be in
/etc/proftpd.conf
instead of /etc/proftpd/proftpd.conf, therefore we create a
symlink (you can skip this command if you don't want to install ISPConfig):

ln -s /etc/proftpd/proftpd.conf /etc/proftpd.conf

Then restart Proftpd:

/etc/init.d/proftpd restart

15 Webalizer

To install webalizer,
just run

apt-get install webalizer

16 Synchronize the System Clock

It is a good idea to synchronize the system
clock with an NTP (network
time protocol) server over the internet.
Simply run

apt-get install ntp ntpdate

and your system time will always be in sync.

17 Install Some Perl Modules Needed By SpamAssassin (Comes With
ISPConfig)

Run

apt-get install libhtml-parser-perl libdb-file-lock-perl
libnet-dns-perl

18 ISPConfig

The configuration of the server is now
finished, and if you wish you can now install ISPConfig
on it. Please check out the ISPConfig installation manual: http://www.ispconfig.org/manual_installation.htm

18.1 A Note On SuExec

If you want to run CGI scripts under suExec,
you should specify /var/www as the home directory for
websites created by ISPConfig as Ubuntu's suExec is compiled with /var/www as
Doc_Root.
Run

/usr/lib/apache2/suexec -V

and the output should look like this:

root@server1:~# /usr/lib/apache2/suexec -V

-D AP_DOC_ROOT="/var/www"

-D AP_GID_MIN=100

-D AP_HTTPD_USER="www-data"

-D AP_LOG_EXEC="/var/log/apache2/suexec.log"

-D AP_SAFE_PATH="/usr/local/bin:/usr/bin:/bin"

-D AP_UID_MIN=100

-D AP_USERDIR_SUFFIX="public_html"

Unless you install ISPConfig in expert mode and change the default web root
(which is /var/www), you will be able to run CGI scripts under
suExec with ISPConfig. The following screenshot is taken from an ISPConfig
installation in expert mode. If you want to use ISPConfig, then don't change
the default web root:

Optimize the Mythtv Mysql Database

2007-06-29T09:22:00.000-07:00

In the contrib directory there is a Perl script, optimize_mythdb.pl to run MYSQL utilities Repair and Optimize on each table in your MythTV database. It is recommended to run it daily from a cron job.

First make sure it is executable:

chmod 755 /usr/share/doc/mythtv-0.20/contrib/optimize_mythdb.pl

Create a shell script to run daily:

###### optimize_mythdb.sh
#!/bin/sh

OPT_MYTHDB='/usr/share/doc/mythtv-0.20/contrib/optimize_mythdb.pl'
LOG='/var/log/mythtv/optimize_mythdb.log'

echo "Started ${OPT_MYTHDB} on `date`" >> ${LOG}
${OPT_MYTHDB} >> ${LOG}
echo "Finished ${OPT_MYTHDB} on `date`" >> ${LOG}

run with your daily cron jobs

Linux server: Printerinstallering og deling

2007-06-19T08:07:00.000-07:00

Tilføj printer

1. Gå til System-> Administration-> Printere>- "add new printer.
2. Nu skal man specificere om printeren er tilslutte som lokal via USB eller via netværk. I dette tilfælde er den USB.
3. Vælge printermodel-> Ok.

Share lokal printer

gksudo gedit /etc/cups/printers.conf

Ændre til

shared yes

Genstart CUPS:

sudo /etc/init.d/cupsus restart

Dele med Windoze

Hvis man har printere som man ønsker at dele med Windoze computere via Samba så gør man følgende:

sudo cupsaddsmb -a

..deler alle printere

For at dele en specifik printer henviser man til dens CUPS navn:

sudo cupsaddsmb hp950

Ændre stier og rettigheder i Mythtv

2007-06-19T07:11:00.000-07:00

Har man sat en ekstra harddisk til mediafiler i sin mythbox skal man sørge for at ændre stier og rettigheder.

Default lægges alt i /var/lib/mythtv/.....osv. Mit nye drev hedder nu hdb5 og mountes automatisk som /media. Skriv fdisk -l for at liste drev

Start med at oprette 4 mapper på hdb5:

1. recordings
2. videos
3. pictures
4. music

Så ændres stier i Mythbackend-programmet:

Under "Generelt"-> mappen hvor optagelserne gemmes" skal stå:

/media/hdb5/recordings

Start nu Frontenden:

Gå til "Konfiguration"-> "Konfiguration"-> "Media"-> "Musik instillinger"-> "Generelle":
Under "Bibliotek der indeholder musik" skal stå:

/media/hdb5/music

Tryk Esc 2 gange tilbage-> Vælg nu "Video indstillinger"-> "Generelle"->
Skriv her:

/media/hdb5/videos

Samme procedure for "Billed instillinger". Her skal stå:

/media/hdb5/pictures

Godt så.....

Afslut Mytvfrontend og gå tilbage til desktoppen. I terminalen skrives nu for at give fuld adgang til det nye bibliotek:

chown -R mythtv.mythtv /media/hdb5/

Vent lidt - der skrives nye rettigheder til disken.

Husk til sidst at køre komandoen

mythfilldatabase

..i terminalen. Ellers bliver ændringerne ikke skrevet til mysql-databasen;-)

change the permissions and ownership of the recordings directory:

sudo chown mythtv.mythtv /media/hdb5/
sudo chmod u=rwx,g=rwx,o=rwx /media/hdb5/recordings

gentages for /videos, /music og /pictures

(This assumes that your directory for recordings is /var/lib/mythtv. If you have the recordings stored somewhere else, be sure to replace /var/lib/mythtv in the above command with that location.)

The end result is that the ownership and permissions should match /var/lib/mythtv as it was set by the installer. (You might want to replace /var/lib/mythtv with a symbolic link to your custom location if you are using a customized location.)

Tilføj et Sony Ericsson HBH-610 Bluetooth headset til mobil

2007-06-19T04:18:00.000-07:00

1. Check batteristatus: Hold +/-tasterne nede samtidigt.

Et blink: Tom
To blink: Halvfyldt
Tre blink: Fuldopladet

2. Opladetid: 2 timer

3. Reset: Hold +/- nede og se efter 3 blink

4. Parring: Hold "call handling" knappen nede i 5 sekunder mens mobilen forbinder. Check at lampen blinker rød/grøn.

5. Passkey er 0000

6. Tænde headset: Hold "call" knap nede og se efter 3 blink

Koncepter for Improvisation

2007-06-18T05:25:00.000-07:00

MAJOR 7

MAJOR

Durskala & Arpeggio
Treklange fra 1, 4 & 5
Mol-pentaton fra 2, 3 & 6

LYDIAN

Lydisk skala
Major 5th arpeggio en kvint op.
Min7b5 arppegio en b5 op
Treklange på 2 ,.....(?)
minor-pentatonic fra Maj7

LYDIAN #5

Melodisk mol en b3 ned
Mel. min. arpeggio en b3 ned
Treklang fra 3

Giv Mythtv en fast IP-adresse

2007-06-17T11:57:00.000-07:00

The interface can be configured in

gksudo gedít /etc/network/interfaces

to use staticIP, so it will not attempt a DHCP broadcast on startup. The syntax is something like:

auto eth0
iface eth0 inet static
address 192.168.1.110
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.1

A 'man interfaces' will provide more information.

Start Mythfrontend automatisk efter logon

2007-06-17T10:08:00.000-07:00

The most popular method out there in the other HOWTOS seems to be to use the .xsession file to start up mythfrontend when the mythtv user logs in. My problem with that procedure is that the normal window manager doesn't even appear to start up, so it's difficult to fire up a quick terminal and do anything while myth is running; I find that annoying.

I think that it's better to go to System->Preferences->Sessions, and select the "Startup Programs" tab . In there, put all of the following:

mythfrontend
mythfrontend

From now on, if you log in as the mythtv user, you will be immediately greeted by the friendly MythTV interface. And sorry about mixing in other things that belong in a different topic. The "xset" commands are there to make sure that the screen doesn't blank after an amount of time, which would be incredibly annoying while watching TV. The "irexec" command allows us to map remote keys to various functions as we need, outside of MythTV. I'll use this later for power button functionality.

Automatically login the mythtv user at boot

2007-06-17T10:07:00.000-07:00

When you boot your machine, it would be nice if it would go straight to MythTV; however, at this point, it boots to the graphical login screen. This is easy to fix; just edit

gksudo gedit /etc/gdm/gdm.conf

change the AutomaticLoginEnable and AutomaticLogin variables to:

AutomaticLoginEnable=true
AutomaticLogin=mythtv

Configure the power button on the remote

2007-06-17T10:04:00.000-07:00

For this, all you have to do is download a couple of scripts that I have written and/or modified, and put them both in your /usr/local/bin/directory:

cd /usr/local/bin
wget http://s91928265.onlinehome.us/hfamily/mythtv/mbe.keepup.sh
wget http://s91928265.onlinehome.us/hfamily/mythtv/mythpowerbutton.sh
chmod a+rx mbe.keepup.sh
chmod a+rx mythpowerbutton.sh

As long as you used my lircrc-haupgrey.txt file (in the LIRC step), the mappings are already there for the power button to work immediately. This script will kill the frontend if it is running (and leave the backend alone), or, if the frontend is not running, it will start both the backend (if necessary) and the frontend. Note that for this to work, you should have placed "irexec" in the auto-run section in System->Preferences->Sessions for the mythtv user (done in a previous step).

Automatically back up the MythTV database daily

2007-06-17T10:03:00.000-07:00

If you ever lose your MythTV database, you will be very sad; it contains all MythTV settings, as well as records of every program that you have watched, the programs you have recorded, etc. etc. Backing up is easy to do, especially since I have a small script that will do it for you.

cd /usr/local/bin
wget http://s91928265.onlinehome.us/hfamily/mythtv/backup.database.shchmod a+rx backup.database.sh

Now, etc /etc/crontab and add in the following line:

30 12 * * * mythtv /usr/local/bin/backup.database.sh /scratch/dbbackup >& /dev/null

Making sure the mythbackend stays up

2007-06-17T09:59:00.000-07:00

OK, I'll admit that I'm a little overboard on not wanting to miss any recordings. I run a script every three minutes to make sure that the backend is still up, and restart it if it is not. You already have this script if you already did the "Configure the power button on the remote" step above, but just in case, we will re-fetch the required script:

cd /usr/local/bin
wget http://s91928265.onlinehome.us/hfamily/mythtv/mbe.keepup.shchmod a+rx mbe.keepup.sh

And now, add the following line to your /etc/crontab:

*/3 * * * * mythtv /usr/local/bin/mbe.keepup.sh cron >& /dev/null

Automatically login the mythtv user at boot

2007-06-17T08:50:00.000-07:00

When you boot your machine, it would be nice if it would go straight to MythTV; however, at this point, it boots to the graphical login screen. This is easy to fix; just edit /etc/gdm/gdm.conf,

gksudo gedit /etc/gdm/gdm.conf

change the AutomaticLoginEnable and AutomaticLogin variables to:

AutomaticLoginEnable=true
AutomaticLogin=mythtv

Linux er for sindsygt....

2007-06-17T01:21:00.000-07:00

...svært nogle gange. Tag f.eks. GUI'en til Samba kaldet Swat. Swat installeres fint via Synaptic, men kører ikke default via http://localhost:901/, som manualen beskriver.

Efter at have prøvet alle krumspring finder jeg efter 2 timers søgen jeg - langt nede i "dybet" - på Ubuntuforums dette:

I installed both Samba and Swat. Samba appears to be working, but I can't launch Swat. When I try http://127.0.0.1:901/ I get "the connection was refused when attempting to contact 127.0.0.1". Now I do not know how to launch Swat. Anyone?

Have you tried this ?
sudo update-inetd --enable 'swat'

inetd doesn't work initally in Ubuntu, you need to get 'netkit-inetd' with either snaptic or apt-get, whichever you prefer.

Jeg hentede netkit-inetd og nu virker Swat. Burde dette ikke være installeret pr. default?

Lidt senere finder jeg dette: http://www.jonhoweonline.com/blog/node/87

Find en fil og list den

2007-06-17T00:26:00.000-07:00

find / -name swat -print

Finder her alle filer med navnet "swat" og skriver til skærmen

Bruge VNS viewer fra Ubuntu

2007-06-16T08:54:00.000-07:00

Open your terminal from Applications—>Accessories—>Terminal and enter the following command

vncviewer -fullscreen 192.168.1.10 (eller hvad klientens ip er)

If you want to quit vncviewer

Press ‘F8′ and select Quit viewer

Sæt hastigheden på CPU'en op og ned efter belastning

2007-06-16T07:45:00.000-07:00

PS: Kun for CPU'er som understøtter Dynamic Frequency Scaling.

I terminalen:

sudo chmod +s /usr/bin/cpufreq-selector

Derefter:

Højreklik Gnome's top panel og vælg "tilføj til panel". Bladre ned og vælge "CPU frekvensskalering"

Køre Netbank på Ubuntu med Internet Explorer

2007-06-16T04:37:00.001-07:00

sudo gedit /etc/apt/sources.list

Tilføj:

deb http://de.archive.ubuntu.com/ubuntu feisty universe
deb http://wine.budgetdedicated.com/apt edgy main

kør

sudo apt-get update

Installere wine og cabextract

Kør:

sudo apt-get install wine cabextract

Svar ja til alle [y/N]

Installere IEs4Linux

For at insrallere IEs4Linux, gør man følgende:

cd ~
wget http://www.tatanka.com.br/ies4linux/downloads/ies4linux-latest.tar.gz
tar zxvf ies4linux-latest.tar.gz
cd ies4linux-*
./ies4linux

Man blivver stillet nogle spørgsmål. Svar JA til alle.

Danske Bank specifik indstilling

For at få f.eks. Danske Bank til at spille:

Gå til "Funktioner> Internetindstillinger

Delete files> Delete all offline content> OK
Gå til "Secuirity> Trusted sites> Sites
Fjern hak i "Require....."
Tilføj *.danskebank.dk
Sæt hak igen og tryk OK

Mythtv Speed Tips

2007-06-15T09:47:00.000-07:00

If a process is run with elevated privileges, it's possible to realize some performance gains. If you configure your system in just the right way, you can run the mythfrontend process at a higher processing priority than standard user processes get. This can be useful if your system is completely taxed during playback, which is usually the case when playing back high-definition recordings (unless you have a really fast processor, such as a 3.6GHz Pentium 4 or better). On some systems, altering your mythfrontend binary to run as set-uid root is sufficient:

# chmod u+s /usr/bin/mythfrontend

However, recent changes to the 2.6 Linux kernel have made that method obsolete, and favor another solution. For the latest kernels, you must run PAM 0.79 or later (PAM is an acronym for pluggable authentication modules), and then make a few changes to /etc/security/limits.conf. Assuming you're running mythfrontend as user mythtv, add the following to limits.conf:


Mythtv     -      rtprio       50
Mythtv     -      nice         0

These changes aren't dynamic, so you'll need to log out and log back in to have those changes applied to your mythtv user account.

Using either or both of the preceding privilege escalation methods, launch mythfrontend from a console window, navigate to Utilities>Setup>TV Settings>Playback, and check the box for "Enable realtime priority threads" (see Figure 1). Then work your way through the rest of the settings pages. At that point, you should be able to watch a recording with real-time priority enabled. Briefly start watching either a recording or live TV, and then exit out of mythfrontend. On the console from which you launched mythfrontend, you should see a message that looks something like the following:

2006-01-29 11:27:34.264 Using realtime priority.

If you haven't configured everything just right, you'll see the following instead:

2006-01-29 11:28:07.004 Realtime priority would require SUID as root.

Retrace your steps if you run into this error. If one privilege escalation method fails, try the other, or try enabling both at the same time, which should more or less guarantee success. Make sure you're running the latest PAM available for your system and be sure to completely log out and log back in (or even try a reboot, if you feel the urge)

Ubuntu Home filserver med Samba og printserver med CUPS

2007-06-15T07:24:00.000-07:00

Her er min opskrift på en Linuxserver under Ubuntu med fuld desktop. Primær funktion er at dele printere via Samba og CUPS samt fildeling mellem Windoze og Linux computere.

Serveren arbejder som Home server uden DC (domain Controller) så alle har nem adgang til foldere og drev.

Aktivere root bruger passwd for at lette installationen:

sudo passwd root
su

Editere /etc/network/interfaces og sæt en fast IP:

gksudo gedit /etc/network/interfaces

Tilføj:

auto lo
iface lo inet loopback
# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map eth0
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1

Genstart netværket:

/etc/init.d/networking restart

Editere /etc/hosts and tilføj den nye IP:

gksudo gedit /etc/hosts

Tilføj:

127.0.0.1 localhost.localdomain localhost
192.168.1.10 server1.example.com server1

Sæt Hostname

echo server1 > /etc/hostname
/bin/hostname -F /etc/hostname

Sæt Resolve

nano /etc/resolv.conf

Indsæt:

search peterlund.org
domain peterlund.org

nameserver 192.168.1.1
nameserver 212.242.40.3
nameserver 212.242.40.51

Editere /etc/apt/sources.list og opdatere installationen:

gksudo gedit /etc/apt/sources.list

Tilføje:

deb http://de.archive.ubuntu.com/ubuntu/ feisty main restricteddeb-src http://de.archive.ubuntu.com/ubuntu/ feisty main restricted deb

http://de.archive.ubuntu.com/ubuntu/ feisty-updates main restricteddeb-src http://de.archive.ubuntu.com/ubuntu/ feisty-updates main restricted deb

http://de.archive.ubuntu.com/ubuntu/ feisty universedeb-src http://de.archive.ubuntu.com/ubuntu/ feisty universe deb

http://de.archive.ubuntu.com/ubuntu/ feisty multiversedeb-src http://de.archive.ubuntu.com/ubuntu/ feisty multiverse

http://de.archive.ubuntu.com/ubuntu/ feisty-backports main restricted universe multiverse
deb-src http://de.archive.ubuntu.com/ubuntu/ feisty-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu feisty-security main restricteddeb-src http://security.ubuntu.com/ubuntu feisty-security main restricteddeb

http://security.ubuntu.com/ubuntu feisty-security universedeb-src http://security.ubuntu.com/ubuntu feisty-security universedeb

http://security.ubuntu.com/ubuntu feisty-security multiverse
deb-src http://security.ubuntu.com/ubuntu feisty-security multiverse

Kør:

apt-get update
apt-get upgrade

Install SSH Daemon:

apt-get install ssh openssh-server

Log ind med Putty på 192.168.1.10 og forsæt resten af installationen herfra.

Sætte quota:

apt-get install quota

Edit /etc/fstab så det ser ud som herunder (Jeg tilføjede, usrquota, grpquota til de partitioner som har mount mount point)

gksudo gedit /etc/fstab

Indsæt:

# /etc/fstab: static file system information.
#
#
proc /proc proc defaults 0 0
# /dev/sda1
UUID=226d9304-88ca-44c0-a3e3-d1ad26cfc084 / ext3 defaults,errors=remount-
ro,usrquota,grpquota 0 1
# /dev/sda5
UUID=d824ce36-04b8-4870-83f4-f1a5037c2de4 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0

Kør:

touch /quota.user /quota.group
chmod 600 /quota.*
mount -o remount /
quotacheck -avugm
quotaon –avug

Man ser på et tidspunkt en fejl som der her når man kører quotacheck -avugm første gang:

quotacheck: WARNING - Quotafile //quota.user was probably truncated. Cannot save quota
settings...
quotacheck: WARNING - Quotafile //quota.group was probably truncated. Cannot save quota
settings...

Det er normalt, så bare gå videre:

Installere Samba og Swat

apt-get install samba swat samba-common samba-doc libcupsys2-gnutls10 libkrb53 winbind smbclient netkit-inetd

Konfigurere Swat

For at konfigurer systemet for at køre Swat er der two filer der skal ændres:

/etc/services
/etc/inetd.conf

I /etc/services skal tilføjes:

swat 901/tcp

Med hensyn til /etc/inetd.conf er det en catch. For at virke skal den pege på det rigtige /swat-bibliotek.

Kør komandoen:

which swat

Hvis svaret er:

/usr/sbin/swat

..så retter man /etc/inetd.conf så stien ser således ud:

#Samba Web Administration Tool:
#swat           stream  tcp     nowait.400 root /usr/sbin/swat  swat

Før man kan logge ind i Swat skal man tilføje root brugeren til samba password databasen.

I terminalen:

smbpasswd -a root

Username: root
Password: "Et_eller_andet_password"

Hvis paswordet allerede er genereretr køres istedet:

smbpasswd -e root

..for at enable brugeren.

Start Swat op

For at start Swat op tænder man sin favorit browser op at lader den pege på:

http://localhost:901/

Konfigurere Samba med Swat

Under punktet kaldet "Global" tilføjes:

workgroup
Server1
lo, eth0
workgroup
server1
lo, eth0
host allow = 192.168.1.10, 127.0.0.1

Samba konfiguration

gksudo gedit /etc/samba/smb.conf

Creating the global section

Quote:

[global]
netbios name = server1
server string = Samba Server
workgroup = workgroup
security = user
encrypt passwords = yes
smb passwd file = /var/lib/samba/private/smbpasswd
log file = /var/log/samba/%m.log
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
wins support = yes
hostname lookups = yes
hosts equiv = /etc/hosts
hosts allow = 192.168. localhost
hosts deny = All
interfaces = lo eth0
bind interfaces only = yes
guest ok = yes
browse list = yes
printcap name = cups
printing = cups
load printers = yes

These fields will be explained below:
netbios name: This field should be filled in with the name of your server, this is what your windows computer will refer to the server as.

server string: This field is not really required, but it is handy incase you don't remember what you called your computer e.g. like me :P

workgroup: This field tells the server which Workgroup it belongs to. This field is absolutely essential.

security: This field refers to the level of security which should be present. There are two levels of security which I feel is within the scope of this howto to explain:
1. Share level security: Anyone can access any share without entering a username and password, i.e. no security.
2. User level security. If someone wants to access a share on the server, they need to enter a valid username and password.

A valid username is any user who has an account on your server.

To add a user, use the useradd command. A valid user needs a valid password, but to be able to use the share, they need a valid samba password. To add a samba password for a user, just execute this command:

Code:

# smbpasswd -a user_name

Personally I recommend you use user level security. However, if you feel the need to use share level security, by all means do so, but for making sure everything works, set it to user level security. This is because the command which tests whether the Smaba server works requires user level security to work. Once the server is up and running, you can set it back to share level security.

encrypt passwords: Sounds pretty obvious doesn't it, I don't want other people knowing my passwords easily, so they should be encrypted.

smb passwd file: The file where the samba passwords should be stored. You can use a whereis or a find to find the proper location of your smbpasswd file.

log file: The file where the server should create the logs for each machine the %m you see there will actually be replaced with the name of the machine.

socket options: These are supposed to improve the sending and recieving of data.

wins support: One of my W2K box refuses to see the Samba server without this option enabled. This option just causes the Samba server to act as a WINS server. Because this option is enabled, you should set the WINS server option in your Windows clients to the IP address of the Samba server.

hostname lookups: This field just asks whether the server should perform lookups based on the hostname of the client computers. If you set this field, you beed a hosts equiv field to tell the server the equivalent ip's of the other computers.

hosts equiv: This field just tells the server the loacation of the file which translates a IP address to a hostname.

hosts allow / hosts deny: These fields set which hosts can access the server based on their IP address or hostnames. In the example hosts allow field, I have told it to allow any computer with an IP address in the range 192.168.0.1 to 192.168.0.255 on the subnet 255.255.255.0 to have access to the server, localhost should also be included so that we can test to see wether the server works.
The hosts deny entry is set to All as I don't want anyone else accessing the shares.

interfaces: This field is only required if you have multiple network cards/connections. (Yes the Internet is a type of connection). This field should be set with the names of the interface/s that the Samba server should listen to for requests. Valid interface names on your system can be found by using the /sbin/ifconfig command.

bind interfaces only: This field tells the server only to listen to the interfaces listed in the "interfaces" field.

guest ok: allow guests to see the server, and some limited browsing. Usually should be set to no.

printcap name / printing: The type of printing system we are going to use.

load printers: Well we do want the system to load the printers automatically so that clients can use it, don't we?

Ch 1.2 Setting up shares

Shares on the server are what other people can see and access.

1.2.1 Setting up file shares:
A basic file share should have the name of the share and any other relevant details, below is an example of a public file share which everybody can access.
[public] <------- This is the name of the share path = /home/samba/public comment = Shared folders guest ok = yes create mode = 0766 browseable = yes public = yes read only = no this share allows everybody to access the shared folder on the server under /home/samba/server. To create such a share with relevant permissions, execute these commands:

Code:

# mkdir /home/samba/public
# chmod -R 777 /home/samba/public

Now some people may want to access their own files from any computer connected to the network and prevent others from accessing it. In such a case, create a share like the following:

[home_directories]
comment = User's home directory
path = /home/%U
read only = no
valid users = %U root <--- We only want the legimitate user and root to be able to access the share Note for sharing home directories with password protections, you obviously have to set the security level to user in the global section. File shares can be set to things like removeable media such as cd/dvd drives and usb drives, all you have to do is tell the server the correct path to the resource e.g. /mnt/usb 1.2.2 Setting up Print shares We are now going to setup the Print share

Quote:

[printers]
comment = All Printers
browseable = no
printable = yes
writable = no
public = yes
guest ok = yes
path = /var/spool/samba
printer admin = root

This section is like a "global" setting for printer, we are allowing guests to be able to print from it and only allow root to administer it.

The next section just defines which printer to share, if you have multiple printers connected to your computer, just create more of the printer shares outlined below:

Quote:

[HP5160] <--- The name I will be referring to my printer from now on comment = HP Deskjet 5160 printable = yes path = /var/spool/samba public = yes guest ok = yes printer admin = root

Once all that is done, save the file and perhaps create a backup of it. Now we will test the server.

Ch 1.3 Testing the Samba Server
There is a command called testparm which will parse the smb.conf file and see if you have made any errors. To run it, just do:

Code:

# testparm
// if /usr isn't in your path, you may have to run the following command:
# /usr/bin/testparm

Now we have to see if the samba service is running, to do that, use the following commands:

Code:

# ps -e  grep smbd
# ps -e  grep nmbd

If samba has not started, run the following command:

Code:

# /etc/init.d/samba start

Now we see if the services are running and the shares can be accessed by using the smbclient command.

Code:

# smbclient -L localhost

It will prompt you for the present user's samba password.

If the present user doesn't have a valid samba password, simply execute this command:

Code:

# smbpasswd -a user_name

Note, the execution of the smbclient command results in the most errors, most noteably a NT_STATUS_LOGON FAILURE error. A few things you can do to fix this:
1. Check that the smb.conf file has you in the correct workgroup
2. Check your samba passwords and which password file it uses.

Also, if you make any changes to the smb.conf file, you need to restart the samba service by executing this command:

Code:

# /etc/init.d/samba restart
// alternatively, you can do this
# /etc/init.d/samba stop
# /etc/init.d/samba start

Ch 1.4 Client Configuration
For all Windows clients you need to do the following:
1. Set the workgroup to the correct workgroup set in the smb.conf file
2. Under the Advanced TCP/IP settings for the adapter, there will be an entry for WINS server, set this to the IP address of the Samba server.
3. If you have a firewall e.g. Norton or Zone Alarm running, tell it to allow communication from the Samba server, normally, you just tell it the IP address of the server and set it to "Allow".
4. Sometimes you may need a restart for things to work :P

Linux clients:
To access Windows shares or SMB shares on the Samba server, you need to execute following command as root:

Code:

# mount -t smbfs -o username=YOUR_USERNAME,password=YOUR_SHARE_PASSWORD //Server_name/share /mount_point

Alternatively you can write up the entry in your /etc/fstab file like so:

Quote:

//Server_name/Share /mount_point smbfs username=YOUR_USERNAME,password=YOUR_SHARE_PASSWOR D,rw,users,umask=000 0 0

YOUR_SHARE_PASSWORD is the password you have assigned to that share, if it is a windows share, use your windows password.

Since you have mounted windows shares in linux through Samba, you can now write to those partitions even NTFS based ones.

Note: for the above commands to work, you need the correct entries in the /etc/hosts file as shown below:

Quote:

// Server's IP address Hostname
192.168.0.1 My_Samba_Server

Ch 2. Setting up CUPS
CUPS is the Common Unix Printing System, we shall use this on our server to share the printer with clients. Note, here I am assuming that the printer will be connected to the Samba Server by means of either a USB or Parallel cable and not through the network.

Ch 2.1 Editing cupsd.conf
Now, like samba, cups has a configuration file, namely cupsd.conf. We shall edit the defalt cupsd.conf file as it would be difficult to start with a clean file, also there is plenty of documentation in the cupsd.conf file and if you feel brave enough, by all means enable some settings and whatnot. Below, I will show you how to edit the cupsd.conf file to get the basics running.

Firstly open the cupsd.conf file with your favourite editor:

Code:

# nano -w /etc/cups/cupsd.conf

the cupsd.conf file is fairly large, I'd suggest you edit the sections below first to get the server working, then play around with it.

Quote:

ServerName Name_of_Print_Server
ServerAdmin root@Name_of_Print_Server
.
.
MaxCopies 10 // I don't want someone accidentally wasting paper and ink on a job
.
.
MaxClients 5 // Set this to whatever you like I don't want more than 5 connections to my server
.
.
BrowseAddress @IF(eth0) // change eth0 to your lan connection, just tells where to send printing updates to
.
BrowseAllow @IF(eth0) // only allow printing from LAN.
BrowseDeny All // I don't want people on internet to try print using my printer
BrowseOrder deny,allow // We first stop everyone from printing, then allow only local printing.
.
.

Order Deny,Allow
Deny From All
Allow From 127.0.0.1 192.168.0.* // Change 192.168.0.* to address of internal network

.
.

AuthType Basic
AuthClass System
Order Deny,Allow
Deny From All
Allow From 127.0.0.1 // Only the users sitting at the print server can perform admin

Now, I know that at some point people are going to print MS Office Documents, if the following lines aren't uncommented, then you are going to get some screwed up prints. Trust me, I learned the hard way...

In /etc/cups/mime.convs file, uncomment the following line, it is towards the end.

Quote:

# application/octet-stream application/vnd.cups-raw 0

i.e. remove the # sign at begining of line.

Similarly, uncomment the following line in /etc/cups/mime.types:

Quote:

# application/octet-stream

Now, before proceeding further, we need to start cups with:

Code:

# /etc/init.d/cupsd start

Ch 2.1 Installing the Drivers
Installing the Linux drivers:
Firstly, goto the linuxprinting.org site and get the correct CUPS driver for your printer. (link). Download the ppd file and place it in /usr/share/cups/model.

There are 2 ways of installing the Linux driver, firstly using the command line, as root do the following:

Code:

# lpadmin -p Printer_name_used_in_Samba -E -v usb:/dev/usb/ltp0 -m Some_printer_name.ppd

The field Printer_name_used_in_Samba should be replaced with whatever you have shared your printer as. In the example smb.conf file given in Ch 1, I shared my printer as HP5160.

The field usb:/dev/usb/ltp0 is what the system refers to as the location of your printer, note this filed will vary across different systems. On some systems, when using usb printers, it could be at /dev/ultp0. If you have a parallel printer, replace usb with parallel:/dev/lpt0 or similar.

The field Some_printer_name.ppd is the name of the printer driver you have downloaded. For example, the HP Deskjet 5160 printer has a ppd file with the name HP-DeskJet_5160-hpijs.ppd.

If that method doesn't work, you can use the CUPS web interface to setup the printer. Simply launch your favourite web browser and point it to http://name_of_print_server:631/ or http://localhost:631/ . Simply point it to the location of the printer, setup its share name and tell it the correct driver to use. Note, you would need to login to this admin webpage with username as root and with your root password. Note this is your root system password and not the samba password.

Installing Windows Drivers:
You can install the drivers in one of two ways. You can either have the driver files installed on to the CUPS server, then when you add a printer on the client, it will go to that directory and fetch the drivers. Or you can install the driver as normal on each client and point it to the shared printer on the CUPS server (Note, with this method, I couldn't get it to work using HP's own drivers and had to use Adobe's drivers).

Firstly, I will explain how to set it up so that the drivers reside on the server.

At the time of writing of this howto, the CUPS Windows drivers are still under developement and hence won't be used here. Instead you have two options, either to use the Windows or Adobe Postscript drivers. Note If you have Windows clients which are pre Win 2K, you will need to use the Adobe Drivers.

Using Windows Postscript drivers
1. Make a directory in /usr/local/share/cups called "drivers"
2. Now on your windows machine, Navigate to the C:\Windows\System32\Spool\Drivers\W32X86\3 folder. Copy whatever files in this folder to a flash drive, or if your samba server is working, copy it to a share on the server.
3. Now copy whatever files which are in this directory to /usr/local/share/cups/drivers

Using Adobe Postscript drivers
1. Make a directory in /usr/share/cups called "drivers"
2. Grab yourself a copy of the Adobe postscript drivers for your language from here. Also, get a ppd file for your printer.
3. Launch the adobe Installer and tell it to use the ppd for your printer, now the drivers will be extracted to C:\Windows\System32\Spool\Drivers folder. Copy these files to usb or a samba share on your server.
4. Copy the extracted driver files from a usb drive or samba server to /usr/local/share/cups/drivers.

Now, because we are setting it up so that the server will contain the drivers, we need add some things to the smb.conf file regarding the location of the drivers. Note the configuration below must be used for all printers

Quote:

[print$]
comment = Printer Drivers
path = /etc/samba/printer # this path holds the driver structure after cupsaddsmb command
guest ok = yes
browseable = yes
read only = yes
write list = root

Once that has been added, restart your samba serveice i.e:

Code:

/etc/init.d/samba restart

Now, to add the drivers to samba to be shared to all clients, we execute this command:

Code:

cupsaddsmb -H Name_of_Samba_Server -U root -h Name_of_Print_Server -a

In most cases, Name_of_Samba_Server and Name_of_Print_Server are the same.

The 2nd method of installing the drivers would i.e so that drivers are on client systems is like so:
Using the printer driver which came with your printer, tell it to install as a network printer and point it to the printer which resides on the Samba server. Note, for some reason this method didn't work for me and I had to use the Adobe method outlined below:

Grab yourself a copy of the Adobe postscript drivers for your language from here. Also, get a ppd file for your printer. Run the Adobe installer, point it to the location of the printer on the samba server. Now Under printing in the Control Panel, tell it to use this as default printer.

Ch 2.2 Client Configuration for CUPS
Windows Client configuration:
If you set it up so that driver files reside on the server, in explorer, simply navigate to the shared printer, right click on it and say "Connect", the drivers will be downloaded and you can start using it.

Otherwise simply go to the Add printer wizard in Control Panel and point it to the location of the Printer on the server. You may also want to set it as your default printer.

Linux Client Configuration (Other than the server):
Install a CUPS client on your system, usually by installing the CUPS server package, a CUPS client will also be installed. Now edit the /etc/cups/client.conf file and add the following:

Quote:

ServerName Name_of_Print_Server

And that is all there is to it. Now you should have a working file and print server.

If you want a more detailed version of the printing howto in Samba, see Kurt Pfeifle's "Printing Support in Samba 3.0 manual"

If you want more examples for setting up different configurations of a samba server, be sure to check out the official Samba by Example guide

Installing CUPS

apt-get install cupsys cupsys-client cupsys-driver-gimpprint defoma fontconfig foomatic-db foomatic-filters libcupsimage2 libexpat1 libfontconfig1 libfreetype6 libjpeg62 libpaper1 libpng12-0 libslp1 libtiff4 patch perl perl-modules ttf-bitstream-vera ucf

To get access to the web interface from my workstation (IP 192.168.0.70), I will change cups to listen on the server IP and allow access from the IP 192.168.0.70. You will have to change this IP to suit into your network configuration.

Referencer

http://www.extremetech.com/article2/0,1697,1047877,00.asp

Komplet HTPC med Mythtv på Ubuntu og PVR-250

2007-05-29T00:52:00.000-07:00

1. Installere Ubuntu
2. Opdatere systemet
3. Hente og installere programmer
4. Teste TV-modtagelse
5. Scanne TV-kanaler
6. Installere Mythtv-pakken
7. Ændre password for brugeren mythtv og tildele rettigheder
8. Hente TV-lister fra nettet med XMLTV
9. Køre mythtv-setup

Mythtv. Drømmen om den ultimative Medieserver for TV, DVD, mp3 og billeder. Jeg hader det egentligt med en stor passion. Det er en bitch hvis man ikke holder sig til en slavisk fremgangsmetode og det straffer hårdt hvis man improviserer for meget undervejs. Jeg må have re-installeret Mythtv mindst 100 gange igennem de sidste 4 år - uden at kunne sige at jeg har fået det til at virke fuldt ud. Det nøder mig dog stadigt at jeg ikke har kunnet knække nøden helt, så derfor prøver jeg endnu engang at få det til at spille, og denne gang vil jeg gå metodisk og struktureret til værks.

1. Installere Ubuntu

Hent en ISO fra http://www.ubuntu.com/getubuntu/download og lav en fuld standard desktop installation.

Vigtigt: Undlad at kalde din bruger for mythtv – det skaber bare problemer da mythtvinstallationen selv opretter en bruger med dette navn senere. Systemnavnet kan være hvad som helst – jeg vælger htpc.

2. Opdatere systemet

Før man går videre er det vigtigt at systemet er opdateret. Under Administration> Softwarekilder enabler man alle ekstra Ubuntu repositories:

main, universe, restricted og multiverse

Vælg en passende lokation at downloade fra under “source for your geographic location”.
Klik på Updates fanebladet> Vælg Important og Recommended updates> OK og quit. Hvis du får en pop-up med “Software updates available", udfør updates inden du fortsætter. Hvis ikke så gå til System> Administration> Synaptic Package Manager. Klik på Mark All Upgrades> Klik Apply.

For at have alle multimediaprogrammer og codecs inde er det smart at installere programmet Automatix, der – som navnet indikerer – gør det nemt at lave sig en multi media box.

Hent automatix: http://www.getautomatix.com/apt/dists/feisty/main/binary-i386/automatix2_1.1-4.5-7.04feisty_i386.deb

Vælge samtlige video og lyd drivers(codecs) og også gerne hvad der er af diverse medieafspillere.

3. Hente og installere programmer

De fleste ting som skal udføres under installationen skal gøres mens man er logget på som den standardbruger man oprettede under installationen. Lidt senere skal man så logge ind som mythtv bruger. For nu skal alle grundpakker ind, og her bruger vi kommandoen

Sudo – i

i terminalen for at få brugerrettigheder som root:

sudo -i apt-get install apache2 mysql-server phpmyadmin libapache2-mod-auth-mysql dvdauthor ntp ntp-simple gsfonts-x11 msttcorefonts tcsh ivtv-utils xmltv-util xmltv

Derefter for at installere ekstra fonte:

fc-cache -f –v

4. Teste TV-modtagelse

Ubuntu installerer alle drivere til mit Hauppauge PRV-250 af sig selv, så det er egentligt bare at loade driverne og teste at kortet kan ses at systemet:

Depmod
modprobe ivtv
dmesg

Gå lidt ned på listen for at se at kortet er fundet og virker OK. Fang nu et testbillede med:

cat /dev/video0 > /tmp/test.mpg

Tryk Ctrl+C for at stoppe capturing efter et minut. Afspil klippet i et vindue:

mplayer -vo xv /tmp/test.mpg

Hvis kortet virker ser man sne i vinduet.

5. Scanne TV-kanaler

TV-kanalerne skal findes og noteres sammen med de frekvenser de referer til. Først sender vi signalet fra TV-kortes udgang videre til indgangen på mplaver:

mplayer -vo xv /dev/video0

Nu åbner man et nyt terminal vindue og skriver følgende:

ivtv-tune -c23 -teurope-west -d /dev/video0

Parameteren –c er kanalnummeret. Start med at indsætte –c1 og gå frem til 60 eller hvor signalområdet nu ender. PS: Læg mærke til frekvensen når du får et signal igennem og sørg for at notere det. Det skal bruges senere.

På min gamle analoge hus antenne fik jeg følgende resultat:

23 er Kanal kbh på 487.250 MHz
31 er DR1 på 551.250 MHz
33 er STV2 på 567.250 MHz
43 er Stv1 på 647.250 MHz
47 er Sverige 4 på 679.250 MHz
50 er Sverige 4 på 703.250 MHz
53 er TV2 på 727.250 MHz
60 er kanal SBS N på 783.250 MHz
(DR2 mangler her)

6. Installere Mythtv-pakken

sudo -i
apt-get install mythtv mythbrowser mythdvd mythgallery mythmusic mythnews mythvideo mythweather mythweb mythtv-doc mytharchive mythControls mythgame mythvideo

7 . Ændre password for brugeren mythtv og tildele rettigheder

sudo -i
passwd mythtv

For nemheds skyld bruger jeg passwordet mythtv her. Undervejs får du denne besked:

Ubuntu MythTV packages generate a random MySQL password. The generated password for this machine is 'uertscvj'.

PS: Nogle guider anbefaler at man noterer og senere ændrer dette password til Mysql. Min erfaring er, at det skaber store problemer og i værste fald maler man sig op i et hjørne. MySQL og rettighedder er en bitch hvis man ”pille” ved. Rør det ikke med mindre du 100% ved hvad du gør. Brug derfor standardpasswordet indtil videre. Det er kun hvis man vil redigere vha. Phpadmin at passwordet skal bruges. I denne guide bruges i stedet Mythweb, som ikke behøver noget logon.

Nu skal brugeren mythtv tildeles administrator-rettigheder:

gksudo gedit /etc/group

Se efter linier, der starter med "admin", og tilføj ",mythtv". Log ud fra din nuværende X session og ind igen som brugeren mythtv med passwordet mythtv.

Vigtigt: Herfra og frem skal man IKKE åbne noget med sudo –i. Vi vil installere resten som mythtv brugeren.

8. Hente TV-lister fra nettet med XMLTV

Programmet xmltv bruges til at ”høste” data omkring tv-programmers starttid, indhold mv. Jeg vælger at hente hos tv2. Der er andre muligheder – prøv at Goggle emnet. Man skal starte med at oprette en konto hos tv2. Se på http://www.tv2.dk/ for detaljer. Husk at gemme password og logon – de skal bruges lidt senere.

Kør i terminalen:

tv_grab_dk --configure --config-file=tv2.xmltv

Indsæt brugernavn/password og svar Yes/No til de kanaler du skal bruge. Undgå at vælge ”all” med mindre du bruger ”hele pakken”. Der tager nemligen krig at hente data 6 dage frem for 60 kanaler;-). Xmltv vil nu henter alle titler og tider ned. Det kan tage så hav toldmodighed.

9. Mythtv Setup

Før mythtv-seup køres skal man sørge for at backend’en er stoppet. I terminalen køres:

/etc/init.d/mythtv-backend stop

Derefter:

Mythtv-setup

Nu dukker mythtv-setup utility’en op man man stepper sig igennem forskellige optioner:

General

Alt hvad jeg ændrede her var TV standard til PAL og channel-frequency-table til europe-west.

Capture Card

Vælg TV-kort. Hvis du kunne se TV i testen lige før vil kortet også være at vælge. PS: Hvis du ingen kort kan se, så luk mythtv-seup (Esc) og stop backenden. Hvis den kører under setup kan den hijackke kortet og man får en fejl.

Video Source

Video source er i dette tilfælde den fil vi genererede lidt tidligere vha. XMLTV. Filen blev kaldt tv2.xmltv, men bare skriv tv2 – det er nok.

Nu kommer det store tryllenummer. Når du trykker Finish dukker en tidslinie op som stopper ved 50%. Det tog mig en krig at regne ud, at man skal trykke alt+tab for at komme til terminalen( i de tidlige versioner var der ingen note om det på siden). Man fortsætter med at logge ind på tv2-siden og vælger de kanaler man skal bruge. Hav toldmodighed – det tager sin tid.

Input Connections

Dette forbinder dit tv-kort med videokilden. Et godt navn vil være PVR-250. Video sourcen er her igen tv2

Tryk "Scan for channels" og vent. Hvis alt går vel vil du have en bunke kanaler at lege med..

Channel Listings

Her kan du editere de enkelte kanaler. I nogle tilfælde er det nok at angive officielle kanal numre i i andre bliver man nødt at indknaste TV-frekvensen.

Test konfigutionen

Nu kan du forlade setup utility og starte backend’en. Bemærk at den vil starte automatisk når systemet er genstartet.

Sudo -i /etc/init.d/mythtv-backend start

Check for fejl beskeder:

tail -f /var/log/mythtv/mythbackend.log

Nu kører du frontend’en logget ind som mythtv user:

mythfrontend

At this point, you should be able to watch TV, but the schedules won't quite work. See the next section for fixing this.

Opdatere tv-lister i databasen

Kør:

Mythfilldatabase

Vent. Det tager tid

Plugins: henter diverse fra:

http://www.mythtv.org/modules.php?name=Downloads&d_op=viewdownload&cid=1Hvor skal de plugs ligge? lægger dem i home

Diverse: Fjerner sysmlyde og screensaver

The underlying authorization mechanism (sudo) does not allow you to run this program. Contact the system administrator.

Installerer temeaer:

http://www.aldorf.no/mythtv/

Smid dem i /usr/share/mythtv/themes

Også Mythtv OSD "isthmus" skal med. Copy to /usr/share/mythtv/themes

to use it choose "isthmus" last page on Setup/Tv settings/Playback

I recomend "FreeSans" font, it looks much better.

Then, select "Retrieve Lineups", and within a short span of time (say 10 seconds or so) it should get the TV listings you configured over at your listing web site. It has been reported that this process stops, so you may have to Alt-Tab to the terminal and put in your username and password (for the listings grabber) again. Click the Finish Button, and hit ESC to get back to the main menu.

mythfilldatabase

..og så tester vi dyret:

mythbackend & mythfrontend

henter diverse fra:

http://www.mythtv.org/modules.php?name=Downloads&d_op=viewdownload&cid=1

Hvor skal de plugs ligge? lægger dem i home

Ændre placering af filer til /media/hdb5/videos osv:

change the permissions and ownership of the recordings directory:

sudo chown mythtv.mythtv /var/lib/mythtv

sudo chmod u=rwx,g=rwxs,o=rx /var/lib/mythtv

(This assumes that your directory for recordings is /var/lib/mythtv. If you have the recordings stored somewhere else, be sure to replace /var/lib/mythtv in the above command with that location.)

The end result is that the ownership and permissions should match /var/lib/mythtv as it was set by the installer. (You might want to replace /var/lib/mythtv with a symbolic link to your custom location if you are using a customized location.)

PS: Det var det her der virkede: chown -R mythtv.mythtv /media/hdb5/videos osv

Automatisk frontend start

Indstil X Windows til at starte automatisk ved boot. Rigtigt smart er det at vælge "timed login" - så har man nogle sekunder til at vælge at logge ind som administrator hvis noget er gået galt og skal rettes.

Først indsættes følgende i /etc/gdm/gdm.conf-custom file:

[daemon]
AutomaticLoginEnable=true
AutomaticLogin=mythtv

Derefter laves en fil kaldet .gnomerc i mythtv brugerens home folder og i den skrives:

touch /home/mythtv/.gnomerc
chmod 755 .gnomerc

Nu tilføjes denne linie:

sleep 10 &amp;& mythfrontend > /tmp/mythfrontend.log 2>&1 &

Alternativtil auto logon:
Hvis den først metode ikke virker så prøv den her, som bruger inittab til at logge ind som mythtv brugeren og starter X på een gang - uden at man behøver at lave en .bash_profile script.
Find denne linie i din /etc/inittab fil:

6:2345:respawn:/sbin/getty 38400 tty6

Udkommnter linien med #:

#6:2345:respawn:/sbin/getty 38400 tty6

Tilføj en ny linie lige under den du udkommenterede:

6:2345:respawn:/usr/bin/openvt -fwc 2 -- /bin/su - mythtv -c /usr/bin/startx >& /dev/null

Note: Man bør teste denne kommando for at checkke at mythtv brugeren har tilladelse til at starte X serveren. Hvis ikke det virker, så modificer din /etc/X11/Xwrapper.conf fil så den inkludere:

allowed_users=anybody

Note: Nogle vil foretrække denne metode, da den booter direkte i Mythtv uden at vise Ubuntus startbillede

EXTRAS:

Lydoptimering:

Brug OSS emulation af ALSA.

The 'MythFillEPG' Bash script

Alternativ Video Player
Prøv Xine med følgende parametre:

xine -r 4:3 -f -I --no-splash %s

ACPI Nedlukning & Opstart
Hvis dit bundkort tillader det, er det muligt for Mythtv at lukke automatisk ned når det ikke arbejder og vågne op igen når det skal optage en planlagt udsendelse. Én metode er at bruge den indbyggede ACPI Shutdown/Wakeup via RTC alarm funktionen.

Det første er at checke sine BIOS indstillinger. Se under en sub-menu af "Power Management" "APM", el. "Advanced”. Se efter Wake from RTC, Wake From Alarm, RTC Resume, etc. Note: På mange bundkort – med denne feature enabled – vil det vågne op efter en tid sat I BIOS’en og ikke fra en tid sat fra softwaren, som vi ønsker. Kan du ikke få det til at virke, så prøv at slå funktionen fra i BIOS.

Når du er i BIOS så se efter "ACPI Aware OS" og "ACPI 2.0" funktioner. Du har måske – måske ikke brug for disse. Min erfaring er at “ACPI Aware OS” skal være enabled og ACPI 2.0 lod til ikke at gøre nogen forskel. Sidste ting er at notere hvorvidt din hardware clock er sat til UTC eller local tid. Uret er på hovedsiden i BIOS. Hvis systemtiden (i 24 timers format) er det sammesom din lokaltid så er det ikke UTC (med mindre din lokale tidszone er GMT). Hvis Ubuntu er det eneste OS på dit system så er chancen for at tiden er gemt i UTC ret stor.

.
OS Funtion

Når ACPI er aktiveret skriver du:

$ dmesggrep -i acpi

Som vil give dig noget i retning af:

[17179569.184000] BIOS-e820: 000000003bfc0000 - 000000003bfce000 (ACPI data)
[17179569.184000] BIOS-e820: 000000003bfce000 - 000000003bff0000 (ACPI NVS)
[17179569.184000] ACPI: RSDP (v000 ACPIAM ) @ 0x000f9240
[17179569.184000] ACPI: RSDT (v001 A M I OEMRSDT 0x02000614 MSFT 0x00000097) @ 0x3bfc0000
[17179569.184000] ACPI: FADT (v002 A M I OEMFACP 0x02000614 MSFT 0x00000097) @ 0x3bfc0200
[17179569.184000] ACPI: MADT (v001 A M I OEMAPIC 0x02000614 MSFT 0x00000097) @ 0x3bfc0390
[17179569.184000] ACPI: MCFG (v001 A M I OEMMCFG 0x02000614 MSFT 0x00000097) @ 0x3bfc03f0
[17179569.184000] ACPI: OEMB (v001 A M I AMI_OEM 0x02000614 MSFT 0x00000097) @ 0x3bfce040
[17179569.184000] ACPI: DSDT (v001 761GX 761GX964 0x00000000 INTL 0x02002026) @ 0x00000000
[17179569.184000] ACPI: PM-Timer IO Port: 0x808
[17179569.184000] ACPI: Local APIC address 0xfee00000...
etc...

Næste ting er at checke RTC alarmen:

Hvis du skriver:

find /proc/acpi/alarm

Og du får dette retur:

/proc/acpi/alarm

..er alt OK. Hvis ikke, så skal ACPI support aktiveres i BIOS.

hwclock.sh
Dette script er hjertet i ACPI wake-up. hwclock.sh findes i /etc/init.d/ og læser hardware clock’en ved boot og kopierer det til “system tid”. Det kopierer også systemtid tilbage til hardware clock’en ved shutdown. På denne måde skulle hardware clock’en forblive præcis eftersom at system tiden bliver opdateret via NTP.

Mange boards “glemmer” RTC alarm tiden hvis der bliver skrevet til hardware clock’en efter at RTC alarm er sat.

For at komme rundt om dette skal der laves to modifikationer i hwclock.sh scriptet.

Fra dette punkt går jeg ud fra at man er i brugerens home-katalog og har sudo–rettigheder.

$ sudo cp /etc/init.d/hwclock.sh hwclock.sh.bak

Now, make two small additions to the existing hwclock.sh:

$ gksudo gedit /etc/init.d/hwclock.sh

At the head of the file, add the following line:

ACPITIME=`cat /proc/acpi/alarm`

The result looked like this for me:
... comments ...
HWCLOCKPARS=
ACPITIME=`cat /proc/acpi/alarm`
hwclocksh()
{
[ ! -x /sbin/hwclock ] && return 0
etc...

Next, scroll down to the tail of the file and look for:

# Updates the Hardware Clock with the System Clock time.
# This will *override* any changes made to the Hardware Clock.
#
# WARNING: If you disable this, any changes to the system
# clock will not be carried across reboots.
#
if [ "$HWCLOCKACCESS" != no ]; then
if [ "$GMT" = "-u" ]; then
GMT="--utc"
fi
/sbin/hwclock --systohc $GMT $HWCLOCKPARS $BADYEAR
fi
;;

You want to add this line:

echo "$ACPITIME" > /proc/acpi/alarm && sleep 1 && echo "$ACPITIME" > /proc/acpi/alarm

so that section of code now looks like this:

# Updates the Hardware Clock with the System Clock time.
# This will *override* any changes made to the Hardware Clock.
#
# WARNING: If you disable this, any changes to the system
# clock will not be carried across reboots.
#
if [ "$HWCLOCKACCESS" != no ]; then
if [ "$GMT" = "-u" ]; then
GMT="--utc"
fi
/sbin/hwclock --systohc $GMT $HWCLOCKPARS $BADYEAR
echo "$ACPITIME" > /proc/acpi/alarm && sleep 1 &&amp;amp;amp;amp;amp;amp;amp; echo "$ACPITIME" > /proc/acpi/alarm
fi
;;

Save the result.
This added command writes the wake time after the final clock change (the command directly above it).
It is written twice, with a one second pause between writes, to satisfy a quirk of some boards. Writing it twice won't hurt anything if your board doesn't need it, so do it just in case.

Clock Format
To correctly set the wake time, you need to know the format of your RTC alarm.

$ cat /proc/acpi/alarm

will return the RTC format. you should see something like:

2007-**-28 14:10:21

In this example, the format is yyyy-MM-dd hh:mm:ss- the ** may be the correct month, 00 or be blank on your system- having no settable month seems to be common.

First Test
Before you dig too much deeper into setting this up, it's a good idea to determine whether or not your board is going to comply. At this point, everything should be ready to test a wake-up. To do this, you will set the system to wake five minutes from now. If your computer is slower, you can increase the time; if faster, you can decrease it. Just make sure you allow for enough time for the system to shut down completely, with a minute or two to spare before it needs to wake.
The following command uses our example time format of yyyy-MM-dd hh:mm:ss and adds 5 minutes to the ACPI alarm. If your time format is different, you will need to adjust the ordering of +00-00-00 00:05:00 to comply.

$ sudo sh -c 'echo "+00-00-00 00:05:00" > /proc/acpi/alarm'

It is a good idea to check if the command did the job right.
If the year part looks like "0007" instead of "2007", change +00 with +2000; this worked for Acer Ferrari 3400 laptop and Asus M2NPV-VM motherboard...

$ cat /proc/acpi/alarm

Now you can shut down the system to see if it wakes up. Bookmark this page if you haven't already. I'll see you when you get back.
Shut it down:

$ sudo shutdown -h -P now

Sit back, relax and wait for your box to wake up...

Welcome Back!
Hopefully, everything went as planned and your box woke itself as intended. If not, double-check each step above to be sure it was all correctly done. If everything is correct, your board might need to reboot and complete a POST cycle before correctly waking, as some do. Skip ahead now to 3.0 Poweroff Kernel and try that remedy.

If you tried the poweroff kernel but still failed to wake, see 4.0 Troubleshooting.
If it did wake, CONGRATULATIONS! It's all downhill from here...
Scripts and Settings
You will likely need at least one of these scripts for the wake-up/shutdown process:
a script to adjust and set the wake-up time (if your mobo clock is UTC)
a Pre-shutdown script (possibly)
a Server Halt script (if you use poweroff kernel)
Examples of a wake script MythWakeSet, pre-shutdown script MythShutdownCheck and server halt script for poweroff kernel MythShutDown are provided here. If you need to do something special on your system before shutdown, such as special service shutdown scripts, etc., then you are responsible for integrating them into the provided script.

MythWakeSet
If your hardware clock is set to UTC, you need MythWakeSet to adjust between the wake time MythTV will report (local time) with the time the RTC alarm requires (UTC). If your hardware clock is set to local time, you don't need this script.
To create the wake script, open the editor of your choice and copy and paste the following. Save it as MythWakeSet:

#!/bin/bash
#
# MythWakeSet
#
# set mythtv wake-up time with UTC-adjusted time
#
# temp file for working with time
temp_stamp=/home/mythtv/timestamp
# store the wake time passed from mythbackend
echo $1\ $2 > $temp_stamp
# Read the date in *locale* time format and tag the time-zone info to the wake time
localeadd=$(/bin/date -f $temp_stamp +%F\ %T\ %z)
echo $localeadd > $temp_stamp
# adjust this to UTC and store the final wake time
utcadj=$(/bin/date -u -f $temp_stamp +%F\ %T)
# set the alarm
echo $utcadj > /proc/acpi/alarm
Now, make the script executable and put a copy of it in /usr/bin:
$ chmod +x MythWakeSet
$ sudo cp MythWakeSet /usr/bin
MythShutdownCheck

If you use your backend server for other things in addition to MythTV, such as ssh or ftp transfers etc., you want to make sure that MythTV doesn't shut down the system while you are in the middle of something. This is especially true if you have the backend set to a stingy idle timeout like 5 minutes.
One very effective way to do this is to check and see if another user is logged in, since you likely won't be transacting much non-mythtv business as the mythtv user. If you are not watching tv or a recording, but want the backend box to remain alive, all you need to do is log into an ssh session and leave it open.
You can do other checks in addition to- or instead of- checking for logged-in users: such as checking for specific running processes, etc. Add these checks to this script if needed, but first be sure to check that your changes work properly! Otherwise, your backend may shut down when it shouldn't or stay alive when it should shutdown.
If you want to make sure no other users are logged in before shutdown, copy and paste the following into an editor and save it as MythShutdownCheck; if not, skip ahead to 2.3.

#!/bin/bash
#
# MythShutdownCheck
#
# checks to see if any other user is
# logged in before idle shutdown
#
# returns "1" if yes, stopping shutdown
# returns "0" if ok to shutdown
#
if last head grep -q "pts/.*still logged in" # check for active *remote* login?
then
exit 1
else
exit 0
fi

Make the script executable and put a copy of it in /usr/bin:

$ chmod +x MythShutdownCheck
$ sudo cp MythShutdownCheck /usr/bin
mythtv-setup

At this stage, you have the needed scripts and the box woke successfully on test. Now it's time to setup Mythtv to test MythWakeSet.
Stop the server for needed changes and then run mythtv-setup:

$ sudo /etc/init.d/mythtv-backend stop
$ mythtv-setup

The settings you need are under 1. General, on page 5 (Shutdown/Wakeup Options). The settings you need are:
Idle timeout (secs): is how long the backend will wait in an idle state before wanting to shutdown. Normally, you would want this set to a reasonable amount between 300-1200 (5 to 20 minutes)- but to test it out, set it to 30 so you don't have to wait long.
Max wait for recording (min): determines whether or not the backend will shutdown if it is idle and there is a pending recording. e.g. if this is set to 20 minutes, the backend is idle and wants to shut down and the next recording is scheduled three hours in the future, the backend will shutdown and wake itsef up later. If the same conditions are true, but the recording is scheduled to start in 20 or fewer minutes, then it will wait, record it and then check this setting again after reaching an idle state . For now, set this to 1 to make sure it shuts down for our tests.
Startup before rec. (secs): is how much time the backend will allow for itself to fully boot and come up to speed, before being expected to record. Note that this time will be added as an offset to the wake time. You should likely allow at least 200 seconds or more to be sure you do not miss beginning of your recording. Set this to a reasonable estimate of your boot time for now, but time your boot from powerup for your final setting.

Wakeup time format: is the format your board expects for the RTC alarm (you checked this earlier). In this example, it is yyyy-MM-dd hh:mm:ss adjust yours as necesary.
Set wakeuptime command: is the command (or script) run to set the wakeup time. If you are using the UTC script above, enter: sudo /usr/bin/MythWakeSet $time This will call your script and pass it the waketime via the $time variable. If you are just using local time, you can enter sudo sh -c 'echo $time > /proc/acpi/alarm'
Server Halt Command: is the command that is executed to bring the whole thing down. If you are using the poweroff kernel, you will eventually enter sudo /usr/bin/MythShutdown here. For this test, enter: sudo /etc/init.d/mythtv-backend stop, which will only stop the backend.
Pre Shutdown check-command: is the shutdown checker- enter sudo /usr/bin/MythShutdownCheck to use it or enter exit 0 if not.
sudo
The last thing to do before testing is to take care of permission issues. As you probably noticed, the above commands run as "sudo", which would cause problems if it prompted for a password and nobody was there to enter it-- nothing would ever happen.
There are a number of ways to handle this- the method presented here gives the mythtv user sudo privileges, without prompting for a password, for limited commands and resources. There are other alternatives you can explore; each with their own advantages and pitfalls.
To give mythtv user the permissions we need:

$ sudo visudo

Add the following line to the end, making sure it is the only entry for mythtv- if another entry for mythtv exists, replace it with this one:
%mythtv ALL = NOPASSWD: /sbin/shutdown, /usr/bin/MythWakeSet, /proc/acpi/alarm, /usr/bin/MythShutdownCheck, /etc/init.d/mythtv-backend, /usr/bin/MythShutdown
NOTE: If you are using the poweroff kernel, use:
%mythtv ALL = NOPASSWD: /sbin/shutdown, /usr/bin/MythWakeSet, /proc/acpi/alarm, /usr/bin/MythShutdownCheck, /etc/init.d/mythtv-backend, /usr/bin/MythShutdown, /sbin/reboot, /sbin/grub-set-default

Another Test
Before proceeding, go into the frontend and schedule a recording an hour or so from now and note the time it starts.
Now we can test to see if the scripts and their interfaces with MythTV are set up correctly. First, set /proc/acpi alarm to a known value (again, if your date/time format is not yyyy-MM-dd hh:mm:ss, adjust as needed):

$ sudo sh -c 'echo "2007-12-12 12:12:12" > /proc/acpi/alarm'

Then, check to see it was set. You should see something simlar to:

$ cat /proc/acpi/alarm
2007-**-12 12:12:12

Now, fire up the backend to test the write to /proc/acpi/alarm. In this case, we won't lauch it as a daemon so we can see what is being logged:

$ mythbackend &

It should immediately start warning you of impending shutdown, count it down and then stop. Hit Enter to get a command prompt and then check to see if MythWakeSet worked:

$ cat /proc/acpi/alarm
2007-**-01 20:59:00

As the example shows, the time returned should now reflect the waketime and not all 12's, as we set before the test. Of course, yours will probably not match the example...
If your hardware clock is in UTC, to see if the waketime is set correctly:
Take the start time of the recording you set a little while ago (24 hour format), add or subract (as appropriate) for your time zone offset, and subtract the amount of time you set for Start before recording in step 2.3.

For example:
Recording was for 4pm (16:00:00)
Local time is GMT-5 +(05:00:00)
Start before rec was -(00:01:00)
Time with offset is 20:59:00

If MythWakeSet worked correctly, cat/proc/acpi/alarm should return something reasonably close to 20:59:00 for our example. If, after checking your math, yours still varies substantially or is unchanged from 12's, go back and review each step to check for errors. If you have the recording options in MythTV to wake a minute or two (or more) before the scheduled recording, this will also cause a small discrepancy.

The FINAL Test
The final and most important test is to put it all together for a full shutdown/wakeup.
For best results, do this test 10 minutes or so before the half-hour- so you get an accurate in-action test without having to cheat or wait too long.
Make sure the backend is shut down and go back into setup:

$ sudo killall mythbackend
$ mythtv-setup

Return to the Shutdown/Wakeup page and make the following changes:
Idle timeout (secs): 120Server Halt Command: sudo shutdown -h -P now
if you are using the poweroff kernel this will be: sudo /usr/bin/MythShutdown (see 3.1 MythShutdown)
And then start the backend:

$ sudo /etc/init.d/mythtv-backend start

In the frontend, find a show- on any tunable channel- that begins at the next half-hour and set it to record. Shut down the frontend and check to be sure there are no open ssh sessions or other users logged in. If this is a combined frontend/backend, log out of your current session.
Within two or so minutes, the backend should shut itself down.
Now is a good time to get a sandwich or a cold drink (or both!) and wait for it to turn itself on and boot up!
Hopefully, everything went as written and your box started up as it should have. If not, but you could successfully wake in step 1.4, check every step from 2.0 forward- it should be working properly. There's likely a small mistake somewhere.
When it wakes and records it should , all that is left for you to do is shutdown mythtv-backend, go back into mythtv-setup and make your final settings for Idle timeout, etc.
ENJOY!

MythWelcome
If you ran frontend and backend on the same machine, you can use MythWelcome to decide if the machine has been woken up by user and the start of the frontend is needed or not. With MythWelcome the Frontend is automatically started if you started the machine manually, but if its started automatically via acpi-wakeup the frontend won't start and look the backend from shutting down when recording is finished. Unfortunately MythWelcome is original build for using with nvram-wakeup, but you can also use it with nvram wakeup.
First you have to manipulate /usr/share/mythtv/startmythtv.sh to specify that mythwelcome is loaded in startup instead of loading the frontend directly. You can do this by starting an editor with
$ sudo nano /usr/share/mythtv/startmythtv.sh

Look for the last lines

#start mythtv frontend software
exec mythfrontend
and change it to

#start mythtv frontend software
#exec mythfrontend
sleep 5
exec mythwelcome

I need the sleep options because mythwelcome is faster than the backend, without this i get an error that the backend is not running. Restart
Modify MythWakeSet

Because MythWelcome uses a Unix timestamp to set the wakup time you need to modify the /usr/bin/MythWakeSet script. Open it via
sudo nano /usr/bin/MythWakeSet
and replace
# store the wake time passed from mythbackend
echo $1\ $2 > $temp_stamp
with
# store the wake time passed from mythbackend
##echo $1\ $2 > $temp_stamp
tmp=`echo $2 awk -F: '{print strftime("%Y-%m-%dT%T", $1)}'`
tmp1=`echo $tmp awk 'BEGIN { FS = "T" } { print $1 }'`
tmp2=`echo $tmp awk 'BEGIN { FS = "T" } { print $2 }'`
echo $tmp1\ $tmp2 > $temp_stamp
Configure MythWelcome
Exit the frontend, you will automaticaly get the mythwelcome screen. Press F11 to enter the setup and enter the following values: nvram-wakeup Command: sudo /usr/bin/MythWakeSetnvram-wakeup Restart Command leave blank!Command to reboot: sudo shutdown -h -r now leave the rest unchanged.
Configure MythBackend
Navigate to Shutdown/Wakeup Options and change the following values: Wakeup time format:: yyy-MM-ddThh:mm:ssSet wakeuptime Command: mythshutdown --setwakeup $timeServer halt Command: sudo shutdown -h -P nowPre Shutdown check-command: mythshutdown --check
Now test your configuration, but be aware that mythshutdown won't proceed if there is an recording less than 15 minutes away!
Poweroff Kernel
Before proceeding, try enabling/disabling (make it the opposite of what it is now) the Wake from RTC setting in BIOS, booting back into Ubuntu and attempting 1.4 First Test again. If it still fails after having tried adjusting BIOS settings, return any changed BIOS settings to their original state and try the following poweroff kernel remedy.
If you are not careful, these changes can hose your grub and booting could be an adventure. If have not edited your grub menu before or are not sure what you are doing, you should ask someone for assistance or google for grub editing information. PLEASE BACK UP YOUR menu.lst BEFORE MAKING THESE CHANGES!!!
So just back it up, cowboy...
$ sudo cp /boot/grub/menu.lst menu.lst.bak
The poweroff kernel's sole function is to shut the computer off- but it does so after rebooting and completing the reboot and POST cycle, which satisfies the quirks of some boards (including an older tested by the author).
To test if your motherboard might need a poweroff kernel, set a wake up time a few minutes in the future, restart the PC in the normal manner, but turn the PC off (by pressing the power button briefly, not by holding it down for a few seconds) after the POST but before Linux boots up. If the PC wakes up using this method, then the poweroff kernel should work for you. If it doesn't, this is not necessarily indicative of failure- at least one tested board failed this procedure but worked very well with the poweroff kernel.
First, install the poweroff kernel- download, unpack it and copy it to /boot:
$ wget http://prdownloads.sourceforge.net/nvram-wakeup/reboot-2004.10.03.tar.bz2?download
$ tar -xvjf reboot-2004.10.03.tar.bz2
$ sudo cp reboot-2004.10.03/bzImage.2.4.20.poweroff /boot
Next, edit the grub menu:
$ gksudo gedit /boot/grub/menu.lst
find the line at the head that reads:
default X
make note of the default number that is there (X) and then change it to:
default saved
This will cause grub to boot the last menu entry that was set (using grub-set-default, surprisingly). In this case, you will set the default value to the poweroff kernel. On reboot, grub will load, boot the poweroff kernel and shutdown.
Setting the default back to the "usual" kernel in the poweroff kernel menu entry ensures that when it wakes, it will boot into Ubuntu and MythTV as normal. The "usual" kernel is the X you just wrote down.
Append this entry to the end of your menu list:
title POWER OFF
savedefault X ### replace X with your default value from the step above ###
root (hd0,0) ##### this entry should match the ''root'' statement of your default kernel ####
kernel /boot/bzImage.2.4.20.poweroff root=/dev/null
Next, counting from 0, determine the menu entry for this poweroff kernel.
e.g. if you show one kernel, one recovery mode, one memtest and this kernel, the menu entry would be 3... if you have only a main kernel and this poweroff kernel, then it is 1, etc. Remember not to count any menu items that are commented out (with #).
Double-check the menu list to be sure you counted correctly!
Now you can test it out. Substitute value of poweroff kernel you determined above for P in the following and reboot:
$ sudo grub-set-default P
$ sudo reboot
Your computer should reboot, go through POST, load grub and then shut off.
When this works, you are ready to try a wake again-
$ sudo sh -c 'echo "+00-00-00 00:05:00" > /proc/acpi/alarm'
$ sudo grub-set-default P ## again, substitute "P" with poweroff value
$ sudo reboot
See you back at Step 1.5...

MythShutdown
If you are using the poweroff kernel, you will need this script to set the default grub selection and reboot. Copy and paste the following into an editor and save it as MythShutdown
#!/bin/bash
#
# MythShutdown
#
# saves the powerof kernel grub entry and reboots
#
sudo grub-set-default ''P'' ### replace "P" with the poweroff menu value from 3.0!
sudo reboot
Make it executable and copy it to /usr/bin:
$ chmod +x MythShutdown
$ sudo cp MythShutdown /usr/bin
Troubleshooting
Small mistakes are easy to make, so double and triple-check the things you have done.
If you were able to wake your board in step 1.4 (whether or not you are using the poweroff kernel), but you can't get MythTV to wake- chances are you made one or more small mistakes. Go back and check thoroughly.
If you were unable to get your board to wake for the test in step 1.4:
Try it again after changing the BIOS RTC wake setting to the opposite of what it is now
Try it with various combinations of BIOS settings for Power Management-type functions
Google, google, google...
Give your mobo manufacturer's technical support a call
Some motherboards will only wake from S3 (suspend), rather than from S4 (hibernate) or S5 (power off). If yours is one of these, you'll have to investigate suspending your PC instead of shutting it down.
Investigate other options- your board might be one that just won't wake with ACPI
Man, I Give Up!
If you have reached this stage, I'm sorry that ACPI wakeup did not work for your board.
To return things back to their original state:
$ sudo cp hwclock.sh.bak /etc/init.d/hwclock.sh
$ sudo cp menu.lst.bak /boot/grub
$ sudo rm MythWakeSet /usr/bin/MythWakeSet MythShutdownCheck /usr/bin/MythShutdownCheck MythShutdown /usr/bin/MythShutdown
To remove the backup system files:
$ sudo rm hwclock.sh.bak menu.lst.bak
If you aren't frustrated to the point of loathing shutdown/wakeup, you can investigate other wakeup options via google, the MythTV forums and our excellent Ubuntu forums.
Good Luck!

Ubuntu, T60 and Wifi LAN

2007-05-23T05:43:00.000-07:00

Jeg har leget med Opensource de sidste 5-6 år uden egentligt at bruge det til noget. Med den nye Ubuntu 7.03 Feisty er tingene begyndt at fungere på et helt andet niveau end tidligere.

Ubuntu Live-install CD'en kører uden problemer og er derfor røget ind på den bærbare. Jeg har dog haft problemer med at få det trådløse netværk til at virke. Her er en kort "howto" omkring hvordan jeg fik det til atfungere på min Lenovo T60 IBM Thinkpad:

Installing a Wifi driver on Linux (Ubuntu Feisty) using ndiswrapper for the ThinkPad 11a/b/g/n Wireless mini pci LAN card.

1. Get ndiswrapper:
http://sourceforge.net/project/showfiles.php?group_id=93482

2. Download Lenovo T60 Windows driver:
http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-66449

3. Extract its contents with cabextract. You need only the NET5416.INF file.
Run:

cabextract 7iwc16ww.exe

4. Install the driver NET5416.inf file with ndiswrapper:

sudo -i
cd WINXP_2K/
/usr/sbin/ndiswrapper -i NET5416.INF

5.Is the driver is installed?:

ndiswrapper –l

6. load ndiswrapper module:

depmod -a
modprobe ndiswrapper

7. Running iwconfig in the terminal shows the card:

iwconfig wlan0

wlan0 IEEE 802.11b ESSID:"My Home Wireless"
Mode:Managed Frequency:2.462 GHz Access Point: 01:23:45:67:89:AB
Bit Rate:11 Mb/s
Encryption key:off
Power Management:off
Link Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

8. Load ndiswrapper at start:

Add the following to /etc/rc.local to start your network card automatically.

modprobe -r ndiswrapper
modprobe ndiswrapper

9. Reboot and enjoy!

Tricks, Licks & Harmonix

Installing Apache 2.2 from source on Ubuntu

Verifying Which Ports Are Listening with Nmap

Test an MX record

To start or stop services under any debian based distro

WordPress Installation on Ubuntu

Installing AlienBBC on Linux

Instructions for installing Slimserver Ubuntu (Debian)

Installing Slimserver on Ubuntu Feisty 7.04

X-Forwarding mythtv-setup

Installere Imon VDF

The Perfect Setup - Ubuntu 7.04 LAMP

1 Enable The root Account

2 Install The SSH Server

3 Configure The Network

4 Edit /etc/apt/sources.list And Update Your Linux Installation

5 Change The Default Shell

6 Install Some Software

8 Quota

9 DNS Server

10 MySQL

11 Postfix With SMTP-AUTH And TLS

12 Courier-IMAP/Courier-POP3

13 Apache/PHP5

13.1 Disable PHP Globally

14 Proftpd

15 Webalizer

16 Synchronize the System Clock

17 Install Some Perl Modules Needed By SpamAssassin (Comes WithISPConfig)

18 ISPConfig

18.1 A Note On SuExec

Optimize the Mythtv Mysql Database

Linux server: Printerinstallering og deling

Ændre stier og rettigheder i Mythtv

Tilføj et Sony Ericsson HBH-610 Bluetooth headset til mobil

Koncepter for Improvisation

Giv Mythtv en fast IP-adresse

Start Mythfrontend automatisk efter logon

Automatically login the mythtv user at boot

Configure the power button on the remote

Automatically back up the MythTV database daily

Making sure the mythbackend stays up

Automatically login the mythtv user at boot

Linux er for sindsygt....

Find en fil og list den

Bruge VNS viewer fra Ubuntu

Sæt hastigheden på CPU'en op og ned efter belastning

Køre Netbank på Ubuntu med Internet Explorer

Installere wine og cabextract

Installere IEs4Linux

Mythtv Speed Tips

Ubuntu Home filserver med Samba og printserver med CUPS

Installing CUPS

Komplet HTPC med Mythtv på Ubuntu og PVR-250

Ubuntu, T60 and Wifi LAN

17 Install Some Perl Modules Needed By SpamAssassin (Comes With
ISPConfig)