1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5
>Server configuration</TITLE
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
TITLE="tuXlab Cookbook"
11
HREF="index.html"><LINK
14
LTSP, Wizzy, Wikipedia"
15
HREF="x1395.html"><LINK
17
TITLE="Dynamic Host Configuration Protocol"
18
HREF="x1491.html"></HEAD
29
SUMMARY="Header navigation table"
73
NAME="server-configuration"
75
>Chapter 9. Server configuration</H1
81
NAME="wizzy-configuration"
82
>9.1. Wizzy configuration</A
85
>A Wizzy server plays two roles. In the first place, it serves as an
86
internet proxy, serving cached pages to a lab without a permanent
87
internet connection. In the second place, it connects to the internet and
88
retrieves requested pages to store them locally, sends queued email, and
89
fetches received mail.</P
91
>These two roles don't have to be fulfilled by the same server: they
92
may be split across two servers, for example if the school has no
93
internet access. In this case, there will be a Wizzy in the tuXlab and
94
another one at a remote location with internet connectivity.</P
96
>The hardware requirements for the Wizzy server are far less than
97
those of the classroom application server, since it has to do far less
98
work. All it needs to do most of the time is to serve up saved pages from
99
its hard disk. For this, a server with a 200+MHz
107
>, and a 40GB RAID 1 disk array is adequate.</P
113
NAME="software-used-by-the-wizzy-server"
114
>9.1.1. Software used by the Wizzy server</A
121
>The Wizzy server uses
133
> for booting, the same as the classroom
136
>XXX: What does the Wizzy server use
140
> for? Does it also boot from the classroom
145
>It uses the Lightweight Directory Access Protocol (LDAP) for
146
authentication. When users access their email on the Wizzy server
147
they will need to supply a username and password. This information
148
is kept by an LDAP server, which maintains a directory where user
149
information may be looked up. It is analogous to a telephone
152
>Ideally, there should be only one directory for a tuXlab,
153
which contains the information on all the users and resources (such
154
as printers) in the lab. Currently, however, the directory
155
maintained by the Wizzy server is separate from the user database
156
on the classroom server.</P
160
>The Unix-to-Unix Copy Protocol (UUCP) is used for
167
> email sending and receiving, as well as for
168
fetching web pages. As long as a service can be configured to use
169
UUCP for communication, it is possible to provide the service
170
without a permanent internet connection. For this reason, Wizzy
175
>The Wizzy server uses BIND (the Berkeley Internet Name
176
Daemon) for domain name services (
180
>), on the local network.
184
> is how IP addresses, such as
188
>, are resolved to readable domain
192
>server.myschool.tuxlab.org.za</TT
195
>XXX: I'm not sure what "on the local network" means here.
196
Does that mean it only resolves names that are local to the
199
>XXX: What domain name does a classroom server get?</P
203
>For email, Wizzy uses the Courier IMAP server for inbound
206
>IMAP (the Internet Mail Access Protocol) provides a way for
207
all kinds of mail clients (such as Thunderbird, or Mozilla's email
208
component) to access a mail store. In Wizzy's case, the Courier
209
package handles mail storage and IMAP access. Wizzy also provides a
210
webmail client to access the mail store using a web browser.</P
214
>To send mail, Wizzy uses the
226
>, one of the most important jobs the
227
Wizzy does is to provide a browsable offline copy of all the web
228
pages that interest tuXlab users. It does this using the
230
HREF="http://www.gedanken.demon.co.uk/wwwoffle/"
233
> program to provide a local web cache. It augments
237
> (the World Wide Web Offline Explorer)
238
with some custom programs, since Wizzy's disconnected mode of
239
operation goes beyond the options offered by
247
>The Wizzy server provides its administration functions as
248
well as webmail as web pages, and uses the
250
HREF="http://www.apache.org/"
254
serve these pages. They may be accessed by going to XXX
267
>For a local FTP server, Wizzy uses XXX: vsftpd (XXX: but what
268
is the local FTP server used for?)</P
272
>In its role as a connection to the internet, the Wizzy server
277
> with which the school has an account, in
278
order to retrieve web pages. It does not, however, use any email
283
> may provide: all mail goes through Andy
284
Rabagliati's server in Cape Town using UUCP.</P
288
>For the sake of data integrity, Wizzy uses a RAID disk system
289
for storage. RAID is a
294
>Redundant Array of Inexpensive Disks</I
297
way to federate multiple hard disk drives in such a way that the
298
failure of any one disk does not result in data loss.</P
307
NAME="wizzy-as-a-classroom-server"
308
>9.1.2. Wizzy as a classroom server</A
311
>The Wizzy project predates tuXlabs. It can also be configured to
312
provide a similar range of application serving functions as the tuXlab
313
classroom server provides. In this configuration, it uses the following
320
>Like the tuXlab server, Wizzy uses the
329
thin-client NFS-mounted root directory.</P
337
> (the Network FileSystem) for home directories
338
that are NFS-mounted by the thin clients.</P
340
>XXX: I don't know if I'm understanding this correctly. Does
341
Wizzy mount the users' home directories from the classroom server,
342
e.g. in order to server web pages from them?</P
353
SUMMARY="Footer navigation table"
395
>, Wizzy, Wikipedia</TD
405
>Dynamic Host Configuration Protocol</TD
b'\\ No newline at end of file'
added
removed
lore/c1420.html
