From: lawf@base.bellcore.com (Lawrence Fan) Subject: Re: 386bsd, linux: which runs more out of the box? Date: Tue, 30 Mar 1993 19:48:16 GMT
In article <1993Mar23.052609.11978@serval.net.wsu.edu>, hlu@eecs.wsu.edu (HJ Lu) writes:
|>
|> We have tried very hard to make porting to Linux easy. The Linux C library
|> is ANSI/POSIX compliant. Unless the software is developed for 386BSD or
|> something like that, porting to Linux should be easier. Also the floating
|> point part of Linux C library should be less buggy. But there are a few
|> exceptions:
|>
|> 1. signal in Linux is POSIX. You can do everything with POSIX except for
|> sigvector. Sun also supports POSIX signal.
|> 2. tty in Linux is POSIX. Sun also supports POSIX tty.
|> 3. time functions are POSIX, plus a few BSD and SYSV extensions.
|> 4. setjmp/longjmp functions are POSIX. But you can use -D__FAVOR_BSD
|> to make it BSD or use sigsigjmp/siglongjmp.
|>
|> From my experiences, 95% of codes from public sites should be compiled
|> right out of box, at most with a few warning if those codes are not
|> ANSI/POSIX ready. You can try to compile one of your favorite packages.
|>
Talking about porting to Linux. I have some questions:
1) Do we have SIGBUS?
2) I see there are include files under /usr/include that has the
same file names as /usr/src/linux/include/linux. As we update
the linux kernel version, the files under /usr/src/linux/include/linux
gets updated but not the ones in /usr/include. Why is that?
==========================================================================
Lawrence Fan (908) 699-8051
Bellcore RRC-1R217 444 Hoes Lane, Piscataway, NJ 08854
lawf@base.bellcore.com