Date: Mon, 18 Dec 2000 18:35:49 -0600 From: "Michael C . Wu" <keichii@iteration.net> To: Warner Losh <imp@village.org> Cc: freebsd-small@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: StrongARM support? Message-ID: <20001218183549.B9025@peorth.iteration.net> In-Reply-To: <200012190021.RAA95681@harmony.village.org>; from imp@village.org on Mon, Dec 18, 2000 at 05:21:27PM -0700 References: <20001218162732.A70076@peorth.iteration.net> <20001218151235.D69041@peorth.iteration.net> <78656.976769151@winston.osd.bsdi.com> <3A3862E4.5A46E14C@wireless.net> <20001218151235.D69041@peorth.iteration.net> <200012182119.OAA94431@harmony.village.org> <20001218162732.A70076@peorth.iteration.net> <200012190021.RAA95681@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 18, 2000 at 05:21:27PM -0700, Warner Losh scribbled: | In message <20001218162732.A70076@peorth.iteration.net> "Michael C . Wu" writes: | : Just an idea/question: | : Can we possibly use crunchgen to generate a big binary for userland tools | : only? Then we can drop in new binaries with ease. | | No. I will not do that. The biggest reason is that it is an | unbelievable PITA to manitain if you have other applications to load | onto the box that are outside of the FreeBSD tree. I tried doing that | once upon a time and found that with shared libraries for everything, | and 16M or larger parts that it wasn't necessary at all since the | savings was so meager. Right, I sensed that maintenance would be a great problem too. It's just a novelty idea. | : However, I think that simply buying a 100mb SANDISK is easier. :) | | If you need 100MB parts, you are doing something wrong. We're running | on 32M parts with 10-20M free depending on the application(s) we layer | onto the device here at Timing Soltuions. And that's without using | filesystem level compression. If we could run only out of memory, | we'd be able to fit on a 8M part with room to spare. I agree with you that 100MB is overkill, but I think the cost has gone down enough to consider even a full powered embedded system with complete documentation and other added functionality. .oO (IRCing from a router...) *joke* Would 20mb be a comfortable target for "make buildsmallworld installsmallworld" ? The build would have to be interactive. And the interactive build can record all the options/choices done by the user for future builds. That leaves room for everyone to use at least 4mb on 24mb CF media, and 12mb on 32mb CF media. | 1.44MB is too small, but 16M is way fat. The base system is a smidge | over 7M. You could trim that to about 6M for standard /etc/rc files | and about 4M if you roll your own and use the tineware tools from | PicoBSD and don't need anything else (eg router, ppp-on-a-stick, | etc). Our application requires a control program that's fairly large | because it has a lot to do, which is why we chose the 32M parts. | Also, for a long time the smallest flash I could build was 16M before I think space for logging, stored backups of updates could be of good use. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001218183549.B9025>