Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!decwrl!netcomsv!netcom.com!pcbsd From: pcbsd@netcom.com (PCBSD Development Manager) Subject: Re: Whats up with the OS/2 port of NetBSD? Message-ID: <pcbsdCJ4nt7.MIH@netcom.com> Organization: NETCOM On-line Communication Services (408 241-9760 guest) X-Newsreader: TIN [version 1.2 PL1] References: <CIsAFt.Hq0@news2.cis.umn.edu> <2fs77e$oat@sparc10.entropic.com> <pcbsdCItqKB.ApB@netcom.com> <crt.757602914@tiamat.umd.umich.edu> Date: Tue, 4 Jan 1994 22:58:19 GMT Lines: 30 Rob Shady (crt@tiamat.umd.umich.edu) wrote: : pcbsd@netcom.com (PCBSD Development Manager) writes: : [Misc. Deleted] : >Our goal is... : >to be as closely compatible with NetBSD and BSD4.4 as possible given some : >OS/2 limitations. : Now this is somewhat more realistic than what you had stated before... I try to be as unrealistic as possible, but sometimes ... :-) Native operating systems will always place constraints on even the best of plans. For example, you will not be able to use a colon : in OS/2 file names since OS/2 file systems do not allow it (it is a drive separator only). On the other hand, you will be able to use symbolic links which OS/2 does not have. : >PCBSD is also evolving to include System 5 support. : That could be a big mistake.. Unless your leaving the BSD4.4 stuff in as : well (although some of it conflicts, which may make it difficult). System 5 support is going to be IN ADDITION to the BSD support. So far, we see no conflicts since a particular task will be running using either Sys5 or BSD system calls (i.e. different subsystems). -- --------------------------------- ------------------------------ -- PCBSD Development Manager -- -- Service Commitment Support -- --------------------------------- ------------------------------