From owner-freebsd-small Sun Mar 28 0:32: 1 1999 Delivered-To: freebsd-small@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 00A7B14BF6 for ; Sun, 28 Mar 1999 00:31:59 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.42]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA37BC; Sun, 28 Mar 1999 10:31:39 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id KAA89111; Sun, 28 Mar 1999 10:31:36 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <92643.922600571.viking@twin-city.net> Date: Sun, 28 Mar 1999 10:31:35 +0100 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: mark Subject: RE: is this list active? Cc: freebsd-small@freebsd.org Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Mar-99 mark wrote: > I just subscribed because I am somewhat interested in picobsd. > > Please pardon my intrusion, I merely wanted to know if this list is > active. We deluge(?) ourselves in tranquility... Anyways, just to make this mail somewhat more interesting: Zebra is now out of Alpha status and into Beta status. I have tried to maintain compilation compatibility for 2.2.8 (2.2.x probably) towards CURRENT (4.x). Could interested parties get the sources from the anoncvs server and compile and test it? And if found to have some quirks for your platform, tell me about it and I'll see what I can do... www.zebra.org Thanks, --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Mar 28 0:52:25 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 3B0B3156BD for ; Sun, 28 Mar 1999 00:52:16 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id IAA00638 for ; Sun, 28 Mar 1999 08:51:57 GMT Received: (from imp@localhost) by harmony.village.org (8.9.3/8.8.3) id XAA79553 for freebsd-small@freebsd.org; Sat, 27 Mar 1999 23:18:32 -0700 (MST) Date: Sat, 27 Mar 1999 23:18:32 -0700 (MST) From: Warner Losh Message-Id: <199903280618.XAA79553@harmony.village.org> To: freebsd-small@freebsd.org Subject: PocketBSD Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, Trolling the net, and also making strange postings about CE machines, I discovered that there is a FreeBSD based thing called PocketBSD. Seems to duplicate the goals of PicoBSD, but I've not been able to find out much about PcoketBSD. I do know that it runs on NEC MobileGear PDA machines (these are Intel based), but little beyond that. All the web pages that I could find were in Japanese. I've found several places on the net that I can learn Japanese from, but none offer translations services (so I have to go about it the long, hard slow way :-<. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Mar 28 10:11:26 1999 Delivered-To: freebsd-small@freebsd.org Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (Postfix) with ESMTP id 9E60A14C2B for ; Sun, 28 Mar 1999 10:11:23 -0800 (PST) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id LAA20000; Sun, 28 Mar 1999 11:10:31 -0700 (MST) From: "Chad R. Larson" Message-Id: <199903281810.LAA20000@freebie.dcfinc.com> Subject: Re: PocketBSD To: imp@harmony.village.org (Warner Losh) Date: Sun, 28 Mar 1999 11:10:31 -0700 (MST) Cc: freebsd-small@FreeBSD.ORG In-Reply-To: <199903280618.XAA79553@harmony.village.org> from Warner Losh at "Mar 27, 99 11:18:32 pm" Reply-To: chad@dcfinc.com X-unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > All the web pages that I could find were in Japanese. I've found > several places on the net that I can learn Japanese from, but none > offer translations services (so I have to go about it the long, hard > slow way :-<. Go to www.altavista.com and enter the URL there. They have a translation service built in that will any of take something like 26 languages to any other. In my experience, the translations run fairly crude. You wouldn't turn them in to your language class. But they're usable. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Mar 28 11:38: 5 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 2A5AE14EB0 for ; Sun, 28 Mar 1999 11:38:01 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id TAA02055; Sun, 28 Mar 1999 19:37:41 GMT 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 MAA22743; Sun, 28 Mar 1999 12:37:05 -0700 (MST) Message-Id: <199903281937.MAA22743@harmony.village.org> To: chad@dcfinc.com Subject: Re: PocketBSD Cc: freebsd-small@FreeBSD.ORG In-reply-to: Your message of "Sun, 28 Mar 1999 11:10:31 MST." <199903281810.LAA20000@freebie.dcfinc.com> References: <199903281810.LAA20000@freebie.dcfinc.com> Date: Sun, 28 Mar 1999 12:37:05 -0700 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903281810.LAA20000@freebie.dcfinc.com> "Chad R. Larson" writes: : Go to www.altavista.com and enter the URL there. They have a : translation service built in that will any of take something : like 26 languages to any other. Can you be more explicit in your instructions? The only languages that I could get translation on are English, Spanish, French, German, Italian and Portugese. There may be 26 languages in their initial menu, but I don't see any way to translate a Japanese document into english. How would I get a translation of, say, the document at http://www.kt.rim.or.jp/~chick/PocketBSD/ Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Mar 28 11:50:48 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 A0C9E14D99 for ; Sun, 28 Mar 1999 11:50:44 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id TAA02102; Sun, 28 Mar 1999 19:50:25 GMT 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 MAA22867; Sun, 28 Mar 1999 12:49:50 -0700 (MST) Message-Id: <199903281949.MAA22867@harmony.village.org> Subject: Re: PocketBSD Cc: chad@dcfinc.com, freebsd-small@FreeBSD.ORG In-reply-to: Your message of "Sun, 28 Mar 1999 12:37:05 MST." <199903281937.MAA22743@harmony.village.org> References: <199903281937.MAA22743@harmony.village.org> <199903281810.LAA20000@freebie.dcfinc.com> Date: Sun, 28 Mar 1999 12:49:50 -0700 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903281937.MAA22743@harmony.village.org> Warner Losh writes: : There may be 26 languages in their initial menu, but I don't see any : way to translate a Japanese document into english. How would I get a : translation of, say, the document at : http://www.kt.rim.or.jp/~chick/PocketBSD/ BTW, after a little digging, I did find systrans pro, but that runs $1000 for a single user license. Not exactly a good investment for what I want it for. Too bad SYSTRAMS Personal doesn't support even unidirectional translation from Japanese -> English, as the Personal system is only $30 for unidirectional or $50 for bidirectional. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Mar 29 10:58:33 1999 Delivered-To: freebsd-small@freebsd.org Received: from mail.glenatl.glenayre.com (mail.glenatl.glenayre.com [157.230.160.51]) by hub.freebsd.org (Postfix) with SMTP id 369B3154A6 for ; Mon, 29 Mar 1999 10:58:10 -0800 (PST) (envelope-from jhicks@glenatl.glenayre.com) Received: from jhicks.glenatl.glenayre.com by mail.glenatl.glenayre.com (SMI-8.6/SMI-SVR4) id NAA23629; Mon, 29 Mar 1999 13:47:17 -0500 Received: from jhicks.glenatl.glenayre.com (localhost [127.0.0.1]) by jhicks.glenatl.glenayre.com (8.9.2/8.8.5) with ESMTP id SAA00443; Mon, 29 Mar 1999 18:49:48 GMT Message-Id: <199903291849.SAA00443@jhicks.glenatl.glenayre.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mark Cc: freebsd-small@freebsd.org Subject: Re: is this list active? In-reply-to: Your message of "Sat, 27 Mar 1999 21:56:11 PST." <92643.922600571.viking@twin-city.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Mar 1999 18:49:48 +0000 From: Jerry Hicks Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just subscribed because I am somewhat interested in picobsd. > > Please pardon my intrusion, I merely wanted to know if this list is active. Somewhat, although not as active lately because of the stability of PicoBSD ;-) Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Mar 29 11:17:17 1999 Delivered-To: freebsd-small@freebsd.org Received: from tellink.net (pm-5-20.tellink.net [208.3.160.46]) by hub.freebsd.org (Postfix) with ESMTP id 95097158CC for ; Mon, 29 Mar 1999 11:17:01 -0800 (PST) (envelope-from chip@tellink.net) Received: (from root@localhost) by tellink.net (8.9.1/8.9.1) id OAA12571 for freebsd-small@freebsd.org; Mon, 29 Mar 1999 14:17:38 -0500 (EST) (envelope-from chip) Message-ID: <19990329141738.A12556@expi> Date: Mon, 29 Mar 1999 14:17:38 -0500 From: Chip Marshall To: freebsd-small@freebsd.org Subject: MP3 playing PicoBSD Reply-To: cmarshall@expi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Real-OS: FreeBSD holly 3.0-RELEASE FreeBSD 3.0-RELEASE Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After reading about Oliver Fromme's MPEG audio player project, I though it would be interesting to start such a project of my own. On the page about the project, http://dorifer.heim3.tu-clausthal.de/~olli/project/, he mentions having a single floppy variant of FreeBSD that just boots and plays MP3's from a CD. Unfortunatly, he also states he will not give out the floppy image, since it is customized to his configuration. Has anyone else out there done anything like this with PicoBSD? Also, as a bit of a side note, does PicoBSD work with an elf bootloader? -- Chip Marshall Exploration Physics International, Inc. Internet Technology Programmer http://www.eboai.org/~chip/ InterNIC handle - CLM21 PGP key available on my web page On IRC via EFnet as Magus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Mar 29 12:38:31 1999 Delivered-To: freebsd-small@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id AF55414E66 for ; Mon, 29 Mar 1999 12:38:24 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 7919618C6; Mon, 29 Mar 1999 22:38:08 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 7609D4999; Mon, 29 Mar 1999 22:38:08 +0200 (CEST) Date: Mon, 29 Mar 1999 22:38:08 +0200 (CEST) From: Andrzej Bialecki To: Chip Marshall Cc: freebsd-small@FreeBSD.ORG Subject: Re: MP3 playing PicoBSD In-Reply-To: <19990329141738.A12556@expi> 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, 29 Mar 1999, Chip Marshall wrote: > After reading about Oliver Fromme's MPEG audio player project, I > though it would be interesting to start such a project of my own. On > the page about the project, > http://dorifer.heim3.tu-clausthal.de/~olli/project/, he mentions > having a single floppy variant of FreeBSD that just boots and plays > MP3's from a CD. Unfortunatly, he also states he will not give out > the floppy image, since it is customized to his configuration. Has > anyone else out there done anything like this with PicoBSD? It should be trivial to do. Just take one of standard Picobsd configs, and add MP3 player. > > Also, as a bit of a side note, does PicoBSD work with an elf > bootloader? Yes, by default. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Mar 30 3:56:46 1999 Delivered-To: freebsd-small@freebsd.org Received: from nostromo.netdev.net (nostromo.netdev.net [62.160.67.193]) by hub.freebsd.org (Postfix) with ESMTP id 8694214DFA for ; Tue, 30 Mar 1999 03:56:38 -0800 (PST) (envelope-from elrond@phoe.netdev.net) Received: from phoe.netdev.net (phoe.netdev.net [62.160.67.1]) by nostromo.netdev.net (8.9.1/8.9.1/phoe-2.0) with ESMTP id NAA25308; Tue, 30 Mar 1999 13:56:18 +0200 (CEST) Received: (from elrond@localhost) by phoe.netdev.net (8.8.5/8.8.8/phoe-1.0009) id NAA22164; Tue, 30 Mar 1999 13:56:15 +0200 (MET DST) Date: Tue, 30 Mar 1999 13:56:15 +0200 From: Bertrand Petit To: Andrzej Bialecki Cc: Chip Marshall , freebsd-small@FreeBSD.ORG Subject: Re: MP3 playing PicoBSD Message-ID: <19990330135615.A22066@phoe.netdev.net> References: <19990329141738.A12556@expi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Andrzej Bialecki on Mon, Mar 29, 1999 at 10:38:08PM +0200 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 29, 1999 at 10:38:08PM +0200, Andrzej Bialecki wrote: > > the floppy image, since it is customized to his configuration. Has > > anyone else out there done anything like this with PicoBSD? > > It should be trivial to do. Just take one of standard Picobsd configs, and > add MP3 player. The difficult part in this project is the hardware. As the aim is to build an audio playing unit, the harware must be conceived such that there is no need for cooling at all. Could modern processors be underclocked enough so that no fan is required? Maybe a big heat sink could do. The power source also must bear the absence of fan. Another big issue is the digital to analogue converter. One could not use average PC soundcard as they are poorly shielded if shielded at all. I think the lambda sound cards rate as low-fi. -- %!PS Il n'y a pas de mauvaises reponses, il n'y a que de mauvaises questions /B{bind def}def/m{moveto}B/d{dup}B/s{gsave}B/r{grestore}B/S{stroke}B/P{false charpath}B/G{setgray}B/W{setlinewidth}B/z{0 G 1 W}B/Times-Roman findfont 120 scalefont setfont 60 10 m 56 rotate(elrond@netdev.net)d d s z 40 40 rmoveto P S r s 0.5 G .5 W P flattenpath{newpath m 40 40 rlineto S}d{}{}pathforall r s z P S r 400 120 m (Bertrand) show 400 -160 m (Petit) show showpage To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Mar 31 8:50:55 1999 Delivered-To: freebsd-small@freebsd.org Received: from tellink.net (pm-4-7.tellink.net [208.3.160.184]) by hub.freebsd.org (Postfix) with ESMTP id B860C15C92 for ; Wed, 31 Mar 1999 08:50:19 -0800 (PST) (envelope-from chip@tellink.net) Received: (from chip@localhost) by tellink.net (8.9.1/8.9.1) id LAA16081; Wed, 31 Mar 1999 11:49:54 -0500 (EST) (envelope-from chip) Message-ID: <19990331114953.A16012@expi> Date: Wed, 31 Mar 1999 11:49:53 -0500 From: Chip Marshall To: Bertrand Petit Cc: freebsd-small@freebsd.org Subject: Re: MP3 playing PicoBSD Reply-To: cmarshall@expi.com References: <19990329141738.A12556@expi> <19990330135615.A22066@phoe.netdev.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990330135615.A22066@phoe.netdev.net>; from Bertrand Petit on Tue, Mar 30, 1999 at 01:56:15PM +0200 X-Real-OS: FreeBSD holly 3.0-RELEASE FreeBSD 3.0-RELEASE Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 30, 1999 at 01:56:15PM +0200, Bertrand Petit wrote: > The difficult part in this project is the hardware. As the aim > is to build an audio playing unit, the harware must be conceived such > that there is no need for cooling at all. Could modern processors be > underclocked enough so that no fan is required? Maybe a big heat sink > could do. The power source also must bear the absence of fan. These points were brought up in Fromme's discussion of the project, and I believe that a low-end AMD K5 would provide enough power to decode MP3, but not generate all the much heat. Also, since the only things in the box are the mboard, CD-ROM, and a sound card (and maybe an ether card) a very small power supply would do. But these are pretty much the same conclusions that Fromme came to, only I think his plan was with a Pentium 90. > Another big issue is the digital to analogue converter. One > could not use average PC soundcard as they are poorly shielded if > shielded at all. I think the lambda sound cards rate as low-fi. I hadn't really given much thought to this. I was just planning on using an old SB16 I had lying around. It there a way to improve shielding on these? -- Chip Marshall Exploration Physics International, Inc. Internet Technology Programmer http://www.eboai.org/~chip/ InterNIC handle - CLM21 PGP key available on my web page On IRC via EFnet as Magus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Mar 31 19:12:59 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 BCA1A1507E for ; Wed, 31 Mar 1999 19:12:54 -0800 (PST) (envelope-from imp@rover.village.org) Received: (from imp@localhost) by rover.village.org (8.9.3/8.9.3) id UAA00275 for freebsd-small@freebsd.org; Wed, 31 Mar 1999 20:12:34 -0700 (MST) (envelope-from imp) Date: Wed, 31 Mar 1999 20:12:34 -0700 (MST) From: Warner Losh Message-Id: <199904010312.UAA00275@rover.village.org> To: freebsd-small@freebsd.org Subject: picobsd? Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just built a pico bsd system and found that it gave me the following error message when I booted the floppy: Read Error Any ideas? The floppy read back OK when I dd'd it. This is with the isp configuration (and custom conf file) if that matters. The errror happened before the \|/- came up... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 1 8:35:48 1999 Delivered-To: freebsd-small@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id BF5FE14E3E for ; Thu, 1 Apr 1999 08:35:29 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 1959318C6; Thu, 1 Apr 1999 18:35:18 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 1659A49BE; Thu, 1 Apr 1999 18:35:18 +0200 (CEST) Date: Thu, 1 Apr 1999 18:35:16 +0200 (CEST) From: Andrzej Bialecki To: Warner Losh Cc: freebsd-small@FreeBSD.ORG Subject: Re: picobsd? In-Reply-To: <199904010312.UAA00275@rover.village.org> 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 Wed, 31 Mar 1999, Warner Losh wrote: > I just built a pico bsd system and found that it gave me the following > error message when I booted the floppy: > Read Error So far I've never really investigated such cases, but using another floppy almost always helped... A bug in the fd driver? Bad floppy? Who knows... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 1 8:59:27 1999 Delivered-To: freebsd-small@freebsd.org Received: from Tandem.com (suntan.tandem.com [192.216.221.8]) by hub.freebsd.org (Postfix) with ESMTP id 192BF152C2 for ; Thu, 1 Apr 1999 08:59:25 -0800 (PST) (envelope-from Dung.Nguyen@compaq.com) Received: from exccup-conn01.mis.tandem.com (exccup-conn01.mis.tandem.com [130.252.226.231]) by Tandem.com (8.9.3/2.0.1) with ESMTP id IAA28087 for ; Thu, 1 Apr 1999 08:59:05 -0800 (PST) Received: by exccup-conn01.mis.tandem.com with Internet Mail Service (5.5.2232.9) id ; Thu, 1 Apr 1999 08:59:04 -0800 Message-ID: <2BAEE918EF6CD1118FA800805F57F12E03550FEF@EXCAUS-11601> From: "Nguyen, Dung" To: "'freebsd-small@freebsd.org'" Subject: Date: Thu, 1 Apr 1999 08:59:03 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Has anyone tried to use BOOTP to boot PicoBSD? Thanks, Dung Nguyen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 1 9: 9:10 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 25AD214E3E for ; Thu, 1 Apr 1999 09:09:07 -0800 (PST) (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 KAA02048; Thu, 1 Apr 1999 10:08:50 -0700 (MST) (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 KAA19397; Thu, 1 Apr 1999 10:08:50 -0700 (MST) Message-Id: <199904011708.KAA19397@harmony.village.org> To: Andrzej Bialecki Subject: Re: picobsd? Cc: freebsd-small@FreeBSD.ORG In-reply-to: Your message of "Thu, 01 Apr 1999 18:35:16 +0200." References: Date: Thu, 01 Apr 1999 10:08:50 -0700 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Andrzej Bialecki writes: : So far I've never really investigated such cases, but using another floppy : almost always helped... A bug in the fd driver? Bad floppy? Who knows... I tried another floppy, and that one worked. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 1 10:53:55 1999 Delivered-To: freebsd-small@freebsd.org Received: from nostromo.netdev.net (nostromo.netdev.net [62.160.67.193]) by hub.freebsd.org (Postfix) with ESMTP id 4D42B154D4 for ; Thu, 1 Apr 1999 10:53:42 -0800 (PST) (envelope-from elrond@phoe.netdev.net) Received: from phoe.netdev.net (phoe.netdev.net [62.160.67.1]) by nostromo.netdev.net (8.9.1/8.9.1/phoe-2.0) with ESMTP id UAA02850; Thu, 1 Apr 1999 20:53:18 +0200 (CEST) Received: (from elrond@localhost) by phoe.netdev.net (8.8.5/8.8.8/phoe-1.0009) id UAA10224; Thu, 1 Apr 1999 20:53:16 +0200 (MET DST) Date: Thu, 1 Apr 1999 20:53:16 +0200 From: Bertrand Petit To: Chip Marshall Cc: freebsd-small@FreeBSD.ORG Subject: Re: MP3 playing PicoBSD Message-ID: <19990401205316.F6653@phoe.netdev.net> References: <19990329141738.A12556@expi> <19990330135615.A22066@phoe.netdev.net> <19990331114953.A16012@expi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990331114953.A16012@expi>; from Chip Marshall on Wed, Mar 31, 1999 at 11:49:53AM -0500 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 31, 1999 at 11:49:53AM -0500, Chip Marshall wrote: > > Another big issue is the digital to analogue converter. One > > could not use average PC soundcard as they are poorly shielded if > > shielded at all. I think the lambda sound cards rate as low-fi. > > I hadn't really given much thought to this. I was just planning on > using an old SB16 I had lying around. It there a way to improve > shielding on these? Very old SB16 cards (the ones with IDE controllers) are quite good but the newer generations are to be avoided. The last time I asked a friend on this subject he gave a pointer to a 8 in 4 out audio card. That's not suitable for such a project. My best guess it to pipe a numerical signal to an hi-fi numerical amplifier. -- %!PS Il n'y a pas de mauvaises reponses, il n'y a que de mauvaises questions /B{bind def}def/m{moveto}B/d{dup}B/s{gsave}B/r{grestore}B/S{stroke}B/P{false charpath}B/G{setgray}B/W{setlinewidth}B/z{0 G 1 W}B/Times-Roman findfont 120 scalefont setfont 60 10 m 56 rotate(elrond@netdev.net)d d s z 40 40 rmoveto P S r s 0.5 G .5 W P flattenpath{newpath m 40 40 rlineto S}d{}{}pathforall r s z P S r 400 120 m (Bertrand) show 400 -160 m (Petit) show showpage To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 1 11:10:25 1999 Delivered-To: freebsd-small@freebsd.org Received: from atlconn1.panamsat.com (unknown [208.217.183.161]) by hub.freebsd.org (Postfix) with ESMTP id 12345151A4 for ; Thu, 1 Apr 1999 11:10:17 -0800 (PST) (envelope-from RFischer@PanAmSat.com) Received: by ATLCONN1 with Internet Mail Service (5.5.2232.9) id ; Thu, 1 Apr 1999 14:18:39 -0500 Message-ID: <2179AABD7346D111A51400805F85B816A6F2AE@LBHEXCH1> From: "Fischer, Roger" To: "'freebsd-small@freebsd.org'" Subject: PicoBSD boot error? Date: Thu, 1 Apr 1999 14:08:54 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for jumping to the mailing list so fast. I couldn't find any documentation on the website. I downloaded the "dialup" version of PicoBSD and installed it on a floppy. When I tried to boot it on an IBM ThinkPad 600, I got the welcome screen and then the following error, repeating over and over and over... Error: D:0x0 C:6 H:1 S:7 Error: D:0x0 C:6 H:1 S:7 Error: D:0x0 C:6 H:1 S:7 Error: D:0x0 C:6 H:1 S:7 Error: D:0x0 C:6 H:1 S:7 Error: D:0x0 C:6 H:1 S:7 ... Is there an installation FAQ or something I can go to so I don't need to bother the mailing list with trivial questions like this? Thanks, Roger Roger G. Fischer Email: rfischer@panamsat.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 1 11:24:29 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 459E114C22 for ; Thu, 1 Apr 1999 11:24:26 -0800 (PST) (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 MAA02472; Thu, 1 Apr 1999 12:24:09 -0700 (MST) (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 MAA20166; Thu, 1 Apr 1999 12:24:10 -0700 (MST) Message-Id: <199904011924.MAA20166@harmony.village.org> To: "Fischer, Roger" Subject: Re: PicoBSD boot error? Cc: "'freebsd-small@freebsd.org'" In-reply-to: Your message of "Thu, 01 Apr 1999 14:08:54 EST." <2179AABD7346D111A51400805F85B816A6F2AE@LBHEXCH1> References: <2179AABD7346D111A51400805F85B816A6F2AE@LBHEXCH1> Date: Thu, 01 Apr 1999 12:24:10 -0700 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <2179AABD7346D111A51400805F85B816A6F2AE@LBHEXCH1> "Fischer, Roger" writes: : When I tried to boot it on an IBM ThinkPad 600, : I got the welcome screen and then the following : error, repeating over and over and over... : Error: D:0x0 C:6 H:1 S:7 The FAQ doesn't cover this, exactly. However, it means that track 6 of your floppy is bad. Try another floppy. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 1 11:45: 3 1999 Delivered-To: freebsd-small@freebsd.org Received: from pele1.bjc.org (pele1.bjc.org [199.217.143.98]) by hub.freebsd.org (Postfix) with SMTP id 789D914C22 for ; Thu, 1 Apr 1999 11:44:58 -0800 (PST) (envelope-from GPL3866@bjcmail.carenet.org) Received: by pele1.bjc.org; id NAA09757; Thu, 1 Apr 1999 13:36:43 -0600 Received: from bjcmail.carenet.org(159.251.103.47) by pele1.bjc.org via smap (4.1) id xma008413; Thu, 1 Apr 99 13:33:54 -0600 Received: FROM rhtntsrv01 BY rhtntsrv01.carenet.org ; Thu Apr 01 13:40:16 1999 Received: from BJ4-Message_Server by rhtntsrv01 with Novell_GroupWise; Thu, 01 Apr 1999 13:40:15 -0600 Message-Id: X-Mailer: Novell GroupWise 5.5 Date: Thu, 01 Apr 1999 13:40:09 -0600 From: "Patrick Light" To: Subject: Re: PicoBSD boot error? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sounds like the floppy might have a bad sector. Did you format the disk = with DOS before dd'ing it? That usually clears up bad sector problems. >>> "Fischer, Roger" 04/01 1:08 PM >>> Sorry for jumping to the mailing list so fast. I couldn't find any documentation on the website. I downloaded the "dialup" version of PicoBSD and installed it on a floppy. When I tried to boot it on an IBM ThinkPad 600, I got the welcome screen and then the following error, repeating over and over and over... Error: D:0x0 C:6 H:1 S:7 Error: D:0x0 C:6 H:1 S:7 Error: D:0x0 C:6 H:1 S:7 Error: D:0x0 C:6 H:1 S:7 Error: D:0x0 C:6 H:1 S:7 Error: D:0x0 C:6 H:1 S:7 ... Is there an installation FAQ or something I can go to so I don't need to bother the mailing list with trivial questions like this? Thanks, Roger Roger G. Fischer Email: rfischer@panamsat.com=20 =20 To Unsubscribe: send mail to majordomo@FreeBSD.org=20 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 Thu Apr 1 11:51:10 1999 Delivered-To: freebsd-small@freebsd.org Received: from bbs.mpcs.com (bbs.mpcs.com [209.101.88.2]) by hub.freebsd.org (Postfix) with ESMTP id 7650114E3A for ; Thu, 1 Apr 1999 11:50:59 -0800 (PST) (envelope-from hg@penny.n2wx.ampr.org) Received: from pickle.n2wx.ampr.org (cc1017255-a.srst1.fl.home.com [24.3.122.197]) by bbs.mpcs.com (8.8.8/8.8.8/MPCS spamzap) with ESMTP id OAA17313 for ; Thu, 1 Apr 1999 14:50:38 -0500 Received: (from root@localhost) by pickle.n2wx.ampr.org (8.9.2/8.8.2/n2wx) id OAA15913 for freebsd-small@freebsd.org; Thu, 1 Apr 1999 14:50:37 -0500 (EST) Received: from penny.n2wx.ampr.org (penny.n2wx.ampr.org [172.16.0.5]) by pickle.n2wx.ampr.org (8.9.2/8.9.2/n2wx) with ESMTP id OAA15907 for ; Thu, 1 Apr 1999 14:50:32 -0500 (EST) (envelope-from hg@n2wx.ampr.org) Received: (from hg@localhost) by penny.n2wx.ampr.org (8.9.2/8.8.8/n2wx) id OAA34593; Thu, 1 Apr 1999 14:50:30 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14083.52742.463595.834769@penny.south.mpcs.com> Date: Thu, 1 Apr 1999 14:50:30 -0500 (EST) From: Howard Goldstein To: freebsd-small@freebsd.org Subject: MFS_ROOT as sync mount - ? X-Mailer: VM 6.62 under Emacs 19.34.1 Reply-To: hgoldste@bbs.mpcs.com Organization: disorganization Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to build my picobsd so as to have it do its MFS_ROOT mount as a synchronous mount. Does anyone know the proper incantation? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 1 14:47:26 1999 Delivered-To: freebsd-small@freebsd.org Received: from atlconn1.panamsat.com (unknown [208.217.183.161]) by hub.freebsd.org (Postfix) with ESMTP id 9AAA414D5C for ; Thu, 1 Apr 1999 14:47:17 -0800 (PST) (envelope-from RFischer@PanAmSat.com) Received: by ATLCONN1 with Internet Mail Service (5.5.2232.9) id ; Thu, 1 Apr 1999 17:55:39 -0500 Message-ID: <2179AABD7346D111A51400805F85B816A6F2B1@LBHEXCH1> From: "Fischer, Roger" To: 'Warner Losh' Cc: "'freebsd-small@freebsd.org'" Subject: RE: PicoBSD boot error? Date: Thu, 1 Apr 1999 17:45:53 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yep, That was the error, thanks. Funny, I reformatted the floppy, and ran a disk check on it and it still tested OK, but wouldn't work. I put the image on a new floppy, and it worked fine. ciao, Rog -----Original Message----- From: Warner Losh [mailto:imp@harmony.village.org] Sent: Thursday, April 01, 1999 11:24 AM To: Fischer, Roger Cc: 'freebsd-small@freebsd.org' Subject: Re: PicoBSD boot error? In message <2179AABD7346D111A51400805F85B816A6F2AE@LBHEXCH1> "Fischer, Roger" writes: : When I tried to boot it on an IBM ThinkPad 600, : I got the welcome screen and then the following : error, repeating over and over and over... : Error: D:0x0 C:6 H:1 S:7 The FAQ doesn't cover this, exactly. However, it means that track 6 of your floppy is bad. Try another floppy. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 1 14:49:47 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 18D3E1527A for ; Thu, 1 Apr 1999 14:49:36 -0800 (PST) (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 PAA02905; Thu, 1 Apr 1999 15:49:19 -0700 (MST) (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 PAA21123; Thu, 1 Apr 1999 15:49:23 -0700 (MST) Message-Id: <199904012249.PAA21123@harmony.village.org> To: "Fischer, Roger" Subject: Re: PicoBSD boot error? Cc: "'freebsd-small@freebsd.org'" In-reply-to: Your message of "Thu, 01 Apr 1999 17:45:53 EST." <2179AABD7346D111A51400805F85B816A6F2B1@LBHEXCH1> References: <2179AABD7346D111A51400805F85B816A6F2B1@LBHEXCH1> Date: Thu, 01 Apr 1999 15:49:22 -0700 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <2179AABD7346D111A51400805F85B816A6F2B1@LBHEXCH1> "Fischer, Roger" writes: : Funny, I reformatted the floppy, and ran a disk check : on it and it still tested OK, but wouldn't work. I had a very similar problem recently. The only thing I different between the disk that worked and the one that didn't was to make the lable, then apply it to the disk (this worked) rather than writing directly on the lable that was there already with a soft pen (this failed). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 1 20:32: 9 1999 Delivered-To: freebsd-small@freebsd.org Received: from mail.badger1.net (mail.badger1.net [207.113.50.4]) by hub.freebsd.org (Postfix) with ESMTP id 5FB6415E0D for ; Thu, 1 Apr 1999 20:32:05 -0800 (PST) (envelope-from roger@badger1.net) Received: from [192.168.0.4] (max.badger1.net [207.113.50.199]) by mail.badger1.net (8.8.7/8.8.7) with ESMTP id UAA22819 for ; Thu, 1 Apr 1999 20:31:44 -0800 X-Sender: roger@mail.badger1.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 1 Apr 1999 20:31:50 -0800 To: freebsd-small@freebsd.org From: Roger Fischer Subject: Newbie Network questions Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hope that these questions aren't too stupid. I'm sorta a newbie at this. I've got the dial-up version of picoBSD running on my Mac running VirtualPC. (Boots right up really slick like) I'll be running in on an IBM ThinkPad with a PCI ethernet card too. Question, Is there a command similar to dmesg to see what hardware pico recognizes? Stuff on bootup scrolls by too fast to read. VirtualPC emulates a DEC 21041 based PCI Ethernet card. How do I configure the ethernet interface? I didn't see it in the FAQ. Another question concerning mounting my DOS partitions. mount -t msdos /dev/wd0s1 /dos works to mount the c: partition on my WinNT machine at work. What would be the device of my D: partition? Is there a way to view the partitions on the harddisk? And, this command didn't work to mount the hard drive partitions on Virtual PC. I got an error that states... msdos: /dev/wd0s1: Device not configured Any ideas? sorry if these are totally stupid questions. Thanks, Roger Roger Fischer roger@badger1.net http://www.badger1.net %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% When once you have tasted flight, you will always walk the earth with your eyes turned skyward; for there you have been and there you will always be. -Leonardo da Vinci 1452-1519 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 1 20:41:14 1999 Delivered-To: freebsd-small@freebsd.org Received: from mail.badger1.net (mail.badger1.net [207.113.50.4]) by hub.freebsd.org (Postfix) with ESMTP id A58C81564C for ; Thu, 1 Apr 1999 20:41:04 -0800 (PST) (envelope-from roger@badger1.net) Received: from [192.168.0.4] (max.badger1.net [207.113.50.199]) by mail.badger1.net (8.8.7/8.8.7) with ESMTP id UAA22861 for ; Thu, 1 Apr 1999 20:40:44 -0800 X-Sender: roger@mail.badger1.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 1 Apr 1999 20:40:45 -0800 To: freebsd-small@freebsd.org From: Roger Fischer Subject: Is there a need to add a new user? Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a need to add a new user? or just use root? I notice that there is neither an /etc/passwd file, nor a vipw command to edit the file. I tried adding myself (roger) as a user by editing master.passwd, then created a directory, but when I tried to chown the directory to roger, I got an error that said "no such user". I also noticed that there was no "passwd" command. can a password be changed? Thanks, Roger Roger Fischer roger@badger1.net http://www.badger1.net %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% When once you have tasted flight, you will always walk the earth with your eyes turned skyward; for there you have been and there you will always be. -Leonardo da Vinci 1452-1519 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 1 22:11: 9 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 3C04614E6B for ; Thu, 1 Apr 1999 22:11:05 -0800 (PST) (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 XAA00227 for ; Thu, 1 Apr 1999 23:10:58 -0700 (MST) (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 XAA37250 for ; Thu, 1 Apr 1999 23:10:55 -0700 (MST) Message-Id: <199904020610.XAA37250@harmony.village.org> To: freebsd-small@freebsd.org Subject: named Date: Thu, 01 Apr 1999 23:10:54 -0700 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm close to getting my ssh/socks5/named/mail system replaced with a PicoBSD disk. I've got ssh and socks5 on there now, and will be writing a simple conncetion forwarding client to handle mail. However, that does leave me with named to get up and running. Or would that be possible to do with a simple udp forwarding program as well (ala netcat). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Apr 2 0:20:27 1999 Delivered-To: freebsd-small@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id B3ACC154F8 for ; Fri, 2 Apr 1999 00:20:19 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 53DFF18C6; Fri, 2 Apr 1999 10:20:09 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 4FC9349BE; Fri, 2 Apr 1999 10:20:09 +0200 (CEST) Date: Fri, 2 Apr 1999 10:20:09 +0200 (CEST) From: Andrzej Bialecki To: Warner Losh Cc: freebsd-small@FreeBSD.ORG Subject: Re: picobsd? In-Reply-To: <199904011708.KAA19397@harmony.village.org> 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, 1 Apr 1999, Warner Losh wrote: > In message Andrzej Bialecki writes: > : So far I've never really investigated such cases, but using another floppy > : almost always helped... A bug in the fd driver? Bad floppy? Who knows... > > I tried another floppy, and that one worked. So, after all, it seems we have some buglet in fd code, because there was obviously some CRC error which should be reported when formatting... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Apr 2 0:52: 7 1999 Delivered-To: freebsd-small@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id C0ACD14E65 for ; Fri, 2 Apr 1999 00:52:05 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 0120218C6; Fri, 2 Apr 1999 10:51:56 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 0048449BE; Fri, 2 Apr 1999 10:51:55 +0200 (CEST) Date: Fri, 2 Apr 1999 10:51:55 +0200 (CEST) From: Andrzej Bialecki To: Warner Losh Cc: freebsd-small@FreeBSD.ORG Subject: Re: named In-Reply-To: <199904020610.XAA37250@harmony.village.org> 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, 1 Apr 1999, Warner Losh wrote: > > I'm close to getting my ssh/socks5/named/mail system replaced with a > PicoBSD disk. I've got ssh and socks5 on there now, and will be > writing a simple conncetion forwarding client to handle mail. > However, that does leave me with named to get up and running. Or > would that be possible to do with a simple udp forwarding program as > well (ala netcat). I kind of remember reading somewhere about freely available, primitive, barebones DNS server. If I could only recall its name... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Apr 2 7:51:17 1999 Delivered-To: freebsd-small@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id B306714D37 for ; Fri, 2 Apr 1999 07:51:07 -0800 (PST) (envelope-from alhoang@nortelnetworks.com) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id HAA28603; Fri, 2 Apr 1999 07:47:13 -0800 (PST) Received: from mailhost.corpeast.BayNetworks.COM (ns3.corpeast.baynetworks.com [132.245.135.91]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id HAA25156; Fri, 2 Apr 1999 07:50:14 -0800 (PST) Received: from bl-mail2.corpeast.BayNetworks.com (bl-mail2-hme0.corpeast.baynetworks.com [132.245.135.83]) by mailhost.corpeast.BayNetworks.COM (SMI-8.6/BNET-97/05/05-S) with SMTP id KAA27559; Fri, 2 Apr 1999 10:50:08 -0500 for Received: from mantra1 ([132.245.156.24]) by bl-mail2.corpeast.BayNetworks.com (Post.Office MTA v3.5.1 release 219 ID# 0-51848U14000L14000S0V35) with SMTP id com; Fri, 2 Apr 1999 10:51:47 -0500 Message-Id: <3.0.32.19990402103955.00b29e80@bl-mail2.corpeast.baynetworks.com> X-Sender: ahoang@bl-mail2.corpeast.baynetworks.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 02 Apr 1999 10:39:56 -0500 To: Warner Losh From: Alain Hoang Subject: Re: PocketBSD Cc: freebsd-small@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Unfortunately I didn't have alot of time to really sit down and read it and come up with any really good English equivalent but I just wanted to give you a sumary of http://www.kt.rim.or.jp/~chick/PocketBSD/. Basically it's a small description of the web page writer's life with portables and how he started with a Sharp pokekon (Pocket Console?) and how he moved to a HP-200LX which broke and he moved to a Palm Pilot later. I think he moved to one other platform however my Japanese Reader barfed on this so I can't make out what he was saying on that part. The next part is a description of the Mini Package system that was came up with (not sure if he did it) since he found the Ports collection to FreeBSD very handy however it won't fit on the platform he is using however by stripping away the manual pages and other things a Mini Package could be created which is what you see there and he goes on to describe packages that have been ported to Mini Ports. Notably mutt, smpost, a Japanese IME and Perl4. Unfortunately there's not alot of HW specs or technical details of that sort on the page that might be able to help. Hope that might help. Sorry for the very rough description but time time time. Best Regards, Alain Hoang alhoang@nortelnetworks.com At 12:49 PM 3/28/99 -0700, you wrote: >In message <199903281937.MAA22743@harmony.village.org> Warner Losh writes: >: There may be 26 languages in their initial menu, but I don't see any >: way to translate a Japanese document into english. How would I get a >: translation of, say, the document at >: http://www.kt.rim.or.jp/~chick/PocketBSD/ > >BTW, after a little digging, I did find systrans pro, but that runs >$1000 for a single user license. Not exactly a good investment for >what I want it for. Too bad SYSTRAMS Personal doesn't support even >unidirectional translation from Japanese -> English, as the Personal >system is only $30 for unidirectional or $50 for bidirectional. > >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 Apr 2 12:17:20 1999 Delivered-To: freebsd-small@freebsd.org Received: from internetdevices.com (idi-fk-gw.abhiweb.com [205.138.236.250]) by hub.freebsd.org (Postfix) with ESMTP id DE97D14FF6 for ; Fri, 2 Apr 1999 12:17:17 -0800 (PST) (envelope-from wwolfe@internetdevices.com) Received: from pc-wwolfe (localhost [127.0.0.1]) by internetdevices.com (8.8.7/8.8.7) with SMTP id MAA03780 for ; Fri, 2 Apr 1999 12:16:29 -0800 (PST) Message-ID: <002201be7d45$e2e311a0$e9ec10ac@pc-wwolfe.internetdevices.com> From: "Wendell Wolfe" To: Subject: subscribe wwolfe@internetdevices.com Date: Fri, 2 Apr 1999 12:17:52 -0800 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.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe wwolfe@internetdevices.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Apr 5 7:13:32 1999 Delivered-To: freebsd-small@freebsd.org Received: from internexus.net (internexus.net [206.152.14.2]) by hub.freebsd.org (Postfix) with SMTP id 04E5615479 for ; Mon, 5 Apr 1999 07:13:30 -0700 (PDT) (envelope-from cliff@cliffsworld.com) Received: (qmail 31765 invoked from network); 5 Apr 1999 14:11:31 -0000 Received: from ppp2.internexus.net (HELO mother) (206.152.14.194) by internexus.net with SMTP; 5 Apr 1999 14:11:31 -0000 Message-Id: <4.1.19990405101447.00d07570@mail.internexus.net> X-Sender: compat@mail.internexus.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 05 Apr 1999 10:15:02 -0400 To: freebsd-small@freebsd.org From: cliff ainsworth III Subject: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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 Apr 5 8: 7: 1 1999 Delivered-To: freebsd-small@freebsd.org Received: from ftp.twin-city.net (unknown [208.8.246.210]) by hub.freebsd.org (Postfix) with ESMTP id 651D714D21 for ; Mon, 5 Apr 1999 08:06:43 -0700 (PDT) (envelope-from mark@twin-city.net) X-Transmitted-to: hub.freebsd.org [204.216.27.18] ;Mon, 05 Apr 1999 08:13:18 -0700 Received: from mark (208.8.246.204) by twin-city.net (Viking/1.04-290) with SMTP for ; Mon, 05 Apr 1999 08:12:53 -0700 Message-ID: <011001be7f75$62f3d240$ccf608d0@mark> Subject: small install Date: Mon, 5 Apr 1999 08:02:54 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_010D_01BE7F3A.B59ABBC0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 To: From: "Mark Koskenmaki" Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_010D_01BE7F3A.B59ABBC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The reason I've gotten interested in picobsd (various flavors) is that = I'm fascinated with using freebsd in an assortment of low-end machines, = dedicated to single tasks (dns, router, ppp server, mail server). = However, I've read through the pages, and haven't seen how I get set up = to create my own installs. I'd actually like to put it on small hard = drives, instead of just a floppy. =20 I realize this isn't exactly what you're doing with it, but I'd like the = ability to compile support for various things into it that doesn't seem = to be available now. =20 Please pardon my ignorance. And, I didn't recall finding any = (understandable to me) references to doing this on the web pages. mark ------=_NextPart_000_010D_01BE7F3A.B59ABBC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
The reason I've gotten interested in = picobsd=20 (various flavors) is that I'm fascinated with using freebsd in an = assortment of=20 low-end machines, dedicated to single tasks (dns, router, ppp server, = mail=20 server).    However, I've read through the pages, and = haven't=20 seen how I get set up to create my own installs.    I'd = actually=20 like to put it on small hard drives, instead of just a = floppy.  =20
 
I realize this isn't exactly what = you're doing=20 with it, but I'd like the ability to  compile support for various = things=20 into it that doesn't seem to be available now.  
 
Please pardon my = ignorance.   And, I=20 didn't recall finding any (understandable to me) references to doing = this on the=20 web pages.
 
mark
 
 
------=_NextPart_000_010D_01BE7F3A.B59ABBC0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Apr 5 13:10:50 1999 Delivered-To: freebsd-small@freebsd.org Received: from internetdevices.com (idi-fk-gw.abhiweb.com [205.138.236.250]) by hub.freebsd.org (Postfix) with ESMTP id 365681547C for ; Mon, 5 Apr 1999 13:10:48 -0700 (PDT) (envelope-from wwolfe@internetdevices.com) Received: from pc-wwolfe (localhost [127.0.0.1]) by internetdevices.com (8.8.7/8.8.7) with SMTP id NAA16481 for ; Mon, 5 Apr 1999 13:08:35 -0700 (PDT) Message-ID: <00a201be7fa0$35ec5c10$e9ec10ac@pc-wwolfe.internetdevices.com> From: "Wendell Wolfe" To: Subject: Sysinstall boot disk Date: Mon, 5 Apr 1999 13:09:28 -0700 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.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am trying to recreate a boot disk. I have compiled several by going into the /usr/src/release directory and typing make boot.flp and correcting several make errors. I have done this with versions 2.7, 2.8, 3.1. My problem is when the floppy boots up it boots up fine then says starting MFS file system and stops. The next step would be just for it to run the sysinstall program. On all 3 the same thing happens they all stop at the same point. In the Crunch file the progs sysinstall is listed. Can someone explain to me how the kernel knows to run the sysinstall program instead of init once it has booted. If I am going about it the wrong way please let me know. I only want a boot floppy that runs sysinstall once it boots. Thanks, Wendell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 6 2:18:15 1999 Delivered-To: freebsd-small@freebsd.org Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (Postfix) with ESMTP id F407D151C4 for ; Tue, 6 Apr 1999 02:18:06 -0700 (PDT) (envelope-from Andrew.Holt@UK.Sun.COM) Received: from UK.Sun.COM ([129.156.85.58]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id CAA09090 for ; Tue, 6 Apr 1999 02:16:07 -0700 (PDT) Received: from sale-wts by UK.Sun.COM (SMI-8.6/SMI-SVR4-sd.fkk205) id KAA16663; Tue, 6 Apr 1999 10:16:06 +0100 Received: from my-home60 by sale-wts (SMI-8.6/SMI-SVR4-se.fkk202) id KAA17863; Tue, 6 Apr 1999 10:16:06 +0100 Date: Tue, 6 Apr 1999 10:13:00 +0100 (BST) From: Andrew Holt Reply-To: Andrew Holt Subject: subscribe To: freebsd-small@freebsd.org 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 subscribe ----------------------------------------------------------------------------- Another month ends ... All targets met, All systems working, All customers satisfied, All staff eager and enthusiastic, All Pigs fed and ready to fly ----------------------------------------------------------------------------- Andrew Holt email: andrew.holt@uk.sun.com Technical Consultant phone: (0161) 905 8070 Sun Professional Services (Custom Engineering) City gate, Cross Street, Sale,Cheshire, M33 7JR ----------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 8 9: 7:59 1999 Delivered-To: freebsd-small@freebsd.org Received: from hotmail.com (unknown [216.32.180.116]) by hub.freebsd.org (Postfix) with SMTP id 5DBDF14C93 for ; Thu, 8 Apr 1999 09:07:53 -0700 (PDT) (envelope-from garyfitz@hotmail.com) Received: (qmail 2866 invoked by uid 65534); 8 Apr 1999 16:05:49 -0000 Message-ID: <19990408160549.2865.qmail@hotmail.com> X-Originating-IP: [208.254.86.69] From: "Gary Fitz" To: Subject: subscribe Date: Thu, 8 Apr 1999 12:06:32 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0017_01BE81B8.3E430DE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0017_01BE81B8.3E430DE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable subscribe ------=_NextPart_000_0017_01BE81B8.3E430DE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
subscribe
------=_NextPart_000_0017_01BE81B8.3E430DE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 8 12:51: 9 1999 Delivered-To: freebsd-small@freebsd.org Received: from otto.oss.uswest.net (otto.oss.uswest.net [204.147.85.81]) by hub.freebsd.org (Postfix) with ESMTP id 05EFE14DE0 for ; Thu, 8 Apr 1999 12:50:57 -0700 (PDT) (envelope-from pmckenna@otto.oss.uswest.net) Received: (from pmckenna@localhost) by otto.oss.uswest.net (8.9.3/8.9.2) id OAA86338 for freebsd-small@FreeBSD.org; Thu, 8 Apr 1999 14:48:33 -0500 (CDT) (envelope-from pmckenna) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 08 Apr 1999 14:48:33 -0500 (CDT) From: Pete Mckenna To: freebsd-small@FreeBSD.org Subject: pico with ssh and sysinstall under 3.1 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get lots of these when trying to use ssh and / or sysinstall with the pico dial build. Is it crunching out needed code in an attempt to shrink things ? What can I do ? This is from stable source cvsupped today. sysinstall.lo: In function `userAddUser': sysinstall.lo(.text+0x13d49): undefined reference to `dialog_clear_norefresh' sysinstall.lo(.text+0x13d50): undefined reference to `use_helpfile' sysinstall.lo: In function `slice_wizard': sysinstall.lo(.text+0x14348): undefined reference to `Debug_Disk' sysinstall.lo(.text+0x1434e): undefined reference to `CheckRules' sysinstall.lo(.text+0x1448f): undefined reference to `Delete_Chunk' sysinstall.lo(.text+0x144df): undefined reference to `All_FreeBSD' sysinstall.lo(.text+0x14540): undefined reference to `Set_Bios_Geom' sysinstall.lo(.text+0x14564): undefined reference to `Disk_Names' sysinstall.lo(.text+0x1462a): undefined reference to `Create_Chunk' sysinstall.lo(.text+0x1466f): undefined reference to `Open_Disk' sysinstall.lo(.text+0x1467e): undefined reference to `Free_Disk' sysinstall.lo(.text+0x146de): undefined reference to `Write_Disk' sysinstall.lo(.text+0x146f7): undefined reference to `Free_Disk' sysinstall.lo(.text+0x146fe): undefined reference to `Open_Disk' sysinstall.lo(.text+0x147c6): undefined reference to `chunk_n' sysinstall.lo(.text+0x147e3): undefined reference to `chunk_n' sysinstall.lo(.text+0x147f9): undefined reference to `chunk_n' cc -O -pipe -DCRUNCHED_BINARY -c crunch1.c cc -static -o crunch1 crunch1.o init.lo getty.lo ssh.lo ppp.lo ftp.lo telnet.lo ee.lo gzip.lo more.lo ash.lo test.lo kget.lo echo.lo pwd.lo msg.lo stty.lo hostname.lo cat.lo kill.lo sps.lo vm.lo ns.lo chmod.lo chown.lo help.lo cp.lo df.lo fsck.lo ping.lo mv.lo ln.lo traceroute.lo ifconfig.lo kbdcontrol.lo moused.lo ls.lo mkdir.lo mount.lo mount_msdos.lo mount_cd9660.lo mount_ext2fs.lo rm.lo route.lo sysctl.lo umount.lo vidcontrol.lo -ll -ledit -lutil -lmd -lcrypt -lftpio -lgnuregex -lmp -lgmp -lm -lncurses -lmytinfo -lipx -lz -ltermcap -ltelnet -lalias ssh.lo: In function `rsa_public_encrypt': ssh.lo(.text+0xf41e): undefined reference to `R_RandomInit' ssh.lo(.text+0xf457): undefined reference to `R_RandomUpdate' ssh.lo(.text+0xf477): undefined reference to `RSAPublicEncrypt' ssh.lo(.text+0xf497): undefined reference to `R_RandomFinal' ssh.lo: In function `rsa_private_decrypt': ssh.lo(.text+0xf522): undefined reference to `RSAPrivateDecrypt' ---------------------------------- E-Mail: Pete Mckenna Date: 08-Apr-99 Time: 14:28:16 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 8 13:27: 7 1999 Delivered-To: freebsd-small@freebsd.org Received: from ns.quantum.ru (ns.quantum.ru [193.125.201.2]) by hub.freebsd.org (Postfix) with ESMTP id A9EE515076 for ; Thu, 8 Apr 1999 13:26:33 -0700 (PDT) (envelope-from dsk@quantum.ru) Received: from dennis (ppp1.quantum.ru [193.125.201.28]) by ns.quantum.ru (8.9.1/8.9.1) with SMTP id AAA04446 for ; Fri, 9 Apr 1999 00:27:59 +0400 (MSD) From: "Dennis S. Kulikov" To: Subject: Date: Fri, 9 Apr 1999 00:24:27 +0400 Message-ID: <01be81fd$ccf3eec0$1cc97dc1@dennis> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 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 Apr 12 0:10:59 1999 Delivered-To: freebsd-small@freebsd.org Received: from didone.econ.unian.it (didone.econ.unian.it [193.205.135.210]) by hub.freebsd.org (Postfix) with ESMTP id 9438C150B6 for ; Mon, 12 Apr 1999 00:10:49 -0700 (PDT) (envelope-from stefano@posta.econ.unian.it) Received: from posta.econ.unian.it (posta.econ.unian.it [193.205.135.212]) by didone.econ.unian.it (8.8.8/8.8.8/Debian/GNU) with ESMTP id JAA14877 for ; Mon, 12 Apr 1999 09:08:28 +0200 Message-Id: <199904120708.JAA14877@didone.econ.unian.it> Received: from VILLAREY/SpoolDir by posta.econ.unian.it (Mercury 1.31); 12 Apr 99 09:04:28 GMT+1 Received: from SpoolDir by VILLAREY (Mercury 1.31); 12 Apr 99 09:04:26 GMT+1 From: "Stefano Luchetta" To: freebsd-small@freebsd.org Date: Mon, 12 Apr 1999 09:04:17 MET MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: X-mailer: Pegasus Mail for Win32 (v3.01a) 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 Tue Apr 13 6:12:36 1999 Delivered-To: freebsd-small@freebsd.org Received: from maila.enctc.edu.tw (maila.enctc.edu.tw [203.72.152.9]) by hub.freebsd.org (Postfix) with ESMTP id 9915D153F1 for ; Tue, 13 Apr 1999 06:12:22 -0700 (PDT) (envelope-from proo@maila.enctc.edu.tw) Received: from maila.enctc.edu.tw (dhcp-1-744.giga.net.tw [203.133.28.128] (may be forged)) by maila.enctc.edu.tw (8.9.1/8.9.1) with ESMTP id VAA00978 for ; Tue, 13 Apr 1999 21:12:22 GMT (envelope-from proo@maila.enctc.edu.tw) Message-ID: <3713421B.37D5FEE6@maila.enctc.edu.tw> Date: Tue, 13 Apr 1999 21:09:47 +0800 From: proo X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: small@freebsd.org Subject: freebsd-small Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 13 10:18:17 1999 Delivered-To: freebsd-small@freebsd.org Received: from dfw-ix1.ix.netcom.com (dfw-ix1.ix.netcom.com [206.214.98.1]) by hub.freebsd.org (Postfix) with ESMTP id 0630415722 for ; Tue, 13 Apr 1999 10:18:12 -0700 (PDT) (envelope-from dp@lore.org) Received: (from smap@localhost) by dfw-ix1.ix.netcom.com (8.8.4/8.8.4) id MAA23542 for ; Tue, 13 Apr 1999 12:15:49 -0500 (CDT) Received: from mail.fosterfarms.com(216.102.51.2) by dfw-ix1.ix.netcom.com via smap (V1.3) id rma023401; Tue Apr 13 12:14:51 1999 Message-ID: <37135E44.6B49200F@lore.org> Date: Tue, 13 Apr 1999 08:09:56 -0700 From: Dale Phillips X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-small dphi@ix.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 13 13:46:55 1999 Delivered-To: freebsd-small@freebsd.org Received: from lunatic.oneinsane.net (lunatic.oneinsane.net [207.113.133.231]) by hub.freebsd.org (Postfix) with ESMTP id BEF0414E84 for ; Tue, 13 Apr 1999 13:46:52 -0700 (PDT) (envelope-from insane@lunatic.oneinsane.net) Received: (from insane@localhost) by lunatic.oneinsane.net (8.9.2/8.9.2) id NAA75787 for freebsd-small@freebsd.org; Tue, 13 Apr 1999 13:44:33 -0700 (PDT) (envelope-from insane) Date: Tue, 13 Apr 1999 13:44:33 -0700 From: "Ron 'The InSaNe One' Rosson" To: freebsd-small@freebsd.org Subject: PicoBSD Configuration Message-ID: <19990413134432.A72348@lunatic.oneinsane.net> Reply-To: insane@oneinsane.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD lunatic.oneinsane.net 3.1-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane-pgp5i.txt X-Uptime: 1:43PM up 2 days, 19:57, 4 users, load averages: 0.00, 0.02, 0.00 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am wondering if it is possible to build a PicoBSD floppy that will act as a DHCP client and do NAT. Trying to find alternatives for for COX@Home here in San Diego, CA for a Relative. TIA -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void ------------------------------------------------------------------- I started out with nothing and I still have most of it left To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 13 21: 5:40 1999 Delivered-To: freebsd-small@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id CD06914D2F for ; Tue, 13 Apr 1999 21:05:37 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id AAA21131; Wed, 14 Apr 1999 00:03:17 -0400 (EDT) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id AAA28479; Wed, 14 Apr 1999 00:03:16 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990413134432.A72348@lunatic.oneinsane.net> Date: Wed, 14 Apr 1999 00:03:16 -0400 (EDT) From: John Baldwin To: "Ron 'The InSaNe One' Rosson" Subject: RE: PicoBSD Configuration Cc: freebsd-small@freebsd.org Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Apr-99 Ron 'The InSaNe One' Rosson wrote: > I am wondering if it is possible to build a PicoBSD floppy that > will act as a DHCP client and do NAT. Trying to find alternatives > for for COX@Home here in San Diego, CA for a Relative. Don't see why it wouldn't be. Just create a custom config, add natd to the crunch, and either add dhcp to the crunch or build a static binary that you copy onto the disk. Just look at the examples in /usr/src/release/picobsd adn go from there. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 14 6:48:32 1999 Delivered-To: freebsd-small@freebsd.org Received: from ns.quantum.ru (ns.quantum.ru [193.125.201.2]) by hub.freebsd.org (Postfix) with ESMTP id 632D614BDE for ; Wed, 14 Apr 1999 06:47:55 -0700 (PDT) (envelope-from dsk@quantum.ru) Received: from dennis (denis.quantum.ru [193.125.201.20]) by ns.quantum.ru (8.9.1/8.9.1) with SMTP id RAA18120 for ; Wed, 14 Apr 1999 17:49:02 +0400 (MSD) Message-ID: <001301be86d9$c0525900$14c97dc1@quantum.ru.quantum.ru> From: "Dennis S. Kulikov" To: Subject: Date: Wed, 14 Apr 1999 17:48:17 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0010_01BE869E.FA830D80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0010_01BE869E.FA830D80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable subscribe dsk@quantum.ru ------=_NextPart_000_0010_01BE869E.FA830D80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
subscribe = dsk@quantum.ru
------=_NextPart_000_0010_01BE869E.FA830D80-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 14 12: 0:57 1999 Delivered-To: freebsd-small@freebsd.org Received: from freja.webgiro.com (unknown [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id A3C86157DA for ; Wed, 14 Apr 1999 12:00:40 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id A3A0818C6; Wed, 14 Apr 1999 20:58:22 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id A2CAC4992; Wed, 14 Apr 1999 20:58:22 +0200 (CEST) Date: Wed, 14 Apr 1999 20:58:22 +0200 (CEST) From: Andrzej Bialecki To: Wendell Wolfe Cc: freebsd-small@FreeBSD.ORG Subject: Re: Sysinstall boot disk In-Reply-To: <00a201be7fa0$35ec5c10$e9ec10ac@pc-wwolfe.internetdevices.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 Mon, 5 Apr 1999, Wendell Wolfe wrote: > In the Crunch file the progs sysinstall is listed. Can someone explain to > me > how the kernel knows to run the sysinstall program instead of init once it > has booted. If I am going about it the wrong way please let me know. > I only want a boot floppy that runs sysinstall once it boots. It simply tries to execute the following programs: /sbin/init /sbin/init.bak /sbin/oinit /stand/sysinstall Your symptoms look like there is no init nor sysinstall on your MFS root. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 14 17:56:26 1999 Delivered-To: freebsd-small@freebsd.org Received: from phluffy.fks.bt (net25-cust199.pdx.wantweb.net [24.236.25.199]) by hub.freebsd.org (Postfix) with ESMTP id 832C714E05 for ; Wed, 14 Apr 1999 17:56:18 -0700 (PDT) (envelope-from myke@ees.com) Received: from localhost (myke@localhost) by phluffy.fks.bt (8.8.8/8.8.8) with ESMTP id RAA03723; Wed, 14 Apr 1999 17:53:50 -0700 (PDT) (envelope-from myke@ees.com) Date: Wed, 14 Apr 1999 17:53:49 -0700 (PDT) From: Mike Holling X-Sender: myke@phluffy.fks.bt To: "Ron 'The InSaNe One' Rosson" Cc: freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD Configuration In-Reply-To: <19990413134432.A72348@lunatic.oneinsane.net> 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 > I am wondering if it is possible to build a PicoBSD floppy that > will act as a DHCP client and do NAT. Trying to find alternatives > for for COX@Home here in San Diego, CA for a Relative. I did this very thing a few months ago. I've been wanting to contribute it back to PicoBSD, but it requires using pieces of the DHCP port and so there's no clean way to build it. I corresponded briefly with Andrzej back then and he said that he was setting up a framework that would make this easier. Unfortunately I've been pretty busy this month and haven't had time to see if that's happened yet. Anyway, it's pretty straightforward. I used the WIDE dhcp port, and built dhcpc statically linked. Then I modified the crunch Makefile to incorporate the dhcpc bits, and now I have dhcpc available on the floppy. I added the dhcpd server too and a small program so that you can have PicoBSD get an IP via dhcp on the external interface, and then offer private (10.0.0.x) IPs with the learned DNS server to the internal LAN hosts. It works really well, a handful of people are using it and no one's had any kind of problems. I'd be happy to help you out in any way to get this working. - Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 15 11:56:16 1999 Delivered-To: freebsd-small@freebsd.org Received: from csad.coventry.ac.uk (unknown [194.66.38.38]) by hub.freebsd.org (Postfix) with SMTP id 1D284158D1 for ; Thu, 15 Apr 1999 11:56:13 -0700 (PDT) (envelope-from justin@csad.coventry.ac.uk) Received: (qmail 2250 invoked by uid 901); 15 Apr 1999 18:53:57 -0000 Date: 15 Apr 1999 18:53:57 -0000 Message-ID: <19990415185357.2249.qmail@csad.coventry.ac.uk> From: justin@csad.coventry.ac.uk To: freebsd-small@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-URL: http://www.freebsd.org/~picobsd/ X-Mailer: Lynx, Version 2.8rel.2 X-Personal_name: Justin Murdock Subject: Any other small BSDs out there? Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, I've done the advocacy bit, but the company turned round and called my bluff. They're new product is supposed to have CE, but there are some interesting problems. Hardware consists of: Mips processor (That's why I asked about *other* BSDs) 16MB Flash ROM 16/32MB RAM Optional 80MB Flash Disk Touch screen. IR link. Do any of you have any ideas as to where I could look, how much time/money a proof of concept would take, how much time/money a stable platform would need. It's for running dedicated applications on - surveying meter readings &c. (I was suggesting FreeBSD for their wintel laptops, but that didn't stop them trying to torpedo me with this :) justin justin@csad.coventry.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 15 12: 6:43 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 927A614BE7 for ; Thu, 15 Apr 1999 12:06:11 -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 NAA46291; Thu, 15 Apr 1999 13:03:40 -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 NAA03549; Thu, 15 Apr 1999 13:03:31 -0600 (MDT) Message-Id: <199904151903.NAA03549@harmony.village.org> To: justin@csad.coventry.ac.uk Subject: Re: Any other small BSDs out there? Cc: freebsd-small@FreeBSD.ORG In-reply-to: Your message of "15 Apr 1999 18:53:57 -0000." <19990415185357.2249.qmail@csad.coventry.ac.uk> References: <19990415185357.2249.qmail@csad.coventry.ac.uk> Date: Thu, 15 Apr 1999 13:03:31 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990415185357.2249.qmail@csad.coventry.ac.uk> justin@csad.coventry.ac.uk writes: : Do any of you have any ideas as to where I could look, : how much time/money a proof of concept would take, : how much time/money a stable platform would need. Hmmm. Sounds like a fun MIPS device. There is currently an effort underway to get NetBSD running on MIPS based handhelds. Specifically NEC Vr41xx based PDAs. This is being done by a group of Japanese hackers and isn't stable yet, to the best of my knowledge (my MIPS based PDA comes in tomorrow or Monday). They have written a boot loader as well for WinCE. There is also another effort to get the R39xx based PDAs working with Linux, but I'm only allowed to mention it in passing. There is another effort to get Linux working on a WINCE based X/Win terminal which uses Vr4300, but I can't talk about it more than that. What kind of MIPS processor is there? I'm available for consulting on this :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Apr 17 2: 3:55 1999 Delivered-To: freebsd-small@freebsd.org Received: from Hedgehog.Intranet (d6.si.ru [195.128.76.56]) by hub.freebsd.org (Postfix) with ESMTP id 9E56F14D79 for ; Sat, 17 Apr 1999 02:03:50 -0700 (PDT) (envelope-from laskavy@Berkeley.Gambit.Msk.SU) Received: (from laskavy@localhost) by Hedgehog.Intranet (8.9.2/8.9.2) id NAA00666; Sat, 17 Apr 1999 13:01:23 +0400 (MSD) (envelope-from laskavy) Date: Sat, 17 Apr 1999 13:01:23 +0400 (MSD) From: "óÅÒÇÅÊ ó. ìÁÓËÁ×ÙÊ" Message-Id: <199904170901.NAA00666@Hedgehog.Intranet> To: freebsd-small@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit X-URL: mailto:freebsd-small@freebsd.org X-Mailer: Lynx, Version 2.8.2dev.17 Subject: PicoBSD, the Small BSD Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >What is PicoBSD? > > PicoBSD is a one floppy version of FreeBSD 3.0-current, which in its -----------------------------------------------^^^^^^^^^^^ We want to update this > different variations allows you to have secure dialup access, small > diskless router or even a dial-in server. And all this on only one > standard 1.44MB floppy. It runs on a minimum 386SX CPU with 8MB of RAM > (no HDD required!). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Apr 17 18:27:39 1999 Delivered-To: freebsd-small@freebsd.org Received: from Thanatos.Shenton.Org (Thanatos.Shenton.Org [209.31.147.195]) by hub.freebsd.org (Postfix) with ESMTP id 6ECA614EE9 for ; Sat, 17 Apr 1999 18:27:34 -0700 (PDT) (envelope-from chris@shenton.org) Received: (from chris@localhost) by Thanatos.Shenton.Org (8.9.3/8.9.2) id VAA75382; Sat, 17 Apr 1999 21:33:15 -0400 (EDT) (envelope-from chris) To: freebsd-small@freebsd.org Subject: "kernel" way too large, name not as in docs From: Chris Shenton Date: 17 Apr 1999 21:33:13 -0400 Message-ID: <87r9piww4m.fsf@Thanatos.Shenton.Org> Lines: 44 X-Mailer: Gnus v5.6.45/Emacs 20.3 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Been starting to play with building a PicoBSD kernel for a diskless PPP dial-out box to NAT my LAN. I'd like to be able to hand these out to friends and customers cuz they can't seem to get NT to do this, especially with leased lines. I'm using 3.1-STABLE built from cvsup a few hours ago. I followed the "build" process as described in the docs in the .../picobsd/doc/ dir and don't see a "picobsd.bin" kernel as described in the docs. I do see a "kernel" in the build dir but it's way too large for a floppy. Further it doesn't seem to change with different selections of dial, router, net, or isp. Is there some "make clean" I need to do first? It does seem to be installing old kernel images from .../sys/compile/PICOBSD-*.*/ rather than generating new ones the second time around. Below are the sizes of the kernel and fs.PICOBSD built in "build/" as well as the "kernel" built in /sys/PICOBSD-*.*/: __FILE_____SIZE__________________________ SELECTED_TYPE kernel fs.PICOBSD PICOBSD-*.*/kernel dial (init) 2917359 1638400 2917359 dial (oinit) 2917359 1638400 ?? router 2917359 839680 1925446 net 2917359 1740800 2892088 isp 3309508 1740800 3309508 I just did a build of isp (something I hadn't done earlier) as I was typing this and saw it announcing its load-up: loading kernel text data bss dec hex filename 1212986 1828508 141728 3183222 309276 kernel So on the name issue, is it just that the doc is out of sync with the build process and "kernel" is what I really want? Any hints why my kernel is sooooo large? This looks like cool stuff and I'm anxious to start playing with it. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Apr 18 23:39:13 1999 Delivered-To: freebsd-small@freebsd.org Received: from FreeBSD.IM.ntu.edu.tw (freebsd.im.ntu.edu.tw [140.112.106.205]) by hub.freebsd.org (Postfix) with ESMTP id ACC4014E51 for ; Sun, 18 Apr 1999 23:37:45 -0700 (PDT) (envelope-from eric@FreeBSD.IM.ntu.edu.tw) Received: from localhost (eric@localhost) by FreeBSD.IM.ntu.edu.tw (8.9.3/8.9.1) with ESMTP id OAA14190; Mon, 19 Apr 1999 14:34:32 +0800 (CST) (envelope-from eric@FreeBSD.IM.ntu.edu.tw) Date: Mon, 19 Apr 1999 14:34:32 +0800 (CST) From: Eric To: Warner Losh Cc: justin@csad.coventry.ac.uk, freebsd-small@FreeBSD.ORG Subject: Re: Any other small BSDs out there? In-Reply-To: <199904151903.NAA03549@harmony.village.org> 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, 15 Apr 1999, Warner Losh wrote: > In message <19990415185357.2249.qmail@csad.coventry.ac.uk> > justin@csad.coventry.ac.uk writes: > underway to get NetBSD running on MIPS based handhelds. Specifically > NEC Vr41xx based PDAs. This is being done by a group of Japanese How can the BSD/Linux be Romized ??? Boot from MFS and then write a special boot loader? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Apr 18 23:44:47 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 956ED15160 for ; Sun, 18 Apr 1999 23:44:45 -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 AAA57682; Mon, 19 Apr 1999 00:41: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 AAA20658; Mon, 19 Apr 1999 00:41:39 -0600 (MDT) Message-Id: <199904190641.AAA20658@harmony.village.org> To: Eric Subject: Re: Any other small BSDs out there? Cc: justin@csad.coventry.ac.uk, freebsd-small@FreeBSD.ORG In-reply-to: Your message of "Mon, 19 Apr 1999 14:34:32 +0800." References: Date: Mon, 19 Apr 1999 00:41:39 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Eric writes: : How can the BSD/Linux be Romized ??? : Boot from MFS and then write a special boot loader? You do need a special boot loader to boot from WinCE. BSD can be romized by using a MFS root. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 21 21: 9:52 1999 Delivered-To: freebsd-small@freebsd.org Received: from skynet.my.domain (ppp27.internexus.net [206.152.14.219]) by hub.freebsd.org (Postfix) with ESMTP id AAA4D158CA for ; Wed, 21 Apr 1999 21:08:50 -0700 (PDT) (envelope-from cliff@cliffsworld.com) Received: from cliffsworld.com (localhost.my.domain [127.0.0.1]) by skynet.my.domain (8.9.2/8.9.2) with ESMTP id AAA03286 for ; Thu, 22 Apr 1999 00:09:38 -0400 (EDT) (envelope-from cliff@cliffsworld.com) Message-ID: <371EA101.85F2C30@cliffsworld.com> Date: Thu, 22 Apr 1999 00:09:37 -0400 From: cliff ainsworth III Reply-To: freebsd@cliffsworld.com Organization: http://www.cliffsworld.com X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 3.1-RELEASE i386) MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: what to do with an old 486 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have this 486/33 with 20 megs of ram, a 125 meg hard drive and a Netgear nic. I would like to use it as a dial out box for my lan. I have a Netgear hub. I would love to use PicoBSD as my server and possibly be able to dial back into it. Does Pico support multilink PPP like FreeBSD does? OpenBSD and NetBSD don't support multilink yet. So I figured I would try Pico before I just install FreeBSD on it. Any ideas or suggested configs for it? Here's another question. since Pico is built on 3.0 does it support SMP? I don't see a reference to it so I shall assume not. thanx in advance -cliff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 21 21:15:54 1999 Delivered-To: freebsd-small@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 799E31593C for ; Wed, 21 Apr 1999 21:15:45 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA03460; Thu, 22 Apr 1999 13:43:16 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA86269; Thu, 22 Apr 1999 13:43:16 +0930 (CST) Date: Thu, 22 Apr 1999 13:43:16 +091800 From: Greg Lehey To: freebsd@cliffsworld.com Cc: freebsd-small@FreeBSD.ORG Subject: Re: what to do with an old 486 Message-ID: <19990422134315.N54567@freebie.lemis.com> References: <371EA101.85F2C30@cliffsworld.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <371EA101.85F2C30@cliffsworld.com>; from cliff ainsworth III on Thu, Apr 22, 1999 at 12:09:37AM -0400 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 22 April 1999 at 0:09:37 -0400, cliff ainsworth III wrote: > I have this 486/33 with 20 megs of ram, a 125 meg hard drive and a > Netgear nic. I would like to use it as a dial out box for my lan. I have > a Netgear hub. I would love to use PicoBSD as my server and possibly be > able to dial back into it. Does Pico support multilink PPP like FreeBSD > does? OpenBSD and NetBSD don't support multilink yet. So I figured I > would try Pico before I just install FreeBSD on it. Any ideas or > suggested configs for it? Here's another question. since Pico is built > on 3.0 does it support SMP? I don't see a reference to it so I shall > assume not. PicoBSD will support whatever you can cram into the disk. But why bother? It's much easier just to install FreeBSD on the hard disk. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 21 22:39:34 1999 Delivered-To: freebsd-small@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id CB56B14F5B for ; Wed, 21 Apr 1999 22:39:32 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id WAA09000; Wed, 21 Apr 1999 22:37:02 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199904220537.WAA09000@freeway.dcfinc.com> Subject: Re: what to do with an old 486 In-Reply-To: <371EA101.85F2C30@cliffsworld.com> from cliff ainsworth III at "Apr 22, 99 00:09:37 am" To: freebsd@cliffsworld.com Date: Wed, 21 Apr 1999 22:37:02 -0700 (MST) Cc: freebsd-small@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, cliff ainsworth III wrote: > I have this 486/33 with 20 megs of ram, a 125 meg hard drive and a > Netgear nic. I would like to use it as a dial out box for my lan. I have > a Netgear hub. I would love to use PicoBSD as my server and possibly be > able to dial back into it. Does Pico support multilink PPP like FreeBSD > does? OpenBSD and NetBSD don't support multilink yet. So I figured I > would try Pico before I just install FreeBSD on it. Any ideas or > suggested configs for it? Here's another question. since Pico is built > on 3.0 does it support SMP? I don't see a reference to it so I shall > assume not. No offense, but if you've got a 125 meg hard drive on the machine, why not just run FreeBSD. I think 2.2.8 would do you just fine, and you'd have access to a larger universe of fellow travellers if you needed help. I'd run PicoBSD on diskless (or floppy only) machines. I've run FreeBSD in as small a machine as a 386/20 laptop with an 80 meg hard drive and 8 meg of RAM. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 22 0:50:14 1999 Delivered-To: freebsd-small@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id F3C1514DBD for ; Thu, 22 Apr 1999 00:50:08 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id DAA10964; Thu, 22 Apr 1999 03:47:34 -0400 (EDT) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id DAA01704; Thu, 22 Apr 1999 03:47:34 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <371EA101.85F2C30@cliffsworld.com> Date: Thu, 22 Apr 1999 03:47:33 -0400 (EDT) From: John Baldwin To: freebsd@cliffsworld.com Subject: RE: what to do with an old 486 Cc: freebsd-small@freebsd.org Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Apr-99 cliff ainsworth III wrote: > I have this 486/33 with 20 megs of ram, a 125 meg hard drive and a > Netgear nic. I would like to use it as a dial out box for my lan. I have > a Netgear hub. I would love to use PicoBSD as my server and possibly be > able to dial back into it. Does Pico support multilink PPP like FreeBSD > does? OpenBSD and NetBSD don't support multilink yet. So I figured I > would try Pico before I just install FreeBSD on it. Any ideas or > suggested configs for it? Here's another question. since Pico is built > on 3.0 does it support SMP? I don't see a reference to it so I shall > assume not. It doesn't support SMP by default, but you could easily build your own that had SMP support in about 10 minutes or so. As for supporting multilink PPP, if FreeBSD does, then Pico does, since it uses the same exact ppp program. :) Hope this helps. > thanx in advance > > -cliff --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 22 4: 9: 6 1999 Delivered-To: freebsd-small@freebsd.org Received: from relay03.netaddress.usa.net (relay03.netaddress.usa.net [204.68.24.183]) by hub.freebsd.org (Postfix) with SMTP id 75620153C7 for ; Thu, 22 Apr 1999 04:08:19 -0700 (PDT) (envelope-from thepinkpages@usa.net) Received: (qmail 17536 invoked from network); 22 Apr 1999 11:05:50 -0000 Received: from nw175.netaddress.usa.net (204.68.24.75) by outbound.netaddress.usa.net with SMTP; 22 Apr 1999 11:05:50 -0000 Received: (qmail 27643 invoked by uid 60001); 22 Apr 1999 11:05:49 -0000 Message-ID: <19990422110549.27642.qmail@nw175.netaddress.usa.net> Received: from 204.68.24.75 by nw175 via web-mailer(M3.0.0.70) on Thu Apr 22 11:05:49 GMT 1999 Date: 22 Apr 99 05:05:49 MDT From: To: freebsd-small@freebsd.org Subject: subscribe X-Mailer: USANET web-mailer (M3.0.0.70) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe ____________________________________________________________________ Get free e-mail and a permanent address at http://www.netaddress.com/?N=3D= 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Apr 26 20:57:30 1999 Delivered-To: freebsd-small@freebsd.org Received: from astart4.astart.com (astart4.astart.com [206.71.174.196]) by hub.freebsd.org (Postfix) with ESMTP id D97421530F for ; Mon, 26 Apr 1999 20:57:10 -0700 (PDT) (envelope-from papowell@astart4.astart.com) Received: (from papowell@localhost) by astart4.astart.com (8.8.8/8.8.8) id UAA21200; Mon, 26 Apr 1999 20:56:11 -0700 (PDT) Date: Mon, 26 Apr 1999 20:56:11 -0700 (PDT) From: papowell@astart4.astart.com Message-Id: <199904270356.UAA21200@astart4.astart.com> To: freebsd-small@freebsd.org Subject: Need help with FreeBSD 3.1 - problems Cc: papowell@astart4.astart.com Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Let me start with an aside on this. A couple of months ago I was given a demonstration of the picobsd floppy for network, and was surprised at how much it had. It was cool. Neat. Nifty. So, suddenly (Monday, 8:00 AM) I have been shoved into the horrible position of needing to regenerate and make such a floppy, but this time with some UGLY drivers in it. By Friday. No problem - I just cd /usr/src/release/picobsd and do the cd build sh build - run the script, get the stuff working, THEN use my already working kernel - no sweat. the build dies several horrible deaths - this is NOT what I expected with FreeBSD... I yank the phone out of the wall, stoke up on coffee, painkillers, and cancel my appointment to have my teeth worked on. (Perhaps there is a bright side to this.) Use the brutal diagnostic techniques I am infamous for, i.e. - tracing each and every step of the Make and Shell scripts I make the following incredible discoveries. 1. stage 1 references /usr/mdec/boot0, etc etc. This is not there any more... it now appears to be /boot/boot0, etc. So I use /boot/boot0 2. During stage2, crunchgen is used to extract the object files for /usr/src/usr.sbin/ppp it fails to get the chap_MS.o object, and during the crunch build you get a missing file. No problem. I can live without ppp. 3. During stage3, we get references to /usr/mdec/boot0, which we know about.... and suddenly we have: dd if=/usr/mdec/boot1 of=picobsd.bin conv=notrunc 2> /dev/null disklabel -Brw -b /usr/mdec/fdboot -s /usr/mdec/bootfd \ /dev/rvn0 fd1440 2>&1 >/ dev/null Ummm... /usr/mdec/fdboot does not exist, /usr/mdec/bootfd does not exist... Sigh... The Distribution HAD this stuff, it uses it. What the &*()(*&*() is going on? I discover that the /usr/src/release/Makefile is truly a MFH (Makefile From Hell). I fight my way through, slaying princesses, flaming toads, and watering dragons (you know what I mean)... To suddenly discover that THEY DON'T USE THE SAME METHOD TO BUILD THE FLOPPY This is from the Necrocommunicomnicon... I mean the Makefile... Here is where I threw in the probverbial towel. /usr/src/Makefile: # Now, just to get this picture down once and for all: # # +------------------------------------------------------------------------+ # |boot.flp | # +-----+-----+------------------------------------------------------------+ # |boot1|boot2|floppy filesystem "bootfd" | # +-----+-----+-+--------------------------------------------------------+-+ # |kernel | # +------------+-----------------------------------------+-+ # |mfs filesystem "mfsfd" | # +-----------------------------------------+ # **** OK, This I understand **** release.8: write_mfs_in_kernel dumpnlist rm -rf ${RD}/mfsfd mkdir ${RD}/mfsfd cd ${RD}/mfsfd && \ mkdir -p etc dev mnt stand/help @cd ${.CURDIR} && $(MAKE) installCRUNCH CRUNCH=boot \ DIR=${RD}/mfsfd/stand ZIP=false ( cd ${RD}/trees/bin/dev && \ ls console tty ttyv0 ttyv1 ttyv2 ttyv3 null zero | \ cpio -dump ${RD}/mfsfd/dev ) **** and a lot of stuff, where they put files lovingly in place *** But they never seem to GENERATE THE BOOT floppy. ****************************** ** OFFER ** ****************************** If somebody can help me out with this in the next couple of days, I will personally give them A. BSD Daemon Tshirt by Phil Foglio, the fellow who did the first daemon. Ummm.... OK OK, so it will be one of a couple of HUNDRED we will be giving away, but it is still a T shirt. B. A Free Dinner at the next USENIX and/or LISA Conference. And yes, you can bring a couple of buddies along as well. C. A free LPRng print spooler CD. Printer not included. Sigh... Patrick Powell Astart Technologies, papowell@astart.com 9475 Chesapeake Drive, Suite D, Network and System San Diego, CA 92123 Consulting 619-874-6543 FAX 619-279-8424 LPRng - Print Spooler (http://www.astart.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 27 9: 7: 4 1999 Delivered-To: freebsd-small@freebsd.org Received: from cavecreations.com (cavecreations.com [192.41.27.30]) by hub.freebsd.org (Postfix) with ESMTP id C736815648 for ; Tue, 27 Apr 1999 09:06:51 -0700 (PDT) (envelope-from albert@achtung.com) Received: (cave@localhost) by cavecreations.com (8.8.5) id KAA28148; Tue, 27 Apr 1999 10:06:46 -0600 (MDT) Date: Tue, 27 Apr 1999 10:06:46 -0600 (MDT) Message-Id: <199904271606.KAA28148@cavecreations.com> From: To: freebsd-small@freebsd.org Cc: Subject: subscribe Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe -- Sent by Pop3Now, http://www.pop3now.com (c) 1998,1999 Cave Creations Corp. All rights reserved. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 27 10:30:29 1999 Delivered-To: freebsd-small@freebsd.org Received: from astart4.astart.com (astart4.astart.com [206.71.174.196]) by hub.freebsd.org (Postfix) with ESMTP id A034415569 for ; Tue, 27 Apr 1999 10:30:27 -0700 (PDT) (envelope-from papowell@astart4.astart.com) Received: (from papowell@localhost) by astart4.astart.com (8.8.8/8.8.8) id KAA27209 for freebsd-small@FreeBSD.ORG; Tue, 27 Apr 1999 10:29:29 -0700 (PDT) Date: Tue, 27 Apr 1999 10:29:29 -0700 (PDT) From: papowell@astart4.astart.com Message-Id: <199904271729.KAA27209@astart4.astart.com> To: freebsd-small@FreeBSD.ORG Subject: archive site for freebsd-mail Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hate to ask this, but I have just spend a slew of time trying to find this, but are the FreeBSD mailing lists archived somewhere? 1. If they are, could the FreeBSD.org main web page have a link to a page listing the locations of the sites? 2. If not, then perhaps somebody could arrange to have them archived on a site? Several seem to be doing this for other lists. Patrick ("history - those who do not learn by it are doomed to repeat it... but only if there are records") Powell Patrick ("History is written by the winners.") Powell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 27 11: 7:16 1999 Delivered-To: freebsd-small@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 54E2914D77 for ; Tue, 27 Apr 1999 11:07:13 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id AE20D18CB; Tue, 27 Apr 1999 20:07:25 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id AB25649C2; Tue, 27 Apr 1999 20:07:25 +0200 (CEST) Date: Tue, 27 Apr 1999 20:07:23 +0200 (CEST) From: Andrzej Bialecki To: papowell@astart4.astart.com Cc: freebsd-small@FreeBSD.ORG Subject: Re: archive site for freebsd-mail In-Reply-To: <199904271729.KAA27209@astart4.astart.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 Tue, 27 Apr 1999 papowell@astart4.astart.com wrote: > I hate to ask this, but I have just spend a slew of time > trying to find this, but are the FreeBSD mailing lists > archived somewhere? > > 1. If they are, could the FreeBSD.org main web page have a link > to a page listing the locations of the sites? They are, and the Web pages say so (http://www.freebsd.org/mail). Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 28 4:13:43 1999 Delivered-To: freebsd-small@freebsd.org Received: from ns.quantum.ru (ns.quantum.ru [193.125.201.2]) by hub.freebsd.org (Postfix) with ESMTP id 9C88915644 for ; Wed, 28 Apr 1999 04:12:54 -0700 (PDT) (envelope-from dsk@quantum.ru) Received: from denis (denis.quantum.ru [193.125.201.20]) by ns.quantum.ru (8.9.1/8.9.1) with SMTP id PAA21708 for ; Wed, 28 Apr 1999 15:16:49 +0400 (MSD) Message-ID: <001001be91c4$d2341a00$14c97dc1@quantum.ru.quantum.ru> From: "Dennis S. Kulikov" To: Subject: Date: Wed, 28 Apr 1999 15:16:49 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01BE918A.23790280" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.100 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.100 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000D_01BE918A.23790280 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable HI All! Does somebody install PicoBSD for i486, i386? All goes good? Dennis. ------=_NextPart_000_000D_01BE918A.23790280 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 HI All!
 Does somebody install PicoBSD for i486,=20 i386?
All goes good?
 
Dennis.
------=_NextPart_000_000D_01BE918A.23790280-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 28 4:35:38 1999 Delivered-To: freebsd-small@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id 8A8A6156D0 for ; Wed, 28 Apr 1999 04:35:32 -0700 (PDT) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.1/8.9.0) id VAA17111; Wed, 28 Apr 1999 21:35:09 +1000 (EST) Message-ID: <19990428213506.39937@welearn.com.au> Date: Wed, 28 Apr 1999 21:35:06 +1000 From: Sue Blake To: "Dennis S. Kulikov" Cc: freebsd-small@FreeBSD.ORG Subject: Re: your mail References: <001001be91c4$d2341a00$14c97dc1@quantum.ru.quantum.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <001001be91c4$d2341a00$14c97dc1@quantum.ru.quantum.ru>; from Dennis S. Kulikov on Wed, Apr 28, 1999 at 03:16:49PM -0700 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 28, 1999 at 03:16:49PM -0700, Dennis S. Kulikov wrote: > HI All! > Does somebody install PicoBSD for i486, i386? > All goes good? My mail/dns/web/router machine is a 386, and it has been working fine for 18 months. -- Regards, -*Sue*- (` () '` To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 28 9:58:15 1999 Delivered-To: freebsd-small@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id E2FE81540F for ; Wed, 28 Apr 1999 09:58:07 -0700 (PDT) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id NAA24891; Wed, 28 Apr 1999 13:17:49 -0400 (EDT) (envelope-from dervish) Date: Wed, 28 Apr 1999 13:17:49 -0400 From: Natty Rebel To: Sue Blake Cc: freebsd-small@freebsd.org Subject: Re: your mail Message-ID: <19990428131749.A24569@ikhala.tcimet.net> References: <001001be91c4$d2341a00$14c97dc1@quantum.ru.quantum.ru> <19990428213506.39937@welearn.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990428213506.39937@welearn.com.au>; from Sue Blake on Wed, Apr 28, 1999 at 09:35:06PM +1000 X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 2C CE A5 D7 FA 4D D5 FD 9A CC 2B 23 04 46 48 F8 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Sue Blake (sue@welearn.com.au): > On Wed, Apr 28, 1999 at 03:16:49PM -0700, Dennis S. Kulikov wrote: > > HI All! > > Does somebody install PicoBSD for i486, i386? > > All goes good? > > My mail/dns/web/router machine is a 386, and it has been working fine > for 18 months. hi sue, do you have an hdd on that box? > > -- > > Regards, > -*Sue*- > (` > () > '` #;^) i'khala -- natty rebel harder than the rest ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 28 10:40:34 1999 Delivered-To: freebsd-small@freebsd.org Received: from dfw-ix2.ix.netcom.com (dfw-ix2.ix.netcom.com [206.214.98.2]) by hub.freebsd.org (Postfix) with ESMTP id 19D9515456 for ; Wed, 28 Apr 1999 10:40:31 -0700 (PDT) (envelope-from sverzunov@netscaler.com) Received: (from smap@localhost) by dfw-ix2.ix.netcom.com (8.8.4/8.8.4) id MAA29282 for ; Wed, 28 Apr 1999 12:40:20 -0500 (CDT) Received: from sji-ca12-56.ix.netcom.com(205.186.214.184) by dfw-ix2.ix.netcom.com via smap (V1.3) id rma029149; Wed Apr 28 12:39:47 1999 Message-ID: <372745DE.D9AA2289@netscaler.com> Date: Wed, 28 Apr 1999 10:31:10 -0700 From: Sergey Verzunov Reply-To: sverzunov@netscaler.com Organization: NetScaler Inc. X-Mailer: Mozilla 4.06 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: Flash based system dump Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. Is there any method for dumping crashed kernel somewhere, when BSD works from small (24MB) flash disk. Did somebody face with such a problem? Thanks a lot. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 28 13:15:28 1999 Delivered-To: freebsd-small@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id DAC81157E7 for ; Wed, 28 Apr 1999 13:15:13 -0700 (PDT) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.1/8.9.0) id GAA19065; Thu, 29 Apr 1999 06:15:00 +1000 (EST) Message-ID: <19990429061455.49557@welearn.com.au> Date: Thu, 29 Apr 1999 06:14:55 +1000 From: Sue Blake To: Natty Rebel Cc: freebsd-small@FreeBSD.ORG Subject: Re: your mail References: <001001be91c4$d2341a00$14c97dc1@quantum.ru.quantum.ru> <19990428213506.39937@welearn.com.au> <19990428131749.A24569@ikhala.tcimet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19990428131749.A24569@ikhala.tcimet.net>; from Natty Rebel on Wed, Apr 28, 1999 at 01:17:49PM -0400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 28, 1999 at 01:17:49PM -0400, Natty Rebel wrote: > Quoting Sue Blake (sue@welearn.com.au): > > On Wed, Apr 28, 1999 at 03:16:49PM -0700, Dennis S. Kulikov wrote: > > > HI All! > > > Does somebody install PicoBSD for i486, i386? > > > All goes good? > > > > My mail/dns/web/router machine is a 386, and it has been working fine > > for 18 months. > hi sue, > do you have an hdd on that box? Yes, and it's not PicoBSD but it could be, since you can roll your own PicoBSD using the components of FreeBSD that you need. If you don't need to run a GUI, even a low end 386 will give surprising performance with an efficient operating system. Got a 386 handy? Try any standard issue PicoBSD floppy and see what it's like, bearing in mind you can build your own floppy if for example you need to choose different hardware support. It only takes a few minutes to try. Without a hard disk you could have yourself a nice little router/DNS machine, or a personal "portable" machine for dialling your ISP, using only equipment that was long ago written off. I've found a lot of dying floppy drives on very old machines, maybe coincidence, but if you do have a spare, hang on to it for peace of mind in case your luck is similar. My monitors die next, then much later power supplies, although many creaky old antiques just keep working year after year. -- Regards, -*Sue*- (` () '` To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 28 19:38:25 1999 Delivered-To: freebsd-small@freebsd.org Received: from astart4.astart.com (astart4.astart.com [206.71.174.196]) by hub.freebsd.org (Postfix) with ESMTP id B2F1914FA3 for ; Wed, 28 Apr 1999 19:38:21 -0700 (PDT) (envelope-from papowell@astart4.astart.com) Received: (from papowell@localhost) by astart4.astart.com (8.8.8/8.8.8) id TAA07823; Wed, 28 Apr 1999 19:37:17 -0700 (PDT) Date: Wed, 28 Apr 1999 19:37:17 -0700 (PDT) From: papowell@astart4.astart.com Message-Id: <199904290237.TAA07823@astart4.astart.com> To: abial@webgiro.com, papowell@astart4.astart.com Subject: Re: archive site for freebsd-mail Cc: freebsd-small@FreeBSD.ORG Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From abial@webgiro.com Tue Apr 27 11:06:16 1999 > Date: Tue, 27 Apr 1999 20:07:23 +0200 (CEST) > From: Andrzej Bialecki > To: papowell@astart4.astart.com > Cc: freebsd-small@FreeBSD.ORG > Subject: Re: archive site for freebsd-mail > > On Tue, 27 Apr 1999 papowell@astart4.astart.com wrote: > > > I hate to ask this, but I have just spend a slew of time > > trying to find this, but are the FreeBSD mailing lists > > archived somewhere? > > > > 1. If they are, could the FreeBSD.org main web page have a link > > to a page listing the locations of the sites? > > They are, and the Web pages say so (http://www.freebsd.org/mail). > > Andrzej Bialecki > > // WebGiro AB, Sweden (http://www.webgiro.com) > // ------------------------------------------------------------------- > // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- > > Voila! After a seriously hard day of pounding, code reading, and sacrificing my lunch time, I seem to have created a floppy... Not content with this, I have taken the various scripts, etc., and written comments for them. Now, you say 'WHY DO THIS'... I know, I know... comments... documentation... whimpy stuff. But perhaps this might help the next person. If there is any interest, I would be pleased/willing to post my notes on Generating PICOBSD Floppies Using FreeBSD 3.1-RELEASE Also, for your enjoyment, here is a description of just what happens during the boot process of the floppy, together with a massaged version of the 'stage3' script: ### we return to our original directory, and copy the kernel to the floppy image ### kernel cd ${pwd} cp kernel.gz /mnt/kernel.gz rm kernel.gz ### now we add the boot loader - boot1 and boot2 were done by disklabel ### ### Here is the boot sequence: ### (boot0 on floppy sector 0/0/1) loaded into memory and executed ### boot1 finds UNIX partition, brings in boot2, starts execution of boot2 ### Boot1 usually does things using BIOS facilities ### Boot2 has quite a bit of the UNIX ufs file system, and can understand UFS ### file systems. ### boot2 will open /boot.config, read THE SINGLE LINE IN THE FILE, ### and interpret it as the name of a kernel and some options to pass ### to the kernel. ### The PICOBSD setup initializes boot.config with ### /boot/loader ### which tells boot2 to use the /boot/loader code as a kernel. ### ### What is this all about? The answer is simple: we want to be able to ### configure the devices by using the 3rd Stage Loader. But this ### loader is a little big, so we use the kzip (kernel zip) facility ### to compress it and attach a bit of code to decompress and then run ### the compressed code. ### ### The /boot/loader will now uncompress itself and will then read the ### (documented in the source code) file ### /boot/loader.rc ### This contains a list of commands that the loader understands. ### (Aside: /boot/loader.rc used to be /boot/boot.conf in earlier FreeBSD ### releases, and this name is is pretty close to boot.config (see above). ### I wonder how many people this has confused?) ### ### The /boot/loader.rc file contains the following commands: ### load /kernel ### load -t userconfig_script /kernel.config ### boot -P ### (see /usr/src/boot/common/help.common for list of commands) ### ### load /kernel loads /kernel into memory, and the boot -P ### line will boot it with the -P (use serial console if no keyboard) option. ### (see man boot for details of the flags) ### ### The load -t userconfig_script /kernel.config ### sets the kernel's 'userconfig_script' option value to ### "/kernel.config". The 'userconfig' module in the kernel ### (see /usr/src/sys/i386/i386/userconfig.c for the nasty details) ### will open and read this file, getting commands to set device ### configuration and other things. ### These commands can be: ### example ### di disable dev di de0 ### dr drq dev # dr 4 ### ei # EISA slots ei 4 ### en enable dev en ep0 ### ex exit (quit) ex ### f flags dev mask f de0 0xff ### h help ### intro intro screen ### iom iomem dev addr iom ed0 0xdf0000 ### ios iosize dev size iosize ed0 0x1000 ### ir irq dev # irq ed0 5 ### l ls, list l ### pn pnp ... pnp ### po port dev addr port ed0 0x300 ### res reset CPU res ### q quit q ### v visual mode v ### ### I strongly suspect that this has been included strictly as a Tour de Force ### example of how to make the loading as flexible as possible, etc, without ### needing to compile a special version of the boot code. ### ### Finally, after all this work, the kernel is loaded into memory, ### and kernel execution is started. Of course we have compressed the ### kernel, so it will promptly uncompress itself and start execution. ### ### The userconfig module is started, it reads the /kernel.config file, ### and then, since we have generated our kernel with the INTRO_USERCONFIG ### option, the kernel will go into VISUAL userconfig ### operation. ### ### To stop the loader from going into /kernel.config ### user interactive mode automatically, you need to modify the ### PICOBSD configuration file. Remove the ### options INTRO_USERCONFIG #imply -c and parse info area ### And regenerate the kernel. ### ### Suggested Alternatives ### ### Skipping the /boot/loader ### To do this, set /boot.config to contain only '-P' ### By default, you will get the kernel loaded. You should also ### compile the kernel without the INTRO_USERCONFIG option. ### # we make a compressed loader mkdir /mnt/boot cp /boot/loader . kzip -v loader mv loader.kz /mnt/boot/loader rm -f loader loader.o # set up the /boot.config file to cause boot2 to load /boot/loader echo "/boot/loader" >/mnt/boot.config # set up the /boot/loader.rc to cause the /boot/loader to # load in the kernel and set options cat >/mnt/boot/loader.rc < Fixing permissions"; cd /mnt; chown -R root * ) ### little bit of information for users df -ik /mnt ls -Rl /mnt umount /mnt # and we are finished vnconfig -u /dev/rvn0 Patrick Powell Astart Technologies, papowell@astart.com 9475 Chesapeake Drive, Suite D, Network and System San Diego, CA 92123 Consulting 619-874-6543 FAX 619-279-8424 LPRng - Print Spooler (http://www.astart.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 28 20: 4:23 1999 Delivered-To: freebsd-small@freebsd.org Received: from astart4.astart.com (astart4.astart.com [206.71.174.196]) by hub.freebsd.org (Postfix) with ESMTP id 4468714E99 for ; Wed, 28 Apr 1999 20:04:21 -0700 (PDT) (envelope-from papowell@astart4.astart.com) Received: (from papowell@localhost) by astart4.astart.com (8.8.8/8.8.8) id UAA07892; Wed, 28 Apr 1999 20:03:19 -0700 (PDT) Date: Wed, 28 Apr 1999 20:03:19 -0700 (PDT) From: papowell@astart4.astart.com Message-Id: <199904290303.UAA07892@astart4.astart.com> To: freebsd-small@FreeBSD.ORG, sverzunov@netscaler.com Subject: Re: Flash based system dump Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From owner-freebsd-small@FreeBSD.ORG Wed Apr 28 10:39:37 1999 > Date: Wed, 28 Apr 1999 10:31:10 -0700 > From: Sergey Verzunov > To: freebsd-small@FreeBSD.ORG > Subject: Flash based system dump > > Hi. > > Is there any method for dumping crashed kernel somewhere, when BSD works > from small (24MB) flash > disk. > Did somebody face with such a problem? > > Thanks a lot. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message > This is usually a nasty problem, solved in different manners on different systems. If a system 'goes down' due to a panic, you can usually generate a core dump in a simple way - 1. Pass 1 - find out how big it is. 2. Pass 2 - write out starting at the top end of memory - 4 bytes 3. Put the length into the last 4 bytes. When you reboot your system, you use /dev/kmem (or whatever it is today) to go to the end of memory, pick up the length, go to where the start looks reasonable, and then copy the file to file. The good news is that if you have LOTS and LOTS of memory, this works fine. The bad news is that some UNIX systems INSIST on using the high memory for a work area, system area, etc. Been there more times than I want to think about. Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 28 20: 7:13 1999 Delivered-To: freebsd-small@freebsd.org Received: from astart4.astart.com (astart4.astart.com [206.71.174.196]) by hub.freebsd.org (Postfix) with ESMTP id 48983157E8 for ; Wed, 28 Apr 1999 20:07:11 -0700 (PDT) (envelope-from papowell@astart4.astart.com) Received: (from papowell@localhost) by astart4.astart.com (8.8.8/8.8.8) id UAA07910; Wed, 28 Apr 1999 20:05:49 -0700 (PDT) Date: Wed, 28 Apr 1999 20:05:49 -0700 (PDT) From: papowell@astart4.astart.com Message-Id: <199904290305.UAA07910@astart4.astart.com> To: dervish@ikhala.tcimet.net, sue@welearn.com.au Subject: Re: your mail Cc: freebsd-small@FreeBSD.ORG Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ummm... well... I just put up a print spooler on a 386 motherboard with 8 megs of RAM, 1.6Gig hard drive. Nobody noticed that they were no longer using an UltraSparc server. By the way, the system name was 'wimper'... Patrick ("Next time I use a toaster") Powell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 28 20:18:56 1999 Delivered-To: freebsd-small@freebsd.org Received: from members.unlimited.net (members.unlimited.net [209.186.200.8]) by hub.freebsd.org (Postfix) with ESMTP id 8A7271548B for ; Wed, 28 Apr 1999 20:18:53 -0700 (PDT) (envelope-from norami@unlimited.net) Received: from unlimited.net (ts3-103.unlimited.net [209.186.200.103]) by members.unlimited.net (8.8.7/8.8.5) with ESMTP id TAA25890; Wed, 28 Apr 1999 19:14:05 -0700 Message-ID: <3727D0E7.28337455@unlimited.net> Date: Wed, 28 Apr 1999 20:24:23 -0700 From: John Oram Reply-To: norami@unlimited.net Organization: norAmi X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: papowell@astart4.astart.com Cc: freebsd-small@FreeBSD.ORG Subject: Re: archive site for freebsd-mail References: <199904290237.TAA07823@astart4.astart.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patrick: You have NO IDEA just how much enjoyment I got out of this email!! You have saved a heck of a lot of work! I am not as proficent in FreeBSD OS as other stuff. Your step-by-step is saves many hours of frustration and false starts. Thank you very much! John O papowell@astart4.astart.com wrote: > *snip > Not content with this, I have taken the various scripts, etc., > and written comments for them. Now, you say 'WHY DO THIS'... > > I know, I know... comments... documentation... whimpy stuff. > > But perhaps this might help the next person. If there is any interest, > I would be pleased/willing to post my notes on > > Generating PICOBSD Floppies Using FreeBSD 3.1-RELEASE > > Also, for your enjoyment, * snip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 28 22:30:28 1999 Delivered-To: freebsd-small@freebsd.org Received: from astart4.astart.com (astart4.astart.com [206.71.174.196]) by hub.freebsd.org (Postfix) with ESMTP id 1080C14F22 for ; Wed, 28 Apr 1999 22:29:55 -0700 (PDT) (envelope-from papowell@astart4.astart.com) Received: (from papowell@localhost) by astart4.astart.com (8.8.8/8.8.8) id WAA08070; Wed, 28 Apr 1999 22:28:49 -0700 (PDT) Date: Wed, 28 Apr 1999 22:28:49 -0700 (PDT) From: papowell@astart4.astart.com Message-Id: <199904290528.WAA08070@astart4.astart.com> To: freebsd-small@FreeBSD.ORG Subject: Revised picobsd Build Procedures and Scripts (Not official) Cc: papowell@astart4.astart.com Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following is NOT repeat NOT an official update. Beware! Your milage may vary, not valid in states with right angle corner borders (quick! How many is that?) and has been shown to cause brain damage in student assistants. Enjoy. Note: My best regards, wishes, thanks, and admiration to Andrzej Bialecki Michael Bretterklieber Patrick ("Documentation? Hell, most of the staff here can't even THINK in sentences. Forth, PostScript, Perl, and Tcl/Tk has taken their toll.") Powell Patrick Powell Astart Technologies, papowell@astart.com 9475 Chesapeake Drive, Suite D, Network and System San Diego, CA 92123 Consulting 619-874-6543 FAX 619-279-8424 LPRng - Print Spooler (http://www.astart.com) Revised picobsd Build Procedures and Scripts For Compliance with FreeBSD 3.1-RELEASE Patrick Powell Wed Apr 28 20:26:09 PDT 1999 1. Modifications The modifications to the picobsd build procedures was done as a result of working only with the FreeBSD 3.1-RELEASE and reflects the current use of the various utilities. These include a. VNODE support b. disklabel utility c. newfs utility In addition, the scripts have been modified to allow a user specified configuration similar to the net, isp, router, dialer and custom provided by the original Build procedures. Finally, an effort was made to extend the scripts to handle more (and less) number of files in the various crunch, mfs.tree, and floppy.tree systems. 2. Missing kzip /usr/lib/aout files on FreeBSD 3.1-RELEASE The necessary library files for the kzip utility are missing on the FreeBSD 3.1-RELEASE. Do the following steps to create and install them: cd /usr/src/sys/i386/boot/kzipboot make all install Note: kzip is present, but for completeness, you create and install using: cd /usr/src/usr.bin/kzip make all install 3. Build Script Modifications build -> build + build_script The build script was modified and the 'build_kernel' function was extracted and made a separate file. This allows the set -e to be used and greated control of error detection and reporting during the build_kernel phase. The set -e option was used in all scripts to terminate at the first error. Checks for file existence were added to prevent the copying of a non-existent file to terminate operation. You can also specify a 'configuration' in a fashion similar to the isp, router, etc. The kernel naming conventions have been changed slightly to allow more flexibility in this. There were a bunch of initializations that needed to be fixed up when the user configuration stuff was done. 4. MFS and Floppy Image Generation The following modificiations were made in order to be compliant with the current VNODE support commands vnconfig, disklabel, and newfs. MFS Creation (stage1 script) umount /dev/vn0 2> /dev/null || true umount /mnt 2> /dev/null || true vnconfig -u /dev/rvn0 2> /dev/null || true dd of=fs.PICOBSD if=/dev/zero count=${SIZE} bs=1k 2> /dev/null vnconfig -s labels -c /dev/rvn0 fs.PICOBSD 2>/dev/null disklabel -rw vn0 auto INODES=4096 newfs -i $INODES -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null mount /dev/vn0c /mnt The dd command creates the fd.PICOBSD file, the vnconfig with the appropriate options will use it as a device, and then the disklabel command will simply label it. Note that since this is NOT a bootable device, no boot blocks need to be installed. Finally, we do a newfs to create the file system structure and then we mount it. Floppy Image file Creation (stage3 script) umount /dev/vn0 2> /dev/null || true umount /mnt 2> /dev/null || true vnconfig -u /dev/rvn0 2> /dev/null || true dd of=picobsd.bin if=/dev/zero count=1440 bs=1k 2> /dev/null vnconfig -c /dev/rvn0 picobsd.bin 2>/dev/null disklabel -Brw /dev/rvn0 fd1440 2>&1 >/dev/null newfs -i 4096 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null mount /dev/vn0c /mnt This is almost identical to the previous step, with the modified disklabel command. The -Brw option will cause boot blocks to be put onto the image, and the fd1440 disktab entry sets the geometry. The news command will create a disk with 4096 inodes - this has been reduce to 1024 in testing with no problems. Note that the number of inodes can be pretty small on the root system if you create an MFS system for general use. 4. Detailed Description of Boot Sequence The following is a detailed description of how the system boots from the boot floppy, and how this sequence relates to the commands in the stage3 file used to generate the boot disk. In the stage3 build script, we create and mount the floppy image on /mnt using the dd, vnconfig, newfs, and mount commands described above. The kernel has been created and compressed using gzip. We copy the kernel to the floppy image: cp kernel.gz /mnt/kernel.gz At this point, if we use dd to copy the floppy image to a floppy disk, we would discover that the boot loader could not handle a compressed kernel. In the past, this was handled by the kzip utility, which would compress the kernel and then prefix and append some code that would uncompress and then execute the kernel. We will use a different and rather more elaborate method for booting. Here is the boot sequence: (boot0 on floppy sector 0/0/1) loaded into memory and executed This is done by the PC BIOS. Boot1 uses the PC BIOS facilities, and is limited to reading a boot record by the various limitations of the PC BIOS facilities. boot1 finds UNIX partition, brings in boot2, starts execution of boot2 Boot1 looks at the partition table information and finds the 'active' partition and loads 'boot2' from a fixed location on the partition. Boot2 has quite a bit of the UNIX ufs file system, and can understand UFS file systems. boot2 will open /boot.config, read THE SINGLE LINE IN THE FILE, and interpret it as the name of a kernel and some options to pass to the kernel. You can interatively specify these values by pressing a key during the boot process and entering them at the prompt. The PICOBSD setup initializes boot.config with the line: /boot/loader which tells boot2 to use the /boot/loader code as a kernel. What is this all about? The answer is simple: we want to be able to configure the devices and we need a loader that is smart enough to uncompress our kernel. The boot3 loader (just called loader now) is a little big, so we use the kzip (kernel zip) facility to compress it and attach a bit of code to decompress and then run the compressed code. As I were saying, the boot2 loader copies the file /boot/loader into memory now executes it. The /boot/loader will now uncompress itself and will then read the (this is documented in the source code) file /boot/loader.rc This file contains a list of commands that the loader understands. (Aside: /boot/loader.rc used to be /boot/boot.conf in earlier FreeBSD releases, and this name is is pretty close to boot.config (see above). I wonder how many people this has confused?). If there are no commands then the /boot/loader will try to load kernel and then kernel.old by default. Note that kernel.gz and kernel.old.gz will also be tried. The /boot/loader.rc file on the floppy disk contains the following lines: load /kernel load -t userconfig_script /kernel.config boot -P If you are interested in this stuff, see /usr/src/boot/common/help.common for a complete list of commands understood by the loader. The load /kernel causes the loader to look for /kernel and /kernel.gz, which it will unzip and loader into memory. The load -t userconfig_script /kernel.config will cause the loader to pass to the kernel's a 'userconfig_script' option with the value "/kernel.config". The 'userconfig' module in the kernel (see /usr/src/sys/i386/i386/userconfig.c for the nasty details) will open and read this file, getting commands to set device configuration and other things. These commands can be: example di disable dev di de0 dr drq dev # dr 4 ei # EISA slots ei 4 en enable dev en ep0 ex exit (quit) ex f flags dev mask f de0 0xff h help intro intro screen iom iomem dev addr iom ed0 0xdf0000 ios iosize dev size iosize ed0 0x1000 ir irq dev # irq ed0 5 l ls, list l pn pnp (scan) pnp po port dev addr port ed0 0x300 res reset CPU res q quit q v visual mode v These commands are useful if you have a stock kernel and need to use it on systems with a differnt set of hardware. The need for port (io) address and interrupt modification is used only with ISA and not with PCI bus cards. The boot -P command line will boot it with the -P (use serial console if no keyboard) option. (see man boot for details of the flags). Finally, after all this work, the kernel is uncompressed and loaded into memory, and kernel execution is started. The kernel does its initialization, and then the userconfig kernel module is initialized. The 'userconfig_script' setting will cause it to it reads the /kernel.config file, and then, since we have generated our kernel with the INTRO_USERCONFIG option, the kernel will go into VISUAL userconfig operation. To stop the loader from going into /kernel.config user interactive mode automatically, you need to modify the PICOBSD configuration file. Comment out the following line: options INTRO_USERCONFIG #imply -c and parse and regenerate the kernel. Here are the commands used to set up all of this: # we make a compressed loader mkdir /mnt/boot cp /boot/loader . kzip -v loader mv loader.kz /mnt/boot/loader rm -f loader loader.o # set up the /boot.config file to cause boot2 to load /boot/loader echo "/boot/loader" >/mnt/boot.config # set up the /boot/loader.rc to cause the /boot/loader to # load in the kernel and set options cat >/mnt/boot/loader.rc <README << 'END-of-README' X Revised picobsd Build Procedures and Scripts X For Compliance with FreeBSD 3.1-RELEASE X Patrick Powell X Wed Apr 28 20:26:09 PDT 1999 X X1. Modifications X X The modifications to the picobsd build procedures was done X as a result of working only with the FreeBSD 3.1-RELEASE X and reflects the current use of the various utilities. X X These include X a. VNODE support X b. disklabel utility X c. newfs utility X X In addition, the scripts have been modified to allow a user X specified configuration similar to the net, isp, router, dialer X and custom provided by the original Build procedures. X X Finally, an effort was made to extend the scripts to handle more X (and less) number of files in the various crunch, mfs.tree, X and floppy.tree systems. X X X2. Missing kzip /usr/lib/aout files on FreeBSD 3.1-RELEASE X X The necessary library files for the kzip utility are missing on the X FreeBSD 3.1-RELEASE. Do the following steps to create and install them: X X cd /usr/src/sys/i386/boot/kzipboot X make all install X X Note: kzip is present, but for completeness, you create and install X using: X cd /usr/src/usr.bin/kzip X make all install X X3. Build Script Modifications X X build -> build + build_script X X The build script was modified and the 'build_kernel' X function was extracted and made a separate file. This allows X the set -e to be used and greated control of error detection X and reporting during the build_kernel phase. X X The set -e option was used in all scripts to terminate at the X first error. Checks for file existence were added to prevent X the copying of a non-existent file to terminate operation. X X4. MFS and Floppy Image Generation X X The following modificiations were made in order to be compliant X with the current VNODE support commands vnconfig, disklabel, X and newfs. X X MFS Creation (stage1 script) X X umount /dev/vn0 2> /dev/null || true X umount /mnt 2> /dev/null || true X vnconfig -u /dev/rvn0 2> /dev/null || true X dd of=fs.PICOBSD if=/dev/zero count=${SIZE} bs=1k 2> /dev/null X vnconfig -s labels -c /dev/rvn0 fs.PICOBSD 2>/dev/null X disklabel -rw vn0 auto X INODES=4096 X newfs -i $INODES -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null X mount /dev/vn0c /mnt X X The dd command creates the fd.PICOBSD file, the X vnconfig with the appropriate options will use it as a X device, and then the disklabel command will simply label it. X Note that since this is NOT a bootable device, no boot blocks X need to be installed. Finally, we do a newfs to create the X file system structure and then we mount it. X X Floppy Image file Creation (stage3 script) X X umount /dev/vn0 2> /dev/null || true X umount /mnt 2> /dev/null || true X vnconfig -u /dev/rvn0 2> /dev/null || true X dd of=picobsd.bin if=/dev/zero count=1440 bs=1k 2> /dev/null X vnconfig -c /dev/rvn0 picobsd.bin 2>/dev/null X disklabel -Brw /dev/rvn0 fd1440 2>&1 >/dev/null X newfs -i 4096 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null X mount /dev/vn0c /mnt X X This is almost identical to the previous step, with the X modified disklabel command. The -Brw option will cause X boot blocks to be put onto the image, and the fd1440 X disktab entry sets the geometry. The news command will X create a disk with 4096 inodes - this has been reduce to X 1024 in testing with no problems. Note that the number of X inodes can be pretty small on the root system if you create X an MFS system for general use. X X4. Detailed Description of Boot Sequence X XThe following is a detailed description of how the system boots Xfrom the boot floppy, and how this sequence relates to the commands Xin the stage3 file used to generate the boot disk. X XIn the stage3 build script, we create and mount the floppy image Xon /mnt using the dd, vnconfig, newfs, and mount commands described Xabove. X XThe kernel has been created and compressed using gzip. We copy Xthe kernel to the floppy image: X X cp kernel.gz /mnt/kernel.gz X X XAt this point, if we use dd to copy the floppy image to a floppy Xdisk, we would discover that the boot loader could not handle a Xcompressed kernel. In the past, this was handled by the kzip Xutility, which would compress the kernel and then prefix and append Xsome code that would uncompress and then execute the kernel. We Xwill use a different and rather more elaborate method for booting. X X XHere is the boot sequence: X X (boot0 on floppy sector 0/0/1) loaded into memory and executed X XThis is done by the PC BIOS. Boot1 uses the PC BIOS facilities, Xand is limited to reading a boot record by the various limitations Xof the PC BIOS facilities. X X boot1 finds UNIX partition, brings in boot2, starts execution of boot2 X XBoot1 looks at the partition table information and finds the 'active' Xpartition and loads 'boot2' from a fixed location on the partition. X X XBoot2 has quite a bit of the UNIX ufs file system, and can understand XUFS file systems. boot2 will open /boot.config, read THE SINGLE XLINE IN THE FILE, and interpret it as the name of a kernel and some Xoptions to pass to the kernel. You can interatively specify these Xvalues by pressing a key during the boot process and entering them Xat the prompt. X XThe PICOBSD setup initializes boot.config with the line: X X /boot/loader X Xwhich tells boot2 to use the /boot/loader code as a kernel. X XWhat is this all about? The answer is simple: we want to be able to Xconfigure the devices and we need a loader that is smart enough Xto uncompress our kernel. The boot3 loader (just called loader now) Xis a little big, so we use the kzip (kernel zip) facility Xto compress it and attach a bit of code to decompress and then run Xthe compressed code. X X XAs I were saying, the boot2 loader copies the file /boot/loader Xinto memory now executes it. The /boot/loader will now uncompress Xitself and will then read the (this is documented in the source Xcode) file X X /boot/loader.rc X XThis file contains a list of commands that the loader understands. X(Aside: /boot/loader.rc used to be /boot/boot.conf in earlier FreeBSD Xreleases, and this name is is pretty close to boot.config (see above). XI wonder how many people this has confused?). If there are no commands Xthen the /boot/loader will try to load kernel and then kernel.old Xby default. Note that kernel.gz and kernel.old.gz will also be tried. X XThe /boot/loader.rc file on the floppy disk contains the following lines: X X load /kernel X X load -t userconfig_script /kernel.config X X boot -P X XIf you are interested in this stuff, see /usr/src/boot/common/help.common Xfor a complete list of commands understood by the loader. X XThe load /kernel causes the loader to look for /kernel and /kernel.gz, Xwhich it will unzip and loader into memory. X XThe load -t userconfig_script /kernel.config will cause the loader Xto pass to the kernel's a 'userconfig_script' option with the value X"/kernel.config". The 'userconfig' module in the kernel (see X/usr/src/sys/i386/i386/userconfig.c for the nasty details) will Xopen and read this file, getting commands to set device configuration Xand other things. These commands can be: X X example X di disable dev di de0 X dr drq dev # dr 4 X ei # EISA slots ei 4 X en enable dev en ep0 X ex exit (quit) ex X f flags dev mask f de0 0xff X h help X intro intro screen X iom iomem dev addr iom ed0 0xdf0000 X ios iosize dev size iosize ed0 0x1000 X ir irq dev # irq ed0 5 X l ls, list l X pn pnp (scan) pnp X po port dev addr port ed0 0x300 X res reset CPU res X q quit q X v visual mode v X XThese commands are useful if you have a stock kernel and need to Xuse it on systems with a differnt set of hardware. The need for Xport (io) address and interrupt modification is used only with ISA Xand not with PCI bus cards. X XThe boot -P command line will boot it with the -P (use serial Xconsole if no keyboard) option. (see man boot for details of the Xflags). X XFinally, after all this work, the kernel is uncompressed and Xloaded into memory, and kernel execution is started. The kernel Xdoes its initialization, and then the userconfig kernel module is Xinitialized. The 'userconfig_script' setting will cause it to it Xreads the /kernel.config file, and then, since we have generated Xour kernel with the INTRO_USERCONFIG option, the kernel will go Xinto VISUAL userconfig operation. X XTo stop the loader from going into /kernel.config Xuser interactive mode automatically, you need to modify the XPICOBSD configuration file. Comment out the following line: X X options INTRO_USERCONFIG #imply -c and parse X Xand regenerate the kernel. X XHere are the commands used to set up all of this: X X # we make a compressed loader mkdir /mnt/boot cp /boot/loader . X kzip -v loader mv loader.kz /mnt/boot/loader rm -f loader loader.o X X # set up the /boot.config file to cause boot2 to load /boot/loader X echo "/boot/loader" >/mnt/boot.config X X # set up the /boot/loader.rc to cause the /boot/loader to X # load in the kernel and set options X X cat >/mnt/boot/loader.rc <build << 'END-of-build' X#!/bin/sh - X X# usage: build [what] X# what can be 'dial', 'net', 'isp', 'router', user X# X X# X# $Id: build,v 1.12 1999/01/19 23:02:05 abial Exp $ X# X Xwhile [ -n "$1" ] ; do X case "$1" in X -v ) verbose=-x; X set -x X ;; X * ) break;; X esac Xdone X X# You can set the SRC variable which points to your source tree. It's X# /usr/src by default (most people shouldn't change it). XSRC=/usr/src X X# Default MFS sizes for different types of the floppy. Again, most people X# shouldn't change them unless they know what they are doing. X XDIAL_DFLT_SIZE=1600 XROUTER_DFLT_SIZE=820 XNET_DFLT_SIZE=1700 XISP_DFLT_SIZE=1700 XDFLT_SIZE=1700 X X# DEVFS is currently broken. Always set this. X# XNO_DEVFS=yes X X# Path to srcdirs of special program for init(8) (standard if empty) XINIT= X X# --------- YOU SHOULD NOT NEED TO CHANGE ANYTHING BELOW ----------- X# The "build" script will ask you for parameters. Just run it... :-) X# --------- YOU SHOULD NOT NEED TO CHANGE ANYTHING BELOW ----------- X X X# Build kernel with previously set parameters. X X X# Main build procedure. It calls other scripts (stage1-3 and populate) Xmain() { X Xsuffix="-$TYPE" Xexport suffix Xif [ ! -d ../${TYPE} ] ; then X echo "You need `pwd`/../${TYPE} directory "; false; fi; Xif [ ! -f ../${TYPE}/conf/PICOBSD ] ; then X echo "You need `pwd`/../${TYPE}/conf/PICOBSD file"; false; fi; X Xclear Xecho "-> Building with following parameters:" Xecho -n " Type: ${TYPE}" Xif [ "X${INIT}" != "X" ] Xthen X echo " (using ${INIT} as init(8))" Xelse X echo "" Xfi Xecho " MFS size: ${SIZE} kB" Xecho " Language: ${LANGUAGE}" Xecho "" Xecho "-> We'll use the sources living in ${SRC}" Xecho "" Xecho "-> I hope you have checked the ../${TYPE}/conf/PICOBSD config file..." Xecho "" Xecho "" X# sleep 2 X X Xexport SIZE LANGUAGE TYPE SRC NO_DEVFS INIT X Xfor i in build_kernel stage1 populate stage2 stage3 Xdo X echo "====================== ${i} started =====================" X sh $verbose ./${i} X if [ "X$?" != "X0" ] X then X echo "" X echo "-> ERROR in \"${i}\" script. Aborting the build process." X echo -n "-> Cleaning temporary files... " X umount -f /mnt X vnconfig -u /dev/rvn0 X ./clean ${TYPE} X echo "Done." X exit 10 X else X echo "==================== ${i} completed =====================" X fi Xdone X} X X# Ask for, and set the custom config directory X Xset_custom() { X clear X echo " Custom directory setup" X echo "" X echo "Please enter the full path to the directory containing your" X echo "custom setup." X echo "This directory tree must be laid out exactly like the standard" X echo "ones. (E.g. you can type in /home/abial/work/custom, which" X echo "should contain conf/, crunch1/, floppy.tree/, lang/, mfs.tree/)." X echo "" X read -p "Enter the custom directory: " CUST_DIR X if [ "X${CUST_DIR}" = "X" ] X then X echo "-> Error. Custom directory cannot be null!" X exit 1 X fi X} X X# Set the LANGUAGE variable X Xset_lang() { X clear X echo " Language setup" X echo "" X echo "Language can be either 'en' (English - default) or 'pl' (Polish)" X echo "" X read -p "Enter the LANGUAGE (en, pl): " LANGUAGE X if [ "X${LANGUAGE}" = "X" ] X then X LANGUAGE=en X fi X} X X# Set the INIT variable X Xset_init() { X clear X echo " Choose your init(8) program" X echo "" X echo "You can choose either standard init(8) (which requires getty), or" X echo "you can choose 'oinit' from TinyWare collection." X echo "" X read -p "Enter the INIT (init, oinit): " INIT X if [ "X${INIT}" = "Xinit" ] X then X unset INIT X fi X} X X# Set the default MFS size depending on the type of setup Xset_dflt_size() { X if [ -z "$SIZE" ] ; then X case $TYPE in X dial ) SIZE=$DIAL_DFLT_SIZE;; X net ) SIZE=$NET_DFLT_SIZE;; X router ) SIZE=$ROUTER_DFLT_SIZE;; X isp ) SIZE=$ISP_DFLT_SIZE;; X * ) SIZE=$DFLT_SIZE;; X esac X fi; X echo "default MFS size for \"${TYPE}\" type floppy is ${SIZE} K" X} X X# Set the default INIT size depending on the type of setup X Xset_dflt_init() { X if [ -z "$INIT" ] ; then X case $TYPE in X router ) INIT=oinit;; X esac X fi; X echo "default INIT for \"${TYPE}\" is '${INIT}'" X} X X# Set MFS size interactively X Xset_size() { X clear X echo " Memory Filesystem (MFS) Size setup" X echo "" X echo " Size can be anything decent (usually 1700 or 2500) in kB." X echo " NOTE1: you can also use other numbers (e.g. 1500, 1456, 1789 ...)" X echo " even much bigger (like 4567), but keep in mind that this memory is" X echo " totally lost to other programs. Usually you want to keep this as small as" X echo " possible." X echo "" X echo " NOTE2: for pre-canned setups there are specific requirements:" X echo " dial - requires at least SIZE=$DIAL_DFLT_SIZE" X echo " router - requires at least SIZE=$ROUTER_DFLT_SIZE (500kB less without SNMP)" X echo " net - requires at least SIZE=$NET_DFLT_SIZE (500kB less without SNMP)" X echo " isp - requires at least SIZE=$ISP_DFLT_SIZE (500kB less without SNMP)" X echo "" X echo " The last two configurations are not likely to run reliably on machines" X echo " with less than 10MB of RAM, while the 'dial' is tested and proved to run" X echo " as many as ~30 processes on 10 consoles with only 8MB RAM. YMMV." X echo "" X read -p "Enter the SIZE in kB: " SIZE X if [ "X${SIZE}" = "X" ] X then X set_dflt_size X fi X} X X# Set type of floppy interactively X Xset_type() { X clear X echo " Setup the type of configuration" X echo "" X X echo " Type can be either 'dial', 'router', 'net' or 'isp'. There are four" X echo " sets of configuration files in subdirs ../dial, ../router, ../net" X echo " and ../isp respectively - the contents of the floppy is constructed" X echo " basing on the Makefiles and scripts in them." X echo "" X echo " You can also type in 'custom', and you'll be asked to enter the" X echo " full path to directory tree, where you stored your custom" X echo " configuration, laid out exactly like the standard ones. (E.g." X echo " you can type in /home/abial/work/custom, which should contain" X echo " conf/, crunch1/, floppy.tree/, lang/, mfs.tree/)." X echo "" X echo " If you define TYPE=dial, you'll end up having a floppy which is" X echo " suitable for dialup access and not much else. If you define TYPE=net," X echo " you'll have a small router-fixit-like floppy, which lacks most" X echo " interactive tools. TYPE=isp gives you a dialin server floppy." X echo "" X read -p "Enter the TYPE of the floppy (dial, net, router, isp): " TYPE X if [ "X${TYPE}" = "X" ] X then X TYPE=dial X fi X case $TYPE in X custom ) X set_custom X (ln -sf ${CUST_DIR} ../custom) X ;; X esac X set_dflt_size X set_dflt_init X} X Xput_title() { X clear X echo " Building the PicoBSD v. 0.4 floppy" X echo "============================================================================" X echo "" X} X X X#------------------------------------------------------------------- X# Main entry of the script X X# If $1="package", it creates a neat set of floppies X Xif [ X"$1" = X"package" ] Xthen X touch build.status X echo "##############################################" >>build.status X echo "## `date` ">>build.status X echo "##############################################" >>build.status X ./clean dial X for y in en pl X do X for z in dial router net isp X do X TYPE=${z} X LANGUAGE=${y} X INIT= X SIZE= X set_dflt_size X set_dflt_init X echo "---------------------------------------------">>build.status X echo "Building TYPE=${z}, LANGUAGE=${y}, INIT=${INIT}, SIZE=${SIZE}" >>build.status X export TYPE SIZE LANGUAGE SRC NO_DEVFS INIT X main X if [ "X$?" != "X0" ] X then X echo " ** FAILED! **">>build.status X else X echo " (ok)">>build.status X fi X mv picobsd.bin pb_${y}${suffix}.bin X echo "Calling ./clean for ${TYPE}, ${LANGUAGE}, ${SIZE}">>build.status X ./clean ${TYPE} X done X done X exit 0 Xfi X X# Set build parameters interactively X XTYPE=$1 Xif [ -z "$TYPE" ] ; then X TYPE=dial Xfi; XLANGUAGE=en Xset_dflt_size Xset_dflt_init Xif [ "$1X" = "X" ] ; then Xwhile [ "X${ans}" != "Xn" ] Xdo X put_title X echo "Current build parameters are as follows:" X echo "" X echo " 1. Type: ${TYPE}" X if [ "X${INIT}" != "X" ] X then X echo " a. (using ${INIT} as init(8))" X else X echo " a. (using stock init as init(8))" X fi X echo "" X echo " 2. MFS size: ${SIZE} kB" X echo " 3. Language: ${LANGUAGE}" X echo "" X echo "Which parameter would you like to change?" X read -p "(1, a, 2, 3; n -no change, build it ; q -quit): " ans X case ${ans} in X 1) set_type X clear X ;; X a) set_init X clear X ;; X 2) set_size X clear X ;; X 3) set_lang X clear X ;; X q) echo "" X echo "Hey! Don't give up so quickly. Quitting for now..." X echo "" X exit 0 X ;; X n) ;; X *) echo "Unknown option \"${ans}\". Try again." X sleep 2 X clear X ;; X esac Xdone Xfi X# Export the parameters Xexport LANGUAGE SIZE TYPE SRC NO_DEVFS INIT X# Call the build procedure Xmain X# Install if it's ok. Xecho "" Xif [ "X$?" = "X0" ] Xthen X echo "The build process was completed successfuly." X echo "" X echo "Now we are going to install the image on the floppy." X ./install Xfi Xexit 0 END-of-build echo x - build_kernel sed 's/^X//' >build_kernel << 'END-of-build_kernel' X#!/bin/sh - X# build a kernel X Xset -e Xecho "" Xecho "-> Checking if we have to build the PICOBSD kernel..." X(cd ../${TYPE}/conf; make) Xecho "" END-of-build_kernel echo x - clean sed 's/^X//' >clean << 'END-of-clean' X#! /bin/sh - X X# X# $Id: clean,v 1.7.2.1 1999/02/05 12:15:00 abial Exp $ X# Xset -e X Xif [ $# -lt 1 ] Xthen X echo "What to clean? Possible targets are 'dial', 'net', 'isp', 'router' or 'all'" X exit 1 Xfi X Xif [ "$1" = "all" ] Xthen X list="dial net isp router" X if [ -f picobsd.bin ] X then X mv -f picobsd.bin picobsd.bin.old X fi Xelse X list=$1 X if [ -f picobsd.bin ] X then X mv -f picobsd.bin picobsd.bin.$1 X fi Xfi X Xrm -f kernel kernel.kz fs.PICOBSD *.o *core *.db Xcd .. Xrm -rf help/tmp_hlp Xecho "===================== $0 tools started ====================" Xfor i in `ls -d tinyware/[a-z]*` tools/write_mfs_in_kernel Xdo X (cd ${i}; \ X if [ -f Makefile ]; \ X then \ X make clean && make cleandepend;\ X fi) Xdone Xfor j in $list Xdo X echo "===================== $0 $j started ======================" X (cd ${j}/crunch1; \ X if [ -f Makefile ]; \ X then \ X make clean ; \ X fi) X echo "=============== $0 $j completed successfuly ==============" Xdone END-of-clean echo x - install sed 's/^X//' >install << 'END-of-install' X#!/bin/sh X X# X# $Id: install,v 1.2 1998/09/29 11:58:54 abial Exp $ X# XFILENAME=picobsd.bin X Xset -e X Xecho "Please insert a blank floppy in /dev/fd0." Xecho "WARNING: the contents of the floppy will be permanently erased!" Xecho "Your options:" Xecho " * ^C to abort," Xecho " * Enter to install \"${FILENAME}\"," Xecho " * name of other file to install." Xecho "" Xread -p "Your choice: " junk Xif [ "X${junk}" != "X" ] Xthen X FILENAME=${junk} Xfi Xecho "Writing ${FILENAME}..." Xdd if=${FILENAME} of=/dev/rfd0 Xecho "Done." END-of-install echo x - modify sed 's/^X//' >modify << 'END-of-modify' X#!/bin/sh X X# Mount the picobsd.bin image on /mnt X# so you can modify the files X# X Xumount /mnt 2> /dev/null || true Xumount /dev/vn0 2> /dev/null || true Xvnconfig -u /dev/rvn0 2> /dev/null || true Xvnconfig -c /dev/rvn0 picobsd.bin 2>/dev/null Xmount /dev/vn0c /mnt END-of-modify echo x - populate sed 's/^X//' >populate << 'END-of-populate' X#!/bin/sh -x X# X# $Id: populate,v 1.8.2.2 1999/02/15 00:29:51 abial Exp $ X# X Xset -e X. ../Version X Xpwd=`pwd` X Xecho "-> Populating MFS tree..." Xcd ../${TYPE}/mfs.tree Xmake Xif [ X"${NO_DEVFS}" != X"" ] Xthen X make devnodes Xfi X X# we put in the /etc/rc script X# if there is a ../lang.mfs.rc.${LANGUAGE} -> /etc/rc X# if there is a ../lang.mfs.oinit.rc.${LANGUAGE} -> /etc/oinit.rc X Xif [ -f ../lang/mfs.rc.${LANGUAGE} ] ; then X cat ../lang/mfs.rc.${LANGUAGE}| \ X sed -e "s/@VER@/${VER}/g" > \ X /mnt/etc/rc Xfi X Xif [ -f ../lang/mfs.oinit.rc.${LANGUAGE} ] ; then X cat ../lang/mfs.oinit.rc.${LANGUAGE}| \ X sed -e "s/@VER@/${VER}/g" > \ X /mnt/etc/oinit.rc Xfi X Xif [ ! -f /mnt/etc/oinit.rc -a -f /mnt/etc/rc ] ; then X ln -s rc /mnt/etc/oinit.rc Xfi X Xif [ -f login.conf ] ; then X cp login.conf /mnt/etc/login.conf Xfi; X Xif [ ../lang/README.${LANGUAGE} ] ; then X cat ../lang/README.${LANGUAGE} | \ X sed -e "s/@VER@/${VER}/g" > \ X /mnt/README Xfi; Xif [ -f ../lang/update.${LANGUAGE} ] ; then X cp ../lang/update.${LANGUAGE} /mnt/stand/update Xfi Xif [ "${TYPE}" = "dial" ] Xthen X cp ../lang/reboot.${LANGUAGE} /mnt/stand/reboot X ln -f /mnt/stand/reboot /mnt/stand/shutdown X cp ../lang/login.${LANGUAGE} /mnt/stand/login X cp ../lang/dialup.${LANGUAGE} /mnt/stand/dialup X (cd ../../help;\ X rm -rf tmp_hlp;\ X mkdir tmp_hlp;\ X for i in `ls *.hlp.${LANGUAGE}`;\ X do \ X cp $i tmp_hlp/`basename $i .hlp.${LANGUAGE}`;\ X done;\ X cd tmp_hlp;\ X ar -cru help.a *;\ X cp help.a /mnt/help.a) Xfi X Xecho "-> Making and installing crunch1..." Xcd ../crunch1 Xmake "SRC=${SRC}" && make install 2>&1 >/dev/null Xif [ "X$?" != "X0" ] Xthen X echo "-> ERROR while building ../${TYPE}/crunch1..." X echo "-> Aborting $0" X exit 10 Xfi X Xcd ${pwd} X X(echo "-> Fixing permissions"; cd /mnt; chown -R root *) END-of-populate echo x - stage1 sed 's/^X//' >stage1 << 'END-of-stage1' X#!/bin/sh -x X X# X# $Id: stage1,v 1.7 1999/01/19 23:02:05 abial Exp $ X# X Xset -e Xecho ${SRC}/sys/compile/PICOBSD${suffix}.${SIZE}/kernel X Xif [ ! -f ${SRC}/sys/compile/PICOBSD${suffix}.${SIZE}/kernel ]; then X echo "-> ERROR: you must build PICOBSD${suffix}.${SIZE} first" X exit 1 Xfi X Xecho "-> Preparing kernel..." Xcp -p ${SRC}/sys/compile/PICOBSD${suffix}.${SIZE}/kernel kernel X#if [ "${TYPE}" != "dial" ] X#then X# echo "-> Preparing kvm database..." X# mv /var/db/kvm_kernel.db /var/db/old.db X# kvm_mkdb kernel X# cp /var/db/kvm_kernel.db kvm_kernel.db X# mv /var/db/old.db /var/db/kvm_kernel.db X#fi X Xecho "-> Preparing MFS filesystem..." Xumount /dev/vn0 2> /dev/null || true Xumount /mnt 2> /dev/null || true Xvnconfig -u /dev/rvn0 2> /dev/null || true X Xdd of=fs.PICOBSD if=/dev/zero count=${SIZE} bs=1k 2> /dev/null X X### --- removed papowell@astart.com X### This is not needed with 3.1 disklabel utility X#awk 'BEGIN {printf "%c%c", 85, 170}' | \ X# dd of=fs.PICOBSD obs=1 seek=510 conv=notrunc 2> /dev/null X X#vnconfig -c /dev/rvn0 fs.PICOBSD 2>/dev/null Xvnconfig -s labels -c /dev/rvn0 fs.PICOBSD 2>/dev/null X Xif [ "X$?" != "X0" ] Xthen X echo "-> Error while doing vnconfig of fs.PICOBSD on /dev/rvn0..." X echo " Most probably your running kernel doesn't have the vn(4) device." X echo "-> Aborting $0" X exit 10 Xfi X X### --- removed papowell@astart.com X### This is not needed with 3.1 disklabel utility X#dd if=/usr/mdec/boot1 of=fs.PICOBSD conv=notrunc 2> /dev/null X### *** dd writes boot record? X#dd if=/boot/boot1 of=fs.PICOBSD conv=notrunc 2> /dev/null X X### --- removed papowell@astart.com X### from --- to --- and replaced by 'disklabel vn0 auto' Xdisklabel -rw vn0 auto X X##--- This command does weird things on 2.2.x systems. In such case use normal X## disktype here instead X#if [ "${TYPE}" != "router" ] X#then X# disklabel -rw vn0 auto X#else X# if [ ${SIZE} -lt 1024 ] X# then X# disklabel -rw /dev/rvn0 fd${SIZE} X# else X# disklabel -rw vn0 auto X# fi X#fi X### --- X Xif [ "X$?" != "X0" ] Xthen X echo "-> Error while labeling fs.PICOBSD (vn0)..." X echo "-> Aborting $0" X exit 10 Xfi X X# Default setting for other (custom) setups. XINODES=4096 X# You can save some space on MFS if you don't want so many inodes... Xif [ -z "$INODES" ] ; then X case $TYPE in X * ) INODES=4096;; X router ) INODES=3072;; X esac Xfi X Xnewfs -i $INODES -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null Xmount /dev/vn0c /mnt Xif [ "X$?" != "X0" ] Xthen X echo "-> Error while mounting fs.PICOBSD (/dev/vn0c) on /mnt..." X echo "-> Aborting $0" X exit 10 Xfi END-of-stage1 echo x - stage2 sed 's/^X//' >stage2 << 'END-of-stage2' X#!/bin/sh -x X X# X# $Id: stage2,v 1.3 1999/01/14 23:14:46 abial Exp $ X# Xset -e X Xif [ ! -f kernel ]; then X echo "-> ERROR: you must build PICOBSD${suffix}.${SIZE} kernel first" X exit 1 Xfi X Xecho "-> Preparing kernel with MFS filesystem inside..." X X### display how much you have used Xdf -ik /mnt Xumount /mnt 2>&1 >/dev/null Xfsck -p /dev/rvn0c Xvnconfig -u /dev/rvn0 2>&1 >/dev/null X X# generate the write_mfs_in_kernel tool Xif [ ! -f ../tools/write_mfs_in_kernel/wmik ]; then X (cd ../tools/write_mfs_in_kernel; make) Xfi X X../tools/write_mfs_in_kernel/wmik kernel fs.PICOBSD Xstrip kernel Xstrip --remove-section=.note --remove-section=.comment kernel X X### compress the kernel Xgzip -9 -n -f kernel Xrm fs.PICOBSD END-of-stage2 echo x - stage3 sed 's/^X//' >stage3 << 'END-of-stage3' X#!/bin/sh -x X X# X# $Id: stage3,v 1.4 1999/01/14 23:14:46 abial Exp $ X# Xset -e X X. ../Version X Xif [ ! -f kernel.gz ]; then X echo "-> ERROR: you must build kernel.gz first" X exit 1 Xfi X Xecho "-> Preparing 1.44 floppy filesystem..." X### comments added papowell@astart.com Wed Apr 28 16:12:04 PDT 1999 X X### we make sure that the rvn0 system is available Xumount /dev/vn0 2> /dev/null || true Xumount /mnt 2> /dev/null || true Xvnconfig -u /dev/rvn0 2> /dev/null || true X X### now we make the file for the vnode file system Xdd of=picobsd.bin if=/dev/zero count=1440 bs=1k 2> /dev/null X X### --- removed papowell@astart.com X### this does not seem to be needed when using 3.1 disklabel utility X#awk 'BEGIN {printf "%c%c", 85, 170}' | \ X# dd of=picobsd.bin obs=1 seek=510 conv=notrunc 2> /dev/null X# vnconfig -s labels -c /dev/rvn0 picobsd.bin 2>/dev/null X X# we now configure the picobsd.bin file for use as the vnode file system Xvnconfig -c /dev/rvn0 picobsd.bin 2>/dev/null X X### -- removed papowell@astart.com X### the disklabel 'fd1440' should take care of this X### Note 1: FreeBSD 3.1-RELEASE does not use mdec X#dd if=/usr/mdec/boot1 of=picobsd.bin conv=notrunc 2> /dev/null X### the disklabel 'fd1440' should take care of this X#dd if=/boot/boot1 of=picobsd.bin conv=notrunc 2> /dev/null X X### -- updated papowell X### the disklabel with fd1440 will take care of the boot sectors X### and boot information X#disklabel -Brw -b /usr/mdec/fdboot -s /usr/mdec/bootfd /dev/rvn0 fd1440 2>&1 >/dev/null X X# we label the vnode file system as a floppy disk and install boot X# blocks Xdisklabel -Brw /dev/rvn0 fd1440 2>&1 >/dev/null X X### -- updated papowell@astart.co X### you may find that 32768 inodes is a little much, especially if you X### need every little bit of space X### newfs -i 32768 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null X X# now we do a newfs and mount the file as /mnt Xnewfs -i 4096 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null Xmount /dev/vn0c /mnt X X### sigh... this is ugly, but it works... Xpwd=`pwd` X X### --- added comments papowell@astart.com X### Note 1: these files are generated from the X### language dependent part of the tree. If the file X### is not there, then you get a nasty error and die X### We put a check for the file. Note that this allows X### us to put the rc.conf and rc.network files into a list X### Note 2: really, we ought to simply do: X### for i in ../lang/*.${LANGUAGE} X### and not worry about the language specific files X### Xcd ../${TYPE}/floppy.tree Xecho "-> Copying language dependent files..." Xfor i in hosts motd rc resolv.conf rc.conf Xdo X if [ -f ../lang/${i}.${LANGUAGE} ] ; then X cat ../lang/${i}.${LANGUAGE} | \ X sed -e "s/@VER@/${VER}/g" > \ X etc/${i} X fi; Xdone X X### --- removed, see above comments about tests X#if [ "${TYPE}" != "router" ] X#then X# cat ../lang/rc.conf.${LANGUAGE} | \ X# sed -e "s/@VER@/${VER}/g" > \ X# etc/rc.conf X# cat ../lang/rc.network.${LANGUAGE}| \ X# sed -e "s/@VER@/${VER}/g" > \ X# etc/rc.network X#fi X Xecho "-> Populating floppy filesystem..." X### -- this is tricky - you want to put in the boot.help file Xcat ../lang/boot.help.${LANGUAGE} | \ X sed -e "s/@VER@/${VER}/g" > \ X /mnt/boot.help X X### now you copy all the files in ${TYPE}/floppy.tree to /mnt Xcp -pr . /mnt Xrm -rf /mnt/CVS /mnt/etc/CVS /mnt/etc/ppp/CVS X X### this provides a prebuilt password file - but it takes space Xif [ "${TYPE}" = "dial" ] Xthen X pwd_mkdb -d etc/ etc/master.passwd X mv etc/spwd.db /mnt/etc/ X rm etc/pwd.db Xfi X X### we return to our original directory, and copy the kernel to the floppy image X### kernel Xcd ${pwd} Xcp kernel.gz /mnt/kernel.gz Xrm kernel.gz X X### now we add the boot loader - boot1 and boot2 were done by disklabel X### X### Here is the boot sequence: X### (boot0 on floppy sector 0/0/1) loaded into memory and executed X### boot1 finds UNIX partition, brings in boot2, starts execution of boot2 X### Boot1 usually does things using BIOS facilities X### Boot2 has quite a bit of the UNIX ufs file system, and can understand UFS X### file systems. X### boot2 will open /boot.config, read THE SINGLE LINE IN THE FILE, X### and interpret it as the name of a kernel and some options to pass X### to the kernel. X### The PICOBSD setup initializes boot.config with X### /boot/loader X### which tells boot2 to use the /boot/loader code as a kernel. X### X### What is this all about? The answer is simple: we want to be able to X### configure the devices by using the 3rd Stage Loader. But this X### loader is a little big, so we use the kzip (kernel zip) facility X### to compress it and attach a bit of code to decompress and then run X### the compressed code. X### X### The /boot/loader will now uncompress itself and will then read the X### (documented in the source code) file X### /boot/loader.rc X### This contains a list of commands that the loader understands. X### (Aside: /boot/loader.rc used to be /boot/boot.conf in earlier FreeBSD X### releases, and this name is is pretty close to boot.config (see above). X### I wonder how many people this has confused?) X### X### The /boot/loader.rc file contains the following commands: X### load /kernel X### load -t userconfig_script /kernel.config X### boot -P X### (see /usr/src/boot/common/help.common for list of commands) X### X### load /kernel loads /kernel into memory, and the boot -P X### line will boot it with the -P (use serial console if no keyboard) option. X### (see man boot for details of the flags) X### X### The load -t userconfig_script /kernel.config X### sets the kernel's 'userconfig_script' option value to X### "/kernel.config". The 'userconfig' module in the kernel X### (see /usr/src/sys/i386/i386/userconfig.c for the nasty details) X### will open and read this file, getting commands to set device X### configuration and other things. X### These commands can be: X### example X### di disable dev di de0 X### dr drq dev # dr 4 X### ei # EISA slots ei 4 X### en enable dev en ep0 X### ex exit (quit) ex X### f flags dev mask f de0 0xff X### h help X### intro intro screen X### iom iomem dev addr iom ed0 0xdf0000 X### ios iosize dev size iosize ed0 0x1000 X### ir irq dev # irq ed0 5 X### l ls, list l X### pn pnp ... pnp X### po port dev addr port ed0 0x300 X### res reset CPU res X### q quit q X### v visual mode v X### X### I strongly suspect that this has been included strictly as a Tour de Force X### example of how to make the loading as flexible as possible, etc, without X### needing to compile a special version of the boot code. X### X### Finally, after all this work, the kernel is loaded into memory, X### and kernel execution is started. Of course we have compressed the X### kernel, so it will promptly uncompress itself and start execution. X### X### The userconfig module is started, it reads the /kernel.config file, X### and then, since we have generated our kernel with the INTRO_USERCONFIG X### option, the kernel will go into VISUAL userconfig X### operation. X### X### To stop the loader from going into /kernel.config X### user interactive mode automatically, you need to modify the X### PICOBSD configuration file. Remove the X### options INTRO_USERCONFIG #imply -c and parse info area X### And regenerate the kernel. X### X### Suggested Alternatives X### X### Skipping the /boot/loader X### To do this, set /boot.config to contain only '-P' X### By default, you will get the kernel loaded. You should also X### compile the kernel without the INTRO_USERCONFIG option. X### X X# we make a compressed loader Xmkdir /mnt/boot Xcp /boot/loader . Xkzip -v loader Xmv loader.kz /mnt/boot/loader Xrm -f loader loader.o X X# set up the /boot.config file to cause boot2 to load /boot/loader Xecho "/boot/loader" >/mnt/boot.config X X# set up the /boot/loader.rc to cause the /boot/loader to X# load in the kernel and set options Xcat >/mnt/boot/loader.rc < Fixing permissions"; cd /mnt; chown -R root * ) X X### little bit of information for users Xdf -ik /mnt Xls -Rl /mnt X Xumount /mnt X# and we are finished Xvnconfig -u /dev/rvn0 END-of-stage3 exit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 28 22:49:19 1999 Delivered-To: freebsd-small@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 7DD99157BB for ; Wed, 28 Apr 1999 22:49:16 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id WAA17889; Wed, 28 Apr 1999 22:48:49 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199904290548.WAA17889@freeway.dcfinc.com> Subject: Re: archive site for freebsd-mail In-Reply-To: <3727D0E7.28337455@unlimited.net> from John Oram at "Apr 28, 99 08:24:23 pm" To: norami@unlimited.net Date: Wed, 28 Apr 1999 22:48:49 -0700 (MST) Cc: papowell@astart4.astart.com, freebsd-small@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > But perhaps this might help the next person. If there is any interest, > > I would be pleased/willing to post my notes on > > > > Generating PICOBSD Floppies Using FreeBSD 3.1-RELEASE If the picoBSD gang don't incorporate your documentation into their own tree, then please post it here. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 29 20: 6:43 1999 Delivered-To: freebsd-small@freebsd.org Received: from astart4.astart.com (astart4.astart.com [206.71.174.196]) by hub.freebsd.org (Postfix) with ESMTP id 7FBA114D66 for ; Thu, 29 Apr 1999 20:06:41 -0700 (PDT) (envelope-from papowell@astart4.astart.com) Received: (from papowell@localhost) by astart4.astart.com (8.8.8/8.8.8) id UAA11181; Thu, 29 Apr 1999 20:05:32 -0700 (PDT) Date: Thu, 29 Apr 1999 20:05:32 -0700 (PDT) From: papowell@astart4.astart.com Message-Id: <199904300305.UAA11181@astart4.astart.com> To: jkh@zippy.cdrom.com Subject: picobsd and /dev/MAKEDEV problems Cc: freebsd-small@freebsd.org Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been adding some functionality to the various build scripts, when I discovered that the /dev/MAKEDEV script was not generating devices, but picobsd/build was not reporting an error. I discovered the following code (single example here) in /dev/MAKEDEV case $unit in [0-9]|[0-9][0-9]|[0-4][0-9][0-9]|50[0-9]|51[0-1]) for slicepartname in s0h s1 s2 s3 s4 do **************>>>>>>> sh MAKEDEV $name$unit$slicepartname **************>>>>>>> done ;; *) echo bad unit for disk in: $i ;; esac Clearly /dev/MAKEDEV wants to be run in the /dev directory. However, the build scripts assume that they can do: sh /dev/MAKEDEV The sh MAKEDEV failes as it does not find a MAKEDEV file in the current directory. Here are patches to the picobsd configuration files that fix this problem. *** picobsd/dial/mfs.tree/Makefile Thu Apr 29 19:56:47 1999 --- picobsd/dial/mfs.tree/Makefile.orig Thu Apr 29 19:55:18 1999 *************** *** 62,71 **** # We don't do it under 'all' because it's needed only on non-DEVFS systems devnodes: tree (cd ${DESTDIR}/dev; \ ! ln -s /dev/MAKEDEV MAKEDEV; \ ! ./MAKEDEV std sysmouse tun2 cuaa0 cuaa1 cuaa2 vty10 fd0 pty0; \ ! ./MAKEDEV psm0; \ ! ./MAKEDEV wd0 wd1 acd0; \ ! rm MAKEDEV; ) clean: --- 62,69 ---- # We don't do it under 'all' because it's needed only on non-DEVFS systems devnodes: tree (cd ${DESTDIR}/dev; \ ! /dev/MAKEDEV std sysmouse tun2 cuaa0 cuaa1 cuaa2 vty10 fd0 pty0; \ ! /dev/MAKEDEV psm0; \ ! /dev/MAKEDEV wd0 wd1 acd0 ) clean: *** picobsd/isp/mfs.tree/Makefile Thu Apr 29 19:58:22 1999 --- picobsd/isp/mfs.tree/Makefile.orig Thu Apr 29 19:55:18 1999 *************** *** 33,40 **** # We don't do it under 'all' because it's needed only on non-DEVFS systems devnodes: tree (cd ${DESTDIR}/dev; \ ! ln -s /dev/MAKEDEV; \ ! ./MAKEDEV std wd0 wd1 acd0 tun2 vty10 fd0 pty0; \ ! ./MAKEDEV cuaa0 cuaa1 cuaa2 cuaa3 cuaa4; \ ! ./MAKEDEV cuaa5 cuaa6 cuaa7 cuaa8 cuaa9; \ ! rm MAKEDEV; ) --- 33,38 ---- # We don't do it under 'all' because it's needed only on non-DEVFS systems devnodes: tree (cd ${DESTDIR}/dev; \ ! /dev/MAKEDEV std wd0 wd1 acd0 tun2 vty10 fd0 pty0; \ ! /dev/MAKEDEV cuaa0 cuaa1 cuaa2 cuaa3 cuaa4; \ ! /dev/MAKEDEV cuaa5 cuaa6 cuaa7 cuaa8 cuaa9) *** picobsd/net/mfs.tree/Makefile Thu Apr 29 19:58:47 1999 --- picobsd/net/mfs.tree/Makefile.orig Thu Apr 29 19:55:18 1999 *************** *** 33,38 **** # We don't do it under 'all' because it's needed only on non-DEVFS systems devnodes: tree (cd ${DESTDIR}/dev; \ ! ln -s /dev/MAKEDEV; \ ! ./MAKEDEV std tun2 cuaa0 cuaa1 cuaa2 vty10 fd0 pty0 wd0 wd1 acd0 ; \ ! rm MAKEDEV; ) --- 33,36 ---- # We don't do it under 'all' because it's needed only on non-DEVFS systems devnodes: tree (cd ${DESTDIR}/dev; \ ! /dev/MAKEDEV std tun2 cuaa0 cuaa1 cuaa2 vty10 fd0 pty0 wd0 wd1 acd0) *** picobsd/router/mfs.tree/Makefile Thu Apr 29 20:00:17 1999 --- picobsd/router/mfs.tree/Makefile.orig Thu Apr 29 19:55:18 1999 *************** *** 33,38 **** # We don't do it under 'all' because it's needed only on non-DEVFS systems devnodes: tree (cd ${DESTDIR}/dev; \ ! ln -s /dev/MAKEDEV; \ ! ./MAKEDEV std tun2 vty3 fd0 pty0 wd0 wd1 acd0 cuaa0 cuaa1 cuaa2; \ ! rm MAKEDEV; ) --- 33,36 ---- # We don't do it under 'all' because it's needed only on non-DEVFS systems devnodes: tree (cd ${DESTDIR}/dev; \ ! /dev/MAKEDEV std tun2 vty3 fd0 pty0 wd0 wd1 acd0 cuaa0 cuaa1 cuaa2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Apr 30 1: 2:31 1999 Delivered-To: freebsd-small@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1962B1584A for ; Fri, 30 Apr 1999 01:02:13 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA11634 for ; Fri, 30 Apr 1999 01:02:25 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Prev-Resent: Fri, 30 Apr 1999 01:02:25 -0700 Prev-Resent: "freebsd-small@freebsd.org " Replied: Wed, 28 Apr 1999 23:23:04 -0700 Replied: "papowell@astart4.astart.com " Received: from astart4.astart.com (papowell@astart4.astart.com [206.71.174.196]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA45776 for ; Wed, 28 Apr 1999 22:13:03 -0700 (PDT) (envelope-from papowell@astart4.astart.com) From: papowell@astart4.astart.com Received: (from papowell@localhost) by astart4.astart.com (8.8.8/8.8.8) id WAA08049; Wed, 28 Apr 1999 22:11:46 -0700 (PDT) Date: Wed, 28 Apr 1999 22:11:46 -0700 (PDT) Message-Id: <199904290511.WAA08049@astart4.astart.com> To: jkh@zippy.cdrom.com, papowell@astart4.astart.com Subject: Re: Printing, Documentation, etc Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No problem. By the way, just for your enjoyment: Revised picobsd Build Procedures and Scripts For Compliance with FreeBSD 3.1-RELEASE Patrick Powell Wed Apr 28 20:26:09 PDT 1999 1. Modifications The modifications to the picobsd build procedures was done as a result of working only with the FreeBSD 3.1-RELEASE and reflects the current use of the various utilities. These include a. VNODE support b. disklabel utility c. newfs utility In addition, the scripts have been modified to allow a user specified configuration similar to the net, isp, router, dialer and custom provided by the original Build procedures. Finally, an effort was made to extend the scripts to handle more (and less) number of files in the various crunch, mfs.tree, and floppy.tree systems. 2. Missing kzip /usr/lib/aout files on FreeBSD 3.1-RELEASE The necessary library files for the kzip utility are missing on the FreeBSD 3.1-RELEASE. Do the following steps to create and install them: cd /usr/src/sys/i386/boot/kzipboot make all install Note: kzip is present, but for completeness, you create and install using: cd /usr/src/usr.bin/kzip make all install 3. Build Script Modifications build -> build + build_script The build script was modified and the 'build_kernel' function was extracted and made a separate file. This allows the set -e to be used and greated control of error detection and reporting during the build_kernel phase. The set -e option was used in all scripts to terminate at the first error. Checks for file existence were added to prevent the copying of a non-existent file to terminate operation. 4. MFS and Floppy Image Generation The following modificiations were made in order to be compliant with the current VNODE support commands vnconfig, disklabel, and newfs. MFS Creation (stage1 script) umount /dev/vn0 2> /dev/null || true umount /mnt 2> /dev/null || true vnconfig -u /dev/rvn0 2> /dev/null || true dd of=fs.PICOBSD if=/dev/zero count=${SIZE} bs=1k 2> /dev/null vnconfig -s labels -c /dev/rvn0 fs.PICOBSD 2>/dev/null disklabel -rw vn0 auto INODES=4096 newfs -i $INODES -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null mount /dev/vn0c /mnt The dd command creates the fd.PICOBSD file, the vnconfig with the appropriate options will use it as a device, and then the disklabel command will simply label it. Note that since this is NOT a bootable device, no boot blocks need to be installed. Finally, we do a newfs to create the file system structure and then we mount it. Floppy Image file Creation (stage3 script) umount /dev/vn0 2> /dev/null || true umount /mnt 2> /dev/null || true vnconfig -u /dev/rvn0 2> /dev/null || true dd of=picobsd.bin if=/dev/zero count=1440 bs=1k 2> /dev/null vnconfig -c /dev/rvn0 picobsd.bin 2>/dev/null disklabel -Brw /dev/rvn0 fd1440 2>&1 >/dev/null newfs -i 4096 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null mount /dev/vn0c /mnt This is almost identical to the previous step, with the modified disklabel command. The -Brw option will cause boot blocks to be put onto the image, and the fd1440 disktab entry sets the geometry. The news command will create a disk with 4096 inodes - this has been reduce to 1024 in testing with no problems. Note that the number of inodes can be pretty small on the root system if you create an MFS system for general use. 4. Detailed Description of Boot Sequence The following is a detailed description of how the system boots from the boot floppy, and how this sequence relates to the commands in the stage3 file used to generate the boot disk. In the stage3 build script, we create and mount the floppy image on /mnt using the dd, vnconfig, newfs, and mount commands described above. The kernel has been created and compressed using gzip. We copy the kernel to the floppy image: cp kernel.gz /mnt/kernel.gz At this point, if we use dd to copy the floppy image to a floppy disk, we would discover that the boot loader could not handle a compressed kernel. In the past, this was handled by the kzip utility, which would compress the kernel and then prefix and append some code that would uncompress and then execute the kernel. We will use a different and rather more elaborate method for booting. Here is the boot sequence: (boot0 on floppy sector 0/0/1) loaded into memory and executed This is done by the PC BIOS. Boot1 uses the PC BIOS facilities, and is limited to reading a boot record by the various limitations of the PC BIOS facilities. boot1 finds UNIX partition, brings in boot2, starts execution of boot2 Boot1 looks at the partition table information and finds the 'active' partition and loads 'boot2' from a fixed location on the partition. Boot2 has quite a bit of the UNIX ufs file system, and can understand UFS file systems. boot2 will open /boot.config, read THE SINGLE LINE IN THE FILE, and interpret it as the name of a kernel and some options to pass to the kernel. You can interatively specify these values by pressing a key during the boot process and entering them at the prompt. The PICOBSD setup initializes boot.config with the line: /boot/loader which tells boot2 to use the /boot/loader code as a kernel. What is this all about? The answer is simple: we want to be able to configure the devices and we need a loader that is smart enough to uncompress our kernel. The boot3 loader (just called loader now) is a little big, so we use the kzip (kernel zip) facility to compress it and attach a bit of code to decompress and then run the compressed code. As I were saying, the boot2 loader copies the file /boot/loader into memory now executes it. The /boot/loader will now uncompress itself and will then read the (this is documented in the source code) file /boot/loader.rc This file contains a list of commands that the loader understands. (Aside: /boot/loader.rc used to be /boot/boot.conf in earlier FreeBSD releases, and this name is is pretty close to boot.config (see above). I wonder how many people this has confused?). If there are no commands then the /boot/loader will try to load kernel and then kernel.old by default. Note that kernel.gz and kernel.old.gz will also be tried. The /boot/loader.rc file on the floppy disk contains the following lines: load /kernel load -t userconfig_script /kernel.config boot -P If you are interested in this stuff, see /usr/src/boot/common/help.common for a complete list of commands understood by the loader. The load /kernel causes the loader to look for /kernel and /kernel.gz, which it will unzip and loader into memory. The load -t userconfig_script /kernel.config will cause the loader to pass to the kernel's a 'userconfig_script' option with the value "/kernel.config". The 'userconfig' module in the kernel (see /usr/src/sys/i386/i386/userconfig.c for the nasty details) will open and read this file, getting commands to set device configuration and other things. These commands can be: example di disable dev di de0 dr drq dev # dr 4 ei # EISA slots ei 4 en enable dev en ep0 ex exit (quit) ex f flags dev mask f de0 0xff h help intro intro screen iom iomem dev addr iom ed0 0xdf0000 ios iosize dev size iosize ed0 0x1000 ir irq dev # irq ed0 5 l ls, list l pn pnp (scan) pnp po port dev addr port ed0 0x300 res reset CPU res q quit q v visual mode v These commands are useful if you have a stock kernel and need to use it on systems with a differnt set of hardware. The need for port (io) address and interrupt modification is used only with ISA and not with PCI bus cards. The boot -P command line will boot it with the -P (use serial console if no keyboard) option. (see man boot for details of the flags). Finally, after all this work, the kernel is uncompressed and loaded into memory, and kernel execution is started. The kernel does its initialization, and then the userconfig kernel module is initialized. The 'userconfig_script' setting will cause it to it reads the /kernel.config file, and then, since we have generated our kernel with the INTRO_USERCONFIG option, the kernel will go into VISUAL userconfig operation. To stop the loader from going into /kernel.config user interactive mode automatically, you need to modify the PICOBSD configuration file. Comment out the following line: options INTRO_USERCONFIG #imply -c and parse and regenerate the kernel. Here are the commands used to set up all of this: # we make a compressed loader mkdir /mnt/boot cp /boot/loader . kzip -v loader mv loader.kz /mnt/boot/loader rm -f loader loader.o # set up the /boot.config file to cause boot2 to load /boot/loader echo "/boot/loader" >/mnt/boot.config # set up the /boot/loader.rc to cause the /boot/loader to # load in the kernel and set options cat >/mnt/boot/loader.rc <README << 'END-of-README' X Revised picobsd Build Procedures and Scripts X For Compliance with FreeBSD 3.1-RELEASE X Patrick Powell X Wed Apr 28 20:26:09 PDT 1999 X X1. Modifications X X The modifications to the picobsd build procedures was done X as a result of working only with the FreeBSD 3.1-RELEASE X and reflects the current use of the various utilities. X X These include X a. VNODE support X b. disklabel utility X c. newfs utility X X In addition, the scripts have been modified to allow a user X specified configuration similar to the net, isp, router, dialer X and custom provided by the original Build procedures. X X Finally, an effort was made to extend the scripts to handle more X (and less) number of files in the various crunch, mfs.tree, X and floppy.tree systems. X X X2. Missing kzip /usr/lib/aout files on FreeBSD 3.1-RELEASE X X The necessary library files for the kzip utility are missing on the X FreeBSD 3.1-RELEASE. Do the following steps to create and install them: X X cd /usr/src/sys/i386/boot/kzipboot X make all install X X Note: kzip is present, but for completeness, you create and install X using: X cd /usr/src/usr.bin/kzip X make all install X X3. Build Script Modifications X X build -> build + build_script X X The build script was modified and the 'build_kernel' X function was extracted and made a separate file. This allows X the set -e to be used and greated control of error detection X and reporting during the build_kernel phase. X X The set -e option was used in all scripts to terminate at the X first error. Checks for file existence were added to prevent X the copying of a non-existent file to terminate operation. X X4. MFS and Floppy Image Generation X X The following modificiations were made in order to be compliant X with the current VNODE support commands vnconfig, disklabel, X and newfs. X X MFS Creation (stage1 script) X X umount /dev/vn0 2> /dev/null || true X umount /mnt 2> /dev/null || true X vnconfig -u /dev/rvn0 2> /dev/null || true X dd of=fs.PICOBSD if=/dev/zero count=${SIZE} bs=1k 2> /dev/null X vnconfig -s labels -c /dev/rvn0 fs.PICOBSD 2>/dev/null X disklabel -rw vn0 auto X INODES=4096 X newfs -i $INODES -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null X mount /dev/vn0c /mnt X X The dd command creates the fd.PICOBSD file, the X vnconfig with the appropriate options will use it as a X device, and then the disklabel command will simply label it. X Note that since this is NOT a bootable device, no boot blocks X need to be installed. Finally, we do a newfs to create the X file system structure and then we mount it. X X Floppy Image file Creation (stage3 script) X X umount /dev/vn0 2> /dev/null || true X umount /mnt 2> /dev/null || true X vnconfig -u /dev/rvn0 2> /dev/null || true X dd of=picobsd.bin if=/dev/zero count=1440 bs=1k 2> /dev/null X vnconfig -c /dev/rvn0 picobsd.bin 2>/dev/null X disklabel -Brw /dev/rvn0 fd1440 2>&1 >/dev/null X newfs -i 4096 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null X mount /dev/vn0c /mnt X X This is almost identical to the previous step, with the X modified disklabel command. The -Brw option will cause X boot blocks to be put onto the image, and the fd1440 X disktab entry sets the geometry. The news command will X create a disk with 4096 inodes - this has been reduce to X 1024 in testing with no problems. Note that the number of X inodes can be pretty small on the root system if you create X an MFS system for general use. X X4. Detailed Description of Boot Sequence X XThe following is a detailed description of how the system boots Xfrom the boot floppy, and how this sequence relates to the commands Xin the stage3 file used to generate the boot disk. X XIn the stage3 build script, we create and mount the floppy image Xon /mnt using the dd, vnconfig, newfs, and mount commands described Xabove. X XThe kernel has been created and compressed using gzip. We copy Xthe kernel to the floppy image: X X cp kernel.gz /mnt/kernel.gz X X XAt this point, if we use dd to copy the floppy image to a floppy Xdisk, we would discover that the boot loader could not handle a Xcompressed kernel. In the past, this was handled by the kzip Xutility, which would compress the kernel and then prefix and append Xsome code that would uncompress and then execute the kernel. We Xwill use a different and rather more elaborate method for booting. X X XHere is the boot sequence: X X (boot0 on floppy sector 0/0/1) loaded into memory and executed X XThis is done by the PC BIOS. Boot1 uses the PC BIOS facilities, Xand is limited to reading a boot record by the various limitations Xof the PC BIOS facilities. X X boot1 finds UNIX partition, brings in boot2, starts execution of boot2 X XBoot1 looks at the partition table information and finds the 'active' Xpartition and loads 'boot2' from a fixed location on the partition. X X XBoot2 has quite a bit of the UNIX ufs file system, and can understand XUFS file systems. boot2 will open /boot.config, read THE SINGLE XLINE IN THE FILE, and interpret it as the name of a kernel and some Xoptions to pass to the kernel. You can interatively specify these Xvalues by pressing a key during the boot process and entering them Xat the prompt. X XThe PICOBSD setup initializes boot.config with the line: X X /boot/loader X Xwhich tells boot2 to use the /boot/loader code as a kernel. X XWhat is this all about? The answer is simple: we want to be able to Xconfigure the devices and we need a loader that is smart enough Xto uncompress our kernel. The boot3 loader (just called loader now) Xis a little big, so we use the kzip (kernel zip) facility Xto compress it and attach a bit of code to decompress and then run Xthe compressed code. X X XAs I were saying, the boot2 loader copies the file /boot/loader Xinto memory now executes it. The /boot/loader will now uncompress Xitself and will then read the (this is documented in the source Xcode) file X X /boot/loader.rc X XThis file contains a list of commands that the loader understands. X(Aside: /boot/loader.rc used to be /boot/boot.conf in earlier FreeBSD Xreleases, and this name is is pretty close to boot.config (see above). XI wonder how many people this has confused?). If there are no commands Xthen the /boot/loader will try to load kernel and then kernel.old Xby default. Note that kernel.gz and kernel.old.gz will also be tried. X XThe /boot/loader.rc file on the floppy disk contains the following lines: X X load /kernel X X load -t userconfig_script /kernel.config X X boot -P X XIf you are interested in this stuff, see /usr/src/boot/common/help.common Xfor a complete list of commands understood by the loader. X XThe load /kernel causes the loader to look for /kernel and /kernel.gz, Xwhich it will unzip and loader into memory. X XThe load -t userconfig_script /kernel.config will cause the loader Xto pass to the kernel's a 'userconfig_script' option with the value X"/kernel.config". The 'userconfig' module in the kernel (see X/usr/src/sys/i386/i386/userconfig.c for the nasty details) will Xopen and read this file, getting commands to set device configuration Xand other things. These commands can be: X X example X di disable dev di de0 X dr drq dev # dr 4 X ei # EISA slots ei 4 X en enable dev en ep0 X ex exit (quit) ex X f flags dev mask f de0 0xff X h help X intro intro screen X iom iomem dev addr iom ed0 0xdf0000 X ios iosize dev size iosize ed0 0x1000 X ir irq dev # irq ed0 5 X l ls, list l X pn pnp (scan) pnp X po port dev addr port ed0 0x300 X res reset CPU res X q quit q X v visual mode v X XThese commands are useful if you have a stock kernel and need to Xuse it on systems with a differnt set of hardware. The need for Xport (io) address and interrupt modification is used only with ISA Xand not with PCI bus cards. X XThe boot -P command line will boot it with the -P (use serial Xconsole if no keyboard) option. (see man boot for details of the Xflags). X XFinally, after all this work, the kernel is uncompressed and Xloaded into memory, and kernel execution is started. The kernel Xdoes its initialization, and then the userconfig kernel module is Xinitialized. The 'userconfig_script' setting will cause it to it Xreads the /kernel.config file, and then, since we have generated Xour kernel with the INTRO_USERCONFIG option, the kernel will go Xinto VISUAL userconfig operation. X XTo stop the loader from going into /kernel.config Xuser interactive mode automatically, you need to modify the XPICOBSD configuration file. Comment out the following line: X X options INTRO_USERCONFIG #imply -c and parse X Xand regenerate the kernel. X XHere are the commands used to set up all of this: X X # we make a compressed loader mkdir /mnt/boot cp /boot/loader . X kzip -v loader mv loader.kz /mnt/boot/loader rm -f loader loader.o X X # set up the /boot.config file to cause boot2 to load /boot/loader X echo "/boot/loader" >/mnt/boot.config X X # set up the /boot/loader.rc to cause the /boot/loader to X # load in the kernel and set options X X cat >/mnt/boot/loader.rc <build << 'END-of-build' X#!/bin/sh - X X# usage: build [what] X# what can be 'dial', 'net', 'isp', 'router', user X# X X# X# $Id: build,v 1.12 1999/01/19 23:02:05 abial Exp $ X# X Xwhile [ -n "$1" ] ; do X case "$1" in X -v ) verbose=-x; X set -x X ;; X * ) break;; X esac Xdone X X# You can set the SRC variable which points to your source tree. It's X# /usr/src by default (most people shouldn't change it). XSRC=/usr/src X X# Default MFS sizes for different types of the floppy. Again, most people X# shouldn't change them unless they know what they are doing. X XDIAL_DFLT_SIZE=1600 XROUTER_DFLT_SIZE=820 XNET_DFLT_SIZE=1700 XISP_DFLT_SIZE=1700 XDFLT_SIZE=1700 X X# DEVFS is currently broken. Always set this. X# XNO_DEVFS=yes X X# Path to srcdirs of special program for init(8) (standard if empty) XINIT= X X# --------- YOU SHOULD NOT NEED TO CHANGE ANYTHING BELOW ----------- X# The "build" script will ask you for parameters. Just run it... :-) X# --------- YOU SHOULD NOT NEED TO CHANGE ANYTHING BELOW ----------- X X X# Build kernel with previously set parameters. X X X# Main build procedure. It calls other scripts (stage1-3 and populate) Xmain() { X Xsuffix="-$TYPE" Xexport suffix Xif [ ! -d ../${TYPE} ] ; then X echo "You need `pwd`/../${TYPE} directory "; false; fi; Xif [ ! -f ../${TYPE}/conf/PICOBSD ] ; then X echo "You need `pwd`/../${TYPE}/conf/PICOBSD file"; false; fi; X Xclear Xecho "-> Building with following parameters:" Xecho -n " Type: ${TYPE}" Xif [ "X${INIT}" != "X" ] Xthen X echo " (using ${INIT} as init(8))" Xelse X echo "" Xfi Xecho " MFS size: ${SIZE} kB" Xecho " Language: ${LANGUAGE}" Xecho "" Xecho "-> We'll use the sources living in ${SRC}" Xecho "" Xecho "-> I hope you have checked the ../${TYPE}/conf/PICOBSD config file..." Xecho "" Xecho "" X# sleep 2 X X Xexport SIZE LANGUAGE TYPE SRC NO_DEVFS INIT X Xfor i in build_kernel stage1 populate stage2 stage3 Xdo X echo "====================== ${i} started =====================" X sh $verbose ./${i} X if [ "X$?" != "X0" ] X then X echo "" X echo "-> ERROR in \"${i}\" script. Aborting the build process." X echo -n "-> Cleaning temporary files... " X umount -f /mnt X vnconfig -u /dev/rvn0 X ./clean ${TYPE} X echo "Done." X exit 10 X else X echo "==================== ${i} completed =====================" X fi Xdone X} X X# Ask for, and set the custom config directory X Xset_custom() { X clear X echo " Custom directory setup" X echo "" X echo "Please enter the full path to the directory containing your" X echo "custom setup." X echo "This directory tree must be laid out exactly like the standard" X echo "ones. (E.g. you can type in /home/abial/work/custom, which" X echo "should contain conf/, crunch1/, floppy.tree/, lang/, mfs.tree/)." X echo "" X read -p "Enter the custom directory: " CUST_DIR X if [ "X${CUST_DIR}" = "X" ] X then X echo "-> Error. Custom directory cannot be null!" X exit 1 X fi X} X X# Set the LANGUAGE variable X Xset_lang() { X clear X echo " Language setup" X echo "" X echo "Language can be either 'en' (English - default) or 'pl' (Polish)" X echo "" X read -p "Enter the LANGUAGE (en, pl): " LANGUAGE X if [ "X${LANGUAGE}" = "X" ] X then X LANGUAGE=en X fi X} X X# Set the INIT variable X Xset_init() { X clear X echo " Choose your init(8) program" X echo "" X echo "You can choose either standard init(8) (which requires getty), or" X echo "you can choose 'oinit' from TinyWare collection." X echo "" X read -p "Enter the INIT (init, oinit): " INIT X if [ "X${INIT}" = "Xinit" ] X then X unset INIT X fi X} X X# Set the default MFS size depending on the type of setup Xset_dflt_size() { X if [ -z "$SIZE" ] ; then X case $TYPE in X dial ) SIZE=$DIAL_DFLT_SIZE;; X net ) SIZE=$NET_DFLT_SIZE;; X router ) SIZE=$ROUTER_DFLT_SIZE;; X isp ) SIZE=$ISP_DFLT_SIZE;; X * ) SIZE=$DFLT_SIZE;; X esac X fi; X echo "default MFS size for \"${TYPE}\" type floppy is ${SIZE} K" X} X X# Set the default INIT size depending on the type of setup X Xset_dflt_init() { X if [ -z "$INIT" ] ; then X case $TYPE in X router ) INIT=oinit;; X esac X fi; X echo "default INIT for \"${TYPE}\" is '${INIT}'" X} X X# Set MFS size interactively X Xset_size() { X clear X echo " Memory Filesystem (MFS) Size setup" X echo "" X echo " Size can be anything decent (usually 1700 or 2500) in kB." X echo " NOTE1: you can also use other numbers (e.g. 1500, 1456, 1789 ...)" X echo " even much bigger (like 4567), but keep in mind that this memory is" X echo " totally lost to other programs. Usually you want to keep this as small as" X echo " possible." X echo "" X echo " NOTE2: for pre-canned setups there are specific requirements:" X echo " dial - requires at least SIZE=$DIAL_DFLT_SIZE" X echo " router - requires at least SIZE=$ROUTER_DFLT_SIZE (500kB less without SNMP)" X echo " net - requires at least SIZE=$NET_DFLT_SIZE (500kB less without SNMP)" X echo " isp - requires at least SIZE=$ISP_DFLT_SIZE (500kB less without SNMP)" X echo "" X echo " The last two configurations are not likely to run reliably on machines" X echo " with less than 10MB of RAM, while the 'dial' is tested and proved to run" X echo " as many as ~30 processes on 10 consoles with only 8MB RAM. YMMV." X echo "" X read -p "Enter the SIZE in kB: " SIZE X if [ "X${SIZE}" = "X" ] X then X set_dflt_size X fi X} X X# Set type of floppy interactively X Xset_type() { X clear X echo " Setup the type of configuration" X echo "" X X echo " Type can be either 'dial', 'router', 'net' or 'isp'. There are four" X echo " sets of configuration files in subdirs ../dial, ../router, ../net" X echo " and ../isp respectively - the contents of the floppy is constructed" X echo " basing on the Makefiles and scripts in them." X echo "" X echo " You can also type in 'custom', and you'll be asked to enter the" X echo " full path to directory tree, where you stored your custom" X echo " configuration, laid out exactly like the standard ones. (E.g." X echo " you can type in /home/abial/work/custom, which should contain" X echo " conf/, crunch1/, floppy.tree/, lang/, mfs.tree/)." X echo "" X echo " If you define TYPE=dial, you'll end up having a floppy which is" X echo " suitable for dialup access and not much else. If you define TYPE=net," X echo " you'll have a small router-fixit-like floppy, which lacks most" X echo " interactive tools. TYPE=isp gives you a dialin server floppy." X echo "" X read -p "Enter the TYPE of the floppy (dial, net, router, isp): " TYPE X if [ "X${TYPE}" = "X" ] X then X TYPE=dial X fi X case $TYPE in X custom ) X set_custom X (ln -sf ${CUST_DIR} ../custom) X ;; X esac X set_dflt_size X set_dflt_init X} X Xput_title() { X clear X echo " Building the PicoBSD v. 0.4 floppy" X echo "============================================================================" X echo "" X} X X X#------------------------------------------------------------------- X# Main entry of the script X X# If $1="package", it creates a neat set of floppies X Xif [ X"$1" = X"package" ] Xthen X touch build.status X echo "##############################################" >>build.status X echo "## `date` ">>build.status X echo "##############################################" >>build.status X ./clean dial X for y in en pl X do X for z in dial router net isp X do X TYPE=${z} X LANGUAGE=${y} X INIT= X SIZE= X set_dflt_size X set_dflt_init X echo "---------------------------------------------">>build.status X echo "Building TYPE=${z}, LANGUAGE=${y}, INIT=${INIT}, SIZE=${SIZE}" >>build.status X export TYPE SIZE LANGUAGE SRC NO_DEVFS INIT X main X if [ "X$?" != "X0" ] X then X echo " ** FAILED! **">>build.status X else X echo " (ok)">>build.status X fi X mv picobsd.bin pb_${y}${suffix}.bin X echo "Calling ./clean for ${TYPE}, ${LANGUAGE}, ${SIZE}">>build.status X ./clean ${TYPE} X done X done X exit 0 Xfi X X# Set build parameters interactively X XTYPE=$1 Xif [ -z "$TYPE" ] ; then X TYPE=dial Xfi; XLANGUAGE=en Xset_dflt_size Xset_dflt_init Xif [ "$1X" = "X" ] ; then Xwhile [ "X${ans}" != "Xn" ] Xdo X put_title X echo "Current build parameters are as follows:" X echo "" X echo " 1. Type: ${TYPE}" X if [ "X${INIT}" != "X" ] X then X echo " a. (using ${INIT} as init(8))" X else X echo " a. (using stock init as init(8))" X fi X echo "" X echo " 2. MFS size: ${SIZE} kB" X echo " 3. Language: ${LANGUAGE}" X echo "" X echo "Which parameter would you like to change?" X read -p "(1, a, 2, 3; n -no change, build it ; q -quit): " ans X case ${ans} in X 1) set_type X clear X ;; X a) set_init X clear X ;; X 2) set_size X clear X ;; X 3) set_lang X clear X ;; X q) echo "" X echo "Hey! Don't give up so quickly. Quitting for now..." X echo "" X exit 0 X ;; X n) ;; X *) echo "Unknown option \"${ans}\". Try again." X sleep 2 X clear X ;; X esac Xdone Xfi X# Export the parameters Xexport LANGUAGE SIZE TYPE SRC NO_DEVFS INIT X# Call the build procedure Xmain X# Install if it's ok. Xecho "" Xif [ "X$?" = "X0" ] Xthen X echo "The build process was completed successfuly." X echo "" X echo "Now we are going to install the image on the floppy." X ./install Xfi Xexit 0 END-of-build echo x - build_kernel sed 's/^X//' >build_kernel << 'END-of-build_kernel' X#!/bin/sh - X# build a kernel X Xset -e Xecho "" Xecho "-> Checking if we have to build the PICOBSD kernel..." X(cd ../${TYPE}/conf; make) Xecho "" END-of-build_kernel echo x - clean sed 's/^X//' >clean << 'END-of-clean' X#! /bin/sh - X X# X# $Id: clean,v 1.7.2.1 1999/02/05 12:15:00 abial Exp $ X# Xset -e X Xif [ $# -lt 1 ] Xthen X echo "What to clean? Possible targets are 'dial', 'net', 'isp', 'router' or 'all'" X exit 1 Xfi X Xif [ "$1" = "all" ] Xthen X list="dial net isp router" X if [ -f picobsd.bin ] X then X mv -f picobsd.bin picobsd.bin.old X fi Xelse X list=$1 X if [ -f picobsd.bin ] X then X mv -f picobsd.bin picobsd.bin.$1 X fi Xfi X Xrm -f kernel kernel.kz fs.PICOBSD *.o *core *.db Xcd .. Xrm -rf help/tmp_hlp Xecho "===================== $0 tools started ====================" Xfor i in `ls -d tinyware/[a-z]*` tools/write_mfs_in_kernel Xdo X (cd ${i}; \ X if [ -f Makefile ]; \ X then \ X make clean && make cleandepend;\ X fi) Xdone Xfor j in $list Xdo X echo "===================== $0 $j started ======================" X (cd ${j}/crunch1; \ X if [ -f Makefile ]; \ X then \ X make clean ; \ X fi) X echo "=============== $0 $j completed successfuly ==============" Xdone END-of-clean echo x - install sed 's/^X//' >install << 'END-of-install' X#!/bin/sh X X# X# $Id: install,v 1.2 1998/09/29 11:58:54 abial Exp $ X# XFILENAME=picobsd.bin X Xset -e X Xecho "Please insert a blank floppy in /dev/fd0." Xecho "WARNING: the contents of the floppy will be permanently erased!" Xecho "Your options:" Xecho " * ^C to abort," Xecho " * Enter to install \"${FILENAME}\"," Xecho " * name of other file to install." Xecho "" Xread -p "Your choice: " junk Xif [ "X${junk}" != "X" ] Xthen X FILENAME=${junk} Xfi Xecho "Writing ${FILENAME}..." Xdd if=${FILENAME} of=/dev/rfd0 Xecho "Done." END-of-install echo x - modify sed 's/^X//' >modify << 'END-of-modify' X#!/bin/sh X X# Mount the picobsd.bin image on /mnt X# so you can modify the files X# X Xumount /mnt 2> /dev/null || true Xumount /dev/vn0 2> /dev/null || true Xvnconfig -u /dev/rvn0 2> /dev/null || true Xvnconfig -c /dev/rvn0 picobsd.bin 2>/dev/null Xmount /dev/vn0c /mnt END-of-modify echo x - populate sed 's/^X//' >populate << 'END-of-populate' X#!/bin/sh -x X# X# $Id: populate,v 1.8.2.2 1999/02/15 00:29:51 abial Exp $ X# X Xset -e X. ../Version X Xpwd=`pwd` X Xecho "-> Populating MFS tree..." Xcd ../${TYPE}/mfs.tree Xmake Xif [ X"${NO_DEVFS}" != X"" ] Xthen X make devnodes Xfi X X# we put in the /etc/rc script X# if there is a ../lang.mfs.rc.${LANGUAGE} -> /etc/rc X# if there is a ../lang.mfs.oinit.rc.${LANGUAGE} -> /etc/oinit.rc X Xif [ -f ../lang/mfs.rc.${LANGUAGE} ] ; then X cat ../lang/mfs.rc.${LANGUAGE}| \ X sed -e "s/@VER@/${VER}/g" > \ X /mnt/etc/rc Xfi X Xif [ -f ../lang/mfs.oinit.rc.${LANGUAGE} ] ; then X cat ../lang/mfs.oinit.rc.${LANGUAGE}| \ X sed -e "s/@VER@/${VER}/g" > \ X /mnt/etc/oinit.rc Xfi X Xif [ ! -f /mnt/etc/oinit.rc -a -f /mnt/etc/rc ] ; then X ln -s rc /mnt/etc/oinit.rc Xfi X Xif [ -f login.conf ] ; then X cp login.conf /mnt/etc/login.conf Xfi; X Xif [ ../lang/README.${LANGUAGE} ] ; then X cat ../lang/README.${LANGUAGE} | \ X sed -e "s/@VER@/${VER}/g" > \ X /mnt/README Xfi; Xif [ -f ../lang/update.${LANGUAGE} ] ; then X cp ../lang/update.${LANGUAGE} /mnt/stand/update Xfi Xif [ "${TYPE}" = "dial" ] Xthen X cp ../lang/reboot.${LANGUAGE} /mnt/stand/reboot X ln -f /mnt/stand/reboot /mnt/stand/shutdown X cp ../lang/login.${LANGUAGE} /mnt/stand/login X cp ../lang/dialup.${LANGUAGE} /mnt/stand/dialup X (cd ../../help;\ X rm -rf tmp_hlp;\ X mkdir tmp_hlp;\ X for i in `ls *.hlp.${LANGUAGE}`;\ X do \ X cp $i tmp_hlp/`basename $i .hlp.${LANGUAGE}`;\ X done;\ X cd tmp_hlp;\ X ar -cru help.a *;\ X cp help.a /mnt/help.a) Xfi X Xecho "-> Making and installing crunch1..." Xcd ../crunch1 Xmake "SRC=${SRC}" && make install 2>&1 >/dev/null Xif [ "X$?" != "X0" ] Xthen X echo "-> ERROR while building ../${TYPE}/crunch1..." X echo "-> Aborting $0" X exit 10 Xfi X Xcd ${pwd} X X(echo "-> Fixing permissions"; cd /mnt; chown -R root *) END-of-populate echo x - stage1 sed 's/^X//' >stage1 << 'END-of-stage1' X#!/bin/sh -x X X# X# $Id: stage1,v 1.7 1999/01/19 23:02:05 abial Exp $ X# X Xset -e Xecho ${SRC}/sys/compile/PICOBSD${suffix}.${SIZE}/kernel X Xif [ ! -f ${SRC}/sys/compile/PICOBSD${suffix}.${SIZE}/kernel ]; then X echo "-> ERROR: you must build PICOBSD${suffix}.${SIZE} first" X exit 1 Xfi X Xecho "-> Preparing kernel..." Xcp -p ${SRC}/sys/compile/PICOBSD${suffix}.${SIZE}/kernel kernel X#if [ "${TYPE}" != "dial" ] X#then X# echo "-> Preparing kvm database..." X# mv /var/db/kvm_kernel.db /var/db/old.db X# kvm_mkdb kernel X# cp /var/db/kvm_kernel.db kvm_kernel.db X# mv /var/db/old.db /var/db/kvm_kernel.db X#fi X Xecho "-> Preparing MFS filesystem..." Xumount /dev/vn0 2> /dev/null || true Xumount /mnt 2> /dev/null || true Xvnconfig -u /dev/rvn0 2> /dev/null || true X Xdd of=fs.PICOBSD if=/dev/zero count=${SIZE} bs=1k 2> /dev/null X X### --- removed papowell@astart.com X### This is not needed with 3.1 disklabel utility X#awk 'BEGIN {printf "%c%c", 85, 170}' | \ X# dd of=fs.PICOBSD obs=1 seek=510 conv=notrunc 2> /dev/null X X#vnconfig -c /dev/rvn0 fs.PICOBSD 2>/dev/null Xvnconfig -s labels -c /dev/rvn0 fs.PICOBSD 2>/dev/null X Xif [ "X$?" != "X0" ] Xthen X echo "-> Error while doing vnconfig of fs.PICOBSD on /dev/rvn0..." X echo " Most probably your running kernel doesn't have the vn(4) device." X echo "-> Aborting $0" X exit 10 Xfi X X### --- removed papowell@astart.com X### This is not needed with 3.1 disklabel utility X#dd if=/usr/mdec/boot1 of=fs.PICOBSD conv=notrunc 2> /dev/null X### *** dd writes boot record? X#dd if=/boot/boot1 of=fs.PICOBSD conv=notrunc 2> /dev/null X X### --- removed papowell@astart.com X### from --- to --- and replaced by 'disklabel vn0 auto' Xdisklabel -rw vn0 auto X X##--- This command does weird things on 2.2.x systems. In such case use normal X## disktype here instead X#if [ "${TYPE}" != "router" ] X#then X# disklabel -rw vn0 auto X#else X# if [ ${SIZE} -lt 1024 ] X# then X# disklabel -rw /dev/rvn0 fd${SIZE} X# else X# disklabel -rw vn0 auto X# fi X#fi X### --- X Xif [ "X$?" != "X0" ] Xthen X echo "-> Error while labeling fs.PICOBSD (vn0)..." X echo "-> Aborting $0" X exit 10 Xfi X X# Default setting for other (custom) setups. XINODES=4096 X# You can save some space on MFS if you don't want so many inodes... Xif [ -z "$INODES" ] ; then X case $TYPE in X * ) INODES=4096;; X router ) INODES=3072;; X esac Xfi X Xnewfs -i $INODES -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null Xmount /dev/vn0c /mnt Xif [ "X$?" != "X0" ] Xthen X echo "-> Error while mounting fs.PICOBSD (/dev/vn0c) on /mnt..." X echo "-> Aborting $0" X exit 10 Xfi END-of-stage1 echo x - stage2 sed 's/^X//' >stage2 << 'END-of-stage2' X#!/bin/sh -x X X# X# $Id: stage2,v 1.3 1999/01/14 23:14:46 abial Exp $ X# Xset -e X Xif [ ! -f kernel ]; then X echo "-> ERROR: you must build PICOBSD${suffix}.${SIZE} kernel first" X exit 1 Xfi X Xecho "-> Preparing kernel with MFS filesystem inside..." X X### display how much you have used Xdf -ik /mnt Xumount /mnt 2>&1 >/dev/null Xfsck -p /dev/rvn0c Xvnconfig -u /dev/rvn0 2>&1 >/dev/null X X# generate the write_mfs_in_kernel tool Xif [ ! -f ../tools/write_mfs_in_kernel/wmik ]; then X (cd ../tools/write_mfs_in_kernel; make) Xfi X X../tools/write_mfs_in_kernel/wmik kernel fs.PICOBSD Xstrip kernel Xstrip --remove-section=.note --remove-section=.comment kernel X X### compress the kernel Xgzip -9 -n -f kernel Xrm fs.PICOBSD END-of-stage2 echo x - stage3 sed 's/^X//' >stage3 << 'END-of-stage3' X#!/bin/sh -x X X# X# $Id: stage3,v 1.4 1999/01/14 23:14:46 abial Exp $ X# Xset -e X X. ../Version X Xif [ ! -f kernel.gz ]; then X echo "-> ERROR: you must build kernel.gz first" X exit 1 Xfi X Xecho "-> Preparing 1.44 floppy filesystem..." X### comments added papowell@astart.com Wed Apr 28 16:12:04 PDT 1999 X X### we make sure that the rvn0 system is available Xumount /dev/vn0 2> /dev/null || true Xumount /mnt 2> /dev/null || true Xvnconfig -u /dev/rvn0 2> /dev/null || true X X### now we make the file for the vnode file system Xdd of=picobsd.bin if=/dev/zero count=1440 bs=1k 2> /dev/null X X### --- removed papowell@astart.com X### this does not seem to be needed when using 3.1 disklabel utility X#awk 'BEGIN {printf "%c%c", 85, 170}' | \ X# dd of=picobsd.bin obs=1 seek=510 conv=notrunc 2> /dev/null X# vnconfig -s labels -c /dev/rvn0 picobsd.bin 2>/dev/null X X# we now configure the picobsd.bin file for use as the vnode file system Xvnconfig -c /dev/rvn0 picobsd.bin 2>/dev/null X X### -- removed papowell@astart.com X### the disklabel 'fd1440' should take care of this X### Note 1: FreeBSD 3.1-RELEASE does not use mdec X#dd if=/usr/mdec/boot1 of=picobsd.bin conv=notrunc 2> /dev/null X### the disklabel 'fd1440' should take care of this X#dd if=/boot/boot1 of=picobsd.bin conv=notrunc 2> /dev/null X X### -- updated papowell X### the disklabel with fd1440 will take care of the boot sectors X### and boot information X#disklabel -Brw -b /usr/mdec/fdboot -s /usr/mdec/bootfd /dev/rvn0 fd1440 2>&1 >/dev/null X X# we label the vnode file system as a floppy disk and install boot X# blocks Xdisklabel -Brw /dev/rvn0 fd1440 2>&1 >/dev/null X X### -- updated papowell@astart.co X### you may find that 32768 inodes is a little much, especially if you X### need every little bit of space X### newfs -i 32768 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null X X# now we do a newfs and mount the file as /mnt Xnewfs -i 4096 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null Xmount /dev/vn0c /mnt X X### sigh... this is ugly, but it works... Xpwd=`pwd` X X### --- added comments papowell@astart.com X### Note 1: these files are generated from the X### language dependent part of the tree. If the file X### is not there, then you get a nasty error and die X### We put a check for the file. Note that this allows X### us to put the rc.conf and rc.network files into a list X### Note 2: really, we ought to simply do: X### for i in ../lang/*.${LANGUAGE} X### and not worry about the language specific files X### Xcd ../${TYPE}/floppy.tree Xecho "-> Copying language dependent files..." Xfor i in hosts motd rc resolv.conf rc.conf Xdo X if [ -f ../lang/${i}.${LANGUAGE} ] ; then X cat ../lang/${i}.${LANGUAGE} | \ X sed -e "s/@VER@/${VER}/g" > \ X etc/${i} X fi; Xdone X X### --- removed, see above comments about tests X#if [ "${TYPE}" != "router" ] X#then X# cat ../lang/rc.conf.${LANGUAGE} | \ X# sed -e "s/@VER@/${VER}/g" > \ X# etc/rc.conf X# cat ../lang/rc.network.${LANGUAGE}| \ X# sed -e "s/@VER@/${VER}/g" > \ X# etc/rc.network X#fi X Xecho "-> Populating floppy filesystem..." X### -- this is tricky - you want to put in the boot.help file Xcat ../lang/boot.help.${LANGUAGE} | \ X sed -e "s/@VER@/${VER}/g" > \ X /mnt/boot.help X X### now you copy all the files in ${TYPE}/floppy.tree to /mnt Xcp -pr . /mnt Xrm -rf /mnt/CVS /mnt/etc/CVS /mnt/etc/ppp/CVS X X### this provides a prebuilt password file - but it takes space Xif [ "${TYPE}" = "dial" ] Xthen X pwd_mkdb -d etc/ etc/master.passwd X mv etc/spwd.db /mnt/etc/ X rm etc/pwd.db Xfi X X### we return to our original directory, and copy the kernel to the floppy image X### kernel Xcd ${pwd} Xcp kernel.gz /mnt/kernel.gz Xrm kernel.gz X X### now we add the boot loader - boot1 and boot2 were done by disklabel X### X### Here is the boot sequence: X### (boot0 on floppy sector 0/0/1) loaded into memory and executed X### boot1 finds UNIX partition, brings in boot2, starts execution of boot2 X### Boot1 usually does things using BIOS facilities X### Boot2 has quite a bit of the UNIX ufs file system, and can understand UFS X### file systems. X### boot2 will open /boot.config, read THE SINGLE LINE IN THE FILE, X### and interpret it as the name of a kernel and some options to pass X### to the kernel. X### The PICOBSD setup initializes boot.config with X### /boot/loader X### which tells boot2 to use the /boot/loader code as a kernel. X### X### What is this all about? The answer is simple: we want to be able to X### configure the devices by using the 3rd Stage Loader. But this X### loader is a little big, so we use the kzip (kernel zip) facility X### to compress it and attach a bit of code to decompress and then run X### the compressed code. X### X### The /boot/loader will now uncompress itself and will then read the X### (documented in the source code) file X### /boot/loader.rc X### This contains a list of commands that the loader understands. X### (Aside: /boot/loader.rc used to be /boot/boot.conf in earlier FreeBSD X### releases, and this name is is pretty close to boot.config (see above). X### I wonder how many people this has confused?) X### X### The /boot/loader.rc file contains the following commands: X### load /kernel X### load -t userconfig_script /kernel.config X### boot -P X### (see /usr/src/boot/common/help.common for list of commands) X### X### load /kernel loads /kernel into memory, and the boot -P X### line will boot it with the -P (use serial console if no keyboard) option. X### (see man boot for details of the flags) X### X### The load -t userconfig_script /kernel.config X### sets the kernel's 'userconfig_script' option value to X### "/kernel.config". The 'userconfig' module in the kernel X### (see /usr/src/sys/i386/i386/userconfig.c for the nasty details) X### will open and read this file, getting commands to set device X### configuration and other things. X### These commands can be: X### example X### di disable dev di de0 X### dr drq dev # dr 4 X### ei # EISA slots ei 4 X### en enable dev en ep0 X### ex exit (quit) ex X### f flags dev mask f de0 0xff X### h help X### intro intro screen X### iom iomem dev addr iom ed0 0xdf0000 X### ios iosize dev size iosize ed0 0x1000 X### ir irq dev # irq ed0 5 X### l ls, list l X### pn pnp ... pnp X### po port dev addr port ed0 0x300 X### res reset CPU res X### q quit q X### v visual mode v X### X### I strongly suspect that this has been included strictly as a Tour de Force X### example of how to make the loading as flexible as possible, etc, without X### needing to compile a special version of the boot code. X### X### Finally, after all this work, the kernel is loaded into memory, X### and kernel execution is started. Of course we have compressed the X### kernel, so it will promptly uncompress itself and start execution. X### X### The userconfig module is started, it reads the /kernel.config file, X### and then, since we have generated our kernel with the INTRO_USERCONFIG X### option, the kernel will go into VISUAL userconfig X### operation. X### X### To stop the loader from going into /kernel.config X### user interactive mode automatically, you need to modify the X### PICOBSD configuration file. Remove the X### options INTRO_USERCONFIG #imply -c and parse info area X### And regenerate the kernel. X### X### Suggested Alternatives X### X### Skipping the /boot/loader X### To do this, set /boot.config to contain only '-P' X### By default, you will get the kernel loaded. You should also X### compile the kernel without the INTRO_USERCONFIG option. X### X X# we make a compressed loader Xmkdir /mnt/boot Xcp /boot/loader . Xkzip -v loader Xmv loader.kz /mnt/boot/loader Xrm -f loader loader.o X X# set up the /boot.config file to cause boot2 to load /boot/loader Xecho "/boot/loader" >/mnt/boot.config X X# set up the /boot/loader.rc to cause the /boot/loader to X# load in the kernel and set options Xcat >/mnt/boot/loader.rc < Fixing permissions"; cd /mnt; chown -R root * ) X X### little bit of information for users Xdf -ik /mnt Xls -Rl /mnt X Xumount /mnt X# and we are finished Xvnconfig -u /dev/rvn0 END-of-stage3 exit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Apr 30 1:15:23 1999 Delivered-To: freebsd-small@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2B518158D6 for ; Fri, 30 Apr 1999 01:14:53 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA11713; Fri, 30 Apr 1999 01:14:41 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: papowell@astart4.astart.com Cc: freebsd-small@freebsd.org Subject: Re: picobsd and /dev/MAKEDEV problems In-reply-to: Your message of "Thu, 29 Apr 1999 20:05:32 PDT." <199904300305.UAA11181@astart4.astart.com> Date: Fri, 30 Apr 1999 01:14:41 -0700 Message-ID: <11707.925460081@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have been adding some functionality to the various build > scripts, when I discovered that the /dev/MAKEDEV script was not > generating devices, but picobsd/build was not reporting an error. Hmmm. This doesn't apply to -current sources, which appear to have changed a bit in this area. Are you sure you're using the latest picobsd sources? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Apr 30 4:16:25 1999 Delivered-To: freebsd-small@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 0324F15057 for ; Fri, 30 Apr 1999 04:16:23 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id E7D6C18D0; Fri, 30 Apr 1999 13:16:45 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id E6EEF49BD; Fri, 30 Apr 1999 13:16:45 +0200 (CEST) Date: Fri, 30 Apr 1999 13:16:45 +0200 (CEST) From: Andrzej Bialecki To: papowell@astart4.astart.com Cc: freebsd-small@FreeBSD.ORG Subject: Re: Revised picobsd Build Procedures and Scripts (Not official) In-Reply-To: <199904290528.WAA08070@astart4.astart.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 Wed, 28 Apr 1999 papowell@astart4.astart.com wrote: > The following is NOT repeat NOT an official update. Beware! Your > milage may vary, not valid in states with right angle corner > borders (quick! How many is that?) and has been shown to cause > brain damage in student assistants. > > Enjoy. Hey, you've done a great job! I'd be glad to import these changes to the picobsd source tree. Thank you very much! (if you could send me a 'cvs diff -u' output it would simplify things...). I also feel I owe you all my apologies for ..erhm.. not so fast response to your comments and suggestions during last few months. I'm in process of changing my job, my family status, and at the same time I'm moving to another country (well, in fact I'm traveling back and forth every other week for now :-/ ). and the project I'm working on consumes ca. 14 hr/day, so there is not much left for hacking... So, I'm sorry. OTOH, I'll gladly accept patches, and also I'll try at least to maintain the source tree compilable. Let's hope I'll have more time after June... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat May 1 8:10:15 1999 Delivered-To: freebsd-small@freebsd.org Received: from server.cronosnet.com (server.cronosnet.com [195.103.68.193]) by hub.freebsd.org (Postfix) with ESMTP id 1F35515B18 for ; Sat, 1 May 1999 08:09:49 -0700 (PDT) (envelope-from vmori@cronosnet.com) Received: from cronosnet.com (dialup-13.cronosnet.com [195.103.68.222]) by server.cronosnet.com (8.8.8/8.6.9) with ESMTP id RAA26614 for ; Sat, 1 May 1999 17:17:13 +0200 (CEST) Message-ID: <372B191E.7897DAE4@cronosnet.com> Date: Sat, 01 May 1999 17:09:18 +0200 From: Vittorio Mori X-Mailer: Mozilla 4.07 [en] (Win95; I) MIME-Version: 1.0 To: "freebsd-small@FreeBSD.ORG" Subject: Bridging under PicoBSD compiled w/ 3.1-RELEASE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a problem with the options BRIDGE in the PicoBSD package ... Simply, the bridge doesn't work ;( With my greatest disappointment, the bridge does not seem to work even in my bsd-box kernel. My setup: FreeBSD Box: A Cyrix 6x86MX-pr300 with 32 mb ram: - two PCI NE2000 cards (chipset RealTek 8029) configured as ed1 & ed2 - bridging enabled in the kernel with the options BRIDGE & the sysctl variable Two PC clients in the network: one is set as IP 192.168.1.2 the other is IP 192.168.1.100 I simply PING from one client to another to see packets going trough the bridge. With 3.1-RELEASE : no way. The bridge is correctly initialized, the cards put in PROMISC mode, but no banana. The sad story : the PicoBSD disk downloaded from Lugi's page http://www.iet.unipi.it/~luigi WORKS perfectly. Even with two el-cheapo Realtek 8139 (fast-ethernet 10/100) cards (officially unsupported). It does all by itself: boots & the bridge code starts working. Now: is anyone here using the BRIDGE options in Fbsd 3.1-RELEASE ? And under PicoBSD ? Results ? Tnx in advance, Wyk'99 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat May 1 17:27:52 1999 Delivered-To: freebsd-small@freebsd.org Received: from astart2.astart.com (astart2.astart.com [206.71.174.194]) by hub.freebsd.org (Postfix) with ESMTP id C5A1B14CA3 for ; Sat, 1 May 1999 17:27:33 -0700 (PDT) (envelope-from papowell@astart2.astart.com) Received: from astart.com (astart52.astart.com [206.71.174.244]) by astart2.astart.com (8.8.7/8.8.5) with ESMTP id RAA07793 for ; Sat, 1 May 1999 17:38:05 -0700 (PDT) Message-ID: <36E9B1B5.3AD7E06C@astart.com> Date: Fri, 12 Mar 1999 16:30:45 -0800 From: Patrick Powell Organization: Astart Technologies X-Mailer: Mozilla 4.07 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: How2Build Update Content-Type: multipart/mixed; boundary="------------EBAC1F2D12499441013FE952" Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------EBAC1F2D12499441013FE952 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit This is a modified version of the how2build.html page in /usr/src/release/picobsd/doc/src/how2build.html I have added some corrections and additions, including a section on how FreeBSD 3.1-RELEASE sets up a two floppy boot system. Patrick Powell --------------EBAC1F2D12499441013FE952 Content-Type: text/html; charset=us-ascii; name="00049D62.html" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="00049D62.html" Content-Base: "file:///C|/WINDOWS/TEMP/00049D62.html" <center>PicoBSD Development Kit</center>

How to Build Your Own Version of PicoBSD

Andrzej Bialecki <abial@freebsd.org>

Updated and Extended by Patrick Powell <papowell@astart.com>

1. Introduction

2. Using the PicoBSD build Procedures

3. Build Options and Extensions

4. The Details

5. Multiple Boot Floppies

1. Introduction

The Using the PicoBSD build Procedures section is a guide to using the PicoBSD build facilities. Build Options and Extensions describes the options used by the build script, and the other scripts of the PicoBSD package. The Intrinsics document provides an expert level guide to the various scripts and their actions. The Details is a more an expanded form of the Intrinsics notes, together with explanations of some of the underlying technology used to make the various PicoBSD components.

1.1 Errata for FreeBSD 3.1-RELEASE

The following errata have been found in the FreeBSD 3.1-RELEASE.

  1. Missing kzip /usr/lib/aout files on FreeBSD 3.1-RELEASE.

    The necessary library files for the kzip utility are missing on the FreeBSD 3.1-RELEASE. Do the following steps to create and install them: 

       cd /usr/src/sys/i386/boot/kzipboot
   make all install
  2. Crunchgen, ppp, and -DRELEASE_CRUNCH

    Some of the binaries such as ppp will not build correctly unless the RELEASE_CRUNCH environment variable is set to 1. You must also set the -DRELEASE_CRUNCH flag in the ${TYPE}/crunch1/Makfile: 

    *** net/crunch1/Makefile        Sat May  1 16:13:50 1999
--- net/crunch1/Makefile.orig   Wed Apr 28 09:22:50 1999
***************
*** 12,18 ****
        fi
        @cat crunch.conf|sed -e "s@/usr/src@${SRC}@" >crunch1.conf
        @crunchgen ./crunch1.conf
!       @${MAKE} -f crunch1.mk -DRELEASE_CRUNCH -DNOPAM all \
            "CFLAGS=${CFLAGS} -DCRUNCHED_BINARY -DNOSECURE -DNOCRYPT" #2>&1 >/dev/null

  clean:
--- 12,18 ---- 
        fi
        @cat crunch.conf|sed -e "s@/usr/src@${SRC}@" >crunch1.conf
        @crunchgen ./crunch1.conf
!       @${MAKE} -f crunch1.mk -DNOPAM all \
            "CFLAGS=${CFLAGS} -DCRUNCHED_BINARY -DNOSECURE -DNOCRYPT" #2>&1 >/dev/null
    
  clean:

2. Using the PicoBSD build Procedures
  1. Get the file picobsd.tgz. It contains the scripts you'll need. Also, I assume you run quite -current system with full sources installed.

    NOTE1: beginning with version 0.4, PicoBSD sources are maintained as part of official FreeBSD CVS repository, so if you have recent source tree you can find them in /src/release/picobsd.

    NOTE2: there were some mysterious interactions between vn(4) driver and 'disklabel auto' in versions earlier than 3.0. There is another set of scripts prepared by Dinesh Nair which allows to build PicoBSD floppies on a earlier systems.

    NOTE3: this document reflects the modified build procedures that were developed by Patrick Powell . These are based on the FreeBSD 3.1-RELEASE distribution.

    Unpack the archive into your src/release/picobsd. You'll need at least 5MB of free space.

  2. Change working directory (cd build) and run the ./build script. Select target language, size of MFS and one of pre-canned setups (personal dialup, dialin server or router-like). Details of each setup are contained in dial/, router/, isp/ and net/ directories respectively. You should at least check ${TYPE}/config/PICOBSD file to make sure it contains the drivers you want.

    You can also choose a special type called 'custom'. You'll need to supply the full path to your own custom config tree constructed exactly like one of the standard config directories. Also, you'll probably want to adjust the number of inodes on MFS - see the stage1 script and look for INODES=.

    You can create your own configuration. The recommended method is to start with an existing configuration, such as net, and to copy the files to a your new configuration. For example, to create small, you would do: 

    cd /usr/src/release/picobsd
cp -r net small
  3. There are several directories which contain some sources and config files: 
    	build/			main build directory; you MUST cd here!
	dial/			config files for dialup setup
		conf/		kernel config file
		crunch1/	crunch of system programs
		mfs.tree/	contains the MFS configuration
		lang/		contains language-dependent files
		floppy.tree/	contains the startup floppy hierarchy

	isp/			config files for dialin server setup
		...		(as above)
	net/			config files for router-like setup
		...		(as above)
	tinyware/		collection of small system utilities
	tools/			additional tools them needed during build

    There are no /etc/passwd nor /etc/pwd.db files on the "dial" floppy - in case of other types, they are reconstructed from /etc/master.passwd on each startup (and then put on MFS with the rest of /etc). In case of "dial" type floppy, you don't need them at all.

    NOTE: thanks to the above, the floppy is needed only during startup, and then only if you want to synchronize (possibly changed) MFS /etc with the one on the floppy. It means that you can pull off the floppy from the drive as soon as login: prompt appears. In other words, it is almost equal to read-only floppy.

  4. Edit the set of installed programs.
    • Go to ${TYPE}/crunch1 directory, and edit it to suit your needs. Keep in mind that floppies aren't made of rubber... :-)
    • There are some patches included in these directories, which are applied during build process to some of the Makefiles in your /usr/src. These patches attempt to decrease the size of some programs by cutting off rarely/unlikely used parts. The patches are reversed when you do a make clean (or build/clean for that matter).

      NOTE: patches may fail to apply, if your sources are too different from the ones I used. Don't worry: they are so straightforward that you can apply them by hand.

    • In order to have a functioning system you MUST include at least one of init, or oinit, or sysinstall in your crunch.conf. Of course these can be your own programs... But if you install the stock init, you also have to install sh, getty, login etc... to provide for the standard login support.

      This release of PicoBSD contains a small replacement for init(8), called 'oinit'. You can find it in TinyWare collection.

  5. Make sure that the system you're running has /dev/[r]vn0* entries in /dev directory (if not, you can make them with 'MAKEDEV vn0'), AND that your running kernel has built-in vnode driver (there should be a line in your kernel config file stating 'pseudo-device vn').
  6. You'll need at least 9MB of free disk space, and free /mnt directory.
  7. Do a cd build/ and fire off the ./build script. Select the build parameters or 'n' for 'no change'. If all is well, after some time (like 10-30m) you end up with a 'picobsd.bin' file in this directory.

    The build script accepts the following options: 

    build [-v] [-n] [config]
  -v   verbose operation
  -n   do not write floppy
  config  - configuration, must be directory ../config
    The -v option will show the execution steps in detail. The -n suppresses writing a floppy. This can be done at a later time by using dd to copy the output picobsd.bin file to the floppy. 
    dd if=picobsd.bin of=/dev/rfd0

    If there were any errors, please execute the build script using the -v option and try to find what causes this error. Most often this will be one of the following reasons:

    • crunchgen can't find the source directory for a program 'proggy':
      • make sure that the source directory for 'proggy' is called 'proggy', otherwise the crunchgen won't find it
      • make sure that the Makefile allows crunchgen to deduce the set of objects to build. You can manually add an OBJS= ... to the program's Makefile.
    • crunch fails to build.
      • check your system source tree for stale .depend files and/or objects (*.o)
      • see if the individual programs can be built using original Makefiles. If not, cvsup the correct sources.
      • crunch fails to include all of the object files for a program. See the crunch(8) man page on how to explicitly specify the object files needed. You might also want to try to fix the Makefile for the program if it is a standard system utility.
    • /: write failed - file system is full
      • this one is obvious - you wanted to put too many programs on the MFS and/or the target floppy. Or, you really don't have any space left on the root partition.. :-)
      • also, you can check if the MFS size is correctly reported while it's still mounted (right after stage1 script ends).
    You can also remove 2>&1 redirections from Makefiles to see the stderr.

That's all. You're welcome to change and improve these scripts. If you stumble upon something which looks like a good idea to have it here, let me know.

If, for some reason, the scripts don't work for you at all, also let me know.

3. Build Options and Extensions

The build command is invoked with: 

build [-v] [-n] [config]
  -v   verbose operation
  -n   do not write floppy
  config  - configuration, must be directory ../config

The -v option will show the execution steps in detail. The -n suppresses writing a floppy. This can be done at a later time by using dd to copy the output picobsd.bin file to the floppy.

The build script's purpose is to set the following environment variables, and then invoke the build_kernel, stage1, populate, stage2, stage3, and optionally install scripts. See Intrinsics or the sections below for details about each of these scripts.

  • TYPE=config
    This is the name of the configuration that will be built. By default, the configuration files will be in ../$TYPE, relative to the build directory. The when the custom configuration is used, build will create a symbolic link from ../custom to the specified location of the files.
  • SRC=path to source files
    This is the location of the source files for the system configuration. The default is /usr/src
  • SIZE=N
    The number of Kbytes of memory to be used at run time for the MFS (Memory File System). This should be large enough to contain all of the executables files to be placed in MFS. See the discussion later about the Kernel and MFS Generation.
  • LANGUAGEen or pl
    Some of the files put in the MFS during creation have English and Polish versions. The default is en (English).
  • INODES=1024
    The number of inodes for the MFS. If you want to put a large number of files into the MFS, then you will need to increase the number of inodes.
  • PREBUILD_PASSWD=no
    You can prebuild the /etc/passwd file and put it into the MFS. However, this will take up quite a bit of space. The default is to put a small /etc/master.passwd file into the MFS, and during system initialization to create the /etc/passwd file using the pw_dbgen. This method allows you to store a modified password file on the floppy disk and be able to edit it using normal tools. This is discussed in later sections.

The build_kernel script will configure and build a kernel using the files in the ../${TYPE}/conf directory. The kernel will be in the /usr/src/sys/i386/compile/PICOBSD-${TYPE} directory.

The stage1 script will create an MSF file system of $SIZE Kbytes and mount it on /mnt. The populate script will copy files from ../${TYPE}/lang and generate a crunch file using the ../${TYPE}/crunch1 directory and files. These are all put into the MFS generated by stage1. stage2 will put the MFS into the kernel, and finally stage3 will generate a floppy disk image. The install script may then be used to copy the image to an actual floppy disk.

4. The Details

This section is a discussion of the various techniques and background technology needed to build a FreeBSD PICOBSD release. It assumes that the reader is familiar with building a FreeBSD system, and has had some experience with system installation as well.

For technical details, I recommend studying the reading list available in the FreeBSD FAQ. There are many excellent books and articles there, but it is difficult to know where to start.

4.1 Kernel, MFS, and Root File System

One of the more interesting aspects of the picobsd system is how you embed a Memory File System image into a kernel, and how the entire system gets packaged and started. These notes will explain the underlying methods, and will hopefully provide a guideline to persons wanting to use picobsd for some radically different situtations.

First, we will review the BSD Kernel boot process, then we will discuss the root file system and how the kernel finds and mounts the root file system. Next we will briefly cover how the Memory File System is implemented in the kernel, and then how you can specify that the root file system is a MFS. Finally, we will explain how the contents of the MFS are initialized at system generation, and how we can then compress a kernel to make it even smaller.

4.2 BSD Kernel Organization

Briefly, the BSD kernel image is organized as a series of blocks of bytes in a file. Depending on the type of kernel object format, the location and order differ, but the following blocks are present:

  • header - tells the size, location, and order of the other blocks in the executable. Also tells the size and location of unitialized data areas, and the staring location or entry point of the code.
  • code - the executable code
  • preinitializaed data - strings and other values that have been statically initialized during system compilation.
  • relocation information - used to update kernel address locations

During system boot, the kernel executable code is loaded into memory, the initialized memory is set up, the uninitialized memory area is zeroed, and the relocation information is scanned and locations in the kernel are set to actual locations of strings or other data structures in memory. The loader will then jump to (or call) the kernel entry point.

At this point the kernel is now in charge, and will proceede to execute code to initialize various modules or data structures and hardware devices. This initialization is not the device probing, but a much more low level initialization of devices such as the floating point unit, memory management, and other essential devices.

One of the most essential devices is the root file system device. In fact, this is so essential that it is actually specified in the kernel config file used to build the kernel: 

config          kernel  root on fd0a
For details on this, see the /usr/share/doc/smm/04.config. If you really want to suffer, you can also look at /usr/src/sys/kern/init_main.c for some really gory details.

By explicitly specifying the root file system device early in the booting process the kernel will be able to read (and write) files from the root device. This allows the kernel to read a kernel configuration file from the root file system which can be used to modify device probing operations.

After probing and initializing devices, the kernel will then start scheduling processes for execution. One of the very first processes is the so called init process. In FreeBSD 3.1-RELEASE, the kernel will sequentially search for /sbin/init, /sbin/oinit, /sbin/init.bak, or /stand/sysinstall, and execute the first one it finds. It is the responsibility of this process to carry out the necessary system initialization and set up user logins. By convention, the init process will run the /etc/rc script to do initialization, wait for users to log on. See man init, or the /usr/src/sbin/init/init.c file for the graphic details.

You should be aware that init will record login and other information in the following files: 

/var/run/utmp     The utmp file.
/var/log/wtmp     The wtmp file.
/var/log/lastlog  The lastlog file.
The good news is that init will not create the files. The bad news is that the files will continue to grow, and may fill up the file system. On very small file system this can be a problem, and you should not create these files or arrange for them to be truncated at appropriate intervals.

4.3 Memory File Systems

A Unix file system consists of a device corresponding to hardware where the information is stored, a device driver which provides the necessary kernel level operations to read and write data from the device, and a mount service which provides the interface between the kernel's file system primitives (read, write, open, etc) and the device driver. The mount service can also translate one file system format such as MSDOS into sensible UNIX files.

The Memory File System has a rather simple device and device driver: the device is a block of memory. The device driver simply copies information to and from these memory areas.

This memory area can in two places:

  1. Process image, which can be swapped out, size limited by swap space
  2. Kernel memory, size limited by physical memory

At this point, I suggest you look at the MFS man page (man mfs) and A Pageable Memory Based Filesystem in /usr/share/doc/papers/memfs.ascii.gz for details of how this is implemented. Effectively, you run the mfs_mount command all that happens is a process will do a The MFS which uses Kernel Memory is the one which we are interested in. We first need to generate a kernel which will support MFS and allow us to use the MFS as a root device. We do this with the configuration options: 

options         MFS                     #Memory File System
options         MFS_ROOT                #MFS usable as root device
options         MFS_ROOT_SIZE=10        #Size in Kbytes

The first option, MFS, simply adds the MFS kernel modules to the kernel. The second option will define a initialized mfs_root character array of size MFS_ROOT_SIZE K bytes, and force the kernel to use this array as the root file system.

Here is the declaration of the mfs_root variable in /usr/src/sys/ufs/mfs/mfs_vfsops.c: 

static u_char mfs_root[MFS_ROOT_SIZE*1024] = "MFS Filesystem goes here";
static u_char end_mfs_root[] __unused = "MFS Filesystem had better STOP here";

During the system initialization, the kernel will look at the mfs_root variable, and expect it to have the same format as a UFS file system. If it does, then it will treat this device as the root device, and ignore any root device specified by the config specification.

We will explore how we can construct a file system and place it in the mfs_root array in the next couple of sections.

4.4 VNODE Devices and File Systems

In a previous section, we discussed how the MFS file system allows blocks of memory (even in a user process) to be used as a file system. Well, files are simply blocks of memory in some sense. Can we create a device that will allow us to access a file as a device?

The vnode device driver does exactly this. When we run the vnodeconfig program, this establishes a link between a file and a vnode device. The vnode device driver then tranlates low level kernel block io reads and writes in file lseeks and file read and write operations. Lets see how we can construct a file that we can uses as a device: 

dd of=fs.PICOBSD if=/dev/zero count=2500 bs=1k 2> /dev/null
vnconfig -s labels -c /dev/rvn0 fs.PICOBSD 2>/dev/null

The dd command will create a 2500 Kbyte file of all zeros, and then the vnconfig command will link the file to the /dev/rvn0 and /dev/vn0 devices. You can use /dev/rnv0 to access the file contents: 

dd if=/dev/rnv0 bs=1 count=4 seek=32
But we can also format the device ... I mean file so that its contents have the structure of a hard drive. In the FreeBSD environment we use the disk label utility to write a block of data at a specific offset from the start of the disk... I mean file, that provides information about the number of sectors, tracks, and cylinders on the device, and installs any boot blocks if requred. This is done using the disklabel command as follows: 
disklabel -rw vn0 auto

The auto option will simply query the VNODE driver code for the disk information and will copy this to the label area. See man disklabel for details about this operation.

The file contents now are an image of a generic disk drive, and we can now create a file system on it using the newfs command: 

INODES=4096
newfs -i $INODES -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null
mount /dev/vn0c /mnt

The number of inodes that are created on the disk determines the maximum number of files that can be stored on the disk. The -i 4096 parameter specifies that we create one inode for each 32K bytes. One a 2048Kbyte file system, this would be 512 inodes, or a maximum of 512 files.

4.5 Initializing MFS Root File Systems

By using dd, vnconfig, disklabel, and newfs, we can create a file fs.PICOBSD whose contents are exactly the same as a copy of a real disk system. We can mount this device and then copy files to it: 

mkdir /mnt/etc
cp /etc/rc /mnt/etc/rc
cp /etc/init /mnt/etc/rc
...
umount /mnt
fsck -p /dev/rvn0c
vnconfig -u /dev/rvn0

At this point, we will have a file, fs.PICOBSD, whose contents are exactly the same a disk based file system, and which we could use as a root file system if it was on a physical device.

Now we do a really tricky thing: we are going to copy this file system image into the MFS area in the kernel. We find the string "MFS Filesystem goes here" in the kernel image, and we brutally copy the fs.PICOBSD file over top of it.

The write_mfs_in_kernel utility will do exactly this; see /usr/src/release/picobsd/tools/write_mfs_in_kernel for details. We use: 

write_mfs_in_kernel kernel fs.PICOBSD

If we were to load this kernel into memory and start it executing, it would examine the contents of the mfs_root, discover that it is a file system image, and then the MFS file system image as its root disk.

4.6 Compressing The Kernel

In the previous steps we outline how we would make a kernel with a MFS root file system, and how we would initialize the file system. However, there is a small problem with this kernel - it is extremely large. We have a least 2500 K bytes of initialized data (the MFS image).

We can get around this by compressing the kernel using (say) gzip (Lempel-Ziv algorithm), or the even more efficient bzip (block-sorting algorithm). One of the more pleasant things about these algorithms is that they compress long strings of zeros (0) with excellent efficiency. Here are some sample numbers 

Filesystem  1K-blocks     Used    Avail Capacity iused   ifree  %iused
/dev/vn0c        2387     1300     1087    54%     285     353    45%
                      Raw     Stripped    Compressed
Kernel (2500K MFS)  4102K     3840K       1258K
Kernel (3500K MFS)  5126K     4864K       1260K
As you can see, there is approximately a 2k increase in compressed kernel size for a 1000K increase in MFS size.

4.7 Build_kernel, Stage1, Populate, and Stage2 Scripts

The build script will first call the build_kernel script to build a kernel with the MFS and MFS_ROOT options and MFS_ROOT_SIZE set to the MFS file system size.

Next, the stage1 script generates the fs.PICOBSD file which will be used for the Memory File System. This is done using the commands: 

umount /dev/vn0 2> /dev/null || true
umount /mnt 2> /dev/null || true
vnconfig -u /dev/rvn0 2> /dev/null || true
#  generate a file of $SIZE K of zeros
dd of=fs.PICOBSD if=/dev/zero count=${SIZE} bs=1k 2> /dev/null
vnconfig -s labels -c /dev/rvn0 fs.PICOBSD 2>/dev/null
#  we autolabel this
disklabel -rw vn0 auto
n=
if [ -n "$INODES" ] ; then
        n="-i $INODES";
fi
newfs $n -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null
mount /dev/vn0c /mnt

We now have a file system mounted on /tmp which we will now fill with the files for the MFS. The populate will effectively generate a root file system by creating the /dev, /etc, /usr, /sbin, and other directories, creating the device files in /dev, and copying other files in place.

The populate script also generates a crunch executable, which is a single file that has the executables for a large number of commands. This reduces the number of duplicate statically linked executables that are needed for a small file system.

After the MFS is created and populated, the stage2 script will embed the MFS into the kernel, and strip and compress the kernel. 

umount /mnt 2>&1 >/dev/null
fsck -p /dev/rvn0c
vnconfig -u /dev/rvn0 2>&1 >/dev/null
if [ ! -f ../tools/write_mfs_in_kernel/wmik ]; then
        (cd ../tools/write_mfs_in_kernel; make)
fi
../tools/write_mfs_in_kernel/wmik kernel fs.PICOBSD
strip kernel
strip --remove-section=.note --remove-section=.comment kernel
gzip -9 -n -f kernel

First, we unmount the fs.PICOBSD file, and run fsck to ensure that it is in a consistent state and mark the file system as clean so the kernel will not try to run fsck during system startup. We also strip the kernel to remove symbol tables and contents. This reduces the kernel size substantially, but means that we will be unable to use some utilities that require a symbol table. We then use the write_mfs_in_kernel command to copy the MFS to the kernel, and then use gzip to compress the kernel.

We are now ready to put all of this onto a floppy disk. But first, let us review how we boot from a floppy disk.

4.8 Building the Boot Floppy with Stage3 Script

The stage3 we creates a floppy image file and then mounts it on /mnt using the following dd, vnconfig, newfs, and mount commands: 

umount /dev/vn0 2> /dev/null || true
umount /mnt 2> /dev/null || true
vnconfig -u /dev/rvn0 2> /dev/null || true
dd of=picobsd.bin if=/dev/zero count=1440 bs=1k 2> /dev/null
vnconfig -c /dev/rvn0 picobsd.bin 2>/dev/null
disklabel -Brw /dev/rvn0 fd1440 2>&1 >/dev/null
newfs -i 4096 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null
mount /dev/vn0c /mnt

The dd command creates a 1440Kbyte file which will be our floppy disk image. The vnconfig then attaches it to the /dev/rvn0 and /dev/vn0 VNODE device.

The disklabel command is where a lot of subtle things happen that are not explicity visible. The -B option causes the /boot/boot1 and /boot/boot2 files to be written to the floppy disk, and installed as boot blocks for the device. The fd1440 will cause the disk image to be labelled as a 1440K floppy disk. Finally, we mount the floppy image onto /mnt in preparation for copying files to it.

The inquisitive readers who examine the /boot directory will discover there is also a /boot/boot0 file. The /boot/boot0 is the boot file used on multi-system hard drives, and allows users to select which of multiple systems they wish to boot. This boot file is installed in the Master Boot Record (MBR) which is only available on drives that support a MSDOS partition structure, such as hard drives and some removable media (Zip) drives. Since we are using a floppy disk, we do not need to worry about boot0.

We copy the compressed kernel to the floppy image: 

cp kernel.gz /mnt/kernel.gz

At this point, you can copy the floppy image to an actual floppy disk and then mount the floppy using the following commands: 

# for writes to all devices including VNODE devices
sync
dd if=fs.PICOBSD of=/dev/rfd0
mkdir /tmp/mnt
mount /dev/fd0 /tmp/mnt
ls /tmp/mnt
The ls command will show that the floppy disk has the kernel.gz. If you feel adventurous, you can try to boot the floppy. If you do, you will be suprised to find that the boot code reports that it cannot find a /kernel file. Even if you rename the kernel.gz to kernel, then the boot code will still give an error.

What is happening? The boot1 and boot2 loaders expect to load reqular, non-compressed kernels into memory and execute them. They do not have any uncompression facilities as they are very small and simple.

One way to handle this is to use the kzip utility, which compresses a kernel, then adds code to uncompress the kernel and then jump to the kernel entry point.

Rather than use this, we will add a level3 bootstrap loader that not only is smart enough to not only uncompress the kernel, but also can pass in user specified configuration values and perform other configuration functions.

Here is the final boot sequence we will use:

  1. boot1 on floppy sector 0/0/1 loaded into memory and executed by BIOS
  2. boot2 on UNIX partition loaded into memory and executed by boot1 (uses /boot.config for information)
  3. /boot/loader loaded memory and executed by boot2 (uses /boot/loader.rc for information)
  4. /kernel.kz decompressed and loaded into memory, modified by /boot/loader, and executed. (uses /kernel.config for information)

The boot1 code (/boot/boot1) was placed on the first sector of the floppy by the disklabel program. It also labelled the disk and wrote the boot2 code (/boot/boot2) into a standard sector location. Boot1 has just enough code to load Boot2 using the PC BIOS facilities, and is limited to loading it from a standard location in a file system partition. Boot1 finds UNIX partition, copies boot2, to memory and then jumps to the boot2 entry point.

Boot2 is about 8Kbytes of code and data, and can read a Unix UFS file systems using BIOS calls. For details on its capabilities, see man boot for details. There are several hardwired files and configuration entries in boot4. Boot2 will examine the partition that it was loaded from and make sure it has a UNIX UFS file system or a file system it can manage. It will then try to open /boot.config, read a single line from the file, and interpret it in the same way as a user specified boot optons. It will then pause for a few seconds to allow a user to entry new or modified values by pressing a key during the boot process and entering them at the prompt.

The PICOBSD setup uses its capabilities by creating a /boot.config on the floppy disk image and initialing it with: 

/boot/loader
This will cause boot2 to find and load file /boot/loader into memory and execute it as a kernel.

What is this all about? The answer is simple: we want to be able to configure the devices and we need a loader that is smart enough to uncompress our kernel. The boot3 loader (just called loader now) has these and a tremendouse number of other capabilities, and it just a trifle large (131Kbytes). We use the kzip (kernel zip) facility to compress it and attach a bit of code to decompress and then run the compressed code, and then copy the compressed file to the /boot/loader file on the floppy: 

# we make a compressed loader mkdir /mnt/boot cp /boot/loader .
mkdir /mnt/boot
cp /boot/loader loader
kzip -v loader
mv loader.kz /mnt/boot/loader
rm -f loader loader.o
echo "/boot/loader" >/mnt/boot.config

The boot2 loader copies the file /boot/loader into memory now executes it. The /boot/loaderwill now uncompress itself and can read commands from the console or the following file (whose location is not very well documented in the man pages): 

/boot/loader.rc

(Aside: /boot/loader.rc used to be /boot/boot.conf in earlier FreeBSD releases, and this name is is pretty close to boot.config (see above). I wonder how many people this has confused?.)

If there is not file or there are no commands in the file then the /boot/loader will try to locate /kernel, /kernel.gz, /kernel.old, /kernel.gz.old, in turn and will load the first one found into memory and execute it.

The PICOBSD stage3 script initializes /boot/loader.rc on the floppy disk with the following commands: 

load /kernel
load -t userconfig_script /kernel.config
boot -P

If you are interested in the capabilities of loader, see /usr/src/boot/common/help.common or /boot/loader.help for a command summary.

Now let us see what happens when /boot/loader carries out the above commands. The load /kernel causes it to search for /kernel and /kernel.gz; it will find /kernel.gz and uncompress it as it is loaded into memory.

The load -t userconfig_script /kernel.config will cause the loader to copy the contents of /kernel.config into memory, and label it as the userconfig_script module. When the kernel is started, the userconfig module in the kernel (see /usr/src/sys/i386/i386/userconfig.c for the nastier details) will check to see if the userconfig_script module has been loaded, and will then read device configuration settings from it. The commands can have the form: 

  cmd     usage              example
  di      disable dev        di de0
  dr      drq dev #          dr 4
  ei      eisa # (EISA slots)ei 4
  en      enable dev         en ep0
  ex      exit (quit)        ex
  f       flags dev mask     f  de0 0xff
  h       help               h
  intro   intro screen       intro
  iom     iomem  dev addr    iom ed0 0xdf0000
  ios     iosize dev size    iosize ed0 0x1000
  ir      irq dev #          irq ed0 5
  l       ls, list           l
  pn      pnp (scan)         pnp
  po      port dev addr      port ed0 0x300
  res     reset CPU          res
  q       quit               q
  v       visual mode        v

If you generate a stock kernel for a large number of systems, you may discover that some systems have different hardware IO addresses than those in the kernel. The need for port (io) address and interrupt modification is used only with ISA and not with PCI bus cards.

The boot -P causes the /boot/loader to jump to the loaded kernel entry point, and pass it a -P (use serial console if no keyboard) flag. See man boot for details of the flags and their actions.

Finally, kernel execution is started. The kernel does its initialization, and the kernel userconfig kernel module is initialized. The userconfig_script value set by /boot/loader causes it to reads the /kernel.config file, and if we have generated our kernel with the INTRO_USERCONFIG option, the kernel will go into VISUAL userconfig operation.

To stop the loader from going into VISUAL userconfig operation, you must to modify the PICOBSD kernel configuration file. Comment out the following line: 

options         INTRO_USERCONFIG        #imply -c and parse
and regenerate the kernel.

Pleae be aware that the MFS in the kernel is not used until after the devices have been probed. Thus, the boot.config and kernel.config files will be read from the floppy disk file system.

Here are the commands from script3 used to set up the floppy disk for booting: 

mkdir /mnt/boot
cp /boot/loader .
kzip -v loader mv loader.kz /mnt/boot/loader rm -f loader loader.o
# set up the /boot.config file to cause boot2 to load /boot/loader
echo "/boot/loader" >/mnt/boot.config
# set up the /boot/loader.rc to cause the /boot/loader to
# load in the kernel and set options
cat  >/mnt/boot/loader.rc <<EOF
load /kernel
load -t userconfig_script /kernel.config
boot -P
EOF

4.9 Startup and Floppy Files

Once the kernel has been loaded into memory, and execution has started, it will run the first of /sbin/init, /sbin/oinit, /sbin/init.bak, /sbin/init.bak, or /stand/sysinstall that it finds on the root file system which is actually the MFS, due to the MFS_ROOT kernel configuration option. If the MFS file system contained all of the files that we would ever need, or we would not need to modify any configuration options, then we are finished with setting up our system.

On the other hand, we might discover that there are some configuration settings such as network IP addresses, hard drives to be mounted, or a /var MFS file system to be created and mounted. To allow our system to be easily configured, we will put a set of files on the floppy disk which are then copied to the MFS file system as part of the boot procedure. This is managed by following items in the PICOBSD installation.

  1. ${TYPE}/floppy.tree/*
    These files are copied to floppy disk during the PICOBSD installation process. The default is a boot.config and kernel.config to be used during the boot process, and a /etc directory containing files which will overwrite the MFS /etc files.
  2. ${TYPE}/lang/mfs.rc.${LANG}
    This file is copied to the MFS /etc/rc file, and will be executed as part of the system startup procedure.
Here is the contents of the net/lang/mfs.rc.en file: 
mount -o rdonly /dev/fd0a /start_floppy
cd /start_floppy/etc
cp -Rp . /etc/
cd /etc
pwd_mkdb -p ./master.passwd
umount /start_floppy
echo "Ok. (Now you may remove floppy if you like)"
echo ""
. rc
exit 0

Let us see what this does. First, it mounts the floppy disk on the /start_floppy directory, and then copies all the files in the floppy /etc directory to the MFS /etc directory. Then it unmounts the floppy and proceeds to execute the /etc/rc file again. This may appear to be an endless loop, but if we have an /etc/rc file on the floppy, this will overwrite the MFS /etc/rc file, and we will execute it instead of the MFS file.

The ${TYPE}/lang/rc.en file is copied to the floppy /etc/rc file during setup. Here is a sample to show the various things that can be done. 

#!/bin/sh
############################################
### Special setup for one floppy PICOBSD ###
### THIS IS NOT THE NORMAL /etc/rc !!!!! ###
############################################
if [ -f /etc/rc.conf ]; then
    . /etc/rc.conf
fi
mount -a -t nonfs
swapon -a
if [ "x$swapfile" != "xNO" -a -w "$swapfile" -a -b /dev/vn0b ]; then
        echo "Adding $swapfile as additional swap."
        vnconfig /dev/vn0b $swapfile && swapon /dev/vn0b
fi
rm -f /var/run/*
# configure serial devices
if [ -f /etc/rc.serial ]; then
        . /etc/rc.serial
fi
# start up the initial network configuration.
if [ -f /etc/rc.network ]; then
        . /etc/rc.network
        network_pass1
fi
mount -a -t nfs
chmod 666 /dev/tty[pqrsPQRS]*
#(cd /var/run && { cp /dev/null utmp; chmod 644 utmp; })
if [ -n "$network_pass1_done" ]; then
    network_pass2
fi
if [ -n "$network_pass2_done" ]; then
    network_pass3
fi
if [ "X${inetd_enable}" = X"YES" ]; then
        echo "Starting inetd."; inetd ${inetd_flags}
fi

#  make device database
dev_mkdb
exit 0

This looks a lot more like a regular rc startup file. However, this is very stripped down, and makes a lot of assumptions about the environment it is running in. First, the /etc/rc.conf file is read, and is used to set various options that are used in the script. The mount -a -t nonfs will mount all of the non-NFS files that are listed in the /etc/fstab file. If you have a CDROM or hard drive that you want to mount, you can add this the the /etc/fstab file. The swapon -a command will set any swap that is specified in /etc/fstab.

The next entry shows how you can set up a swap file using the VNODE file system. This is useful if the drive that you are mounting is a single partition and you do not want to have a swap partition. One example of this is when you have a MSDOS file system that you mount but still want to have a swap file. This is rather ugly and nasty, but in small systems which need to boot on multiple platforms can prove to be very useful.

The rm -f /var/run/* command is very standard and makes sure that there are no entries in the /var/run directory. If this is MFS, then there will not be any, but you might have mounted /var in a previous step, and this will clean it out.

After setting up swap, we proceed to start up networking and then mount any NFS file systems specified in /etc/fstab. Finally, we start up the various servers that we want to run on our system.

5. Multiple Boot Floppies

One of the problems that you will sooner or later encounter is that you simply cannot get all of your code onto a single floppy disk. The following sections outline some procedures you can use to solve this problem.

5.1 Boot and MFS Using Loader

One of the most common solutions is to have two or more floppies. The first one contains the kernel and a very small amount of glue files, while the other contains the actual MFS file system. If you check the /boot/loader.help file in the FreeBSD 3.1-RELEASE, you will discover the following interesting commands: 

echo [-n] [<message>]

  Emits <message>, with no trailing newline if -n is specified.  This
  is most useful in conjunction with scripts and the '@' line prefix.
  Variables are substituted by prefixing them with $, eg.
    echo Current device is $currdev
  will print the current device.

read [-t <value>] [-p <prompt>] [<variable name>]
  The read command reads a line of input from the terminal.  If the
  -t argument is specified, it will return nothing if no input has
  been received after <value> seconds.  (Any keypress will cancel
  the timeout).
  
  If -p is specified, <prompt> is printed before reading input. No
  newline is emitted after the prompt.
  
  If a variable name is supplied, the variable is set to the value
  read, less any terminating newline.

load [-t <type>] <filename>
  Loads the module contained in <filename> into memory.  If no other
  modules are loaded, <filename> must be a kernel or the command will
  fail.
  
  If -t is specified, the module is loaded as raw data of <type>, for
  later use by the kernel or other modules.  <type> may be any string.

Now suppose that we were to place the following commands into the /boot/loader.rc file: 

load /kernel
echo Please insert MFS root floppy and press enter:
read
load -t mfs_root /mfsroot
boot

The load command will cause the loader to load (and uncompress) the /kernel or /kernel.gz file. The echo and read print a line on the console and then wait for the user to put a new floppy in the floppy drive. The load -t mfs_root /mfsroot command is very interesting. It will cause the loader to copy the contents of the file /mfsroot into the kernel module mfs_root. The mfs_root is where the kernel expects to find the MFS image.

Thus, we can simply put our MFS file system onto a floppy disk in the file /mfsroot and we can now load this.

A basic limitation of this method is that your MFS must fit in a single file, and cannot be compressed. However, as we will see in the next section, we can easily get around this problem.

5.2 Boot and Compressed MFS

As we saw in previous sections, the root file system must contain an init program which is the first process started by the kernel. We can use the process to perform the following actions:

  1. start a shell script which will
    1. ask the user to mount a floppy NNN
    2. mount the floppy
    3. check to see that there is a file, say FNNN, on the floppy. This will contain compressed files.
    4. Uncompress the file FNNN from the floppy
    5. After all the files have been extracted from the floppy, runs a cleanup script that would change permissions, create database files, or concatenate files that needed to be split to put them on a floppy.
  2. runs the /etc/rc script

This is simply an adaptation of a common method used to distributes software on floppy disk media.

5.3 Boot and CDROM

If you have a CDROM reader on your system, then it is possible to simply mount a CDROM and extract the files from the CDROM. However, these files are still placed in memory and on systems with limited amounts of memory and large numbers of files needed this may not be desireable.

The union file system mount facility can be used to solve this problem. A union mount allows you to overlay two directory structures. For example, suppose that I had directory /my/usr which contained a set of files that I wanted to use in place of the standard /usr files. Due to hardwired paths in various systems utilities, I could simply not change a PATH environment variable. I would normally be forced to copy all of the files from /my/usr to /usr, and then copy the originals back in place. This can be very time consuming and is fraught with danger, especially if extra files are left in place. The mount -b option will invert the search order, so that the original file system is search first, then the union mount.

Consider the following mount command: 

mount -t union /my/usr /usr
The /usr is the common or uniondir. The mount command causes the /my/usr directory to appear at /usr; when a file is searched for, the /my/usr directory contents are searched first, and if the file is not found then the original /usr is searched.

Now suppose that we have a CDROM that has all of the files that we would like to use. We can mount the cdrom and then union mount it as follows: 

mount -t cd9660 /dev/wcd0a /mnt_cd
mount -t union /mnt_cd /
Now when we access a file, we will get the file from the CDROM first.

One of the problems with this method is that every time we search for a directory, then a shadow directory is created in the original MFS file system as well. We can rapidly run out of INODES unless we are careful, as our MFS file system is usually pretty small due to space limitations of the kernel. A way around this is to simply create a true Memory File System and mount this. We then can mount and copy files to this MFS file system. This is most effectively done during the /etc/rc initialization. 

# /etc/rc
mount -t cd9660 /dev/wcd0 /cdrom
# allow 1024 blocks of 512 bytes or 512K, lots of inodes for shadowing
mount_mfs -i 2048 -s 1024 -T /dev/null /usr
# allow 102400 blocks of 512 bytes or 51200K
mount_mfs -s 102400 -T /dev/null /var
# want to have /usr writable so we reverse order
mount -b -t union /cdrom/usr /usr

The good news is that this is an excellent way to provide small MFS based systesm. The bad news is that as of FreeBSD 3.1-RELEASE, the union file system has severe problems and is not yet fully supported.

Last modified: Fri Apr 30 18:14:55 PDT 1999 by Patrick Powell
Generated: @DATE@

<papowell@astart.com>

<abial@freebsd.org>

--------------EBAC1F2D12499441013FE952-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun May 2 3:23: 9 1999 Delivered-To: freebsd-small@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 5EF7214E21; Sun, 2 May 1999 03:23:00 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id MAA22201; Sun, 2 May 1999 12:22:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id MAA02756; Sun, 2 May 1999 12:22:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Date: Sun, 02 May 1999 12:22:59 +0200 Message-ID: <2754.925640579.1@critter.freebsd.dk> From: Poul-Henning Kamp Subject: FreeBSD interrupt responsetime... MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message Subject: FreeBSD interrupt responsetime... From: Poul-Henning Kamp Date: Sun, 02 May 1999 12:22:59 +0200 Message-ID: <2754.925640579@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Bcc: Blind Distribution List: ; MIME-Version: 1.0 A company asked me for data on interrupt response times in FreeBSD and I've done a setup in my lab to measure it. I have completed the first half of the task: characterising the jitter on the response time, and the data are presented for all to see here. The second half of the task is more tricky: measuring the delay from the external stimuli until we execute the first statement in the interrupt handler, but if I can crack that nut data will be forthcoming on that as well. These data are for the ppsdriver, using a FAST_INTR, running in single user mode with no other programs, and only a tickle of data stored to the disk from the measuring program. The input event rate was 1Hz. Total samples: 86664 Standard Deviation: 250 nsec Average: 0 (dataset centered on mean) Median: -30.1 nsec Min: -763 nsec Max: 2936 nsec first column: the percentage of samples second column: +/- span around the median in nsec third column: +/- span around the mean in nsec In other words, 50 percent of the samples were inside a band of +/- 137 nsec of the mean of all the samples. 10 23 24 20 48 49 30 74 75 40 102 104 50 132 137 60 168 174 70 208 217 75 233 242 80 261 271 90 356 358 95 474 456 97.5 636 606 98 693 663 98.5 763 733 99 864 834 99.25 992 962 99.5 1215 1184 99.75 1215 1436 99.9 1642 1612 99.95 1741 1711 99.99 2040 2009 100 2966 2936 -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun May 2 7: 5: 5 1999 Delivered-To: freebsd-small@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id EC52715327; Sun, 2 May 1999 07:04:57 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id KAA57867; Sun, 2 May 1999 10:04:57 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <199905021404.KAA57867@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp From: "Louis A. Mamakos" Subject: Re: FreeBSD interrupt responsetime... References: <2754.925640579.1@critter.freebsd.dk> In-reply-to: Your message of "Sun, 02 May 1999 12:22:59 +0200." <2754.925640579.1@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 May 1999 10:04:57 -0400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And for something completely different, I've got some data measured a bit differently. This is with a 1-Hz periodic interrupt source, multi-user mode, with a "normal" vs. FAST_INTR service routine. This is a dump of the buckets kept in the device driver of number of times that the interrupt service latency was between the intervals listed. 5us <= 250831 < 6us 6us <= 751473 < 7us 7us <= 67305 < 8us 8us <= 5032 < 9us 9us <= 1467 < 10us 10us <= 877 < 11us 11us <= 518 < 12us 12us <= 369 < 13us 13us <= 165 < 14us 14us <= 112 < 15us 15us <= 469 < 16us 16us <= 199 < 17us 17us <= 18 < 18us 18us <= 9 < 19us 19us <= 5 < 20us 20us <= 12 < 22us 22us <= 12 < 24us 24us <= 5 < 28us 32us <= 1 < 35us 50us <= 1 < 75us 100us <= 2 < 250us The hardware configuration is a 233MHz Pentium MMX based Motorola CPV5000 CompactPCI system board, with a Datum bc635CPCI time and frequency processor board. The PCI bus this is connected to is one bridge away from the CPU and is the normal 32 bit wide, 33MHz variety. This system's got an fxp0 ethernet and adaptec SCSI on board. This system was far from idle when this data was collected, with substantial network and disk activity during some periods. (For detail on the hardware, see: http://www.mcg.mot.com/WebOS/omf/GSS/MCG/prod ucts/proddb/templates/display_datasheet.html?[qrec=0000412+[prodid=CPV5000 http://www.bancomm.com/cbc637cpci.htm ) I program the bc635 to generate an interrupt once each second, at about 500ms past the start of the second. When the interrupt service routine is invoked, I read the current time out of the board and see how long it took. I'm more concerned at this point about the varience in response, rather than the absolute latency; though I would like to improve that. I've been thinking about ways to instrument to low-level interrupt service code to capture a timestamp and save it away somewhere prior to the splX() interrupt scheduling. Sounds like it would be worth trying to re-do this with a FAST_INTR service routine to see how much of a difference that would make. I'm using a -current from early March as the basis of this work, and haven't tried to merge any of the subsequent changes (newbus, etc.) until that's well settled down. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun May 2 10:16:41 1999 Delivered-To: freebsd-small@freebsd.org Received: from ns1.tu-graz.ac.at (ns1.tu-graz.ac.at [129.27.2.3]) by hub.freebsd.org (Postfix) with ESMTP id 1015E1542D for ; Sun, 2 May 1999 10:16:30 -0700 (PDT) (envelope-from mbretter@sbox.tu-graz.ac.at) Received: from babsi.tu-graz.ac.at (teleweb-17.vc-graz.ac.at [193.171.247.17]) by ns1.tu-graz.ac.at (8.8.6/8.8.6) with SMTP id TAA02232 for ; Sun, 2 May 1999 19:16:26 +0200 (MET DST) From: Michael Bretterklieber To: freebsd-small@FreeBSD.ORG Subject: Re: Bridging under PicoBSD compiled w/ 3.1-RELEASE Date: Sun, 2 May 1999 19:14:48 +0200 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <372B191E.7897DAE4@cronosnet.com> MIME-Version: 1.0 Message-Id: <99050219191800.00340@babsi.tu-graz.ac.at> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Am Sa , 01 Mai 1999 schrieb Vittorio Mori: > I have a problem with the > > options BRIDGE > > in the PicoBSD package ... > > Simply, the bridge doesn't work ;( > I have a version that works, but at the beginning I had many problems with bridging and dummynet in 3.1 Release, so you have to upgrade some source-files via CVS. bridge.c if_ed.c ip_dummynet.c ip_fw.c Bye, -- \|/ @ @ +---------------------------oOO-(_)-OOo---------------------------+ Michael Bretterklieber Office: Michael.Bretterklieber@gamed.com Privat: mbretter@sbox.tu-graz.ac.at URL: http://www.sbox.tu-graz.ac.at/home/m/mbretter/ +-----------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon May 3 11: 9: 0 1999 Delivered-To: freebsd-small@freebsd.org Received: from hecke.math.rochester.edu (hecke.math.rochester.edu [128.151.122.27]) by hub.freebsd.org (Postfix) with ESMTP id 1910B14CA7 for ; Mon, 3 May 1999 11:08:45 -0700 (PDT) (envelope-from hfir@math.rochester.edu) Received: from hecke.math.rochester.edu (hecke.math.rochester.edu [128.151.122.27]) by hecke.math.rochester.edu (8.9.2/8.9.1) with ESMTP id OAA28067 for ; Mon, 3 May 1999 14:05:05 -0400 (EDT) (envelope-from hfir@math.rochester.edu) Date: Mon, 3 May 1999 14:05:05 -0400 (EDT) From: Hoss Firooznia To: freebsd-small@FreeBSD.ORG Subject: PicoBSD boot error: can't load kernel 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 folks, I've happily been experimenting with PicoBSD for several months now, modifying the 'net' configuration, making custom configurations, etc., all without problems. Recently, however, I'm encountering odd boot errors that I can't seem to track down. I CVSup'ed the latest 3.1-STABLE sources and ran the 'build' script as per the instructions; everything compiles and crunches correctly, picobsd.bin is written to floppy... but when I then try to boot the floppy I consistently get the following error: Loading kernel. Please wait... /kernel text=0xc379c elf_loadexec: archsw.readin failed can't load 'kernel' Error booting This happens with both a modified 'net' configuration as well as with the stock 'router' configuration. The boot blocks and boot loader seem to work as usual (I get the usual loader messages, the BootFORTH menu, etc.) but the boot loader apparently can't read in the kernel properly. I've tried multiple machines and multiple disks, but the problem remains - so presumably this isn't simply a hardware read error. Does the problem sound familiar to anyone? Am I (most likely) missing something obvious? Thanks! - Hoss -- Hoss Firooznia, UNIX SA, Department of Mathematics, University of Rochester PGP public key: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon May 3 13:47:54 1999 Delivered-To: freebsd-small@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id A037014C1C for ; Mon, 3 May 1999 13:47:50 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 01CED18D0; Mon, 3 May 1999 22:48:15 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 00EF449DA; Mon, 3 May 1999 22:48:15 +0200 (CEST) Date: Mon, 3 May 1999 22:48:14 +0200 (CEST) From: Andrzej Bialecki To: Hoss Firooznia Cc: freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD boot error: can't load kernel In-Reply-To: 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 May 1999, Hoss Firooznia wrote: > Hi folks, > > > Loading kernel. Please wait... > /kernel text=0xc379c > elf_loadexec: archsw.readin failed > can't load 'kernel' > Error booting > > This happens with both a modified 'net' configuration as well as with the > stock 'router' configuration. The boot blocks and boot loader seem to work > as usual (I get the usual loader messages, the BootFORTH menu, etc.) but > the boot loader apparently can't read in the kernel properly. > > I've tried multiple machines and multiple disks, but the problem remains - > so presumably this isn't simply a hardware read error. Does the problem > sound familiar to anyone? Am I (most likely) missing something obvious? Well, it looks familiar to me - more or less it means "I can't read this sector from the media, help!", and I usually was able to get rid of it with a new floppy... but in your case, if you already tried it, well... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon May 3 13:54:56 1999 Delivered-To: freebsd-small@freebsd.org Received: from hecke.math.rochester.edu (hecke.math.rochester.edu [128.151.122.27]) by hub.freebsd.org (Postfix) with ESMTP id 14C6C14EE9 for ; Mon, 3 May 1999 13:54:52 -0700 (PDT) (envelope-from hfir@math.rochester.edu) Received: from germain.math.rochester.edu (germain.math.rochester.edu [128.151.122.36]) by hecke.math.rochester.edu (8.9.2/8.9.1) with ESMTP id QAA29966; Mon, 3 May 1999 16:51:12 -0400 (EDT) (envelope-from hfir@math.rochester.edu) Date: Mon, 3 May 1999 16:51:12 -0400 (EDT) From: Hoss Firooznia To: Andrzej Bialecki Cc: freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD boot error: can't load kernel In-Reply-To: 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 May 1999, Andrzej Bialecki wrote: > > Loading kernel. Please wait... > > /kernel text=0xc379c > > elf_loadexec: archsw.readin failed > > can't load 'kernel' > > Error booting > > Well, it looks familiar to me - more or less it means "I can't read this > sector from the media, help!", and I usually was able to get rid of it > with a new floppy... but in your case, if you already tried it, well... Okay, this encouraging. I guess I've just had a string of bad floppies; I'll have to get some fresh ones and try again. Thanks very much for the help. :-) - Hoss To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon May 3 14: 0:17 1999 Delivered-To: freebsd-small@freebsd.org Received: from beowulf.utmb.edu (beowulf.utmb.edu [129.109.59.83]) by hub.freebsd.org (Postfix) with ESMTP id 832AF14EE9 for ; Mon, 3 May 1999 14:00:08 -0700 (PDT) (envelope-from bdodson@beowulf.utmb.edu) Received: (from bdodson@localhost) by beowulf.utmb.edu (8.9.2/8.9.2) id PAA00419; Mon, 3 May 1999 15:58:04 -0500 (CDT) (envelope-from bdodson) Date: Mon, 3 May 1999 15:58:04 -0500 (CDT) Message-Id: <199905032058.PAA00419@beowulf.utmb.edu> From: "M. L. Dodson" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andrzej Bialecki Cc: Hoss Firooznia , freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD boot error: can't load kernel In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki writes: > On Mon, 3 May 1999, Hoss Firooznia wrote: > > > Hi folks, > > > > > > Loading kernel. Please wait... > > /kernel text=0xc379c > > elf_loadexec: archsw.readin failed > > can't load 'kernel' > > Error booting > > > > This happens with both a modified 'net' configuration as well as with the > > stock 'router' configuration. The boot blocks and boot loader seem to work > > as usual (I get the usual loader messages, the BootFORTH menu, etc.) but > > the boot loader apparently can't read in the kernel properly. > > > > I've tried multiple machines and multiple disks, but the problem remains - > > so presumably this isn't simply a hardware read error. Does the problem > > sound familiar to anyone? Am I (most likely) missing something obvious? > > Well, it looks familiar to me - more or less it means "I can't read this > sector from the media, help!", and I usually was able to get rid of it > with a new floppy... but in your case, if you already tried it, well... > > Andrzej Bialecki Hmmmm.... I get that message when multibooting regular FreeBSD (3.1-stable kernel, but 3.1-release bootblocks) and NT, using the NT boot loader to load our /boot/loader sequence. Works fine when /boot.config contains 1:da(0,a)/kernel so there is nothing wrong with the kernel. I suspect a mismatch somewhere between the 3.1-release boot stuff (specifically, /boot/loader) and the 3.1-stable kernel, but I haven't gotten around to a make world and installation of new bootblocks. You might try cvsupping the 3.1-stable boot hierarchy, and using the new boot blocks on the floppy. (Although I don't know what that would do to your regular system disk.) A full make world might work better. There are hints of this kind of problem in the stable mailing list archives, I think. Bud Dodson > > // WebGiro AB, Sweden (http://www.webgiro.com) > // ------------------------------------------------------------------- > // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message -- M. L. Dodson bdodson@scms.utmb.edu 409-772-2178 FAX: 409-772-1790 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon May 3 14: 1:19 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 2277C14EE9 for ; Mon, 3 May 1999 14:01:16 -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 PAA07128 for ; Mon, 3 May 1999 15:00:35 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: (from imp@localhost) by harmony.village.org (8.9.3/8.8.3) id PAA52290 for freebsd-small@FreeBSD.ORG; Mon, 3 May 1999 15:01:48 -0600 (MDT) Date: Mon, 3 May 1999 15:01:48 -0600 (MDT) From: Warner Losh Message-Id: <199905032101.PAA52290@harmony.village.org> To: freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD boot error: can't load kernel Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Okay, this encouraging. I guess I've just had a string of bad floppies; I have about 50 or 60 of the goofy things laying around. For important data, I make two copies. For disks that have even one error, I round file them and try again with another disk. I had about 150 when I started this policy... At this rate I may need to buy disks for the first time in years :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon May 3 14:12: 3 1999 Delivered-To: freebsd-small@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 1E0941535F for ; Mon, 3 May 1999 14:11:57 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id B059C18D0; Mon, 3 May 1999 23:12:25 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id AF55449DA; Mon, 3 May 1999 23:12:25 +0200 (CEST) Date: Mon, 3 May 1999 23:12:25 +0200 (CEST) From: Andrzej Bialecki To: "M. L. Dodson" Cc: Hoss Firooznia , freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD boot error: can't load kernel In-Reply-To: <199905032058.PAA00419@beowulf.utmb.edu> 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 May 1999, M. L. Dodson wrote: > Andrzej Bialecki writes: > > On Mon, 3 May 1999, Hoss Firooznia wrote: > > > > > Hi folks, > > > > > > > > > Loading kernel. Please wait... > > > /kernel text=0xc379c > > > elf_loadexec: archsw.readin failed > > > can't load 'kernel' > > > Error booting > > > > > > This happens with both a modified 'net' configuration as well as with the > > > stock 'router' configuration. The boot blocks and boot loader seem to work > > > as usual (I get the usual loader messages, the BootFORTH menu, etc.) but > > > the boot loader apparently can't read in the kernel properly. > > > > > > I've tried multiple machines and multiple disks, but the problem remains - > > > so presumably this isn't simply a hardware read error. Does the problem > > > sound familiar to anyone? Am I (most likely) missing something obvious? > > > > Well, it looks familiar to me - more or less it means "I can't read this > > sector from the media, help!", and I usually was able to get rid of it > > with a new floppy... but in your case, if you already tried it, well... > > > > Andrzej Bialecki > > Hmmmm.... I get that message when multibooting regular FreeBSD > (3.1-stable kernel, but 3.1-release bootblocks) and NT, > using the NT boot loader to load our /boot/loader sequence. > Works fine when /boot.config contains > > 1:da(0,a)/kernel > > so there is nothing wrong with the kernel. I suspect a mismatch > somewhere between the 3.1-release boot stuff (specifically, > /boot/loader) and the 3.1-stable kernel, but I haven't gotten > around to a make world and installation of new bootblocks. You Hmm... Could be also some problem with geometry perhaps.. it's a wild guess, but who knows.. you usually don't have problems with figuring out the geometry of a floppy, whereas with HDDs it's a different story. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon May 3 14:15:56 1999 Delivered-To: freebsd-small@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 73FF814C2B for ; Mon, 3 May 1999 14:15:53 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 6D8AC18D0; Mon, 3 May 1999 23:16:18 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 6A83649DA; Mon, 3 May 1999 23:16:18 +0200 (CEST) Date: Mon, 3 May 1999 23:16:18 +0200 (CEST) From: Andrzej Bialecki To: Warner Losh Cc: freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD boot error: can't load kernel In-Reply-To: <199905032101.PAA52290@harmony.village.org> 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 May 1999, Warner Losh wrote: > : Okay, this encouraging. I guess I've just had a string of bad floppies; > > I have about 50 or 60 of the goofy things laying around. For important data, > I make two copies. For disks that have even one error, I round file them and > try again with another disk. I had about 150 when I started this policy... > At this rate I may need to buy disks for the first time in years :-) OTOH, I suspect we still have some problem with our fd driver.. The same floppies work for me under windows, and the argument "well, it's windows - you never know" is moot, because the _data_ on them is still readable and in good shape... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue May 4 13:31:23 1999 Delivered-To: freebsd-small@freebsd.org Received: from beowulf.utmb.edu (beowulf.utmb.edu [129.109.59.83]) by hub.freebsd.org (Postfix) with ESMTP id 2944E14E84 for ; Tue, 4 May 1999 13:31:11 -0700 (PDT) (envelope-from bdodson@beowulf.utmb.edu) Received: (from bdodson@localhost) by beowulf.utmb.edu (8.9.3/8.9.2) id PAA00309; Tue, 4 May 1999 15:28:58 -0500 (CDT) (envelope-from bdodson) Date: Tue, 4 May 1999 15:28:58 -0500 (CDT) Message-Id: <199905042028.PAA00309@beowulf.utmb.edu> From: "M. L. Dodson" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andrzej Bialecki Cc: "M. L. Dodson" , Hoss Firooznia , freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD boot error: can't load kernel In-Reply-To: References: <199905032058.PAA00419@beowulf.utmb.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki writes: > On Mon, 3 May 1999, M. L. Dodson wrote: > > > Andrzej Bialecki writes: > > > On Mon, 3 May 1999, Hoss Firooznia wrote: > > > > > > > Hi folks, > > > > > > > > > > > > Loading kernel. Please wait... > > > > /kernel text=0xc379c > > > > elf_loadexec: archsw.readin failed > > > > can't load 'kernel' > > > > Error booting > > > > > > > > This happens with both a modified 'net' configuration as well as with the > > > > stock 'router' configuration. The boot blocks and boot loader seem to work > > > > as usual (I get the usual loader messages, the BootFORTH menu, etc.) but > > > > the boot loader apparently can't read in the kernel properly. > > > > > > > > I've tried multiple machines and multiple disks, but the problem remains - > > > > so presumably this isn't simply a hardware read error. Does the problem > > > > sound familiar to anyone? Am I (most likely) missing something obvious? > > > > > > Well, it looks familiar to me - more or less it means "I can't read this > > > sector from the media, help!", and I usually was able to get rid of it > > > with a new floppy... but in your case, if you already tried it, well... > > > > > > Andrzej Bialecki > > > > Hmmmm.... I get that message when multibooting regular FreeBSD > > (3.1-stable kernel, but 3.1-release bootblocks) and NT, > > using the NT boot loader to load our /boot/loader sequence. > > Works fine when /boot.config contains > > > > 1:da(0,a)/kernel > > > > so there is nothing wrong with the kernel. I suspect a mismatch > > somewhere between the 3.1-release boot stuff (specifically, > > /boot/loader) and the 3.1-stable kernel, but I haven't gotten > > around to a make world and installation of new bootblocks. You > > Hmm... Could be also some problem with geometry perhaps.. it's a wild > guess, but who knows.. you usually don't have problems with figuring out > the geometry of a floppy, whereas with HDDs it's a different > story. A make world and reboot solved my multiboot problems. So, Hoss, if you have the situation I had: a 3.1-RELEASE boot chain, but your /usr/src tree was -STABLE, you might suspect the same problem I had. I know that the problem that I had was also reproduced using a dedicated boot floppy with 3.1-RELEASE boot chain and 3.1-STABLE kernel.gz, so I don't think is was (directly, in any case) specific to a hard disk geometry problem. Good luck. Bud Dodson > > Andrzej Bialecki > > // WebGiro AB, Sweden (http://www.webgiro.com) > // ------------------------------------------------------------------- > // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- > -- M. L. Dodson bdodson@scms.utmb.edu 409-772-2178 FAX: 409-772-1790 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue May 4 21:41:41 1999 Delivered-To: freebsd-small@freebsd.org Received: from hecke.math.rochester.edu (hecke.math.rochester.edu [128.151.122.27]) by hub.freebsd.org (Postfix) with ESMTP id 2831614FBF for ; Tue, 4 May 1999 21:41:36 -0700 (PDT) (envelope-from hfir@math.rochester.edu) Received: from hecke.math.rochester.edu (hecke.math.rochester.edu [128.151.122.27]) by hecke.math.rochester.edu (8.9.2/8.9.1) with ESMTP id AAA45361; Wed, 5 May 1999 00:37:21 -0400 (EDT) (envelope-from hfir@math.rochester.edu) Date: Wed, 5 May 1999 00:37:21 -0400 (EDT) From: Hoss Firooznia To: "M. L. Dodson" Cc: Andrzej Bialecki , freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD boot error: can't load kernel In-Reply-To: <199905042028.PAA00309@beowulf.utmb.edu> 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 Tue, 4 May 1999, M. L. Dodson wrote: > A make world and reboot solved my multiboot problems. So, Hoss, > if you have the situation I had: a 3.1-RELEASE boot chain, but > your /usr/src tree was -STABLE, you might suspect the same > problem I had. Yes! This diagnosis was right on target, Bud, thank you. :-) I actually wound up identifying the boot loader as a culprit after installing a recent -STABLE kernel on the PicoBSD build box and finding that I couldn't boot that kernel, either... doh! Though I may have complicated matters by making a new boot loader a few days back in an attempt to solve an earlier problem: I had reverted to 3.1-RELEASE sources in the hopes of avoiding what I (mistakenly) thought was a problem with -STABLE, after which I manually reinstalled the older -RELEASE boot loader. In any case, reinstalling the loader from -STABLE sources in /usr/src/sys/boot did the trick. Andrzej, I notice that the stage3 build script is getting the floppy's loader from /boot/loader (if I'm reading the script correctly). What do you think about changing it to build from source rather than relying on the installed version? Thanks again to all for the valuable help! - Hoss To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu May 6 8:11: 0 1999 Delivered-To: freebsd-small@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id BA8D914CBF for ; Thu, 6 May 1999 08:10:56 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA13820; Fri, 7 May 1999 00:10:23 +0900 (JST) Message-ID: <3731B055.F4F9C974@newsguy.com> Date: Fri, 07 May 1999 00:08:06 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Hoss Firooznia Cc: "M. L. Dodson" , Andrzej Bialecki , freebsd-small@FreeBSD.ORG, Mike Smith Subject: Re: PicoBSD boot error: can't load kernel References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I could have avoided a lot of pain if I were reading my mail... :-) Just to confirm and make it clear to everyone, if the error message says "elf_loadexec: archsw.readin failed", then it's a signal that loader and kernel are mismatched, no doubt about it. Alas, we can track what loader can boot what kernel, but we have no way of verifying this. Maybe I ought to talk to Mike about putting in /kernel an identifier of the lowest loader version that can boot it. Hoss Firooznia wrote: > > On Tue, 4 May 1999, M. L. Dodson wrote: > > > A make world and reboot solved my multiboot problems. So, Hoss, > > if you have the situation I had: a 3.1-RELEASE boot chain, but > > your /usr/src tree was -STABLE, you might suspect the same > > problem I had. > > Yes! This diagnosis was right on target, Bud, thank you. :-) > > I actually wound up identifying the boot loader as a culprit after > installing a recent -STABLE kernel on the PicoBSD build box and finding > that I couldn't boot that kernel, either... doh! Though I may have > complicated matters by making a new boot loader a few days back in an > attempt to solve an earlier problem: I had reverted to 3.1-RELEASE sources > in the hopes of avoiding what I (mistakenly) thought was a problem with > -STABLE, after which I manually reinstalled the older -RELEASE boot loader. > > In any case, reinstalling the loader from -STABLE sources in > /usr/src/sys/boot did the trick. Andrzej, I notice that the stage3 > build script is getting the floppy's loader from /boot/loader (if I'm > reading the script correctly). What do you think about changing it > to build from source rather than relying on the installed version? > > Thanks again to all for the valuable help! > > - Hoss > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness if that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu May 6 14:16:32 1999 Delivered-To: freebsd-small@freebsd.org Received: from gta.com (mailgate.gta.com [199.120.225.4]) by hub.freebsd.org (Postfix) with ESMTP id C890615250 for ; Thu, 6 May 1999 14:16:25 -0700 (PDT) (envelope-from lab@gta.com) Received: from gta.com (GTA internal mail system) by gta.com with ESMTP id RAA21319 for ; Thu, 6 May 1999 17:16:40 -0400 (EDT) Message-ID: <37320638.FB5D8844@gta.com> Date: Thu, 06 May 1999 17:14:33 -0400 From: Larry Baird X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 3.1-STABLE i386) MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: 4MB DiskOnChip Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone had any luck booting from a 4MB diskOnChip using FreeBSD 3.1.0? I can boot just fine from a 2MB model. I get the following error from boot2 when it tries to load loader: Disk error 0x1 (lba=0x1af0) If I revert back to the 2.2.8 boot2 file I get: 1724 > 1023 (BIOS limit) Chasing thru the code it would appear that when boot1 uses int13 to read the drive parameters from bios, they are somehow incorrect. I just need to figure out how to get some I/O out of this assembly code to prove this theory. Thanks in advance, Larry -- ----------------------------------------------------------------------------- Larry Baird Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | TEL 407-380-0220, FAX 407-380-6080 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat May 8 8: 1:42 1999 Delivered-To: freebsd-small@freebsd.org Received: from ns1.tu-graz.ac.at (ns1.tu-graz.ac.at [129.27.2.3]) by hub.freebsd.org (Postfix) with ESMTP id 27187155E3 for ; Sat, 8 May 1999 08:01:37 -0700 (PDT) (envelope-from mbretter@sbox.tu-graz.ac.at) Received: from babsi.tu-graz.ac.at (teleweb-17.vc-graz.ac.at [193.171.247.17]) by ns1.tu-graz.ac.at (8.8.6/8.8.6) with SMTP id RAA01691 for ; Sat, 8 May 1999 17:01:35 +0200 (MET DST) From: Michael Bretterklieber To: freebsd-small@FreeBSD.ORG Subject: Re: 4MB DiskOnChip Date: Sat, 8 May 1999 16:59:14 +0200 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <37320638.FB5D8844@gta.com> MIME-Version: 1.0 Message-Id: <99050817043500.00291@babsi.tu-graz.ac.at> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Am Do , 06 Mai 1999 schrieb Larry Baird: > Has anyone had any luck booting from a 4MB diskOnChip using FreeBSD > 3.1.0? > Yes, It works fine. > I can boot just fine from a 2MB model. > > I get the following error from boot2 when it tries to load loader: > Disk error 0x1 (lba=0x1af0) > > If I revert back to the 2.2.8 boot2 file I get: > 1724 > 1023 (BIOS limit) > > Chasing thru the code it would appear that when boot1 uses int13 to read > > the drive parameters from bios, they are somehow incorrect. I just > need > to figure out how to get some I/O out of this assembly code to prove > this > theory. > I use the bootloader from 3.1-RELEASE. I prepared the DOC2k disk with this script #!/bin/sh dd if=/dev/zero of=/dev/rfla0 count=64 fdisk -v -f doc2k4.conf -i fla0 disklabel -w -r fla0 auto disklabel -B -b /boot/boot1 -s /boot/boot2 fla0 newfs /dev/fla0s1c and doc2k4.conf: p 1 165 0 7888 a 1 Bye, -- \|/ @ @ +---------------------------oOO-(_)-OOo---------------------------+ Michael Bretterklieber Office: Michael.Bretterklieber@gamed.com Privat: mbretter@sbox.tu-graz.ac.at URL: http://www.sbox.tu-graz.ac.at/home/m/mbretter/ +-----------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message