dxxb@beta.lanl.gov (David W. Barts) (10/10/88)
About 10 days ago, I sent a request to the net for information on FTP'able Minix patches. Information about the archives on bugs.nosc.mil follows. Thanks to browman@nosc.mil and paula@boeing.com for the info. Haven't actually had time to try it out yet; will probably give it a try this weekend or some evening this week. -> Bugs.Nosc.Mil archives comp.os.minix news articles of lasting interest -> and other Minix material, such as a list of machines reported to be -> able to run Minix. Material of widespread interest includes diffs for -> updating v1.1 to v1.2 and preliminary fixes headed for v1.3, code developing -> toward a serial port driver, diffs for cross compilation under MS-C and -> Turbo-C, the new asld with split I&D, and recently the editor, Elle v4.1. -> -> This material is available by anonymous FTP (during non-business hours) -> on bugs.nosc.mil in directory pub/Minix . The file SUBJECTS contains a list -> of Subject lines serving as a kind of index. The file names are mostly just -> the Message-Id of a news article. -> -> Several ways to get these kinds of goodies, in order: -> -> 1. Look, or ask someone you know to look, for articles still available -> on the machine where you read news, or on a neighbor. -> 2. Ask the person who posted the material to mail it to you. -> 3. Get access to a machine on the ArpaNet (or talk to an acquaintance who -> has access) and FTP to louie.udel.edu or bugs.nosc.mil . -> 4. To get smaller selections from the bugs.nosc.mil archive by Email, -> see the instructions following. -> 5. To get very large amounts of material from archives, talk to someone -> in charge of it, e.g. me, about mailing a tape. Surface-mailing of tapes -> is cheap. Voluminous Email is expensive, though not as expensive as -> posting news. -> -> Everything available to anonymous FTP in directory pub/Minix can be obtained by -> sending a mailed request to minix-server@bugs.nosc.mil or nosc!minix-server . -> Include in the message, either among the header fields or the body, a line like: -> Reply-To: <your mail address-> -> -> and after that a line or lines naming desired files e.g.: -> -> send compatibility -> send SUBJECTS -> send 1180@botter.cs.vu.nl -> -> to get an automatic mailed reply. Notice file names are case sensitive. -> <your mail address-> should look something like one of these examples: -> -> you@stolaf.uucp -> sdcsvax!ihnp4!mtgzz!guru -> cs.vu.nl!giant@uunet.uu.net -> person%utoronto.bitnet@cunyvm.cuny.edu -> user%ulowell.csnet@relay.cs.net -> honcho%durham.mailnet@mit-multics.arpa . -> -> Email is not free. Abuse of the system will cause bad karma. -> Contents may have settled during shipment. -> -> -> Vincent Broman, code 632, Naval Ocean Systems Center, San Diego, CA 92152, USA -> Phone: +1 619 553 1641 Internet: broman@nosc.mil Uucp: -> sdcsvax!nosc!broman -> David W. Barts N5JRN, Ph. 509-373-4554 (FTS 440-4554), dxxb@lanl.GOV BCS Richland Inc. | 603 1/2 Guernsey St. P.O. Box 300, M/S S2-01 | Prosser, WA 99350 Richland, WA 99352 | Ph. 509-786-1024