| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2062.1 | Re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Jan 29 1996 12:13 | 23 |
| Date Of Receipt: 22-JAN-1996 15:45:13.59
From: SMURF::FLUME::"[email protected]"
To: flume::odehelp, sankaran@dec:.zko.rusure
CC: GOODWIN@dec:.zko.rusure, FLUME::OVERMAN, SANKARAN@dec:.zko.rusure
Subj: Re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files
Jyoti, in 3.2C the what command creates those extra files, and you can't
write into that directory:
/usr/sde/osf1/build/v32csupportos.nightly/output/usr/sys/BINARY
I don't know where the "what" command tries to create that file (where
you are -- your current working directory, or where the target file is),
but whatever the case is, I think you'll need to give the "what" command
a place to do its thing where it can have permission to create a file.
Do a ls -ld <directory> to see the owner:group and permissions of whatever
directory you want to use.
Or maybe it's something else entirely... :-)
Dick
|
| 2062.2 | Re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Jan 29 1996 12:19 | 26 |
| Date Of Receipt: 22-JAN-1996 18:17:41.20
From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: rusure::sankaran
CC: goodwin@DEC:.zko.flume, odehelp@DEC:.zko.flume, overman@DEC:.zko.flume
Subj: Re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files
I don't understand what's going on either; you CAN do 'what output/bin/ls',
for example, within the same nightly tree, just fine. I didn't think
'what' tried to open anything for writing, just for reading. The same
error exists elsewhere too. Eg. From ptos.nightly, served from another
server, I get the same error as well, however the following workaround
does work, copying it to another location:
flume-1360 % what usr/sys/BINARY/procfs_vnops.o
usr/sys/BINARY/procfs_vnops.o:
usr/sys/BINARY/procfs_vnops.o: Read-only file system
flume-1361 % cp usr/sys/BINARY/procfs_vnops.o /tmp
flume-1362 % what /tmp/procfs_vnops.o
/tmp/procfs_vnops.o:
$RCSfile: procfs_vnops.c,v $ $Revision: 1.1.73.3 $ (DEC) $Date: 1996/01/17 19:24:25 $
flume-1363 % rm /tmp/procfs_vnops.o
flume-1364 %
-josh
|
| 2062.3 | Re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Jan 29 1996 12:24 | 13 |
| Date Of Receipt: 23-JAN-1996 08:41:35.43
From: SMURF::SEAN::davidson "D. Sean Davidson"
To: sean::jmf, rusure::sankaran
CC: sean::goodwin, sean::odehelp, sean::overman
Subj: Re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files
This appears to be fixed in platinum. If I cd ptos.nightly/output/usr/bin and
do a what on ls I get the expected results instead of the 'Read-only file
system' error. This looks like a V3.2[C-x] bug that needs to get fixed or
back ported from platinum.
Sean
|
| 2062.4 | re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Jan 29 1996 12:25 | 135 |
| Date Of Receipt: 23-JAN-1996 10:33:40.19
From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE 23-Jan-1996 1030"
To: davidson@DEC:.zko.flume
CC: odehelp@DEC:.zko.flume, sankaran@DEC:.zko.flume, goodwin@DEC:.zko.flume
Subj: re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files
Sean, this isn't quite the problem - what I'd found was that if you cd
to */output/usr/bin and do a what on ls it works - in both v32support
and ptos, but, and this includes ptos, if you try the same in either
the pt or v32support in */output/usr/sys/BINARY on, eg, procfs_vnops.o,
you do get this error.
I checked the modes of the file, and ., .., ../.., all the way back to /,
and there's no read problem; I can cat/cp the file just fine.
Very odd.
flume-1375 % /usr/sde/osf1/build/ptos.nightly/output/usr/sys/BINARY
flume-1376 % what procfs_vnops.o
procfs_vnops.o:
procfs_vnops.o: Read-only file system
-josh
------- Forwarded Messages
Return-Path: [email protected]
Delivery-Date: Mon, 22 Jan 96 15:32:07 -0500
Return-Path: [email protected]
Received: from ralpha.zk3.dec.com by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM)
id AA19542; Mon, 22 Jan 1996 15:31:48 -0500
Received: from flume.zk3.dec.com by falpha.zk3.dec.com; (5.65v3.2/1.1.8.2/20May95-1022AM)
id AA29973; Mon, 22 Jan 1996 15:31:44 -0500
Received: from DECnet-Mail11.flume.zk3.dec.com by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM)
id AA13448; Mon, 22 Jan 1996 15:23:33 -0500
Date: Mon, 22 Jan 1996 15:23:33 -0500
Message-Id: <[email protected]>
From: [email protected] (THINK subtly, ACT simply | Jyoti | 381-1351 | ZKO3-2/T43 | USEG)
To: [email protected]
Cc: [email protected], SANKARAN, GOODWIN
Subject: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files
Hi,
Since the middle of last week, it no longer seems possible to inquire the RCS
revisions of files in the v32csupportos nightly build output tree: the message
received states that the file system is read-only.
guru root 50 -> what $v32c_out//usr/sys/BINARY/procfs_vnops.o
/usr/sde/osf1/build/v32csupportos.nightly/output//usr/sys/BINARY/procfs_vnops.o:
/usr/sde/osf1/build/v32csupportos.nightly/output//usr/sys/BINARY/procfs_vnops.o:
Read-only file system
No problem, however, with the v32supportos nightly build output tree:
guru root 55 -> what $v32_out//usr/sys/BINARY/procfs_vnops.o
/usr/sde/osf1/build/v32supportos.nightly/output//usr/sys/BINARY/procfs_vnops.o:
$RCSfile: procfs_vnops.c,v $ $Revision: 1.1.84.2 $ (DEC) $Date: 1996/01/
17 19:28:08 $
Could someone kindly explain what the problem is?
Thanks,
Jyoti Sankaran
------- Message 2
Return-Path: jmf
Delivery-Date: Mon, 22 Jan 96 18:15:50 -0500
Return-Path: jmf
Received: from ralpha.zk3.dec.com by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM)
id AA24296; Mon, 22 Jan 1996 18:15:42 -0500
Received: from flume.zk3.dec.com by falpha.zk3.dec.com; (5.65v3.2/1.1.8.2/20May95-1022AM)
id AA24267; Mon, 22 Jan 1996 18:15:39 -0500
Received: by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM)
id AA21814; Mon, 22 Jan 1996 18:15:13 -0500
Date: Mon, 22 Jan 1996 18:15:13 -0500
From: Joshua M. Friedman OSF/UNIX SDE <jmf>
Message-Id: <[email protected]>
To: [email protected]
Subject: Re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files
Cc: goodwin, odehelp, overman
I don't understand what's going on either; you CAN do 'what output/bin/ls',
for example, within the same nightly tree, just fine. I didn't think
'what' tried to open anything for writing, just for reading. The same
error exists elsewhere too. Eg. From ptos.nightly, served from another
server, I get the same error as well, however the following workaround
does work, copying it to another location:
flume-1360 % what usr/sys/BINARY/procfs_vnops.o
usr/sys/BINARY/procfs_vnops.o:
usr/sys/BINARY/procfs_vnops.o: Read-only file system
flume-1361 % cp usr/sys/BINARY/procfs_vnops.o /tmp
flume-1362 % what /tmp/procfs_vnops.o
/tmp/procfs_vnops.o:
$RCSfile: procfs_vnops.c,v $ $Revision: 1.1.73.3 $ (DEC) $Date: 1996/01/17 19:24:25 $
flume-1363 % rm /tmp/procfs_vnops.o
flume-1364 %
- -josh
------- Message 3
Return-Path: [email protected]
Delivery-Date: Tue, 23 Jan 96 08:38:58 -0500
Return-Path: [email protected]
Received: from sean.zk3.dec.com by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM)
id AA01181; Tue, 23 Jan 1996 08:38:56 -0500
Received: by sean.zk3.dec.com (5.65v3.2/1.1.10.4/19Sep95-1131AM)
id AA23567; Tue, 23 Jan 1996 08:38:42 -0500
Date: Tue, 23 Jan 1996 08:38:42 -0500
From: D. Sean Davidson <[email protected]>
Message-Id: <[email protected]>
To: jmf, [email protected]
Subject: Re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files
Cc: goodwin, odehelp, overman
This appears to be fixed in platinum. If I cd ptos.nightly/output/usr/bin and
do a what on ls I get the expected results instead of the 'Read-only file
system' error. This looks like a V3.2[C-x] bug that needs to get fixed or
back ported from platinum.
Sean
------- End of Forwarded Messages
|
| 2062.5 | Re: WHAT (for finding out RCS revs) does not appear to work on v3.2c
nightly build output files | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Jan 29 1996 12:26 | 191 |
| Date Of Receipt: 23-JAN-1996 10:47:59.20
From: SMURF::FLUME::"[email protected]" "Grant Van Dyck 23-Jan-1996 1045"
To: "Joshua M. Friedman, OSF/UNIX SDE 381-1548" <[email protected]>
CC: [email protected], [email protected], [email protected],
[email protected]
Subj: Re: WHAT (for finding out RCS revs) does not appear to work on v3.2c
nightly build output files
This is a known bug in all releases up to ptos maybe where it got fixed.
When you do a what on a .o file, it wants to write temp files in the directory
where the .o lives. Since that's read-only for most people, you get this error.
If you copy the file to someplace you have write access to and then try it ...
cardinal kernel/BINARY [27] what dlb.o
dlb.o:
dlb.o: Read-only file system
cardinal kernel/BINARY [28] cp dlb.o /tmp
cardinal kernel/BINARY [29] what /tmp/dlb.o
/tmp/dlb.o:
$RCSfile: dlb.c,v $ $Revision: 1.1.12.3 $ (DEC) $Date: 1995/03/20
23:13:31 $
cardinal kernel/BINARY [30] cd /tmp
cardinal /tmp [32] ls -al dl*
-rw-r--r-- 1 vandyck system 117578 Jan 23 10:41 dlb.o
-rw-r--r-- 1 vandyck system 216568 Jan 23 10:42 dlb.oZaaghoa
See the turd it leaves behind? Classy behavior isn't it.
-Grant
| Sean, this isn't quite the problem - what I'd found was that if you cd
| to */output/usr/bin and do a what on ls it works - in both v32support
| and ptos, but, and this includes ptos, if you try the same in either
| the pt or v32support in */output/usr/sys/BINARY on, eg, procfs_vnops.o,
| you do get this error.
|
| I checked the modes of the file, and ., .., ../.., all the way back to /,
| and there's no read problem; I can cat/cp the file just fine.
|
| Very odd.
|
| flume-1375 % /usr/sde/osf1/build/ptos.nightly/output/usr/sys/BINARY
| flume-1376 % what procfs_vnops.o
| procfs_vnops.o:
| procfs_vnops.o: Read-only file system
|
|
| -josh
|
|
| ------- Forwarded Messages
|
| Return-Path: [email protected]
| Delivery-Date: Mon, 22 Jan 96 15:32:07 -0500
| Return-Path: [email protected]
| Received: from ralpha.zk3.dec.com by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16J
an95-0946AM)
| id AA19542; Mon, 22 Jan 1996 15:31:48 -0500
| Received: from flume.zk3.dec.com by falpha.zk3.dec.com; (5.65v3.2/1.1.8.2/20M
ay95-1022AM)
| id AA29973; Mon, 22 Jan 1996 15:31:44 -0500
| Received: from DECnet-Mail11.flume.zk3.dec.com by flume.zk3.dec.com; (5.65v3.
2/1.1.8.2/16Jan95-0946AM)
| id AA13448; Mon, 22 Jan 1996 15:23:33 -0500
| Date: Mon, 22 Jan 1996 15:23:33 -0500
| Message-Id: <[email protected]>
| From: [email protected] (THINK subtly, ACT simply | Jyoti | 381-13
51 | ZKO3-2/T43 | USEG)
| To: [email protected]
| Cc: [email protected], SANKARAN, GOODWIN
| Subject: WHAT (for finding out RCS revs) does not appear to work on v3.2c nig
htly build output files
|
| Hi,
|
| Since the middle of last week, it no longer seems possible to inquire the RC
S
| revisions of files in the v32csupportos nightly build output tree: the messag
e
| received states that the file system is read-only.
|
| guru root 50 -> what $v32c_out//usr/sys/BINARY/procfs_vnops.o
| /usr/sde/osf1/build/v32csupportos.nightly/output//usr/sys/BINARY/procfs_vnops
.o:
| /usr/sde/osf1/build/v32csupportos.nightly/output//usr/sys/BINARY/procfs_vnops
.o:
| Read-only file system
|
|
| No problem, however, with the v32supportos nightly build output tree:
|
| guru root 55 -> what $v32_out//usr/sys/BINARY/procfs_vnops.o
| /usr/sde/osf1/build/v32supportos.nightly/output//usr/sys/BINARY/procfs_vnops.
o:
| $RCSfile: procfs_vnops.c,v $ $Revision: 1.1.84.2 $ (DEC) $Date: 1996/
01/
| 17 19:28:08 $
|
| Could someone kindly explain what the problem is?
|
| Thanks,
| Jyoti Sankaran
|
|
| ------- Message 2
|
| Return-Path: jmf
| Delivery-Date: Mon, 22 Jan 96 18:15:50 -0500
| Return-Path: jmf
| Received: from ralpha.zk3.dec.com by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16J
an95-0946AM)
| id AA24296; Mon, 22 Jan 1996 18:15:42 -0500
| Received: from flume.zk3.dec.com by falpha.zk3.dec.com; (5.65v3.2/1.1.8.2/20M
ay95-1022AM)
| id AA24267; Mon, 22 Jan 1996 18:15:39 -0500
| Received: by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM)
| id AA21814; Mon, 22 Jan 1996 18:15:13 -0500
| Date: Mon, 22 Jan 1996 18:15:13 -0500
| From: Joshua M. Friedman OSF/UNIX SDE <jmf>
| Message-Id: <[email protected]>
| To: [email protected]
| Subject: Re: WHAT (for finding out RCS revs) does not appear to work on v3.2
c nightly build output files
| Cc: goodwin, odehelp, overman
|
| I don't understand what's going on either; you CAN do 'what output/bin/ls',
| for example, within the same nightly tree, just fine. I didn't think
| 'what' tried to open anything for writing, just for reading. The same
| error exists elsewhere too. Eg. From ptos.nightly, served from another
| server, I get the same error as well, however the following workaround
| does work, copying it to another location:
|
| flume-1360 % what usr/sys/BINARY/procfs_vnops.o
| usr/sys/BINARY/procfs_vnops.o:
| usr/sys/BINARY/procfs_vnops.o: Read-only file system
|
| flume-1361 % cp usr/sys/BINARY/procfs_vnops.o /tmp
| flume-1362 % what /tmp/procfs_vnops.o
| /tmp/procfs_vnops.o:
| $RCSfile: procfs_vnops.c,v $ $Revision: 1.1.73.3 $ (DEC) $Date: 1996/
01/17 19:24:25 $
| flume-1363 % rm /tmp/procfs_vnops.o
| flume-1364 %
|
| - -josh
|
|
| ------- Message 3
|
| Return-Path: [email protected]
| Delivery-Date: Tue, 23 Jan 96 08:38:58 -0500
| Return-Path: [email protected]
| Received: from sean.zk3.dec.com by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan
95-0946AM)
| id AA01181; Tue, 23 Jan 1996 08:38:56 -0500
| Received: by sean.zk3.dec.com (5.65v3.2/1.1.10.4/19Sep95-1131AM)
| id AA23567; Tue, 23 Jan 1996 08:38:42 -0500
| Date: Tue, 23 Jan 1996 08:38:42 -0500
| From: D. Sean Davidson <[email protected]>
| Message-Id: <[email protected]>
| To: jmf, [email protected]
| Subject: Re: WHAT (for finding out RCS revs) does not appear to work on v3.2
c nightly build output files
| Cc: goodwin, odehelp, overman
|
| This appears to be fixed in platinum. If I cd ptos.nightly/output/usr/bin an
d
| do a what on ls I get the expected results instead of the 'Read-only file
| system' error. This looks like a V3.2[C-x] bug that needs to get fixed or
| back ported from platinum.
|
| Sean
|
|
| ------- End of Forwarded Messages
|
--
-Grant
|
| 2062.6 | re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Jan 29 1996 12:27 | 46 |
| Date Of Receipt: 23-JAN-1996 11:21:56.43
From: SMURF::GURU::goodwin "Dick Goodwin USG"
To: davidson jmf
CC: odehelp sankaran
Subj: re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files
Here is the code from the v32c what.c that causes the error:
if(fheader.f_magic == ALPHAMAGICZ) {
strcpy(oname, infile);
strcat(oname, "ZXXXXXX");
tfname = (char *)mktemp(oname);
if((fdout = open(tfname, O_CREAT | O_RDWR, 0644)) < 0) {
perror (infile);
exit (1);
}
close(fdout);
It seems that if the .o file is in compressed format (ALPHAMAGICZ),
then "what" tries to create this temp file, to which it will uncompress
the target .o file.
The reason .../output/usr/bin/ls works is that it is not in ALPHAMAGICZ
format, so "what" does not try to create the temp file.
The reason .../output/usr/sys/BINARY/procfs_vnops.o does not work is
that it IS in ALPHAMAGICZ format, and "what" fails when it tries to
create the temp file because the filesystem is mounted "ro", as the
error implies.
I can copy .../output/usr/sys/BINARY/procfs_vnops.o to my own system
and get a similar error if I put it in a directory to which I do not
have write permission.
I can copy a v32 version of procfs_vnops.o (uncompressed) to the same
directory on my system, and the v32c "what" works OK.
And finally, I can use the v32 version of "what" and it works OK too,
both on the procfs_vnops.o in my write-protected directory and on the
procfs_vnops.o in .../output/usr/sys/BINARY/.
The only thing I don't understand yet is how the v32 version of what
can find the RCS string in the compressed format files. I'll take
a look at it as soon as the links build in my v32 sandbox.
Dick
|
| 2062.7 | Re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Jan 29 1996 12:28 | 17 |
| Date Of Receipt: 23-JAN-1996 11:48:38.48
From: SMURF::FLUME::johnf "John Flanagan USG Test Johnf Tools Group 23-Jan-1996 1146"
To: "Joshua M. Friedman, OSF/UNIX SDE 381-1548" <jmf@DEC:.zko.flume>
CC: davidson@DEC:.zko.flume, odehelp@DEC:.zko.flume, sankaran@DEC:.zko.flume,
goodwin@DEC:.zko.flume, johnf@DEC:.zko.flume
Subj: Re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files
There's a flaw in Lee Miller's algorithm for doing the decompress
of an ALPHAMAGICZ file [compressed BINARY object]. He attempts to
create a temp file in the location of the compressed BINARY. In
the case of v32csupportos.nightly, this is in the obj/alpha/kernel/BINARY
tree which is not writeable by non-root users.
"what" on ls works fine because it is not a compressed BINARY.
John
|
| 2062.8 | re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Jan 29 1996 12:29 | 16 |
| Date Of Receipt: 23-JAN-1996 11:51:15.68
From: SMURF::FLUME::overman "James C. Overman"
To: davidson goodwin jmf
CC: odehelp sankaran
Subj: re: WHAT (for finding out RCS revs) does not appear to work on v3.2c nightly build output files
This problem has been reported and solved by David Smith.
See QARs 41902 42402 40650 39299 for more information.
It would seem that the fix should be put into V32CSUPPORTOS and
brought forward thru all of the V32[D-Z]* support pools.
my $.02
James
|