From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3A1F1C82.4E067C65@gsyc.escet.urjc.es> From: Francisco J Ballesteros MIME-Version: 1.0 To: 9fans@cse.psu.edu Subject: Re: [9fans] Crazy idea... or a new project? References: <20001124190548.3A130199EE@mail.cse.psu.edu> <3A1ED86E.82426D1D@gsyc.escet.urjc.es> <01d901c0565d$7a5f7f40$0ab9c6d4@cybercable.fr> <3A1EFBA4.26627FE7@gsyc.escet.urjc.es> <01ff01c0566f$e7df3ee0$0ab9c6d4@cybercable.fr> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Sat, 25 Nov 2000 02:57:22 +0100 Topicbox-Message-UUID: 3203de10-eac9-11e9-9e20-41e7f4b1d025 Boyd Roberts wrote: > > no disk, no fan > > you _always_ boot across the wire and no you don't > do it like NFS diskless boots. for a local boot, I think I could afford a second boot if I changed something. but, again, for a regular terminal booting from the net I agree itīs best to let the server link the kernel (if you changed hw). > > boot with a generic and then load in the other pieces, > on the fly. I just do not like dynamic loading because in the end, I found I (most of the times) had to rebuild my unix kernel whenever I changed hw---you know, forgot to configure an (static) option needed for the new board, or just got the module out of date wrt the kernel, or just the hardware was new and there was no module before, ... > > you wouldn't happen to use linux, by chance? I use plan9 booting from a local disk for almost everything, and I also use linux. You are right in that I was thinking along the way I boot the kernel and not along the way a terminal should boot---otherwise it would have been kind of obvious to do the link in the server instead of booting the terminal twice; but I never thought about it. have a good night. zzZ zz PS: still laughing because of the p-n-p + n-p-n :-)