Sure, do update but don't remove the old kernel. That way you'll be able to boot the old one if things go haywire. Maybe boot a live CD with the target kernel version first.

Yes, safest way would be to update using the backports.org repo.

This is not an answer to your question, but if I may suggest, try dist-upgrading to Testing (Squeeze). I find it very stable despite it being 'Testing'. And it's running with the 2.6.30-2-686 kernel.

I'm using Squeeze on my HP DV6000. And I've got wireless and all working. It's a thought.

I,d like to thank u all for ur useful comments,but wht abt Debian Testing(Squeeze) ?.is it stable that much ?,actually i,m very satisfied with Lenny stable release after updating a lot of software and all drivers work properly,except Microphone jack and bluetooth as well, the more important reason is i like KDE 3.5 much more that KDE 4
cuz i feel it's much faster and more stable,wht do u think abt that ?.
any body can give us more info abt his experience with Testing and wht's the ranges and level of problems that he,d faced after moving to it ? and if u suggest to stay with stable version would u plz provide me with a brief explanation how to update the kernel with the right and safe way?.
any additional info,links will be very useful .
thx in advanced

If you are happy with Debian stable I would strongly suggest you keep using it and not install testing. If after some time you have learned some more and found that you really do want to run testing you can reconsider. Basically, I if you are asking questions like how to use backports, I think you are probably not ready for testing.

Anyway to answer your question about kernels in backports: right now it seems the newest is 2.6.30.
http://packages.debian.org/search?su...inux-image-2.6

If this new enough for you, add the following line to the file /etc/apt/source.list
The run
The 2nd and 3rd command will probably return nothing, indicating that there are no 2.6.31/32 kernels in the repo at the moment.
The last command should list some 2.6.30 kernels, I don't know exactly which since I don't know what your machine arch is.

For example, on the Debian stable machine I have access to this would show
Then (assuming your arch is amd64) do
If 2.6.30 really is too old for you I can show you how to package a 2.6.32 kernel for your stable system, using the Debian method. Don't worry it is *much* easier than it sounds... but that is for another post.

Cheers,

Evo2.

As to the stabiliy of Squeeze, I can attest to it. I've been using it for many, many months. The only problem I had with Squeeze was when I tried to upgrade to Grub2. And I found I didn't have to. Screwed my OS big time.

But like evo2 said, if your happy with Lenny, stick with it. Not a thing wrong with that.

One of the best link I can provide is this one:

http://www.debiantutorials.org/

All sorts of help listed. From wireless to streaming video and beyond. The forum is off line. But you can still search it for tips and how-tos.


About KDE, I don't use it. Can't comment. I prefer Gnome. All manly men use Gnome. It's a know fact.

thx very much,actually i already have backports added to my sources.list file.
Lenny stable is good for me,but recently i faced some issues that made me to consider testing,additionally i got tired updating software shipped with Lenny that as u know they have very old versions.
have u used Testing yet or still with Lenny ?
can u tell me precisely wht are the knowledge i have to get be4 getting to Testing,may be i already have
finally,i,ll appreciate it so much if u explain how to install the latest version of the kernel 2.6.32 ,i downloaded the source from kernel.org ,but i didn't try yet to play with it ,so tell us wht u think brother.
greetZ.

actually,i,m happy with Debian in general ,but u know i like my packages up2date always,so the benefit of Testing that it has more newer versions of packages and has KDE4 , i said be4 that i like KDE 3.5 much than 4 but,but still don't have a problem to use 4 as well .
i,m form KDE party and don,t use Gnome,u know every one has his own mind and thinking ,but we still(me and u) in the same square(Debian).
greetZ

Compile a kernel: it'll put hair on your chest ;-)

In the following in any <code>block</code>, commands prefixed with "#" need to be performed as root (with via su or sudo). Commands not prefixed with "#" should be performed in your usually user account.

Here we go.

It is probably best to use the kernel source already patched by Debian:

After downloading it, install it:
This will put a file in /usr/src

Now make sure you have installed the kernel-package package. This will give youthe tools you need to build a debian pacakge of your new kernel
I've included a few extra packages in case you don't already have them installed.

At this point I should tell you to look at /usr/share/doc/kernel-package/README.gz
This file is the reference you should use if there are gaps in my instructions.

