Remove some programs which live as atf tests now.

Add a test/example program for using audio/pad in a rump kernel.
It stuffs some nice sounds into the virtual kernel's /dev/audio,
reads the PCM from /dev/pad, and writes the data to stdout from
where it can be piped to audioplay to test that things actually
work.

If you want to know the secret message, you'll just have to run
this program ;)

Add an example/test program for rump bluetooth. This does discovery
and prints the address and name of the first peer encountered (if any):

ubt0 at uhub0 port 1
ubt0: Cambridge Silicon Radio Bluetooth USB Adapter, rev 2.00/19.15, addr 2
device ubt0, addr xx:xx:xx:xx:xx:xx
my peer: yy:yy:yy:yy:yy:yy, major class: 2 (phone)
peer name: Mokia maailmalta

Add a simple tty server which attaches to /dev/ttyU in the rump
kernel and provides the same device on the host with pud(4). I
can succesfully talk to my u3g device using tip(1) against the
server's devices. Some characters are lost here and there, though
(probably a problem with interrupt pipes in ugenhc). Once that
issues is solved, there is no reason why e.g. pppd (chat) could
not be used against the server.

Now, why would anyone want to do this instead of using the kernel
driver directly? Well, for one, on my laptop I run netbsd-5 which
doesn't have a u3g driver which supports the u3g hardware I have.

As anyone with half an eye can see, this is quite copypasted from
umserv and there is plenty of opportunity for uncopypasting for
the eager vi-wielder.

descend into new subdirs

Stick a top-level subdir-makefile here for easy build-testing.

Add readme explaining which grue has ok'd the eating of some code
until recently located here.

Add an example/test program for rump bluetooth. This does discovery
and prints the address and name of the first peer encountered (if any):

ubt0 at uhub0 port 1
ubt0: Cambridge Silicon Radio Bluetooth USB Adapter, rev 2.00/19.15, addr 2
device ubt0, addr xx:xx:xx:xx:xx:xx
my peer: yy:yy:yy:yy:yy:yy, major class: 2 (phone)
peer name: Mokia maailmalta

Add an example/test program for rump bluetooth. This does discovery
and prints the address and name of the first peer encountered (if any):

ubt0 at uhub0 port 1
ubt0: Cambridge Silicon Radio Bluetooth USB Adapter, rev 2.00/19.15, addr 2
device ubt0, addr xx:xx:xx:xx:xx:xx
my peer: yy:yy:yy:yy:yy:yy, major class: 2 (phone)
peer name: Mokia maailmalta

Fix some small bugs pointed out byt pooka@. Remove not needed -D defines and
do not include private kernel header files. Instead copy part of it to test
program.

Add small testing program which uses RUMP libdm to test device-mapper
functionality in userspace.

Include public interface describing user-kernel interface from include/dev/dm.

Fix some small bugs pointed out byt pooka@. Remove not needed -D defines and
do not include private kernel header files. Instead copy part of it to test
program.

Add small testing program which uses RUMP libdm to test device-mapper
functionality in userspace.

Add small testing program which uses RUMP libdm to test device-mapper
functionality in userspace.

Add small testing program which uses RUMP libdm to test device-mapper
functionality in userspace.

update component lists: scsipi is independent of umass now

* support cd devices (@scsibus & @atapibus, per libumass)
* support cd9660
* add "probe" keyword, which just prints the dmesg in verbose form

rumpusbhc is now ugenhc

WARNS

Try ffs is msdosfs mount fails -- I happened to have one USB stick
where the file system is ffs.

Add an example program which shows how to mount and read files from
an msdos file system which is located on a usb stick. What makes
this special is that the USB driver stack (and the file system
driver, of course) is run in rump instead of in the host kernel.

Check open return value and close fd when we're done.

Use DIOCTUR to test if a newly configured CD drive is ready instead
of playing a random waiting game.

Pause after probe here too, so that you can amuse yourself by
unplugging and replugging devices and looking at the detach/attach
feedback messages.

* support cd devices (@scsibus & @atapibus, per libumass)
* support cd9660
* add "probe" keyword, which just prints the dmesg in verbose form

