Regarding committing a machine 24/7 for generating images, have you
thought about running such a machine in VMware? They have released a free
VMware Server product that can be installed on a Linux host (or Windows, but
it would have to be a Windows Server OS, I believe). That way, the machine
could be used for other purposes as well.
From: Manuel Kasper [mailto:mk at neon1 dot net]
Sent: Saturday, March 18, 2006 12:20 PM
To: m0n0wall dash committers at lists dot m0n0 dot ch
Cc: m0n0wall dash dev at lists dot m0n0 dot ch
Subject: [m0n0wall-committers] New changelog file, v1.22, snapshots
I'm preparing for the next m0n0wall release, and as you've probably
noticed, I've finally added the m0n0wall change log file that I've
had lying around on my disk to the repository (in wall/trunk).
If you could add a line to the top of CHANGELOG whenever you make a
change to trunk that isn't completely trivial (like a spelling
correction), I'd be grateful, since I need that information to
compile the change log that gets published on m0n0.ch when a new
release comes out. :)
I've already added entries for everything I've commited to the
repository since 1.21; please add your changes (in a concise format
suitable for end users ;) in there as well.
At this point I'm not sure whether we should release a beta version
(e.g. 1.22b1) or go straight ahead and do a 1.22. Jonathan has made
some extensive captive portal/RADIUS changes, but apparently those
have already received enough testing. Paul, what about the user/group
manager (cool stuff BTW!)?
About the automated build server for nightly snapshots: I've
considered running a job on the m0n0.ch server, but I'm a bit wary of
doing that since it requires running as root (for vnconfig/mdconfig
and to get the permissions right) - unless somebody knows of another
solution for that? Seems a bit wasteful to run a machine 24/7 just
for generating images. ;) Maybe with jail...
Thank you for your help and contributions!