From owner-freebsd-hackers Mon Nov 23 10:33:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16890 for freebsd-hackers-outgoing; Mon, 23 Nov 1998 10:33:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16885 for ; Mon, 23 Nov 1998 10:33:01 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA23245; Mon, 23 Nov 1998 10:31:30 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdA23238; Mon Nov 23 18:31:25 1998 Date: Mon, 23 Nov 1998 10:30:36 -0800 (PST) From: Julian Elischer To: Robert Nordier cc: freebsd-hackers@FreeBSD.ORG, ambrisko@whistle.com Subject: Re: Changing the load address of the kernel? In-Reply-To: <199811230844.KAA12135@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG check with ambrisko@whistle.com he's done a lot with netbooting. On Mon, 23 Nov 1998, Robert Nordier wrote: > > We do need a more capable netboot replacement, and if Lanworks is > as responsive as they appear to be, then supporting their product > may be an easy route to satisfying this requirement. > > It might be a reasonable solution to make something like this > available as a port; after all, the boot blocks are *expected* to > be somewhat out of sync with kernel development. > > Though I'd quite like to see it working with the new boot1/boot2 > and boot/loader code, in some form, now that Oliver has shown the > way. > julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message