Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!pacbell.com!amdahl!netcomsv!netcom.com!pcbsd From: pcbsd@netcom.com (PCBSD Development Manager) Subject: Re: Porting NetBSD to OS/2 and Windows NT Message-ID: <pcbsdCGK5Jt.Dxy@netcom.com> Organization: NETCOM On-line Communication Services (408 241-9760 guest) X-Newsreader: TIN [version 1.1 PL8] References: <crt.753372692@tiamat.umd.umich.edu> Date: Tue, 16 Nov 1993 00:04:40 GMT Lines: 34 Rob Shady (crt@tiamat.umd.umich.edu) wrote: : sommerfeld@apollo.hp.com (Bill Sommerfeld) writes: : >In article <pcbsdCGE4oI.5zw@netcom.com> pcbsd@netcom.com (PCBSD Development Manager) writes: : >Why not just write a OS/2 or Windows NT emulator which runs under : >NetBSD or Mach? People are working on WINE (which is a WABI : >implementation for for NetBSD & Linux). One thing at a time :-) : > What that means is that some of the Section 3 and up code needs to be : > modified to be able to work with desktop filesystems transparently. : >"desktop filesystems"? I've got a UNIX file system on my desk top : >here and at work. It handles newlines correctly. : I missed that one.. What exactly *IS* a 'desktop filesystem'... I was refering to the CP/M, DOS derived filesystems. Sorry. : > One of the most frustrating differences on desktop is the \r\n used : > to delimit the end of line in text files (whereas it is just \n on : > UNIX). : Not to mention that if this is your 'most frustrating difference' so far, : you've got a *LONG* way to go.. ;) Believe it or not, we were able to solve all our other problems gracefuly. This is the only one that remains a problem. -- --------------------------------- ------------------------------ -- PCBSD Development Manager -- -- Service Commitment Support -- --------------------------------- ------------------------------