HP3000-L Archives

October 1997, Week 1

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:
Mike Paivinen <[log in to unmask]>
Reply To:
Mike Paivinen <[log in to unmask]>
Date:
Tue, 30 Sep 1997 04:33:18 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (45 lines)
Jerry Fochtman ([log in to unmask]) wrote:
: At 01:50 PM 9/29/97 -0400, Rick LITTLE wrote:
: >If HP can "PROTECT" some files, why not all the files needed in the Bootup
: and
: >Startup processes???

We believed up to this point that we had.

: There exists a 'PROTECTED' indicator in the flags area of a file label. If I
: recall, the memory dump file, which is required to be on LDEV 1 has this flag
: set so that the file cannot be easily moved it another LDEV.  Perhaps HP
: should use this to lock-down all files required to be on LDEV 1 and the
: various tools which go underneath the file system 'honor' this flag....?

Actually, the configuration files required to boot your system were preserved
... they just weren't the files you expected.

Whenever you do a START NORECOVERY [GROUP=<config group>], a new configuration
group is established.  If you don't specify the GROUP parameter, the new
configuration group is CONFIG.  During the boot process, the OS makes a copy
of the specified or default configuration files in BOOTUP.SYS.  Then,
subsequent START [RECOVERY] boots use the config files in BOOTUP.SYS,
not the ones in the original configuration group.  None of the configuration
groups are considered protected, and they don't need to be.  The current
configuration is always in BOOTUP.SYS and those files *ARE* protected.  In
fact, once you realized your mistake, you could have done a
START NORECOVERY GROUP=BOOTUP.  Then, after booting, you could have fixed
the CONFIG.SYS group and re-booted with a START NORECOVERY.

Now, that doesn't explain the problem with PERFLOG.MPEXL.SYS.  The OS was
designed to boot successfully even if the only disc on-line is LDEV 1.
Sounds to me like PERFLOG now prevents MPE from working as designed.  So,
either 1) PERFLOG needs to be protected like other boot files, or 2) code needs
to be changed to allow the system to boot even if no PERFLOG exists.

Mike P.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Mike Paivinen
[log in to unmask]

Hewlett-Packard
CSY - Mailstop 47UA
19447 Pruneridge Avenue
Cupertino, CA   95014

ATOM RSS1 RSS2