From owner-freebsd-current Wed Apr 22 20:00:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14595 for freebsd-current-outgoing; Wed, 22 Apr 1998 20:00:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14519 for ; Thu, 23 Apr 1998 03:00:27 GMT (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (rtfm [199.232.255.52]) by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id DAA04375 for ; Thu, 23 Apr 1998 03:00:17 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id XAA01282 for current@freebsd.org; Wed, 22 Apr 1998 23:00:16 -0400 (EDT) From: Mikhail Teterin Message-Id: <199804230300.XAA01282@rtfm.ziplink.net> Subject: Re: ELF kernels: When? In-Reply-To: <199804222032.NAA00578@dingo.cdrom.com> from "Mike Smith" at "Apr 22, 98 01:32:09 pm" To: current@FreeBSD.ORG Date: Wed, 22 Apr 1998 23:00:16 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" So, does anyone know enough about bootblocks to look at integrating => NetBSD's? [...] => They have done a significant amount of work in this area it seems, => and they already have a two-stage design. Trying to squeeze every => last bit out of the current blocks seems futile.. =The only thing "wrong" with their code is that their second stage =bootblock has a blocklist for the third stage. That's Ugly. Yet its there. Please, excuse me wondering into an area I have very limited understanding of, but why can not FreeBSD be booted by NetBSD bootblocks? Would not this be a sensible step to take? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message