AT&T plan 9site
does not compile on NeXTSTEP due to the lacking of some library
strdup. However, it is trivial to patch
it. I have put together
I assume that the source code for the u9fs is installed at
/usr/local/plan9/unix/src/u9fs and the plan 9
distribution is installed in /usr/local/plan9.
# cd /usr/local/plan9/unix/src/u9fs # patch < u9fs-patch-for-NeXTSTEP.diff.txt
Before compile the file, take a look at the
Makefile. There is a flag for whether the underlying arch
is big or small endian. Make sure to set it properly according to the
NeXTSTEP machine you have.
# make install
# Plan 9 file server u9fs stream tcp nowait root /usr/local/plan9/unix/bin/u9fs u9fs /usr/local/plan9
Run the following command as root to add the u9fs services to the service databse.
# echo u9fs 564/tcp u9fs | niload services .
# ps -aux | grep inetd # kill -HUP [inetd pid]
chroot(). You need to copy several files into the /usr/local/plan9/etc directory.
# cd /usr/local/plan9/etc # nidump hosts . > hostsMake sure the IP for the NeXT machine and the IP for the file server is in there.
# cd /usr/local/plan9/etc # nidump passwd . > passwd
# cd /usr/local/plan9/etc # echo next > hosts.equiv ^^^^ file name for you black machine
# cd /usr/local/plan9 # echo none next > .rhosts ^^^^^^^^^^^^^^^^^^^^^^^ put all account for Plan 9 user
# directory contain boot /usr/local/plan9 68020/9nextstation %% next 1 00:00:0f:00:9b:ba 22.214.171.124 68020/9nextstation
# ps -aux | grep bootpd # kill -9 bootpd # /usr/etc/bootpd
bootprogram for NeXT machine
bootis located in
/private/tftpboot/boot. Copy it to
/usr/local/plan9.However, the newer version does not do the initialization properly and this causes the plan 9 to hang during boot time. I used the
bootfrom NeXTStep 2.1. If you don't have access to NeXTStep 2.1
boot, email@example.com sent me a suggestion about how to get
bootin 3.x to work. See the following.
Here is the moment you have been waiting for.
> ben 68020/9nextstationIf you are using boot from NS 2.1, you should see the Plan 9 coming up on the screen. If you use later version of the boot program, the system will hang with Exception #4. Don't panic yet. The following may fix it. Thanks to firstname.lastname@example.org.
A quick fix if you don't have an early version boot program is to start the kernel manually with the following commands to the ROM monitor, after the exception occurs:
> r pc ? 4000000 > cThis changes the program counter to the correct entry point 4000000 and then execution is begun at that point.
I haven't tried that but let me know if you do. If everything goes well, you need to tell the black box what is its IP and where the file server is.
It does not matter what value you set the authentication server since it will not be used by the client.
[boot message ...] root at (tcp il)[il]: tcp my ip address[no default]: [IP of the next machine] my net mask[no default]: [netmask] my gateway[no default]: [IP of the gateway] file server[no default]: [IP of the file server] authentication server [0.0.0.0]: [RET to take default][ user[none]: [RET]