Notes for fvwm-2.5.24 on Minix 3.1.3a
			    01/22/2008

----------------------------------------------------------
***  WARNING!  ***
This package will not build without increasing the
stack+malloc size of /usr/gnu/bin/gld to 9 meg (9437184)
with chmem!
You must do this before trying to run build.minix.
It is not allowed to do this in a package's build script,
and there is no provision in binsizes for doing this -
binsizes only operates on the ack toolchain components.
----------------------------------------------------------


	This is a port of the FVWM window manager to Minix3.

	This package will only build under Minix 3.1.3a or newer; and
it will only build with gcc.

	The build.minix script in the top level directory builds and
installs the package. It will refuse to run on releases older than
3.1.3a, or to use the ack toolchain. 

	build.minix installs files as follows: 

		fvwm binaries are installed in /usr/local/bin
		fvwm scripts and samples are installed in /usr/local/share/fvwm
		fvwm modules are installed in /usr/local/libexec/fvwm
		fvwm man pages are installed in /usr/local/share/man 

After installing, you may need to issue the following command to make the
man pages accessible:

	# makewhatis /usr/local/share/man

However, I have observed a bug in the stock Minix 3.1.3a system, such that
man often does not see newly installed man pages in /usr/local/man or in
/usr/local/share/man, even after running makewhatis to update the whatis
database and verifying that the database actually contains entries for the
new pages (whatis/apropos also fails to see them). I have not had time to
try to debug this problem.


When time permits, I would like to make a package of some extra sample
configuration goodies not included in the standard distribution, so that
the user's first exposure to FVWM will not be to the fairly bleak default
look & feel of a bare bones system sans config files. This would include
menus set up with applications that are actually likely to be installed
on a Minix system. That will need to be a separate package.


	A few patches were required to build under Minix. These
patches have not been submitted to the package developer yet.
They are quick and dirty hacks - they work, but should be cleaned up.

1. libs/fsm.h  --  patched to insure that sys/select gets included.

2. configure  --  Removed the test for strings.h, so that it will not
get included. Currently in Minix (3.1.3a) string.h and strings.h
conflict, and fvwm-root will fail to compile if they are both included.



	There are a few problems with FVWM on Minix as yet. They are
most likely Minix bugs, as 3.1.3a is said to be fairly unstable.
In spite of these, most things work, and it is quite usable. It's
the only window manager I use under Minix.

1. FvwmConsole does not work - it dies immediately. We don't know
why yet.

2. The "Setup 95 Script" (that appears on the default menu when no
config files are present) hangs the X server when you try to save the
config, necessitating a reboot. We don't know why yet.

3. FvwmTalk only partly works. Ths first command entered is received
and executed, but then the form hangs & must be manually killed.

4. The FvwmCommandS/FvwmCommand pair do not work. FvwmCommandS dies
immediately.

4. The PipeRead comand does not work. It hangs the X server, requiring
a reboot.

The common thread appears to be "things that try to set up a full-duplex
communication channel via pipes" - I will try to debug this as soon as
I have time.


- RBW