Re: Accessing (the i4b) device driver
Andrew Gordon wrote: > On Fri, 30 Apr 2004, Martin Moeller wrote: > > > > I'm totally new to FreeBSD programming, so please forgive my troll-like > > question! I'd like to write a nifty little program showing if somebody is > > calling me via an ISDN line. In the far future, the program should show the > > caller's telephone number. For (guessed) 5 years it's shown me Name of all(*) callers, not just number ! I use xterm, tail -f, grep, & the log file. I added the number to name code years back, 'cos I can't remember numbers. Try man isdnd (*) callers from analogue lines show as "not available" BTW The correct list for deep isdn issues is not hackers@ but isdn@ (but this easy question might be happy on questions@ :-) - Julian Stacey. Unix C & Net Services Consultant - Munich. http://berklix.com Mail in Ascii text/plain: Html + Mime dumped as Spam. Schnupftabak probieren: Ihr Rauchen = mein allergischer Kopfschmerz ! VCF Europa 5.0 am 01./02. Mai 2004 in Muenchen http://www.vcfe.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB device driver question: timeout() and usbd_do_request()
Hello, I'm writing a USB driver for a device that does not have any interrupt. It only has Bulk-in and Bulk-out. A periodic polling status from default pipe is required to have a smooth data transfer. I used timeout() routine to call usbd_do_request() for polling. I thought maybe timeout() is called under interrupt context, since usbd_do_request() access system I/O, it crashes. However, by adding this timeout() in ucomstart(), it didn't crash until the third call to timeout(). Removing usbd_do_request() allows the timeout() to work without any problem. From the USB analyzer, I could see that even if the system crashed, a request was sent to the USB device correctly. There are two crashdump messages printed out to the screen, I could only catch the second one. The first one scrolled off the screen too fast. By counting the byte and the instruction pointer, the routine crashed in acquire_lock(). I 'greped' the kernel source code, didn't see this routine. I know I'm missing some important FreeBSD concept since I'm new to it, by reading related document did not reveal anything that might help me. If usbd_do_request() should never be used in timeout() as a callback routine, what other options do I have, to implement a status-polling scheme? Thank you very much in advance. Rita ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Accessing (the i4b) device driver
* Julian H. Stacey <[EMAIL PROTECTED]> [02052004 17:14] > BTW The correct list for deep isdn issues is not hackers@ but isdn@ > (but this easy question might be happy on questions@ :-) Hi everybody, thank you very much for your answers concerning showing an ISDN caller's ID. I'm using Bjoern Zeeb's approach at the moment and it works good, but I'm still obsessed by the idea of a nifty little Gnome panel applet showing me the phone number of a caller. Julian, You're absolutely correct: Questions concerning the configuration and use of ISDN belong to @questions or @isdn. BUT: The thing I actually asked was how to communicate with a device driver (in this case: i4b's) to get the job done with a C program. Luckily (thanks to Gerald Heinig) I've been directed to the source code of isdnd to see how things are done there. But I guess understanding such a complex program as this takes a while. *sigh* :( It seems as if my little gnome program has to wait a little... So, thanks again for all your answers and sorry! if this was the wrong list to post to. Regards, Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Enumerating devices and hardware conf from userland
Hi all, Sorry first if my question seems stupid : I'm new in the FreeBSD Kernel design and so don't know all interfaces of the kernel in user land. I'm developping a tool running in userland (root) (a command line tools) for enumerating all devices present on the machine : This tool must scan all hardware buses : pci, but usb, firewire, ide, etc and retreive devices states : configure, not configured, handle by a driver, not handle by a driver, witch modules is the driver. And I want to have all devices present inside a machine. In some recent Kernel, there is a way from userland, to take a handle from the root hardware tree, enumeratiing first buses, and under buses, witch device are connect to those buses. This is is what I am looking for. How to do this under FreeBSD ? THX in advance for your help, advice, comment. Thierry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Enumerating devices and hardware conf from userland
"Thierry DELHAISE" <[EMAIL PROTECTED]> wrote: > I'm developping a tool running in userland (root) (a command line > tools) for enumerating all devices present on the machine : take a look at http://www.magnicomp.com/sysinfo/ first :) Cyrille Lefevre. -- home: mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Squid, SquidGuard, FreeBSD
Looked at squidguard and dansguardian ...
looked at what the aware schools are using ...
went with dansguardian ... because it does the 'lookinside' of the
content returned as well as the site block list mode.
I also use a 'trick' that was mentioned in the Jan 2004 issue of
Sysadmin mag as below. It's listed, not on detailed their website, so
you do need the dead tree copy.
http://www.samag.com/articles/2004/0401/
! <
you MUST read the article prior to implementation <
! <
This only works if you are running a local DNS server
---8<--- cut from named.conf
//
// internet web-based ad sites
// this now defines _MY_ name-server as the master reference to
// locate them ... as the dummy-block file just points to localhost
// so things just vanish or appear as 'broken links' (so sad ;-( )
// as we dont have the sites here.
//
// SysAdmin mag Jan 2004
//
zone "adimages.go.com" { type master; file "dummy-block"; };
---8<--- end cut - theres more
The dummy-block file looks like this (name changed to protect the
innocent! Insert your own appropriate host names)
# more /etc/namedb/dummy-block
$TTL 24h
@ IN SOA host.example.net. root.host.example.net. (
200403141650
86400
300
604800
3600 )
@ IN NS dns.example.net.
@ IN A 127.0.0.1
* IN A 127.0.0.1
What a pity - no ad sites ;-)
As I said above - RTFM in the sysadmin mag article before using this on
your system as YMMV.
Murray T
On Sat, 2004-05-01 at 20:40, Thomas-Martin Seck wrote:
> * Ed Stover <[EMAIL PROTECTED]> [gmane.os.freebsd.devel.hackers]:
>
> > Has any one successfully done squid with squidGuard on a FreeBSD later then
> > 4.5 ? I have made it work on 4.5 but nothing later because of the berkly db
> > changes after 4.5, if you have made contentent filtering work on
> > FreeBSD-current can I get some tips? I like 4.5 but 4.9 has better hardware
> > coverage.
>
> squid and squidGuard work flawlessly on -STABLE if you don't mind that
> squidGuard (nowadays?) needs db3 from ports.
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
> This Email has been scanned for Viruses by MailMarshal.
>
This Email has been scanned for Viruses by MailMarshal.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
