Re: Search a symbol in the source tree

1999-10-13 Thread Chuck Robey
On Wed, 13 Oct 1999, W Gerald Hicks wrote: > > Er, global is part of the base system. :-) > > Hehe, I knew that. > > My point was that the entire package isn't built and the author's > going GPL anyway and since nobody recommended it ... That sure would > make a nice port ;-) That's simply no

Re: The meaning of LK_INTERLOCK

1999-10-13 Thread Bill Studenmund
On Wed, 13 Oct 1999, Zhihui Zhang wrote: > > The comments say that the flag LK_INTERLOCK means "unlock passed simple > lock after getting lk_interlock". Under what circumstances are we going to > need two simple locks (release the first one after getting the second > one)? I can not understand t

Re: Search a symbol in the source tree

1999-10-13 Thread W Gerald Hicks
> Er, global is part of the base system. :-) Hehe, I knew that. My point was that the entire package isn't built and the author's going GPL anyway and since nobody recommended it ... That sure would make a nice port ;-) For the original poster gtags/htags is an excellent tool for your purposes

Re: --enable-haifa

1999-10-13 Thread Ollivier Robert
According to W Gerald Hicks: > Just curious what effect using the --enable-haifa flag for building > gcc-2.95.1/x86 would have so I did a comparison using the Dhrystone > benchmark from /usr/ports/benchmarks/bytebench. I think the Haifa scheduler is only really effective on pure RISC processors l

Re: Search a symbol in the source tree

1999-10-13 Thread Peter Jeremy
On Tue, 12 Oct 1999 10:32:00 -0400 (EDT), Zhihui Zhang <[EMAIL PROTECTED]> wrote: >Can anyone suggest me a way of searching symbols in the entire /usr/src >tree? I use id-utils (/usr/ports/devel/id-utils). It builds a single database file and has a variety of tools (including e-lisp) to search

Re: Generating interrupts ?

1999-10-13 Thread Mike Smith
> > See sys/i386/bios.c for how to make BIOS calls out of the kernel. But > note that obtaining this information in the kernel is too late. See > sys/boot/i386/libi386/biosdisk.c for how to call the BIOS in the > loader, where you have a chance to obtain this information and use it > to dec

Re: Generating interrupts ?

1999-10-13 Thread Mike Smith
> Your close. > I actually made a bootable CD which installs a modified version of FreeBSD, with > our product running on on top of it. The CD automatically boots up, installs > everything, configures everything and then it asks you for a password. At this > stage it gathered information of the pa

Re: Generating interrupts ?

1999-10-13 Thread Mike Smith
> > I want to read the the type of motherboard the system is running on, as well > as the BIOS version string. > It's easy to read the harware the bios detects ( it's in the 64 bytes you > can read from port 71 ) but i need the the other info ass well. Read the Intel paper on UUIDs and GUIDs and

The meaning of LK_INTERLOCK

1999-10-13 Thread Zhihui Zhang
The comments say that the flag LK_INTERLOCK means "unlock passed simple lock after getting lk_interlock". Under what circumstances are we going to need two simple locks (release the first one after getting the second one)? I can not understand this easily from the source code. Any help is appre

Re: --enable-haifa

1999-10-13 Thread Kris Kennaway
On Wed, 13 Oct 1999, W Gerald Hicks wrote: > Just curious what effect using the --enable-haifa flag for building > gcc-2.95.1/x86 would have so I did a comparison using the Dhrystone > benchmark from /usr/ports/benchmarks/bytebench. This seems marginal, in other words. How did the results vary w

Re: paper on fine-grained OS timers

1999-10-13 Thread John Polstra
In article <[EMAIL PROTECTED]>, Mohit Aron <[EMAIL PROTECTED]> wrote: > I'd like to tell the BSD community about my paper entitled > "Soft timers: efficient microsecond software timer support for network > processing" that's going to appear in SOSP 1999. The abstract for the paper > is at

Re: Search a symbol in the source tree

