blarson@umb.umb.edu (Bruce Robert Larson) (02/21/90)
I just caught the tail of this discussion, about setting up setting root and usr filesystems under SCO UNIX 3.2, so excuse me if I'm repeating things that have already been said. It is easy to create a separate /usr filesystem, but it will break some of the SCO install scripts and other things too. SCO counts on /usr being a part of the root filesystem. When they install MAIL, SCO links (or tries to, in the case of separate /usr) /usr/bin/mailx to /bin/mail. Since you cannot link across filesystem boundaries, this breaks the install script in the sense that /bin/mail will not exist unless you explicitly copy it in. If /bin/mail does not exist, then the TCP/IP install script will fail by cycling in a closed loop. Further, /etc/(u)mountall is a script that calls /usr/bin/(u)mnt! I recall seeing the mountall call fail because /usr was not mounted. This problem was also easily fixed, by mounting each filesystem explicitly in /etc/rc2. Since I was setting up the system for a client, I decided to scrap the separate usr filesystem. My clients are new to UNIX and would not have been amused by the other surprises that would have inevitably popped up. I did create separate /tmp and /usr/spool filesystems, however, and haven't had any problems with them. Bruce blarson@umb.edu