Andreas Jellinghaus a écrit :
Am Dienstag 01 November 2005 23:37 schrieb Aurelien Jarno:
Hi,
Hi!
The current version of openct fails to build on GNU/kFreeBSD. Please
find attached a small patch to fix that. It would be nice if you can
include it in your next upload.
thanks, applied to svn trunk, will be part of the next release.
Thanks.
btw: any chance you have a smart card reader or usb crypto
token? would be very interesting to have someone test
openct on freebsd. last time I sat down with bsd guys
to test and debug freebsd kernel crashed everytime we
unplugged a device, so we haven't tested since :(
Unfortunately I can't do any test as I don't have such a device. If I
found one, I'll test this package.
also maybe you know: does debian/freebsd or freebsd
in general have a usbd, i.e. some deamon that can monitor
all available usb devices, and call some script whenever a
new device is plugged in?
Yes, there is usbd, something similar to hotplug. We haven't packaged it
for Debian though
also how could such a daemon pass detailed information
which device is new to the script? on linux we have the
full patch to the device in /proc/bus/usb/ which is unique,
is there something like that on freebsd?
Yes, there is something like that, a bit different though. Each USB
device has its device node in /dev/ (FreeBSD is using a dynamic /dev, a
bit like devfs). The name of the device node depends on its function,
devices without kernel driver are simply called ugen0, ugen1, ...
usbd could handle that and could pass the name of this device to a
program it executes.
openct is using the linux hotplug system and it works great.
I'm sure the BSDs have something similar, but so far I never
found anyone who could fill in the details for our users.
I am sure usbd is suitable for doing the same as on Linux.
Bye,
Aurelien
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`- people.debian.org/~aurel32 | www.aurel32.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
