From owner-freebsd-current Mon Feb 17 5:12:37 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 182F237B401 for ; Mon, 17 Feb 2003 05:12:36 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C19343FAF for ; Mon, 17 Feb 2003 05:12:35 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0008.cvx21-bradley.dialup.earthlink.net ([209.179.192.8] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18kl47-0000eA-00; Mon, 17 Feb 2003 05:12:12 -0800 Message-ID: <3E50DF57.F08E208E@mindspring.com> Date: Mon, 17 Feb 2003 05:10:47 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Makoto Matsushita Cc: riccardo@torrini.org, freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD/i386 kern.flp flooding again References: <20030216204544U.matusita@jp.FreeBSD.org> <20030216210359E.matusita@jp.FreeBSD.org> <20030217092427.GA20732@trudy.torrini.home> <20030217184245R.matusita@jp.FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4621ddb3e7b406450fc082436e73b975b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Makoto Matsushita wrote: > riccardo> Is this stuff really needed on a boot floppy? Maybe we can leave > riccardo> only I486_CPU? What about removing also device eisa and/or bpf? > riccardo> (I'm just curious, don't expect to be an expert :-) > > The bpf is required for DHCP client. We cannot remove it, or cannot > network install FreeBSD via fetch-IPv4-address-by-DHCP-only network. > I doubt if we can already livin' IPv6-only network :-) IPv6 is supposed to support stateless autoconfiguration, and not need DHCP to get you a routable address. IPv4 can do this too (via link.local), but IPv4 pretty much requires either a NAT box to participate in making the non-routable addressed assigned internally work, or DHCP is needed. Worst case, you can manually configure a routable address, so that's an option, if there's nothing else that can be pulled out safely. Probably it would be worthwhile to leave any driver not in the boot or install path on a separate floppy; I thought that was already the case? > I have no idea about eisa; I don't have any (PCs and cards). But if > eisa is removed, we lost some users who has EISA-based PCs so it may > be avoided. > > Note that both devices cannot load as a kernel module at this time; > removing these devices means that we cannot use them for installation. Anything in the boot path, by definition, can't be a module, without orphaning some user or another. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message