From owner-freebsd-current Sun Jan 20 20:19: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 7392F37B402 for ; Sun, 20 Jan 2002 20:18:58 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g0L4IcD62237; Sun, 20 Jan 2002 23:18:38 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 20 Jan 2002 23:18:37 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Glenn Gombert Cc: freebsd-current@FreeBSD.ORG Subject: Re: Diskless Boot Working in -Current ?? In-Reply-To: <3.0.6.32.20020120142635.00da3b28@imatowns.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 I use diskless booting daily on 5.0-CURRENT, and after some tweaks to rc.diskless[12] (now committed) it works just fine. In 5.0-CURRENT, FFS is used directly over malloc disks (md) to support local storage. You should be able to configure netbooing on 5.0 in much the same way as RELENG_4. Are you having a specific problem, or is this just an "is this possible?"? Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Sun, 20 Jan 2002, Glenn Gombert wrote: > I have several kernels built using v4.3 that boot fine over an > etherboot/NFS network but a kernel built using GENERIC (with the necesary > options added to diskless booting, does not seem to boot), also the option > 'MFS' (Memory File System) seems to have been removed from -CURRENT for > some reason.... this is necessary for DISKLESS NFS booting isn't it ??..... > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message