HP3000-L Archives

June 1999, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Gerald R. Dillard" <[log in to unmask]>
Reply To:
Date:
Wed, 16 Jun 1999 13:18:22 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (20 lines)
In a message dated 06/16/1999 12:49:56 PM Eastern Daylight Time,
[log in to unmask] writes:

> On reboot with recovery, the
>  system "loses" IOCONFIG changes that were made in late
>  February and returns to a state current in last August.  When
>  we apply these IOCONFIG changes they CANNOT be written
>  to BOOTUP.SYS because of a security violation as
>  reproduced below.

If you go into SYSGEN and set the base configuration group to CONFIG, you
should be able to observe changes that have been made to the system
configuration via IOCONFIG.  The changes have not really been "lost".

When booting with a START RECOVERY, the default configuration group is
BOOTUP.  A copy of the system configuration used during the last hard boot,
START NORECOVERY, is placed in the BOOTUP group for recovery purposes.
Changes to the system configuration can not be saved to the BOOTUP group.
This is usually a give away that the system was last started with a RECOVERY.

ATOM RSS1 RSS2