>>> Yes, I am volunteering if nobody else wants to do it.
>> In this case I volunteer to do some spellchecking and proof reading ;-)
> Cool, patches like that are useful and easy to merge...
I didn't want to way for something to proof read, so I started on my own.
Most descriptions are the same as in 2.6.0-test5. Please pay special
attention to the follwoing help textes, as I have written them on my own.
--- linux-2.4.22-uml/Documentation/Configure.help Wed Sep 17 12:03:54
+++ linux-2.4.22-uml2/Documentation/Configure.help Thu Sep 18 18:31:42
@@ -27646,6 +27646,96 @@
Quick & dirty crypto test module.
+Separate Kernel Address Space support
+ This option controls whether skas (separate kernel address space)
+ support is compiled in. If you have applied the skas patch to the
+ host, 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
+ 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
+ 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
+ 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
+ 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 host you have to say Y here. N should be
+ a save choice most of the time.
+Support for high memory
+ Currently broken, so N is the save answer.
+Support for /proc/mm
+ If you don't know what this does just say Y.
+Kernel stack size 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
+ Don't ask. Just say Y.
+Support for software watchdog inside UML
+ It's save to say N here.
+COW block device
+ 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.
+ 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,
Patrick "Petschge" Kilian
Erst wenn das letzte Closed-Source-System gehackt ist, werdet ihrmerken,
dass man Sicherheit nicht durch Verschleierung oder durch