From owner-freebsd-small Sun Apr 2 16:42:11 2000 Delivered-To: freebsd-small@freebsd.org Received: from gateway.int.nomadic.com.au (nomadi.lnk.telstra.net [139.130.54.149]) by hub.freebsd.org (Postfix) with ESMTP id 84AC237BC0F for ; Sun, 2 Apr 2000 16:42:07 -0700 (PDT) (envelope-from greg@nomadic.com.au) Received: from wks47 (wks47.int.nomadic.com.au [192.168.1.47]) by gateway.int.nomadic.com.au (8.9.3/8.8.7) with SMTP id JAA06057 for ; Mon, 3 Apr 2000 09:39:41 +1000 From: "Greg" To: Subject: NFS Date: Mon, 3 Apr 2000 09:36:53 +1000 Message-ID: <000001bf9cfc$53b7a860$2f01a8c0@int.nomadic.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I need to build a number of cheap, low performance floppy boot systems for a production testing environment. I want the machines to boot Linux or FreeBSD from floppy and then use NFS to grab the latest test software from the server. I've experimented with the Linux Router Project's single floppy system but I haven't been able to get NFS working. Has anybody run Pico-BSD as an NFS client ? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Apr 2 18:35:38 2000 Delivered-To: freebsd-small@freebsd.org Received: from www.minix.cx (massive.geek.edu [216.73.11.10]) by hub.freebsd.org (Postfix) with ESMTP id F38D337BB12 for ; Sun, 2 Apr 2000 18:35:23 -0700 (PDT) (envelope-from jontow@www.minix.cx) Received: (from jontow@localhost) by www.minix.cx (8.9.3/8.9.3) id BAA01978; Mon, 3 Apr 2000 01:35:28 GMT (envelope-from jontow) Date: Mon, 3 Apr 2000 01:35:28 +0000 From: Jonathan Towne To: Greg Cc: freebsd-small@freebsd.org Subject: Re: NFS Message-ID: <20000403013528.A1954@minix.cx> References: <000001bf9cfc$53b7a860$2f01a8c0@int.nomadic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <000001bf9cfc$53b7a860$2f01a8c0@int.nomadic.com.au>; from greg@nomadic.com.au on Mon, Apr 03, 2000 at 09:36:53AM +1000 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 03, 2000 at 09:36:53AM +1000, Greg scribbled: # Hello, # I need to build a number of cheap, low performance floppy boot systems for a # production testing environment. # I want the machines to boot Linux or FreeBSD from floppy and then use NFS to # grab the latest test software from the server. [snip] # Has anybody run Pico-BSD as an NFS client ? Yes, as a matter of fact, I did all sorts of fun stuff with it.. things like running XFree86 with KDE and windowmaker and Mozilla, all over NFS.. rather trivial to get working, basically, just get a network connection and "mount_nfs server:path /mountpoint" -- - Jonathan Towne wrongway@slic.com - System/Network Administrator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Apr 3 5:35:15 2000 Delivered-To: freebsd-small@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id DF37437B552; Mon, 3 Apr 2000 05:35:12 -0700 (PDT) (envelope-from sheldonh@FreeBSD.org) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id FAA13486; Mon, 3 Apr 2000 05:35:12 -0700 (PDT) (envelope-from sheldonh@FreeBSD.org) Date: Mon, 3 Apr 2000 05:35:12 -0700 (PDT) From: Message-Id: <200004031235.FAA13486@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-small@FreeBSD.org Subject: Re: misc/17737: Major repair of PicoBSD Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Synopsis: Major repair of PicoBSD Responsible-Changed-From-To: freebsd-bugs->freebsd-small Responsible-Changed-By: sheldonh Responsible-Changed-When: Mon Apr 3 05:34:39 PDT 2000 Responsible-Changed-Why: Over to the maintaining group. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Apr 3 23:16:27 2000 Delivered-To: freebsd-small@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 1CCFB37B813; Mon, 3 Apr 2000 23:16:26 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA87391; Mon, 3 Apr 2000 23:16:25 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 3 Apr 2000 23:16:25 -0700 (PDT) From: Kris Kennaway To: Jonathan Towne Cc: Greg , freebsd-small@freebsd.org Subject: Network booting (Re: NFS) In-Reply-To: <20000403013528.A1954@minix.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Apr 2000, Jonathan Towne wrote: > Yes, as a matter of fact, I did all sorts of fun stuff with it.. things like > running XFree86 with KDE and windowmaker and Mozilla, all over NFS.. rather > trivial to get working, basically, just get a network connection and > "mount_nfs server:path /mountpoint" Changing the subject, but something that would be REALLY COOL to do is to have a PicoBSD floppy which does nothing but establish a secure network connection to a remote server (e.g. over the internet) and downloads signed KLDs, packages, configuration files, etc into a MFS to bootstrap. For example, except for the XF86Config file, you could fairly easily make a "take-anywhere" X client floppy this way. In principle we could even make a bootserver.freebsd.org which hands out such signed components to a client on request (making the regular ports collections packages cryptographically signed would be a good first step). Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 1:48:50 2000 Delivered-To: freebsd-small@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id 1F36137B6C0; Tue, 4 Apr 2000 01:48:41 -0700 (PDT) (envelope-from jon@phoenix.welearn.com.au) Received: (from jon@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id SAA03468; Tue, 4 Apr 2000 18:48:32 +1000 (EST) (envelope-from jon) Date: Tue, 4 Apr 2000 18:48:30 +1000 From: Jonathan Michaels To: Kris Kennaway Cc: freebsd-small@FreeBSD.ORG Subject: Re: Network booting (Re: NFS) Message-ID: <20000404184828.E1768@phoenix.welearn.com.au> Reply-To: jon@welearn.com.au Mail-Followup-To: Kris Kennaway , freebsd-small@FreeBSD.ORG References: <20000403013528.A1954@minix.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Kris Kennaway on Mon, Apr 03, 2000 at 11:16:25PM -0700 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 03, 2000 at 11:16:25PM -0700, Kris Kennaway wrote: > On Mon, 3 Apr 2000, Jonathan Towne wrote: > > > Yes, as a matter of fact, I did all sorts of fun stuff with it.. things like > > running XFree86 with KDE and windowmaker and Mozilla, all over NFS.. rather > > trivial to get working, basically, just get a network connection and > > "mount_nfs server:path /mountpoint" > > Changing the subject, but something that would be REALLY COOL to do is to > have a PicoBSD floppy which does nothing but establish a secure network > connection to a remote server (e.g. over the internet) and downloads > signed KLDs, packages, configuration files, etc into a MFS to bootstrap. > For example, except for the XF86Config file, you could fairly easily make > a "take-anywhere" X client floppy this way. > > In principle we could even make a bootserver.freebsd.org which hands out > such signed components to a client on request (making the regular ports > collections packages cryptographically signed would be a good first step). taking this one step further and to help those who live in climates where th government is some what "cryptographically challanged", given that most countries have (or are having) setup freebsd usergroups that have an attendant array of ftp-, mail-, mailinglist-exploder- -servers and so on it probably wouldn't be that hard to establish (and provide ar mirror driven update), bootserver.au.freebsd.org.au where one could replace the ".au." with the iso id for thier country. this would preclude problems with "importing cryptographic materials which is becoming if not already a serious national criminal offence (punishable with time in prision). this way it is possible to get the stuff you need (i am talking about the whole picture not just the as required services from the bootserver.*) from one clearly identifiable that is clearly and explicitly within the national boundries of the users respective country. also one other side effect would be the lessening of load on teh national gateway servers, well ok not fro them but the enduser might get better performance by not having to use congested routers like mae-east, mae-west etc etc. here in australia we go through mae-west i think and most of teh time ftp's etc drop out is because mae-west is struggleing for breathing space .. ok someting like that. warm regards jonathan please excuse my less than technical explanation i'm having more than my usuall quota of thinking and remembering problems today .. it is so bad that i have noticed that someting is wrong. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 11:16:49 2000 Delivered-To: freebsd-small@freebsd.org Received: from mail3.mmcable.com (fe3.rdc-kc.rr.com [24.94.163.50]) by hub.freebsd.org (Postfix) with ESMTP id 321AC37B6AA for ; Tue, 4 Apr 2000 11:16:46 -0700 (PDT) (envelope-from jss@subatomix.com) Received: from vulcan ([24.27.131.184]) by mail3.mmcable.com with Microsoft SMTPSVC(5.5.1877.357.35); Tue, 4 Apr 2000 13:16:45 -0500 Message-ID: <001f01bf9e6a$3a0b3c00$2aa85c0a@vulcan> From: "Jeffrey S. Sharp" To: "freebsd-small" Subject: Mounting and Corruption Rehashed Date: Tue, 4 Apr 2000 14:16:05 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Let's set the way-back knob to a few months ago. We were discussing the viability of doing the following: * Mounting flash read-only on / * Mounting small MFS filesystems on /var and /tmp * Temporarily remounting / read-write to make changes The problem was this little paragraph from `man mount`: > Switching a filesystem back and forth between asynchronous > and normal op­eration or between read/write and read/only > access using ``mount -u'' may gradually bring about severe > filesystem corruption. Someone spoke up and said that they had actually experienced this corruption. Please excuse me if the following is a dumb question: why even mount the flash _read-only_ in the first place? If /var and /tmp are on separate filesystems (MFS), what write operations are going to happen to the flash that mounting read-only would prevent? Thanks, as always, for any helpful information. =============================== Jeffrey S. Sharp (XorAxAx) jss@subatomix.com -----BEGIN GEEK CODE BLOCK----- Version 3.12 GCS/IT/MU d-@ s-:+ a21 C++(++++) UBL+(+++$)> P L+(+++$)> E+> W++ N+(++) o? K? w++$> !O M(-) !V PS+ PE Y PGP- t+ 5 X+ R(+) tv+ b+ DI++(+++) G++ e> h--- r+++ y+++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 11:36:50 2000 Delivered-To: freebsd-small@freebsd.org Received: from cdc.net (server1.cdc.net [207.244.0.12]) by hub.freebsd.org (Postfix) with SMTP id D1DE637B525 for ; Tue, 4 Apr 2000 11:36:33 -0700 (PDT) (envelope-from mwade@cdc.net) Received: (qmail 18195 invoked from network); 4 Apr 2000 18:25:04 -0000 Received: from unknown (HELO cdc.net) (207.244.0.13) by server1.cdc.net with SMTP; 4 Apr 2000 18:25:04 -0000 Received: (qmail 23038 invoked by uid 100); 4 Apr 2000 18:25:04 -0000 Date: Tue, 4 Apr 2000 14:25:03 -0400 (EDT) From: Mike Wade X-Sender: mwade@server2 To: "Jeffrey S. Sharp" Cc: freebsd-small Subject: Re: Mounting and Corruption Rehashed In-Reply-To: <001f01bf9e6a$3a0b3c00$2aa85c0a@vulcan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Apr 2000, Jeffrey S. Sharp wrote: > Please excuse me if the following is a dumb question: why even mount the > flash _read-only_ in the first place? If /var and /tmp are on separate > filesystems (MFS), what write operations are going to happen to the flash > that mounting read-only would prevent? > > Thanks, as always, for any helpful information. If you ever plan to upgrade the software or store configuration / data on your flash then you obviouslly have to mount rw sometime. Your application may not require this though... --- Mike Wade (mwade@cdc.net) Director of Systems Administration CDC Internet, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 11:37:12 2000 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DD48337B82D for ; Tue, 4 Apr 2000 11:37:06 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA93356; Tue, 4 Apr 2000 12:37:05 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA70239; Tue, 4 Apr 2000 12:36:22 -0600 (MDT) Message-Id: <200004041836.MAA70239@harmony.village.org> To: "Jeffrey S. Sharp" Subject: Re: Mounting and Corruption Rehashed Cc: "freebsd-small" In-reply-to: Your message of "Tue, 04 Apr 2000 14:16:05 CDT." <001f01bf9e6a$3a0b3c00$2aa85c0a@vulcan> References: <001f01bf9e6a$3a0b3c00$2aa85c0a@vulcan> Date: Tue, 04 Apr 2000 12:36:22 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <001f01bf9e6a$3a0b3c00$2aa85c0a@vulcan> "Jeffrey S. Sharp" writes: : Let's set the way-back knob to a few months ago. We were discussing the : viability of doing the following: : : * Mounting flash read-only on / : * Mounting small MFS filesystems on /var and /tmp : * Temporarily remounting / read-write to make changes : : The problem was this little paragraph from `man mount`: : : > Switching a filesystem back and forth between asynchronous : > and normal op­eration or between read/write and read/only : > access using ``mount -u'' may gradually bring about severe : > filesystem corruption. : : Someone spoke up and said that they had actually experienced this : corruption. I've not seen corruption. However, I oly change one or two files somewhat infrequently and tend to reboot often when I'm changing the underlying filesystem. : Please excuse me if the following is a dumb question: why even mount the : flash _read-only_ in the first place? If /var and /tmp are on separate : filesystems (MFS), what write operations are going to happen to the flash : that mounting read-only would prevent? The superblock gets updated from time to time. Also, when things are mounted r/o you can power off at any time and know that the filesystem will be stable when you come back. I've had some problems in the past where I've trashed a filesystem that was mounted r/w by doing this at just the wrong time even though there wasn't much activity. Mounting R/O ensures that you don't accidentally do writes as well. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 12:31:12 2000 Delivered-To: freebsd-small@freebsd.org Received: from mail4.mmcable.com (fe4.rdc-kc.rr.com [24.94.163.51]) by hub.freebsd.org (Postfix) with ESMTP id 7B5A837B77C for ; Tue, 4 Apr 2000 12:31:08 -0700 (PDT) (envelope-from jss@subatomix.com) Received: from vulcan ([24.27.131.184]) by mail4.mmcable.com with Microsoft SMTPSVC(5.5.1877.357.35); Tue, 4 Apr 2000 14:31:06 -0500 Message-ID: <005a01bf9e74$9d2bc6b0$2aa85c0a@vulcan> From: "Jeffrey S. Sharp" To: "Warner Losh" Cc: "freebsd-small" References: <001f01bf9e6a$3a0b3c00$2aa85c0a@vulcan> <200004041836.MAA70239@harmony.village.org> Subject: Re: Mounting and Corruption Rehashed Date: Tue, 4 Apr 2000 15:30:27 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : The problem was this little paragraph from `man mount`: > : > : > Switching a filesystem back and forth between asynchronous > : > and normal op­eration or between read/write and read/only > : > access using ``mount -u'' may gradually bring about severe > : > filesystem corruption. > : > : Someone spoke up and said that they had actually > : experienced this corruption. > > I've not seen corruption. However, I oly change one or > two files somewhat infrequently and tend to reboot often > when I'm changing the underlying filesystem. Good. I don't need to change stuff much or often in my application, either. However, as soon as I get something booted using flash as root, I'll do some testing to see if heavy writes + repeated remounting does indeed cause corruption in a DiskOnChip. > The superblock gets updated from time to time. Aye, there's the rub! > Also, when things are mounted r/o you can power off at any > time and know that the filesystem will be stable when you > come back. Aye, there's the other rub! =============================== Jeffrey S. Sharp (XorAxAx) jss@subatomix.com -----BEGIN GEEK CODE BLOCK----- Version 3.12 GCS/IT/MU d-@ s-:+ a21 C++(++++) UBL+(+++$)> P L+(+++$)> E+> W++ N+(++) o? K? w++$> !O M(-) !V PS+ PE Y PGP- t+ 5 X+ R(+) tv+ b+ DI++(+++) G++ e> h--- r+++ y+++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 13:32:35 2000 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E613837BB9B for ; Tue, 4 Apr 2000 13:32:26 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA93695; Tue, 4 Apr 2000 14:32:08 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA70776; Tue, 4 Apr 2000 14:31:24 -0600 (MDT) Message-Id: <200004042031.OAA70776@harmony.village.org> To: "Jeffrey S. Sharp" Subject: Re: Mounting and Corruption Rehashed Cc: "freebsd-small" In-reply-to: Your message of "Tue, 04 Apr 2000 15:30:27 CDT." <005a01bf9e74$9d2bc6b0$2aa85c0a@vulcan> References: <005a01bf9e74$9d2bc6b0$2aa85c0a@vulcan> <001f01bf9e6a$3a0b3c00$2aa85c0a@vulcan> <200004041836.MAA70239@harmony.village.org> Date: Tue, 04 Apr 2000 14:31:24 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <005a01bf9e74$9d2bc6b0$2aa85c0a@vulcan> "Jeffrey S. Sharp" writes: : > Also, when things are mounted r/o you can power off at any : > time and know that the filesystem will be stable when you : > come back. : : Aye, there's the other rub! : My current bouncer box has / mounted ro and is a 48MB flash card with about 20MB of binaries on it. The rest gets nfs mounted. Makes crash recovery fairly easy. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 13:43:25 2000 Delivered-To: freebsd-small@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 3155E37B8D6; Tue, 4 Apr 2000 13:43:24 -0700 (PDT) From: "Jonathan M. Bresler" To: imp@village.org Cc: jss@subatomix.com, freebsd-small@FreeBSD.ORG In-reply-to: <200004042031.OAA70776@harmony.village.org> (message from Warner Losh on Tue, 04 Apr 2000 14:31:24 -0600) Subject: Re: Mounting and Corruption Rehashed Message-Id: <20000404204324.3155E37B8D6@hub.freebsd.org> Date: Tue, 4 Apr 2000 13:43:24 -0700 (PDT) Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My current bouncer box has / mounted ro and is a 48MB flash card with > about 20MB of binaries on it. The rest gets nfs mounted. Makes crash > recovery fairly easy. > > Warner how about sending out at how-to on this?? jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 13:48: 6 2000 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 91B1937B6E1; Tue, 4 Apr 2000 13:48:03 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA93745; Tue, 4 Apr 2000 14:47:53 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA70876; Tue, 4 Apr 2000 14:47:11 -0600 (MDT) Message-Id: <200004042047.OAA70876@harmony.village.org> To: "Jonathan M. Bresler" Subject: Re: Mounting and Corruption Rehashed Cc: jss@subatomix.com, freebsd-small@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 Apr 2000 13:43:24 PDT." <20000404204324.3155E37B8D6@hub.freebsd.org> References: <20000404204324.3155E37B8D6@hub.freebsd.org> Date: Tue, 04 Apr 2000 14:47:10 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000404204324.3155E37B8D6@hub.freebsd.org> "Jonathan M. Bresler" writes: : how about sending out at how-to on this?? What did you have in mind? Right now I create a minimal flash card with just enough of / and /usr to be able to boot, ssh in and do a make install of kernels. The script to do this is still somewhat gross and green. Once you have that, the read only + nfs part is relatively easy (both of these are done via fstab). I suspect you want the former and not the latter, right? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 13:49:13 2000 Delivered-To: freebsd-small@freebsd.org Received: from cdc.net (server1.cdc.net [207.244.0.12]) by hub.freebsd.org (Postfix) with SMTP id E14B637BBF2 for ; Tue, 4 Apr 2000 13:49:05 -0700 (PDT) (envelope-from mwade@cdc.net) Received: (qmail 17488 invoked from network); 4 Apr 2000 20:26:09 -0000 Received: from unknown (HELO cdc.net) (207.244.0.13) by server1.cdc.net with SMTP; 4 Apr 2000 20:26:09 -0000 Received: (qmail 23337 invoked by uid 100); 4 Apr 2000 20:26:09 -0000 Date: Tue, 4 Apr 2000 16:26:09 -0400 (EDT) From: Mike Wade X-Sender: mwade@server2 To: "Jeffrey S. Sharp" Cc: freebsd-small Subject: Re: Mounting and Corruption Rehashed In-Reply-To: <005a01bf9e74$9d2bc6b0$2aa85c0a@vulcan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Apr 2000, Jeffrey S. Sharp wrote: > Good. I don't need to change stuff much or often in my application, > either. However, as soon as I get something booted using flash as root, > I'll do some testing to see if heavy writes + repeated remounting does > indeed cause corruption in a DiskOnChip. I've experienced file system corruption with the DiskOnChip while toggling back and forth between mount ro -> rw -> ro. All of my file data was mysteriously replaced with NULL's. Please let me know your findings though. =) > > The superblock gets updated from time to time. > > Aye, there's the rub! > > > Also, when things are mounted r/o you can power off at any > > time and know that the filesystem will be stable when you > > come back. > > Aye, there's the other rub! From my understanding a journaling filesystem would help out but does not exist yet on FreeBSD. Would the soft updates feature help any with preventing corruption due to reboots? --- Mike Wade (mwade@cdc.net) Director of Systems Administration CDC Internet, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 13:59:36 2000 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DF1EB37BAE0 for ; Tue, 4 Apr 2000 13:59:30 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA93813; Tue, 4 Apr 2000 14:59:28 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA71025; Tue, 4 Apr 2000 14:58:45 -0600 (MDT) Message-Id: <200004042058.OAA71025@harmony.village.org> To: Mike Wade Subject: Re: Mounting and Corruption Rehashed Cc: "Jeffrey S. Sharp" , freebsd-small In-reply-to: Your message of "Tue, 04 Apr 2000 16:26:09 EDT." References: Date: Tue, 04 Apr 2000 14:58:45 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Mike Wade writes: : I've experienced file system corruption with the DiskOnChip while toggling : back and forth between mount ro -> rw -> ro. All of my file data was : mysteriously replaced with NULL's. Please let me know your findings : though. =) We've had similar corruptions on DiskOnChip w/o the ro -> rw -> ro junk :-(. : >From my understanding a journaling filesystem would help out but does not : exist yet on FreeBSD. Would the soft updates feature help any with : preventing corruption due to reboots? I don't think it would. However, I don't think that we can enable soft updates in our product w/o sending money to Kirk. And even if we didn't need to, the thing is RO for 99.9999% of the time so it wouldn't be worth it to include in our kernels in these embedded things. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 14:20: 5 2000 Delivered-To: freebsd-small@freebsd.org Received: from cdc.net (server1.cdc.net [207.244.0.12]) by hub.freebsd.org (Postfix) with SMTP id 4A20D37BA92 for ; Tue, 4 Apr 2000 14:20:00 -0700 (PDT) (envelope-from mwade@cdc.net) Received: (qmail 12023 invoked from network); 4 Apr 2000 21:07:07 -0000 Received: from unknown (HELO cdc.net) (207.244.0.13) by server1.cdc.net with SMTP; 4 Apr 2000 21:07:07 -0000 Received: (qmail 23433 invoked by uid 100); 4 Apr 2000 21:07:07 -0000 Date: Tue, 4 Apr 2000 17:07:07 -0400 (EDT) From: Mike Wade X-Sender: mwade@server2 To: Warner Losh Cc: freebsd-small Subject: Re: Mounting and Corruption Rehashed In-Reply-To: <200004042058.OAA71025@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Apr 2000, Warner Losh wrote: > We've had similar corruptions on DiskOnChip w/o the ro -> rw -> ro > junk :-(. Interesting... Any idea if it was software or hardware related? Any details? How are you protecting yourself from corruption? =) > I don't think it would. However, I don't think that we can enable > soft updates in our product w/o sending money to Kirk. And even if we > didn't need to, the thing is RO for 99.9999% of the time so it > wouldn't be worth it to include in our kernels in these embedded > things. I forgot about the soft update license, oh well... Perhaps what really is needed is a minimal flash file system for people like myself who need to be able to update the flash for configuration data. Currently I have a separate partition on flash for RW... --- Mike Wade (mwade@cdc.net) Director of Systems Administration CDC Internet, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 14:27:50 2000 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D2D7E37B99D for ; Tue, 4 Apr 2000 14:27:45 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA93948; Tue, 4 Apr 2000 15:27:40 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA71322; Tue, 4 Apr 2000 15:26:58 -0600 (MDT) Message-Id: <200004042126.PAA71322@harmony.village.org> To: Mike Wade Subject: Re: Mounting and Corruption Rehashed Cc: freebsd-small In-reply-to: Your message of "Tue, 04 Apr 2000 17:07:07 EDT." References: Date: Tue, 04 Apr 2000 15:26:57 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Mike Wade writes: : > We've had similar corruptions on DiskOnChip w/o the ro -> rw -> ro : > junk :-(. : : Interesting... Any idea if it was software or hardware related? Any : details? How are you protecting yourself from corruption? =) We don't know. There were some bad chips a while ago that has been corrected. We don't know if these chips were just bad, or if there was a software problem. As for what we're doing to protect ourselves... We're migrating to using a CF <-> IDE adapter that we're building ourselves. Even doing this, we have a cost advantage over DOC given that the DOC prices haven't been falling at the same rate as CF has. : be able to update the flash for configuration data. Currently I have a : separate partition on flash for RW... That's what we do too. We have two partitions to make sure that we can switch over to the other one if we wear out the first partition. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 14:44: 5 2000 Delivered-To: freebsd-small@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 2899C37B776 for ; Tue, 4 Apr 2000 14:44:02 -0700 (PDT) (envelope-from de.ron.g@skynet.be) Received: from bs904928 (dialup1420.antwerpen.skynet.be [194.78.226.140]) by trinity.skynet.be (Postfix) with SMTP id E0FDA18767 for ; Tue, 4 Apr 2000 23:11:29 +0200 (MET DST) Message-ID: <000c01bf9e79$d0ab9380$8ce24ec2@skynet.be> From: "De Ron Geert" To: Subject: problem Date: Tue, 4 Apr 2000 23:07:39 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01BF9E8A.930F6B80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0009_01BF9E8A.930F6B80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I can't get the picoBSD on a floppy. I downloaded rawrite.exe and = fdimage.exe and I typed C:\windows\dektop fdimage.exe pb_en-R.bin a: What do I wrong? Greetz, Geert ------=_NextPart_000_0009_01BF9E8A.930F6B80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I can't get the picoBSD on a floppy. I = downloaded=20 rawrite.exe and fdimage.exe
and I typed C:\windows\dektop = fdimage.exe=20 pb_en-R.bin a:
What do I wrong?
 
