From owner-freebsd-emulation Fri Oct 16 01:52:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00507 for freebsd-emulation-outgoing; Fri, 16 Oct 1998 01:52:15 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from bock.nettek-llc.com (d01a850c.dip.cdsnet.net [208.26.133.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00455; Fri, 16 Oct 1998 01:51:47 -0700 (PDT) (envelope-from stevel@mail.cdsnet.net) Received: from mail.cdsnet.net (localhost.nettek-llc.com [127.0.0.1]) by bock.nettek-llc.com (8.9.1/8.9.1) with ESMTP id BAA27412; Fri, 16 Oct 1998 01:49:28 -0700 (PDT) (envelope-from stevel@mail.cdsnet.net) Message-ID: <36270897.F7381BBA@mail.cdsnet.net> Date: Fri, 16 Oct 1998 01:49:27 -0700 From: Steve Logue Organization: http://www.nettek-llc.com/ X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith CC: sos@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: LD_PRELOAD & Linux emulation References: <199810160815.BAA01642@dingo.cdrom.com> Content-Type: multipart/alternative; boundary="------------28A153C52CF4A320B443BFCA" Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------28A153C52CF4A320B443BFCA Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mike Smith wrote: > > > We dont ??, strange, I've always thought of it as my baby :) > > Great. Maintain it, Dad. > > 8) > > Seriously, we're probably down 5-10 syscalls, and the supporting > libraries haven't been updated for ~12 months or so. Saying "I wrote > lots of it" is fine, but "I maintain it" is another story altogether. > As far as the linux_lib package/port is concerned, is there room for another person to help? My business runs on FreeBSD, and I have a critical need to be able to run many Linux programs now and in the future. Therefore the proper functioning of such is worth money to me, and I would be willing to maintain a current RedHat machine to steal libraries, and other config files from as well as negotiating with Linux software producing companies. I can also deal with NDA's if needed to improve linux_lib. Lastly, why can't we automate this by scripted extraction straight from a series of Red Hat packages (the horse's mouth) - let Red Hat manage for us what is the latest linux library/config files of the day? -STEVEl -- ------------------------------------------------------------ Steve Logue http://www.nettek-llc.com/ nettek LLC PC hardware/software sales (541) 582-4602 voice/fax Unix/Windows integration ------------------------------------------------------------ --------------28A153C52CF4A320B443BFCA Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Mike Smith wrote:
 
> We dont ??, strange, I've always thought of it as my baby :)

Great.  Maintain it, Dad.

8)

Seriously, we're probably down 5-10 syscalls, and the supporting
libraries haven't been updated for ~12 months or so.  Saying "I wrote
lots of it" is fine, but "I maintain it" is another story altogether.
 

As far as the linux_lib package/port is concerned, is there room for another person to help?
My business runs on FreeBSD, and I have a critical need to be able to run many Linux programs now and in the future.
Therefore the proper functioning of such is worth money to me, and I would be willing to maintain a current RedHat machine to steal libraries, and other config files from as well as negotiating with Linux software producing companies.  I can also deal with NDA's if needed to improve linux_lib.  Lastly, why can't we automate this by scripted extraction straight from a series of Red Hat packages (the horse's mouth) - let Red Hat manage for us what is the latest linux library/config files of the day?

-STEVEl
  

-- 
------------------------------------------------------------
Steve Logue                       http://www.nettek-llc.com/
nettek LLC                        PC hardware/software sales
(541) 582-4602 voice/fax          Unix/Windows integration
------------------------------------------------------------
  --------------28A153C52CF4A320B443BFCA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message