Try ffs is msdosfs mount fails -- I happened to have one USB stick
where the file system is ffs.

Add an example program which shows how to mount and read files from
an msdos file system which is located on a usb stick. What makes
this special is that the USB driver stack (and the file system
driver, of course) is run in rump instead of in the host kernel.

tty support is in rumpkern_tty now

rumpusbhc is now ugenhc

Add a simple terminal program which uses a rump kernel for a ucom@usb
terminal and host terminal stdin/stdout for human interaction.
Tipsy just simply shovels bits between the two. I can use my
JavaStation Krups (*) serial console with this ... without having
to worry abort those pesky usb drivers crashing my desktop kernel.

*) strictly speaking it's uwe's ;)

In "probeonly", pause after bootstrap to make "monkey plug and
unplug device, monkey see fancy dmesg info" possible.

Add a simple terminal program which uses a rump kernel for a ucom@usb
terminal and host terminal stdin/stdout for human interaction.
Tipsy just simply shovels bits between the two. I can use my
JavaStation Krups (*) serial console with this ... without having
to worry abort those pesky usb drivers crashing my desktop kernel.

*) strictly speaking it's uwe's ;)

add -D_KERNTYPES

tty support is in rumpkern_tty now

Add a simple tty server which attaches to /dev/ttyU in the rump
kernel and provides the same device on the host with pud(4). I
can succesfully talk to my u3g device using tip(1) against the
server's devices. Some characters are lost here and there, though
(probably a problem with interrupt pipes in ugenhc). Once that
issues is solved, there is no reason why e.g. pppd (chat) could
not be used against the server.

Now, why would anyone want to do this instead of using the kernel
driver directly? Well, for one, on my laptop I run netbsd-5 which
doesn't have a u3g driver which supports the u3g hardware I have.

As anyone with half an eye can see, this is quite copypasted from
umserv and there is plenty of opportunity for uncopypasting for
the eager vi-wielder.

Don't include <rump/rumpvnode_if.h> from rump.h. It's not needed
unless you're doing something special, but requires register_t.
Adjust the few places which actually need rumpvnode_if.h.

Clean up vnode lock operations pass 2:

VOP_UNLOCK(vp, flags) -> VOP_UNLOCK(vp): Remove the unneeded flags argument.

Welcome to 5.99.32.

Discussed on tech-kern.

Add a simple tty server which attaches to /dev/ttyU in the rump
kernel and provides the same device on the host with pud(4). I
can succesfully talk to my u3g device using tip(1) against the
server's devices. Some characters are lost here and there, though
(probably a problem with interrupt pipes in ugenhc). Once that
issues is solved, there is no reason why e.g. pppd (chat) could
not be used against the server.

Now, why would anyone want to do this instead of using the kernel
driver directly? Well, for one, on my laptop I run netbsd-5 which
doesn't have a u3g driver which supports the u3g hardware I have.

As anyone with half an eye can see, this is quite copypasted from
umserv and there is plenty of opportunity for uncopypasting for
the eager vi-wielder.

rumpusbhc is now ugenhc

Add an example program which reads keypresses from the ukbd driver
(via wscons) and simply prints them on screen.

Add an example program which reads keypresses from the ukbd driver
(via wscons) and simply prints them on screen.

rumpusbhc is now ugenhc

Add an example to show how to print with a rump ulpt driver.

Add an example to show how to print with a rump ulpt driver.

rumpusbhc is now ugenhc

Read mouse events from wsmouse and move a silly curses cursor around
the screen (quite poorly, i might add ;).

Read mouse events from wsmouse and move a silly curses cursor around
the screen (quite poorly, i might add ;).

add -D_KERNTYPES

update component lists: scsipi is independent of umass now

rumpusbhc is now ugenhc

Add a simple example of how to run the kernel umass/USB in userspace
and attach it back to the host kernel using pud(4). The result is
pretty much indistinguisable from if kernel drivers were used.

It's possible to e.g. mount a file system backed by the userspace
block device driver:

