From: Manbing <manbing3@gmail.com>
To: Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: Manbing <manbing3@gmail.com>,
linux-um@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation: update UserModeLinux-HOWTO.txt
Date: Sun, 23 Feb 2020 01:19:27 +0800 [thread overview]
Message-ID: <1582391968-3960-1-git-send-email-manbing3@gmail.com> (raw)
Original content is obsolete. Which is based on kernel 2.4.0-prerelease.
Updating content according to kernel 5.5.1.
Signed-off-by: Manbing <manbing3@gmail.com>
---
Documentation/virt/uml/UserModeLinux-HOWTO.txt | 42 +++++---------------------
1 file changed, 8 insertions(+), 34 deletions(-)
diff --git a/Documentation/virt/uml/UserModeLinux-HOWTO.txt b/Documentation/virt/uml/UserModeLinux-HOWTO.txt
index 87b80f5..08ee28d 100644
--- a/Documentation/virt/uml/UserModeLinux-HOWTO.txt
+++ b/Documentation/virt/uml/UserModeLinux-HOWTO.txt
@@ -1,6 +1,6 @@
User Mode Linux HOWTO
User Mode Linux Core Team
- Mon Nov 18 14:16:16 EST 2002
+ Mon Feb 10 08:27:24 EST 2020
This document describes the use and abuse of Jeff Dike's User Mode
Linux: a port of the Linux kernel as a normal Intel Linux process.
@@ -215,26 +215,17 @@
Compiling the user mode kernel is just like compiling any other
- kernel. Let's go through the steps, using 2.4.0-prerelease (current
+ kernel. Let's go through the steps, using 5.5.1 (current
as of this writing) as an example:
- 1. Download the latest UML patch from
-
- the download page <http://user-mode-linux.sourceforge.net/
-
- In this example, the file is uml-patch-2.4.0-prerelease.bz2.
-
-
- 2. Download the matching kernel from your favourite kernel mirror,
+ 1. Download the matching kernel from your favourite kernel mirror,
such as:
- ftp://ftp.ca.kernel.org/pub/kernel/v2.4/linux-2.4.0-prerelease.tar.bz2
- <ftp://ftp.ca.kernel.org/pub/kernel/v2.4/linux-2.4.0-prerelease.tar.bz2>
- .
+ wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.5.1.tar.xz
- 3. Make a directory and unpack the kernel into it.
+ 2. Make a directory and unpack the kernel into it.
@@ -255,31 +246,14 @@
host%
- tar -xzvf linux-2.4.0-prerelease.tar.bz2
-
-
-
-
-
-
- 4. Apply the patch using
-
-
-
- host%
- cd ~/uml/linux
-
-
-
- host%
- bzcat uml-patch-2.4.0-prerelease.bz2 | patch -p1
+ tar xvf linux-5.5.1.tar.xz
- 5. Run your favorite config; `make xconfig ARCH=um' is the most
+ 3. Run your favorite config; `make xconfig ARCH=um' is the most
convenient. `make config ARCH=um' and 'make menuconfig ARCH=um'
will work as well. The defaults will give you a useful kernel. If
you want to change something, go ahead, it probably won't hurt
@@ -293,7 +267,7 @@
- 6. Finish with `make linux ARCH=um': the result is a file called
+ 4. Finish with `make linux ARCH=um': the result is a file called
`linux' in the top directory of your source tree.
Make sure that you don't build this kernel in /usr/src/linux. On some
--
2.7.4
next reply other threads:[~2020-02-22 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 17:19 Manbing [this message]
2020-02-22 18:17 ` [PATCH] Documentation: update UserModeLinux-HOWTO.txt Anton Ivanov
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=1582391968-3960-1-git-send-email-manbing3@gmail.com \
--to=manbing3@gmail.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=corbet@lwn.net \
--cc=jdike@addtoit.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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).