On Tue, May 03, 2005 at 05:48:54AM -0700, cisco4ng wrote:
> my bad. I did see:
>
> Saving old bootmgr.
>
> and then:
>
> Installing new bootmgr.
Curious. After this grabs a copy of the bootmgr and md5s it, then compares
it with the hash of the new one. If they don't match it should whinge - as I
my bad. I did see:
Saving old bootmgr.
and then:
Installing new bootmgr.
I am using IPSO 3.5FCS14 because IPSO 3.7.1 build 004 does NOT work with
IP530 or IP740 with Gig interfaces (IPSO 3.5FCS14 works with Gig interfaces).
I can only use either 3.5 or 3.7.1 build 004 because those are the two
On Tue, May 03, 2005 at 04:03:38AM -0700, cisco4ng wrote:
> Hi,
> I have scripts to automate the firewall building process. First the
> firewall is installed with IPSO 3.5FCS14 mannually from boot manager.
> After that, it is run through scripts to upgrade to IPSO 3.7.1 build 004
> and Checkpoint
Hi,
I have scripts to automate the firewall building process. First the firewall
is installed
with IPSO 3.5FCS14 mannually from boot manager. After that, it is run through
scripts
to upgrade to IPSO 3.7.1 build 004 and Checkpoint NG FP3. I actually saw this
message
from the console output dur
On Sun, May 01, 2005 at 06:11:42AM -0700, cisco4ng wrote:
> All,
>
> I have a Nokia IP650 and I install IPSO 3.5FCS14 at bootmanager from
> scratch. Later on, I install IPSO 3.7.1build004 with the following
> command: "/etc/newimage -k -R -b -l ipso.tgz". By the way ipso.tgz is IPSO
> 3.7.1build 0
All,
I have a Nokia IP650 and I install IPSO 3.5FCS14 at bootmanager from scratch.
Later on,
I install IPSO 3.7.1build004 with the following command: "/etc/newimage -k -R
-b -l ipso.tgz".
By the way ipso.tgz is IPSO 3.7.1build 004.
My understanding is that the option "-b" will force a bootmana
