Bug#31450: boot-floppies 2.1.4 fails to build for m68k
On Mon, 04 Jan 1999 22:00:13 -0800, Michael Schmitz <MSchmitz@lbl.gov> said:
> Adam Di Carlo wrote:
>> Michael, first off, care to help with the documentation of the
>> Installation System? Cf
>> http://www.debian.org/~aph/boot-floppies/m68k/install.html . I
>> need the m68k stuff to be critiqued, corrected, and filled out.
>> You can send me text in ASCII or SGML (linuxdoc), I don't mind.
> For starters, check
> http://www.linux-m68k.org/debian-{atari,mac}.html.
Yes, I'm aware of those.
> There's Franky's
> Amiga install guide out somewhere too, I forgot the URL.
http://www.informatik.uni-oldenburg.de/~amigo/debian_inst.html
And don't forget:
ftp://baltimore.wwaves.com/pub/MacLinux/debian-support/Debian-2.0-Mac-Install.html
> They walk
> users through the details of the actual install but don't cover the
> system requirements and other things in section 2 of your document.
> The machine specific install guides available would fit in section 6
> I guess. I only had a brief look at them but will have a closer look
> (wish I could get it as ASCII text :-)
Well, actually, the whole documents would have to be severely ripped
down and then re-threaded into the boot-floppies Install Manual.
Technical note: I'm using 'SGML marked sections' (cf
http://www.sgml.u-net.com/book/sgml-8.htm) for architecture dependant
portions, i.e., '<![ %i386 [ ... ]]>'.
My focus is on documenting the *official* installation system. Some
of those documents reference stuff which isn't really part of the
official boot-floppies package. This should be fixed. Example: in
the m68k boot disks, basecont.txt is called base-contents, but there's
no code in the actual boot-floppies packge that does this. That's a
bit of a conundrum for me since it is probably done by hand; I can't
just monitor code changes in CVS to pick up changes.
I'm not trying to be a fascist, I'd just like to see the ports come
into the mainstream. If we wanna rename files around, cool, but lets
get the boot-floppies package to actually do that as well.
AFAIK, Mac isn't actually supported by the boot-floppies package, is
it?
>> > - kernel-image-2.0.35 doesn't exist for m68k, substituting
>> 2.0.33. > Eventually, 2.0.36 will be released for m68k, just FYI.
>>
>> You can set whatever kernel you like in the top-level makefile.
>> How is this a bug?
> Yea, that's right, it's a feature. Hardcoded kernel versions later
> on are worse. And the unavailability of a Mac kernel image package
> will force me to fake one in the end.
> I guess I was complaining that these m68k features are still not
> known or considered in the boot-floppies team. I admit that I
> started out without reading the README :-)
Oh, I'm very glad you brought them up. The fact that the
pre-selections mechanism has no facility for dealing with (inevitable)
package drift between ports is a big big bug.
I wish you'd bring up more, since you're clearly doing home things by
hand which I think should be automated.
>> > - rescue.sh expects to find 'root{atari,amiga}.bin' ramdisk
>> images > but fails to pass 'atari' or 'amiga' as argument 1.
>>
>> Oh, that's bad.
> It gets even better; both ramdisks and base system have an
> incomplete set of device files in /dev. Has all sorts of funny side
> effects. Patch (for part of the problems, untested on base yet) and
> description in a separate followup.
Excellent. I hope Enrique wakes up soon and integrates these changes.
BTW, I'm not a code hacker, I'm just a documenter.
>> No clue!
> It's missing. Question goes to Franky: I'll extract the booter from
> the 2.0 set if necessary, ok?
I'd be happy to add this to CVS in the appropriate place, whereever
that may be, if you like. Or go ahead and do it yourself? Do you
work out of the boot-floppies CVS area?
>> > * recode * libc6-pic * recent makedev
>>
>> What's the issue here? I believe these are indeed required to
>> build.
> They are - is it mentioned somewhere, did I miss something? Didn't
> show in James' source dependencies, at least.
> grep Depends control
Depends: libc6-pic, slang1-pic, sysutils, makedev (>=2.3.1-10), newt0.25, newt0.25-dev, popt, zlib1g, zlib1g-dev, recode
> makedev (slink/binary-m68k as of yesterday) isn't recent enough, it
> doesn't know generic-m68k (or generic, for that matter:
> 'generic-generic not known'. Duh.).
If you tell me the needed ver number, I'll be happy to tweak the
versioning for 2.1.5.
> Something strange happens at the end of the whole install (after
> adding some of the devices required manually to speed up the thing):
> I can't log in; the login never prompts for the password but claims
> incorrect login. Any idea on this?
No, I'm just a humble manual writer!
> I'll see that I get a new set of base and rescue disks out tonight;
> don't touch the current set, it's totally broken. New build in
> progress.
Cool, glad to see you guys are agressively working on this stuff.
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: