Changeset b7d0bb4 for postlfs/config
- Timestamp:
- 10/04/2003 12:28:30 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:
- 2fa79e3b
- Parents:
- 2be0e0d
- Location:
- postlfs/config
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/config/bootdisk.xml
r2be0e0d rb7d0bb4 14 14 15 15 <para>Heeding the warning, the rescue disk created here has no 16 dependency on the host system's resources, other than basic boot ability16 dependency on the host system's resources, other than basic boot-ability 17 17 and hardware soundness. At a minimum, the most common sorts of failures 18 18 requiring a rescue boot disk should be addressed by the contents of the … … 66 66 <para>You should make a custom kernel that includes only those features 67 67 needed to rescue your system, so it will have the least size. No 68 sense in building in support for things like <application> xfree86</application>,69 <application> dri</application>, etc, as most rescues are performed from the68 sense in building in support for things like <application>XFree86</application>, 69 <application>DRI</application>, etc, as most rescues are performed from the 70 70 command prompt. Along the same lines, if you have <xref linkend="gcc2"/>, it 71 71 is known to produce smaller kernels. So you might want to use that … … 74 74 compiled with same compiler used to make the kernel.</para> 75 75 76 <para>The rescue image must include support for the file system of your76 <para>The rescue-image must include support for the file system of your 77 77 choice (we presume ext2/3 here), ramdisk and initial ramdisk (initrd). 78 78 Disable everything that you can in the kernel configuration. You should … … 209 209 210 210 <para><emphasis>A cautionary note:</emphasis> if you are not running in a 211 <command>chroot</command> environment, be sure that you do not accident lly211 <command>chroot</command> environment, be sure that you do not accidentally 212 212 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 … … 295 295 No other editing is needed because the boot scripts are not included and 296 296 no automatic mounting will be done using the <filename>fstab</filename>. 297 If you decide to include some boot scripts that might try to mount297 If you decide to include some boot scripts that might try to mount 298 298 things, change the <filename>fstab</filename>'s entries to 299 299 <command>noauto</command> in the options field so they don't cause an -
postlfs/config/compressdoc.xml
r2be0e0d rb7d0bb4 144 144 } 145 145 146 # OK, parse the command 146 # OK, parse the command-line for arguments, and initialize to some sensible 147 147 # state, that is keep hardlinks, parse /etc/man.conf, be most silent, search 148 148 # man.conf in /etc, and don't force (re-)compression. -
postlfs/config/profile.xml
r2be0e0d rb7d0bb4 15 15 <filename>/bin/login</filename>, by reading the 16 16 <filename>/etc/passwd</filename> file. An 17 interactive non-login shell is started at the command 17 interactive non-login shell is started at the command-line (e.g. 18 18 <prompt>[prompt]$</prompt><command>/bin/bash</command>). A non-interactive 19 19 shell is usually present when a shell script is running. It is non-interactive
Note:
See TracChangeset
for help on using the changeset viewer.