[ previous ] [ next ] [ threads ]
 
 From:  Kendrick Vargas <ken at hudat dot com>
 To:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall-dev] SUGGESTION: M0n0wall flashsize and Recommended memory
 Date:  Fri, 15 Sep 2006 12:00:35 -0400
Lee Sharp wrote:
> From: "Bart Smit" <bit at pipe dot nl>
> 
>> I would hate to see m0n0wall leave the embedded arena.
> 
> Me too.  We have pfsence for that.
> 
>>> People with less memory can still use the current images but people
>>> with the minimum amount can benefit the changes.
> 
>> And lack any important updates and fixes to current code? :-(
> 
> I think you are missing something.  The ram disk can expand a bit and
> still fit in 64meg.  It can expand significantly and still fit in 64meg
> at the cost of live firmware updates.  (You would have to pull and write
> the flash elsewhere.)
> 
>> Rather than leaving the "small memory" people behind, I would suggest
>> a split between an "embedded" and a "non-embedded" version, the latter
>> being a superset of the first, and both being maintained.
> 
> Only so much fits.  I think we can get a little more, but eventually you
> will have to loose live firmware updates.  I think this is not
> catastrophic.
> 
> However, another fork is a bad plan.  m0n0wall is embedded, and pfsence
> is not.  Keep it that way.

Just out of curiosity, is it possible to partition a CF device? I'm asking
this because I bought a 512 meg CF for $5 at best buy (admittedly on
special) and I can't imagine it'd be difficult to get a 32 or 64 meg card
for the same amount somewhere. I also imagine that people out there would
have an easier time upgrading a CF card on their embedded device than the
fixed RAM on board (I've got a net4801, so I understand...)

So my question is, would there be a way to designate the extra space on a CF
device for use as scratch space for storing uploads instead of storing in
memory? Also, if the filesystem on the flashdisk isn't compressed, would it
need to be loaded into a ramdisk to consume memory? Would there be any
performance penalties once the system is booted and the daemons and
libraries are loaded in memory anyway if you're running directly from the
device?

As far as I can tell, only one thing really needs to be writeable on disk
and that's the configuration file. If the filesystem could be uncompressed
and on disk (and have enough extra space included), you could modularize and
"pluginize" the system without having to upload complete new images to write
to the card. Upgrades could be a simple matter of patch uploads instead of
whole new images.

I don't know much about FreeBSD. Only really ever played with linux all my
life, and I'm not even sure that you could do this on linux as I have little
experience putting anything other than a FAT filesystem on a CF card. But if
you could put a disklabel (sp?) on a cf card and create multiple partitions,
it might make life easier. Hell, make it something done right after first
boot... "Configure extra space on device".

Just a thought from a newb.
			-peace