DM commands CV and RO

Thread View: mod.computers.apollo

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by "Sundar R. Iyengar" Fri, 28 Feb 1986 05:48

#117

Author: "Sundar R. Iyengar"
Date: Fri, 28 Feb 1986 05:48

27 lines
2047 bytes

We just switched to 4.2BSD.  The "inlib" command, when executed from
within csh, doesn't seem to load the mentioned library (the las
doesn't contain the library name).  Is there a fix for this?

I am also curious to know how the DM commands "ro" and "cv" work.  "ro"
seems to have access to a "file-modified" variable.  When a pad is opened on
a file through the DM command "cv", the pad header indicates the read-only
nature of the pad with a "R".  "ro" correctly handles toggling
the read-only status of this pad (R to I and I to R).  However, when a
similar pad is created using the pad call "pad_$create" with a "pad_$edit"
attribute (the pad header contains an I), "ro" thinks that the pad has been
modified.  An attribute of "pad_$read_edit" disallows "ro" to work on the
pad (this is documented in the manuals).   I wonder what attribute "cv" uses
to create the same pad.  It couldn't use "pad_$edit" unless
it is able to clear the "file-modified" variable and change the pad header
information (to change I to R) and it couldn't use the "pad_$read_edit"
attribute because of the documented "feature".  If "cv" can clear the
"file-modified" variable, what system call does it use to do it?

Thanks.

sundar r. iyengar		

arpa:  sundar.case@csnet-relay     531, crawford hall
csnet: sundar@case		   case western reserve university
uucp:  decvax!cwruecmp!sundar	   cleveland, oh 44106

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads