Re: EDT exposes bug in terminal firmware

In article <6a804e18-0753-445b-a304-8b011dfc139d@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
AEF <spamsink2001@xxxxxxxxx> writes:
On Dec 13, 2:56 pm, billg...@xxxxxxxxxxx (Bill Gunshannon) wrote:
In article <96ac2a4a-5331-4f5d-8207-70c86ea85...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
AEF <spamsink2...@xxxxxxxxx> writes:



On Dec 13, 12:19 pm, billg...@xxxxxxxxxxx (Bill Gunshannon) wrote:
In article <ie513i$kh...@xxxxxxxxxxxxxxxxx>,
Jan-Erik Soderholm <jan-erik.soderh...@xxxxxxxxx> writes:

On 2010-12-13 11:30, Michael Kraemer wrote:
Bill Gunshannon schrieb:

I do that all the time without even leaving the editor (vi on Unix).

vi on Unix does file versioning?

An interesting feature but not one I ever saw any particular value
in.

That was my impression too, back in the bad old times,
when I had to use VMS regularly, before Unix came to my rescue :-)
No reason to keep umpteen versions of the same file,

Then don't do that, if there realy is no reason to keep them.
You can set your full disk to "version limit = 1".

Well, where to begin. That means it is all or nothing. And if you
choose some number inbetween there really is no guarantee it will
actually keep the copy you really needed. My method solves that
problem.

What exactly is your method? How is this different from using the EDT
WRITE command?

Sorry, no one mentioned any "WRITE command. They said that using EXIT
did it. But, again, unless the system has "version limit = 1" as the
default the system will still be filling up your disk quota leading to
the inevitable DOS unless the user knows what it is and what to do about
it. Geeks might, Poli Sci or Theology majors probably don't.

I wasn't thinking of ordinary users working at a DCL prompt.

"Ordinary users" outnumber geeks by a rather large ratio.

In fact,
I didn't think there were any anymore.

While I doubt anyone actually uses it any more there is still an
academic VMS machine here. And in the 20-some years that this
place has offered academic VMS services they have never offered
anything but a DCL prompt. The machines in my department were
the only ones that ever offered DECWindows as the default method
of access.

The only place I saw that was
in my experimental physics group. And we figured it all out just fine.
So I wasn't thinking of Poli Sci users or the like.

So, what did they use? There was a time before Windows could do
email and the web is a mere youngster or does no one here even
remember gopher?

So turn it off for
them. It's a single command in a login command procedure.

Never worked in this kind of environment, have you? :-) Although
it does sound like you would fit in just fine in the datacenter here.


And, you are assuming the users, who had no idea what
"versioning" even was, are going to know that option exists and how
to change it.

Who assumed anything? You have to learn it, like everything else.

And you are once again making an assumption. That is that all the users
have a reason or desire to become geeks. Some see the copmputer as just
a tool and some see it as an annoyance that they are forced to use when
they would really rather just write everything out with a pen and paper.

So there's nothing else they have to learn to use the computer?

They have to learn a lot. They want to learn the bare minimum.
The computer is a tool. They want it to help them with their
work, not increase their workload.

Really? They're all born with all the knowledge they need except for
multiple versions of files and the PURGE command?

And at this point, I give up. I can only imagine the environments where
most of the people here work. I can assure you they don't resemble any
place I have ever worked. But I'll refrain from telling all the horror
stories (like the guy I sent email to for months without ever getting
a reply and one day I asked if he had read his PROFS Mail that morning
and he replied, "What's PROFS?")

bill

--
Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves
billg999@xxxxxxxxxxxxxxx | and a sheep voting on what's for dinner.
University of Scranton |
Scranton, Pennsylvania | #include <std.disclaimer.h>
.

Relevant Pages

  • Re: EDT exposes bug in terminal firmware
    ... No reason to keep umpteen versions of the same file, ... no one mentioned any "WRITE command. ... "Ordinary users" outnumber geeks by a rather large ratio. ... academic VMS machine here. ...
    (comp.os.vms)
  • Re: EDT exposes bug in terminal firmware
    ... On 12/14/2010 10:51 AM, Bill Gunshannon wrote: ... No reason to keep umpteen versions of the same file, ... academic VMS machine here. ... It's a single command in a login command procedure. ...
    (comp.os.vms)
  • Re: EDT exposes bug in terminal firmware
    ... when I had to use VMS regularly, before Unix came to my rescue :-) ... No reason to keep umpteen versions of the same file, ... no one mentioned any "WRITE command. ... you have no experience with VMS it is no more intuitive than Unix, ...
    (comp.os.vms)
  • Announcment from OpenVMS Engineering - Daylight Saving Time changes
    ... VMS version 5.5-2 requires that you modify the system time manually. ... cannot use the DCL "SET TIME" command on a system running DECdts ... SYSMAN with ENVIRONMENT set to CLUSTER. ... Stop the DECps data collector with the command: ...
    (comp.os.vms)
  • Re: Announcment from OpenVMS Engineering - Daylight Saving Time changes
    ... Will it make automatic DST changes using AUTO_DLIGHT_SAVE under VMS ... cannot use the DCL "SET TIME" command on a system running DECdts ... SYSMAN with ENVIRONMENT set to CLUSTER. ... Stop the DECps data collector with the command: ...
    (comp.os.vms)