Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread David O'Brien
On Mon, Dec 18, 2000 at 02:58:16AM +1000, Stephen McKay wrote: The other day, on a whim, I decided to try running an old binary of SimCity (the same one found in the 'commerce' directory on many FBSD cds), and it failed in a odd way... Does anyone have any old a.out binaries other than

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Donald J . Maddox
Looks like you got a lot farther than I did with it... Are you sure you don't have an old aout ld.so on that machine? Here's what I get: dmaddox SimCity Starting SimCity ... SimCity Classic - UNIX / Tcl Tk Toolkit version 3.6b - Mattes /usr/libexec/ld.so: Undefined symbol "___error" called

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread David O'Brien
On Mon, Dec 18, 2000 at 02:58:16AM +1000, Stephen McKay wrote: This has been broken for new users for some time. :-( Those of us upgrading from source have been immune to this problem, because we retain the old a.out ld.so binary. /usr/libexec/ld.so: Undefined symbol "___error" called from

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Donald J . Maddox
Actually, the aout libs I am using when I get the ___error undefined are the ones from the XFree86-3.3.6 distribution, compiled for FreeBSD 3.x. Originally I was using the aout X libs I built myself when building the XFree86-3.3.6 port. Using those, I still got an undefined symbol, but it

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread David O'Brien
On Wed, Dec 20, 2000 at 03:57:07AM -0500, Donald J . Maddox wrote: Looks like you got a lot farther than I did with it... Are you sure you don't have an old aout ld.so on that machine? Nope. This is a box that was a virgin install of 5-CURRENT a month ago. I had to install the compat20 and

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Jeremy Lea
Hi, On Wed, Dec 20, 2000 at 01:52:23AM -0800, David O'Brien wrote: Nope. This is a box that was a virgin install of 5-CURRENT a month ago. I had to install the compat20 and compat21 dists, along with doing a ``pkg_add -r XFree86-aoutlibs''. The Tk is 8.0.5. The XFree86-aoutlibs are

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Donald J . Maddox
On Wed, Dec 20, 2000 at 01:52:23AM -0800, David O'Brien wrote: On Wed, Dec 20, 2000 at 03:57:07AM -0500, Donald J . Maddox wrote: Looks like you got a lot farther than I did with it... Are you sure you don't have an old aout ld.so on that machine? Nope. This is a box that was a virgin

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread David O'Brien
On Wed, Dec 20, 2000 at 05:09:45AM -0500, Donald J . Maddox wrote: res ldd sim sim: -lXext.6 = /usr/X11R6/lib/aout/libXext.so.6.3 (0x200c5000) -lX11.6 = /usr/X11R6/lib/aout/libX11.so.6.1 (0x200cf000) -lc.2 = /usr/lib/compat/aout/libc.so.2.2 (0x20166000) -lm.2 =

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Donald J . Maddox
On Wed, Dec 20, 2000 at 02:24:26AM -0800, David O'Brien wrote: On Wed, Dec 20, 2000 at 05:09:45AM -0500, Donald J . Maddox wrote: res ldd sim sim: -lXext.6 = /usr/X11R6/lib/aout/libXext.so.6.3 (0x200c5000) -lX11.6 = /usr/X11R6/lib/aout/libX11.so.6.1 (0x200cf000) -lc.2 =

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Donald J . Maddox
Interesting. After I installed the XFree86-aoutlibs port, SimCity works fine for me (on an 8-bit display)... It didn't work with the X libs built by the port when aout libs are requested, and it didn't work with the X libs from 3.3.6, but it works with these. Looks good. Can you install the

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Stephen McKay
On Wednesday, 20th December 2000, "David O'Brien" wrote: On Mon, Dec 18, 2000 at 02:58:16AM +1000, Stephen McKay wrote: This has been broken for new users for some time. :-( Those of us upgrading from source have been immune to this problem, because we retain the old a.out ld.so binary.

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Stephen McKay
On Wednesday, 20th December 2000, "Donald J . Maddox" wrote: Looks good. Can you install the XFree896-aoutlib port? You may have seen were someone posted the a.out libs from 3.3.6 are known to not be the the best to use for compatibility use. Interesting. After I installed the

Why 'lnc.ko' instead of 'if_lnc.ko' ?

2000-12-20 Thread Makoto MATSUSHITA
Recently, we have a module of 'lnc' ethernet. Maybe it's the last ethernet driver converted to newbus framework IIRC. Very thank you. However, this kernel module is named as 'lnc.ko'. Other ethernet driver modules are named as 'if_XXX.ko'; why lnc doesn't obey this name convension? Typo, or a

Re: Why 'lnc.ko' instead of 'if_lnc.ko' ?

2000-12-20 Thread Warner Losh
In message [EMAIL PROTECTED] Makoto MATSUSHITA-san writes: : However, this kernel module is named as 'lnc.ko'. Other ethernet : driver modules are named as 'if_XXX.ko'; why lnc doesn't obey this : name convension? Typo, or a new name scheme is used instead? Typo, I think. The module needs to be

Re: Network performance-problem

2000-12-20 Thread Jesper Skriver
On Tue, Dec 19, 2000 at 03:28:06PM +1030, Matthew Thyer wrote: Michael Class wrote: Hello, i am seeing a problem with 5.0-current (from 14.12.00) and a 3COM 3CCFE575CT Lancard (pc-cardbus) using the xl-driver. [snip] Why behaves my FreeBSD-machines worse then the other boxes?

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread David O'Brien
On Wed, Dec 20, 2000 at 11:15:55PM +1000, Stephen McKay wrote: Correcting slightly for your slightly off assumption: The X11 libs were probably built on a 3.x box. Their problem is that being newer than libc.so.2.2 (or was it libc.so.3.0) they use ___error but libc does not supply it. My

Re: Why 'lnc.ko' instead of 'if_lnc.ko' ?

2000-12-20 Thread Makoto MATSUSHITA
imp Typo, I think. The module needs to be named if_XXX.ko for the imp automatic kldload in ifconfig to work. OK, attached below is a (trivial) patch to fix this. -- - Makoto `MAR' MATSUSHITA Index: Makefile === RCS file:

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Donald J . Maddox
On Wed, Dec 20, 2000 at 10:14:09AM -0800, David O'Brien wrote: On Wed, Dec 20, 2000 at 11:15:55PM +1000, Stephen McKay wrote: Correcting slightly for your slightly off assumption: The X11 libs were probably built on a 3.x box. Their problem is that being newer than libc.so.2.2 (or was it

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread David O'Brien
On Wed, Dec 20, 2000 at 05:28:45AM -0500, Donald J . Maddox wrote: Heh :) You don't have to dink around with your config... Just do 'startx -- -bpp 8'. You assume I'm using an XFree86 server ;-) -- I am not. How can you be using the same X libs as me, and not be using XFree86?

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Donald J . Maddox
On Wed, Dec 20, 2000 at 10:43:39AM -0800, David O'Brien wrote: On Wed, Dec 20, 2000 at 05:28:45AM -0500, Donald J . Maddox wrote: How can you be using the same X libs as me, and not be using XFree86? XFree86 has many components to it -- binaries (such as Xterm), libs (such as

Re: Why 'lnc.ko' instead of 'if_lnc.ko' ?

2000-12-20 Thread Warner Losh
In message [EMAIL PROTECTED] Makoto MATSUSHITA writes: : imp Typo, I think. The module needs to be named if_XXX.ko for the : imp automatic kldload in ifconfig to work. : : OK, attached below is a (trivial) patch to fix this. This is a good start at a fix. However, all the attachments for the

I LOVE YOU AND I DON'T WANT YOU TO DIE!!.

2000-12-20 Thread achambergal
Title: We've already paid out over a cool MILLION DOLLARS to WINNERS just like YOU. Enter the Finest, Highest Paying Casino Online $25,000 WINNERS are cashing in at our casino DAILY. Grab YOUR share of this wealth pool and open an account now. We'll bring the finest, most secure,

open in kernelspace

2000-12-20 Thread Tomasz Paszkowski
How to open read file from kernel space. I have seen VOP_[READ,OPEN] but i think there's something easiest ? -- _ __ __ / \ | | / / / \ / \ -- Tomasz Paszkowski --- NS88-6BONE | |\ \| | \ \ |/ \||/ \| === BSD is for people who love Unix

Re: open in kernelspace

2000-12-20 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Tomasz Paszkowski writes: How to open read file from kernel space. I have seen VOP_[READ,OPEN] but i think there's something easiest ? VOP_* is the way to go. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC

Re: open in kernelspace

2000-12-20 Thread Tomasz Paszkowski
On Wed, Dec 20, 2000 at 10:52:05PM +0100, Poul-Henning Kamp wrote: How to open read file from kernel space. I have seen VOP_[READ,OPEN] but i think there's something easiest ? VOP_* is the way to go. :(( So I'll have a long night -- _ __ __ / \ | | / / / \ / \

Re: open in kernelspace

2000-12-20 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Tomasz Paszkowski writes: On Wed, Dec 20, 2000 at 10:52:05PM +0100, Poul-Henning Kamp wrote: How to open read file from kernel space. I have seen VOP_[READ,OPEN] but i think there's something easiest ? VOP_* is the way to go. :(( So I'll have a long night

Re: open in kernelspace

2000-12-20 Thread Tomasz Paszkowski
On Wed, Dec 20, 2000 at 11:10:53PM +0100, Poul-Henning Kamp wrote: Sorry, yes... ktrace, various accounting and of course open(2) will be the best places to start. In all likely hood you're trying to do something the wrong way though... I'm trying to open file located on /, from kernel

Re: Why 'lnc.ko' instead of 'if_lnc.ko' ?

2000-12-20 Thread Makoto MATSUSHITA
imp This is a good start at a fix. However, all the attachments for the imp lnc device also need to be called if_lnc. And they need to share the imp same devclass_t so that unit numbers don't go wonky on you (eg, if you imp have a isa and a pci lnc card in the same system, you might get two

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Stephen McKay
On Wednesday, 20th December 2000, "Donald J . Maddox" wrote: On Wed, Dec 20, 2000 at 10:14:09AM -0800, David O'Brien wrote: On Wed, Dec 20, 2000 at 11:15:55PM +1000, Stephen McKay wrote: Correcting slightly for your slightly off assumption: The X11 libs were probably built on a 3.x box.

Re: Why 'lnc.ko' instead of 'if_lnc.ko' ?

2000-12-20 Thread Warner Losh
In message [EMAIL PROTECTED] Makoto MATSUSHITA writes: : Hmm, fixing these are beyond my skill... I'll go ahead and fix it, or make sure it does. : BTW, are there anybody working on 'pcn' (yet another lance driver) to : work with VMware ? Current 5-current installation floppy makes VMware :

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Kris Kennaway
On Wed, Dec 20, 2000 at 02:05:20AM -0800, Jeremy Lea wrote: Hi, On Wed, Dec 20, 2000 at 01:52:23AM -0800, David O'Brien wrote: Nope. This is a box that was a virgin install of 5-CURRENT a month ago. I had to install the compat20 and compat21 dists, along with doing a ``pkg_add -r

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread Jeremy Lea
Hi, On Wed, Dec 20, 2000 at 07:13:05PM -0800, Kris Kennaway wrote: Argh. I'm going to have to mark that port FORBIDDEN, then, because old versions of the X libraries have remote vulnerabilities. Hmmm... Are there patches available to just fix the security problems? We can't move much beyond

Re: Is compatibility for old aout binaries broken?

2000-12-20 Thread John Hay
On Wed, Dec 20, 2000 at 07:13:05PM -0800, Kris Kennaway wrote: Argh. I'm going to have to mark that port FORBIDDEN, then, because old versions of the X libraries have remote vulnerabilities. Hmmm... Are there patches available to just fix the security problems? We can't move much