The system I'm developing with is currently not in a production state yet.
I've installed a modified version of the ``Linux Terminal Server Project'' http://www.ltsp.org on the AS/400, using the IPCS as the terminal server. BTW: Linux kernel-level DHCP and the AS/400 as a DHCP-Server seem to be incompatible. Use BOOTP!
I've successfully installed StarOffice 5.2 on the IPCS. First I tried to install it by mounting a Directory on the AS/400 under /opt/so52, however that caused an ``Aborted'' message when trying to run the installer.
Then I used the loopback mount trick as second time to mount a 300 MByte ext2 filesystem under /opt/so52 and populated it using an installation from my debian box. After populating it I re-mounted it read-only before doing any user-level configuration.
Staroffice works nicely that way. The first start takes about 50 seconds, but afterwards it's in the client-cache and another start takes only 5 seconds.
Since linux is not integrated into the OS/400 environment the way NT is, it will not get informed on a shutdown caused by varying off the network server description.
You need do perform a shutdown from linux.
You may check and correct filesystem integrity from any linux box in the net as long as the IPCS is varied off and you've choosen NFS-Permissions to allow access from that box.
After a dirty shutdown or a power problem you don't need to go to the IPCS console to fix filesystem problems.
# Mount the AS/400 mount as400:/linux /mnt/as400 # Start filesystem integrity check e2fsck -f /mnt/as400/netfinity/netfinity.disk