[comp.os.minix] fsck.c garbled and system won't boot etc.

pa1343@sdcc15.UUCP (pa1343) (10/15/88)

Sorry my name is not on From: line.  The tyrants here won't let me
have my name in the /etc/passwd file.  Anyway, it's:
John J. Marco
Internet: pa1343@iugrad2.ucsd.edu
uucp: not sure, possibly use the "Path " line above, or as far as I
know, the best path I know is:
~~~~~~!nosc!ucsd!iugrad2!pa1343

To the point:
	I just spent three weeks upgrading an untouched Prentice-
Hall distribution MINIX 1.2 and I could not get the cdiffs for
fsck to work.  I tried over several times with fsck.c and all of 
the posted diffs for it, but not even the first one would work,
leading me to believe that a posting is missing somewhere.  Could
somebody please mail it to me or better yet, mail it to:
broman@cod.nosc.mil  since he updates the archives around here 
and I believe he mentioned in one of his postings that he too is
missing fsck.c (the correct version).

I tried to boot MINIX 1.3c with the ancient 1.2 fsck, but it doesn't
seem to work for me.  I don't think that fsck should crash minix. 
(I am probably wrong)  I boot, and the floppy light goes on and 
keeps trying to read or write the disk (no access sounds from drive)
I even tried the new bootblok fix.  To no avail.  I am wondering if
there is a REQUIRED directory structure for the root file system so
that init can find some files.  (Init seems to have started by the
process table, but floppy and wini both read as IDLE.)
If there is a required directory structure, could somebody post it
to the net as a reference for others.  

Finally, to the point of the harddisk root file system issue.  I
have Jim Paradis's patch to make minix the root file system
/dev/hd2.  I really would like to avoid having to use /dev/hd3
(this is a huge, filled, 5Mb partition with the v1.3 stuff)
Also, I like to keep the main root fs on physical disk and a
100-120kb ramdisk for /tmp.  Is it still possible to do this?

As a last point, has anybody out there ever found a way to make the
BLUE CHIP PC Printer work.  I posted an article last fall about
this, but I have been isolated from usenet for the summer.  It seems
that the printer is not being reset at boot time because when I turn
the printer on the paper-out light goes on for no reason.  The
parallel port probably needs to be initialized in some way to clear
it.  The light stays on also until dos boots up and then the printer
seems to reset.

Any info would be greatly appreciated by me and possibly others with
the same problem.

+-----------------------+---------------------------------+
John J. Marco      	|                   OS      PS    |
pa1343@iugrad2.ucsd.edu | OS/2 on PS/2:    ---- on ----   |
ee52alis@ieng2.ucsd.edu |		     2       2    |
			| DOS on PC...<EOT>		  |
+-----------------------+---------------------------------+

pa1343@sdcc15.UUCP (pa1343) (10/17/88)

In article <638@sdcc15.UUCP>, pa1343@sdcc15.UUCP (pa1343) writes:
> Sorry my name is not on From: line.  The tyrants here won't let me
> have my name in the /etc/passwd file.  Anyway, it's:
> John J. Marco
> Internet: pa1343@iugrad2.ucsd.edu
> uucp: not sure, possibly use the "Path " line above, or as far as I
> know, the best path I know is:
> ~~~~~~!nosc!ucsd!iugrad2!pa1343
> 
Yep, it's me again.  I tried a few new things with minix and it all
failed to get MINIX 1.3 to Boot.

> Hall distribution MINIX 1.2 and I could not get the cdiffs for
> fsck to work.  I tried over several times with fsck.c and all of 

I hand patched the new fsck  (missing some lines though).
It does not help the boot situation, but seems to work fine.
The kernel , mm, tty, IDLE processes are running by a press of 
the <F1> key, but only TTY and IDLE are using CPU cycles.

here is the crash situation:
I boot the computer, an d press '=' at the fsck prompt (I have the
v1.2 P-H supplied root file system in drive 0)  The floppy light 
goes on and nothing happens.  No disk seeks, nothing.  Just 
IDLE for both the floppy and winchester processes.

> Finally, to the point of the harddisk root file system issue.  I

I will try to use the hard disk pathches from 1.2.  If I do, I will
post diffs.   There is no guarantee of this.  (I still can't even
get the @%!* kernel to boot and read the ramdisk into memory. :-( )
 
+-------------------------+---------------------------------+
| John J. Marco      	  |                   OS      PS    |
| pa1343@iugrad2.ucsd.edu | OS/2 on PS/2:    ---- on ----   |
| ee52alis@ieng2.ucsd.edu |		       2       2    |
| 	      		  | DOS on PC...<EOT>		    |
+-------------------------+---------------------------------+