1
1
<!-- retain these comments for translator revision tracking -->
2
<!-- $Id: files.xml 33887 2006-01-09 10:09:48Z cjwatson $ -->
2
<!-- $Id: files.xml 44436 2007-01-23 19:23:09Z fjp $ -->
5
5
<sect1 id="linuxdevices"><title>Linux Devices</title>
8
In Linux you have various special files in
9
<filename>/dev</filename>. These files are called device files. In
10
the Unix world accessing hardware is different. There you have a
11
special file which actually runs a driver which in turn accesses the
12
hardware. The device file is an interface to the actual system
13
component. Files under <filename>/dev</filename> also behave
14
differently than ordinary files. Below are the most important device
8
In Linux various special files can be found under the directory
9
<filename>/dev</filename>. These files are called device files and
10
behave unlike ordinary files. The most common types of device files
11
are for block devices and character devices. These files are an
12
interface to the actual driver (part of the Linux kernel) which in
13
turn accesses the hardware. Another, less common, type of device file
14
is the named <firstterm>pipe</firstterm>.
15
The most important device files are listed in the tables below.
119
<title>Setting Up Your Mouse</title>
123
The mouse can be used in both the Linux console (with gpm) and the X window
124
environment. The two uses can be made compatible if the gpm repeater is used
125
to allow the signal to flow to the X server as shown:
127
<informalexample><screen>
128
mouse => /dev/psaux => gpm => /dev/gpmdata -> /dev/mouse => X
129
/dev/ttyS0 (repeater) (symlink)
131
</screen></informalexample>
133
Set the repeater protocol to be raw (in <filename>/etc/gpm.conf</filename>) while
134
setting X to the original mouse protocol in <filename>/etc/X11/XF86Config</filename>
135
or <filename>/etc/X11/XF86Config-4</filename>.
139
This approach to use gpm even in X has advantages when the mouse is
140
unplugged inadvertently. Simply restarting gpm with
142
<informalexample><screen>
143
# /etc/init.d/gpm restart
144
</screen></informalexample>
146
will re-connect the mouse in software without restarting X.
150
If gpm is disabled or not installed with some reason, make sure to set X to
151
read directly from the mouse device such as /dev/psaux. For details, refer
152
to the 3-Button Mouse mini-Howto at
153
<filename>/usr/share/doc/HOWTO/en-txt/mini/3-Button-Mouse.gz</filename>,
154
<userinput>man gpm</userinput>,
155
<filename>/usr/share/doc/gpm/FAQ.gz</filename>, and
156
<ulink url="&url-xorg;current/doc/html/mouse.html">README.mouse</ulink>.
158
</para><para arch="powerpc">
160
For PowerPC, in <filename>/etc/X11/XF86Config</filename> or
161
<filename>/etc/X11/XF86Config-4</filename>, set the mouse device to
162
<userinput>"/dev/input/mice"</userinput>.
164
</para><para arch="powerpc">
118
<sect2 arch="not-s390" id="device-mouse">
119
<title>Setting Up Your Mouse</title>
122
The mouse can be used in both the Linux console (with gpm) and the X
123
window environment. Normally, this is a simple matter of installing
124
<filename>gpm</filename> and the X server itself. Both should be
125
configured to use <filename>/dev/input/mice</filename> as the mouse
126
device. The correct mouse protocol is named <userinput>exps2</userinput>
127
in gpm, and <userinput>ExplorerPS/2</userinput> in X. The respective
128
configuration files are <filename>/etc/gpm.conf</filename> and
129
<filename>/etc/X11/xorg.conf</filename>.
133
Certain kernel modules must be loaded in order for your mouse to work.
134
In most cases the correct modules are autodetected, but not always for
135
old-style serial and bus mice<footnote>
138
Serial mice usually have a 9-hole D-shaped connector; bus mice have an
139
8-pin round connector, not to be confused with the 6-pin round connector
140
of a PS/2 mouse or the 4-pin round connector of an ADB mouse.
143
</footnote>, which are quite rare except on very old computers. Summary
144
of Linux kernel modules needed for different mouse types:
146
<informaltable><tgroup cols="2"><thead>
148
<entry>Module</entry>
149
<entry>Description</entry>
153
<entry>psmouse</entry>
154
<entry>PS/2 mice (should be autodetected)</entry>
157
<entry>usbhid</entry>
158
<entry>USB mice (should be autodetected)</entry>
161
<entry>sermouse</entry>
162
<entry>Most serial mice</entry>
165
<entry>logibm</entry>
166
<entry>Bus mouse connected to Logitech adapter card</entry>
169
<entry>inport</entry>
170
<entry>Bus mouse connected to ATI or Microsoft InPort card</entry>
172
</tbody></tgroup></informaltable>
174
To load a mouse driver module, you can use the <command>modconf</command>
175
command (from the package with the same name) and look in the category
176
<userinput>kernel/drivers/input/mouse</userinput>.
178
</para><para arch="powerpc">
179
<!-- FJP 20070122: Unsure if this is still valid -->
166
181
Modern kernels give you the capability to emulate a three-button mouse
167
182
when your mouse only has one button. Just add the following lines to
185
200
<sect1 id="tasksel-size-list">
186
201
<title>Disk Space Needed for Tasks</title>
188
<!-- Note for d-i and manual maintainers
189
Sizes of tasks should be determined by running "tasksel new" on a system
190
that been fully installed without selecting any tasks. By selecting a
191
task together with the "manual selection" option, aptitude will be started
192
and show the sizes for the task. After deselecting the packages to be
193
installed, quit aptitude and repeat for other tasks.
194
Space requirements need to be determined from tasksel as tasksel will not
195
install recommended packages while selecting a task from aptitude will.
200
The base installation for i386 using the default 2.4 kernel,
201
including all standard packages, requires 573MB of disk space.
204
A standard installation for the i386 architecture, including all standard
205
packages and using the default 2.6 kernel, takes up &std-system-size;MB of disk space.
206
A minimal base installation, without the <quote>Standard system</quote>
207
task selected, will take &base-system-size;MB.
212
In both cases this is the actual disk space used <emphasis>after</emphasis>
213
the installation is finished and any temporary files deleted. It also does
214
not take into account overhead used by the file system, for example for
215
journal files. This means that significantly more disk space is needed both
216
<emphasis>during</emphasis> the installation and for normal system use.
205
221
The following table lists sizes reported by aptitude for the tasks listed
206
222
in tasksel. Note that some tasks have overlapping constituents, so the
232
<entry>Desktop</entry>
249
<entry>Desktop environment</entry>
250
<entry>&task-desktop-inst;</entry>
251
<entry>&task-desktop-dl;</entry>
252
<entry>&task-desktop-tot;</entry>
256
<entry>Laptop<footnote>
259
There is a large overlap of the Laptop task with the Destop environment task.
260
If you install both, the Laptop task will only require a few MB additional
265
<entry>&task-laptop-inst;</entry>
266
<entry>&task-laptop-dl;</entry>
267
<entry>&task-laptop-tot;</entry>
239
271
<entry>Web server</entry>
272
<entry>&task-web-inst;</entry>
273
<entry>&task-web-dl;</entry>
274
<entry>&task-web-tot;</entry>
246
278
<entry>Print server</entry>
279
<entry>&task-print-inst;</entry>
280
<entry>&task-print-dl;</entry>
281
<entry>&task-print-tot;</entry>
253
285
<entry>DNS server</entry>
286
<entry>&task-dns-inst;</entry>
287
<entry>&task-dns-dl;</entry>
288
<entry>&task-dns-tot;</entry>
260
292
<entry>File server</entry>
293
<entry>&task-file-inst;</entry>
294
<entry>&task-file-dl;</entry>
295
<entry>&task-file-tot;</entry>
267
299
<entry>Mail server</entry>
300
<entry>&task-mail-inst;</entry>
301
<entry>&task-mail-dl;</entry>
302
<entry>&task-mail-tot;</entry>
274
306
<entry>SQL database</entry>
307
<entry>&task-sql-inst;</entry>
308
<entry>&task-sql-dl;</entry>
309
<entry>&task-sql-tot;</entry>