New Zealand Linux

Kdar – backup utility.

Kdar is difficult to load into a Debian (linux) system as you get “cannot find X include” when you compile the source code. After many tries to get the “X include” files and place the X includes in the PATH I found a new way. I found a repository with the deb file.

http://archive.kalyxo.org/pool/main/k/kdar/

<>choose this file
kdar_1.3.2-1_i386.deb
and after download, right click the file and choose install with “Kpackage”.
It will be installed in /usr/bin/kdar.
Luck,
Vince
Last-Modified: 2007-03-07 19:38:50

you need a working network connection and contrib and non-free in your sources.list. Also you need unstable/sid sources for this to work currently.
Open a terminal, su to root and copy the following:

apt-get install build-essential module-assistant &&\
m-a a-i nvidia && apt-get install nvidia-glx nvidia-settings &&\
echo nvidia >> /etc/modules && modprobe nvidia && dpkg-reconfigure xserver-xfree86

— Edit by Pizbit, if you don’t actually want to reconfigure your whole xserver you can ignore the last part (&& dpkg-reconfigure xserver-xfree86 ) and follow the last section below.

done!
Thanks to dpkg on #debian irc.freenode.net

— The below is what I, Pizbit has written. 🙂

Or to use the official NVIDIA package. This will require a internet connection if you don’t already have your kernel headers and the nvidia driver although if you’re using the kernel off the cd and the cd has the kernel headers you’ll save yourself some of your precious BW because apt-get will get the package off the cd assuming it’s in your sources.list etc etc.

Note: If all else fails, read the NVIDIA README!
Go to: http://www.nvidia.com/object/linux.html and download the latest .run file for your CPU. (IA32 for most people). Take note of where you download it to!
Close your x server by logging out – or painfully with ctrl+alt+backspace.
Hit ctrl+alt+F1 , login as root or your normal user then use sudo or su.
You need to actually stop your x server first, this can usually be accomplished by: /etc/init.d/gdm stop Where gdm might be kdm or xdm .(It will only be one of these three)

Most likely you don’t have your kernel headers installed, no worries!:)
Run: apt-cache search `uname -r` header This should return just one package, if it returns more, then, erm, to continue. For example: kernel-headers-2.6.10-3-386 – Linux kernel headers 2.6.10 on 386

Install the kernel headers by: apt-get install ThePackgeName
Chances are you will also need to make a symlink in /usr/src/ cd to this location and: ln -s (I believe it’s always the name of the package you downloaded, in either case it’ll be something clearcut, use uname -r to guide you, the directory should contain this string) linux

eg. cd /usr/src
ln -s kernel-headers-2.6.10-3-386/ linux

Note: If there is already such a symlink it may either have been created for you and you can miss this step or from an older kernel and set of headers, in any case use ls -l linux to see where it comes from, write this down somewhere, rm linux and attempt to make the symlink again.

You may need to: apt-get install build-essential

Run the nvidia installer by going: sh nvidiafile.run
Follow the instructions, it rather easy:) Just say ‘yip’ to everything.
Assuming all goes well, any errors on building the kernel module if it needs too are probably because you don’t have the build-essential package installed or the kernel headers, install it and run the installer again.

Now you need to configure your x server to actually use the driver. If you use xorg you will want to edit: /etc/X11/xorg.conf If you use xfree edit: /etx/X11/XF86Config-4.conf
Where you see all the Load “blah” lines(near the top), put a # at the begining of these lines if you have them(Doesn’t matter if you don’t have them)

Load “dri”
Load “GLcore”

After that, make sure there is in the same section:

Load “glx”

The next step is to actually use the driver, scroll down to where it mentions your video card, it probably already has:

Driver “nv”

Change this to:

Driver “nvidia”

Load up your xserver again. /etc/init.d/gdm (or kdm, xdm) start
The nvidia installer puts it’s README into /usr/share/doc/NVIDIA_GLX-1.0/ , if you get lost have a peek. 🙂 Last-Modified: 2007-03-07 19:38:50

This is handy if you just got yourself that new xxxTB hard drive.

Firstly, BACKUP!
This is one of the most important things to do, you never know when you may screw something up royally.

Make sure your new hdd and old one are both in the machine.

This is only a basic overview for the purposes of a tutorial. It assumes you dont have multiple partitions for /var or /usr or /boot or any other and that all your data is only one the one partition (basicly the home user not a server).
Be aware that if you have an entirely new system and have gone from IDE to SCSI then you may want/need to recompile your kernel before you do this to support the new drive.

These are the commands you probably want to do. /dev/hdxxx is the destination hard drive.

fdisk /dev/hdxx – This is to partition the disk

mkfs -t ext3 /dev/hdxx – This is to format it

mkdir /target

mount /dev/hdxx /target – Mounting the new drive.

rsync -a --exclude="/dev" --exclude="/proc" --exclude="/sys" --exclude="/target" / /target/ – this copies your data accross

mkdir /target/{proc,dev,sys}

(Note: you can probably cp -a /dev across)

cp /dev/MAKEDEV /target/dev/ – this file is needed for making device nodes

cd /target/dev

Now you need to make the device links. This is done with a script called MAKEDEV that you just copyed accross.
./MAKEDEV will give you the options you need/want.

./MAKEDEV generic-i386 should do the basic nodes

Now you have to edit a couple of things.
vi /target/etc/fstab
This only really needs to be done if the hard drives are going to change places on the ide chain.
Please do note that Redhat/Fedora uses labels instead of partitions, label your partitions if you wish to continue with this method, alternativly change the label for the actual device name.

vi /etc/lilo also if needed for the same reasons.

Now for the tricky bit, you can copy the masterboot record with something that looks like this
dd bs=512 count=1 if=/dev/hddxx(oldone) of=/dev/hdxx(newone)

However, apon saying this i have found it to break my partitioning before on some hard drives.
So Im more inclined to just reboot and using another linux install disk or floppy to boot.

I find slackware disk excellent as a rescue disk, when it comes up to the lilo screen i just type
Lilo: linux root=/dev/hdxx(new hard drive)

Debian cd can be booted with,
Lilo: rescue root=/dev/hdxx(new hard drive)

etc. Most distros will do it, just read the help.

Reboot with rescue cd and run lilo or dd the MBR (which i find to screw up sometimes)

Then login as root and rerun your lilo or grub onto the new hard drives MBR.
Last-Modified: 2007-03-07 19:38:50