From owner-freebsd-small Sun Aug 29 0:45:52 1999 Delivered-To: freebsd-small@freebsd.org Received: from pc33.besa.nchu.edu.tw (pc33.besa.nchu.edu.tw [140.120.200.33]) by hub.freebsd.org (Postfix) with ESMTP id C8629150D8 for ; Sun, 29 Aug 1999 00:45:37 -0700 (PDT) (envelope-from baka@pc33.besa.nchu.edu.tw) Received: (from baka@localhost) by pc33.besa.nchu.edu.tw (8.8.6/8.8.6) id PAA10388 for freebsd-small@freebsd.org; Sun, 29 Aug 1999 15:30:01 +0800 (CST) Date: Sun, 29 Aug 1999 15:30:01 +0800 (CST) From: User Baka Message-Id: <199908290730.PAA10388@pc33.besa.nchu.edu.tw> To: freebsd-small@freebsd.org Subject: subscrive Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Aug 30 2: 3: 0 1999 Delivered-To: freebsd-small@freebsd.org Received: from ernst.netinsight.se (ernst.netinsight.se [194.16.221.130]) by hub.freebsd.org (Postfix) with SMTP id 914C714E18 for ; Mon, 30 Aug 1999 02:02:50 -0700 (PDT) (envelope-from johan.rydberg@netinsight.se) Received: from netinsight.se (unverified [194.16.221.239]) by ernst.netinsight.se (EMWAC SMTPRS 0.83) with SMTP id ; Mon, 30 Aug 1999 11:02:32 +0200 Message-ID: <37CA48D4.36D3A318@netinsight.se> Date: Mon, 30 Aug 1999 11:03:16 +0200 From: Johan Rydberg Organization: Net Insight AB X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i686) X-Accept-Language: en MIME-Version: 1.0 To: randal@comtest.com Cc: freebsd-small@FreeBSD.ORG Subject: Re: Problems with BSD in embedded system! References: Your message of "Thu, 26 Aug 1999 14:16:35 +0200." <37C53023.51BE4510@netinsight.se> <199908280346.RAA25163@mail.hits.net> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Randal S. Masutani" wrote: > > On 26 Aug 99, at 11:19, Mike Smith wrote: > > I tested the STPC Client also, but it was on the older board just before > the Gloria board. It worked fine with FreeBSD/PicoBSD, but ISA and PCI > performance really sucked. I did not encounter any of the problems you > have. Make sure of any BIOS settings that may cause problems, you may > want to turn off cache to test that. Also you may need to check how the > STPC chip and Super I/O chips are programmed, they may need to be > reprogrammed to a setting that FreeBSD may work with better. We use a bootstrapper developed by ourself. Maybe that is the problem. > We finally gave up on the STPC and decided to go with the AMD ELAN 410 > chips we had better performance with them. Oh. I see. I will mention this to our hardware designer. -- Johan Rydberg Software System Designer Net Insight AB johan.rydberg@netinsight.net Ingenjörsvägen 3 http://www.netinsight.net SE-117 43 STOCKHOLM phone:+46-8-685 04 16 Sweden fax: +46-8-449 22 40 mob: +46-704-53 57 21 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Aug 30 2: 3:56 1999 Delivered-To: freebsd-small@freebsd.org Received: from ernst.netinsight.se (ernst.netinsight.se [194.16.221.130]) by hub.freebsd.org (Postfix) with SMTP id D19AD15337 for ; Mon, 30 Aug 1999 02:03:51 -0700 (PDT) (envelope-from johan.rydberg@netinsight.se) Received: from netinsight.se (unverified [194.16.221.239]) by ernst.netinsight.se (EMWAC SMTPRS 0.83) with SMTP id ; Mon, 30 Aug 1999 11:03:43 +0200 Message-ID: <37CA491C.36EFA76D@netinsight.se> Date: Mon, 30 Aug 1999 11:04:28 +0200 From: Johan Rydberg Organization: Net Insight AB X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i686) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: freebsd-small@freebsd.org Subject: Re: Problems with BSD in embedded system! References: <199908261819.LAA02929@dingo.cdrom.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > Almost anything. > > We understand that the STPC has problems running FreeBSD; we haven't > been able to resolve the issues we have with the sample board we have. > > But the symptom you're describing is quite different; the only way you > are going to be able to resolve your issue is to build a kernel with > DDB enabled, break to the debugger at the top of init386 and then > single-step your way through until it falls over. How will this be done, since the IDT is intialized within init386. -- Johan Rydberg Software System Designer Net Insight AB johan.rydberg@netinsight.net Ingenjörsvägen 3 http://www.netinsight.net SE-117 43 STOCKHOLM phone:+46-8-685 04 16 Sweden fax: +46-8-449 22 40 mob: +46-704-53 57 21 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Aug 30 10: 5:26 1999 Delivered-To: freebsd-small@freebsd.org Received: from dingo.cdrom.com (castles529.castles.com [208.214.165.93]) by hub.freebsd.org (Postfix) with ESMTP id 01B2C1533F for ; Mon, 30 Aug 1999 10:05:23 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA20930; Mon, 30 Aug 1999 09:58:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908301658.JAA20930@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Johan Rydberg Cc: Mike Smith , freebsd-small@freebsd.org Subject: Re: Problems with BSD in embedded system! In-reply-to: Your message of "Mon, 30 Aug 1999 11:04:28 +0200." <37CA491C.36EFA76D@netinsight.se> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 30 Aug 1999 09:58:53 -0700 From: Mike Smith Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We understand that the STPC has problems running FreeBSD; we haven't > > been able to resolve the issues we have with the sample board we have= =2E > > = > > But the symptom you're describing is quite different; the only way yo= u > > are going to be able to resolve your issue is to build a kernel with > > DDB enabled, break to the debugger at the top of init386 and then > > single-step your way through until it falls over. > = > How will this be done, since the IDT is intialized within init386. = The same way it always works. If you can't single-step through parts = of it, then you will need to stick some form of debugging output in = there (eg. writes to a known port) and watch that in some other fashion. -- = \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Aug 30 18: 1:59 1999 Delivered-To: freebsd-small@freebsd.org Received: from richardson.apana.org.au (richardson.apana.org.au [203.3.126.216]) by hub.freebsd.org (Postfix) with SMTP id E036914E7E for ; Mon, 30 Aug 1999 18:01:41 -0700 (PDT) (envelope-from young@richardson.apana.org.au) Received: from jdy [203.3.126.129] by richardson.apana.org.au [203.3.126.216] with SMTP (MDaemon.v2.7.SP4.T) for ; Tue, 31 Aug 1999 10:44:55 +1000 Message-ID: <009801bef34a$a4eede80$857e03cb@jdy> From: "Young" To: Subject: subscribe Date: Tue, 31 Aug 1999 10:49:11 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-MDaemon-Deliver-To: freebsd-small@freebsd.org X-Return-Path: young@richardson.apana.org.au Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe young@richardson.apana.org.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Sep 1 2: 7: 2 1999 Delivered-To: freebsd-small@freebsd.org Received: from hitpro.hitachi.co.jp (hitpro.hitachi.co.jp [133.145.224.7]) by hub.freebsd.org (Postfix) with ESMTP id 21CE814D32 for ; Wed, 1 Sep 1999 02:06:59 -0700 (PDT) (envelope-from akoba@ebina.hitachi.co.jp) Received: from newton.ebina.hitachi.co.jp by hitpro.hitachi.co.jp (8.9.3/3.7W-hitpro) id SAA26931; Wed, 1 Sep 1999 18:06:48 +0900 (JST) Received: from gpc.ebina.hitachi.co.jp (root@gpc.ebina.hitachi.co.jp [158.214.169.213]) by newton.ebina.hitachi.co.jp (8.9.0/3.7W-EBINA) with ESMTP id SAA20985 for ; Wed, 1 Sep 1999 18:06:48 +0900 (JST) Received: from akoba.ebina.hitachi.co.jp ([158.214.173.134]) by gpc.ebina.hitachi.co.jp (8.9.1/3.7W-EBINA-local) with SMTP id SAA20230 for ; Wed, 1 Sep 1999 18:06:47 +0900 (JST) Message-Id: <199909010905.AA00017@akoba.ebina.hitachi.co.jp> From: Atsuo Kobayashi Date: Wed, 01 Sep 1999 18:05:47 +0900 To: freebsd-small@freebsd.org Subject: build custom failed MIME-Version: 1.0 X-Mailer: AL-Mail32 Version 1.01 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I tried custom build of PicoBSD. and get followings. ====== PicoBSD build -- Current parameters: 1. Type: custom (from /usr/home/akoba/terminal/pico_gen) 2. MFS size: 2400 kB 3. Language: en 4. Site-info: -> We'll use the sources living in /usr/src -> I hope you have checked the ../custom/PICOBSD config file... -> Checking if we have to build the PICOBSD kernel... make: cannot open ../build/Makefile.conf. ======= I think, In custom build, the script once cd to the symbolic link "/usr/src/release/picobsd/custom" . Then "../build/Makefile.conf" not points to "/usr/src/release/picobsd/build/Makefile.conf". Except only case custom is linked to /usr/src/release/picobsd/xxxx. Is that so ? I would like to place custom build parameters on my home directry. How can i do it ? Thanks. Atsuo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Sep 1 2:29:54 1999 Delivered-To: freebsd-small@freebsd.org Received: from dart.sr.se (dart.SR.SE [193.12.91.98]) by hub.freebsd.org (Postfix) with ESMTP id 9308F150BB for ; Wed, 1 Sep 1999 02:29:50 -0700 (PDT) (envelope-from root@aramis.sr.se) Received: from honken.sr.se ([134.25.128.27]) by dart.sr.se (8.9.3/8.9.3) with ESMTP id LAA05198 for ; Wed, 1 Sep 1999 11:27:47 +0200 (MET DST) Received: from aramis.sr.se (root@aramis.SR.SE [134.25.129.1]) by honken.sr.se (8.7.5/8.7.3) with SMTP id LAA17748 for ; Wed, 1 Sep 1999 11:27:46 +0200 (MET DST) Date: Wed, 1 Sep 1999 10:30:27 +0000 (GMT) From: Kent Berggren Cc: freebsd-small@FreeBSD.ORG Subject: micro-motherboard In-Reply-To: <000101bea092$b8e57f30$0100a8c0@sandrab> 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 Hi Look at http://www.cellcomputing.com Have a nice Kent Berggren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Sep 2 23:45:38 1999 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 117CC14FE4; Thu, 2 Sep 1999 23:45:32 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA19977; Fri, 3 Sep 1999 00:44:50 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA20938; Fri, 3 Sep 1999 00:44:55 -0600 (MDT) Message-Id: <199909030644.AAA20938@harmony.village.org> To: config@freebsd.org Cc: small@freebsd.org Subject: Odd idea Date: Fri, 03 Sep 1999 00:44:55 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anybody put together a tftp boot floopy? I was thinking that if I had a supported ethernet card, then I could boot the install ramdisk kernel off a server at ethernet speeds rather than floppy speeds. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Sep 2 23:48:35 1999 Delivered-To: freebsd-small@freebsd.org Received: from dingo.cdrom.com (castles547.castles.com [208.214.165.111]) by hub.freebsd.org (Postfix) with ESMTP id E666114DC3; Thu, 2 Sep 1999 23:48:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA00492; Thu, 2 Sep 1999 23:41:44 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909030641.XAA00492@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh Cc: config@freebsd.org, small@freebsd.org Subject: Re: Odd idea In-reply-to: Your message of "Fri, 03 Sep 1999 00:44:55 MDT." <199909030644.AAA20938@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Sep 1999 23:41:44 -0700 From: Mike Smith Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Has anybody put together a tftp boot floopy? I was thinking that if I > had a supported ethernet card, then I could boot the install ramdisk > kernel off a server at ethernet speeds rather than floppy speeds. I'm working on fixing the network stack in the loader at the moment. Once that's done, you should be able to do just that (or use NFS, for that matter). There's some glue missing (drivers for PC network cards), but that'll be relatively easy by comparison. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 8: 7:47 1999 Delivered-To: freebsd-small@freebsd.org Received: from mail.rdc2.occa.home.com (ha1.rdc2.occa.home.com [24.2.8.66]) by hub.freebsd.org (Postfix) with ESMTP id 7167914DB5 for ; Fri, 3 Sep 1999 08:07:41 -0700 (PDT) (envelope-from shansen@earthlink.net) Received: from p2 ([24.9.137.53]) by mail.rdc2.occa.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990903150740.JAL7267.mail.rdc2.occa.home.com@p2>; Fri, 3 Sep 1999 08:07:40 -0700 From: "Skip Hansen" To: Warner Losh Date: Fri, 3 Sep 1999 08:11:13 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Odd idea Reply-To: shansen@earthlink.net Cc: small@FreeBSD.ORG In-reply-to: <199909030644.AAA20938@harmony.village.org> X-mailer: Pegasus Mail for Win32 (v3.12a) Message-Id: <19990903150740.JAL7267.mail.rdc2.occa.home.com@p2> Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Has anybody put together a tftp boot floopy? I was thinking that if I > had a supported ethernet card, then I could boot the install ramdisk > kernel off a server at ethernet speeds rather than floppy speeds. > > Warner Might as well go all the way and lose the floppy altogether. I boot my PicoBSD firewall box over the network using an EPROM created from the Etherboot port. The only problem is that the port is based on an older version of Etherboot that's hard to find. Doug Ambrisko was very helpful in providing the original tarball. I made a couple of minor modifications to the PicoBSD scripts to include the stuff normally on the floppy in the MFS image and to remove the references to the floppy after boot time and that was it. Skip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 10:12:22 1999 Delivered-To: freebsd-small@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 73776152DD; Fri, 3 Sep 1999 10:12:18 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.2) with ESMTP id MAA69034; Fri, 3 Sep 1999 12:11:22 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 3 Sep 1999 12:11:21 -0500 (CDT) From: Chris Dillon To: Mike Smith Cc: Warner Losh , config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea In-Reply-To: <199909030641.XAA00492@dingo.cdrom.com> 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 Thu, 2 Sep 1999, Mike Smith wrote: > > > > Has anybody put together a tftp boot floopy? I was thinking that if I > > had a supported ethernet card, then I could boot the install ramdisk > > kernel off a server at ethernet speeds rather than floppy speeds. > > I'm working on fixing the network stack in the loader at the moment. > Once that's done, you should be able to do just that (or use NFS, for > that matter). There's some glue missing (drivers for PC network > cards), but that'll be relatively easy by comparison. Will/could that support configuration via DHCP? -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 12:18:58 1999 Delivered-To: freebsd-small@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 1456314BE5; Fri, 3 Sep 1999 12:18:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00622; Fri, 3 Sep 1999 12:08:27 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909031908.MAA00622@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Dillon Cc: Mike Smith , Warner Losh , config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea In-reply-to: Your message of "Fri, 03 Sep 1999 12:11:21 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Sep 1999 12:08:27 -0700 From: Mike Smith Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 2 Sep 1999, Mike Smith wrote: > > > > > > > Has anybody put together a tftp boot floopy? I was thinking that if I > > > had a supported ethernet card, then I could boot the install ramdisk > > > kernel off a server at ethernet speeds rather than floppy speeds. > > > > I'm working on fixing the network stack in the loader at the moment. > > Once that's done, you should be able to do just that (or use NFS, for > > that matter). There's some glue missing (drivers for PC network > > cards), but that'll be relatively easy by comparison. > > Will/could that support configuration via DHCP? Yes; initially it will do only bootp, but DHCP is assumed to be coming. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 12:36:55 1999 Delivered-To: freebsd-small@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 85DCA14BF9; Fri, 3 Sep 1999 12:36:51 -0700 (PDT) (envelope-from ji@research.att.com) Received: from amontillado.research.att.com (amontillado.research.att.com [135.207.24.32]) by mail-green.research.att.com (Postfix) with ESMTP id 93E571E02F; Fri, 3 Sep 1999 15:36:13 -0400 (EDT) Received: from arran.research.att.com (arran.research.att.com [135.207.24.12]) by amontillado.research.att.com (8.8.7/8.8.7) with ESMTP id PAA28277; Fri, 3 Sep 1999 15:36:10 -0400 (EDT) From: John Ioannidis Received: (from ji@localhost) by arran.research.att.com (8.7.5/8.7) id PAA20985; Fri, 3 Sep 1999 15:36:12 -0400 (EDT) Date: Fri, 3 Sep 1999 15:36:12 -0400 (EDT) Message-Id: <199909031936.PAA20985@arran.research.att.com> To: imp@village.org, mike@smith.net.au Subject: Re: Odd idea Cc: config@freebsd.org, small@freebsd.org Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Didn't there use to be a loader that one could burn on eprom, stick the eprom in an ethernet card, and boot? I remember playing with it a few years ago, but it was probably back in the 2.1.5 days. /ji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 12:42: 7 1999 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3EF751537E; Fri, 3 Sep 1999 12:41:57 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA22617; Fri, 3 Sep 1999 13:41:36 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA46559; Fri, 3 Sep 1999 13:41:47 -0600 (MDT) Message-Id: <199909031941.NAA46559@harmony.village.org> To: John Ioannidis Subject: Re: Odd idea Cc: mike@smith.net.au, config@freebsd.org, small@freebsd.org In-reply-to: Your message of "Fri, 03 Sep 1999 15:36:12 EDT." <199909031936.PAA20985@arran.research.att.com> References: <199909031936.PAA20985@arran.research.att.com> Date: Fri, 03 Sep 1999 13:41:47 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909031936.PAA20985@arran.research.att.com> John Ioannidis writes: : Didn't there use to be a loader that one could burn on eprom, stick the : eprom in an ethernet card, and boot? I remember playing with it a few : years ago, but it was probably back in the 2.1.5 days. Yes, but I wanted to do this from floppy to speed up the installation process. I wanted to do this once rather than many times. Also, my ethernet cards don't have bootroms. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 12:44:15 1999 Delivered-To: freebsd-small@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 6A1A515E40; Fri, 3 Sep 1999 12:43:46 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00799; Fri, 3 Sep 1999 12:35:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909031935.MAA00799@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Ioannidis Cc: imp@village.org, mike@smith.net.au, config@freebsd.org, small@freebsd.org Subject: Re: Odd idea In-reply-to: Your message of "Fri, 03 Sep 1999 15:36:12 EDT." <199909031936.PAA20985@arran.research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Sep 1999 12:35:56 -0700 From: Mike Smith Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Didn't there use to be a loader that one could burn on eprom, stick the > eprom in an ethernet card, and boot? I remember playing with it a few > years ago, but it was probably back in the 2.1.5 days. These days you go out and buy a PXE-compliant boot ROM for your card, or update your motherboard BIOS if you have onboard networking hardware. The i386 loader will be PXE 2.0 compliant when we're done with it; at the moment I'm only working on the Alpha, but adding PXE support will be fairly straightforward. You can buy third-party PXE-compliant bootroms for almost every card ever manufactured. InCom (www.incom.de) support several hundred at least, and they're only one vendor. You can read more about PXE at Intel's developer site (developer.intel.com); I am actively looking for a contributor to help with the PXE code. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 13:37:12 1999 Delivered-To: freebsd-small@freebsd.org Received: from mail.rdc2.occa.home.com (ha1.rdc2.occa.home.com [24.2.8.66]) by hub.freebsd.org (Postfix) with ESMTP id C3F31156E9 for ; Fri, 3 Sep 1999 13:36:47 -0700 (PDT) (envelope-from shansen@earthlink.net) Received: from p2 ([24.9.137.53]) by mail.rdc2.occa.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990903203547.CEJF15959.mail.rdc2.occa.home.com@p2> for ; Fri, 3 Sep 1999 13:35:47 -0700 From: "Skip Hansen" To: small@FreeBSD.ORG Date: Fri, 3 Sep 1999 13:39:20 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Odd idea Reply-To: shansen@earthlink.net In-reply-to: <199909031941.NAA46559@harmony.village.org> References: Your message of "Fri, 03 Sep 1999 15:36:12 EDT." <199909031936.PAA20985@arran.research.att.com> X-mailer: Pegasus Mail for Win32 (v3.12a) Message-Id: <19990903203547.CEJF15959.mail.rdc2.occa.home.com@p2> Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can make a floppy image of the Etherboot code that runs from a floppy. That's the way they test images to avoid blowing lots of EPROMS while tweaking the configuration. > In message <199909031936.PAA20985@arran.research.att.com> John Ioannidis writes: > : Didn't there use to be a loader that one could burn on eprom, stick the : > eprom in an ethernet card, and boot? I remember playing with it a few : years > ago, but it was probably back in the 2.1.5 days. > > Yes, but I wanted to do this from floppy to speed up the installation > process. I wanted to do this once rather than many times. Also, my > ethernet cards don't have bootroms. > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 14:17:20 1999 Delivered-To: freebsd-small@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B3E1E14C96; Fri, 3 Sep 1999 14:17:15 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-9.ucdavis.edu [169.237.16.137]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA48031; Fri, 3 Sep 1999 14:16:49 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA55167; Fri, 3 Sep 1999 14:16:48 -0700 (PDT) (envelope-from obrien) Date: Fri, 3 Sep 1999 14:16:44 -0700 From: "David O'Brien" To: Mike Smith Cc: config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea Message-ID: <19990903141644.J49271@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <199909031908.MAA00622@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199909031908.MAA00622@dingo.cdrom.com> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Will/could that support configuration via DHCP? > > Yes; initially it will do only bootp, but DHCP is assumed to be coming. IMHpersonalO, bootp is suffient. From RFC 2131: o DHCP must provide service to existing BOOTP clients. ... From the client's point of view, DHCP is an extension of the BOOTP mechanism. This behavior allows existing BOOTP clients to interoperate with DHCP servers without requiring any change to the clients' initialization software. RFC 1542 [2] details the interactions between BOOTP and DHCP clients and servers [9]. ... There are two primary differences between DHCP and BOOTP. First, DHCP defines mechanisms through which clients can be assigned a network address for a finite lease, allowing for serial reassignment of network addresses to different clients. Second, DHCP provides the mechanism for a client to acquire all of the IP configuration parameters that it needs in order to operate. I do not believe the extra bits DHCP can offer a client will be used in the loader. Thus BOOTP is suffient. Applicable RFCs are in /usr/ports/net/isc-dhcp/work/dhcp-2.0/doc/ -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 14:59:48 1999 Delivered-To: freebsd-small@freebsd.org Received: from mark.kingsu.ab.ca (mark.kingsu.ab.ca [199.185.113.37]) by hub.freebsd.org (Postfix) with ESMTP id 83BF415200 for ; Fri, 3 Sep 1999 14:59:40 -0700 (PDT) (envelope-from bwood@KingsU.ab.ca) Received: from KingsU.ab.ca (kingsnet.kingsu.ab.ca [199.185.113.33]) by mark.kingsu.ab.ca (8.9.3/8.9.2) with ESMTP id PAA69282 for ; Fri, 3 Sep 1999 15:59:39 -0600 (MDT) (envelope-from bwood@KingsU.ab.ca) Message-Id: <199909032159.PAA69282@mark.kingsu.ab.ca> Received: from KINGSNET/SpoolDir by KingsU.ab.ca (Mercury 1.44); 3 Sep 99 15:59:47 -0700 Received: from SpoolDir by KINGSNET (Mercury 1.44); 3 Sep 99 15:59:35 -0700 From: "Broderick Wood" Organization: The King's University College To: small@FreeBSD.ORG Date: Fri, 3 Sep 1999 15:59:26 -0600 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Odd idea In-reply-to: <19990903141644.J49271@dragon.nuxi.com> References: <199909031908.MAA00622@dingo.cdrom.com> X-mailer: Pegasus Mail for Win32 (v3.12a) Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Will/could that support configuration via DHCP? > > > > Yes; initially it will do only bootp, but DHCP is assumed to be > > coming. > > IMHpersonalO, bootp is suffient. > > From RFC 2131: > o DHCP must provide service to existing BOOTP clients. > ... > From the client's point of view, DHCP is an extension of the BOOTP > mechanism. This behavior allows existing BOOTP clients to > interoperate with DHCP servers without requiring any change to the > clients' initialization software. RFC 1542 [2] details the > interactions between BOOTP and DHCP clients and servers [9]. > ... > There are two primary differences between DHCP and BOOTP. First, > DHCP defines mechanisms through which clients can be assigned a > network address for a finite lease, allowing for serial > reassignment of network addresses to different clients. Second, > DHCP provides the mechanism for a client to acquire all of the IP > configuration parameters that it needs in order to operate. > > > I do not believe the extra bits DHCP can offer a client will be used > in the loader. Thus BOOTP is suffient. Applicable RFCs are in > /usr/ports/net/isc-dhcp/work/dhcp-2.0/doc/ Except that a site can configure to NOT allow BootP clients with a DHCP server. I am using this option using ISC-DHCP for FreeBSD so that I have more control over the leases and such for my student network... --------------------------- -BMW- Don't just stand there! Pray something! (bwood@kingsu.ab.ca) Broderick Wood, Director of Information Technology Services The King's University College 9125 - 50 Street Edmonton, Alberta T6B 2H3 (780) 465-8315 (780) 465-3534 (FAX) ><> <>< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 15: 3:47 1999 Delivered-To: freebsd-small@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id E89F614BF5; Fri, 3 Sep 1999 15:03:43 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.2) with ESMTP id RAA71245; Fri, 3 Sep 1999 17:03:09 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 3 Sep 1999 17:03:09 -0500 (CDT) From: Chris Dillon To: "David O'Brien" Cc: Mike Smith , config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea In-Reply-To: <19990903141644.J49271@dragon.nuxi.com> 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 Fri, 3 Sep 1999, David O'Brien wrote: > > > Will/could that support configuration via DHCP? > > > > Yes; initially it will do only bootp, but DHCP is assumed to be coming. > > IMHpersonalO, bootp is suffient. > > >From RFC 2131: [...snip...] > > I do not believe the extra bits DHCP can offer a client will be used in > the loader. Thus BOOTP is suffient. Applicable RFCs are in > /usr/ports/net/isc-dhcp/work/dhcp-2.0/doc/ BOOTP is not necessarily sufficient. BOOTP does not allow truly dynamic configuration, or at least not with the ISC dhcpd. It at least requires a host and hardware declaration for each BOOTP client, even if you allow dynamic IP addresses to be assigned, while DHCP does not. In my case, I would need to use DHCP because of this limitation. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 15:44:48 1999 Delivered-To: freebsd-small@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id EBD7F150CA; Fri, 3 Sep 1999 15:44:41 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-3-24.ucdavis.edu [169.237.17.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA48395; Fri, 3 Sep 1999 15:44:06 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA55538; Fri, 3 Sep 1999 15:39:33 -0700 (PDT) (envelope-from obrien) Date: Fri, 3 Sep 1999 15:39:33 -0700 From: "David O'Brien" To: Chris Dillon Cc: config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea Message-ID: <19990903153932.A55391@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19990903141644.J49271@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > BOOTP is not necessarily sufficient. BOOTP does not allow truly > dynamic configuration, or at least not with the ISC dhcpd. Remember we are talking about the loader here, for net booting. Not for after you've booted. When net booting you need to tell the loader the kernel's name and the path to / . I could be wrong, but I think you usually would not want these dolled out randomly. For example: host net-install { hardware ethernet 8:0:2b:32:bf:5c; fixed-address 192.168.1.3; option host-name "foo.nuxi.com"; option domain-name-servers 192.168.1.2 option broadcast-address 192.168.1.255; option routers 192.168.1.1; option domain-name "nuxi.com"; option root-path "/export/freebsd-install"; filename "install.bin"; } you could of course specify swap here and have a diskless setup. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 15:51:49 1999 Delivered-To: freebsd-small@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id E9A97150E3; Fri, 3 Sep 1999 15:51:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA01768; Fri, 3 Sep 1999 15:44:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909032244.PAA01768@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com Cc: Chris Dillon , config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea In-reply-to: Your message of "Fri, 03 Sep 1999 15:39:33 PDT." <19990903153932.A55391@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Sep 1999 15:44:26 -0700 From: Mike Smith Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > BOOTP is not necessarily sufficient. BOOTP does not allow truly > > dynamic configuration, or at least not with the ISC dhcpd. > > Remember we are talking about the loader here, for net booting. Not for > after you've booted. When net booting you need to tell the loader the > kernel's name and the path to / . I could be wrong, but I think you > usually would not want these dolled out randomly. For example: You don't want them handed out randomly, no, but conversely you (probably ) want the same address to be used by the system once it's up and running. At least in theory if the loader is able to pull the DHCP config off, it can pass the relevant lease details on to the kernel, which can be used to seed dhclient. It's all a bit vague at the moment, and there's plenty of room to change things around as the code matures. For now, suffice to say that I expect to add DHCP if for no other reason than that's all that PXE supports. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 16:16:50 1999 Delivered-To: freebsd-small@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id CA7CF14BE4; Fri, 3 Sep 1999 16:16:42 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-3-24.ucdavis.edu [169.237.17.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id QAA48626; Fri, 3 Sep 1999 16:16:15 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id QAA55735; Fri, 3 Sep 1999 16:16:05 -0700 (PDT) (envelope-from obrien) Date: Fri, 3 Sep 1999 16:16:05 -0700 From: "David O'Brien" To: Mike Smith Cc: config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea Message-ID: <19990903161605.B55391@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19990903153932.A55391@dragon.nuxi.com> <199909032244.PAA01768@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199909032244.PAA01768@dingo.cdrom.com> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At least in theory if the loader is able to pull the DHCP config off, > it can pass the relevant lease details on to the kernel, which can be > used to seed dhclient. Actually you wouldn't pass them to the kernel (which knows nothing of DHCP). I think it would be better to just configure things for normal DHCP and let ``dhclient'' request a lease in the normal way. I can't think of how to start ``dhclient'' and keep it from asking for a new lease (which is what you would need to do here). While you could pass the data from the loader into /var/db/dhclient.leases. This file is used if `dhclient' can't get a response from the DHCP server. lease { interface "fxp0"; fixed-address 169.237.7.195; option subnet-mask 255.255.255.0; option routers 169.237.7.254; option domain-name-servers 169.237.250.250; option host-name "erebus.cs.ucdavis.edur"; option domain-name "cs.ucdavis.edu"; option broadcast-address 169.237.7.255; option dhcp-lease-time 600; option dhcp-message-type 5; option dhcp-server-identifier 169.237.7.38; renew 3 1999/8/11 02:10:40; rebind 3 1999/8/11 02:14:25; expire 3 1999/8/11 02:15:40; } > For now, suffice to say that I expect to add DHCP if for no other > reason than that's all that PXE supports. If that's what they do, my would be that they query to get the initial data, and then let the OS do its normal DHCP client processing. If so then this makes your job easier as you don't have to worry about passing the data out of the loader. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Sep 3 16:28:32 1999 Delivered-To: freebsd-small@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 33102150A9; Fri, 3 Sep 1999 16:28:28 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id QAA01951; Fri, 3 Sep 1999 16:20:12 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909032320.QAA01951@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com Cc: config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea In-reply-to: Your message of "Fri, 03 Sep 1999 16:16:05 PDT." <19990903161605.B55391@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Sep 1999 16:20:12 -0700 From: Mike Smith Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If that's what they do, my would be that they query to get the initial > data, and then let the OS do its normal DHCP client processing. If so > then this makes your job easier as you don't have to worry about passing > the data out of the loader. Sounds good to me. 8) -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Sep 4 12:37: 6 1999 Delivered-To: freebsd-small@freebsd.org Received: from THUNDERstorm.plex.nl (THUNDERstorm.plex.nl [194.229.212.8]) by hub.freebsd.org (Postfix) with SMTP id 1250E152DC; Sat, 4 Sep 1999 12:36:59 -0700 (PDT) (envelope-from j.backus@bugworks.com) Received: from daffy (isdn-1c078.plex.nl [212.206.188.81]) by THUNDERstorm.plex.nl (SMI-8.6/SMI-SVR4) id VAA05904; Sat, 4 Sep 1999 21:37:10 +0200 Message-Id: <199909041937.VAA05904@THUNDERstorm.plex.nl> X-Disclaimer: Plex is a public access Internet provider From: "Jac Backus" To: Mike Smith Date: Sat, 4 Sep 1999 21:36:40 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Odd idea Cc: imp@village.org, mike@smith.net.au, config@freebsd.org, small@freebsd.org In-reply-to: <199909031935.MAA00799@dingo.cdrom.com> References: Your message of "Fri, 03 Sep 1999 15:36:12 EDT." <199909031936.PAA20985@arran.research.att.com> X-mailer: Pegasus Mail for Win32 (v3.12) Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ha die Jos, Leuk dat PXE... Probeer er maar eens achter te komen hoe dit zou moeten werken zonder Intel software speeltjes:-(. groetjes, Jacques On 3 Sep 99, at 12:35, Mike Smith wrote: > > Didn't there use to be a loader that one could burn on eprom, stick the > > eprom in an ethernet card, and boot? I remember playing with it a few > > years ago, but it was probably back in the 2.1.5 days. > > These days you go out and buy a PXE-compliant boot ROM for your card, > or update your motherboard BIOS if you have onboard networking hardware. > > The i386 loader will be PXE 2.0 compliant when we're done with it; at > the moment I'm only working on the Alpha, but adding PXE support will > be fairly straightforward. > > You can buy third-party PXE-compliant bootroms for almost every card > ever manufactured. InCom (www.incom.de) support several hundred at > least, and they're only one vendor. > > You can read more about PXE at Intel's developer site > (developer.intel.com); I am actively looking for a contributor to help > with the PXE code. > > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ msmith@freebsd.org > \\ -- Joseph Merrick \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-config" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Sep 4 12:47:52 1999 Delivered-To: freebsd-small@freebsd.org Received: from dart.sr.se (dart.SR.SE [193.12.91.98]) by hub.freebsd.org (Postfix) with ESMTP id 17C8D152A4 for ; Sat, 4 Sep 1999 12:47:38 -0700 (PDT) (envelope-from root@aramis.sr.se) Received: from honken.sr.se ([134.25.128.27]) by dart.sr.se (8.9.3/8.9.3) with ESMTP id VAA24869 for ; Sat, 4 Sep 1999 21:45:58 +0200 (MET DST) Received: from aramis.sr.se (root@aramis.SR.SE [134.25.129.1]) by honken.sr.se (8.7.5/8.7.3) with SMTP id VAA14304 for ; Sat, 4 Sep 1999 21:45:57 +0200 (MET DST) Date: Sat, 4 Sep 1999 20:48:49 +0000 (GMT) From: Kent Berggren Cc: small@FreeBSD.ORG Subject: Re: Odd idea In-Reply-To: <199909041937.VAA05904@THUNDERstorm.plex.nl> 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 Pleas not Swedish:-)/kenta On Sat, 4 Sep 1999, Jac Backus wrote: > Ha die Jos, > > Leuk dat PXE... > Probeer er maar eens achter te komen hoe dit zou moeten werken > zonder Intel software speeltjes:-(. > > groetjes, > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Sep 4 19:14:12 1999 Delivered-To: freebsd-small@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D9B91532F; Sat, 4 Sep 1999 19:14:09 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.2) with ESMTP id VAA79865; Sat, 4 Sep 1999 21:13:50 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Sat, 4 Sep 1999 21:13:49 -0500 (CDT) From: Chris Dillon To: "David O'Brien" Cc: config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea In-Reply-To: <19990903153932.A55391@dragon.nuxi.com> 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 Fri, 3 Sep 1999, David O'Brien wrote: > > BOOTP is not necessarily sufficient. BOOTP does not allow truly > > dynamic configuration, or at least not with the ISC dhcpd. > > Remember we are talking about the loader here, for net booting. Not for > after you've booted. When net booting you need to tell the loader the > kernel's name and the path to / . I could be wrong, but I think you > usually would not want these dolled out randomly. For example: > > host net-install { > hardware ethernet 8:0:2b:32:bf:5c; > fixed-address 192.168.1.3; > option host-name "foo.nuxi.com"; > option domain-name-servers 192.168.1.2 > option broadcast-address 192.168.1.255; > option routers 192.168.1.1; > option domain-name "nuxi.com"; > option root-path "/export/freebsd-install"; > filename "install.bin"; > } > > you could of course specify swap here and have a diskless setup. Doh. I wish there were some way other than specifying the MAC address to say to the DHCP/BOOTP server "give me FOO configuration". I was trying to think of a way to make a boot disk which required a minimal amount of system-dependant information tied to the boot disk itself or to the station you are booting it from. Unfortunately I guess neither BOOTP nor DHCP can fit this bill (or can it?). -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Sep 4 19:30:37 1999 Delivered-To: freebsd-small@freebsd.org Received: from dingo.cdrom.com (castles529.castles.com [208.214.165.93]) by hub.freebsd.org (Postfix) with ESMTP id E5FF914BD5; Sat, 4 Sep 1999 19:30:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id TAA08660; Sat, 4 Sep 1999 19:14:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909050214.TAA08660@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Dillon Cc: "David O'Brien" , config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea In-reply-to: Your message of "Sat, 04 Sep 1999 21:13:49 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Sep 1999 19:14:10 -0700 From: Mike Smith Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Doh. I wish there were some way other than specifying the MAC address > to say to the DHCP/BOOTP server "give me FOO configuration". I was > trying to think of a way to make a boot disk which required a minimal > amount of system-dependant information tied to the boot disk itself or > to the station you are booting it from. Unfortunately I guess neither > BOOTP nor DHCP can fit this bill (or can it?). You need a physical token of some sort to identify the machine; either you use the MAC address or in some cases the GUID or UUID storage (on an intel system) or some other NVRAM token depending on the system in question. But the ethernet MAC address is about the only universal uniquifier that any system has, so you really don't have much choice. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Sep 4 22:21:49 1999 Delivered-To: freebsd-small@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 3138A14CFC; Sat, 4 Sep 1999 22:21:46 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.2) with ESMTP id AAA80382; Sun, 5 Sep 1999 00:20:48 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Sun, 5 Sep 1999 00:20:48 -0500 (CDT) From: Chris Dillon To: Mike Smith Cc: "David O'Brien" , config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea In-Reply-To: <199909050214.TAA08660@dingo.cdrom.com> 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 Sat, 4 Sep 1999, Mike Smith wrote: > > Doh. I wish there were some way other than specifying the MAC address > > to say to the DHCP/BOOTP server "give me FOO configuration". I was > > trying to think of a way to make a boot disk which required a minimal > > amount of system-dependant information tied to the boot disk itself or > > to the station you are booting it from. Unfortunately I guess neither > > BOOTP nor DHCP can fit this bill (or can it?). > > You need a physical token of some sort to identify the machine; either > you use the MAC address or in some cases the GUID or UUID storage (on an > intel system) or some other NVRAM token depending on the system in > question. > > But the ethernet MAC address is about the only universal uniquifier > that any system has, so you really don't have much choice. I was thinking more along the line of the dhcp-client-identifier which is sent to the DHCP server by the client (which I guess is what you are referring to, also, in the case of the "token"). Since the hostname can be used as this identifier, it would be possible for me to give each install disk a hostname of install# and then configure dhcpd to give anything with hostname install* a certain configuration. Would the DHCP client in the loader support doing this? If not, maybe I can hack it up into doing so. :-) Using the MAC address as the token is just a little bit of a pain in the @ss since there are potentially thousands of systems, and new systems must have their MAC addresses entered first before they can be used. If support in isc-dhcpd isn't there for specifying something like: group { next-server boot.foo.com; filename "kernel"; dhcp-client-identifier "install*"; } or possibly even: host install* { next-server boot.foo.com; filename "kernel"; dhcp-client-identifier "install*"; } Think it would be a useful enough feature to submit to ISC, assuming it doesn't already exist? At the very worst I could do (and can be done right now, without mod to the dhcpd): group { next-server boot.foo.com; filename "kernel"; host install1 { dhcp-client-identifier "install1"; } host install2 { dhcp-client-identifier "install2"; } host install3 { dhcp-client-identifier "install3"; } ad nauseum... } -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Sep 4 23:26:39 1999 Delivered-To: freebsd-small@freebsd.org Received: from dingo.cdrom.com (castles529.castles.com [208.214.165.93]) by hub.freebsd.org (Postfix) with ESMTP id A8BFE14FFF; Sat, 4 Sep 1999 23:26:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA09759; Sat, 4 Sep 1999 23:19:12 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909050619.XAA09759@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Dillon Cc: config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea In-reply-to: Your message of "Sun, 05 Sep 1999 00:20:48 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Sep 1999 23:19:11 -0700 From: Mike Smith Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You need a physical token of some sort to identify the machine; either > > you use the MAC address or in some cases the GUID or UUID storage (on an > > intel system) or some other NVRAM token depending on the system in > > question. > > > > But the ethernet MAC address is about the only universal uniquifier > > that any system has, so you really don't have much choice. > > I was thinking more along the line of the dhcp-client-identifier which > is sent to the DHCP server by the client (which I guess is what you > are referring to, also, in the case of the "token"). Since the > hostname can be used as this identifier, it would be possible for me > to give each install disk a hostname of install# and then configure > dhcpd to give anything with hostname install* a certain configuration. In this case, the physical token is the floppy disk. > Would the DHCP client in the loader support doing this? If it didn't, you would have the source code, and I would be very receptive to any input along those lines. 8) -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message