[mdlug] KDE 4

[Raymond McLaughlin]

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?

Robert Adkins wrote:
> 
> 	A great deal has changed in the world of compiling/installing a
> Linux Kernel. It's practically automagic, in that the scripts not only
> create a truly easy to understand GUI, it also reads in all the settings
> from your existing kernel, including the location it resides and modules it
> requires AND even reads in your boot loader. Once finished with setting up
> the configuration, the compiling process will install the kernel AND modify
> your bootloader for the new kernel.
> 
> 	This is worlds beyond the old days. I wish that I had access to such
> tools way back in the heady days of Red Hat 5.2... I would have been
> compiling my own kernel for years now.
> 
> 	-Rob
> 
> 	"Meh, kids these days and there newfangled GUI Kernel Compiling and
> Configuring tools... Get offa my lawn..." - Me