Subject: | |
From: | |
Reply To: | |
Date: | Tue, 9 Jan 2001 11:38:47 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Thanks for the script example, Stan. I was thinking about trying something
like that as one way to approach it. It'd still be cleaner/easier if
volutil/showset supported wildcards.
Why would I want that? Mostly for those fuzzy-memory times when I have to
remember "What was the name of that volclass I set up? And what volset did
I associate it with?" Really, it'd be nice to have a wildcardable showset
for other things too; wouldn't you like to do a "showset @ ALL" and send
that to a printer to keep in the "how to rebuild the system from scratch"
notebook?
And yes, I like using XEQ in scripts instead of RUN when possible to avoid
the END OF PROGRAM tag. It's a little thing, but it's annoying. ;-)
--Jon
At 11:00 AM 1/9/2001 -0800, Stan Sieler wrote:
>Re:
> > Is there a command to list all volume classes defined in volutil?
>
>Why? At first glance, I can see no reason to want to do this..
...
>I suspect you could create an MPEX script (or sh/grep/cut :) that would
>do what you want:
>...
>Here's an awkward example.
...
>Note that I avoided "END OF PROGRAM" from the "sh.hpbin" by using
>XEQ instead of RUN....I couldn't safely avoid that via an implied run,
>because both "sh" and "sh.hpbin.sys"
>might trigger someone's "sh" UDC/command file, getting incorrect results.
|
|
|