On Thu, Sep 14, 2006 at 07:30:39PM -0700, Brian Morris wrote: > On 9/14/06, Christian T. Steigies <[EMAIL PROTECTED]> wrote:
> >The initrd is not used on m68k, so don't worry about copying it onto the > >mac > >OS side or giving it as a boot parameter. All necessary drivers are built > >in, everything else can be loaded from the modules when you installed the > >deb. > > is there a reason you are doing this, which seems to > complicate the hardware support ? Doing what, not using initrd? How does that complicate hardware support? Using initrd complicated software support, AFAIK initrd does not work on SCSI systems yet, if you have patches for that, we'd be happy to know. It does not really matter where the drivers come from, built into the kernel, loaded as modules or loaded from the initrd. With an initrd, you save some space in the kernel, but I prefer to have a bootable kernel over saving a few kb. What I could do is disable building the initrd for m68k, that is supposed to be possible, but I haven't found out how. I don't really care, so we waste a few kb on the harddisk of the user, but at least we now have working initrd tools on m68k, so in case initrd should ever work on m68k, we could easily switch over and build smaller kernels. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
