This file is indexed.

/usr/share/doc/paw/README.Debian is in paw 1:2.14.04.dfsg.2-9.1build1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
Notes on paw
------------

1) Graphics window corruption

If you experience corruption of the graphics window when other windows are
moved over top of it, turn on the BackingStore option of the X server.
In the "Screen" section of your /etc/X11/xorg.conf or /etc/X11/XF86Config-4
file (whichever one exists), you should have something like:

Section "Screen"
	.
	.
	.
    Option "BackingStore"
	.
	.
	.
EndSection

Be aware that making this change will cause Debconf to refuse to update your X
settings when you upgrade your X server package.  See the blurb at the top of
/etc/X11/xorg.conf (if you have xserver-xorg installed) or
/etc/X11/XF86Config-4 (if you have xserver-xfree86 installed) for more
information.

2) Remote data files

PAW can read files remotely from computers running the distributed PAW
(pawserv) server, which is included in the pawserv Debian package.  This is
done from within PAW using 'rlogin' and 'rshell' commands; see the PAW
User's Guide for details.  Please note that these commands transmit passwords
in clear text and should be used only within a secured LAN.

3) Path issues

If you compile a FORTRAN script within PAW, the path to the file cannot
be excessively long (more than 256 characters).

4) Filename case issues

The default behavior in Debian has been set so that PAW is case-sensitive
in its treatment of filenames.  If you have any old PAW scripts that do not
treat filenames in a case-sensitive way, you may need to add the line

        filecase convert

to the beginning of them.

5) 64-bit issues

This package is now believed to be more or less functional on 64-bit machines.
On these architectures, PAW is linked statically against the CERN libraries, as
they cannot properly handle pointer differences that do not fit in a 32-bit
variable.  See the file README.64-bit in the cernlib-base package.

-- Kevin McCarty <kmccarty@debian.org>, Tue, 19 Sep 2006