From owner-freebsd-small Wed Jan 12 10:15:11 2000 Delivered-To: freebsd-small@freebsd.org Received: from ns1.eds.ch (ns1.eds.ch [194.235.48.8]) by hub.freebsd.org (Postfix) with ESMTP id 208AD14D4A; Wed, 12 Jan 2000 10:15:07 -0800 (PST) (envelope-from roberto.Nunnari@agie.ch) Received: from onyx.eds.ch (onyx.eds.ch [206.122.128.224]) by ns1.eds.ch (8.9.3/8.9.3) with ESMTP id TAA21037; Wed, 12 Jan 2000 19:21:16 +0100 (MET) Received: from mailsrv.eds.ch (mailsrv.eds.ch [194.235.174.72] (may be forged)) by onyx.eds.ch (8.9.3/8.9.3) with ESMTP id TAA05143; Wed, 12 Jan 2000 19:19:20 +0100 (MET) Received: from agie.ch ([198.132.159.194]) by mailsrv.eds.ch (Netscape Messaging Server 3.6) with ESMTP id AAA28E5; Wed, 12 Jan 2000 19:12:35 +0100 Message-ID: <387CC4F5.FAB08644@agie.ch> Date: Wed, 12 Jan 2000 19:16:21 +0100 From: "Roberto Nunnari, AGIE" Organization: AGIE X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: freebsd-small@freebsd.org Subject: Re: minimum HW requirement References: <200001121643.IAA02293@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Hi there. > > > > I'd like to use picoBSD in an embedded system with very > > small resorces. It should be a 386 with just 1 or 2 Mb RAM. > > > > The system is a deeply embedded one, with no networking, nor > > graphics, sound, TCPIP, etc... > > > > All it needs would be a multitasking kernel, message queues, > > semaphores, pipes, memory management, I/O system, > > parallel port, and a couple of serial ports. > > > > I'd like to know how hard scaling down picoBSD to fit these > > constraints would be. > > "How long is a piece of string"? Seriously, without knowing what > resources or experience you have available, all that can reasonably be > said is "yes, it's possible". > > There's at least one product I'm aware of using a cut-down FreeBSD on a > 386ex in 2MB of RAM. I think that still has networking in the system too. > I'm used to work with OSs that you can scale down very easily just running a configuration utility or editing some configuration files. There you can choose the functionality you want to include in your OS and what you don't want to include. I never tried to scale down a unix system even though I have a good basilar understanding of unix OS architecture. The question is: - can you just work on the configuration files and choose what to include in picoBSD and what not or you have to go deep into the OS code? - if not, will something similar (configuration utility) be included in FreeBSD 4.0 or later? I just have a FreeBSD 3.2-stable PC I'm playing with and as I very much like it and came across picoBSD, thought I could set it up as my development platform for a project of mine. I was really too much in a hurry when I posted that message, but the question wasn't how long will it take. What I meant (which probably is different from what I said) is that I would be grateful for any hints/links/advice/experiences from the FreeBSD community on scaling down picoBSD. Best regards. -- Roberto Nunnari -software engineer- mailto:roberto.nunnari@agie.ch AGIE - http://www.agie.com Via dei pioppi 16 tel: +41-91-8069138 6616 Losone """ Switzerland (o o) =======================oOO==(_)==OOo======================== MY OPNIONS ARE NOT NECESSARELY THOSE OF MY EMPLOYER To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message