From owner-freebsd-small Mon Apr 3 23:16:27 2000 Delivered-To: freebsd-small@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 1CCFB37B813; Mon, 3 Apr 2000 23:16:26 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA87391; Mon, 3 Apr 2000 23:16:25 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 3 Apr 2000 23:16:25 -0700 (PDT) From: Kris Kennaway To: Jonathan Towne Cc: Greg , freebsd-small@freebsd.org Subject: Network booting (Re: NFS) In-Reply-To: <20000403013528.A1954@minix.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Apr 2000, Jonathan Towne wrote: > Yes, as a matter of fact, I did all sorts of fun stuff with it.. things like > running XFree86 with KDE and windowmaker and Mozilla, all over NFS.. rather > trivial to get working, basically, just get a network connection and > "mount_nfs server:path /mountpoint" Changing the subject, but something that would be REALLY COOL to do is to have a PicoBSD floppy which does nothing but establish a secure network connection to a remote server (e.g. over the internet) and downloads signed KLDs, packages, configuration files, etc into a MFS to bootstrap. For example, except for the XF86Config file, you could fairly easily make a "take-anywhere" X client floppy this way. In principle we could even make a bootserver.freebsd.org which hands out such signed components to a client on request (making the regular ports collections packages cryptographically signed would be a good first step). Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message