Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!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: Update to 1.5.10 Upgrade Kit Message-ID: <1990Jul23.090004.255@math.lsa.umich.edu> Date: 23 Jul 90 09:00:04 GMT References: <5299@plains.UUCP> <90196.231041BLS7@psuvm.psu.edu> Sender: usenet@math.lsa.umich.edu Organization: University of Michigan Math Dept., Ann Arbor Lines: 112 In article <90196.231041BLS7@psuvm.psu.edu> BLS7@psuvm.psu.edu writes: >*sigh* I agree! >I think *someone* who has a running ST 1.5.10 pacakage should make a new >upgrade kit for the ST. Here are some problems: (and I'm only going to >1.5.0) Real Soon Now... > 1) The first thing that you're supposed to unpack and make is the new > make for Minix. Well, this is fine and dandy *but* you have to have > the utime.h file and some other .c files which are *not* with the ST > package as far as I can tell. Putting it truthfully in the READ_ME > file that comes with make it says that the files that are needed were > posted *but* this is over 7 months since the probable posting date of > the articles. The upgrade itself is supposed to take more than enough > time why should we have to scrounge around for all of the needed files? > Yeah, this was a real drag. I think you also needed the new library before I could link the new make. I wound up using the old make to build the 1.5.0 library first, then fiddled with header files until I could get the new make running. At any rate, going to 1.5.0 was a nightmare because the library was really buggy. Word of advice if you're still going thru this - don't wipe out your 1.1 bin directories. I was really hosed by not backing up the binaries. ls, more, and tos{dir,read,write} stopped working, among others. (None of these are really crucial; you can survive without them, but it's very very painful. In particular, since I needed the tos command to get the later updates onto my minix drive, I was heavily bumming...) I dunno what the problems were, but it took a long time before I could get my 1.1 lib and include back into working order to get a good 1.1 version of each command running again. > 2) How are the PC 1.5 files archived? I have them sitting as (supposedly) > ASCII text on floppy right now. Here is *exactly* what I did to get > them: (for those ppl who e-mailed me flames like "do you know what ftp > is?" because of my last post.) > > a) I ftp'd the files from plains.nodak.edu to pogo.ai.mit.edu > (borrowing a unix account there) > b) I uncompressed *everything*. > c) I ftp'd the files down to a pc floppy. Step c is suspect. Did you ftp as binary or text? > d) I brought the floppys home. > e) I did a `tos -r /dev/dd0 filename >filename' If you ftp'd as text in step c, then you needed "-ra" to get the CR/LF conversion. If you ftp'd binary, then I don't understand where the problem is. > > (For those who don't know -- Atari and IBM have the same format of disks > thus there are no problems with downloading to a PC then taking the > disks to an Atari.) > > After all of this I have a whole bunch of unwanted :M's after everything > but that is minor to fix. Oh, that answers that question.... (re: my previous two comments.) > > I have no problem with the ST files now as I wrote a little C program > which takes off all of the :M's in it fine but, the PC files dont seem > to want to work. I have tried `sh get these files. (Both before and after trying my little program on > them -- Since I couldnt find anything that said how the PC files are > archived.) Could have just used "tr -d 015", but no matter. I thought these were all shar files, but they probably used sed, which you don't have in Minix ST 1.1. I unpacked everything on a Unix box. I tar'd my 1.1 source tree off my ST and transferred it to the Unix box, and applied all the patches there. I'm now re-extracting all the upgrade kits in combination with RCS, so I can keep track of when files appeared/got updated, and prepare cdiffs for a new upgrade kit. > > 3) Among all of the rest there are references in the directions for the > upgrade to 1.5.0 to files in the PC upgrade that *do not exist*. > (i.e. Step #7 in the directions mentions PC part #73 -- some kind > soul told me already that this is patch.00.Z.) Hm. In the files I got off plains.nodak.edu, the :Index file plainly listed which filename matched which posting number. At any rate, yeah, there are a lot of missing files. I think they finally appear for ST use in the 1.5.10 upgrade kit. At least, I seem to have a complete collection now. > >In conclusion I will say this: > > The ST upgrades might have been quite fine if you were around while they >were being develpoed and posted but, they are in very poor shape now. I think >it's time for someone to come out with the "definitive" ST 1.1 to ST 1.5.10 >upgrade kit with *either* nothing to do with the PC Upgrade Kit *or* with all >of the parts of the PC Kit *clearly* listed out that are needed. I personally >would devote days to making this reality but, alas I have to get 1.5.10 running >before I could make that happen. > >Could someone with a running ST 1.5.10 version would please e-mail me? As I >would really like to have it running -- 1.1 has lots-o-bugs that seem to be >popping up right in the things that i really need. > > > Babs Silvis It's been quite the hassle, that's for sure. But I guess having the rs232 stuff is worth it. Lots of the commands work much much better. ls doesn't run out of space in the commands directory, etc. I don't think it's worthwhile to only go to 1.5.0, or 1.5.5, you'll definitely want to go straight from 1.1 to 1.5.10. -- -- 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...