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

Diff of /xml/htdocs/doc/en/openrc-migration.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<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openrc-migration.xml,v 1.4 2008/04/14 20:43:07 nightmorph Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openrc-migration.xml,v 1.5 2008/04/14 21:49:37 nightmorph Exp $ -->
4 4
5<guide link="/doc/en/openrc-migration.xml"> 5<guide link="/doc/en/openrc-migration.xml">
6<title>Baselayout and OpenRC Migration Guide</title> 6<title>Baselayout and OpenRC Migration Guide</title>
7 7
8<author title="Author"> 8<author title="Author">
22 22
23<!-- The content of this document is licensed under the CC-BY-SA license --> 23<!-- The content of this document is licensed under the CC-BY-SA license -->
24<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 24<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
25<license/> 25<license/>
26 26
27<version>1.2</version> 27<version>1.3</version>
28<date>2008-04-14</date> 28<date>2008-04-14</date>
29 29
30<chapter> 30<chapter>
31<title>Background</title> 31<title>Background</title>
32<section> 32<section>
189Please note the difference between <b>module_</b> and <b>modules_</b>. 189Please note the difference between <b>module_</b> and <b>modules_</b>.
190</note> 190</note>
191 191
192</body> 192</body>
193</section> 193</section>
194<section id="volume"> 194<section id="boot">
195<title>Volume management</title> 195<title>Boot runlevel</title>
196<body> 196<body>
197 197
198<p>
199Volume management services for your block storage devices should be
200automatically migrated for you when you switch to OpenRC and baselayout-2.
201However, in case they aren't, you'll need to follow the instructions below.
202</p> 198<p>
203 199The <c>boot</c> runlevel performs several important steps for every machine. For
200example, making sure your root filesystem is mounted read/write, that your
201filesystems are checked for errors, that your mountpoints are available, and
202that the <path>/proc</path> pseudo-filesystem is started at boot.
204<p> 203</p>
204
205<p>
205Volume management services for your block storage devices are no longer run by 206With OpenRC, volume management services for your block storage devices are no
206default. This means that lvm, raid, swap, device-mapper (dm), dm-crypt, evms, and the 207longer run automatically at boot. This includes lvm, raid, swap, device-mapper
207like will not be run automatically. If you use these addons, you will have to 208(dm), dm-crypt, evms, and the like. You must ensure the appropriate initscript
208add the proper initscript to the <c>boot</c> runlevel. Otherwise, it's possible 209for these services is in the <c>boot</c> runlevel, otherwise it's possible that
209your system will not boot. When you install the various volume management 210your system will not boot!
210services, they will install an appropriate initscript in
211<path>/etc/init.d</path>. You must ensure the appropriate initscript is in the
212<c>boot</c> runlevel.
213</p> 211</p>
214 212
215<p> 213<p>
216While the OpenRC ebuild will attempt to do this migration for you, you should 214While the OpenRC ebuild will attempt to do this migration for you, you should
217verify that it migrated all the volume management services properly. 215verify that it migrated all the volume management services properly:
218</p> 216</p>
219 217
220<pre caption="Check all services in boot runlevel"> 218<pre caption="Display all services in boot runlevel">
221# <i>ls -l /etc/runlevels/boot/</i> 219# <i>ls -l /etc/runlevels/boot/</i>
222</pre> 220</pre>
223 221
224<p> 222<p>
223If you don't see root, procfs, mtab, swap, and fsck in the above listing,
224perform the following to add them to the <c>boot</c> runlevel:
225</p>
226
227<pre caption="Adding missing volume management services to the boot runlevel">
228# <i>rc-update add root boot</i>
229# <i>rc-update add procfs boot</i>
230# <i>rc-update add mtab boot</i>
231# <i>rc-update add fsck boot</i>
232# <i>rc-update add swap boot</i>
233</pre>
234
235<p>
225If you know you use mdraid, lvm, and swap but do not see them above, you would run 236If you know you use mdraid and lvm but do not see them above, you would run
226the following to add initscripts to the <c>boot</c> runlevel. 237the following to add initscripts to the <c>boot</c> runlevel:
227</p> 238</p>
228 239
229<pre caption="Adding missing volume management services to the boot runlevel"> 240<pre caption="Adding missing volume management services to the boot runlevel">
230# <i>rc-update add raid boot</i> 241# <i>rc-update add raid boot</i>
231# <i>rc-update add lvm boot</i> 242# <i>rc-update add lvm boot</i>
232# <i>rc-update add swap boot</i>
233</pre>
234
235<p>
236Also, make sure your root filesystem is mounted read/write, that your
237filesystems are checked for errors, that your mountpoints are available, and
238that the <path>/proc</path> pseudo-filesystem is started at boot. Here's a handy
239shell script to make it happen:
240</p>
241
242<pre caption="Adding other critical services to the boot runlevel">
243# <i>for x in root fsck mtab procfs ; do rc-update add $x boot ; done</i>
244</pre> 243</pre>
245 244
246</body> 245</body>
247</section> 246</section>
248<section> 247<section>

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

  ViewVC Help
Powered by ViewVC 1.1.20