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
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Drawbacks</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="tuXlab Cookbook"
HREF="index.html"><LINK
REL="UP"
TITLE="Thin-client computing"
HREF="c567.html"><LINK
REL="PREVIOUS"
TITLE="Benefits"
HREF="x928.html"><LINK
REL="NEXT"
TITLE="Hardware"
HREF="x974.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>tuXlab Cookbook</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="x928.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 6. Thin-client computing</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="x974.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="drawbacks"
>6.5. Drawbacks</A
></H1
><P
>Every solution will have some drawbacks, and a tuXlab is no
exception. I'll just mention a few in passing.</P
><P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>Unreal Tournament will be lethargic or lag in response
rate</DT
><DD
><P
>Graphics-intensive applications such as games will not
perform well, as all the display information will have to be pushed
over the network by the server. This is hundreds of times slower
than driving a local graphics card. Playing action games, however,
is not a goal of the tuXlab project.</P
></DD
><DT
>All the clients run the same
<ACRONYM
CLASS="acronym"
>OS</ACRONYM
></DT
><DD
><P
>Since it's really only one instance of Linux serving all the
desktops and applications, all the clients in the lab will
necessarily offer a Linux environment. It is possible for the
server to run software such as Wine (which enables many Windows
programs to run under Linux) or VMWare (which allows the server to
run instances of other operating systems), but in these cases the
underlying system will still be Linux, and the server will still be
doing all the work.</P
></DD
><DT
>Single point of failure</DT
><DD
><P
>While it's very convenient that the thin-client workstations
are interchangeable and that you can access your desktop from
anywhere, it does mean that a catastrophic failure of the server
will put
<SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>all</I
></SPAN
> client workstations out of
commission.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="x928.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="x974.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Benefits</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="c567.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Hardware</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
|