Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!rochester!pt.cs.cmu.edu!zardoz.club.cc.cmu.edu!ddj
From: ddj@zardoz.club.cc.cmu.edu (Doug DeJulio)
Newsgroups: comp.sys.next
Subject: Re: Syquest HD speed
Keywords: Syquest
Message-ID: <12475@pt.cs.cmu.edu>
Date: 25 Mar 91 16:50:22 GMT
References: <1991Mar25.025045.29202@nntp-server.caltech.edu>
Organization: Castle Anthrax, Pittsburgh
Lines: 20

In article <1991Mar25.025045.29202@nntp-server.caltech.edu> dlisoski@pooh.caltech.edu (Derek Lee Lisoski) writes:

> it behaves exactly like a floppy, but it initializes to 38 usable MB.
> So it seemed like it would act like a big fast (25ms) floppy, right?
> Well, it acted like a big floppy, but it was NOT fast.

>   Question: Is there some fundamentally different way in which the NeXT
>treats removable vs. fixed media?

YES!  When the NeXT puts a filesystem on a floppy, it optimizes for
space insted of speed.  I don't know if it does this for flopticals,
so it might not be for *all* removable media.

You can use tunefs(8) to change this.  Type "man 8 tunefs" for more
info, or look it up in digital librarian.
-- 
Doug DeJulio
ddj@zardoz.club.cc.cmu.edu

       "You can tune a filesystem, but you can't tune a fish."