1999-10-13 Thread Bill Fumerola
On Wed, 13 Oct 1999, John Polstra wrote: > > That sure would make a nice port, especially since we could > > easily recommend gozilla as a nice way to browse and search > > the source tree. > > Er, global is part of the base system. :-) And for those who like to point and laugh: c [199

Re: Search a symbol in the source tree

1999-10-13 Thread John Polstra
In article <[EMAIL PROTECTED]>, W Gerald Hicks <[EMAIL PROTECTED]> wrote: > I find it ironic that nobody has suggested global yet; > > That sure would make a nice port, especially since we could > easily recommend gozilla as a nice way to browse and search > the source tree. Er, global is part

Re: Unquoted mail (was: aio_read kills machine)

1999-10-13 Thread Stephen McKay
On Tuesday, 12th October 1999, Greg Lehey wrote: >On Monday, 11 October 1999 at 20:39:11 -0500, Matthew D. Fuller wrote: >> On Tue, Oct 12, 1999 at 11:04:50AM +0930, a little birdie told me >> that Greg Lehey remarked >>> >>> What mailer are you using? It didn't quote the "From " at the >>> begi

Re: alpha scheduling needs some tuning

1999-10-13 Thread Andrew Gallatin
Jason Thorpe writes: > On Tue, 12 Oct 1999 23:37:53 -0400 (EDT) > Andrew Gallatin <[EMAIL PROTECTED]> wrote: > > > Has anybody noticed that scheduling appears to be broken on the alpha? > > > > On both i386 & alpha, try: > > > > echo "main(){for(;;);}" > foo.c > > cc foo.c >

Re: Generating interrupts ?

1999-10-13 Thread Johan Kruger
Your close. I actually made a bootable CD which installs a modified version of FreeBSD, with our product running on on top of it. The CD automatically boots up, installs everything, configures everything and then it asks you for a password. At this stage it gathered information of the particular s

Re: Generating interrupts ?

1999-10-13 Thread Mark Newton
Johan Kruger wrote: > H, OK , well, i want to use the specific strings as part of the > info with which i am going to encrypt the kernel. Don't ask why, i am > not at liberty to say. Great. We get to deal with someone who wants assistance but is too concerned with intrigue to fully expl

Re: Generating interrupts ?

1999-10-13 Thread Johan Kruger
H, OK , well, i want to use the specific strings as part of the info with which i am going to encrypt the kernel. Don't ask why, i am not at liberty to say. Don't worry , it'l work, i just need the info from the motherboard and bios rev begin:vcard n:Kruger;Johan tel;cell:+27 83 3015923 tel

Re: Generating interrupts ?

1999-10-13 Thread Mark Newton
Johan Kruger wrote: > I want to read the the type of motherboard the system is running on, as well > as the BIOS version string. With all due respect, part of the whole point of UNIX is that you don't need to care about that. Why not tell us what you're actually trying to achieve (instead of

Re: Generating interrupts ?

1999-10-13 Thread Johan Kruger
I want to read the the type of motherboard the system is running on, as well as the BIOS version string. It's easy to read the harware the bios detects ( it's in the 64 bytes you can read from port 71 ) but i need the the other info ass well. begin:vcard n:Kruger;Johan tel;cell:+27 83 3015923 t

Re: Generating interrupts ?

1999-10-13 Thread Narvi
On Wed, 13 Oct 1999, Johan Kruger wrote: > In DOS it's possible to load the AX register with DA8C and generate a > int 15, which will return the BIOS version string and the chipset > identification int CL register. How do i do it in FreeBSD, and how do i > generate a interrupt for that manner ?

Generating interrupts ?

1999-10-13 Thread Johan Kruger
In DOS it's possible to load the AX register with DA8C and generate a int 15, which will return the BIOS version string and the chipset identification int CL register. How do i do it in FreeBSD, and how do i generate a interrupt for that manner ? Greeting fellow FreeBSD users, by the way, 4.0-CUR

Re: Symbols and klds

1999-10-13 Thread Doug Rabson
On Tue, 12 Oct 1999, Warner Losh wrote: > > How does one tell ddb about dynamic modules? I've had a couple of > crashes in my code where I've needed symbols from things dynamically > loaded... Does gdb grok them any better? > I thought ddb was supposed to know about them already but perhaps