Debian Codegraph @

README

raw
1 This is biff+comsat-0.17-pre-20000412 for Linux.
2
3 This package updates biff+comsat-0.16.
4
5 If you're reading this off a CD, go right away and check the net
6 archives for later versions and security fixes. As of this writing the
7 home site for NetKit is
8 ftp://ftp.uk.linux.org/pub/linux/Networking/netkit
9
10 Contents:
11 comsat Daemon for asynchronous new mail notification
12 biff Control program for comsat
13
14 Requires:
15 Working compiler, libc, and kernel.
16
17 Security:
18 This release contains no security fixes relative to
19 biff+comsat 0.16. However, versions prior to NetKit-0.09
20 should not be used.
21
22 Installation:
23 Do "./configure --help" and decide what options you want. The
24 defaults should be suitable for most Linux systems. Then run
25 the configure script.
26
27 Do "make" to compile.
28 Then (as root) do "make install".
29
30 Save a backup copy of any mission-critical program in case the
31 new one doesn't work, and so forth. We warned you.
32
33 If you get gcc warnings from files in /usr/include, they are
34 due to problems in your libc, not netkit. (You may only see
35 them when compiling netkit because netkit turns on a lot of
36 compiler warnings.)
37
38 DEC CC:
39 The DEC compiler for the Alpha is now freely available. This
40 is a much better compiler with gcc, that is, it generates much
41 better code. If you have the DEC compiler, you can explicitly
42 use the DEC compiler instead of gcc by configuring like this:
43
44 ./configure --with-c-compiler=ccc
45
46 It is known to generate spurious warnings on some files. Also,
47 some headers from some versions of glibc confuse it; that may
48 prevent netkit from working. Other problems should be reported
49 as bugs.
50
51 Bugs:
52 Please make sure the header files in /usr/include match the
53 libc version installed in /lib and /usr/lib. If you have weird
54 problems this is the most likely culprit.
55
56 Also, before reporting a bug, be sure you're working with the
57 latest version.
58
59 If something doesn't compile for you, fix it and send diffs.
60 If you can't, send the compiler's error output.
61
62 If it compiles but doesn't work, send as complete a bug report as
63 you can. Patches and fixes are welcome, as long as you describe
64 adequately what they're supposed to fix. Please, one patch per
65 distinct fix. Please do NOT send the whole archive back or
66 reindent the source.
67
68 Be sure to send all correspondence in e-mail to the netkit address.
69 Postings to netnews or mailing lists will not be seen due to the
70 enormous volume. Also, anything that doesn't get filed in the bug
71 database is quite likely to end up forgotten.
72
73 Please don't report known bugs (see the BUGS file(s)) unless you
74 are including fixes. :-)
75
76 Mail should be sent to: [email protected]
77
78
79 Early in April 2000, a hacker broke into the machine that was hosting
80 the netkit bug database for me and trashed it. Unfortunately, it seems
81 backups hadn't gotten done for a while, so three months of mail (since
82 mid-January) was lost. So, if you sent something and didn't hear back,
83 or you sent something, heard back, but the changes failed to appear in
84 this release (unlikely but possible) - please resend.
85
86 Please see http://www.hcs.harvard.edu/~dholland/computers/netkit.html
87 if you are curious why it was so long between the 0.10 and 0.16 releases.
88
89 After this release is finalized, if there are no immediate problems, I
90 plan to hand over the source tree to Red Hat for subsequent maintenance,
91 unless some alternative arrangements can be made.
92
93 David A. Holland
94 12 April 2000