user-mode port 0.58-2.4.18-36

Jeff Dike (jdike@karaya.com)
Fri, 05 Jul 2002 17:50:17 -0500


This is the fourth release of the 2.4.18 UML.

The major changes in this release include:

It is now possible the to attach the UML gdb to sleeping threads.
This is done by detaching gdb from the in-context thread and attaching
it to the host pid of the sleeping UML process. UML may be continued
by reattaching to the in-context thread. This feature was sponsored
by Cluster File Systems, Inc.

There is a /proc/exitcode, which allows a UML process to set the
eventual UML exit code.

Fixed some segfaults caused by calling openpty, which has an unusually
large stack frame, overflowing the UML kernel stack.

The tty logging patch is integrated. This allows UML honeypots to
log all tty traffic to a host file. This logging can't be detected
or interfered with by root inside the UML.

UML now has a "hardware" watchdog.

The UML binary now lives in its own physical memory. This makes it
easier for the swsusp patch to be ported to UML.

Fixed a bug with lots of zombies causing a UML panic.

It is now possible to move backing files and update the COW files with
ubdx=cow-file,new-backing-file. Note that you must preserve the
modification time when moving a backing file with something like
'cp -p' or 'tar p'.

Added support for kernel watchpoints. They can be mixed with
watchpoints in gdb inside UML.

Fixed the bug which was closing file descriptors which should have
been left open. This was most often seen as a panic during UML
shutdown, although it also appeared in other places.

The mconsole driver now sends panic notifications to mconsole clients.

A number of smaller bugs were fixed and features added.

The project's home page is http://user-mode-linux.sourceforge.net

Downloads are available at
http://user-mode-linux.sourceforge.net/dl-sf.html

Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/