Hello

Add this in  /etc/apt/sources.list

#Lenny backports
deb http://www.backports.org/debian lenny-backports main contrib non-free

Then

apt-get install debian-backports-keyring

apt-get install -t lenny-backports pidgin

 From the spanish list (in spanish) :
http://xbitcarry.wordpress.com/2009/11/10/instalar-pidgin-2-6-2-en-debian-lenny/ 

bruno

“aProgram > /dev/null 2> 1&”

duah bosan dengan perintah begituan

nah cobain yang ini deh gan

“aProgram 2>&1 | tee aProgram.log”

that’s cool for interactive n documented login

P4 System running Debain Linux with custom compile 2.6.xx.xx series kernel. In order to write CDs at command prompt you need programs:
1)mkisofs – Create an ISO file image so that cdrecord can use the same to burn on a CD.
2)cdrecord – It is a utility capable of burning an actual disc i.e. ISO images created with mkisofs.
Since these packages were not installed I quickly run the commands to install it:
# apt-get install mkisofs
# apt-get install cdrecord

Configure cdrecord to write a CD

Under kernel version 2.6 you would not want to use ide-scsi for
CD-writing, the new kernel provides a superior access method that finally supports DMA access when writing CDs. Find out the device name used by your cdwriter i.e. find out the virtual SCSI ID of your device:
# cdrecord dev=ATA: -scanbusOutput:

Cdrecord-Clone 2.01a34 (i686-pc-linux-gnu)
Copyright (C) 1995-2004 Jrg Schilling
scsidev: 'ATA:'
devname: 'ATA'
scsibus: -1 target: -1 lun: -1
Warning: Using badly designed ATAPI via /dev/hd*
interface.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
scsibus1:
 1,0,0 100) 'SONY' 'CD-Writer' '1.0g'
 1,1,0 101) *
 1,2,0 102) *
 1,3,0 103) *
 1,4,0 104) *
 1,5,0 105) *
 1,6,0 106) *
 1.7.0 107) *

As you see SONY CD-WRITER at 1,0,0. The comma separated number you need to pass to command line option as -dev=1,0,0. You can write an ISO image to CD with the following command:
# cdrecord -v -dev=ATA:1,0,0 speed=4 mydata.iso

Where,

• -speed=XX : Specify writing speed.
• -v : Verbose output.
• -dev : The virtual SCSI ID of your device

Here is an example, to create backup of /home/hosting-app/ directory:

a) Create an ISO file that can be opened on both windows and Linux computer:
$ mkisofs -v -o /tmp/happ.iso -R /home/hosting-app

b) Write an ISO (happ.iso) to CD i.e. burn an image:
$ cdrecord -v -dev=ATA:1,0,0 speed=4 /tmp/happ.iso

Read man pages of cdrecord and mkisofs for more information.

wget –limit-rate=24k -e http_proxy=10.151.38.xxx:1234 -np -nc -t 0 -w 1.5 -e robots=off -rbc -i target.txt

http://webchat.freenode.net

http://www.mibbit.com

$ ffmpeg -i lilin.kecil.flv -vn lilin.kecil.ogg

yes it works

Go forth and multiply

Documenting a Debian Linux system in order to reproduce it

Use cases

System Documentation

Every system administrator knows its a good idea to keep documentation about the servers he’s maintaining : you need it to prepare migrations, in recovery scenarios, to plan software roll-out or modifications to a configuration, or to look up configuration details when troubleshooting. Because most of this information is present in the system itself, you can find it there, but that doesn’t help if the server you need to know about has just crashed and you’re trying to rebuild an other one to replace it. Better collect that information in advance.

Most system administrators find this boring. So they put it off, and then forget to do it. Or they start with some documentation, then forget to keep it up to date, so the documentation of the system doesn’t reflect the actual configuration of the system (and when the time comes that you need to reproduce that tweaked daemon config, you don’t remember that final detail that makes it all work).

So, let’s see if we can document a server automatically, and keep the documentation up to date as well. Read the rest of this entry »

Clone It

Reproducing a running Linux system

rsync

rsync is a program that behaves in much the same way that rcp (remote copy) does, but has many more options and uses the rsync remote-update protocol to greatly speedup file transfers when the destination file already exists.

The rsync remote-update protocol allows rsync to transfer just the differences between two sets of files across the network link, using an efficient checksum-search algorithm described in the technical report that accompanies this package.

Some of the additional features of rsync are:

• support for copying links, devices, owners, groups and permissions
• exclude and exclude-from options similar to GNU tar
• a CVS exclude mode for ignoring the same files that CVS would ignore
• can use any transparent remote shell, including rsh or ssh
• does not require root privileges
• pipelining of file transfers to minimize latency costs
• support for anonymous or authenticated rsync servers (ideal for mirroring)

from: manpage of rsync Read the rest of this entry »

If you set DEBIAN_FRONTEND=noninteractive (to stop debconf prompts from appearing) and add force-confold and force-confdef to your /etc/dpkg/dpkg.cfg file, you should have a completely noninteractive package installation experience. Any package that still prompts you for information has a release critical bug (and I say that as both an automation junkie and as a Debian developer).

# vi /etc/apt/sources.list (replace ‘etch’ to ‘lenny’)
# sudo apt-get update && sudo apt-get -q -y –force-yes dist-upgrade
#   vi /etc/apt/apt.conf (if error with proxy server)

but u still prompted with last setting up thats abt your conf… n i think the old conf will be fine coz i assume it worked

***********************

Using apt-get behind a proxy (Ubuntu)
It is quite difficult to use apt-get in ubuntu when you are behind a proxy. To be able to install packages behind a proxy, you need to have a few details:

username: The user name with with you get through the proxy
password: The password with with you get through the proxy
proxyserver: The proxy server
port: The port with with you connect to the proxy server (default is 80)

The proxy can be set in two ways:

Edit your /etc/apt/apt.conf file as root.
Put these line at the end of your /etc/apt/apt.conf file :

Acquire::http::Proxy “http://username:password-AT-proxyserver:port/”

OR
Edit your /etc/bash.bashrc file as root.
Put these line at the end of your /etc/bash.bashrc file :

export http_proxy=http://username:password-AT-proxyserver-DOT-net:port/
export ftp_proxy=http://username:password@proxyserver-DOT-netport/

You can omit the username:password, if your proxy server has no password. That’s all for today! Happy apt-get-ing!

Introduction

A local mirror is useful for a site that has many Ubuntu Servers and Workstations. Apt-cacher is a good way to do this without a massive installation, however, apt-cacher does not allow for much control over what is downloaded and when it is downloaded.

By maintaining an internal mirror, a site can control when updates are grabbed from the Internet. There are two good ways (that I know of) to maintain an internal mirror without using a proxy or apt-cacher.

1. Use Debmirror - Debmirror will allow you to select which parts of the archive (dapper, edgy, edgy-security, etc) you want to mirror. This is useful because it allows a finer degree of control and works well with limited hard drive space.
2. Use rsync - The great thing about rsync is it will grab EVERY file that is in those archives. The problem is that because it does not discriminate, you have the full mirror… all 200 some gigs worth of mirror. So, as more versions come online, the more you will ultimately have to support. As of this writing, my mirror contains hoary, breezy, dapper, edgy, and the packages for the new feisty.
   Read the rest of this entry »