Now you are almost ready to build the kernel. Usually you should only do things as root when you really need to: ie you should not compile code as root. An easy way to get around this is to put yourself in the src group and make /usr/src writable by the src group:
Note the last two commands may not be needed as the system may already be set up that way (I can't remember the default). For the change in the first command to take effect you will have to log out and back in again.

Now it's time to build the kernel.

Now you should see a new Debian package called something like
Install it with
Ok and that *should* do it. Let me know if you need me to further explain any of the steps. For example "make oldconfig" or "make menuconfig".

Actually, I use Unstable on my laptop and desktop, but I use Lenny on my home server. I use stable on the home server since it streams media to my TV, and if I'm in the mood to sit down and watch TV or listen to music I am not going to be in the mood for fixing servers.
Good question and I don't really know the answer. However can tell you roughly what I did: I think I used Stable for about a year every day before I migrated to testing, and then about another year with testing before I migrated to unstable. Prior to that I had about a year or two experience as a user of different unix systems.

Cheers,

Evo2.

1 members found this post helpful.

The problem with Testing is that it tends to break.

Right now kde and gnome as well as a few other things can't be installed in testing without also having unstable in your sources.list.
Your safest bet is to stick with stable and use the backports.org repo for things that you need newer packages.

Different branches is one of the many strong suites of Debian. One can be very conservative (Stable/Lenny), somewhat daring (Testing/Squeeze) or 'Oh The Hell With, I'm Going For Broke! (Unstable/Sid).

I've been using Testing since it's Etch days. That is to say when Sarge was the official Stable version and Etch was considered Testing. Can't say it's been a trouble free trip. But for the most part, it's been a rather smooth road. Especially if one waits a few months after a Stable release to get into the new Testing

Nothing wrong with Stable. While the apps do seen to be a tad long in the tooth they are rock solid and trouble free. It's perfect for the conservatives of us. Certainly the right choice for management critical use.

Testing is my personal preference because the apps are more up to date. My Squeeze OS had Gnome 2.28 and Iceweasel (Firefox) 3.5.5. It has a tendency to hic-up once in a while. Nothing so major that the next update won't fix. And that's all I've had to do to fix things. If you could call it fixing. To date I've only had one problem and that was with the new Grub2. Something I didn't know a thing about and something I shouldn't have touched. I'd recommend it for the knowledgeable Linux user or the daring among us. Also for home use.

As far as Unstable, well, that's for masochist. (Ducking his head). Don't shoot me Sid users, please. Sid is just that, too unstable. I don't even like to play around with it. But that's just my opinion. Unstable is the right choice for those who like to jack around with their OSs all the time. It's a puzzle for those who like to delve, and dig and constantly tweak their operating system.

And so there you have it. Pick your own poison and have fun.

Don't worry, I don't carry a gun.

Ask not what Debian can do for you, but what you can do for Debian!

You are missing one very important reason for running unstable: contributing to Debian. It is the unstable users who are the first line of quality control for new packages: finding bugs and submitting bug reports. Having two "non-stable" levels of Debian: Unstable and Testing
is one of the reasons Debian is able to make such rock solid releases. If there was only one "non-stable" (call it testing or unstable or whatever you like), it would be to difficult to introduce significant changes and it would also make it very difficult for the distro to stablise for a release.

So I think it is extremely important that both Unstable and Testing have users.

Cheers,

Evo2.

You are absolutely correct in what you say here.
But please don't forget, the exposure on the stable/testing/unstable issue was meant for a guy who asked a question, what he should be prepared of when switching from stable to testing. In other words: "I just learnt swimming in the pool in the garden, what will I encounter (and is it dangerous) if I now jump into the lake farther away in the meadows?"
So, at this moment, you can't expect him to jump into the lively river that feeds the lake and ask him to give feedback as to where there are disturbing rocks, waterswirls and whatsoever.

Besides that, but please don't feel stept on your toes with the following remark, maybe 2 to 3 percent of the real users would be able to so clearly define and describe a bug, that the programmer (or the maintainer) of the package even understands, what the user really meant to say and where he should search for the solution in the numerous code-lines.

Phiebie, you hit the nail square on the head! Nothing successes like success. Here's a new comer to Debian and the last thing he needs is to be thrown into the deep-end. Lets try wading on the beach first. See if the water is fine. Give him some water wings and let him splash around. And while we're at it, lets get him to view streaming videos and audio and visit sites with Flash and all that good stuff everybody wants to do.

Long time Linux user forget about all the hair pulling and teeth gnashing we went through way back then to get our systems working. Most folks don't want to do that. And not a damn thing wrong with that. Does any Windows user what to go through that? Why of course not. Now, with Linux, that can't be helped. A little trial and tribulation is to be expected. Still, lets make the journey as painless as possible. Let's get the young man a system that works. No need to suggest sidux or Sid or Gentoo or Linux From Scratch or for that matter Slackware.

Of course while these distro will really help in learning about the true guts of Linux. Let's hold off on that for the time being. Who in hell wants to be a Computer Major? Let surf the web first. No, lets get the distro install and working first and tweaked out. Then we can delve and dig and poke and prod. Lets save the hair pulling and teeth gnash for later.