*BSD News Article 23975


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!uwm.edu!caen!destroyer!news.itd.umich.edu!tiamat.umd.umich.edu!crt
From: crt@tiamat.umd.umich.edu (Rob Shady)
Newsgroups: comp.os.386bsd.development
Subject: Re: Porting NetBSD to OS/2 and Windows NT
Date: 15 Nov 1993 09:13:40 -0500
Organization: Univerisity of Michigan - Dearborn
Lines: 39
Message-ID: <crt.753372692@tiamat.umd.umich.edu>
References: <crt.753111416@tiamat.umd.umich.edu> <pcbsdCGE4oI.5zw@netcom.com> <SOMMERFELD.93Nov12161654@snarfblatt.apollo.hp.com>
NNTP-Posting-Host: cw-u01.umd.umich.edu

sommerfeld@apollo.hp.com (Bill Sommerfeld) writes:

>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).

Now, see... *THIS* makes sense to me.. I could live with that, and I think
it would be ALOT more feasible.

>   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'...

>   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.

Not to mention that if this is your 'most frustrating difference' so far,
you've got a *LONG* way to go.. ;)