Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 Apr 2000 18:48:30 +1000
From:      Jonathan Michaels <jon@welearn.com.au>
To:        Kris Kennaway <kris@FreeBSD.ORG>
Cc:        freebsd-small@FreeBSD.ORG
Subject:   Re: Network booting (Re: NFS)
Message-ID:  <20000404184828.E1768@phoenix.welearn.com.au>
In-Reply-To: <Pine.BSF.4.21.0004032310260.86883-100000@freefall.freebsd.org>; from Kris Kennaway on Mon, Apr 03, 2000 at 11:16:25PM -0700
References:  <20000403013528.A1954@minix.cx> <Pine.BSF.4.21.0004032310260.86883-100000@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 03, 2000 at 11:16:25PM -0700, Kris Kennaway wrote:
> 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).

taking this one step further and to help those who live in
climates where th government is some what "cryptographically
challanged", given that most countries have (or are having)
setup freebsd usergroups that have an attendant array of ftp-,
mail-, mailinglist-exploder- -servers and so on it probably
wouldn't be that hard to establish (and provide ar mirror
driven update),

bootserver.au.freebsd.org.au

where one could replace the ".au." with the iso id for thier
country. this would preclude problems with "importing
 cryptographic materials which is becoming if not already a
serious national criminal offence (punishable with time in
prision).

this way it is possible to get the stuff you need (i am talking
about the whole picture not just the as required services from the
bootserver.*) from one clearly identifiable that is clearly and
explicitly within the national boundries of the users
respective country.

also one other side effect would be the lessening of load on
teh national gateway servers, well ok not fro them but the
enduser might get better performance by not having to use
congested routers like mae-east, mae-west etc etc. here in
australia we go through mae-west i think and most of teh time
ftp's etc drop out is because mae-west is struggleing for
breathing space .. ok someting like that.

warm regards

jonathan

please excuse my less than technical explanation i'm having
more than my usuall quota of thinking and remembering problems
today .. it is so bad that i have noticed that someting is
wrong.

-- 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-small" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000404184828.E1768>