branches: 1.1.2; 1.1.6; 1.1.14; 1.1.16;
Add initial support for userspace block/char device drivers. This
is a very rough cut supporting only open/close/read/write for char
devices for the time being. It also takes some extra liberties in
error value processing wrt. to the request-response protocol, but
that will be fixed later. On the bright side, I haven't managed
to crash my test kernel in several hours with this anymore, so it
can be considered extra-stable ... All in all this is remarkably
similar to puffs from multiple angles (well, actually, big surprise
there) and these two will share more and more code in the future.

The hardest part, coming up with the name, was done by agc. I'm
not exactly sure what "pud" is supposed to stand for, but if my
British is anything close to par, I understand that "pud" over
there can stand for just about anything, so it's a safe bet.

avoid some uninitialised variable warnings.

Third argument of MODULE() is typically a string literal.
Moreover it (at least sometimes) didn't build otherwise.

Add support for building pud as module. Do it in a same way how putter is
done.

branches: 1.8.4; 1.8.6; 1.8.8;
Ansify function definitions w/o arguments. Generated with sed.

branches: 1.7.2;
Change major()/minor() to return 32-bit types again, called
devmajor_t/devminor_t, as proposed on tech-kern.
This avoids 64-bit arithmetics and 64-bit printf formats in parts
of the kernel where it is not really useful, and helps clarity.

branches: 1.6.4; 1.6.12; 1.6.14; 1.6.24; 1.6.32;
one more lock to destroy

* version the registration interface
* destroy all created locks

PUD_CONF_IOCTL is a goner. Noticed by dillo.

branches: 1.3.2;
Add support for block devices.

silence, might be used uninitialized warning!

Add initial support for userspace block/char device drivers. This
is a very rough cut supporting only open/close/read/write for char
devices for the time being. It also takes some extra liberties in
error value processing wrt. to the request-response protocol, but
that will be fixed later. On the bright side, I haven't managed
to crash my test kernel in several hours with this anymore, so it
can be considered extra-stable ... All in all this is remarkably
similar to puffs from multiple angles (well, actually, big surprise
there) and these two will share more and more code in the future.

The hardest part, coming up with the name, was done by agc. I'm
not exactly sure what "pud" is supposed to stand for, but if my
British is anything close to par, I understand that "pud" over
there can stand for just about anything, so it's a safe bet.

fix tripple/quadruple "r" letter typos in comments and log messages.

branches: 1.7.2; 1.7.8;
Replace DIOCGPART -> DIOCGPARTINFO which returns the data needed instead of
pointers.

branches: 1.6.22; 1.6.40;
Handle DIOCGPART in-kernel because a userspace server doesn't have
a chance in phobos of handling it. This makes it possible to do a
kernel mount of most file systems with the block device backed by
a pud userspace server.

- i'm too young to compile
- hey, no tty rough
- hurd me plenty
=> abstraction-violence
- nightmare!

fix pasto

branches: 1.4.4; 1.4.12; 1.4.14; 1.4.24; 1.4.34; 1.4.42;
Support bdev/cdev ioctl.

branches: 1.3.2;
Add support for block devices.

mmap should return -1 on error. Also, shuffle functions around to
make this more feng shui.

Add initial support for userspace block/char device drivers. This
is a very rough cut supporting only open/close/read/write for char
devices for the time being. It also takes some extra liberties in
error value processing wrt. to the request-response protocol, but
that will be fixed later. On the bright side, I haven't managed
to crash my test kernel in several hours with this anymore, so it
can be considered extra-stable ... All in all this is remarkably
similar to puffs from multiple angles (well, actually, big surprise
there) and these two will share more and more code in the future.

The hardest part, coming up with the name, was done by agc. I'm
not exactly sure what "pud" is supposed to stand for, but if my
British is anything close to par, I understand that "pud" over
there can stand for just about anything, so it's a safe bet.

branches: 1.4.4; 1.4.12; 1.4.14;
* version the registration interface
* destroy all created locks

Support bdev/cdev ioctl.

branches: 1.2.2;
Add support for block devices.

Add initial support for userspace block/char device drivers. This
is a very rough cut supporting only open/close/read/write for char
devices for the time being. It also takes some extra liberties in
error value processing wrt. to the request-response protocol, but
that will be fixed later. On the bright side, I haven't managed
to crash my test kernel in several hours with this anymore, so it
can be considered extra-stable ... All in all this is remarkably
similar to puffs from multiple angles (well, actually, big surprise
there) and these two will share more and more code in the future.

The hardest part, coming up with the name, was done by agc. I'm
not exactly sure what "pud" is supposed to stand for, but if my
British is anything close to par, I understand that "pud" over
there can stand for just about anything, so it's a safe bet.

branches: 1.1.2; 1.1.6; 1.1.14; 1.1.16;
Add initial support for userspace block/char device drivers. This
is a very rough cut supporting only open/close/read/write for char
devices for the time being. It also takes some extra liberties in
error value processing wrt. to the request-response protocol, but
that will be fixed later. On the bright side, I haven't managed
to crash my test kernel in several hours with this anymore, so it
can be considered extra-stable ... All in all this is remarkably
similar to puffs from multiple angles (well, actually, big surprise
there) and these two will share more and more code in the future.

The hardest part, coming up with the name, was done by agc. I'm
not exactly sure what "pud" is supposed to stand for, but if my
British is anything close to par, I understand that "pud" over
there can stand for just about anything, so it's a safe bet.