/[gentoo]/xml/htdocs/doc/en/migration-to-2.6.xml
Gentoo

Diff of /xml/htdocs/doc/en/migration-to-2.6.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.4 Revision 1.5
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3 3
4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/migration-to-2.6.xml,v 1.4 2004/11/27 14:19:18 neysx Exp $ --> 4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/migration-to-2.6.xml,v 1.5 2004/11/28 14:26:04 swift Exp $ -->
5 5
6<guide link="/doc/en/migration-to-2.6.xml"> 6<guide link="/doc/en/migration-to-2.6.xml">
7 7
8<title>The complete Gentoo Linux 2.6 migration guide</title> 8<title>The complete Gentoo Linux 2.6 migration guide</title>
9 9
26<abstract> 26<abstract>
27This document will aid you in the process of migrating from Linux 2.4 to Linux 27This document will aid you in the process of migrating from Linux 2.4 to Linux
282.6, devfs to udev and OSS to ALSA. 282.6, devfs to udev and OSS to ALSA.
29</abstract> 29</abstract>
30 30
31<version>0.1.2</version> 31<version>0.1.3</version>
32<date>2004-11-27</date> 32<date>2004-11-28</date>
33 33
34<chapter> 34<chapter>
35<title>Introduction</title> 35<title>Introduction</title>
36 36
37<section> 37<section>
200<p> 200<p>
201You should now remove modutils and install module-init-tools: 201You should now remove modutils and install module-init-tools:
202</p> 202</p>
203 203
204<pre caption="Switching from modutils to module-init-tools"> 204<pre caption="Switching from modutils to module-init-tools">
205# <i>emerge unmerge modutils</i> 205# <i>emerge unmerge sys-apps/modutils</i>
206# <i>emerge module-init-tools</i> 206# <i>emerge module-init-tools</i>
207</pre> 207</pre>
208 208
209<note> 209<note>
210Don't worry - even though you have just unmerged modutils, module-init-tools 210Don't worry - even though you have just unmerged modutils, module-init-tools
229udev: 229udev:
230</p> 230</p>
231 231
232<pre caption="Installing udev"> 232<pre caption="Installing udev">
233# <i>emerge -a udev</i> 233# <i>emerge -a udev</i>
234</pre>
235
236</body>
237</section>
238<section>
239<title>Checking for essential device nodes</title>
240<body>
241
242<p>
243When the system boots up, the system requires some essential device nodes. As
244udev is not included in the kernel, it is not activated immediately. To work
245around this, you must ensure that you have some essential device nodes on your
246disk.
247</p>
248
249<p>
250Our installation stage files will have created the required devices during the
251initial installation. However, some users have reported that this is not the
252case. We will use this opportunity to check that the device files exist, and
253create them if they do not.
254</p>
255
256<p>
257As your existing device manager will be mounted at /dev, we cannot access it
258directly. So we will bind-mount your root partition to another location and
259access the /dev directory from there.
260</p>
261
262<pre caption="Bind-mounting your root partition and listing static devices">
263# <i>mkdir -p /mnt/temp</i>
264# <i>mount -o bind / /mnt/temp</i>
265# <i>cd /mnt/temp/dev</i>
266# <i>ls -l console null</i>
267</pre>
268
269<p>
270If the above <e>ls</e> command reported that either <c>console</c> or
271<c>null</c> do not exist, then you must create them yourself, as shown below.
272</p>
273
274<pre caption="Creating the missing console and null nodes">
275# <i>mknod -m 660 console c 5 1</i>
276# <i>mknod -m 660 null c 1 3</i>
277</pre>
278
279<p>
280You should now unmount your bind-mounted root partition, even if you did not
281have to create those devices:
282</p>
283
284<pre caption="Unmounting the bind-mounted root">
285# <i>umount /mnt/temp</i>
234</pre> 286</pre>
235 287
236</body> 288</body>
237</section> 289</section>
238<section> 290<section>

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.5

  ViewVC Help
Powered by ViewVC 1.1.20