Re: PCIOCGETCONF/PCIOCREAD requires write permission?

2000-12-10 Thread Daniel C. Sobral
David O'Brien wrote: On Fri, Dec 08, 2000 at 12:07:49AM -0700, Chad R. Larson wrote: I thought the space staked out by the *BSD gang was approximately this: NetBSD - the least amount of platform-specific code possible; run on most anything OpenBSD - pro-active security,

Re: PCIOCGETCONF/PCIOCREAD requires write permission?

2000-12-10 Thread Warner Losh
In message [EMAIL PROTECTED] "Daniel C. Sobral" writes: : ported to every hardware platform under sun, and we do not go out of our : way to provide security. Thus, NetBSD and OpenBSD have the edge on us on What? I don't see how you can say that about security... Warner To Unsubscribe: send

Re: PCIOCGETCONF/PCIOCREAD requires write permission?

2000-12-10 Thread Daniel C. Sobral
Warner Losh wrote: In message [EMAIL PROTECTED] "Daniel C. Sobral" writes: : ported to every hardware platform under sun, and we do not go out of our : way to provide security. Thus, NetBSD and OpenBSD have the edge on us on What? I don't see how you can say that about security... We

Patching live kernels

2000-12-10 Thread Alfred Perlstein
Ok, sometimes we find a bug in a particular release where what's needed is a function replaced with fixed code. I'm wondering if it's possible to: 1) look at the kernel symbol table for a particular function in a particular object file (static functions would be even better?) 2) replace the

Re: Patching live kernels

2000-12-10 Thread Jake Burkholder
Ok, sometimes we find a bug in a particular release where what's needed is a function replaced with fixed code. I'm wondering if it's possible to: 1) look at the kernel symbol table for a particular function in a particular object file (static functions would be even better?) 2)

Re: Patching live kernels

2000-12-10 Thread Andrew R. Reiter
afaik, Yes. There are two articles that I know of that deal with the specifics of modifying binaries to inject ones own code. The first is one that deals mostly with libbfd (binary file descriptor) and linux. iirc, libbfd worked a great deal better under linux than under FreeBSD. I recall

subscribe

2000-12-10 Thread Sean Peck
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

Configuring Gateway/NAT on Freebsd

2000-12-10 Thread Sean Peck
I am trying to configure a FreeBSD 3.3 box to act as a gateway/NAT translater for my network. I have added the following to the my rc.conf ifconfig_tun0="inet 172.168.0.1 netmask 255.255.255.0" gateway_enabled="YES" natd_enabled="YES" natd_ingerface="tun0" and tun0 to my network_interfaces

Re: PCIOCGETCONF/PCIOCREAD requires write permission?

2000-12-10 Thread Wes Peters
"Daniel C. Sobral" wrote: David O'Brien wrote: On Fri, Dec 08, 2000 at 12:07:49AM -0700, Chad R. Larson wrote: I thought the space staked out by the *BSD gang was approximately this: NetBSD - the least amount of platform-specific code possible; run on most anything

Re: PCIOCGETCONF/PCIOCREAD requires write permission?

2000-12-10 Thread Wes Peters
"Daniel C. Sobral" wrote: Warner Losh wrote: In message [EMAIL PROTECTED] "Daniel C. Sobral" writes: : ported to every hardware platform under sun, and we do not go out of our : way to provide security. Thus, NetBSD and OpenBSD have the edge on us on What? I don't see how you can

kern/23409, atapi_queue_cmd error codes?

2000-12-10 Thread Eyal Soha
I submitted and started debugging kern/23409: CD-RW driver fails unless CD in drive at boot up. I seem to be getting error code 0x5 and 0x10 from acd_mode_sense() when I'm booting up. What do those error codes mean? Do they correspond to the error register bits listed in atapi-all.h? #define