README
1README - Uptime Client v4.2
2
3 This is de README file of the Uptime Client, from now on referred
4 to as Upclient.
5
6
7LICENSE
8
9 This program is free software; you can redistribute it and/or modify
10 it under the terms of the GNU General Public License as published by
11 the Free Software Foundation; either version 2 of the License, or
12 (at your option) any later version.
13
14
15OFFICIAL WEBSITES
16
17 Uptime Client : http://uptimes.atomicvoid.net
18 (alex@uptimes.net)
19
20 Uptimes Project: http://www.uptimes.net
21 (tgm@uptimes.net)
22
23
24PLATFORMS
25
26 Uptime Client currently compiles and runs on these platforms:
27 - *BSD (FreeBSD, OpenBSD, NetBSD, Darwin are confirmed)
28 - UnixWare
29 - Ultrix
30 - BeOS
31 - Solaris 2.6+
32 - Irix
33 - Linux
34 - AIX
35 - Windows NT4 / Windows 2000
36
37 Version 4.2.1.20 is tested on Linux 2.0.36 (libc5) through 2.2.18
38 (glibc 2.1, 2.2), OpenBSD 2.7 and 2.8, FreeBSD 4.1 and SunOS 5.6.
39 Please test the syntax of the configuration file thoroughly and
40 the Makefile system.
41
42 Request:
43 I'd like to have a shell account on a Irix, Ultrix, UnixWare and AIX
44 system. I only need: man, bash/tcsh, make, compiler, diskspace. So If
45 you feel generous, don't hesitate to contact me.
46
47
48INSTALLATION
49
50 See the INSTALL file for that (-:
51
52
53DEINSTALLATION
54
55 Now, you don't really want that, do you??
56
57
58PATCHES & DEVELOPMENT
59
60 I welcome any patches send in by you. But I would like you to ask to
61 code in my style. I don't use any tabs in code aligning, only two
62 spaces for each indentation level. Hm, not entirely true, for I indent
63 some variable declarations and #define's with tabs. Just take a look
64 at the code and you'll know how I prefer the coding style of your
65 patches (-:
66
67 The Uptime Client has a developers mailinglist where you can discuss
68 it's development and receive announcements on new versions:
69
70 "uptimes-devel@atomicvoid.net"
71
72 Contact alex@uptimes.net if you'd like to be added to the list, don't
73 write to the list please.
74
75
76VERSION NUMBERING
77
78 Versions of the Uptime Client start with the protocol version, then
79 an Linux style indicator of the type of branch, even numbers stable,
80 odd numbers development, then the version indicator of that branch.
81
82 ex: Uptime Client v4.2.1.17
83 4.2 = Major Uptime Client version number that just follows the
84 Uptimes Protocol version number
85 1.17 = Uptime Client's version of previous protocol indicator
86 1 = branch version, odd numbers mean unstable
87 17 = Uptime Client's version of the previous branch
88 indicator
89
90 ex: 4.2.1.17 = Uptimes Protocol 4.2, unstable branch version 1,
91 revision/version of that branch: 17.
92 4.2.2.0 = Uptimes Protocol 4.2, stable branch version 2,
93 revision/version of that branch: 0 (first release).
94
95 Conclusion: it sucks (-:
96
97
98THE END
99
100 tgm (tgm@uptimes.net) and Alex (alex@uptimes.net) hope you like the
101 Uptimes Project. Please feel free to send comments to either one of
102 us.
103