🚀 go-pugleaf

In article <1992Aug10.114453.13836@cs.tu-berlin.de>, marcel@opal.cs.tu-berlin.de (Marcel Weiher) writes:
|> jmd@cube.handheld.com (Jim De Arras) writes:
|> 
|> >In article <1992Aug9.194718.15868@leland.Stanford.EDU> dmitri@physics (Dmitri  
|> >Linde) writes:
|> >> A couple of days ago I started working on ramdisk for NeXT. It almost
|> >> works now, but before I finish it, I would like to know if anybody
|> >> is actually interested in it?
|> >> 
|> >> 	- Dmitri Linde
|> >> P.S. Please reply to dmitri@StarConn.com, not to the newsgroup. Thanx.
|> >
|> >This is a joke, right?
|> 
|> Probably just as much of a joke as his InstantTeX package.  
|> "It'll do all Edit can do, and only costs $150".  Has a cutesy
|> Icon, though.
|> 
|> Marcel

Right. I thought that InstantTeX would do like other TeX-WYSIWYG-packages
which TeX in realtime. It simply does not. What it does is starting TeX
once in a while when you type. This works well with letters and other small
documents, but have you ever tried some _real work_, like a 50+ page document?

I would actually believe in Dmitri writing a ramdisk for the NeXT. I have
waited long for something like that to hog up my memory. There are already
enough useful programs that use much memory, why not try one that does
nothing but add no free space?

Honestly speaking: If someone needs more speed for perpetual access to the
same old files over and over again (like with TeXing), a ramdisk is not
the solution (at least for Unix users). It _is_ possible, though, to patch
/sdmach so that it uses more than the usual 16 buffers (128 K). I have configured
my system to use 384 buffers (i.e. 3 MByte) and it works quite well with that
setting.


cheers, Uwe

Uwe Meyer-Gruhl                      "Close female relative wear combat boots"
Lehrstuhl Informatik IX
Technische Universitaet Muenchen     email:MeyerGru@Informatik.TU-Muenchen.DE
Orleansstr. 34, D-8000 Muenchen 80   tel: ++49 89 48095-209