From owner-freebsd-arch Wed Nov 15 10:15:18 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A7FA37B4CF; Wed, 15 Nov 2000 10:15:16 -0800 (PST) Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id A478F6E2E3C; Wed, 15 Nov 2000 10:15:15 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id KAA27643; Wed, 15 Nov 2000 10:15:02 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda27637; Wed Nov 15 10:14:44 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.1/8.9.1) id eAFIEdw55545; Wed, 15 Nov 2000 10:14:39 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdk55096; Wed Nov 15 10:14:26 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.1/8.9.1) id eAFIEPu56217; Wed, 15 Nov 2000 10:14:25 -0800 (PST) Message-Id: <200011151814.eAFIEPu56217@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdN55772; Wed Nov 15 10:13:36 2000 X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.1.1-RELEASE X-Sender: cy To: Terry Lambert Cc: adrian@FreeBSD.ORG (Adrian Chadd), arch@FreeBSD.ORG Subject: Re: RANDOMDEV inspired realitycheck regarding i386/i486... In-reply-to: Your message of "Wed, 15 Nov 2000 17:38:59 GMT." <200011151739.KAA13021@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Nov 2000 10:13:35 -0800 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011151739.KAA13021@usr01.primenet.com>, Terry Lambert writes: > > > > If no /entropy is found it takes a full minute to do the randomdev > > > > seeding during boot on a P5/133. > > > > > > > > Has anybody run a 486 or 386 under current recently ? > > > > 386'en might still have a place for small embedded products but I'm > > proabably going to be flamed when I say I think FreeBSD-current isn't > > very suited to "embedded 386 with tiny everything" applications. > > That's a problem with FreeBSD-current, not a problem with > "embedded 386 with tiny everything". > > I'm reminded when SVR4s footprint first went to 8M of RAM. > > I also find it amusing that I can get an old SVR4.0.2 ES/MP, > and load it on both SMP boxes, and on 6M 386 boxes, when I > am quickly becoming unable to do the same for FreeBSD-current. > > I guess this is inevitable, as security is increased, since > the most secure computer is one which doesn't run... Garfinkel and Spafford write in their book Practical UNIX and Internet Security that the most secure system is one berried under six feet of dirt. Even then tye didn't think it was 100% secure. :) If may comment about the 386/486 issue. I think it would be nice to continue to support 386/486. I and and ISP I do work for don't have an 386's in production but we do have a handful of 486's in use -- they make great firewalls. I even use a 486DX33 with 20 MB RAM as an X server. If we cannot 386/486, however, that would be unfortunate, as IMO the options for various reasons are inferior. It all depends on what our focus should be. What would really be nice would be some kind of charter or 3 year plan from CORE that outlines their vision of what they think FreeBSD should look at that time. This strawman could be use as a basis of debate to define what we really want. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message