perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = "en_DE:en_US:en_GB:en",
        LC_ALL = (unset),
        LANG = "en_US"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

dpkg-reconfigure locales

good luck ...

This tutorial will explain how to install zgegblog-themes in ubuntu jaunty and intrepid
Thanks to Zgegblog for this fantastic themes

First edit /etc/apt/sources.list file

sudo gedit /etc/apt/sources.list

add the following lines

deb http://ppa.launchpad.net/bisigi/ppa/ubuntu karmic main
deb-src http://ppa.launchpad.net/bisigi/ppa/ubuntu karmic main

Save and exit the file

add the GPG key using the following command

sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 1781bd45c4c3275a34bb6aec6e871c4a881574de

Update the source list using the following command

sudo aptitude update

Install all the themes using the following command

sudo aptitude install zgegblog-themes

http://www.ubuntugeek.com/nice-ubuntu-themes-for-jaunty-and-intrepid-users.html

For me automaticly mounting and dismounting the remote drive with sshfs is the solution for me.

As I justinstalled gutsy Ubuntu 7.10 I wrote along this howto in order to document it for my self but allso for others to use. .
First the package sshfs is needed.
This can be installed with the synaptics package manager. Search for sshfs, mark it and have it installed.
After installed sshfs installed, test if you can mount a ssh/scp accessable remote file system.
create a directory where you want to mount it on

Code:

sudo mkdir /RemoteDiskSSH

Mount the desired remote directory on your local file system.

Code:

sudo sshfs remoteuser@remote.machine.address:/Remote/Directory/to/mount /RemoteDiskSSH

If all went oke you can now access the remote file system as it was a local file system from the local folder /RemoteDiskSSH

Code:

sudo ls /RemoteDiskSSH

Want to be able to use the local rights system on that folder? (just if you dont want to go on but want to be able to mount a remote filesystem and have the
local rights translated to it.)

Code:

sudo sshfs -o allow_other,default_permissions remoteuser@remote.machine.address:/Remote/Directory/to/mount /RemoteDiskSSH

now the local rights system will work for this mount

to unmount it just give the command

Code:

sudo fusermount -u /RemoteDiskSSH

As i want the remote directory mount automaticly (with autofs described later on)
i need a passwordless ssh login. This can be done with help of generating public keys.
A public key for the local system is generated with the command:

Code:

ssh-keygen -t rsa

