Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!network.ucsd.edu!usc!elroy.jpl.nasa.gov!mahendo!thyme!kaleb From: kaleb@thyme.jpl.nasa.gov (Kaleb Keithley) Subject: Re: install 0.1 problems Message-ID: <1992Jul22.165732.7669@thyme.jpl.nasa.gov> Organization: Jet Propulsion Laboratory, Pasadena, CA References: <1992Jul21.211019.6250@thyme.jpl.nasa.gov> <1992Jul21.224908.5459@nrao.edu> Date: Wed, 22 Jul 92 16:57:32 GMT Lines: 55 Onto my NEXT QUESTION: I appear to have a corrupt file in the bin01 files -- the extract hangs. My lowly SPARCstation doesn't have cksum, just sum and /usr/5bin/sum, neither of which produce checksum values remotely similar to those in the MANIFEST file. Can anyone point me to source for the cksum program, or even a binary that I could run prior to trying to extract? I've searched the INSTALL.NOTES and all the directories on TinyBSD, and all the directories on my favorite ftp archive -- did I miss it somehow? Thanks in advance. And now, a humorous (I hope) retort to a mildly inflammatory response to my previous questions. Hit 'n' now if you don't want to be (understandably) bothered. In article <1992Jul21.224908.5459@nrao.edu> cflatter@nrao.edu writes: >Talk about hunting gnats with a shotgun! You don't need to do a low level >format to get rid of the BSD disk label: just write some garbage over it >(this is in the release notes). Thanks Chris, your thoughtful response was most appreciated. :-) I've read the release notes about seventeen times so far, and I expect I'll read them a few more times. Apologies in advance, but winnowing out the chaff in the INSTALL.NOTES is a chore in itself. They are just a teensy bit loquacious. But seriously, using the D*S 'fdisk/mbr' wasn't an option, as I didn't have D*S available. I tried to quit the M'soft habit cold turkey, but Bill Gates just keeps reeling me back in. Rest assured, I have corrected that situation. It didn't occur to me to check if the OS/2 fdisk has an "/mbr" option, mainly because I couldn't even get to OS/2 because my system was furiously trying to boot a nonexistent 386BSD. >Funny... I have a Logitech bus mouse installed and it didn't faze BSD at all. >You might check the jumpers on the mouse card --- you might be able to find >a configuration that works both with OS/2 and 386BSD. Another thoughtful and useful response. Well, I've gotten a little further, with the install since asking that question, and I'm sorry if my newbie questions are an annoyance; maybe you ought to consider a vacation :-) Anyway, once I got 386BSD installed onto the hard disk, I was able to reinstall the card and boot successfully off the hard disk. Since I'm not the only one experiencing bus mouse related problems, I no longer attribute it to pilot error. I'm perplexed as to why the TinyBSD on a floppy won't boot with my Logitech bus mouse card in, but TinyBSD on the hard disk will. -- Kaleb Keithley kaleb@thyme.jpl.nasa.gov Not authorized, in any way, shape, or form, to speak for anyone.