fusd-kor_1.10+11-2_amd64.changes is NEW
(new) fusd-kor-source_1.10+11-2_all.deb extra sound
Source for the fusd kernel module
FUSD is a Linux framework for proxying device file callbacks
into user-space, allowing device files to be implemented by
daemons instead of kernel code. Despite being implemented
in user-space, FUSD devices can look and act just like any
other file under /dev which is implemented by kernel callbacks.
.
This package contains a fork from Kor Nielsen, that makes fusd
work on kernel 2.6 with udev
(new) fusd-kor_1.10+11-2.diff.gz extra sound
(new) fusd-kor_1.10+11-2.dsc extra sound
(new) libfusd-dev_1.10+11-2_amd64.deb extra devel
Library for user space proxying device file callbacks
FUSD is a Linux framework for proxying device file callbacks
into user-space, allowing device files to be implemented by
daemons instead of kernel code. Despite being implemented
in user-space, FUSD devices can look and act just like any
other file under /dev which is implemented by kernel callbacks.
.
This package includes the development tools.
(new) libfusd1_1.10+11-2_amd64.deb extra libs
Library for user space proxying device file callbacks
FUSD is a Linux framework for proxying device file callbacks
into user-space, allowing device files to be implemented by
daemons instead of kernel code. Despite being implemented
in user-space, FUSD devices can look and act just like any
other file under /dev which is implemented by kernel callbacks.
.
This package includes the shared library object.
Changes: fusd-kor (1.10+11-2) unstable; urgency=low
.
* Included the user-space library in the libfusd1 and libfusd-dev
packages
Override entries for your package:
Announcing to debian-devel-changes@lists.debian.org
Your package contains new components which requires manual editing of
the override file. It is ok otherwise, so please be patient. New
packages are usually added to the override file about once a week.
You may have gotten the distribution wrong. You'll get warnings above
if files already exist in other distributions.
Reply to: