[2968] in SIPB_Linux_Development
Re: OK, so how does one actually build this boot floppy?
daemon@ATHENA.MIT.EDU (Karl Ramm)
Sun Sep 10 00:50:24 2000
To: Sam Hartman <hartmans@MIT.EDU>
Cc: linux-dev@MIT.EDU
From: Karl Ramm <kcr@1ts.org>
Date: 10 Sep 2000 00:50:15 -0400
In-Reply-To: Sam Hartman's message of "Sat, 9 Sep 2000 22:33:58 -0400 (EDT)"
Message-Id: <uusu2bodf5k.fsf@ORTHANC.MIT.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
dunno, looks like the build tree didn't copy right.
kcr
Sam Hartman <hartmans@MIT.EDU> writes:
> --text follows this line--
>
> In misc/src/trees, I run
> make do-update
>
> Part of the output includes:
>
> Computing ../../../RedHat/instimage/modules dependencies... depmod: *** Unresolved symbols in nfs.o
> depmod: nlmclnt_proc
> depmod: *** Unresolved symbols in parport_cs.o
> depmod: parport_pc_ops
> done.
> Balling ../../../RedHat/instimage/modules modules... done (saved 2104k)
> Computing pcmcia/modules dependencies... depmod: *** Unresolved symbols in nfs.o
> depmod: nlmclnt_proc
> depmod: *** Unresolved symbols in parport_cs.o
> depmod: parport_register_port
> depmod: parport_pc_ops
> depmod: parport_proc_unregister
> depmod: parport_proc_register
> depmod: parport_quiesce
> depmod: parport_unregister_port
> done.
>
>
> How have we ever gotten a floppy that mostly works.
