[mdlug] KDE 4

[bob dion]

On my Sidux system the kernels are all installed with their version 
numbers. The scripts and all the modules, and an entry in grub. If the 
new kernel does not boot I can select and of the other 4 - 5 older 
kernels I keep around. I'm currently running 2.6.28.x, just the other 
day I removed the last of the 2.6.25 kernels.

As for upgrading, Sidux is a rolling distro. I installed it over a year 
ago and do dist-upgrades on a monthly bases. Yes I have had to compile 
some packages like gimp2.6.3 and autopano for hugin and I have been able 
to find compatible deb packages for other photo software I use like 
rawstudio and qtpfsgui.

As a side note, I use checkinstall when compiling, it take over the 
make-install process, creates a deb packages and installs through the 
dpkg system.

BD

Raymond McLaughlin wrote:
> The thing that intimidates me about all this auto-magical; stuff is lack
> of control, and just assuming that it will all work right. I mean when
> it compiles and installs, does it replace your current (working) kernel
> with one that you hope will boot? In the old days I would give the new
> kernel a name like "vmlinuz-test-001", and put it in the boot menu as
> *NOT* the default boot, so I could test it without depending on it
> working. I could always boot the old kernel and try again if something
> was not right.
> 
> Does the new system really assume that every kernel compiled will boot?
>