HP3000-L Archives

September 1997, Week 2

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:
Gavin Scott <[log in to unmask]>
Reply To:
Gavin Scott <[log in to unmask]>
Date:
Fri, 12 Sep 1997 15:38:42 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
GStigers asks:
> It's late Friday after a longish week, so this maybe the dumbest thing
> anyone has ever heard, but that has never stopped me from posting
> before.

That's ok, this may be the stupidest answer anyone has ever heard :-)

> Is anyone using MPE vs. POSIX name spaces to separate classes of
> files within an account? What I have in mind is separating development
> elements such as compile jobs from production elements such as batch
> processing jobs.

Well, just for grins, I just did something like:

:NEWLINK /GAVIN/FAKE,/GAVIN/PUB

Now if I refer to X.FAKE.GAVIN it gives me X.PUB.GAVIN!  You can't do
a :LISTF in @.FAKE.GAVIN, but any access that will follow the symbolic
link will work.  The MPE code that does file.group.account resolution
doesn't seem to care whether any of the filename components are really
groups/accounts or simply symbolic links.

So you could have a DATA1 and a DATA2 group in an account and have all
the programs access everything out of the DATA group which would be a
symbolic link to one or the other as needed.  I'm sure there are other
things than :LISTF that wouldn't work though.

Symbolic links are useful in lots of "pure MPE" places that people don't
usually think of using them because they are perceived as a "Posix"
feature.

This may not help with what you're trying to do, but I found it mildly
entertaining (but them again it *is* late on Friday...)

G.

ATOM RSS1 RSS2