Re. Booting from CF/stik is interesting.

[no.to...@gmail.com]

> Now if a system can respond to Ctrl/Alt/Del ,
> it's quiet far into the boot process.

I think I'm wrong there.
Because Ctrl/Alt/Del is even active from the BIOS
stage of booting on this netbook.

K which is slak13-based, has knl2.6.29.4 & initrd.gz
whereas slak13 has 2.6.29.6 and NO initrd*,
and they both fail with messages <can see your
sda1,2,3,4 hard-disk/s but can't see your CF or USBstik>.

Whereas apparently linux has the Ctrl/Alt/Del action
set via inittab, and my K can do Ctrl/Alt/Del whereas
my slak13 can't, I wrongly/simplistically assumed that
K had progressed further than slak. But K can, without
inittab, do Ctrl/Alt/Del.

Here's K's 'last trace': starting support for loop device,
cdrom fs, squashfs, aufs with brs=1, linux fs, win fs, USB,
PCMIA Cardbus; creating /dev for block devices.

`lsmod` shows: ...aufs, squashfs,sqlzma,unlzma <-last one

Is there any easy way to 'examine/determine what
device-driving capabilities a krnl & initrd have'?

== TIA.