OT: SCO 6.0 - MAJOR BUG!!!!!

[Jay R. Ashworth]

On Sun, Oct 23, 2005 at 12:45:21PM -0400, Jean-Pierre A. Radley wrote:
> | | Okay, I'm ready to be told why this is some kind of a good idea and not a
> | | pure giant bug.
> | 
> | It's a major bug, and I've posted your report to the people who can fix it.
> 
> The first answer I got is that is the usual behavior in Unixware.
> 
> That leaves open the question of whether it is or is not a bug.

If the binaries in question are compiled pure-text, then they will swap
back in (after swap-out) from the filesystem rather than from swap, and
if that's so, any attempt to write that file should generate ETXTBUSY,
as it has since t=0.  (OK, since pure text came to be, which is pretty
close).

If they're *not* compiled pure-text, then you should in fact be able to
write over them once they're loaded... but you shouldn't core dump
running copies of them.

John?  What does

# file /path/to/rclerk

say?

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Designer                          Baylink                             RFC 2100
Ashworth & Associates        The Things I Think                        '87 e24
St Petersburg FL USA      http://baylink.pitas.com             +1 727 647 1274

	"NPR has a lot in common with Nascar... we both turn to the left."
		- Peter Sagal, on Wait Wait, Don't Tell Me!