Planning your SCO XENIX System V Ver. 2.3 disk layout

Metadata:
Published: 2024-01-28
Last modified: Fixed published date and printing


Preface

It is the year 1988. You are holding in your hand installation media for an operating system called XENIX, version 2.3, for your 386-based computer. It comes with an installation manual. On paper, of course, as installation manuals would come back in those days. Helpfully, it provides some guidance on how to plan your disk layout. Albeit the original text is profoundly beautiful in the way only dense technical writing set in 10 pt. Times in book format can be, copyright once more gets in my way of reproducing it here.

To summarize, the manual suggests that you may have a separate /u filesystem if you have a hard disk or partition. It touts the advantages thereof:

  1. Having it may simplify system backups by being able to save on space because there are less files to back up on the other filesystems.
  2. There are speed benefits to small filesystems because smaller filesystems have less inodes and therefore require fewer searching operations through indirection.
  3. If the system crashes, it is more likely to survive without corruption by reducing activity on the root filesystem.

But it also cautions that there is no way to resize filesystems, so some flexibility is lost with a separate /u filesystem and there is some additional complexity introduced to system administration by having a separate filesystem.

At the end of the section about planning your disk layout, it helpfully provides a worksheet for you to work through. Considering that it is paper, it is also effectively single-use. For no reason other than hilariously concentrated autism, I will be reproducing it here with an online calculator written in ungodly JavaScript. However, to preserve the authentic feeling of paper, I am also giving you the option of printing it. This preface will disappear in print mode, leaving only the worksheets.

I had to take some minor creative liberties with the table, namely always displaying the units. On paper, you would always write the units down, but for the sake of clarity, I added them everywhere.

Swap Space Allocation
InstructionsCalculationResult
 × 512K K
 + 256K K
3. Greater of (1) and (2): K
 × 512K K
5. Sum of (3) and (4): K
/u Filesystem Allocation
InstructionsCalculationResult
1. / 2000 MB
2. × .5 MB MB
3. × .5 MB MB
4.Add (2) and (3) for size of /tmp MB
5. MB
6. MB × 1.2 MB
(rounded)
7.Subtract size of root filesystem (6) from XENIX partition (or whole disk) −  MB
8.If (7) is greater than or equal to 5–10 MB, continue, else no /u filesystem
9. × 1.5 MB MB
10. MB
11. MB
12.Add (9) thru (11) for size of /u filesystem MB
13.If /u (12) is less than (7), continue, else no /u
14. × 1000 blk