[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#31450: makedev patch for m68k boot floppies

On Wed, Jan 06, 1999 at 02:05:36AM -0500, Adam Di Carlo wrote:
> On Tue, 05 Jan 1999 02:04:47 -0800, Michael Schmitz <MSchmitz@lbl.gov> said:
> > The version of makedev used in slink (3.1.1-11) doesn't handle the
> > 'generic-m68k' device class. Whatever that class is supposed to
> > contain, the result is that several critical device files are
> > missing:
> > /dev/tty* /dev/sda*, /dev/sdb* /dev/loop*
> > with obvious results when booting the ramdisk or installed base
> > system.  Patch attached.
> Yikes, thanks.  I'll let Enrique handle this; it's over my level of
> competency.  I can't tell if it's a makedev bug or a boot-floppies
> bug; sure looks like boot-floppies is the culprit.

I guess "generic-m68k" should build those devices, like it did in
previous versions. Don't you think so? Oh, wait, there's no generic-m68k
target in /dev/MAKEDEV , just generic-{i386,powerpc} ...

OTOH, I prefer using specific device names on rootdisks.sh and basedisk.sh.
That's more robust than relying on makedev aliases.

> > Other funnies:
> > - mac-us-ext keymap isn't a valid binary map (we had trouble with
> > _incomplete_ binary maps that wiped the kernel keytable on Atari
> > before; this is new).

I guess it's a bug in writemaps. It's strange that it have gone unnoticed
all this time. Perhaps something has changed in the mac keymaps recently?
> > - the 'configure modules' step complains about 'sed: not found',
> > configuring modules is impossible, dinstall keeps prompting that
> > step again and again.
> I thought this was fixed in modconf 0.2.21?

Indeed. Which version are you using for m68k?
Enrique Zanardi					   ezanardi@ull.es

Reply to: