Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!ames!ucsd!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!math.lsa.umich.edu!math.lsa.umich.edu!hyc
From: hyc@math.lsa.umich.edu (Howard Chu)
Newsgroups: comp.os.minix
Subject: Re: minix 1.5 question
Message-ID: <1990Jul22.065622.14640@math.lsa.umich.edu>
Date: 22 Jul 90 06:56:22 GMT
References: <25277@nigel.udel.EDU>
Sender: usenet@math.lsa.umich.edu
Organization: University of Michigan Math Dept., Ann Arbor
Lines: 49

In article <25277@nigel.udel.EDU> Ritzert%DMZRZU71.BITNET@cunyvm.cuny.edu writes:
>I'm rather new in this group and run plain minix st 1.1. Could someone
>please sum up the differences between this old version and the most
>recent version (1.5.10 i think)? Are there new features such as having
>support of an scsi drive with 4 partions of 45 MB each (Supra extended
>format). With the old version only 32 MB are supported, and lots of
>strange problems mounting additional file systems appear. Faster file

Dang, I wasn't aware of this problem! I am using a 45 MB partition
right now, in fact. I hope it doesn't bomb out on me as I get closer to
filling it. I was led to believe that there were no size limits to an
individual partition, though I don't know about the extended partitioning
(more than 4 partitions per drive).


>system? Faster screen io? More elaborate sceduling algorithms, eventually
>priority sceduling? Support of other floppy sizes than 360 k / 720 k ?
>My floppy supports at least and without any problems T:82 S:10, even
>with no name disks. And being able to use ~90 tracks on such a floppy is
>really interesting for backup purposes. Support of the 68881 ? Overscan
>support? POSIX compatibility?

Dunno. My patch to 1.1 allowing arbitrary floppy formats was a little
buggy, and isn't in 1.5. The library has been POSIXized. I'm in the
midst of upgrading to 1.5.10, and I'm not sure I've got it right yet.

Maybe one of you can help me - in upgrading to 1.5.0, building the kernel
yields the message "can only relocate longs" from /lib/cv. It seems to
only be a warning, as I get a kernel.mix output, and this can be built
into a running system.

I also seem to be having problems with my library. (Dunno if that's really
the cause yet.) Various programs die with Sig=11, dumping core. Many programs
die with Sig=10, which I have learned is a prompt to chmem them up a little
higher. I'm suspecting a flaky C library as the cause of Sig=11, but I
don't know. (The prominent example is more, which dies after one screen of
text.)

Just as an aside... My FS now occupies a whole 640K all by itself. 512 slots
and 480 blocks in the buffer cache. Yeehah! Time to pare down my 1.6M RAMdisk.
>
>Thanks in advance
>Michael Ritzert
>ritzert@dfg.dbp.de
--
  -- Howard Chu @ University of Michigan
  one million data bits stored on a chip, one million bits per chip
	if one of those data bits happens to flip,
		one million data bits stored on the chip...