🚀 go-pugleaf

In article <1992Nov16.115823.1041@beckman.com>, dsroberts@beckman.com writes:
> "Error accessing system authorization file"
> "Error in device name or inappropriate device type for operation"
> "SYSUAF" = "BII$SYSTEM:SYSUAF.DAT"
> "BII$SYSTEM" = "$1$DUA1:[BII.SYS]"

Well, more information, as pointed out, is needed to eliminate some
possibilities.  From the log of the startup in question:

$ define /system/exec/nolog bii$system $1$dua1:[bii.sys]
$ define /system /exec /nolog sysuaf bii$system:sysuaf.dat

So, as all can see, it was indeed defined in executive_mode.

Any other thoughts?  Thanks for the replies so far.

-- 
   Don Roberts                   Internet:  dsroberts@beckman.com
   Beckman Instruments, Inc.     Phone:     714/961-3029
   2500 Harbor Bl. Mailstop X-12 FAX:       714/961-3351
   Fullerton, CA  92634          Disclaimer:  Blame me, not Beckman.
   This was probably the most disastrous election result for the American
   people since James Buchanon became president.  Heaven help us.

In article <1992Nov16.115823.1041@beckman.com>, dsroberts@beckman.com writes:
> Okay, sez I, the logical SYSUAF isn't defined properly.  So, $ SHOW LOGICAL
> /FULL SYSUAF:

Yikes, double checking the log of the session, I see that the /full was NOT
part of my typing Sunday night.  So, though this was run by SYSTEM, which on
our system by default has ALL privs, and though the define's show up in the
log, it may well be possible this was not an exec mode logical.  I guess that
since later during that session I tried, from SYSTEM:

$ define /system /exec sysuaf $1$dua1:[bii.sys]sysuaf.dat

Interactively, it is still possible this command didn't work correctly.  I
still never did a show logical /full, so this is still under question.  And,
though I did perform a $ show logical * /table=*, and no logical of "$1$dua1"
exists, I suppose it is possible there is one anyway.

Basically until I get another chance to try it (this week-end), I'll have to
table this, as the overwhelming opinion is that there must be something wrong
with the logical.  So, I'll show logical /full, I'll try moving sysuaf to the
normal location and a few other things before I ask again (which, I'm sure,
won't be necessary, as I've probably overlooked something rather obvious).

Thanks to my many correspondents for their thoughtful responses.  Thanks
particularly to Ehud, as he really restrained himself on his flame on this :-)
-- 
   Don Roberts                   Internet:  dsroberts@beckman.com
   Beckman Instruments, Inc.     Phone:     714/961-3029
   2500 Harbor Bl. Mailstop X-12 FAX:       714/961-3351
   Fullerton, CA  92634          Disclaimer:  Blame me, not Beckman.
   This was probably the most disastrous election result for the American
   people since James Buchanon became president.  Heaven help us.

In article <1992Nov16.115823.1041@beckman.com> dsroberts@beckman.com writes:

>"Error accessing system authorization file"
>"Error in device name or inappropriate device type for operation"
>
>Okay, sez I, the logical SYSUAF isn't defined properly.  So, $ SHOW LOGICAL
>/FULL SYSUAF:
>
>"SYSUAF" = "BII$SYSTEM:SYSUAF.DAT"
>
>Hmm. exactly the same as the old startup.  How about BII$SYSTEM?
>
>"BII$SYSTEM" = "$1$DUA1:[BII.SYS]"
>
>Also the same.  Well, does the file exist?
>
>$ directory sysuaf
>Directory $1$DUA1:[BII.SYS]
>SYSUAF.DAT;3
>Total of 1 file.
>

Try sho logical/full.  It probably should be defined as an exec 
(def/sys/exec).  The dir would work, but logging in would not. (Security 
reasons)
-- 
Bill Bochnik			| It's hard to be a James Bond in an Abbott
Systems Analyst 		|	and Costello world.
Ciba-Geigy Corporation		| Signed and sealed, they deliver oblivion.
philabs!crpmks!billb		| It's worse than that, he's dead Jim.