custom kernel in local directory
> But won't that be fixed automatically if they're all on the dpkg -
> i command-line? the ordering based on requirements.
if I install my packages like this:
I have a warning because the directory
/lib/modules/2.6.18-4-bootsplash-686/kernel still exists.
If I say Yes, the installation will stop with the sentence "Ok,
aborting, since modules for this image already exist"
I add my log
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3153 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/debian-live-devel/attachments/20070628/683bf76b/attachment.bin