Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ncar!gatech!mcnc!thorin!hatteras!mccabe
From: mccabe@hatteras.cs.unc.edu (Daniel McCabe)
Newsgroups: comp.os.minix
Subject: Re: bogus macminix manual
Keywords: macminix, problems
Message-ID: <17258@thorin.cs.unc.edu>
Date: 3 Nov 90 04:02:54 GMT
References: <135706.19862@timbuk.cray.com>
Sender: news@thorin.cs.unc.edu
Reply-To: mccabe@hatteras.cs.unc.edu (Daniel McCabe)
Organization: University Of North Carolina, Chapel Hill
Lines: 56

In article <135706.19862@timbuk.cray.com> twosheds@ferris.cray.com (Jay Vollmer) writes:
>
>
>	Alright, it's obvious that the instructions for setting-up the disk
>images for MacMinix are hopelessly muddled!  If there is anyone who has hit
>upon the correct procedure, please let us all in on it!
>
>	Inquiring minds...you know the rest.
>                         
>-- 
>_______________________________________
>J.C. Vollmer             |        IT IS
>Macintosh virtuoso       |        NEVER
>twosheds@ferris.cray.com | AS IT SEEMS!

At least 4 mistakes/bugs that can cause grief:

1) p. 66 re: maccreate limit on blocks in partiton

	maccreate is limited to 32768 blocks.  You wanted to dedicate your 
	600 MByte hard disk to minix?  Sorry, you can't (yet).  5 partitions
	at 32 MBytes each gives you at most 160 MBytes for minix.

2) p. 67 re: setup_root parameter #1

	setup_root expects /dev/hd*, **NOT** harddisk:file1 as its first 
	parameter.  Say that you want your root on the file system that you 
	created on /dev/hd0 with fsck.  Then you need to say
		/etc/setup_root /dev/hd0 2048 32000 32000 2048 14000

3) p. 69 re: modifying /etc/rc to mount /usr from harddisk

	If you got rid of the RAM disk because you have a fast harddisk
	(or you just got rid of the RAM disk period), then the root goes
	onto /dev/hd0 and /usr must mount on /dev/hd1.  Therefore, the
	two lines in the middle of p. 69 should read:
		/etc/mount harddisk:file1 /dev/hd1
		/etc/mount /dev/hd1 /usr
	If you follow the instructions in the manual verbatim and don't use 
	a RAM disk, you will encounter errors on booting and won't have 
	anything in /usr!

4) the compiler can't find stdio.h, et al.

	The permissions in /usr/include as it is unpacked from the distribution
	permit reading only by the bin user.  To fix this,
		su bin
		chmod oug+r /usr/include/*
	Repeat the last command for all subdirectories of /usr/include.
	Don't forget to 'exit' to get back to your normal userid from su.

Joe Pickert and Andy Tanenbaum have been informed of these errors (or were
already aware of them).

Cheers,
danm