From: mmalater@nycap.rr.com   
      
   > have you noticed that beos itself is "kind of old?"  it hasn't been   
   > updated since 2000.  more recent versions of gcc have changed the abi,   
   > so it no longer produces object code that is binary-compatible with   
   > beos.   
      
   Sorry I forgot to turn my brain on. Anyway gcc 2.9x is faster than 3.x.   
      
   And also I am kind of lost in the BeOS distribution world. There seems   
   to be three main group:   
   - those directly deriving from the BeOS R5, release by Be,   
   - those made on top of NewOS   
   - those that use a linux kernel, and a thin layer to reproduce the BeOS   
   API on top of the linux kernel.   
      
   Thus the later two don't suffer this abi change. You don't use them   
   because they are not as mature as the real BeOS kernel, right ?   
      
   > if you have specific questions, somebody here might be able to help, but   
      
   I don't think it is so exotic. I just have a Intel Ethernet card 100   
   pro. But I don't understand how 'Network preference' works. It always   
   only propose two cards : ne2000 and 3com   
      
   After reading:   
   http://www.bebits.com/app/3790   
      
   my guess is that everything is /automagically/ configured. I just need   
   to figure out the right PCI id for my ethernet card, and modify the   
   script to modify the hardcoded value in the binary driver eepro100,   
   right ? Do you know, or anybody out there know how to retrieve this   
   magic number from the output of lspci (when running linux) ?   
      
      
   Thanks a lot Johnny,   
   Mathieu   
   BTW, there has been a realpath.c file in the OpenBeOS kernel :   
   http://cvs.sourceforge.net/viewcvs.py/open-beos/current/src/kern   
   l/Jamfile?r1=1.21&r2=1.22   
   which seems to desepear after r1.44...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)