On 5/22/06, ÑîÀÚ <waf dot yang at gmail dot com> wrote:
> After I do this , It's slow when compress this image and when write
> image to cf disk. Other way, I think using entire hardisk that's space
> is 20G, how do I do . If modify count to 20G, the image file will very very
> big and process is very slow.
I don't believe you could actually boot an image that big, unless you
modify how m0n0wall treats its filesystems. As is, it'll extract the
files into RAM at boot, if you actually had 20 GB of files, you'd need
20+ GB RAM.
Not sure why you would want that anyway. There isn't anything in
m0n0wall as is that'll take up any significant amount of disk space.
All the logs are automatically rotated, you'd have to modify how
syslog works to even keep any extra log files (which should never be
kept locally on the firewall anyway, use a syslog server). Only
reason I could see you wanting this is if you added extra software
that needed significant storage space. In that case, you'd need to do
a significant amount of hacking, and would end up with something that
couldn't safely run from a CF.