linux-um archives
 help / color / mirror / Atom feed
From: Patrick Kilian <petschge@gmx.de>
To: User-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] compile help texts for 2.4.*
Date: Mon, 29 Sep 2003 21:08:03 +0200	[thread overview]
Message-ID: <200309292108.03752.petschge@gmx.de> (raw)

Hi Jeff,

this should be the final version of the patch that adds the help texts from
2.6.0-test5 to the 2.4.* kernel branch. Please include this patch in the next
um patches if nobody objects.

This patch is again 2.4.22 but should work with any 2.4.* kernel.

-----

--- linux-2.4.22-uml/Documentation/Configure.help       Wed Sep 17 12:03:54 2003
+++ linux-2.4.22-uml2/Documentation/Configure.help      Mon Sep 29 21:00:38 2003
@@ -27646,6 +27646,98 @@
 CONFIG_CRYPTO_TEST
   Quick & dirty crypto test module.

+Separate Kernel Address Space support
+CONFIG_MODE_SKAS
+  This option controls whether skas (separate kernel address space)
+  support is compiled in.  If you have applied the skas patch to the
+  host and enabled support for /proc/mm in the host kernel, then you
+  certainly want to say Y here (and consider saying N to
+  CONFIG_MODE_TT).  Otherwise, it is safe to say Y.  Disabling this
+  option will shrink the UML binary slightly.
+
+Tracing thread support
+CONFIG_MODE_TT
+  This option controls whether tracing thread support is compiled
+  into UML.  Normally, this should be set to Y.  If you intend to
+  use only skas mode (and the host has the skas patch applied to it),
+  then it is OK to say N here.
+
+Force a static link
+CONFIG_STATIC_LINK
+  If CONFIG_MODE_TT is disabled, then this option gives you the ability
+  to force a static link of UML.  Normally, if only skas mode is built
+  in to UML, it will be linked as a shared binary.  This is inconvenient
+  for use in a chroot jail.  So, if you intend to run UML inside a
+  chroot, and you disable CONFIG_MODE_TT, you probably want to say Y
+  here.
+
+HoneyPot ProcFS
+CONFIG_HPPFS
+  hppfs (HoneyPot ProcFS) is a filesystem which allows UML /proc
+  entries to be overridden, removed, or fabricated from the host.
+  Its purpose is to allow a UML to appear to be a physical machine
+  by removing or changing anything in /proc which gives away the
+  identity of a UML.
+
+  See <http://user-mode-linux.sf.net/hppfs.html> for more information.
+
+  You only need this if you are setting up a UML honeypot.  Otherwise,
+  it is safe to say 'N' here.
+
+2G/2G host address space split
+CONFIG_HOST_2G_2G
+  Most Linux machines are configured so that the kernel occupies the
+  upper 1G of the 4G address space and processes use the lower 3G.
+  However, some machine are configured with a 2G/2G split, with the
+  kernel occupying the upper 2G and processes using the lower 2G.
+
+  To allow UML to run on a such host you have to say Y here. N should be
+  a safe choice most of the time.
+
+Support for /proc/mm
+CONFIG_PROC_MM
+  Enables support for address space separation through /proc/mm.
+  A host kernel needs to have this enabled in order for UML to
+  run in skas mode.  UML kernels do not need to have this option
+  unless they will host sub-UMLs.
+
+  If you don't know what this does just say Y.
+
+Kernel stack size order
+CONFIG_KERNEL_STACK_ORDER
+  This option determines the size of UML kernel stacks.  They will
+  be 1 << order pages.  The default is OK unless you're running Valgrind
+  on UML, in which case, set this to 3.
+
+Anonymous Memory support
+CONFIG_DEV_ANON
+  Don't ask. Just say Y.
+
+Support for software watchdog inside UML
+CONFIG_UML_WATCHDOG
+  Support for a virtual hardware watchdog. It's safe to say N here.
+
+COW block device
+CONFIG_COW
+  This is a layered driver which sits above two other block devices.
+  One is read-only, and the other is a read-write layer which stores
+  all changes.  This provides the illusion that the read-only layer
+  can be mounted read-write and changed.
+
+pcap transport
+CONFIG_UML_NET_PCAP
+ The pcap transport makes a pcap packet stream on the host look
+  like an ethernet device inside UML.  This is useful for making
+  UML act as a network monitor for the host.  You must have libcap
+  installed in order to build the pcap transport into UML.
+
+  For more information, see
+  <http://user-mode-linux.sourceforge.net/networking.html>  That site
+  has examples of the UML command line to use to enable this option.
+
+  If you intend to use UML as a network monitor for the host, say
+  Y here.  Otherwise, say N.
+
 #
 # A couple of things I keep forgetting:
 #   capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,

-----

mfg,
Patrick "Petschge" Kilian

-- 
Ein Passender Vergleich wuerde einen Braunkohletagebaufoerderbagger
mit einbeziehen. Dieser ist zu Strassen so kompatibel wie Notes zu
SMTP.		-- Jürgen P. Meier in d.a.s.r



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

             reply	other threads:[~2003-09-29 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 19:08 Patrick Kilian [this message]
2003-11-09 20:31 ` [uml-devel] compile help texts for 2.4.* Jeff Dike

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=200309292108.03752.petschge@gmx.de \
    --to=petschge@gmx.de \
    --cc=User-mode-linux-devel@lists.sourceforge.net \
    --cc=petschge@web.de \
    /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