culberts@hplwbc.hpl.hp.com (Bruce Culbertson) (05/29/90)
I am typing this note on a pc532 running Minix! (I will mail it from another machine, however.) I logged in for the first time yesterday (Sunday) afternoon and it has been running quite smoothly, all things considered. Spent today loading things onto my pc532 hard disk and fixing a few small bugs I discovered along the way. Performance seems quite snappy aside from I/O, which is not Minix's strong point. The latest version, 1.5, is supposed to have faster I/O but I am running 1.3 currently. I have not yet investigated what it will take to upgrade to 1.5. Another issue I have not thought much about is how to distribute this stuff. I guess I can make cdiff's and send them to Phil Budne's archive. It will take a while to get all the sources in one place, figure out what I changed, make diff's, package things in small enough chunks for mail, etc. I'll try to get this done soon but don't hold your breath. Bruce Culbertson
FELLOWS@UNB.CA (05/30/90)
On Mon, 28 May 90 18:37:38 EDT Bruce Culbertson <culberts@hplwbc. hpl.hp.com> writes: > I am typing this note on a pc532 running Minix! (I will mail it Great! Stuff deleted > strong point. The latest version, 1.5, is supposed to have faster > I/O but I am running 1.3 currently. I have not yet investigated what > it will take to upgrade to 1.5. > It seems that it will be difficult to get a legal base copy of Minix 1.3 at this late date. I had pretty well decided to wait until 1.5.x is published before getting a copy. Point to ponder. Is porting from the Atari version of 1.5 going to be easier or harder than from the PC version? That is, are "endian" problems better or worse than "segments"problems? Dave Fellows
news@daver.bungi.com (06/01/90)
Bruce: > I am typing this note on a pc532 running Minix! (I will mail it Great! However... > strong point. The latest version, 1.5, is supposed to have faster > I/O but I am running 1.3 currently. I have not yet investigated what > it will take to upgrade to 1.5. > Another issue I have not thought much about is how to distribute this > stuff. I guess I can make cdiff's and send them to Phil Budne's > archive. It will take a while to get all the sources in one place, Cdiff's between what and what? I have the Prentice-Hall minix disks that go with the book (I think it's version 1.2). I know that minix is not public domain, but the distribution of minix has to be one of the most convoluted and bollixed machinations ever concocted by a book publisher. What is "cdiff", for that matter? I assume it's something like diff. It's not clear to me if I have access to "Phil Budne's archive." You folks have to be forgiving of newcomers to this net. Please don't assume everyone has downloaded every Minix posting since Julius Caesar crossed the Rubicon, or has a computer with egrep, fgrep, ggrep and hgrep. How about I fax you the title page of my Minix book so you know I have a source license? :-)
budd@bu-it.bu.edu (Phil Budne) (06/02/90)
In article <9006010319.AA19313@virtech.UUCP> someone writes: >What is "cdiff", for that matter? I assume it's something like diff. A context diff (generated using diff -c). cdiffs are much better input for patch than are plain diffs. >It's not clear to me if I have access to "Phil Budne's archive." I keep an ftp archive on BU.EDU in ~ftp/users/budd (see dirs 32k, 32k/PC532 and beowulf) There are several mail/FTP g/w's (Princeton and CSnet) so you should be able to list and grab files. Phil Budne, Boston University