Vserver is a patch that implements BSD jail style virtual host semantics
inside Linux, where every process not only runs in its own namespace (it
reuses the chroot code for that, should switch to CLONE_NEWNS for 2.6),
but also its own hostname and IP address as well as its own view of
/proc.

Because of that added functionality, it needs more than what is
available in the LSM framework (which can only allow/deny permissions,
not alter return values).

The source code has been running stable for the last few years and is in
use at quite a few service providers.  The Fedora project also wants to
use vserver for their build system.  However, vserver for 2.4 just tacks
their syscalls onto the end of the syscall table and the userland tools
find those "dynamic numbers" somehow ...  EWWWW.

For 2.6 I'd like to do things right.  At the moment the vserver patch
has sys_new_s_context and sys_set_ipv4root calls, but since we'll
probably end up getting an ipv6 call too and people are planning future
functionality, I guess it would be more appropriate to multiplex these
through one sys_vserver patch, in the same way sys_ipc works.

For your reference, you can find more information about
vserver on these pages:

	http://www.13thfloor.at/VServer/
	http://www.solucorp.qc.ca/miscprj/s_context.hc

I estimate the project has about a dozen developers now.  We are
planning on making the implementation for 2.6 fairly lightweight,
reusing infrastructure from other code where possible and only doing
things through sys_vserver where there is no other way.

This small change just adds sys_vserver to the syscall table.

This picks up another place where aliases where getting lost.  And adds
a couple of checks.  I can't hang the osdl database thingy anymore.

The transfer alias list loops could probably quite nicely be changed to

	if (unlikely(!list_empty( old_queuelist )))
	    __list_splice( old_queuelist, new_queuelist.prev);

There doesn't seem to be any active maintainer for EFS: It's either
abandoned, or never required specific patches too badly (also quite
possible in this case). 

It went into the tree in 2.3.2 and from there to 2.6.0-test6 I see
nothing that would look like maintainer's update.  OTOH, it's read-only
and shouldn't be too badly broken (or hard to keep alive).

Outside of trunk (i.e.  in 2.4.16--) we have a backport of global 2.5
change (sb_bread()) and check for set_blocksize() failures (from Alan). 
This is the 2.6.x equivalent.

into home.osdl.org:/home/torvalds/v2.5/linux

into home.osdl.org:/home/torvalds/v2.5/linux

into home.osdl.org:/home/torvalds/v2.5/linux

into home.osdl.org:/home/torvalds/v2.5/linux

ide-floppy has screwy bio handling. I rewrote it and got confirmation
from one tester (the only one :) that it actually works now.

into intel.com:/home/lenb/bk/linux-acpi-release-2.6.0

into intel.com:/home/lenb/bk/linux-acpi-test-2.6.0

PA-RISC updates for 2.6.0-test6
 - Some more support for 64-bit userspace
 - Move many EXPORT_SYMBOLs out of parisc_ksyms.c
 - Make both the OSS and ALSA harmony drivers build
 - ioctl typechecking
 - Make math-emu build without warnings.
 - Persuade SuckyIO to not crash the machine.

ELF_CORE_SYNC and dump_smp_unlazy_fpu seem to have been introduced
by Ingo around 2.5.43, but as far as I can tell, never used.

It might not have prevented me from reporting the potential bug, but I
would've known you'd thought about it, it might help future developers,
and it's unlikely to become dangerously wrong.

into kroah.com:/home/linux/BK/pci-2.5

into home.osdl.org:/home/torvalds/v2.5/linux