(hit enter so its saved in your home directory under .ssh/id_rsa

(hit enter for no passphrase)

you have now a .ssh directory with two files
id_rsa and id_rsa.pub

id_rsa is your private key ! protect it well let only YOU have rights on it (default) as if this gets compromised
anyone can gain access to your remote host

id_rsa.pub is the public key it is readable by others and this is what you have to send to the remote host so it can have it in its authorized_keys file

Copy now the public key to the remote machine

Code:

scp ~/.ssh/id_rsa.pub remoteuser@remote.machine.address:~/.

logon with an ssh client to the remote machine the id_rsa.pub file content must be added to the authorized_keys file in the .ssh directory of the homedir of the user you want to connect as.

In this example the remote users home directory

Code:

ssh remoteuser@remote.machine.address
cat ~/id_*.pub >> ~/.ssh/authorized_keys

A alternative simpeler way to get your public key in the authorized_keys file of your remote host is with ssh-copy-id
from your local machine type

Code:

ssh-copy-id -i ~/.ssh/id_rsa.pub remoteuser@remote.machine.address

this does the whole process of copying your public key to the remote machnes users homedir in .ssh in authorized_keys
and sets the rights oke

As later on the mount is done by the local root user you need the public key of root too.

so give command

Code:

sudo gnome-terminal

to open a command terminal as user root and repeat the above procedure.

after this the file authorized_keys at the remote station has both the public key of the local user and the local root so it works in test and in production later when root does the mounwork....

Set the right rights for the file authorized_keys or the ssh deamon ( in my case dropbear) might not want to process the authorize_keys file

Code:

ssh remoteuser@remote.machine.address
chmod 0600 ~/.ssh/authorized_keys

logout from the remote machine and test.

Code:

ssh remoteuser@remote.machine.address

You should now be able to login without giving a password.

If it does not work debug with ssh -v option .

(same for the sudo gnome-terminal )

If it works you can see if the mount works passwordless too

Code:

sudo sshfs remoteuser@remote.machine.address:/Directory/to/mount /RemoteDiskSSH

So ! thats done!!! you can now mount the remote filesystem without using a password.

unmount again with:
Code:

sudo fusermount -u /RemoteDiskSSH

As i said i want the remote filesystem to be mounted automaticly as soon as i try to access it. This can be done with autofs.

First install autofs by starting the synaptics package manager search for autofs, mark for install and have it installed.

theres now a auto.master configuration file in /etc
add the line

/etc/auto.master
Code:

RemoteDiskSSH /etc/auto.ssh uid=1000 gid=1000 -v --ghost --timeout=3600

uid and gid are the local user and group id you want the mount to belong to.

--ghost is the directory will be ghost mounted so you see it with an ls but the actual mount is done when you access it

--timeout gives the maximum inactivity time for the mount. After that it is auto dismounted again.

One more config file is needed and that is /etc/auto,ssh
create the file and put in the following line:

/etc/auto.ssh
Code:

RemoteDiskSSH -fstype=fuse,port=22,rw,nodev,nonempty,noatime,allow_other,max_read=65536 :sshfs\#remoteuser@remote.machine.address\:/Directory/to/mount

You can now test the autofs mounting by starting and stopping the automount service

Code:

sudo /etc/init.d/autofs restart

in /var/log/syslog are the loggings
start a separate command terminal and give this command to follow it all.
Code:

tail -f /var/log/syslog

check if it worked

Code:

ls /RemoteDiskSSH

if all is oke you see the content of the remote file system.

The same you can actually do for a windows or samba share

The question is if you want this as in Ubuntu 7.10 gutsy if you goto menu Places and then browse network locations, you can easily get to the windows shares in your network. (I prefer doing the above)

Nevertheless ill describe here how it can be done using smbfs and autofs.

first you have to install smbfs

Start the synaptics package manager, search for smbfs, mark and install it.

the line for the /etc/auto.master file is

Code:

/ /etc/auto.Samba --ghost -v --timeout=300

Create the file /etc/auto.samba

and fil it with the following line:

/etc/auto.samba
Code:

RemoteDiskSamba -fstype=smbfs,workgroup=WORKGROUPNAME,credentials=/etc/samba.credentials,uid=remoteuser,gid=users ://remote.server.address/ShareName

Then create the credentials file in /etc/samba.credentials

fill this file with the following lines:
/etc/samnba.credentials
Code:

username = remoteusername

password = remotepassword

take care only root can see this file
Code:

sudo chmod 600 /etc/samba.credentials

If this is done just restart the autofs

Code:

sudo /etc/init.d/autofs restart

(tail -f /var/log/syslog in a seperate terminal to see the loggings)

and see if it works.

Good luck!

First you need to edit the /etc/apt/sources.list file using the following command

#nano /etc/apt/sources.list

add the following line

deb http://www.backports.org/debian etch-backports main contrib non-free

save and exit the file.

Update the source list using the following command

#apt-get update

All backports are deactivated by default. If you want to install something from backports run:

#apt-get -t etch-backports install “packagename”

If you are using etch and you want apt to verify the downloaded backports you can import backports.org archive’s key into apt:

#apt-get install debian-backports-keyring

If you want to get your packages from backports upgraded automatically the following entry in /etc/apt/preferences should be sufficient:

Package: *
Pin: release a=etch-backports
Pin-Priority: 200

Once you have backports all set up do one of the following commands

#apt-get update

#apt-get install flashplugin-nonfree

http://www.debianadmin.com/how-to-install-adobe-flash-in-debian-etchlennysid.html

When trying to login with an IMAP connection to your Google Apps for Domains email account, you may encounter this error:

Web Login Required

What Google is telling you is that you need to unlock your account, via your browser, by entering a CAPTCHA. Here's what you must do:

1. Type the URL below into your browser, replacing YourDOMAIN.com with your Google Apps domain.

https://www.google.com/a/YourDOMAIN.com/UnlockCaptcha

2. Enter your Google Apps for Domains User ID, password, and the CAPTCHA displayed by Google.

3. You should then be able to access your email account via IMAP.

For the details of how to configure your IMAP email client, read Google's Instructions - a list of supported client software programs is included.
Document Actions

source:http://plone3.trueblade.com/knowledge/google-apps-for-domains-imap-mail-login-problem

yum install kernel-devel
yum groupinstall "Development Tools"

Sonrada asagidaki adimlari uyguluyoruz.
I recently got stuck while trying to install Headless Virtualbox on a Centos 5.2 server per the directions at Howtoforge here. The RPM failed with the error that it couldn’t find the kernel source. I thought I had already installed kernel-devel, and confirmed that I did. The instructions were to define the KERN_DIR variable like so:

$ export KERN_DIR=/usr/src/kernels/2.6.18-92.1.22.el5-i686/
$ /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module [ OK ]
Removing old VirtualBox netflt kernel module [ OK ]
Removing old VirtualBox kernel module [ OK ]
Recompiling VirtualBox kernel module [ OK ]
Starting VirtualBox kernel module [FAILED]
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)

dmesg shows this:

vboxdrv: disagrees about version of symbol struct_module

Interesting!

After several missteps, it turns out there is a separate development rpm for the PAE kernel:

$ yum install kernel-PAE-devel

After that installs, we are good:

$ export KERN_DIR=/usr/src/kernels/2.6.18-92.1.22.el5-PAE-i686/
$ /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module [ OK ]
Removing old VirtualBox netflt kernel module [ OK ]
Removing old VirtualBox kernel module [ OK ]
Recompiling VirtualBox kernel module [ OK ]
Starting VirtualBox kernel module [ OK ]

Kaynak:http://systembash.com/content/installing-virtualbox-pae-kernel-centos/

debian.org
http://www.debianhelp.org/
http://www.debianhelp.co.uk/
http://www.debianadmin.com/
http://www.debian-administration.org/

[ad#ad-1]

apt-get install fail2ban

mkdir /var/log/named
chmod a+w /var/log/named

Next, edit /etc/bind/named.conf.local and add the following lines

logging {
channel security_file {
file "/var/log/named/security.log" versions 3 size 30m;
severity dynamic; print-time yes; };
category security { security_file; };
};

now to set up fail2ban. Edit the /etc/fail2ban/jail.conf file and change from:

[named-refused-udp]
enabled  = false to:true

[named-refused-tcp]

enabled  = false to true

Then restart fail2ban in the usual manner,

/etc/init.d/fail2ban restart

read more article for click