Changeset 8604d92f for postlfs/config/bootdisk.xml
- Timestamp:
- 10/01/2003 12:45:19 AM (21 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- bb363985
- Parents:
- 2df36e4
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/config/bootdisk.xml
r2df36e4 r8604d92f 149 149 150 150 <para><parameter>bs=1k count=4096</parameter>: These parameters tell 151 < filename>dd</filename> to read and write in "chunks" of 1024 bytes and151 <command>dd</command> to read and write in "chunks" of 1024 bytes and 152 152 process 4096 "chunks".</para> 153 153 … … 157 157 the version of <command>mount</command> (older ones don't have the 158 158 <userinput>-o loop</userinput> option) or if <filename>/etc/mtab</filename> 159 is symlinked to <filename >/proc</filename> (which causes mount to be159 is symlinked to <filename class="directory">/proc</filename> (which causes mount to be 160 160 unable to properly "unbind" a loop device, due to "lost" information). 161 161 An alternate set of commands is provided, after these three commands, … … 186 186 <option>-o loop</option> option <emphasis>and</emphasis> your 187 187 <filename>/etc/mtab</filename> is a real file, rather than a symlink to 188 <filename >/proc</filename>, the three above commands can be replaced188 <filename class="directory">/proc</filename>, the three above commands can be replaced 189 189 by these next two commands.</para> 190 190 … … 204 204 command tells <command>mount</command> to bind the named file to a 205 205 loopback device it automatically selects (the first available) and mount 206 the device on <filename >/mnt/loop1</filename>.</para>206 the device on <filename class="directory">/mnt/loop1</filename>.</para> 207 207 208 208 <para><emphasis>Add components to the file system</emphasis></para> … … 210 210 <para><emphasis>A cautionary note:</emphasis> if you are not running in a 211 211 <command>chroot</command> environment, be sure that you do not accidently 212 omit the <filename >/mnt/loop1</filename> reference in the commands. If212 omit the <filename class="directory">/mnt/loop1</filename> reference in the commands. If 213 213 you do so, you might replace the equivalent components on your host with 214 214 the components that are installed by these procedures. Even if you are … … 258 258 /mnt/loop1/dev</command></userinput></screen> 259 259 260 <para><emphasis>What is needed in the <filename >/etc</filename>260 <para><emphasis>What is needed in the <filename class="directory">/etc</filename> 261 261 directory</emphasis></para> 262 262 … … 276 276 diskette to carry these files.</para> 277 277 278 <para>Some might like to copy their <filename >/etc/rc*</filename>278 <para>Some might like to copy their <filename class="directory">/etc/rc*</filename> 279 279 directory into the ramdisk image, but this may have no value, other 280 280 than archival use, in a worst-case recovery scenario. If you want … … 298 298 <command>noauto</command> in the options field so they don't cause an 299 299 attempt to mount a potentially corrupt partition. Copy it to 300 <filename >/tmp</filename>, edit it as desired and then:</para>300 <filename class="directory">/tmp</filename>, edit it as desired and then:</para> 301 301 302 302 <screen><userinput><command>cp -a /tmp/fstab /mnt/loop1/etc</command></userinput></screen> … … 309 309 control to <command>linuxrc</command> (<application><ulink 310 310 url="http://www.busybox.net/downloads/busybox-0.60.4.tar.bz2">busybox 311 </ulink></application>). It wants to run an <filename >/etc/init.d/rcS</filename>311 </ulink></application>). It wants to run an <filename class="directory">/etc/init.d/rcS</filename> 312 312 script to do any initial setup.</para> 313 313 314 314 <para>If you use devfsd, you will need to set up the 315 315 <filename>rcS</filename> script to handle the devfsd startup. Put the 316 following commands in <filename >/mnt/loop1/etc/init.d/rcS</filename>.316 following commands in <filename class="directory">/mnt/loop1/etc/init.d/rcS</filename>. 317 317 You may also want to add some of the processes shown in the non-devfs 318 318 version that follows.</para> … … 322 322 /sbin/devfsd /dev</userinput></screen> 323 323 324 <para>If you don't use devfsd, but created a static <filename>/dev</filename> 324 <para>If you don't use devfsd, but created a static <filename 325 class="directory">/dev</filename> 325 326 directory using <command>MAKEDEV</command>, or any similar process, the 326 327 <filename>rcS</filename> script will do slightly different things. … … 329 330 files, thus saving space on the diskette.</para> 330 331 331 <para>The script made next will mount <filename >/proc</filename>, turn332 <para>The script made next will mount <filename class="directory">/proc</filename>, turn 332 333 on swap (no harm is done if it fails), make the 333 334 <filename>/etc/passwd</filename> and <filename>/etc/group</filename> … … 533 534 534 535 <para>To make a single-floppy rescue, using devfs, use the following 535 commands. If you use the static <filename >/dev</filename> setup, use536 commands. If you use the static <filename class="directory">/dev</filename> setup, use 536 537 <filename>/dev/fd0</filename> instead of the /dev/floppy/0.</para> 537 538 … … 545 546 the kernel will use when it boots. Because it loads an initrd, it will 546 547 automatically set that as the root device, initially. So, the 547 < userinput>0,0</userinput> gives it "no value", telling the kernel to not548 <option>0,0</option> gives it "no value", telling the kernel to not 548 549 mount any other device. Some folks give <filename>/dev/fd0</filename> or 549 550 something similar. But this has effect <emphasis>only</emphasis> when … … 588 589 following commands, with the proper numbers inserted. Notice that the 589 590 <command>seek</command> parameter's number must be the size, in blocks, 590 of your kernel image. If you use the static <filename >/dev</filename>591 of your kernel image. If you use the static <filename class="directory">/dev</filename> 591 592 setup, use <filename>/dev/fd0</filename> in the commands below, instead 592 593 of <filename>/dev/floppy/0</filename>.</para>
Note:
See TracChangeset
for help on using the changeset viewer.