Re: NVIDIA FreeBSD kernel feature requests

Producing a driver for a GPU card, especially one that possibly converts from GL-foo to foo appropriate to program and feed an ASIC on a video card, is quite different matter entirely. I'm all for open source drivers, and would also encourage NVIDIA to continue to reconsider their closed source d

Re: NVIDIA FreeBSD kernel feature requests

On Mon, Jul 03, 2006 at 08:42:42AM +0530, Joseph Koshy wrote: > In the less benign one that "convenient" binary driver that > you loaded into the kernel would contain a silent security > vulnerability. Google for "Sony DRM rootkit". I think the difference here is that NVIDIA are a little more tru

Re: getc in BSD (was FLEX issues)

On 2006-07-03 20:06, Mike Meyer <[EMAIL PROTECTED]> wrote: > In <[EMAIL PROTECTED]>, James Bailie <[EMAIL PROTECTED]> typed: > > Randall Hyde wrote: > > > This kind of gives me the impression that "getc" is defined a bit > > > differently under FreeBSD than other environments? Any ideas? > > Yes

Re: getc in BSD (was FLEX issues)

In <[EMAIL PROTECTED]>, James Bailie <[EMAIL PROTECTED]> typed: > Randall Hyde wrote: > > This kind of gives me the impression that "getc" is defined a bit > > differently under FreeBSD than other environments? Any ideas? > Yes. It's defined as a macro. Linux says that getc "may be implemented

Re: getc in BSD (was FLEX issues)

Randall Hyde wrote: > This kind of gives me the impression that "getc" is defined a bit > differently under FreeBSD than other environments? Any ideas? Yes. It's defined as a macro. -- James Bailie <[EMAIL PROTECTED]> http://www.jamesbailie.com ___

Re: Stop further socket() or connect() calls.

On Mon, 2006-Jul-03 18:09:27 +0100, mal content wrote: >Was it my imagination or did I see a function in libc that >allowed a process to prevent further network access? The closest is shutdown(2) which can stop further access in one direction on an existing socket - not what you want. >I was look

getc in BSD (was FLEX issues)

Well, having a little bit of time to play around with the issues I'm having with Flex under GCC, I've determined that the problem occurs in the following code fragment: for ( n = 0; n < num_to_read && ( c = getc<

Stop further socket() or connect() calls.

Was it my imagination or did I see a function in libc that allowed a process to prevent further network access? I'm pretty sure that I read the manual page for it and now I can't find it. I was looking for a way to write a small wrapper program that disables network access and then exec()'s a giv

Re: NVIDIA FreeBSD kernel feature requests

On Mon, Jul 03, 2006 at 10:33:29AM +0100, Robert Watson wrote: > > On Sun, 2 Jul 2006, M. Warner Losh wrote: > > >In message: <[EMAIL PROTECTED]> > > "Kip Macy" <[EMAIL PROTECTED]> writes: > >: IIRC lack of per instance cdevs also limits Freebsd to one vmware > >instance. > > > >Can yo

Re: NVIDIA FreeBSD kernel feature requests

On Sun, Jul 02, 2006 at 10:02:17PM -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Christian Zander <[EMAIL PROTECTED]> writes: > : This summary makes an attempt to describe the kernel interfaces needed by > : the NVIDIA FreeBSD i386 graphics driver to achieve feature p

[patch] display jail id in /usr/bin/top

Hi, The attached patch provide top(1) the ability to display jail id. Usage: % top -j or in interactive mode, toggle with 'j'. Suggestions are needed. diff -ruN /usr/src/usr.bin/top/machine.c.orig usr.bin/top/machine.c --- /usr/src/usr.bin/top/machine.c Wed

Re: NVIDIA FreeBSD kernel feature requests

On Sun, 2 Jul 2006, Sam Smith wrote: On Sun, 2 Jul 2006, Michal Mertl wrote: And - again - it will probably take a couple of very skilled programmers' years' time to write good driver from scratch. It took someone far less than that http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pc

Re: NVIDIA FreeBSD kernel feature requests

On Sun, 2 Jul 2006, M. Warner Losh wrote: In message: <[EMAIL PROTECTED]> "Kip Macy" <[EMAIL PROTECTED]> writes: : IIRC lack of per instance cdevs also limits Freebsd to one vmware instance. Can you describe the proper semantics here? A cdev is a cdev, and when we do things like d