linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Kreutzmann <debian@helgefjell.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: Errors in man pages, here: initrd(4): Markup
Date: Sun, 5 Jul 2020 21:50:25 +0200	[thread overview]
Message-ID: <20200705195024.GC24600@Debian-50-lenny-64-minimal> (raw)
In-Reply-To: <e7c88c22-f8b4-80f1-a1bc-fa0179ea8290@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2381 bytes --]

Hello Michael,
On Mon, Apr 20, 2020 at 10:18:41AM +0200, Michael Kerrisk (man-pages) wrote:
> I need more explanation of all of the remaining:

Sorry, missed this one.

> > --
> > Markup "linuxrc"
> > 
> > "It is also possible for the I</linuxrc> executable to change the normal root "
> > "device.  For I</linuxrc> to change the normal root device, I</proc> must be "
> > "mounted.  After mounting I</proc>, I</linuxrc> changes the normal root "
> > "device by writing into the proc files I</proc/sys/kernel/real-root-dev>, I</"
> > "proc/sys/kernel/nfs-root-name>, and I</proc/sys/kernel/nfs-root-addrs>.  For "
> > "a physical root device, the root device is changed by having I</linuxrc> "
> > "write the new root filesystem device number into I</proc/sys/kernel/real-"
> > "root-dev>.  For an NFS root filesystem, the root device is changed by having "
> > "I</linuxrc> write the NFS setting into files I</proc/sys/kernel/nfs-root-"
> > "name> and I</proc/sys/kernel/nfs-root-addrs> and then writing 0xff (e.g., "
> > "the pseudo-NFS-device number) into file I</proc/sys/kernel/real-root-dev>.  "
> > "For example, the following shell command line would change the normal root "
> > "device to I</dev/hdb1>:"
> > --
> > Markup "linuxrc"
> > 
> > "The main motivation for implementing B<initrd> was to allow for modular "
> > "kernel configuration at system installation."
> > --
> > Markup "linuxrc"
> > 
> > "The executable I</linuxrc> loads the necessary modules from the initial root "
> > "filesystem."
> > --
> > Markup "initrd"
> > 
> > "Last but not least, Linux distributions on CD-ROM may use B<initrd> for easy "
> > "installation from the CD-ROM.  The distribution can use B<LOADLIN> to "
> > "directly load I</dev/initrd> from CD-ROM without the need of any floppies.  "
> > "The distribution could also use a B<LILO> boot floppy and then bootstrap a "
> > "bigger RAM disk via I</dev/initrd> from the CD-ROM."

I cannot reproduce what the translator wanted to point out here.
Sorry. Please close.

Greetings

         Helge

-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2020-07-05 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19  6:48 Errors in man pages, here: initrd(4): Markup Helge Kreutzmann
2020-04-20  8:18 ` Michael Kerrisk (man-pages)
2020-07-05 19:50   ` Helge Kreutzmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200705195024.GC24600@Debian-50-lenny-64-minimal \
    --to=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).