From owner-freebsd-small Sun Mar 11 8:39:21 2001 Delivered-To: freebsd-small@freebsd.org Received: from onyx.extra.dp.ua (onyx.extrasy.net [195.248.182.33]) by hub.freebsd.org (Postfix) with ESMTP id 812C137B719 for ; Sun, 11 Mar 2001 08:38:22 -0800 (PST) (envelope-from white@onyx.extra.dp.ua) Received: (from white@localhost) by onyx.extra.dp.ua (8.10.0/8.10.0/Who.Cares) id f2BGcF808560 for small@freebsd.org; Sun, 11 Mar 2001 18:38:15 +0200 (EET) Date: Sun, 11 Mar 2001 18:38:15 +0200 From: Alexander Prohorenko To: small@freebsd.org Subject: SanDisk Message-ID: <20010311183815.C6933@extrasy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.9i Organization: Extra Solutions X-Operating-System: SunOS 5.7 i86pc Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello guys, I've got this one: ad2: 30MB [490/4/32] at ata1-master BIOSPIO I can mount like this: /dev/ad2s1 on /flash (ufs, local) What's the best way to use it as floppy, I mean - is there any good way to use this device instead of floppy, and to put Pico image there using the existing scripts/code? -- Alexander Prohorenko, Extra Solutions http://www.extrasy.net/solutions "Good day to be alive, sir" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Mar 11 9: 8:38 2001 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 17A5437B719 for ; Sun, 11 Mar 2001 09:08:36 -0800 (PST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.2/8.11.0) with ESMTP id f2BH8YX60143; Sun, 11 Mar 2001 10:08:35 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f2BH5OZ03129; Sun, 11 Mar 2001 10:05:24 -0700 (MST) Message-Id: <200103111705.f2BH5OZ03129@billy-club.village.org> To: Alexander Prohorenko Subject: Re: SanDisk Cc: small@FreeBSD.ORG In-reply-to: Your message of "Sun, 11 Mar 2001 18:38:15 +0200." <20010311183815.C6933@extrasy.net> References: <20010311183815.C6933@extrasy.net> Date: Sun, 11 Mar 2001 10:05:24 -0700 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010311183815.C6933@extrasy.net> Alexander Prohorenko writes: : What's the best way to use it as floppy, I mean - is there any : good way to use this device instead of floppy, and to put Pico : image there using the existing scripts/code? A 32MB can be quite useful. I don't bother with picobsd, but instead use my own scripts to populate them. I'm in the middle of a huge release crunch right now, but will try to clean them up after things lighten up. Old versions exist as mkflash-0.1 on my freebsd page http://people.freebsd.org/~imp/mkflash 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 11 9:46:20 2001 Delivered-To: freebsd-small@freebsd.org Received: from onyx.extra.dp.ua (onyx.extrasy.net [195.248.182.33]) by hub.freebsd.org (Postfix) with ESMTP id B7A7137B718 for ; Sun, 11 Mar 2001 09:46:12 -0800 (PST) (envelope-from white@onyx.extra.dp.ua) Received: (from white@localhost) by onyx.extra.dp.ua (8.10.0/8.10.0/Who.Cares) id f2BHjrU09479; Sun, 11 Mar 2001 19:45:53 +0200 (EET) Date: Sun, 11 Mar 2001 19:45:53 +0200 From: Alexander Prohorenko To: Warner Losh Cc: small@FreeBSD.ORG Subject: Re: SanDisk Message-ID: <20010311194552.F6933@extrasy.net> References: <20010311183815.C6933@extrasy.net> <200103111705.f2BH5OZ03129@billy-club.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.9i In-Reply-To: <200103111705.f2BH5OZ03129@billy-club.village.org>; from imp@village.org on Sun, Mar 11, 2001 at 10:05:24AM -0700 Organization: Extra Solutions X-Operating-System: SunOS 5.7 i86pc Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey. On Sun, Mar 11, 2001 at 10:05:24AM -0700, Warner Losh wrote: > In message <20010311183815.C6933@extrasy.net> Alexander Prohorenko writes: > : What's the best way to use it as floppy, I mean - is there any > : good way to use this device instead of floppy, and to put Pico > : image there using the existing scripts/code? [] > A 32MB can be quite useful. I don't bother with picobsd, but instead > use my own scripts to populate them. I'm in the middle of a huge > release crunch right now, but will try to clean them up after things > lighten up. Old versions exist as mkflash-0.1 on my freebsd page I have only this one http://people.freebsd.org/~imp/mkflash-0.1.tar.gz. > http://people.freebsd.org/~imp/mkflash This does not exist. Can you check this please? Are there any examples avaible? I can even try to write a sample doc, for it. But I need something to look at it to be more productive :) Is it PicoBSD based or is based on quite different scheme/idea? Thank you so much. -- Alexander Prohorenko, Extra Solutions http://www.extrasy.net/solutions "Good day to be alive, sir" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Mar 11 12:43:14 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 7E24737B718 for ; Sun, 11 Mar 2001 12:43:12 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id VAA78518; Sun, 11 Mar 2001 21:43:18 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103112043.VAA78518@info.iet.unipi.it> Subject: Re: 386DX-40 with 8 Mb RAM In-Reply-To: from Dinesh Nair at "Mar 10, 2001 04:09:07 pm" To: Dinesh Nair Date: Sun, 11 Mar 2001 21:43:17 +0100 (CET) Cc: Vladimir Zakharov , freebsd-small@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 > > You might need to backport the build scripts and file tree > > and crunchgen modifications from 4.3 to 3.x/2.x > > unnecessary, when andrzej was working on this, i backported it to 2.2.5R > and it sits at www.freebsd.org/~picobsd/picobsd225/ i was referring to the fact that the new script and picobsd tree structure in 4.3 is way more flexible to use. Suffices to say that you can have your config made of as little as 2-3 files and all in your own directory, and the build products do not anymore clutter /usr/src/release/picobsd cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Mar 11 15:40:18 2001 Delivered-To: freebsd-small@freebsd.org Received: from rues.amursk.ru (rues.amursk.ru [194.85.113.66]) by hub.freebsd.org (Postfix) with ESMTP id 3A8A837B718 for ; Sun, 11 Mar 2001 15:40:00 -0800 (PST) (envelope-from chief@ogk.vympel.amursk.ru) Received: from ogk.vympel.amursk.ru (IDENT:root@ogk.vympel.amursk.ru [213.59.139.2]) by rues.amursk.ru (8.9.3/rv-01alpha1) with ESMTP id JAA21634 for ; Mon, 12 Mar 2001 09:39:21 +1000 Posted-Date: Mon, 12 Mar 2001 09:39:21 +1000 Received: from localhost (chief@localhost) by ogk.vympel.amursk.ru (8.10.2/8.10.2) with ESMTP id f2BNcSO03824 for ; Mon, 12 Mar 2001 09:38:35 +1000 Date: Mon, 12 Mar 2001 09:38:28 +1000 (VLAT) From: Vladimir Zakharov To: freebsd-small@FreeBSD.ORG Subject: Re: 386DX-40 with 8 Mb RAM In-Reply-To: <200103112043.VAA78518@info.iet.unipi.it> 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 Sun, 11 Mar 2001, Luigi Rizzo wrote: > i was referring to the fact that the new script and picobsd tree > structure in 4.3 is way more flexible to use. Suffices to say > that you can have your config made of as little as 2-3 files > and all in your own directory, and the build products do not > anymore clutter /usr/src/release/picobsd Thanks Luigi, Yes, it can be more flexible and so on but the only lack of ee editor in 3.0 based Pico drives me insane. Above all the hardware limits do matter so I'd better relay on good old 2.2.5R :) Am I wrong? Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Mar 11 17: 1:44 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail.sicfa.com (ns.sicfa.org [212.43.217.38]) by hub.freebsd.org (Postfix) with ESMTP id 5322837B718 for ; Sun, 11 Mar 2001 17:01:42 -0800 (PST) (envelope-from lucas@sicfa.org) Received: by mail.sicfa.com (Postfix, from userid 511) id 4076316564; Mon, 12 Mar 2001 02:01:28 +0100 (CET) Date: Mon, 12 Mar 2001 02:01:28 +0100 From: Lucas Nussbaum To: Vladimir Zakharov Cc: freebsd-small@freebsd.org Subject: Re: 386DX-40 with 8 Mb RAM Message-ID: <20010312020128.A12434@ns.sicfa.org> References: <200103112043.VAA78518@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from chief@ogk.vympel.amursk.ru on Mon, Mar 12, 2001 at 09:38:28AM +1000 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 12, 2001 at 09:38:28AM +1000, Vladimir Zakharov wrote: > > Yes, it can be more flexible and so on but the only lack of ee editor > in 3.0 based Pico drives me insane. Above all the hardware limits do > matter so I'd better relay on good old 2.2.5R :) Am I wrong? If you don't have it already, you won't be able to find an ISO image or a compiled version of 2.2.5R. So the only way is to compile it from the sources. I've been trying to do so to install FreeBSD on a 486 SX 25 / 4 MB RAM laptop, but make buildworld fails on FreeBSD 4.2. If you manage to compile or have a CD and a good internet connection, let me know :) Lucas -- (A)bort, (R)etry, (T)ake down entire network? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Mar 11 17:14:51 2001 Delivered-To: freebsd-small@freebsd.org Received: from rues.amursk.ru (gosorgan.amursk.ru [194.85.113.66]) by hub.freebsd.org (Postfix) with ESMTP id E6EDF37B718 for ; Sun, 11 Mar 2001 17:14:47 -0800 (PST) (envelope-from chief@ogk.vympel.amursk.ru) Received: from ogk.vympel.amursk.ru (IDENT:root@ogk.vympel.amursk.ru [213.59.139.2]) by rues.amursk.ru (8.9.3/rv-01alpha1) with ESMTP id LAA23152; Mon, 12 Mar 2001 11:15:02 +1000 Posted-Date: Mon, 12 Mar 2001 11:15:02 +1000 Received: from localhost (chief@localhost) by ogk.vympel.amursk.ru (8.10.2/8.10.2) with ESMTP id f2C1Dtg04119; Mon, 12 Mar 2001 11:13:58 +1000 Date: Mon, 12 Mar 2001 11:13:55 +1000 (VLAT) From: Vladimir Zakharov To: Lucas Nussbaum Cc: freebsd-small@FreeBSD.ORG Subject: Re: 386DX-40 with 8 Mb RAM In-Reply-To: <20010312020128.A12434@ns.sicfa.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, 12 Mar 2001, Lucas Nussbaum wrote: > > Yes, it can be more flexible and so on but the only lack of ee editor > > in 3.0 based Pico drives me insane. Above all the hardware limits do > > matter so I'd better relay on good old 2.2.5R :) Am I wrong? > > If you don't have it already, you won't be able to find an ISO image or a > compiled version of 2.2.5R. So the only way is to compile it from the sources. > I've been trying to do so to install FreeBSD on a 486 SX 25 / 4 MB RAM laptop, > but make buildworld fails on FreeBSD 4.2. If you manage to compile or have a CD > and a good internet connection, let me know :) Sorry, Lukas and all buddies. I meant PicoBSD 0.31 by Dinesh Nair based on 2.2.5R of course. Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Mar 11 22: 6:34 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 53C1837B718 for ; Sun, 11 Mar 2001 22:06:31 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id HAA85578; Mon, 12 Mar 2001 07:06:34 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103120606.HAA85578@info.iet.unipi.it> Subject: Re: 386DX-40 with 8 Mb RAM In-Reply-To: from Vladimir Zakharov at "Mar 12, 2001 09:38:28 am" To: Vladimir Zakharov Date: Mon, 12 Mar 2001 07:06:34 +0100 (CET) Cc: freebsd-small@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 > On Sun, 11 Mar 2001, Luigi Rizzo wrote: > > > i was referring to the fact that the new script and picobsd tree > > structure in 4.3 is way more flexible to use. Suffices to say > > that you can have your config made of as little as 2-3 files > > and all in your own directory, and the build products do not > > anymore clutter /usr/src/release/picobsd > > Thanks Luigi, > > Yes, it can be more flexible and so on but the only lack of ee editor > in 3.0 based Pico drives me insane. Above all the hardware limits do what's the problem in adding one line to the crunch config ? cheers luigi > matter so I'd better relay on good old 2.2.5R :) Am I wrong? > > Vladimir > > > 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 Mon Mar 12 0: 1:42 2001 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 2C55537B718 for ; Mon, 12 Mar 2001 00:01:39 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id BAA01558; Mon, 12 Mar 2001 01:00:42 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200103120800.BAA01558@freeway.dcfinc.com> Subject: Re: 386DX-40 with 8 Mb RAM In-Reply-To: <20010312020128.A12434@ns.sicfa.org> from Lucas Nussbaum at "Mar 12, 1 02:01:28 am" To: lucas@sicfa.org (Lucas Nussbaum) Date: Mon, 12 Mar 2001 01:00:42 -0700 (MST) Cc: chief@ogk.vympel.amursk.ru, freebsd-small@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition 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, Lucas Nussbaum wrote: > If you don't have it already, you won't be able to find an ISO image > or a compiled version of 2.2.5R. So the only way is to compile it > from the sources. I've been trying to do so to install FreeBSD on a > 486 SX 25 / 4 MB RAM laptop, but make buildworld fails on FreeBSD 4.2. > If you manage to compile or have a CD and a good internet connection, > let me know :) I've got a 2.2.8-RELEASE machine. Would anything off that be of help? Plus, that machine has the CVS repository. I could check out and build 2.2.5R, if necessary... -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com 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 Mon Mar 12 11: 5: 0 2001 Delivered-To: freebsd-small@freebsd.org Received: from onyx.extra.dp.ua (onyx.extrasy.net [195.248.182.33]) by hub.freebsd.org (Postfix) with ESMTP id 0424137B719 for ; Mon, 12 Mar 2001 11:04:43 -0800 (PST) (envelope-from white@onyx.extra.dp.ua) Received: (from white@localhost) by onyx.extra.dp.ua (8.10.0/8.10.0/Who.Cares) id f2CJ4ZP19750 for small@freebsd.org; Mon, 12 Mar 2001 21:04:35 +0200 (EET) Date: Mon, 12 Mar 2001 21:04:35 +0200 From: Alexander Prohorenko To: small@freebsd.org Subject: Pico?? Message-ID: <20010312210435.K18769@extrasy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.9i Organization: Extra Solutions X-Operating-System: SunOS 5.7 i86pc Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sirs. Can anybody help me with understanding of a new structure of PicoBSD floppy image? Earlier, the disk was just a bootable floppy with kernel and /, /etc structure with gzipped files there, which were ungzipped and put on a MD image during the boot process (am I right?). Currently, the disk looks like just /kernel there. I couldn't get where are all files appear from? I'd love to understand this in details to be more productive in my work with Pico's. Also, I tried to put the /kernel file to the 30MB SanDisk flash disk (the kernel file was taken from /usr/src/release/picobsd/build/build_dir-flogw/kernel, where 'flogw' is my Pico release). Besides, one question more. How could this kernel be put on the floppy, if it's about 4 times bigger then floppy? :) white@mule:~>ls -al /usr/src/release/picobsd/build/build_dir-flogw/kernel -rwxr-xr-x 1 root wheel 5069664 Mar 12 10:48 /usr/src/release/picobsd/build/build_dir-flogw/kernel Thank you for your help, and looking forward your answers. -- Alexander Prohorenko, Extra Solutions http://www.extrasy.net/solutions "Good day to be alive, sir" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Mar 12 12: 6: 5 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 2500337B718 for ; Mon, 12 Mar 2001 12:06:00 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id VAA94111; Mon, 12 Mar 2001 21:06:17 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103122006.VAA94111@info.iet.unipi.it> Subject: Re: Pico?? In-Reply-To: <20010312210435.K18769@extrasy.net> from Alexander Prohorenko at "Mar 12, 2001 09:04:35 pm" To: Alexander Prohorenko Date: Mon, 12 Mar 2001 21:06:16 +0100 (CET) Cc: small@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 > Can anybody help me with understanding of a new structure of PicoBSD > floppy image? Earlier, the disk was just a bootable floppy with > kernel and /, /etc structure with gzipped files there, which were > ungzipped and put on a MD image during the boot process (am I right?). The kernel contains an MFS image embedded in it. After loading, the kernel mounts the image, which in the version you mention is preloaded with the files which were previously on the MFS. The /etc/rc script still tries to mount the floppy and update any files on the image with copies from the floppy, but if the floppy mount fails, the system proceeds with the preloaded image. I had mainly two reasons for doing this. First, this way you can load the kernel off the network using etherboot and have a working system without any floppy. Second, you save some (moderate) amount of space because you do not waste the space for a full fragment/block on each file. You can still update your configuration and save it on the floppy for the next reboot (remember to creste the required directories by hand, the update script still does not do this...). > > Currently, the disk looks like just /kernel there. I couldn't get > where are all files appear from? I'd love to understand this in > details to be more productive in my work with Pico's. > > Also, I tried to put the /kernel file to the 30MB SanDisk flash disk > (the kernel file was taken from > /usr/src/release/picobsd/build/build_dir-flogw/kernel, where 'flogw' > is my Pico release). > > Besides, one question more. How could this kernel be put on the floppy, > if it's about 4 times bigger then floppy? :) the kernel is usually compressed with kgzip, which helps a bit. Though i do not know if it compresses by a factor of four... cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone (510) 666 2927 . ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Mar 12 17:58:16 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail3.info.com.ph (mail3.info.com.ph [203.172.11.152]) by hub.freebsd.org (Postfix) with ESMTP id 2100937B718 for ; Mon, 12 Mar 2001 17:58:11 -0800 (PST) (envelope-from info@foresightone.com) Received: from it_manager.info.com.ph ([202.163.209.16]) by mail3.info.com.ph (8.9.3/8.9.3) with ESMTP id JAA25304 for ; Tue, 13 Mar 2001 09:45:55 +0800 Message-Id: <5.0.2.1.2.20010313095224.00a087f0@localhost> X-Sender: f1si/pop.info.com.ph@localhost (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 13 Mar 2001 09:57:49 +0800 To: freebsd-small@freebsd.org From: "Foresight One Solutions, Inc." Subject: picobsd-router build fails Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all! I have been trying to build a router version of picobsd 0.445. During the build we keep on getting the following error. Does anyone have any ideas on how we can go around this? TIA --- start of log --- (cd /usr/src/sbin/ping && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC depend && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC ping.o) `ping.o' is up to date. (cd /usr/src/usr.sbin/traceroute && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC depend && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC version.o traceroute.o) `version.o' is up to date. `traceroute.o' is up to date. (cd /usr/src/sbin/routed && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC depend && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC if.o input.o main.o output.o parms.o radix.o rdisc.o table.o trace.o) ===> rtquery `if.o' is up to date. `input.o' is up to date. `main.o' is up to date. `output.o' is up to date. `parms.o' is up to date. `radix.o' is up to date. `rdisc.o' is up to date. `table.o' is up to date. `trace.o' is up to date. (cd /usr/src/sbin/ipfw && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC depend && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC ipfw.o) `ipfw.o' is up to date. (cd /usr/src/usr.bin/minigzip && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC depend && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC minigzip.o) `minigzip.o' is up to date. cc -O -pipe -DCRUNCHED_BINARY -DRELEASE_CRUNCH -c crunch1.c cc -static -o crunch1 crunch1.o hostname.lo cat.lo kget.lo oinit.lo ifconfig.lo df.lo sps.lo ns.lo vm.lo msg.lo cp.lo rm.lo ls.lo reboot.lo sysctl.lo route.lo mount.lo umount.lo kill.lo natd.lo pppd.lo less.lo ping.lo traceroute.lo routed.lo ipfw.lo minigzip.lo -lncurses -lmytinfo -lipx -lz -lpcap -lalias -ledit -lutil -lmd -lcrypt -lmp -lgmp -lm -lkvm -lgnuregex -ltelnet hostname.lo: In function `hostname_cache_init(void)': hostname.lo(.text+0x38): undefined reference to `pthread_mutex_init' hostname.lo(.text+0x107): undefined reference to `pthread_mutex_init' hostname.lo(.text+0x11c): undefined reference to `pthread_mutex_lock' hostname.lo(.text+0x131): undefined reference to `hash_free' hostname.lo(.text+0x150): undefined reference to `hash_init' hostname.lo(.text+0x15f): undefined reference to `pthread_mutex_unlock' hostname.lo: In function `add_hostname(in_addr *, char const *)': hostname.lo(.text+0x1eb): undefined reference to `specialflag' hostname.lo(.text+0x203): undefined reference to `pthread_mutex_lock' hostname.lo(.text+0x2ef): undefined reference to `hash_delete' hostname.lo(.text+0x2ff): undefined reference to `hash_insert' hostname.lo(.text+0x343): undefined reference to `pthread_mutex_unlock' hostname.lo: In function `ip_to_hostname(in_addr *, unsigned int *)': hostname.lo(.text+0x364): undefined reference to `specialflag' hostname.lo(.text+0x37c): undefined reference to `pthread_mutex_lock' hostname.lo(.text+0x3ef): undefined reference to `my_strdup' hostname.lo(.text+0x40a): undefined reference to `pthread_mutex_unlock' hostname.lo(.text+0x425): undefined reference to `pthread_mutex_unlock' hostname.lo(.text+0x435): undefined reference to `pthread_mutex_lock' hostname.lo(.text+0x459): undefined reference to `pthread_mutex_unlock' hostname.lo(.text+0x474): undefined reference to `pthread_mutex_unlock' hostname.lo(.text+0x487): undefined reference to `my_strdup' hostname.lo(.text+0x49d): undefined reference to `pthread_mutex_unlock' hostname.lo(.text+0x4bc): undefined reference to `pthread_mutex_unlock' hostname.lo(.text+0x4cc): undefined reference to `my_no_flags_free' hostname.lo(.text+0x4d9): undefined reference to `default_charset_info' hostname.lo(.text+0x547): undefined reference to `my_no_flags_free' hostname.lo: In function `hostname_cache_refresh(void)': hostname.lo(.text+0x58b): undefined reference to `pthread_mutex_init' hostname.lo(.text+0x59a): undefined reference to `pthread_mutex_lock' hostname.lo(.text+0x5a9): undefined reference to `hash_free' hostname.lo(.text+0x5c2): undefined reference to `hash_init' hostname.lo(.text+0x5ce): undefined reference to `pthread_mutex_unlock' hostname.lo: In function `hostname_cache_free(void)': hostname.lo(.text+0x5f8): undefined reference to `pthread_mutex_destroy' hostname.lo(.text+0x61d): undefined reference to `hash_free' hostname.lo(.text+0x62c): undefined reference to `pthread_mutex_destroy' hostname.lo: In function `inc_host_errors(in_addr *)': hostname.lo(.text+0x65c): undefined reference to `pthread_mutex_lock' hostname.lo(.text+0x6c9): undefined reference to `pthread_mutex_unlock' hostname.lo: In function `reset_host_errors(in_addr *)': hostname.lo(.text+0x6ec): undefined reference to `pthread_mutex_lock' hostname.lo(.text+0x75d): undefined reference to `pthread_mutex_unlock' *** Error code 1 Stop in /usr/src/release/picobsd/router/crunch1. *** Error code 1 Stop in /usr/src/release/picobsd/router/crunch1. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Mar 12 19:49:57 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id 5894C37B718 for ; Mon, 12 Mar 2001 19:49:54 -0800 (PST) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.11.3/8.11.3) id f2D4dXa07314 for freebsd-small@freebsd.org; Mon, 12 Mar 2001 20:39:33 -0800 (PST) (envelope-from brucem) Date: Mon, 12 Mar 2001 20:39:33 -0800 (PST) From: "Bruce R. MontagueBrucem" Message-Id: <200103130439.f2D4dXa07314@mail.cruzio.com> To: freebsd-small@freebsd.org Subject: fix to picobsd script DIOCGDINFO Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Using a clean FreeBSD build of a 4.3 STABLE kit cvsuped this monday (12-mar-2001), I couldn't run the "picobsd" script as-is because of a disklabel "DIOCGDINFO" ioctl error. Adding "-s labels" to the "vnconfig" in "init_fs_image()" fixed the problem: --- picobsd.original Tue Feb 20 09:09:40 2001 +++ picobsd Mon Mar 12 20:14:34 2001 @@ -610,7 +610,7 @@ dd if=/dev/zero of=${imgname} count=${imgsize} bs=1k 2> /dev/null dd if=${boot1} of=${imgname} conv=notrunc 2> /dev/null - vnconfig -c vn${VNUM} ${imgname} || fail $? no_vnconfig + vnconfig -s labels -c vn${VNUM} ${imgname} || fail $? no_vnconfig } ------- - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Mar 12 23:12:37 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 87FBD37B719 for ; Mon, 12 Mar 2001 23:12:29 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id IAA00615; Tue, 13 Mar 2001 08:12:46 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103130712.IAA00615@info.iet.unipi.it> Subject: Re: picobsd-router build fails In-Reply-To: <5.0.2.1.2.20010313095224.00a087f0@localhost> from "Foresight One Solutions, Inc." at "Mar 13, 2001 09:57:49 am" To: "Foresight One Solutions, Inc." Date: Tue, 13 Mar 2001 08:12:46 +0100 (CET) Cc: freebsd-small@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 > hi all! > > I have been trying to build a router version of picobsd 0.445. During the > build we keep on getting the following error. Does anyone have any ideas on > how we can go around this? probably the objects are a leftover of some older compile involving the pthread library. Other than cleanup /usr/obj and the source tree, I would suggest to upgrade the stuff in /usr/src/release/picobsd and /usr/src/usr.sbin/crunch so you can use the new scripts which are much less error prone. cheers luigi > TIA > > --- start of log --- > > (cd /usr/src/sbin/ping && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE > -DNOCRYPT -DNONETGRAPH -DNOIPSEC depend && make -DNOPAM -DRELEASE_CRUNCH > -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC ping.o) > `ping.o' is up to date. > (cd /usr/src/usr.sbin/traceroute && make -DNOPAM -DRELEASE_CRUNCH > -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC depend && make -DNOPAM > -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC version.o > traceroute.o) > `version.o' is up to date. > `traceroute.o' is up to date. > (cd /usr/src/sbin/routed && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE > -DNOCRYPT -DNONETGRAPH -DNOIPSEC depend && make -DNOPAM -DRELEASE_CRUNCH > -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC if.o input.o main.o output.o > parms.o radix.o rdisc.o table.o trace.o) > ===> rtquery > `if.o' is up to date. > `input.o' is up to date. > `main.o' is up to date. > `output.o' is up to date. > `parms.o' is up to date. > `radix.o' is up to date. > `rdisc.o' is up to date. > `table.o' is up to date. > `trace.o' is up to date. > (cd /usr/src/sbin/ipfw && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE > -DNOCRYPT -DNONETGRAPH -DNOIPSEC depend && make -DNOPAM -DRELEASE_CRUNCH > -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC ipfw.o) > `ipfw.o' is up to date. > (cd /usr/src/usr.bin/minigzip && make -DNOPAM -DRELEASE_CRUNCH -DNOSECURE > -DNOCRYPT -DNONETGRAPH -DNOIPSEC depend && make -DNOPAM -DRELEASE_CRUNCH > -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC minigzip.o) > `minigzip.o' is up to date. > cc -O -pipe -DCRUNCHED_BINARY -DRELEASE_CRUNCH -c crunch1.c > cc -static -o crunch1 crunch1.o hostname.lo cat.lo kget.lo oinit.lo > ifconfig.lo df.lo sps.lo ns.lo vm.lo msg.lo cp.lo rm.lo ls.lo reboot.lo > sysctl.lo route.lo mount.lo umount.lo kill.lo natd.lo pppd.lo less.lo > ping.lo traceroute.lo routed.lo ipfw.lo minigzip.lo -lncurses -lmytinfo > -lipx -lz -lpcap -lalias -ledit -lutil -lmd -lcrypt -lmp -lgmp -lm -lkvm > -lgnuregex -ltelnet > hostname.lo: In function `hostname_cache_init(void)': > hostname.lo(.text+0x38): undefined reference to `pthread_mutex_init' > hostname.lo(.text+0x107): undefined reference to `pthread_mutex_init' > hostname.lo(.text+0x11c): undefined reference to `pthread_mutex_lock' > hostname.lo(.text+0x131): undefined reference to `hash_free' > hostname.lo(.text+0x150): undefined reference to `hash_init' > hostname.lo(.text+0x15f): undefined reference to `pthread_mutex_unlock' > hostname.lo: In function `add_hostname(in_addr *, char const *)': > hostname.lo(.text+0x1eb): undefined reference to `specialflag' > hostname.lo(.text+0x203): undefined reference to `pthread_mutex_lock' > hostname.lo(.text+0x2ef): undefined reference to `hash_delete' > hostname.lo(.text+0x2ff): undefined reference to `hash_insert' > hostname.lo(.text+0x343): undefined reference to `pthread_mutex_unlock' > hostname.lo: In function `ip_to_hostname(in_addr *, unsigned int *)': > hostname.lo(.text+0x364): undefined reference to `specialflag' > hostname.lo(.text+0x37c): undefined reference to `pthread_mutex_lock' > hostname.lo(.text+0x3ef): undefined reference to `my_strdup' > hostname.lo(.text+0x40a): undefined reference to `pthread_mutex_unlock' > hostname.lo(.text+0x425): undefined reference to `pthread_mutex_unlock' > hostname.lo(.text+0x435): undefined reference to `pthread_mutex_lock' > hostname.lo(.text+0x459): undefined reference to `pthread_mutex_unlock' > hostname.lo(.text+0x474): undefined reference to `pthread_mutex_unlock' > hostname.lo(.text+0x487): undefined reference to `my_strdup' > hostname.lo(.text+0x49d): undefined reference to `pthread_mutex_unlock' > hostname.lo(.text+0x4bc): undefined reference to `pthread_mutex_unlock' > hostname.lo(.text+0x4cc): undefined reference to `my_no_flags_free' > hostname.lo(.text+0x4d9): undefined reference to `default_charset_info' > hostname.lo(.text+0x547): undefined reference to `my_no_flags_free' > hostname.lo: In function `hostname_cache_refresh(void)': > hostname.lo(.text+0x58b): undefined reference to `pthread_mutex_init' > hostname.lo(.text+0x59a): undefined reference to `pthread_mutex_lock' > hostname.lo(.text+0x5a9): undefined reference to `hash_free' > hostname.lo(.text+0x5c2): undefined reference to `hash_init' > hostname.lo(.text+0x5ce): undefined reference to `pthread_mutex_unlock' > hostname.lo: In function `hostname_cache_free(void)': > hostname.lo(.text+0x5f8): undefined reference to `pthread_mutex_destroy' > hostname.lo(.text+0x61d): undefined reference to `hash_free' > hostname.lo(.text+0x62c): undefined reference to `pthread_mutex_destroy' > hostname.lo: In function `inc_host_errors(in_addr *)': > hostname.lo(.text+0x65c): undefined reference to `pthread_mutex_lock' > hostname.lo(.text+0x6c9): undefined reference to `pthread_mutex_unlock' > hostname.lo: In function `reset_host_errors(in_addr *)': > hostname.lo(.text+0x6ec): undefined reference to `pthread_mutex_lock' > hostname.lo(.text+0x75d): undefined reference to `pthread_mutex_unlock' > *** Error code 1 > > Stop in /usr/src/release/picobsd/router/crunch1. > *** Error code 1 > > Stop in /usr/src/release/picobsd/router/crunch1. > > > 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 Tue Mar 13 10: 6: 5 2001 Delivered-To: freebsd-small@freebsd.org Received: from nwlynx.network-lynx.net (nwlynx.network-lynx.net [63.122.185.99]) by hub.freebsd.org (Postfix) with ESMTP id C2B4A37B71B for ; Tue, 13 Mar 2001 10:06:00 -0800 (PST) (envelope-from Don@Silver-Lynx.com) Received: from Silver-Lynx.com (doze-1.network-lynx.net [63.122.185.106]) by nwlynx.network-lynx.net (8.11.1/8.9.3/Who.Cares) with ESMTP id f2DI68j14165 for ; Tue, 13 Mar 2001 11:06:08 -0700 (MST) (envelope-from Don@Silver-Lynx.com) Message-ID: <3AAE618A.E89BF8B1@Silver-Lynx.com> Date: Tue, 13 Mar 2001 11:06:02 -0700 From: Don Wilde X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: mounting ata flash Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We're close (Alex Prohorenko and I). We have the flash booting the pico-compiled kernel file off flash. How do I go about making a device node for the ad0 device so that it ends up embedded in the image that's transferred to flash? Once I boot off of it, I want to mount it to the filesystem rooted in md0 so that I can write to it as JAMFS. What do I need to do? -- Don Wilde Don@Silver-Lynx.com Silver Lynx Embedded Microsystems Architects 2218 Southern Bl. Ste. 12 Rio Rancho, NM 87124 505-891-4175 FAX 891-4185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Mar 13 11:38:26 2001 Delivered-To: freebsd-small@freebsd.org Received: from onyx.extra.dp.ua (onyx.extrasy.net [195.248.182.33]) by hub.freebsd.org (Postfix) with ESMTP id 00BF037B723 for ; Tue, 13 Mar 2001 11:38:10 -0800 (PST) (envelope-from white@onyx.extra.dp.ua) Received: (from white@localhost) by onyx.extra.dp.ua (8.10.0/8.10.0/Who.Cares) id f2DJc4R12131 for small@freebsd.org; Tue, 13 Mar 2001 21:38:04 +0200 (EET) Date: Tue, 13 Mar 2001 21:38:04 +0200 From: Alexander Prohorenko To: small@freebsd.org Subject: 4000+ Message-ID: <20010313213804.F21408@extrasy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.9i Organization: Extra Solutions X-Operating-System: SunOS 5.7 i86pc Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. How can use bigger sizes of disks? [] Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/vn0c 3839 2027 1812 53% 270 752 26% /tmp/picobsd.O69tgiWtJ4 /dev/rvn0c: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/rvn0c: clean, 1812 free (4 frags, 226 blocks, 0.1% fragmentation) disklabel: fd4096: unknown disk type ---> fail: Error <1> error code Error while doing disklabel on of floppy.img size 4096 ---> Aborting ./picobsd What should I write in a disktab for fd4096 and bigger ones? Thanks. -- Alexander Prohorenko, Extra Solutions http://www.extrasy.net/solutions "Good day to be alive, sir" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Mar 14 8: 2:51 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 3A23237B71A for ; Wed, 14 Mar 2001 08:02:49 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id RAA19225; Wed, 14 Mar 2001 17:02:55 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103141602.RAA19225@info.iet.unipi.it> Subject: Re: mounting ata flash In-Reply-To: <3AAE618A.E89BF8B1@Silver-Lynx.com> from Don Wilde at "Mar 13, 2001 11:06:02 am" To: Don Wilde Date: Wed, 14 Mar 2001 17:02:54 +0100 (CET) Cc: freebsd-small@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 > We're close (Alex Prohorenko and I). We have the flash booting the > pico-compiled kernel file off flash. How do I go about making a device if you are using the new script, the set of device nodes is in the "MY_DEVS" variable in the file named "config" in the same directory where you have the PICOBSD and crunch.conf luigi > node for the ad0 device so that it ends up embedded in the image that's > transferred to flash? Once I boot off of it, I want to mount it to the > filesystem rooted in md0 so that I can write to it as JAMFS. What do I > need to do? > -- > Don Wilde Don@Silver-Lynx.com > Silver Lynx Embedded Microsystems Architects > 2218 Southern Bl. Ste. 12 Rio Rancho, NM 87124 > 505-891-4175 FAX 891-4185 > > 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 Wed Mar 14 13:38:27 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id 02A4337B719 for ; Wed, 14 Mar 2001 13:38:22 -0800 (PST) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.11.3/8.11.3) id f2EMRvL10304 for freebsd-small@freebsd.org; Wed, 14 Mar 2001 14:27:57 -0800 (PST) (envelope-from brucem) Date: Wed, 14 Mar 2001 14:27:57 -0800 (PST) From: "Bruce R. Montague" Message-Id: <200103142227.f2EMRvL10304@mail.cruzio.com> To: freebsd-small@freebsd.org Subject: bad /usr/ports/picobsd in bridge crunch.conf Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The uncustomized vanilla 4.3 BETA (4.3-BETA #0: Mon Mar 12) picobsd bridge configuration crunchgen "crunch.conf" file contains references to a non-existant "/usr/ports/picobsd" dir. ==> "picobsd -v bridge" results in crunchgen error: ---- cd: can't cd to /usr/ports/picobsd/more crunchgen: Can't execute: cd /usr/ports/picobsd/more && echo -n `/bin/pwd` ----- ==> There is no "/usr/ports/picobsd" in the ports tree cvsupped at the same time as the rest of RELENG_4. ==> Also, "http://www.FreeBSD.org/cgi/cvsweb.cgi/ports" shows no "picobsd" subtree. ==> Find shows: ---- ./bridge/crunch.conf:special more srcdir /usr/ports/picobsd/more ./bridge/crunch.conf:special sshd srcdir /usr/ports/picobsd/ssh-picobs ./bridge/crunch.conf:special sshd objdir /usr/ports/picobsd/ssh-picobs ---- Hum... In the cvs web the bridge "crunch.conf" has been moved to the attic (?) after earlier being crunch1(?): "http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/picobsd/bridge/Attic/crunch.conf" ==> Temp work-around FIX (?): I didn't need more or ssh, so I commented them out in "/usr/src/release/picobsd/bridge/crunch.conf": ============= --- crunch.conf.original Wed Mar 14 13:30:19 2001 +++ crunch.conf Wed Mar 14 13:32:05 2001 @@ -86,8 +86,8 @@ progs reboot # 0KB. #progs less # 36KB #ln less more -progs more # 12KB -special more srcdir /usr/ports/picobsd/more +#progs more # 12KB +#special more srcdir /usr/ports/picobsd/more progs sysctl progs swapon # 0KB. @@ -158,9 +158,9 @@ # Check the ssh license! If you want to use this, # go to /usr/ports/security/ssh-picobsd, do a make extract configure #progs sshd # includes ssh and scp -special sshd objvar SSHD_OBJS -special sshd srcdir /usr/ports/picobsd/ssh-picobsd/work/ssh-1.2.27 -special sshd objdir /usr/ports/picobsd/ssh-picobsd/work/ssh-1.2.27 +#special sshd objvar SSHD_OBJS +#special sshd srcdir /usr/ports/picobsd/ssh-picobsd/work/ssh-1.2.27 +#special sshd objdir /usr/ports/picobsd/ssh-picobsd/work/ssh-1.2.27 ### ee uses ncurses instead of curses libs -ledit -lutil -lmd -lcrypt -lmp -lgmp -lm -lkvm ================ The crunch.conf header says the file will almost surely need to be customized. - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Mar 14 15:47: 5 2001 Delivered-To: freebsd-small@freebsd.org Received: from gargoyle.apana.org.au (gargoyle-xl0.apana.org.au [210.215.3.53]) by hub.freebsd.org (Postfix) with ESMTP id EDA0737B719 for ; Wed, 14 Mar 2001 15:47:00 -0800 (PST) (envelope-from dougy@gargoyle.apana.org.au) Received: (from uucp@localhost) by gargoyle.apana.org.au (8.9.3/8.9.3) id JAA35692 for ; Thu, 15 Mar 2001 09:47:11 +1000 (EST) (envelope-from dougy@gargoyle.apana.org.au) Received: from bryden.apana.org.au(203.3.126.129), claiming to be "roadrunner" via SMTP by gargoyle.apana.org.au, id smtpdd35689; Thu Mar 15 09:47:08 2001 Message-ID: <0c1801c0ace1$30e7f1a0$817e03cb@apana.org.au> From: "Doug Young" To: Subject: functional differences between variants Date: Thu, 15 Mar 2001 09:47:52 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've read the various README's at http://www.freebsd.org/picobsd, but can't discern any significant difference between the content of the different versions of picoBSD. eg they all appear to support ppp & NICS, so what gives ?? Some postings to the mailing list archives suggest that one needs all the versions available because "ee" is only on one version, however there are conflicting postings on the issue of firewall support ..... apart from those items there doesn't appear to be anything explicit on what differs. Also, is there a reason why picoBSD development still appears to be concentrated on older versions of FreeBSD instead of something in the 4.x line ?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Mar 14 16:10:43 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id 0BD9E37B718 for ; Wed, 14 Mar 2001 16:10:41 -0800 (PST) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.11.3/8.11.3) id f2F10Gj23950 for freebsd-small@freebsd.org; Wed, 14 Mar 2001 17:00:16 -0800 (PST) (envelope-from brucem) Date: Wed, 14 Mar 2001 17:00:16 -0800 (PST) From: "Bruce R. Montague" Message-Id: <200103150100.f2F10Gj23950@mail.cruzio.com> To: freebsd-small@freebsd.org Subject: picobsd script refs nonexistent "./clean" script Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The uncustomized vanilla 4.3 BETA (4.3-BETA #0: Mon Mar 12) "picobsd" script (file "./src/release/picobsd/build/picobsd") references a shell script named "clean" that is not in the directory: ----------- build_package() { touch build.status echo "##############################################" >>build.status echo "## `date` ">>build.status echo "##############################################" >>build.status ./clean dial ----------- --- picobsd.old Wed Mar 14 16:41:07 2001 +++ picobsd Wed Mar 14 16:39:33 2001 @@ -174,7 +174,6 @@ echo "##############################################" >>build.status echo "## `date` ">>build.status echo "##############################################" >>build.status - ./clean dial for z in dial router net isp ; do set_type ${z} echo "---------------------------------------------">>build.status -------------- This "clean" file used to be in the directory; the "CVS log for src/release/picobsd/build/clean" says: ----- Tue Feb 20 04:37:56 2001 "Remove "clean", its functions are now implemented by the main "picobsd" script." ----- Fix (?): remove the ref to "clean" as above, unless there is some transitional thing going on here that the snapshots I am looking at have missed... - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Mar 14 17: 8:46 2001 Delivered-To: freebsd-small@freebsd.org Received: from relay.rost.ru (relay.rost.ru [213.59.222.15]) by hub.freebsd.org (Postfix) with ESMTP id 3F25237B718 for ; Wed, 14 Mar 2001 17:08:44 -0800 (PST) (envelope-from alev@rost.ru) Received: from rost.ru (ppp8-maxwell.krypton.rost.ru [213.59.222.55] (may be forged)) by relay.rost.ru (8.11.2/8.11.2) with ESMTP id f2F18k892855 for ; Thu, 15 Mar 2001 04:08:47 +0300 (MSK) Message-ID: <3AB01605.F697011D@rost.ru> Date: Thu, 15 Mar 2001 04:08:21 +0300 From: al Reply-To: alev@rost.ru X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en,de,fr,nl,ru,uk MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: help Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG help end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Mar 14 17:13:41 2001 Delivered-To: freebsd-small@freebsd.org Received: from gargoyle.apana.org.au (gargoyle-xl0.apana.org.au [210.215.3.53]) by hub.freebsd.org (Postfix) with ESMTP id F063537B719 for ; Wed, 14 Mar 2001 17:13:36 -0800 (PST) (envelope-from dougy@gargoyle.apana.org.au) Received: (from uucp@localhost) by gargoyle.apana.org.au (8.9.3/8.9.3) id LAA37562; Thu, 15 Mar 2001 11:13:27 +1000 (EST) (envelope-from dougy@gargoyle.apana.org.au) Received: from bryden.apana.org.au(203.3.126.129), claiming to be "roadrunner" via SMTP by gargoyle.apana.org.au, id smtpdU37560; Thu Mar 15 11:13:22 2001 Message-ID: <006701c0aced$3c51e300$817e03cb@apana.org.au> From: "Doug Young" To: , References: <3AB01605.F697011D@rost.ru> Subject: Re: help Date: Thu, 15 Mar 2001 11:14:04 +1000 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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG me too :) ----- Original Message ----- From: "al" To: Sent: Thursday, March 15, 2001 11:08 AM Subject: help > help > end > > 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 Wed Mar 14 17:19:42 2001 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 3BFF737B718 for ; Wed, 14 Mar 2001 17:19:33 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id SAA09475; Wed, 14 Mar 2001 18:19:24 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200103150119.SAA09475@freeway.dcfinc.com> Subject: Re: functional differences between variants In-Reply-To: <0c1801c0ace1$30e7f1a0$817e03cb@apana.org.au> from Doug Young at "Mar 15, 1 09:47:52 am" To: dougy@gargoyle.apana.org.au (Doug Young) Date: Wed, 14 Mar 2001 18:19:24 -0700 (MST) Cc: freebsd-small@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition 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, Doug Young wrote: > Also, is there a reason why picoBSD development still appears to be > concentrated on older versions of FreeBSD instead of something in the > 4.x line ?? The kernel in the 4.x line is considerably larger than 2.2.x or 3.5.x, and has some features (like improved SMP support) that is of little use for Pico systems. When you're trying to smoosh stuff down to fit on a floppy, every little bit (byte?) counts. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com 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 Wed Mar 14 17:24:48 2001 Delivered-To: freebsd-small@freebsd.org Received: from gargoyle.apana.org.au (gargoyle-xl0.apana.org.au [210.215.3.53]) by hub.freebsd.org (Postfix) with ESMTP id A060137B718 for ; Wed, 14 Mar 2001 17:24:44 -0800 (PST) (envelope-from dougy@gargoyle.apana.org.au) Received: (from uucp@localhost) by gargoyle.apana.org.au (8.9.3/8.9.3) id LAA37755; Thu, 15 Mar 2001 11:24:47 +1000 (EST) (envelope-from dougy@gargoyle.apana.org.au) Received: from bryden.apana.org.au(203.3.126.129), claiming to be "roadrunner" via SMTP by gargoyle.apana.org.au, id smtpdN37751; Thu Mar 15 11:24:42 2001 Message-ID: <008d01c0acee$d1cf6dc0$817e03cb@apana.org.au> From: "Doug Young" To: Cc: References: <200103150119.SAA09475@freeway.dcfinc.com> Subject: Re: functional differences between variants Date: Thu, 15 Mar 2001 11:25:21 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK that makes sense ... now is there any written info detailing exactly what is in each of the different versions or does one need to poke inside each one individually ?? I hoped the README's would cover that stuff but looks like they are almost "word for word" copies. ----- Original Message ----- From: "Chad R. Larson" To: "Doug Young" Cc: Sent: Thursday, March 15, 2001 11:19 AM Subject: Re: functional differences between variants > As I recall, Doug Young wrote: > > Also, is there a reason why picoBSD development still appears to be > > concentrated on older versions of FreeBSD instead of something in the > > 4.x line ?? > > The kernel in the 4.x line is considerably larger than 2.2.x or > 3.5.x, and has some features (like improved SMP support) that is of > little use for Pico systems. When you're trying to smoosh stuff > down to fit on a floppy, every little bit (byte?) counts. > > -crl > -- > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > chad@dcfinc.com chad@larsons.org larson1@home.com > 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 Wed Mar 14 18:13: 3 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id 7265637B718 for ; Wed, 14 Mar 2001 18:12:58 -0800 (PST) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.11.3/8.11.3) id f2F32XF44977 for freebsd-small@freebsd.org; Wed, 14 Mar 2001 19:02:33 -0800 (PST) (envelope-from brucem) Date: Wed, 14 Mar 2001 19:02:33 -0800 (PST) From: "Bruce R. Montague" Message-Id: <200103150302.f2F32XF44977@mail.cruzio.com> To: freebsd-small@freebsd.org Subject: hard "panic: no init" w picobsd "dial" config Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A hard "panic: no init" occurs when attempting to boot the vanilla uncustomized picobsd "dial" configuration under 4.3 BETA (4.3-BETA #0: Mon Mar 12). The system enters a "jack-rabbit" crash/reboot cycle during boot with the "no init" message. System was built in "./src/release/picobsd/build" with "picobsd dial" command. Problem occurs because neither "init" or "oinit" is included in the "dial" crunch.conf file ("./src/release/picobsd/dial/crunch.conf"). Apparently in the past one or the other of these was written to crunch.conf via the "dial" Makefile as per setting of ${INIT}. The in-dir Makefiles no longer exist. One fix is to ==> 1) change the default build setting specified at the top of "./src/release/picobsd/dial/PICOBSD" to "oinit" (instead of init): ---------- --- PICOBSD.original Wed Mar 14 18:25:28 2001 +++ PICOBSD Wed Mar 14 18:25:48 2001 @@ -2,7 +2,7 @@ # $FreeBSD: src/release/picobsd/dial/PICOBSD,v 1.5.2.2 2001/02/20 00:34:17 luigi Exp $ #Line starting with #PicoBSD contains PicoBSD build parameters #marker def_sz init MFS_inodes floppy_inodes -#PicoBSD 2000 init 4096 32768 +#PicoBSD 2000 oinit 4096 32768 options MD_ROOT_SIZE=2000 # same as def_sz # ----------- ==> 2) and update "./src/release/picobsd/dial/crunch.conf" with the line "progs oinit": ---------- --- crunch.conf.original Wed Mar 14 15:36:03 2001 +++ crunch.conf Wed Mar 14 17:51:43 2001 @@ -25,6 +25,7 @@ ln gzip gzcat ln less more +progs oinit progs sh test kget echo pwd msg stty progs hostname cat kill sps vm ns progs chmod chown help getty ---------- This might not be the desired fix, since the "dial" end-user might want to run a full shell, but that requires additional programs (login). - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Mar 14 21:15:12 2001 Delivered-To: freebsd-small@freebsd.org Received: from online.tmx.com.au (online.tmx.com.au [192.150.129.1]) by hub.freebsd.org (Postfix) with ESMTP id C140837B71A; Wed, 14 Mar 2001 21:14:48 -0800 (PST) (envelope-from mtaylor@bytecraft.com.au) Received: from melexc01.bytecraft.com.au ([203.9.250.249]) by online.tmx.com.au (8.9.3/8.8.8) with ESMTP id QAA01245; Thu, 15 Mar 2001 16:14:40 +1100 (EST) Received: by MELEXC01 with Internet Mail Service (5.5.2448.0) id ; Thu, 15 Mar 2001 16:16:18 +1100 Message-ID: <710709BB8B02D311942E006067441810544294@MELEXC01> From: Murray Taylor To: "'freebsd-small@freebsd.org'" , "'freebsd-questions@freebsd.org'" Subject: PicoBSD Bridge build breaks on 'MFS filesystem signature not foun d in kernel' Date: Thu, 15 Mar 2001 16:16:15 +1100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am attempting to build a picoBSD Bridge using the attached files and it breaks at the almost last step with the message 'MFS filesystem signature not found in kernel' from the write_mfs_in_filesystem.c program Other environmental conditions .... Using 4.2-Stable cvsupped 13/mar/2001 make world done Not yet installed newly rebuilt kernel as system is still being used in production but have done a 'make' in the kernel build directory OK I am using ./picobsd --floppy_size 1440 -v build as the command and am setting MFS bytes/inode to 4096 and MFS size to 2000 via the dialogue box I have changed all ${TYPE} to $THETYPE} as TYPE was never setup anywhere and added the -s labels option to the vnconfig lines throughout the picobsd script. Any suggestions??? Murray Taylor Project Engineer Bytecraft P/L +61 3 9587 2555 +61 3 9587 1614 fax mtaylor@bytecraft.com.au ===== bridge/PICOBSD file ========== # # $FreeBSD: src/release/picobsd/bridge/PICOBSD,v 1.1.4.3 2001/01/29 22:40:02 luigi Exp $ # # Line starting with #PicoBSD contains PicoBSD build parameters #marker def_sz init MFS_inodes floppy_inodes #PicoBSD 1440 init 8192 32768 options MD_ROOT_SIZE=1440 # same as def_sz # next to each option there is the approx. space used in the # picobsd image. machine i386 cpu I386_CPU cpu I486_CPU cpu I586_CPU #cpu I686_CPU ident PICOBSD maxusers 20 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] #options BOOTP options MFS #Memory Filesystem options MD_ROOT #MFS as root options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] #options MSDOSFS #MSDOS Filesystem #options CD9660 #ISO 9660 Filesystem, 12KB #options PROCFS #Process filesystem, 4KB options USERCONFIG #boot -c editor, 4KB options INTRO_USERCONFIG #imply -c and parse info area options VISUAL_USERCONFIG #visual boot -c editor options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT # divert (for natd, 4KB) #options DEVFS options PCI_QUIET # Support for bridging and bandwidth limiting options DUMMYNET options BRIDGE options HZ=1000 options NMBCLUSTERS=4096 #config kernel root on fd0a device isa0 device pci0 device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 #device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 #device ata #device atadisk #device atapicd # 8KB # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 #device psm0 at atkbdc? irq 12 # 8KB device vga0 at isa? # syscons is the default console driver, resembling an SCO console device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # device ppc0 at isa? port? flags 0x40 irq 7 # device ppbus0 # device nlpt0 at ppbus? # device plip0 at ppbus? # device ppi0 at ppbus? # # The following Ethernet NICs are all PCI devices. # device miibus device de0 # DEC/Intel DC21x4x (``Tulip'') #device fxp0 # Intel, 4KB #device xl0 # 3Com #device ep0 #device rl0 # Realtek 8139, 4KB #device dc0 # New Dec/Intel DC21x4x, 8KB #device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 #device ed1 at isa? port 0x300 irq 5 iomem 0xd0000 pseudo-device loop pseudo-device ether pseudo-device tun 2 # 4KB, for ppp #pseudo-device vn pseudo-device pty 16 pseudo-device md # memory disk #options MATH_EMULATE #Support for x87 emulation, 4KB pseudo-device bpf 4 # 4KB, for tcpdump #options NFS #Network Filesystem #options NFS_NOSERVER #Network Filesystem options DDB ====== bridge/config file ============= # configuration for picobsd build script. # it should only contain variable definitions -- it is sourced # by the shell much like rc.conf* files MY_DEVS="std tun2 vty10 fd0 ad0 pty0 cuaa0 cuaa1 bpf0 bpf1 bpf2" ======= bridge/crunch.conf file ======== # # $FreeBSD: src/release/picobsd/bridge/crunch.conf,v 1.1.2.1 2001/02/19 23:24:30 luigi Exp $ # # configuration file for "bridge" floppy. # Depending on your needs, almost surely you will need to # modify your configuration to add/remove/change programs used in # the floppy image. Remember that some programs also require # matching kernel options to enable device drivers etc. # # Next to most of the programs i have tried to indicate the approximate # space consumed, but beware that these values change from release # to release, and might depend on the presence of other programs which # share the same libraries. # # NOTE: the string "/usr/src" will be automatically replaced with the # correct value set in 'build' script - you should change it there # Default build options. Basically tell the Makefiles which understand # that to use the most compact possible version of the code. # buildopts -DNOPAM -DRELEASE_CRUNCH -DNONETGRAPH -DNOIPSEC -DNOINET6 # directories where to look for sources of various binaries. srcdirs /usr/src/bin srcdirs /usr/src/sbin/i386 srcdirs /usr/src/sbin srcdirs /usr/src/usr.bin srcdirs /usr/src/gnu/usr.bin srcdirs /usr/src/usr.sbin srcdirs /usr/src/libexec # Some programs are especially written for PicoBSD and reside here srcdirs /usr/src/release/picobsd/tinyware # # And there are others (mostly ports) which reside in their specific # directories. For them, we use the "special" commands to tell # crunchgen where to look for sources, objects, which Makefile # variables contain the list of sources and objects, and so on. # init is almost always necessary. progs init # 4KB. # fsck is almost always necessary, unless you have everything on the # image and use 'tar' or something similar to read/write raw blocks # from the floppy. progs fsck # 24KB. # ifconfig is needed if you want to configure interfaces... progs ifconfig # 4KB. # # You will also need a shell and a bunch of utilities. # The standard shell is not that large, but you need many # external programs. In fact most of them do not take much space # as they merely issue a system call, and print the result; the # libraries are already needed anyways, so they end up using almost # no additional memory. # There are a few exceptions such as 'less', which in 4.x is # rather large. progs sh # 36KB. ln sh -sh progs echo # 0KB. progs pwd progs mkdir rmdir progs chmod chown progs mv ln # 0KB. progs mount progs minigzip # 0KB. ln minigzip gzip progs cp # 0KB. progs rm progs ls progs kill progs df # 0KB. progs ps # 4KB. progs ns # 4KB. ln ns netstat progs vm # 0KB. progs cat # 0KB. progs test # 0KB. ln test [ progs hostname # 0KB. progs login # 4KB. progs getty # 4KB. progs stty # 4KB. progs w # 0KB. progs msg # 0KB. ln msg dmesg progs kget # 0KB. progs reboot # 0KB. progs less # 36KB ln less more #progs more # 12KB #special more srcdir /usr/ports/picobsd/more progs sysctl progs swapon # 0KB. progs pwd_mkdb # 0KB. progs dev_mkdb # 0KB. progs umount progs mount_std progs du # 0KB. progs tail # 0KB. progs tee # 0KB. progs passwd # 0KB. progs route # 8KB # progs mount_msdos # progs comcontrol # # If you want to run natd, remember the alias library #progs natd # 20KB #libs -lalias # natd # # ppp is rather large. Note that as of Jan.01, RELEASE_CRUNCH # makes ppp not use libalias, so you cannot have aliasing. #progs ppp # 112KB # You need an editor. ee is relatively small, though there are # smaller ones. vi is much larger. # The editor also usually need a curses library. progs ee # 32KB. libs -lncurses # progs vi # ?? # libs -lcurses # for vi #progs tcpdump # 100KB. #special tcpdump srcdir /usr/src/usr.sbin/tcpdump/tcpdump progs arp # 0KB. progs disklabel # 4KB. progs fdisk # 4KB. progs vnconfig # 0KB. progs grep # 16KB. progs date # 4KB. progs mount_nfs # 0KB. ln mount_nfs nfs progs ping # 4KB. #progs routed # 32KB. progs ipfw # 12KB. progs traceroute # 0KB. # progs mount_cd9660 # 4KB. # ln mount_cd9660 cd9660 # progs newfs # 12KB. #ln newfs mount_mfs ln chown chgrp # ln mount_msdos msdos ln mount_std procfs ln mount_std mount_procfs # If you need to access the box remotely, and maybe copy files # from/to it, you can use telnet, rsh or ssh. # inetd is only needed for telnet and rshd progs inetd # 12KB. progs telnet # 20KB. progs telnetd # 12KB. #progs ftp # 28KB. #progs tar # 32KB. # Check the ssh license! If you want to use this, # go to /usr/ports/security/ssh-picobsd, do a make extract configure #progs sshd # includes ssh and scp special sshd objvar SSHD_OBJS special sshd srcdir /usr/ports/picobsd/ssh-picobsd/work/ssh-1.2.27 special sshd objdir /usr/ports/picobsd/ssh-picobsd/work/ssh-1.2.27 ### ee uses ncurses instead of curses libs -ledit -lutil -lmd -lcrypt -lmp -lgmp -lm -lkvm libs -lmytinfo -lipx -lz -lpcap -lwrap libs -ltermcap -lgnuregex -ltelnet # -lcurses ======= bridge/floppy.tree.exclude file ====== etc/snmpd.conf etc/ppp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Mar 14 22:24:31 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 6B2AA37B718 for ; Wed, 14 Mar 2001 22:24:20 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id HAA28372; Thu, 15 Mar 2001 07:24:21 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103150624.HAA28372@info.iet.unipi.it> Subject: Re: PicoBSD Bridge build breaks on 'MFS filesystem signature not foun d in kernel' In-Reply-To: <710709BB8B02D311942E006067441810544294@MELEXC01> from Murray Taylor at "Mar 15, 2001 04:16:15 pm" To: Murray Taylor Date: Thu, 15 Mar 2001 07:24:21 +0100 (CET) Cc: "'freebsd-small@freebsd.org'" X-Mailer: ELM [version 2.4ME+ PL61 (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 You should use a larger MD_ROOT_SIZE such as the 2200kb which was originally in the kernel config file, not the 1440 that you have in your example. The mfs overflows and probably the script does not abort early as it should. cheers luigi > I am attempting to build a picoBSD Bridge using the attached files and it > breaks at the > almost last step with the message > > 'MFS filesystem signature not found in kernel' > > from the write_mfs_in_filesystem.c program > > Other environmental conditions .... > Using 4.2-Stable cvsupped 13/mar/2001 > make world done > Not yet installed newly rebuilt kernel as system is still being used in > production > but have done a 'make' in the kernel build directory OK > > I am using > ./picobsd --floppy_size 1440 -v build > as the command > > and am setting MFS bytes/inode to 4096 > and MFS size to 2000 > via the dialogue box > > I have changed all ${TYPE} to $THETYPE} as TYPE was never setup anywhere > and added the -s labels option to the vnconfig lines > throughout the picobsd script. > > Any suggestions??? > > Murray Taylor > Project Engineer > > Bytecraft P/L +61 3 9587 2555 > +61 3 9587 1614 fax > mtaylor@bytecraft.com.au > > > ===== bridge/PICOBSD file ========== > # > # $FreeBSD: src/release/picobsd/bridge/PICOBSD,v 1.1.4.3 2001/01/29 22:40:02 > luigi Exp $ > # > # Line starting with #PicoBSD contains PicoBSD build parameters > #marker def_sz init MFS_inodes floppy_inodes > #PicoBSD 1440 init 8192 32768 > options MD_ROOT_SIZE=1440 # same as def_sz > > # next to each option there is the approx. space used in the > # picobsd image. > > machine i386 > cpu I386_CPU > cpu I486_CPU > cpu I586_CPU > #cpu I686_CPU > ident PICOBSD > maxusers 20 > > options INET #InterNETworking > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device [keep > this!] > #options BOOTP > options MFS #Memory Filesystem > options MD_ROOT #MFS as root > options COMPAT_43 #Compatible with BSD 4.3 [KEEP > THIS!] > > #options MSDOSFS #MSDOS Filesystem > #options CD9660 #ISO 9660 Filesystem, 12KB > #options PROCFS #Process filesystem, 4KB > options USERCONFIG #boot -c editor, 4KB > options INTRO_USERCONFIG #imply -c and parse info area > options VISUAL_USERCONFIG #visual boot -c editor > > options IPFIREWALL > options IPFIREWALL_DEFAULT_TO_ACCEPT > options IPDIVERT # divert (for natd, 4KB) > #options DEVFS > options PCI_QUIET > # Support for bridging and bandwidth limiting > options DUMMYNET > options BRIDGE > options HZ=1000 > options NMBCLUSTERS=4096 > > #config kernel root on fd0a > > device isa0 > device pci0 > > device fdc0 at isa? port IO_FD1 irq 6 drq 2 > device fd0 at fdc0 drive 0 > > #device ata0 at isa? port IO_WD1 irq 14 > #device ata1 at isa? port IO_WD2 irq 15 > #device ata > #device atadisk > #device atapicd # 8KB > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 > #device psm0 at atkbdc? irq 12 # 8KB > > device vga0 at isa? > > # syscons is the default console driver, resembling an SCO console > device sc0 at isa? > > device npx0 at nexus? port IO_NPX irq 13 > > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > device sio1 at isa? port IO_COM2 irq 3 > > # device ppc0 at isa? port? flags 0x40 irq 7 > # device ppbus0 > # device nlpt0 at ppbus? > # device plip0 at ppbus? > # device ppi0 at ppbus? > > # > # The following Ethernet NICs are all PCI devices. > # > device miibus > device de0 # DEC/Intel DC21x4x (``Tulip'') > #device fxp0 # Intel, 4KB > #device xl0 # 3Com > #device ep0 > #device rl0 # Realtek 8139, 4KB > #device dc0 # New Dec/Intel DC21x4x, 8KB > > #device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 > #device ed1 at isa? port 0x300 irq 5 iomem 0xd0000 > > pseudo-device loop > pseudo-device ether > pseudo-device tun 2 # 4KB, for ppp > #pseudo-device vn > pseudo-device pty 16 > pseudo-device md # memory disk > > #options MATH_EMULATE #Support for x87 emulation, 4KB > pseudo-device bpf 4 # 4KB, for tcpdump > #options NFS #Network Filesystem > #options NFS_NOSERVER #Network Filesystem > options DDB > > > ====== bridge/config file ============= > # configuration for picobsd build script. > # it should only contain variable definitions -- it is sourced > # by the shell much like rc.conf* files > > MY_DEVS="std tun2 vty10 fd0 ad0 pty0 cuaa0 cuaa1 bpf0 bpf1 bpf2" > > ======= bridge/crunch.conf file ======== > # > # $FreeBSD: src/release/picobsd/bridge/crunch.conf,v 1.1.2.1 2001/02/19 > 23:24:30 luigi Exp $ > # > # configuration file for "bridge" floppy. > # Depending on your needs, almost surely you will need to > # modify your configuration to add/remove/change programs used in > # the floppy image. Remember that some programs also require > # matching kernel options to enable device drivers etc. > # > # Next to most of the programs i have tried to indicate the approximate > # space consumed, but beware that these values change from release > # to release, and might depend on the presence of other programs which > # share the same libraries. > # > # NOTE: the string "/usr/src" will be automatically replaced with the > # correct value set in 'build' script - you should change it there > > # Default build options. Basically tell the Makefiles which understand > # that to use the most compact possible version of the code. > # > buildopts -DNOPAM -DRELEASE_CRUNCH -DNONETGRAPH -DNOIPSEC -DNOINET6 > > # directories where to look for sources of various binaries. > srcdirs /usr/src/bin > srcdirs /usr/src/sbin/i386 > srcdirs /usr/src/sbin > srcdirs /usr/src/usr.bin > srcdirs /usr/src/gnu/usr.bin > srcdirs /usr/src/usr.sbin > srcdirs /usr/src/libexec > # Some programs are especially written for PicoBSD and reside here > srcdirs /usr/src/release/picobsd/tinyware > # > # And there are others (mostly ports) which reside in their specific > # directories. For them, we use the "special" commands to tell > # crunchgen where to look for sources, objects, which Makefile > # variables contain the list of sources and objects, and so on. > > # init is almost always necessary. > progs init # 4KB. > # fsck is almost always necessary, unless you have everything on the > # image and use 'tar' or something similar to read/write raw blocks > # from the floppy. > progs fsck # 24KB. > # ifconfig is needed if you want to configure interfaces... > progs ifconfig # 4KB. > # > # You will also need a shell and a bunch of utilities. > # The standard shell is not that large, but you need many > # external programs. In fact most of them do not take much space > # as they merely issue a system call, and print the result; the > # libraries are already needed anyways, so they end up using almost > # no additional memory. > # There are a few exceptions such as 'less', which in 4.x is > # rather large. > progs sh # 36KB. > ln sh -sh > progs echo # 0KB. > progs pwd > progs mkdir rmdir > progs chmod chown > progs mv ln # 0KB. > progs mount > progs minigzip # 0KB. > ln minigzip gzip > progs cp # 0KB. > progs rm > progs ls > progs kill > progs df # 0KB. > progs ps # 4KB. > progs ns # 4KB. > ln ns netstat > progs vm # 0KB. > progs cat # 0KB. > progs test # 0KB. > ln test [ > progs hostname # 0KB. > progs login # 4KB. > progs getty # 4KB. > progs stty # 4KB. > progs w # 0KB. > progs msg # 0KB. > ln msg dmesg > progs kget # 0KB. > progs reboot # 0KB. > progs less # 36KB > ln less more > #progs more # 12KB > #special more srcdir /usr/ports/picobsd/more > > progs sysctl > progs swapon # 0KB. > progs pwd_mkdb # 0KB. > progs dev_mkdb # 0KB. > progs umount > progs mount_std > progs du # 0KB. > progs tail # 0KB. > progs tee # 0KB. > progs passwd # 0KB. > > progs route # 8KB > # progs mount_msdos > # progs comcontrol > # > # If you want to run natd, remember the alias library > #progs natd # 20KB > #libs -lalias # natd > # > # ppp is rather large. Note that as of Jan.01, RELEASE_CRUNCH > # makes ppp not use libalias, so you cannot have aliasing. > #progs ppp # 112KB > > # You need an editor. ee is relatively small, though there are > # smaller ones. vi is much larger. > # The editor also usually need a curses library. > progs ee # 32KB. > libs -lncurses > # progs vi # ?? > # libs -lcurses # for vi > > #progs tcpdump # 100KB. > #special tcpdump srcdir /usr/src/usr.sbin/tcpdump/tcpdump > > progs arp # 0KB. > > progs disklabel # 4KB. > progs fdisk # 4KB. > progs vnconfig # 0KB. > > progs grep # 16KB. > progs date # 4KB. > progs mount_nfs # 0KB. > ln mount_nfs nfs > progs ping # 4KB. > #progs routed # 32KB. > progs ipfw # 12KB. > progs traceroute # 0KB. > # progs mount_cd9660 # 4KB. > # ln mount_cd9660 cd9660 > # progs newfs # 12KB. > #ln newfs mount_mfs > ln chown chgrp > # ln mount_msdos msdos > ln mount_std procfs > ln mount_std mount_procfs > > # If you need to access the box remotely, and maybe copy files > # from/to it, you can use telnet, rsh or ssh. > # inetd is only needed for telnet and rshd > progs inetd # 12KB. > progs telnet # 20KB. > progs telnetd # 12KB. > #progs ftp # 28KB. > #progs tar # 32KB. > > # Check the ssh license! If you want to use this, > # go to /usr/ports/security/ssh-picobsd, do a make extract configure > #progs sshd # includes ssh and scp > special sshd objvar SSHD_OBJS > special sshd srcdir /usr/ports/picobsd/ssh-picobsd/work/ssh-1.2.27 > special sshd objdir /usr/ports/picobsd/ssh-picobsd/work/ssh-1.2.27 > > ### ee uses ncurses instead of curses > libs -ledit -lutil -lmd -lcrypt -lmp -lgmp -lm -lkvm > libs -lmytinfo -lipx -lz -lpcap -lwrap > libs -ltermcap -lgnuregex -ltelnet # -lcurses > > ======= bridge/floppy.tree.exclude file ====== > etc/snmpd.conf > etc/ppp > > 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 Thu Mar 15 0:15:39 2001 Delivered-To: freebsd-small@freebsd.org Received: from leka.almamedia.fi (leka.yhteys.mtv3.fi [62.236.224.129]) by hub.freebsd.org (Postfix) with SMTP id 128E037B718 for ; Thu, 15 Mar 2001 00:15:36 -0800 (PST) (envelope-from jml@cubical.fi) Received: (qmail 15556 invoked from network); 15 Mar 2001 08:15:33 -0000 Received: from dyn-c-042.yhteys.mtv3.fi (HELO snafu.intra.net) (@62.236.227.42) by leka.yhteys.mtv3.fi with SMTP; 15 Mar 2001 08:15:33 -0000 Received: from cubical.fi (huilu.intra.net [192.168.2.2]) by snafu.intra.net (8.11.1/8.11.1) with ESMTP id f2F8FM002422; Thu, 15 Mar 2001 10:15:30 +0200 (EET) (envelope-from jml@cubical.fi) Message-ID: <3AB07A5F.B6A19F76@cubical.fi> Date: Thu, 15 Mar 2001 10:16:31 +0200 From: Juha-Matti Liukkonen Organization: Cubical Solutions Ltd X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: chad@DCFinc.com Cc: Doug Young , freebsd-small@FreeBSD.ORG Subject: Re: functional differences between variants References: <200103150119.SAA09475@freeway.dcfinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, talking of squeezing bits, bzip2 can stuff the kernel and filesystem images into quite a bit smaller space than gzip, giving maybe an extra 200 KB on the floppy. I don't think it would be too difficult to make /boot/loader to support kernel.bz2 as well; libbz2.a comes with the bzip2 port and is quite simple to use. - Juha "Chad R. Larson" wrote: > > As I recall, Doug Young wrote: > > Also, is there a reason why picoBSD development still appears to be > > concentrated on older versions of FreeBSD instead of something in the > > 4.x line ?? > > The kernel in the 4.x line is considerably larger than 2.2.x or > 3.5.x, and has some features (like improved SMP support) that is of > little use for Pico systems. When you're trying to smoosh stuff > down to fit on a floppy, every little bit (byte?) counts. > > -crl > -- > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > chad@dcfinc.com chad@larsons.org larson1@home.com > 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 -- Juha-Matti Liukkonen, Cubical Solutions Ltd Phone: +358(0)405280142 Email: jml@cubical.fi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Mar 15 0:21:11 2001 Delivered-To: freebsd-small@freebsd.org Received: from gargoyle.apana.org.au (gargoyle-xl0.apana.org.au [210.215.3.53]) by hub.freebsd.org (Postfix) with ESMTP id 4A08337B718 for ; Thu, 15 Mar 2001 00:21:03 -0800 (PST) (envelope-from dougy@gargoyle.apana.org.au) Received: (from uucp@localhost) by gargoyle.apana.org.au (8.9.3/8.9.3) id SAA44011; Thu, 15 Mar 2001 18:21:03 +1000 (EST) (envelope-from dougy@gargoyle.apana.org.au) Received: from bryden.apana.org.au(203.3.126.129), claiming to be "roadrunner" via SMTP by gargoyle.apana.org.au, id smtpdN44009; Thu Mar 15 18:21:00 2001 Message-ID: <001a01c0ad28$f83517a0$817e03cb@apana.org.au> From: "Doug Young" To: "Juha-Matti Liukkonen" , Cc: References: <200103150119.SAA09475@freeway.dcfinc.com> <3AB07A5F.B6A19F76@cubical.fi> Subject: Re: functional differences between variants Date: Thu, 15 Mar 2001 18:21:42 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Designing that stuff is a bit beyond my level of comprehension :) If I get a custom build to run at all I'll be happy .... at the rate FreeBSD 4.3 is downloading it will be next week before I can even try. Maybe oneday we'll have DSL or something in OZ ----- Original Message ----- From: "Juha-Matti Liukkonen" To: Cc: "Doug Young" ; Sent: Thursday, March 15, 2001 6:16 PM Subject: Re: functional differences between variants > Hi, > > talking of squeezing bits, bzip2 can stuff the kernel and filesystem > images into quite a bit smaller space than gzip, giving maybe an extra > 200 KB on the floppy. I don't think it would be too difficult to make > /boot/loader to support kernel.bz2 as well; libbz2.a comes with the > bzip2 port and is quite simple to use. > > - Juha > > "Chad R. Larson" wrote: > > > > As I recall, Doug Young wrote: > > > Also, is there a reason why picoBSD development still appears to be > > > concentrated on older versions of FreeBSD instead of something in the > > > 4.x line ?? > > > > The kernel in the 4.x line is considerably larger than 2.2.x or > > 3.5.x, and has some features (like improved SMP support) that is of > > little use for Pico systems. When you're trying to smoosh stuff > > down to fit on a floppy, every little bit (byte?) counts. > > > > -crl > > -- > > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > > chad@dcfinc.com chad@larsons.org larson1@home.com > > 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 > > -- > Juha-Matti Liukkonen, Cubical Solutions Ltd > Phone: +358(0)405280142 > Email: jml@cubical.fi > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Mar 15 0:28: 4 2001 Delivered-To: freebsd-small@freebsd.org Received: from web115.yahoomail.com (web115.mail.yahoo.com [205.180.60.88]) by hub.freebsd.org (Postfix) with SMTP id 3FC6937B719 for ; Thu, 15 Mar 2001 00:28:02 -0800 (PST) (envelope-from dyeske@yahoo.com) Received: (qmail 21921 invoked by uid 60001); 15 Mar 2001 08:27:58 -0000 Message-ID: <20010315082758.21920.qmail@web115.yahoomail.com> Received: from [64.81.49.127] by web115.yahoomail.com; Thu, 15 Mar 2001 00:27:58 PST Date: Thu, 15 Mar 2001 00:27:58 -0800 (PST) From: David Yeske Subject: Re: functional differences between variants To: freebsd-small@FreeBSD.ORG In-Reply-To: <3AB07A5F.B6A19F76@cubical.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think that would be really cool, being able to bzip an mfsroot would also be really useful so you could do the mfsroot load method from /boot/loader, or bzip the kernel after you write_mfs_in_kernel... David --- Juha-Matti Liukkonen wrote: > Hi, > > talking of squeezing bits, bzip2 can stuff the kernel and filesystem > images into quite a bit smaller space than gzip, giving maybe an extra > 200 KB on the floppy. I don't think it would be too difficult to make > /boot/loader to support kernel.bz2 as well; libbz2.a comes with the > bzip2 port and is quite simple to use. > > - Juha > > "Chad R. Larson" wrote: > > > > As I recall, Doug Young wrote: > > > Also, is there a reason why picoBSD development still appears to be > > > concentrated on older versions of FreeBSD instead of something in the > > > 4.x line ?? > > > > The kernel in the 4.x line is considerably larger than 2.2.x or > > 3.5.x, and has some features (like improved SMP support) that is of > > little use for Pico systems. When you're trying to smoosh stuff > > down to fit on a floppy, every little bit (byte?) counts. > > > > -crl > > -- > > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > > chad@dcfinc.com chad@larsons.org larson1@home.com > > 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 > > -- > Juha-Matti Liukkonen, Cubical Solutions Ltd > Phone: +358(0)405280142 > Email: jml@cubical.fi > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message __________________________________________________ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Mar 15 1:33:14 2001 Delivered-To: freebsd-small@freebsd.org Received: from online.tmx.com.au (online.tmx.com.au [192.150.129.1]) by hub.freebsd.org (Postfix) with ESMTP id 8E96537B718 for ; Thu, 15 Mar 2001 01:33:09 -0800 (PST) (envelope-from mtaylor@bytecraft.com.au) Received: from melexc01.bytecraft.com.au ([203.9.250.249]) by online.tmx.com.au (8.9.3/8.8.8) with ESMTP id UAA24389; Thu, 15 Mar 2001 20:32:56 +1100 (EST) Received: by MELEXC01 with Internet Mail Service (5.5.2448.0) id ; Thu, 15 Mar 2001 20:34:35 +1100 Message-ID: <710709BB8B02D311942E006067441810544297@MELEXC01> From: Murray Taylor To: "'Luigi Rizzo'" Cc: "'freebsd-small@freebsd.org'" Subject: RE: PicoBSD Bridge build breaks on 'MFS filesystem signature not foun d in kernel' Date: Thu, 15 Mar 2001 20:33:54 +1100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks again .. much twiddling and tweaking going on .... I understand the need for /etc dir on the floppy but what files need to go in the /root one ? #$&**(^$#T% I believe that the phrase is "bother!" this pile of junk that the boss wants me to use has just had a floppy drive collapse ... not booting, lotsa errors, I'm going home (ps itsa 100MHz Pentium-S which seems to work fine when the floppy works!) (pps At least the BIG MACHINE, a Compaq A550, is going like a train .....) And when I get a new drive and dd another disk I will come back and carry on rewardless (sigh) If there is any other pointers you can give to a pico-newbie they would be greatly appreciated. mjt > -----Original Message----- > From: Luigi Rizzo [SMTP:luigi@info.iet.unipi.it] > Sent: Thursday, 15 March 2001 19:43 > To: Murray Taylor > Subject: Re: PicoBSD Bridge build breaks on 'MFS filesystem signature > not foun d in kernel' > > > Question: > > Where do I preset the values for hostname / card addresses ... Is there > a > > rc.conf file > > type of arrangement?? > > rc tries to match the MAC address with one in /etc/hosts and from > there gets the name and ip. But yes, you can set the hostname > in rc.conf (I think). > > > Question 2: can I mount the pico disk onto the main FreeBSD box and edit > > appropriate files > > or do I use the ee on the disk to edit the necessary items. > > either way. Just remember to create the /etc and /root dirs on > the floppy. > > > Question 3: Is there any special procedures to update the floppy files > with > > the configs > > or are they standard files? ( i recall seeing something about some > update > > command a > > while back...) > > basically standard files, just gzipped to save space. > > luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Mar 15 1:55:52 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id C922B37B71C for ; Thu, 15 Mar 2001 01:55:49 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id KAA29981; Thu, 15 Mar 2001 10:55:56 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103150955.KAA29981@info.iet.unipi.it> Subject: Re: PicoBSD Bridge build breaks on 'MFS filesystem signature not foun d in kernel' In-Reply-To: <710709BB8B02D311942E006067441810544297@MELEXC01> from Murray Taylor at "Mar 15, 2001 08:33:54 pm" To: Murray Taylor Date: Thu, 15 Mar 2001 10:55:56 +0100 (CET) Cc: "'freebsd-small@freebsd.org'" X-Mailer: ELM [version 2.4ME+ PL61 (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 > I understand the need for /etc dir on the floppy but what files > need to go in the /root one ? maybe nothing. > If there is any other pointers you can give to a pico-newbie they would be > greatly > appreciated. unfortunately UTSL is the only thing i can tell you -- the picobsd script contains some comments on what to do and how. Havent had the time to write a manpage yet. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Mar 15 12:18:35 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id 2004637B71D for ; Thu, 15 Mar 2001 12:18:33 -0800 (PST) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.11.3/8.11.3) id f2FL7wR16074 for freebsd-small@freebsd.org; Thu, 15 Mar 2001 13:07:58 -0800 (PST) (envelope-from brucem) Date: Thu, 15 Mar 2001 13:07:58 -0800 (PST) From: "Bruce R. Montague" Message-Id: <200103152107.f2FL7wR16074@mail.cruzio.com> To: freebsd-small@freebsd.org Subject: picobsd "net" mfs.mtree, "fd", INCLUDE_FLOPPY_IN_MFS Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This might not be the desired fix for a "net" build that should be netbootable w/o floppy. - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Mar 15 12:26:20 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id A4F1D37B71A for ; Thu, 15 Mar 2001 12:26:17 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id VAA35525; Thu, 15 Mar 2001 21:26:22 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103152026.VAA35525@info.iet.unipi.it> Subject: Re: picobsd "net" mfs.mtree, "fd", INCLUDE_FLOPPY_IN_MFS In-Reply-To: <200103152107.f2FL7wR16074@mail.cruzio.com> from "Bruce R. Montague" at "Mar 15, 2001 01:07:58 pm" To: "Bruce R. Montague" Date: Thu, 15 Mar 2001 21:26:22 +0100 (CET) Cc: freebsd-small@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 > This might not be the desired fix for a "net" build > that should be netbootable w/o floppy. why ? The main purpose of INCLUDE_FLOPPY_IN_MFS is to have everything in the image so even if the fd mount fails the filesystem under the mount point is already populated with the correct content. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Mar 15 12:44:17 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 73A6637B718 for ; Thu, 15 Mar 2001 12:44:12 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id VAA35603; Thu, 15 Mar 2001 21:44:19 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103152044.VAA35603@info.iet.unipi.it> Subject: Re: hard "panic: no init" w picobsd "dial" config In-Reply-To: <200103150302.f2F32XF44977@mail.cruzio.com> from "Bruce R. Montague" at "Mar 14, 2001 07:02:33 pm" To: "Bruce R. Montague" Date: Thu, 15 Mar 2001 21:44:19 +0100 (CET) Cc: freebsd-small@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 you can imagine, the only version that i tested somehow (and on a local tree, with the /usr/ports/picobsd things) is the "bridge" one... So if you have patches to the PICOBSD and crunch.conf files, they are welcome... One note -- oinit was a solution to save memory and let the system run in 4MB. I seriously doubt we can even think of it with 4.x due to generic code bloat. At which point, the next viable configs being 8 or 16MB, who cares about 200KB more in the decompressed image as long as it fits the floppy. cheers luigi > > A hard "panic: no init" occurs when attempting to > boot the vanilla uncustomized picobsd "dial" > configuration under 4.3 BETA (4.3-BETA #0: Mon Mar > 12). The system enters a "jack-rabbit" crash/reboot > cycle during boot with the "no init" message. > > System was built in > "./src/release/picobsd/build" > with "picobsd dial" command. > > Problem occurs because neither "init" or "oinit" is > included in the "dial" crunch.conf file > ("./src/release/picobsd/dial/crunch.conf"). Apparently > in the past one or the other of these was written > to crunch.conf via the "dial" Makefile as per setting > of ${INIT}. The in-dir Makefiles no longer exist. > > One fix is to > > ==> 1) change the default build setting > specified at the top of > "./src/release/picobsd/dial/PICOBSD" > to "oinit" (instead of init): > > > ---------- > > --- PICOBSD.original Wed Mar 14 18:25:28 2001 > +++ PICOBSD Wed Mar 14 18:25:48 2001 > @@ -2,7 +2,7 @@ > # $FreeBSD: src/release/picobsd/dial/PICOBSD,v 1.5.2.2 2001/02/20 00:34:17 luigi Exp $ > #Line starting with #PicoBSD contains PicoBSD build parameters > #marker def_sz init MFS_inodes floppy_inodes > -#PicoBSD 2000 init 4096 32768 > +#PicoBSD 2000 oinit 4096 32768 > options MD_ROOT_SIZE=2000 # same as def_sz > > # > > ----------- > > > ==> 2) and update > "./src/release/picobsd/dial/crunch.conf" > with the line > "progs oinit": > > ---------- > > --- crunch.conf.original Wed Mar 14 15:36:03 2001 > +++ crunch.conf Wed Mar 14 17:51:43 2001 > @@ -25,6 +25,7 @@ > ln gzip gzcat > ln less more > > +progs oinit > progs sh test kget echo pwd msg stty > progs hostname cat kill sps vm ns > progs chmod chown help getty > > ---------- > > > This might not be the desired fix, since the "dial" > end-user might want to run a full shell, but that > requires additional programs (login). > > > > - bruce > > > > 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 Thu Mar 15 13: 3:17 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id 2954537B719 for ; Thu, 15 Mar 2001 13:03:14 -0800 (PST) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.11.3/8.11.3) id f2FLqmM16134 for freebsd-small@freebsd.org; Thu, 15 Mar 2001 13:52:48 -0800 (PST) (envelope-from brucem) Date: Thu, 15 Mar 2001 13:52:48 -0800 (PST) From: "Bruce R. Montague" Message-Id: <200103152152.f2FLqmM16134@mail.cruzio.com> To: freebsd-small@freebsd.org Subject: mailing error! re "net" mfs.mtree, INCLUDE_FLOPPY_IN_MFS Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry about e-mail error in regard to message that only got out with: >This might not be the desired fix for a "net" build >that should be netbootable w/o floppy. Preceeding unsent text: The uncustomized vanilla 4.3 BETA (4.3-BETA #0: Mon Mar 12) picobsd "net" configuration does not build because the "picobsd/net/mfs.mtree" file does not contain an entry for "fd", which is always required if INCLUDE_FLOPPY_IN_MFS is set to "yes" in the picobsd script (the default). This causes the build to bomb with: ---- cp -Rp /usr/src/release/picobsd/build/build_dir-net/floppy.tree/boot.config /usr/src/release/picobsd/build/build_dir-net/floppy.tree/etc /usr/src/release/picobsd/build/build_dir-net/floppy.tree/kernel.config /tmp/picobsd.a5YFQpDSmY/fd usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory ---- On script error at this point, /dev/vn0c does not get unmounted, so you need to manual do a "umount /dev/vn0c". ---- Fix ?: Add "fd" entry to "./release/picobsd/net/mfs.mtree": --------- --- mfs.mtree.original Wed Mar 14 22:02:26 2001 +++ mfs.mtree Wed Mar 14 22:04:05 2001 @@ -9,6 +9,8 @@ .. etc .. + fd + .. home user .. --------- The system will build, boot, and run... Again, sorry, need better eyes, cordination, something! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Mar 15 14:32:32 2001 Delivered-To: freebsd-small@freebsd.org Received: from online.tmx.com.au (online.tmx.com.au [192.150.129.1]) by hub.freebsd.org (Postfix) with ESMTP id 2A93837B719 for ; Thu, 15 Mar 2001 14:32:27 -0800 (PST) (envelope-from mtaylor@bytecraft.com.au) Received: from melexc01.bytecraft.com.au ([203.9.250.249]) by online.tmx.com.au (8.9.3/8.8.8) with ESMTP id JAA03308; Fri, 16 Mar 2001 09:32:13 +1100 (EST) Received: by MELEXC01 with Internet Mail Service (5.5.2448.0) id ; Fri, 16 Mar 2001 09:33:56 +1100 Message-ID: <710709BB8B02D311942E006067441810544298@MELEXC01> From: Murray Taylor To: "'Bruce R. Montague'" Cc: "'freebsd-small@freebsd.org'" Subject: RE: odd "MFS Filesystem signature not found" Date: Fri, 16 Mar 2001 09:31:56 +1100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Based on Luigi's comment to reset the MD_ROOT_SIZE=2200 as it was in the bridge PICOBSD file it all built fine I am on 4.3-BETA as at 13/mar Note I am using the regular more(aka less) as the ports stuff isnt available and at present (done when I was using the 1440 MD size) I have commented out tcpdump. I did have to modify the picobsd script and add ' -s labels' to all vnconfig lines and I changed all ${TYPE} to ${THETYPE} as TYPE was never set anywhere As my previous email indicated - all I have to do now is get the floppy disk drive replaced by our IT bloke! mjt > -----Original Message----- > From: Bruce R. Montague [SMTP:brucem@mail.cruzio.com] > Sent: Friday, 16 March 2001 07:07 > To: mtaylor@bytecraft.com.au > Subject: odd "MFS Filesystem signature not found" > > > Here's an odd one. I downloaded the latest 4.3 BETA > this monday and have been building the various > picobsd types. > > I build the "bridge" config w/o seeing the MFS > filesystem signature problem... but I _did_ > see this error when building the vanilla "net" > config. > > I did all my builds w/o any changes, that is, > no dialog alterations to the default, no PICOBSD > config file changes. > > No here's the troublesome thing... the problem > "fixed itself". After a session last night and > one this morning (after a reboot), the problem > just disappeared. I had "forced" a good "net" > build by adding to PICOBSD an: > options MD_ROOT_SIZE=2200 # same as def_sz > > line... not really sure why this build > worked... and after doing this I cant > get any build to fail (well, I dont have > a supported Ethernet device in the final > target, so the final system doesnt usually > run, but the build goes fine). > > I'm wondering if maybe something somewhere > can left over as the result of crash, and > not cleaned, causing confusion until a > good build or complete cleanup, etc. > > > - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Mar 15 17: 0:46 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id 7B6E837B718 for ; Thu, 15 Mar 2001 17:00:34 -0800 (PST) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.11.3/8.11.3) id f2G1o8k31203 for freebsd-small@freebsd.org; Thu, 15 Mar 2001 17:50:08 -0800 (PST) (envelope-from brucem) Date: Thu, 15 Mar 2001 17:50:08 -0800 (PST) From: "Bruce R. Montague" Message-Id: <200103160150.f2G1o8k31203@mail.cruzio.com> To: freebsd-small@freebsd.org Subject: tinyware not crunched into net-type picobsd Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The "tinyware" utilities are not included in the current 4.3 Beta picobsd "net" crunchgen, although the /bin links are created. This means that attempting to invoke "vm", "dmesg", "ps", and "netstat" returns an error of the form: "crunch1: ps not compiled in." The build produces the following error: "crunchgen: /usr/src/release/picobsd/build/build_dir-net/crunch1.conf:19: `../../tinyware' is not a directory, skipping it" and "ignoring program because of errors" for the following tinyware pgms: vm msg sps ns The fix appears simply to use the absolute path to tinyware, similar to what is done in the other "crunch.conf" files, that is: "srcdirs /usr/src/release/picobsd/tinyware" instead of: "srcdirs ../../tinyware" ----- --- crunch.cong.original Wed Mar 14 21:35:27 2001 +++ crunch.conf Wed Mar 14 21:37:46 2001 @@ -16,7 +16,7 @@ srcdirs /usr/src/usr.sbin srcdirs /usr/src/libexec # sources for ns & vm -srcdirs ../../tinyware +srcdirs /usr/src/release/picobsd/tinyware ----- The "crunch.conf" files in the picobsd subdirs for the "bridge", "dial", "isp", and "router" types all specify the absolute path. - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Mar 16 10:50:14 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id 4578B37B719 for ; Fri, 16 Mar 2001 10:50:10 -0800 (PST) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.11.3/8.11.3) id f2GJdhC27230 for freebsd-small@freebsd.org; Fri, 16 Mar 2001 11:39:43 -0800 (PST) (envelope-from brucem) Date: Fri, 16 Mar 2001 11:39:43 -0800 (PST) From: "Bruce R. Montague" Message-Id: <200103161939.f2GJdhC27230@mail.cruzio.com> To: freebsd-small@freebsd.org Subject: picoBSD net options MD_ROOT_SIZE missing Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The "./release/picobsd/net/PICOBSD" configuration file does not contain a line: "options MD_ROOT_SIZE=2200 # same as def_sz" under the "#PicoBSD" default-specifier line (all other PICOBSD files do). This causes the compile of the kernel driver for the memory device (md.c) to fail with an "MD_ROOT_SIZE undeclared" error: ../../dev/md/md.c: In function `md_drvinit': ../../dev/md/md.c:482: `MD_ROOT_SIZE' undeclared (first use in this function) ../../dev/md/md.c:482: (Each undeclared identifier is reported only once ../../dev/md/md.c:482: for each function it appears in.) *** Error code 1 Stop in /usr/src/sys/compile/PICOBSD-net. Fix is to add a line: options MD_ROOT_SIZE=2200 # same as def_sz under the default line. --------- --- PICOBSD.original Fri Mar 16 10:50:58 2001 +++ PICOBSD Thu Mar 15 10:35:40 2001 @@ -4,6 +4,8 @@ #Line starting with #PicoBSD contains PicoBSD build parameters #marker def_sz init MFS_inodes floppy_inodes #PicoBSD 2200 init 4096 32768 +options MD_ROOT_SIZE=2200 + machine i386 cpu I386_CPU --------- This makes the specification of this option similar to what is done in the PICOBSD files for bridge, dial, isp, and router. - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Mar 16 13:59: 8 2001 Delivered-To: freebsd-small@freebsd.org Received: from mail.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id C96F137B719 for ; Fri, 16 Mar 2001 13:59:04 -0800 (PST) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.11.3/8.11.3) id f2GMmb100556 for freebsd-small@freebsd.org; Fri, 16 Mar 2001 14:48:37 -0800 (PST) (envelope-from brucem) Date: Fri, 16 Mar 2001 14:48:37 -0800 (PST) From: "Bruce R. Montague" Message-Id: <200103162248.f2GMmb100556@mail.cruzio.com> To: freebsd-small@freebsd.org Subject: PICOBSD bld cleanup and modifying config files. Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a picoBSD circumstance that's probably not a bug but maybe qualifies as an "operator Be-aware". If a build of picobsd fails due to a compilation error while compiling the kernel, changes made thereafter to the relevent PICOBSD config file in the "release/picobsd" tree may not take effect unless the corresponding configuration file (typically in "/usr/src/sys/i386/conf") is deleted manually (for a build of type "net", this file would be named "PICOBSD-net". Editing "/usr/src/release/picobsd/net/PICOBSD" thereafter would have no effect on subsequent "picobsd net" builds). The manual deletion is required because the makefile ("/usr/src/release/picobsd/build/Makefile.conf") dependency in "${COMPILE}: ${CONF}/${CONFFILE}" detects the existing config file and thus does not apply the "$(CONF)/${CONFFILE}:" rule to copy the new PICOBSD configuration file over the version in "/usr/src/sys/i386/conf". Obvious but easy to overlook. ------- The picobsd build script doesn't seem to have a cleanup, unless I've missed something obvious...? To "nuke" everything left over from an old picobsd build, for instance of type "net": * cd /usr/src/sys/compile and delete the "PICOBSD-net" build directory. * cd /usr/src/sys/i386/conf and delete the "PICOBSD-net" config file. * cd /usr and delete the "obj-picobsd" subdirectory. * cd /usr/src/release/picobsd/build and delete the "build_dir-net" subdirectory * cd /tmp and delete the "picobsd.XXXXXXXXXX" (temp name) subdirectory. and delete the "reply.XXXXXXXXXX" temporary file. Have I missed anything? - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Mar 16 14:53:28 2001 Delivered-To: freebsd-small@freebsd.org Received: from spooky.eis.net.au (spooky.eis.net.au [203.12.171.2]) by hub.freebsd.org (Postfix) with ESMTP id 76C9537B71A for ; Fri, 16 Mar 2001 14:53:24 -0800 (PST) (envelope-from ernie@spooky.eis.net.au) Received: (from ernie@localhost) by spooky.eis.net.au (8.11.2/8.9.3) id f2GMrLc10379 for freebsd-small@freebsd.org; Sat, 17 Mar 2001 08:53:21 +1000 (EST) (envelope-from ernie) From: Ernie Elu Message-Id: <200103162253.f2GMrLc10379@spooky.eis.net.au> Subject: How to get FreeBSD on to DiskonChip To: freebsd-small@freebsd.org Date: Sat, 17 Mar 2001 08:52:00 +1000 (EST) X-Mailer: ELM [version 2.5 PL3] 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 I have a SBC with a 40MB DiskOnChip 2000 installed, there is also an IDE drive with FreeBSD 4.2-STABLE on it, from which I have built a kernel with the fla driver installed. How do I get a small distribution of FreeBSD onto the DiskOnChip? The fla README says you can do it with sysinstall but every time I try that it installed the distribution on to my IDE drive desipte the fact I selected the fla drive in the fdisk and disklabel sections What am I doing wrong? Does anyone have a script to create the /dev tree and move across the kernel and basic files so I can boot from the fla device? - Ernie. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Mar 16 15: 2: 7 2001 Delivered-To: freebsd-small@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7A16A37B71A for ; Fri, 16 Mar 2001 15:02:04 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2GN1p938068; Fri, 16 Mar 2001 16:01:51 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103162301.f2GN1p938068@harmony.village.org> To: Ernie Elu Subject: Re: How to get FreeBSD on to DiskonChip Cc: freebsd-small@FreeBSD.ORG In-reply-to: Your message of "Sat, 17 Mar 2001 08:52:00 +1000." <200103162253.f2GMrLc10379@spooky.eis.net.au> References: <200103162253.f2GMrLc10379@spooky.eis.net.au> Date: Fri, 16 Mar 2001 16:01:51 -0700 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200103162253.f2GMrLc10379@spooky.eis.net.au> Ernie Elu writes: : How do I get a small distribution of FreeBSD onto the DiskOnChip? : : The fla README says you can do it with sysinstall but every time I try that : it installed the distribution on to my IDE drive desipte the fact I selected : the fla drive in the fdisk and disklabel sections : : What am I doing wrong? : : Does anyone have a script to create the /dev tree and move across the kernel and : basic files so I can boot from the fla device? I use mkflash :-). However, I have a client that created a small FreeBSD image from a full image, put that in a tarball. He takes a new DOC, puts it into the system, boots off of floppy/cdrom, uses sysinstall to fdisk and disklabel the disk (I use diskprep), then ftp's the file to the part (using get foo.tar.gz | tar xvfz -). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message