golem> disklabel ./rumpsd0d
[...]
5 partitions:
# size offset fstype [fsize bsize cpg/sgs]
d: 1994752 0 unused 0 0 # (Cyl. 0 - 3895)
e: 1994512 240 MSDOS # (Cyl. 0*- 3895)

golem> s mount_msdos ./rumpsd0a /mnt
mount_msdos: "./rumpsd0a" is a non-resolved or relative path.
mount_msdos: using "/usr/home/pooka/src/umserv/rumpsd0a" instead.
mount_msdos: /usr/home/pooka/src/umserv/rumpsd0a on /mnt: Device not configured

golem> s mount_msdos ./rumpsd0e /mnt
mount_msdos: "./rumpsd0e" is a non-resolved or relative path.
mount_msdos: using "/usr/home/pooka/src/umserv/rumpsd0e" instead.
golem> df -h /mnt
Filesystem Size Used Avail %Cap Mounted on
/usr/home/pooka/src/umserv/rumpsd0e 974M 5.2M 968M 0% /mnt

etcetc.

Don't include <rump/rumpvnode_if.h> from rump.h. It's not needed
unless you're doing something special, but requires register_t.
Adjust the few places which actually need rumpvnode_if.h.

Clean up vnode lock operations pass 2:

VOP_UNLOCK(vp, flags) -> VOP_UNLOCK(vp): Remove the unneeded flags argument.

Welcome to 5.99.32.

Discussed on tech-kern.

Add a simple example of how to run the kernel umass/USB in userspace
and attach it back to the host kernel using pud(4). The result is
pretty much indistinguisable from if kernel drivers were used.

It's possible to e.g. mount a file system backed by the userspace
block device driver:

golem> disklabel ./rumpsd0d
[...]
5 partitions:
# size offset fstype [fsize bsize cpg/sgs]
d: 1994752 0 unused 0 0 # (Cyl. 0 - 3895)
e: 1994512 240 MSDOS # (Cyl. 0*- 3895)

golem> s mount_msdos ./rumpsd0a /mnt
mount_msdos: "./rumpsd0a" is a non-resolved or relative path.
mount_msdos: using "/usr/home/pooka/src/umserv/rumpsd0a" instead.
mount_msdos: /usr/home/pooka/src/umserv/rumpsd0a on /mnt: Device not configured

golem> s mount_msdos ./rumpsd0e /mnt
mount_msdos: "./rumpsd0e" is a non-resolved or relative path.
mount_msdos: using "/usr/home/pooka/src/umserv/rumpsd0e" instead.
golem> df -h /mnt
Filesystem Size Used Avail %Cap Mounted on
/usr/home/pooka/src/umserv/rumpsd0e 974M 5.2M 968M 0% /mnt

etcetc.

amazing grep, how sweet the find
that saved a hack like me
script once was lost but now it's found
was -x, but now I sh

Add an example for a rump router cluster setup along with a README.

some contributions to the code from Martti Kuparinen

send routing messages via routing sucket -- works better than via inet sucket

Fix pointer assignment in previous commit (test compile works better
when you do it with the #defines which actually compile the code
in question).

Use a bit more than 1 byte of space for routing messages.

fix typo in, um, copyright.

spotted by a keen-eyed enthusiast ;)

Add an example for a rump router cluster setup along with a README.

some contributions to the code from Martti Kuparinen

amazing grep, how sweet the find
that saved a hack like me
script once was lost but now it's found
was -x, but now I sh

mirror change of -lrumpcrypto ==> -lrumpkern_crypto

rumpusbhc is now ugenhc

The rumpdev_net80211 until-recently-wip component is now rumpnet_net80211.

WARNS + make compile

Add an example program which shows how to do "ifconfig rum0 up".
What makes this special is that the USB driver stack, the rum
driver, network subroutines and net80211 are running in userspace
in a rump kernel instead of in the host kernel.

* use rump_boot_sethowto()
* fail in a nicer way if interface device is not probed

WARNS + make compile

Add an example program which shows how to do "ifconfig rum0 up".
What makes this special is that the USB driver stack, the rum
driver, network subroutines and net80211 are running in userspace
in a rump kernel instead of in the host kernel.