Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!sdd.hp.com!apollo.hp.com!netnews From: sommerfeld@apollo.hp.com (Bill Sommerfeld) Subject: Re: Porting NetBSD to OS/2 and Windows NT Sender: usenet@apollo.hp.com (Usenet News) Message-ID: <SOMMERFELD.93Nov12161654@snarfblatt.apollo.hp.com> In-Reply-To: pcbsd@netcom.com's message of Fri, 12 Nov 1993 18:00:16 GMT Date: Fri, 12 Nov 1993 21:16:53 GMT References: <crt.753111416@tiamat.umd.umich.edu> <pcbsdCGE4oI.5zw@netcom.com> Nntp-Posting-Host: snarfblatt.ch.apollo.hp.com Organization: HP Apollo Systems Division, Chelmsford, MA. Lines: 30 In article <pcbsdCGE4oI.5zw@netcom.com> pcbsd@netcom.com (PCBSD Development Manager) writes: It is possible to consider an operating system a platform, which is what I am doing. The PCBSD project is writing a xxxBSD kernel that would run as a subsystem on OS/2 and NT, and provide all of the Section 2 calls. 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). 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. 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). You can't do this and maintain POSIX compatibility: POSIX.1 says (in section 8.1, line 39..41) "Systems conforming to this part of ISO/IEC 9945 shall make no distinction between the "text streams" and the "binary streams" described in the C standard. - Bill