Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!mtxinu!sybase!binky!tim
From: tim@binky.sybase.com (Tim Wood)
Newsgroups: comp.lang.forth
Subject: Re: porting an MS-DOS Forth to a 386 Unix/Xenix
Keywords: MS-DOS, Forth, porting, source, help
Message-ID: <7266@sybase.sybase.com>
Date: 29 Nov 89 23:57:10 GMT
References: <1989Nov20.211822.1015@tree.uucp>
Sender: news@sybase.sybase.com
Reply-To: tim@binky.UUCP (Tim Wood)
Organization: Sybase, Inc.
Lines: 25

In article <1989Nov20.211822.1015@tree.uucp> stever@tree.uucp (Steve Rudek) writes:
>In a recent posting, sabbagh@csd27.nyu.edu (Hadil G. Sabbagh) said:
>>...in UNIX, it is not _possible_ to write Forth (in either C _or_
>>assembler !!!) because the "text space" (the segment of memory 
>>that holds the executable code image) is defined to be
>>_read-only_.  There may be a way around this if you achieved a
>>sufficiently high level of UNIX wizardry and have the right
>>priviledges :-).
>
>Is he correct?  That would be terrible.  
>{pacbell!sactoh0! OR ucdavis!csusac!}tree!stever

Wrong-O.  You can make a read/write executable image very easily
(in BSD UNIX at least).  Just pass the -N flag to the 'ld' (linker)
program when you build your executable.  This is the oldest form
of executable, back from the days when there wasn't any text sharing.
And it doesn't even require root privilege! :-)



-TW
Sybase, Inc. / 6475 Christie Ave. / Emeryville, CA / 94608	  415-596-3500
tim@sybase.com          {pacbell,pyramid,sun,{uunet,ucbvax}!mtxinu}!sybase!tim
		This message is solely my personal opinion.
		It is not a representation of Sybase, Inc.  OK.