Re: debian boot CDs & G5
Dear Sven,
> Well, having it automatically called on the subarches that need it.
You should be able to put it in the postinst_hook in
kernel-img.conf(5). If not, file a bug report, please.
> Yeah, sure, but i think there is a misunderstanding. the duty of
> discover is exactly to find the modules needed by your system and load
> them. Exactly the same thing mkinitrd does (or more exactly the the
> /bin/init script of the initrd), just in a bigger scale.
There are two subtle differences that make discover less than ideal.
First, discover does both the finding and the loading in one step,
while we want mkinitrd to find the modules and initrd to load them.
Second, discover indiscriminiately attempts to load drivers for all
the hardware, while we only want the root filesystem.
> Remember that discover is used in the debian-installer initrd, so
> why should it not also work for us ?
Because the debian-installer initrd is generic, while kernel-image
initrds are system specific.
> Yeah, until some random user plugs in a random scsi or ide or
> whatever card you had not thought about, and then you are screwed.
> It works for mainstream hardware, but is not robust.
It worked on the G5 out of the box. After I fixed it on my Pismo, it
also worked on every other Powermac I've tried since.
Regards, Jens.
--
J'qbpbe, le m'en fquz pe j'qbpbe!
Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!
Reply to: