HP3000-L Archives

November 1998, 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:
Tim Busche <[log in to unmask]>
Reply To:
Tim Busche <[log in to unmask]>
Date:
Fri, 6 Nov 1998 13:28:17 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (49 lines)
Our SYSSTART file is on LDEV 27 and executes just fine.

-----Original Message-----
From: RON HORNER [mailto:[log in to unmask]]
Sent: Friday, November 06, 1998 1:22 PM
To: [log in to unmask]
Subject: Re: sysstart


Unless the manuals have changed, this is what it says about dev 1:

The SYSSTART file must be created by MANAGER.SYS and needs to reside on
LDEV 1 to function properly.

It's also been my experience that even if the file is on dev2 the system
doesn't execute the file.


        -----Original Message-----
        From:   Gavin Scott [SMTP:[log in to unmask]]
        Sent:   Friday, November 06, 1998 11:48 AM
        To:     [log in to unmask]
        Subject:        sysstart

        Kin writes:
        > Gary Paveza wins the wine coolers.  The file was on ldev 33
instead of ldev
        > 1.

        Fine, except that there is no requirement for SYSSTART to be on
LDEV 1.

        SYSSTART is not accessed untill the system volume set is fully
mounted,
        so it can be spread across any volumes in
MPEXL_SYSTEM_VOLUME_SET.

        Since PUB.SYS can't be moved to a user volume, you don't have to
worry
        about somehow getting it anywhere that it shouldn't be.  In
fact, it would
        probably still work if you put a copy of it on a user volume
(still with
        a creator of MANAGER.SYS) and replaced the PUB.SYS one with a
symbolic link
        pointing to the copy.

        G.

ATOM RSS1 RSS2