On Thursday, 2 October 2008 20:43:00 Markus
Am Donnerstag, 2. Oktober 2008 schrieb Andreas
> On Thursday, 2 October 2008 10:37:40 Dave Plater wrote:
> > Thanks very much for the explanation. I'll keep an open eye for
> > problems and open a bug.
> Thanks! I hope things will be pretty painless.
Unfortunately there is at least one problem. The filesystem driver
support of the base package is also stripped down to ext3 and jbd.
Yes, the base package is supposed to be very minimal, so that you can
use it for building small virtual machine images.
If you are running a system with rootfilesystem
not being one of these
filesystems, the installation of the kernel base package will throw an
error message, because mkinitrd cannot include the filesystem driver
for that filesystem into initrd.
Thanks, I didn't notice that mkinitrd handles different missing modules
differently. (It only warns for some other modules; I did not think of
testing this case as well.)
This is fixed later when installing the default
Yes, that's the expected result.
I know of no good way to tell when an initrd should be created and when
not: in some cases the -base package will be enough, in others the main
package, and in still others, the -extra package will be needed. In the
%post script we don't know if this is the last package, or if another
package will follow. So the best we can do, I believe, is to warn and
skip ahead if mkinitrd finds that modules are missing.
That's ugly. I see it's not a trivial task, so I suggest to ask the
packaging experts (e.g. on opensuse-packaging) on how to fix this in a