================================================ Wed Sep  8 09:30:32 GMT 1993 =

This is the file "NBReadMe.txt". It contains a short summary of which
users should know when using "bash" under OS-9/68k.

The current bash port is "bash-1.12.10".

OSK-bash is a very poor port; it's a real quick and dirty hack. This
is the reason why there is no source comming along with the executable.
Moreover the source would be of no use for you since it does only compile
with my own OSK-port of `gcc' (supported by my own version of `glibc').
I think there is no easy way to compile and link it by uware's cc or
SP's gcc-port.

There was no intention at all to make OSK-bash available to people outside of
my home computer's world! But if you think you can use it, feel free to
use it ...

I would appreciate if you could send bug reports and/or suggestions to me.
Here is my internet address:

		"norbert@veilchen.informatik.rwth-aachen.de"

If you are interested in other OSK-ported GNUware, let me know.
==============================================================================

Things you should know about the OS-9 port of bash:

(The following list is neither sorted in any way nor is it a complete
 reference to the differences between OSK-bash and UN*X-bash. I simply
 wrote it down as it came into my brain ...!)

1) Under certain circumstances bash is very slow.

   The fork() mechanism of OS-9 is completely different from
   that implemented in UN*X. Due to the simple memory management
   mechanism used by OSK, there is no way to clone a process. For that,
   everytime UN*X-bash fork()s a subshell (without exec()ing anything other)
   OSK-bash tries to simulate the cloning as best as it can.
   This is a very expensive and time consuming job. Please be patient.
   For the moment I see no other way to handle it. ... perhaps someday
   someone will implement full MMU support into OSK; this would be
   a great deal ;-).

2) OSK-bash does not understand the `^'-operator for setting
   a process' priority.

3) OSK-bash does not have a `setpr' builtin.

4) When OSK-bash needs to create a temporary file, then it tries
   to create it in the first existing directory of the following list:

	a)	$TMP
	b)	/dd/tmp
	c)	.

5) If one types
	
	`cd /dd/LOCAL/GNU/CMDS ; cd ...'

   then $PWD will contain

	"/dd/LOCAL/GNU/CMDS/...".
   
   This will be fixed!

6) If OSK-bash is a login shell, then the system global initialization
   file "profile" will not be searched for in "/etc".
   Instead of this it will be searched for in two places:

	a)	/dd/local/sys/profile
	b)	/dd/sys/profile

   The first one found will be used.

7) OSK-bash does have a very pathologic `<Ctrl>E' `<Ctrl>C' handling.

   I do not want to say more about that. Try it yourself ....
   The next release will have a more reliable signal handling.

==============================================================================

Norbert Berzen (norbert@veilchen.informatik.rwth-aachen.de)

*** eof
