[ previous ] [ next ] [ threads ]
 
 From:  Dinesh Nair <dinesh at alphaque dot com>
 To:  Peer Dicken <peer at dicken dot name>
 Cc:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall-dev] Firmware Upgrade , failure, WRAP
 Date:  Tue, 21 Sep 2004 23:18:04 +0800
On 21/09/2004 18:40 Peer Dicken said the following:
> Well, is there any mechanism to prevent this? I think of a rescue sytem 
> that is started, if the reset button is pushed longer during boot. the 
> machine could then start the rescue system and write a default system to 
> the CF card....

you could partition the CF into two (or more) partitions, and place two (or 
more) m0n0wall images on them. then using the freebsd BootEasy bootmanager 
bootblocks, you'd be presented with an option to select which partition to 
boot off. this way, if you fsck up your main m0n0wall image, you could 
always boot off the second partitition.

for added reliability, you could modify the functions which write 
config.xml to the CF card and have them write to the other partitions as 
well. this would mean that you'd be back up with your same settings et al.

me ? i just keep a few spare CF cards and do regular backups of config.xml. :)

-- 
Regards,                           /\_/\   "All dogs go to heaven."
dinesh at alphaque dot com                (0 0)    http://www.alphaque.com/
+==========================----oOO--(_)--OOo----==========================+
| for a in past present future; do                                        |
|   for b in clients employers associates relatives neighbours pets; do   |
|   echo "The opinions here in no way reflect the opinions of my $a $b."  |
| done; done                                                              |
+=========================================================================+