Greetz,
Geert
------=_NextPart_000_0009_01BF9E8A.930F6B80-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Apr 4 19:22:55 2000 Delivered-To: freebsd-small@freebsd.org Received: from lepton.subatomix.com (okc-224-168.mmcable.com [24.94.224.168]) by hub.freebsd.org (Postfix) with ESMTP id 7A09037BC01 for ; Tue, 4 Apr 2000 19:22:51 -0700 (PDT) (envelope-from jss@lepton.subatomix.com) Received: from localhost (jss@localhost) by lepton.subatomix.com (8.9.3/8.9.3) with ESMTP id VAA30269; Tue, 4 Apr 2000 21:25:13 -0500 (CDT) (envelope-from jss@lepton.subatomix.com) Date: Tue, 4 Apr 2000 21:25:13 -0500 (CDT) From: "Jeffrey S. Sharp" To: Mike Wade Cc: freebsd-small Subject: Re: Mounting and Corruption Rehashed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Apr 2000, Mike Wade wrote: > > as soon as I get something booted using flash as root, > > I'll do some testing to see if heavy writes + repeated remounting does > > indeed cause corruption in a DiskOnChip. > > I've experienced file system corruption with the DiskOnChip while toggling > back and forth between mount ro -> rw -> ro. All of my file data was > mysteriously replaced with NULL's. Please let me know your findings > though. =) Only the file data? You were still able to get directory listings? I should know something in about a week or so; classes (yuuuech) have been cutting my work week down, so delays are expected. =============================== Jeffrey S. Sharp (XorAxAx) jss@subatomix.com -----BEGIN GEEK CODE BLOCK----- Version 3.12 GCS/IT/MU d-@ s-:+ a21 C++(++++) UBL+(+++$)> P L+(+++$)> E+> W++ N+(++) o? K? w++$> !O M(-) !V PS+ PE Y PGP- t+ 5 X+ R(+) tv+ b+ DI++(+++) G++ e> h--- r+++ y+++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Apr 5 12:34:40 2000 Delivered-To: freebsd-small@freebsd.org Received: from ns1.a-znet.com (ns1.a-znet.com [209.177.29.3]) by hub.freebsd.org (Postfix) with ESMTP id ACA3337B8EC for ; Wed, 5 Apr 2000 12:34:37 -0700 (PDT) (envelope-from klmac@a-znet.com) Received: from klmac.a-znet.com (client22.a-znet.com [209.177.29.22]) by ns1.a-znet.com (8.9.3/8.9.3) with ESMTP id PAA55729 for ; Wed, 5 Apr 2000 15:34:43 -0400 (EDT) (envelope-from klmac@a-znet.com) Message-Id: <4.3.0.20000405153343.00b2c4e0@mail.a-znet.com> X-Sender: klmac@mail.a-znet.com X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Wed, 05 Apr 2000 15:33:58 -0400 To: freebsd-small@freebsd.org From: Ken McKittrick Subject: 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 subscribe Ken McKittrick Network Engineer A-Znet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 6 6:42:52 2000 Delivered-To: freebsd-small@freebsd.org Received: from janus.hosting4u.net (janus.hosting4u.net [209.15.2.37]) by hub.freebsd.org (Postfix) with SMTP id 57C9D37BF8D for ; Thu, 6 Apr 2000 06:42:49 -0700 (PDT) (envelope-from albert@achtung.com) Received: (qmail 21067 invoked from network); 6 Apr 2000 13:42:47 -0000 Received: from mercury.hosting4u.net (HELO achtung.com) (209.15.2.5) by janus.hosting4u.net with SMTP; 6 Apr 2000 13:42:47 -0000 Received: from psylocke ([63.212.134.111]) by achtung.com ; Thu, 06 Apr 2000 08:42:43 -0500 From: "Albert Yang" To: freebsd-small Date: Thu, 6 Apr 2000 06:42:31 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: New Builds of PicoBSD References: <200004042058.OAA71025@harmony.village.org> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12b) Message-ID: <95502856401@mercury.hosting4u.net> Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think whomever has new builds (that work) of PicoBSD should post it on the website. It's fine that we all sit here and tweak the thing with patches here and there, but the community that is not part of this mailing list is not benefiting. So again, someone have access to the website want to maintain it? Let's get this project more underway! Albert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 6 8:37:43 2000 Delivered-To: freebsd-small@freebsd.org Received: from relais1.steria.fr (relais1.steria.fr [193.104.139.252]) by hub.freebsd.org (Postfix) with ESMTP id C49D237C1C2 for ; Thu, 6 Apr 2000 08:37:39 -0700 (PDT) (envelope-from Bruno.Levy@steria.fr) Received: from mail.velizy.net.steria.fr ([168.0.16.223]) by relais1.steria.fr (Netscape Messaging Server 3.62) with ESMTP id 302 for ; Thu, 6 Apr 2000 17:43:06 +0200 Received: from steria.fr ([10.2.74.22]) by mail.velizy.net.steria.fr (Netscape Messaging Server 3.62) with ESMTP id 84 for ; Thu, 6 Apr 2000 17:42:39 +0200 Message-ID: <38ECAF23.FC94628C@steria.fr> Date: Thu, 06 Apr 2000 17:37:07 +0200 From: "Bruno LEVY" Organization: Steria X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: Free BSD 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 DiskOnChip of 32 MB and need a UNIX environment to run 3 small programmes communicating through sockets. Does Pico BSD does it ? Does it do multithreaded ? How much space does it need on disk and RAM ? I also have an EPROM of 8MB, can I use it ? Can it access RS 232 interface ? Many thanks in advance for your responses -- Bruno LEVY Steria Transport Tel +33 1 34 88 63 85 Mobile +33 6 15 15 27 08 Fax +33 1 34 88 63 80 e-mail bruno.levy@steria.fr (-; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 6 8:54: 0 2000 Delivered-To: freebsd-small@freebsd.org Received: from hydrant.intranova.net (hydrant.intranova.net [209.201.95.10]) by hub.freebsd.org (Postfix) with SMTP id ADD7937C052 for ; Thu, 6 Apr 2000 08:53:53 -0700 (PDT) (envelope-from oogali@intranova.net) Received: (qmail 57073 invoked from network); 6 Apr 2000 15:58:28 -0000 Received: from localhost.vdi.net (HELO localhost) (missnglnk@127.0.0.1) by localhost.vdi.net with SMTP; 6 Apr 2000 15:58:28 -0000 Date: Thu, 6 Apr 2000 11:58:28 -0400 (EDT) From: Omachonu Ogali To: Albert Yang Cc: freebsd-small Subject: Re: New Builds of PicoBSD In-Reply-To: <95502856401@mercury.hosting4u.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The purpose of creating the patches was to get PicoBSD working again, which it does, now the patches are waiting for review before they are committed, so if you don't try, review, or give feedback on the patch, PicoBSD will continue to sit there. On Thu, 6 Apr 2000, Albert Yang wrote: > I think whomever has new builds (that work) of PicoBSD should post it > on the website. It's fine that we all sit here and tweak the thing > with patches here and there, but the community that is not part of > this mailing list is not benefiting. > > So again, someone have access to the website want to maintain it? > > Let's get this project more underway! > > Albert > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message > -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 6 8:58:37 2000 Delivered-To: freebsd-small@freebsd.org Received: from green.wl.vg (green.wl.vg [204.200.26.138]) by hub.freebsd.org (Postfix) with ESMTP id 4249437BEA5; Thu, 6 Apr 2000 08:58:35 -0700 (PDT) (envelope-from patrick@whetstonelogic.com) Received: from whetstonelogic.com (patrick [205.252.46.171]) by green.wl.vg (8.9.3/8.9.3) with ESMTP id IAA03351; Thu, 6 Apr 2000 08:58:32 -0700 (PDT) (envelope-from patrick@whetstonelogic.com) Message-ID: <38ECB360.9464DE36@whetstonelogic.com> Date: Thu, 06 Apr 2000 11:55:12 -0400 From: Patrick Gardella Organization: Whetstone Logic, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Albert Yang , freebsd-small@freebsd.org, abial@freebsd.org Subject: Re: New Builds of PicoBSD References: <200004042058.OAA71025@harmony.village.org> <95502856401@mercury.hosting4u.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Albert Yang wrote: > > I think whomever has new builds (that work) of PicoBSD should post it > on the website. It's fine that we all sit here and tweak the thing > with patches here and there, but the community that is not part of > this mailing list is not benefiting. > > So again, someone have access to the website want to maintain it? > > Let's get this project more underway! I can do this. I'm thinking we put the 3.4-STABLE builds on the web site, rather than the 4.0, or -CURRENT builds, since they tend to be large. I'll build the standard ones and put them on the site, if this is ok with Abial (the current maintainer who has been trying to hand this off for a while ;) Patrick ---------- Patrick Gardella patrick@whetstonelogic.com VP-Technology patrick@freebsd.org Whetstone Logic, Inc. This space intentionally left blank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 6 9:24:53 2000 Delivered-To: freebsd-small@freebsd.org Received: from loki.dyn.ez-ip.net (h24-66-207-153.xx.wave.shaw.ca [24.66.207.153]) by hub.freebsd.org (Postfix) with ESMTP id 9AADC37BC0B; Thu, 6 Apr 2000 09:24:50 -0700 (PDT) (envelope-from neo@loki.dyn.ez-ip.net) Received: from localhost (localhost [[UNIX: localhost]]) by loki.dyn.ez-ip.net (8.9.3/8.9.3) id KAA03587; Thu, 6 Apr 2000 10:24:31 -0600 From: dreamwvr Reply-To: dreamwvr@dreamwvr.com Organization: dreamwvr.com To: Patrick Gardella , Albert Yang , freebsd-small@freebsd.org, abial@freebsd.org Subject: Re: New Builds of PicoBSD Date: Thu, 6 Apr 2000 10:17:07 -0600 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <200004042058.OAA71025@harmony.village.org> <95502856401@mercury.hosting4u.net> <38ECB360.9464DE36@whetstonelogic.com> In-Reply-To: <38ECB360.9464DE36@whetstonelogic.com> MIME-Version: 1.0 Message-Id: <0004061024301R.01192@loki.dyn.ez-ip.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, correctomundo .. i gave Pico a try but certainly was able to boot it and so on and get the network up but got a error that i did not have enough ramdisk left but since i don't use FreeBSD at all till now this is quite difficult to adjust. this is due to the fact the the password could not be changed since there was a disk write problem due to ramdisk being full. Solution simply pulled down OpenBSD and built it over the I. still curious about Pico though. nowhere did i find on the Pico site howtos for someone that hits these problems.. first time off. Whereas Linux has LRP which takes about 5-10 minutes to bring up first time around. just food for thought:-)) > > I think whomever has new builds (that work) of PicoBSD should post it > > on the website. It's fine that we all sit here and tweak the thing > > with patches here and there, but the community that is not part of > > this mailing list is not benefiting. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 6 10:29:55 2000 Delivered-To: freebsd-small@freebsd.org Received: from janus.hosting4u.net (janus.hosting4u.net [209.15.2.37]) by hub.freebsd.org (Postfix) with SMTP id D24A937B881 for ; Thu, 6 Apr 2000 10:29:51 -0700 (PDT) (envelope-from albert@achtung.com) Received: (qmail 18597 invoked from network); 6 Apr 2000 17:29:50 -0000 Received: from mercury.hosting4u.net (HELO achtung.com) (209.15.2.5) by janus.hosting4u.net with SMTP; 6 Apr 2000 17:29:50 -0000 Received: from achtung.com ([207.13.193.130]) by achtung.com ; Thu, 06 Apr 2000 12:29:45 -0500 Message-ID: <38ECBBDC.416550EE@achtung.com> Date: Thu, 06 Apr 2000 09:31:24 -0700 From: Albert Yang X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20smp i686) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-small@freebsd.org Subject: Re: New Builds of PicoBSD References: <200004042058.OAA71025@harmony.village.org> <95502856401@mercury.hosting4u.net> <38ECB360.9464DE36@whetstonelogic.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm all for the write, patch, test, feedback, make better process. But if I'm behind on reading the list, or delete an email here or there on accident, then I'm lost as all the patches go flying by. All I'm saying is, if post-patched pico disks are posted on the site, then we can ALL test them and have some sort of version control (sort of) on it. I'd hate to test something, and post it as a problem, and have someone else email me saying "This was fixed in the patch" and I reply with "which patch?" etc... That's not a good feedback cycle. Thanks for the offer Patrick. We need a lot of documentation as well.. Albert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 6 10:53:18 2000 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1532E37BE8F for ; Thu, 6 Apr 2000 10:53:15 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA01917; Thu, 6 Apr 2000 11:53:13 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA92405; Thu, 6 Apr 2000 11:52:23 -0600 (MDT) Message-Id: <200004061752.LAA92405@harmony.village.org> To: "Bruno LEVY" Subject: Re: Free BSD Cc: freebsd-small@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 Apr 2000 17:37:07 +0200." <38ECAF23.FC94628C@steria.fr> References: <38ECAF23.FC94628C@steria.fr> Date: Thu, 06 Apr 2000 11:52:23 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38ECAF23.FC94628C@steria.fr> "Bruno LEVY" writes: : I have a DiskOnChip of 32 MB and need a UNIX environment to run 3 small : programmes communicating through sockets. No problem. : Does Pico BSD does it ? It can. however, I'v eused my own "custom" stripts to generate our systems and not bother with PicoBSD. YMMV. : Does it do multithreaded ? It can. : How much space does it need on disk and RAM ? W/o any compression I've been able to get FreeBSD down to about 16MB, which compresses down to about 5MB with gzip. : I also have an EPROM of 8MB, can I use it ? Maybe. You'll need some kind of driver. : Can it access RS 232 interface ? Yes. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 6 11:15:48 2000 Delivered-To: freebsd-small@freebsd.org Received: from hydrant.intranova.net (hydrant.intranova.net [209.201.95.10]) by hub.freebsd.org (Postfix) with SMTP id DBFCA37B969 for ; Thu, 6 Apr 2000 11:15:34 -0700 (PDT) (envelope-from oogali@intranova.net) Received: (qmail 60149 invoked from network); 6 Apr 2000 18:20:16 -0000 Received: from localhost.vdi.net (HELO localhost) (missnglnk@127.0.0.1) by localhost.vdi.net with SMTP; 6 Apr 2000 18:20:16 -0000 Date: Thu, 6 Apr 2000 14:20:15 -0400 (EDT) From: Omachonu Ogali To: Albert Yang Cc: freebsd-small@freebsd.org Subject: Re: New Builds of PicoBSD In-Reply-To: <38ECBBDC.416550EE@achtung.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Apr 2000, Albert Yang wrote: > I'm all for the write, patch, test, feedback, make better process. But > if I'm behind on reading the list, or delete an email here or there on > accident, then I'm lost as all the patches go flying by. > > All I'm saying is, if post-patched pico disks are posted on the site, > then we can ALL test them and have some sort of version control (sort > of) on it. > > I'd hate to test something, and post it as a problem, and have someone > else email me saying "This was fixed in the patch" and I reply with > "which patch?" etc... That's not a good feedback cycle. I posted the patch to the list, posted it to -current, filed a PR, jhix also sent an email to the list, Greg gave one reply, PR was handed over to the list, and the only feedback I've gotten was from Greg. > Thanks for the offer Patrick. We need a lot of documentation as well.. > > Albert > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message > -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 6 12:48:17 2000 Delivered-To: freebsd-small@freebsd.org Received: from raven.webgroup.ch (webgroup.ch [194.191.122.98]) by hub.freebsd.org (Postfix) with ESMTP id D140837BF4E; Thu, 6 Apr 2000 12:48:09 -0700 (PDT) (envelope-from ast@marabu.ch) Received: (from uucp@localhost) by raven.webgroup.ch (8.9.3/8.9.2/ast-20000114) with UUCP id VAA81620; Thu, 6 Apr 2000 21:48:02 +0200 (CEST) Received: (from uucp@localhost) by hawk.marabu.ch (8.8.8/8.8.8) with UUCP id VAA28879; Thu, 6 Apr 2000 21:41:02 +0200 (MEST) (envelope-from ast@marabu.ch) Received: by marabu.marabu.ch (8.7.5/990131-ast-8.0) id VAA08298; Thu, 6 Apr 2000 21:39:24 +0200 (CEST) Message-Id: <200004061939.VAA08298@marabu.marabu.ch> MIME-Version: 1.0 (NeXT Mail 3.3 v124.8483.6) Content-Type: text/plain In-Reply-To: <200004042047.OAA70876@harmony.village.org> X-Nextstep-Mailer: Mail 3.3 (Enhance 2.0b6) Received: by NeXT.Mailer (1.124.8483.6) From: Adrian Steinmann Date: Thu, 6 Apr 2000 21:39:23 +0200 To: freebsd-small@FreeBSD.ORG Subject: Re: Mounting and Corruption Rehashed Cc: "Jonathan M. Bresler" , jss@subatomix.com, Warner Losh References: <20000404204324.3155E37B8D6@hub.freebsd.org> <200004042047.OAA70876@harmony.village.org> X-Organization: Steinmann Consulting, Apollostrasse 21, 8032 Zurich X-Phone-Numbers: Switzerland, Tel +41 1 380 30 83 Fax +41 1 380 30 85 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello small free-bsd-ers! "Jonathan M. Bresler" recently asked: : how about sending out at how-to on this?? I can't stand lurking anymore, so here goes: This is my special /etc/rc.conf: root_rw_mount=NO rootdev=fla0 diskless_mount=/etc/rc.readonly etc_size=1536 home_size=1024 var_size=32768 and this is my special /etc/rc.readonly: if [ -f /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf elif [ -f /etc/rc.conf ]; then . /etc/rc.conf fi echo -n "Making writable mfs filesystems:" mount_mfs -s ${var_size:=65536} -T qp120at dummy /var while [ -e /var/.readonly ]; do sleep 1; done for d in root log run db msgs cron cron/tabs spool spool/mqueue \ tmp tmp/vi.recover at at/jobs at/spool do mkdir /var/$d && chmod 755 /var/$d done chmod 755 /var chmod 1777 /var/tmp /var/tmp/vi.recover chown daemon /var/at/jobs /var/at/spool touch /var/run/utmp && chmod 644 /var/run/utmp touch /var/log/wtmp && chmod 664 /var/log/wtmp (cd /root && tar cBf - . | (cd /var/root && tar xBf -)) echo -n " var" cp /dev/MAKEDEV /var/tmp mount_mfs -s 256 -i 512 -T qp120at dummy /dev while [ -f /dev/.readonly ]; do sleep 1; done cp /var/tmp/MAKEDEV /dev && rm -f /var/tmp/MAKEDEV cd /dev && sh MAKEDEV std ${rootdev} ${rootdev}s1h vty12 pty0 ttyd0 ttyd1 echo -n " dev" for d in etc home do (cd /$d && tar cBf - .) > /var/tmp/$d.tar eval mount_mfs -s \${${d}_size:=1024} -T qp120at dummy /$d while [ -e /$d/.readonly ]; do sleep 1; done (cd /$d && tar xBf /var/tmp/$d.tar) rm -f /var/tmp/$d.tar && echo -n " $d" done echo You should see this when you come up: $ mount -p /dev/fla0s1a / ufs ro 1 1 mfs:28 /var mfs rw,async 0 0 mfs:73 /dev mfs rw,async 0 0 mfs:816 /etc mfs rw,async 0 0 mfs:822 /home mfs rw,async 0 0 It's not so surprising that by turning just those two knobs we have a flash system which doesn't gradually self destruct since its mounted read-only. When you remount / rread-write to update, just reboot and get on with it (remounting ro works, but can we trust it?). Shall we get /etc/rc.readonly and a special /etc/rc.conf section mentioning "how to" put into the main distribution? _________________________________________________________________________ Dr. Adrian Steinmann Steinmann Consulting Apollostrasse 21 8032 Zurich Tel +41 1 380 30 83 Fax +41 1 380 30 85 Mailto:ast@marabu.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Apr 6 14:40: 8 2000 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1005437BC97; Thu, 6 Apr 2000 14:40:02 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA02839; Thu, 6 Apr 2000 15:39:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA93728; Thu, 6 Apr 2000 15:39:02 -0600 (MDT) Message-Id: <200004062139.PAA93728@harmony.village.org> To: Adrian Steinmann Subject: Re: Mounting and Corruption Rehashed Cc: freebsd-small@FreeBSD.ORG, "Jonathan M. Bresler" , jss@subatomix.com In-reply-to: Your message of "Thu, 06 Apr 2000 21:39:23 +0200." <200004061939.VAA08298@marabu.marabu.ch> References: <200004061939.VAA08298@marabu.marabu.ch> <20000404204324.3155E37B8D6@hub.freebsd.org> <200004042047.OAA70876@harmony.village.org> Date: Thu, 06 Apr 2000 15:39:02 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004061939.VAA08298@marabu.marabu.ch> Adrian Steinmann writes: : Shall we get /etc/rc.readonly and a special /etc/rc.conf section : mentioning "how to" put into the main distribution? We use a similarlly hacked rc.diskless2. I think that we may need to come up with an easier way of doing this so we don't have to keep doing the hacking of this custom script. I like the idea of putting information like this into the handbook. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Apr 7 7:13: 0 2000 Delivered-To: freebsd-small@freebsd.org Received: from mail.nortenet.pt (mar.nortenet.pt [212.13.32.243]) by hub.freebsd.org (Postfix) with ESMTP id ED19C37C2A8 for ; Fri, 7 Apr 2000 07:12:55 -0700 (PDT) (envelope-from mrwho@softhome.net) Received: from slaughterhouse (coi1-pppS6.nortenet.pt [212.13.36.6]) by mail.nortenet.pt (8.9.3/8.9.3) with SMTP id PAA07259 for ; Fri, 7 Apr 2000 15:16:35 +0100 Message-Id: <4.1.20000407064125.00a93b80@pop.softhome.net> Message-Id: <4.1.20000407064125.00a93b80@pop.softhome.net> X-Sender: mrwho@pop.softhome.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 07 Apr 2000 06:44:07 +0100 To: freebsd-small@freebsd.org From: MrWho Subject: Newbie: Configure router Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, it goes something like this: Downloaded the Router version of the disk (I figured that, since I want to put my trusty old 486 as a router for my other 3 machines, I should use that version - correct me if I'm wrong here), made the disk with fdimage, booted my diskless 486 with the disk and it worked. Cool. Now let's configure this... What? No editor? So, how does a guy that has no working machine running FreeBSD/Linux/whatever (only windows machines here) does to edit the configuration files? Thanks for all the help. =============================================== Fausto Paiva, a.k.a. MrWho, a.k.a DareSan "You do not need a parachute to skydive! You only need a parachute to skydive twice..." =============================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Apr 7 9:52:33 2000 Delivered-To: freebsd-small@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 38B8F37B61B; Fri, 7 Apr 2000 09:49:45 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 3DF382DC0A; Fri, 7 Apr 2000 18:53:37 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id A22E17811; Fri, 7 Apr 2000 18:47:44 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 9DB7F10E17; Fri, 7 Apr 2000 18:47:44 +0200 (CEST) Date: Fri, 7 Apr 2000 18:47:44 +0200 (CEST) From: Andrzej Bialecki To: Patrick Gardella Cc: Albert Yang , freebsd-small@freebsd.org, abial@freebsd.org Subject: Re: New Builds of PicoBSD In-Reply-To: <38ECB360.9464DE36@whetstonelogic.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Apr 2000, Patrick Gardella wrote: > Albert Yang wrote: > > > > I think whomever has new builds (that work) of PicoBSD should post it > > on the website. It's fine that we all sit here and tweak the thing > > with patches here and there, but the community that is not part of > > this mailing list is not benefiting. > > > > So again, someone have access to the website want to maintain it? > > > > Let's get this project more underway! > > I can do this. I'm thinking we put the 3.4-STABLE builds on the web > site, rather than the 4.0, or -CURRENT builds, since they tend to be > large. > > I'll build the standard ones and put them on the site, if this is ok > with Abial (the current maintainer who has been trying to hand this off > for a while ;) Yes, please do that. Contact me privately for the details. Thanks! Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Apr 7 14:38:59 2000 Delivered-To: freebsd-small@freebsd.org Received: from mail3.mmcable.com (fe3.rdc-kc.rr.com [24.94.163.50]) by hub.freebsd.org (Postfix) with ESMTP id 894FE37BBB0 for ; Fri, 7 Apr 2000 14:38:50 -0700 (PDT) (envelope-from jss@subatomix.com) Received: from vulcan ([24.27.131.184]) by mail3.mmcable.com with Microsoft SMTPSVC(5.5.1877.357.35); Fri, 7 Apr 2000 16:38:48 -0500 Message-ID: <00bb01bfa0d9$92a27150$2aa85c0a@vulcan> From: "Jeffrey S. Sharp" To: Cc: "Jonathan M. Bresler" , "Warner Losh" , "Adrian Steinmann" References: <20000404204324.3155E37B8D6@hub.freebsd.org> <200004042047.OAA70876@harmony.village.org> <200004061939.VAA08298@marabu.marabu.ch> Subject: Re: Mounting and Corruption Rehashed Date: Fri, 7 Apr 2000 16:38:10 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When you remount / rread-write to update, just reboot and get on > with it (remounting ro works, but can we trust it?). I've done a similar hack by hand and it worked well. However, problems arise when changes have to be made often or when uptime requirements prohibit rebooting unless direly urgent. I have another possible solution to the flash problem: Use two partitions: one for /, kernel, and other static files that stays ro unless you are upgrading, and another for dynamic files that gets switched ro<-->rw. To detect any corruption, compare before-and-after checksums on the dynamic files. If corruption is detected, the partition can get newfs'ed, etc., and the have its files restored from somewhere else (a backup partition, maybe). Also, If you've got some custom application running, it might be prudent for it to keep its writes down by buffering data as long as possible. Or, someone could fix mount... [hint] =============================== Jeffrey S. Sharp (XorAxAx) jss@subatomix.com -----BEGIN GEEK CODE BLOCK----- Version 3.12 GCS/IT/MU d-@ s-:+ a21 C++(++++) UBL+(+++$)> P L+(+++$)> E+> W++ N+(++) o? K? w++$> !O M(-) !V PS+ PE Y PGP- t+ 5 X+ R(+) tv+ b+ DI++(+++) G++ e> h--- r+++ y+++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Apr 8 3:37:21 2000 Delivered-To: freebsd-small@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 66EB037B59A for ; Sat, 8 Apr 2000 03:37:15 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id LAA32094 for freebsd-small@freebsd.org; Sat, 8 Apr 2000 11:36:23 +0100 (BST) (envelope-from nik) Date: Sat, 8 Apr 2000 11:36:22 +0100 From: Nik Clayton To: freebsd-small@freebsd.org Subject: Unified Configuration Interface Project / Slashdot Message-ID: <20000408113621.A31474@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Organization: Slashdot Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, (I'm not subscribed, please cc: replies to me) I've just stumbled across http://www.freebsd.org/~picobsd/picobsd/doc/UCI.html Is this project still under active development? If so, would someone be willing to collaborate with me on a Slashdot story about it? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Apr 8 6:19:45 2000 Delivered-To: freebsd-small@freebsd.org Received: from mobile.webweaving.org (va-138.skylink.it [194.185.55.138]) by hub.freebsd.org (Postfix) with ESMTP id 084E837B63A for ; Sat, 8 Apr 2000 06:19:41 -0700 (PDT) (envelope-from dirkx@mobile.webweaving.org) Received: (from dirkx@localhost) by mobile.webweaving.org (8.9.3/8.9.3) id PAA00813; Fri, 7 Apr 2000 15:39:19 +0200 (CEST) (envelope-from dirkx) Date: Fri, 7 Apr 2000 15:39:19 +0200 (CEST) From: Dirk-Willem van Gulik X-Sender: dirkx@vaio.ispra.webweaving.org To: Bruno LEVY Cc: freebsd-small@FreeBSD.ORG Subject: Re: Free BSD In-Reply-To: <38ECAF23.FC94628C@steria.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Apr 2000, Bruno LEVY wrote: > I have a DiskOnChip of 32 MB and need a UNIX environment to run 3 small > programmes communicating through sockets. > > Does Pico BSD does it ? Yes.. but it might be overkill. A simple stripped down install would propably do just as well. > Does it do multithreaded ? Yes. > How much space does it need on disk and RAM ? That 32Mb is fine. Expect at least 4Mb if not 8 Mb to do something usefull. Smaller than that and you propably end up using some rom dos or something similar. > I also have an EPROM of 8MB, can I use it ? It would need a small driver. I am not sure those exist. I am not aware of any. > Can it access RS 232 interface ? Yes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Apr 8 6:20:42 2000 Delivered-To: freebsd-small@freebsd.org Received: from mobile.webweaving.org (va-138.skylink.it [194.185.55.138]) by hub.freebsd.org (Postfix) with ESMTP id D7FBE37BAC5 for ; Sat, 8 Apr 2000 06:20:38 -0700 (PDT) (envelope-from dirkx@mobile.webweaving.org) Received: (from dirkx@localhost) by mobile.webweaving.org (8.9.3/8.9.3) id IAA04813; Wed, 5 Apr 2000 08:28:00 +0200 (CEST) (envelope-from dirkx) Date: Wed, 5 Apr 2000 08:27:59 +0200 (CEST) From: Dirk-Willem van Gulik X-Sender: dirkx@vaio.ispra.webweaving.org To: De Ron Geert Cc: small@FreeBSD.ORG Subject: Re: problem In-Reply-To: <000c01bf9e79$d0ab9380$8ce24ec2@skynet.be> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Apr 2000, De Ron Geert wrote: > I can't get the picoBSD on a floppy. I downloaded rawrite.exe and fdimage.exe > and I typed C:\windows\dektop fdimage.exe pb_en-R.bin a: ^ > What do I wrong? now what was the error message ? just do RUN command.exe from the Start menu. Type cd C:\windows\Desktop dir rawwrite.exe picoimg.bin a: and mail us the output :-) of tghe error message. Dw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Apr 8 10:30: 4 2000 Delivered-To: freebsd-small@freebsd.org Received: from green.wl.vg (green.wl.vg [204.200.26.138]) by hub.freebsd.org (Postfix) with ESMTP id A4A9137B5DD for ; Sat, 8 Apr 2000 10:29:50 -0700 (PDT) (envelope-from patrick@whetstonelogic.com) Received: from whetstonelogic.com (pathome [209.9.69.194]) by green.wl.vg (8.9.3/8.9.3) with ESMTP id KAA63933; Sat, 8 Apr 2000 10:29:38 -0700 (PDT) (envelope-from patrick@whetstonelogic.com) Message-ID: <38EF6C18.AF10D57C@whetstonelogic.com> Date: Sat, 08 Apr 2000 13:27:52 -0400 From: Patrick Gardella Organization: Whetstone Logic, Inc. X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Nik Clayton Cc: freebsd-small@FreeBSD.ORG Subject: Re: Unified Configuration Interface Project / Slashdot References: <20000408113621.A31474@catkin.nothing-going-on.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nik Clayton wrote: > > Hi guys, > > (I'm not subscribed, please cc: replies to me) > > I've just stumbled across > > http://www.freebsd.org/~picobsd/picobsd/doc/UCI.html > > Is this project still under active development? If so, would someone be > willing to collaborate with me on a Slashdot story about it? No, as far as I know, this has been left on the back burner and is now dried up. Patrick ---------- Patrick Gardella patrick@whetstonelogic.com VP-Technology patrick@freebsd.org Whetstone Logic, Inc. This space intentionally left blank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Apr 8 14:41:45 2000 Delivered-To: freebsd-small@freebsd.org Received: from lepton.subatomix.com (okc-224-168.mmcable.com [24.94.224.168]) by hub.freebsd.org (Postfix) with ESMTP id 012FE37B59C for ; Sat, 8 Apr 2000 14:41:43 -0700 (PDT) (envelope-from jss@lepton.subatomix.com) Received: from localhost (jss@localhost) by lepton.subatomix.com (8.9.3/8.9.3) with ESMTP id QAA39460 for ; Sat, 8 Apr 2000 16:43:46 -0500 (CDT) (envelope-from jss@lepton.subatomix.com) Date: Sat, 8 Apr 2000 16:43:46 -0500 (CDT) From: "Jeffrey S. Sharp" To: freebsd-small Subject: Corruption: My Initial Tests 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 All right, here's some harder evidence. I ran something close to the following on a 3.4-RELEASE system for about 30 minutes against an 8MB DOC2K with a few files on it: #/bin/sh -x while ls; do mount -u -o rw /dev/fla0s1a /mnt cp testfile /mnt mount -u -o ro /dev/fla0s1a /mnt cat /mnt/testfile done When I stopped it, there was no corruption, and fsck reported no problems. 'Course, I didn't run it for days or transfer 6MB files. IMHO, however, I think the corruption Mike experienced was not caused by the mounting thing but was just a firmware/hardware problem. At any rate, we should be putting as much corruption detection/protection as possible into our flash-based applications if they do *any* writing to the flash, as the flash *will* eventually wear out. My apologies if I've beaten this dead penguin...er...horse too much. =============================== Jeffrey S. Sharp (XorAxAx) jss@subatomix.com -----BEGIN GEEK CODE BLOCK----- Version 3.12 GCS/IT/MU d-@ s-:+ a21 C++(++++) UBL+(+++$)> P L+(+++$)> E+> W++ N+(++) o? K? w++$> !O M(-) !V PS+ PE Y PGP- t+ 5 X+ R(+) tv+ b+ DI++(+++) G++ e> h--- r+++ y+++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Apr 8 15:29:46 2000 Delivered-To: freebsd-small@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 9212637B5D3 for ; Sat, 8 Apr 2000 15:29:42 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 070CE2DC07; Sun, 9 Apr 2000 00:33:34 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id DB11D7814; Sun, 9 Apr 2000 00:29:57 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id D6D2510E17; Sun, 9 Apr 2000 00:29:57 +0200 (CEST) Date: Sun, 9 Apr 2000 00:29:57 +0200 (CEST) From: Andrzej Bialecki To: Nik Clayton Cc: freebsd-small@freebsd.org Subject: Re: Unified Configuration Interface Project / Slashdot In-Reply-To: <20000408113621.A31474@catkin.nothing-going-on.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 Sat, 8 Apr 2000, Nik Clayton wrote: > Hi guys, > > (I'm not subscribed, please cc: replies to me) > > I've just stumbled across > > http://www.freebsd.org/~picobsd/picobsd/doc/UCI.html > > Is this project still under active development? If so, would someone be > willing to collaborate with me on a Slashdot story about it? "Project" is too big a name for that. It was just an idea. It still seems interesting, although I would change a lot today... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message