From owner-freebsd-stable Sun Feb 4 02:48:41 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA21081 for stable-outgoing; Sun, 4 Feb 1996 02:48:41 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA21067 Sun, 4 Feb 1996 02:48:38 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id LAA25070; Sun, 4 Feb 1996 11:30:11 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id LAA02394; Sun, 4 Feb 1996 11:09:48 +0100 (MET) Date: Sun, 4 Feb 1996 11:09:48 +0100 (MET) From: Andreas Klemm To: Tomi Vainio cc: ports@FreeBSD.org, stable@FreeBSD.org Subject: Re: cached port updated from 1.4pl0 to 1.4pl2 In-Reply-To: <199602032011.WAA12071@zeta.fidata.fi> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.org Precedence: bulk On Sat, 3 Feb 1996, Tomi Vainio wrote: > Andreas Klemm writes: > > > > Here is the complete modified port. From the ChangeLog: > > > > Changes to the v1.4pl2 release (Jan 20, 1996): > > Hi! > > I have serious problems with cached 1.4pl2 and FreeBSD 2.1-stable. > I can't access harvest web server so I need to find some place where > to get help. How well you know this software? Could you help me? cached is the *object cache* for a www server. It's not a WWW server itself. Don't intermix it. BTW: (Satoshi, huhu !!!! ;-) In the example config file I did a little mistake, perhaps this prevents you to access your proxy server. ascii port has to be 8080 not 80. #ascii_port 3128 ascii_port 8080 Otherwise you should tell me more about your configuration. Another thing is... cached can be run in two operating modes: a) as http accelerator, so that people can access _your_ www server more quickly b) as proxy cache, this makes your WWW accesses to the Internet more quickly. My example config file is intended for usage b). Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<< From owner-freebsd-stable Sun Feb 4 05:20:18 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA01357 for stable-outgoing; Sun, 4 Feb 1996 05:20:18 -0800 (PST) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA01352 for ; Sun, 4 Feb 1996 05:20:16 -0800 (PST) Received: (from kimc@localhost) by moonpie.w8hd.org (8.6.12/8.6.12) id IAA27246; Sun, 4 Feb 1996 08:18:35 -0500 Date: Sun, 4 Feb 1996 08:18:34 -0500 (EST) From: Kim Culhan To: Michael Smith cc: stable@FreeBSD.ORG Subject: Re: majors.i386 In-Reply-To: <199602040426.OAA03111@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG Precedence: bulk On Sun, 4 Feb 1996, Michael Smith wrote: > Kim Culhan stands accused of saying: > > This was recently obtained during a failed attempt from freefall, is > > this delete Ok? > > Since most sup users are the reticent technical types, I'll stand up and > SHOUT ABOUT THIS REALLY LOUDLY. > > _DO_NOT_SUP_FROM_FREEFALL_ Understand, no problem. I will say though that I follow this list rather closely and the only mention I've seen about the alternate sites was a few weeks ago when Jordan announced the need for them. Then there was the announcement re. availability of the supkit. As for mentions about freefall and a critical situaion like this, none that I remember beyond the origonal call but I got the message now. > Freefall is _overloaded_. It is _sinking_. It is the sole cause for true > concern about landfill subsidence in that area. > > If you are in the US, rummage through the .freebsd.org domain; I can resolve > sup2, sup3 and sup4, I'm sure there are more that aren't in there yet. > > If you're overseas, there's likely a server nearer to you; here we have > sup.au.freebsd.org, and sup2.au... at least. > If you sup from Freefall, your hair will fall out, you will give birth to > small hairy aliens that will eat your socks, and _weird_ things may > happen to the state of your source tree. > > Pick a _single_ supserver, and stick with it. You may be half a day or > so behind the bleeding edge, but that will let the commit mails get to > you before you hose everything. I wanted to get it once but the point is well taken. regards kim -- kimc@w8hd.org From owner-freebsd-stable Sun Feb 4 11:21:29 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA25372 for stable-outgoing; Sun, 4 Feb 1996 11:21:29 -0800 (PST) Received: from tellab5.lisle.tellabs.com (tellab5.lisle.tellabs.com [138.111.243.28]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA25363 for ; Sun, 4 Feb 1996 11:21:27 -0800 (PST) From: mikebo@tellabs.com Received: from tellabk.tellabs.com by tellab5.lisle.tellabs.com with smtp (Smail3.1.29.1 #4) id m0tj9zS-000jCDC; Sun, 4 Feb 96 13:20 CST Received: by tellabk.tellabs.com (4.1/1.9) id AA20378; Sun, 4 Feb 96 13:20:45 CST Message-Id: <9602041920.AA20378@tellabk.tellabs.com> Subject: stable digest? To: freebsd-stable@freebsd.org Date: Sun, 4 Feb 1996 13:20:45 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org Precedence: bulk Isn't it time to provide the freebsd-stable list in digest form? I like to follow the discussions, but the volume of individual posts has increased as of late, making it annoying to have to deal with dozens of individual posts. Regards, - Mike -- -------------------------------------------------------------------------- Michael Borowiec - mikebo@tellabs.com - Tellabs Operations Inc. Senior Member of Technical Staff 4951 Indiana Avenue, MS 63 708-512-8211 FAX: 708-512-7099 Lisle, IL 60532 USA -------------------------------------------------------------------------- From owner-freebsd-stable Mon Feb 5 10:02:04 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA13907 for stable-outgoing; Mon, 5 Feb 1996 10:02:04 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA13902 Mon, 5 Feb 1996 10:02:02 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.6.12/8.6.12) with ESMTP id KAA05372; Mon, 5 Feb 1996 10:01:57 -0800 Message-Id: <199602051801.KAA05372@austin.polstra.com> To: jkh@time.cdrom.com Cc: hackers@freebsd.org, stable@freebsd.org Subject: Re: sup is broken? In-reply-to: <26947.823390500@time.cdrom.com> Date: Mon, 05 Feb 1996 10:01:57 -0800 From: John Polstra Sender: owner-stable@freebsd.org Precedence: bulk Jordan wrote: > PLEASE DON'T USE SUP.FREEBSD.ORG TO UPDATE YOURSELF! Good evening, my name is John, and I use sup.freebsd.org to update myself. [ embarrassed applause from the other supaholics in the audience ] Wow, I feel better already! Jordan, I would be more than happy to switch to an alternate sup server, if only the other ones would work worth a sh*t! I have tried several times to use sup2 and other servers. Each time, it has caused me nothing but trouble. Am I just lucky? Last night, after reading your latest admonition against using sup.freebsd.org, I tried again to use sup2. As soon as it connected up, it began systematically deleting the files in my sup tree, shamelessly announcing each deletion as it went about its sordid business. To all appearances, it had the intention of deleting my entire tree. So I killed it, and once again went back to sup.freebsd.org, which always works just fine for me, thank you. When I try an experiment, and that experiment attempts to delete 220 MB of my files, I lose my thirst for adventure very quickly. Nevertheless, if you or somebody else can give me some clue about how to switch to a different sup server without losing all my perfectly good files, I'll try again. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-stable Mon Feb 5 10:27:25 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA15295 for stable-outgoing; Mon, 5 Feb 1996 10:27:25 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA15277 Mon, 5 Feb 1996 10:27:22 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14971(3)>; Mon, 5 Feb 1996 10:26:43 PST Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177478>; Mon, 5 Feb 1996 10:26:33 -0800 X-Mailer: exmh version 1.6.4 10/10/95 To: "Jordan K. Hubbard" cc: Richard Wackerbarth , Kim Culhan , hackers@freebsd.org, stable@freebsd.org Subject: Re: sup is broken? In-reply-to: Your message of "Sat, 03 Feb 1996 15:35:00 PST." <26947.823390500@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 5 Feb 1996 10:26:31 PST From: Bill Fenner Message-Id: <96Feb5.102633pst.177478@crevenia.parc.xerox.com> Sender: owner-stable@freebsd.org Precedence: bulk In message <26947.823390500@time.cdrom.com>you write: >That's one option, or as I also told Kim - PLEASE DON'T USE SUP.FREEBSD.ORG >TO UPDATE YOURSELF! Has anyone thought of not calling it sup.freebsd.org any more? Call it sup-master.freebsd.org, instead, and give sup.freebsd.org 3 A records, those of sup1, sup2, and sup3. That way, if someone doesn't know what they are doing, they will get a random one of sup1, sup2 or sup3; if they know what they are doing they will use sup[123] directly, and it would be really hard to hit freefall by accident. Bill From owner-freebsd-stable Mon Feb 5 13:49:22 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA28458 for stable-outgoing; Mon, 5 Feb 1996 13:49:22 -0800 (PST) Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA28452 Mon, 5 Feb 1996 13:49:17 -0800 (PST) Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id PAA07099; Mon, 5 Feb 1996 15:48:55 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 5 Feb 1996 15:48:59 -0600 To: John Polstra From: Richard Wackerbarth Subject: Re: sup is broken? Cc: hackers@FreeBSD.org, stable@FreeBSD.org Sender: owner-stable@FreeBSD.org Precedence: bulk Jordan wrote: >> PLEASE DON'T USE SUP.FREEBSD.ORG TO UPDATE YOURSELF! John Polstra replied: >Last night, after reading your latest admonition against using >sup.freebsd.org, I tried again to use sup2. As soon as it connected >up, it began systematically deleting the files in my sup tree, >shamelessly announcing each deletion as it went about its sordid >business. To all appearances, it had the intention of deleting my >entire tree. So I killed it, and once again went back to >sup.freebsd.org, which always works just fine for me, thank you. > >When I try an experiment, and that experiment attempts to delete >220 MB of my files, I lose my thirst for adventure very quickly. >Nevertheless, if you or somebody else can give me some clue about >how to switch to a different sup server without losing all my >perfectly good files, I'll try again. As I have pointed out, the cvs tree that I am getting from sup2 also seems to have problems. As a result, my distribution in the name of -stable, reflects the same condition. We MUST get these problems fixed or we all will be forced to "look to the source" for correct data. ---- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-stable Mon Feb 5 14:48:56 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA02680 for stable-outgoing; Mon, 5 Feb 1996 14:48:56 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA02675 Mon, 5 Feb 1996 14:48:51 -0800 (PST) Received: by Sysiphos id AA28166 (5.67b/IDA-1.5); Mon, 5 Feb 1996 23:48:46 +0100 Message-Id: <199602052248.AA28166@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Mon, 5 Feb 1996 23:48:46 +0100 X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: hackers@freebsd.org, current@freebsd.org, stable@freebsd.org Subject: Lost some mail ... Sender: owner-stable@freebsd.org Precedence: bulk Hi all! Just in case you sent some NCR or PCI driver related message within the last 24 hours: We had major reliability problems with our central file server, and it managed to crash (again) while I was just updating my mail inbox. This made me loose soem 30 messages I intended to reply to later ... So in case you don't hear from me within for more than a day after sending mail of some kind, please resend your message, since it most probably was lost. Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-stable Mon Feb 5 15:22:01 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA04932 for stable-outgoing; Mon, 5 Feb 1996 15:22:01 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA04927 Mon, 5 Feb 1996 15:22:00 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id PAA26558; Mon, 5 Feb 1996 15:19:20 -0800 From: Julian Elischer Message-Id: <199602052319.PAA26558@ref.tfs.com> Subject: Re: sup is broken? To: fenner@parc.xerox.com (Bill Fenner) Date: Mon, 5 Feb 1996 15:19:20 -0800 (PST) Cc: jkh@time.cdrom.com, rkw@dataplex.net, kimc@w8hd.org, hackers@freebsd.org, stable@freebsd.org In-Reply-To: <96Feb5.102633pst.177478@crevenia.parc.xerox.com> from "Bill Fenner" at Feb 5, 96 10:26:31 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-stable@freebsd.org Precedence: bulk make it so.. > > In message <26947.823390500@time.cdrom.com>you write: > >That's one option, or as I also told Kim - PLEASE DON'T USE SUP.FREEBSD.ORG > >TO UPDATE YOURSELF! > > Has anyone thought of not calling it sup.freebsd.org any more? Call it > sup-master.freebsd.org, instead, and give sup.freebsd.org 3 A records, those > of sup1, sup2, and sup3. That way, if someone doesn't know what they are > doing, they will get a random one of sup1, sup2 or sup3; if they know what > they are doing they will use sup[123] directly, and it would be really hard to > hit freefall by accident. > > Bill > > From owner-freebsd-stable Mon Feb 5 15:49:55 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA07044 for stable-outgoing; Mon, 5 Feb 1996 15:49:55 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA07026 Mon, 5 Feb 1996 15:49:51 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id PAA03904; Mon, 5 Feb 1996 15:48:55 -0800 Message-Id: <199602052348.PAA03904@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: Julian Elischer cc: fenner@parc.xerox.com (Bill Fenner), jkh@time.cdrom.com, rkw@dataplex.net, kimc@w8hd.org, hackers@freebsd.org, stable@freebsd.org Subject: Re: sup is broken? In-reply-to: Your message of "Mon, 05 Feb 1996 15:19:20 PST." <199602052319.PAA26558@ref.tfs.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 05 Feb 1996 15:48:55 -0800 Sender: owner-stable@freebsd.org Precedence: bulk >make it so.. Not until someone goes and verifies that all of the sup*.freebsd.org targets are working correctly. Also, my experiance with multiple A records is that it always comes up with them same one (not random). -DG David Greenman Core Team/Principal Architect, The FreeBSD Project >> In message <26947.823390500@time.cdrom.com>you write: >> >That's one option, or as I also told Kim - PLEASE DON'T USE SUP.FREEBSD.ORG >> >TO UPDATE YOURSELF! >> >> Has anyone thought of not calling it sup.freebsd.org any more? Call it >> sup-master.freebsd.org, instead, and give sup.freebsd.org 3 A records, those >> of sup1, sup2, and sup3. That way, if someone doesn't know what they are >> doing, they will get a random one of sup1, sup2 or sup3; if they know what >> they are doing they will use sup[123] directly, and it would be really hard to >> hit freefall by accident. >> >> Bill From owner-freebsd-stable Mon Feb 5 16:00:37 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA08053 for stable-outgoing; Mon, 5 Feb 1996 16:00:37 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA08033 Mon, 5 Feb 1996 16:00:31 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16057(1)>; Mon, 5 Feb 1996 15:59:48 PST Received: by crevenia.parc.xerox.com id <177478>; Mon, 5 Feb 1996 15:59:45 -0800 From: Bill Fenner To: davidg@root.com Subject: Re: sup is broken? Cc: hackers@freebsd.org, stable@freebsd.org Message-Id: <96Feb5.155945pst.177478@crevenia.parc.xerox.com> Date: Mon, 5 Feb 1996 15:59:44 PST Sender: owner-stable@freebsd.org Precedence: bulk >Also, my experiance with multiple A records is that it always comes >up with them same one (not random). Recent BIND's will round-robin multiple A records; you should get them from the name server in a pseudo-random order. Try "dig @uucp-gw-1.pa.dec.com a tbfddi1.gw.psu.edu | head -15" several times in a row, you will get different answers. (Of course, if you ask your local caching server, then you will keep getting the same answers -- but we are talking about widely seperated people doing their own individual queries, and everyone is not likely to be talking to the same caching server.) Bill From owner-freebsd-stable Mon Feb 5 16:12:10 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA08782 for stable-outgoing; Mon, 5 Feb 1996 16:12:10 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA08774 for ; Mon, 5 Feb 1996 16:12:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id QAA26093 for ; Mon, 5 Feb 1996 16:11:49 -0800 Date: Mon, 05 Feb 1996 16:11:47 -0800 Message-ID: <26087.823565507@time.cdrom.com> From: "Jordan K. Hubbard" Subject: Re: sup is broken? MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" To: undisclosed-recipients:; Sender: owner-stable@FreeBSD.ORG Precedence: bulk ------- =_aaaaaaaaaa To: John Polstra cc: hackers@freebsd.org Subject: Re: sup is broken? In-reply-to: Your message of "Mon, 05 Feb 1996 10:01:57 PST." <199602051801.KAA05372@austin.polstra.com> Date: Mon, 05 Feb 1996 16:11:47 -0800 Message-ID: <26087.823565507@time.cdrom.com> From: "Jordan K. Hubbard" > Jordan wrote: > > > PLEASE DON'T USE SUP.FREEBSD.ORG TO UPDATE YOURSELF! > > Good evening, my name is John, and I use sup.freebsd.org to update > myself. > > [ embarrassed applause from the other supaholics in the audience ] Hey, OK, let's be honest here - *I* use sup.freebsd.org to update myself (it would be silly otherwise, given that my SLIP line goes directly into that machine, but that's another matter) and a number of other core team people do as well. I didn't mean to imply that using sup.freebsd.org was a mark of shame, simply that the "mainstream" should no longer consider it the one and only place to come for their bits. We've gotten too big for that scheme to work any longer.. :-( That said: > Jordan, I would be more than happy to switch to an alternate sup > server, if only the other ones would work worth a sh*t! I know that there are still some problems with the other sup sites, and it's more than likely that some additional shuffling of the servers and name space will be required until we have fairly beefy and reliable machines serving sup2.freebsd.org and sup3.freebsd.org at a minimum. We're just starting out with this here, more in panic reaction to freefall melting down than anything else, and it's going to take a little longer to work the bugs out. I didn't say that this was all going to work right away! :-) Nonetheless, even without fully functional backup, it's clear that sup.freebsd.org is now too overloaded to even use for most people and we have to do the best we can with the alternative resources available. We have no other choice! On the brighter side, someone just volunteered to create a sup server at a fairly well-connected spot (and I'll be coy about it for now to avoid potentially jeopardizing these arrangements during their vulnerable boost phase) and that may go a fair ways towards solving these problems. Not that more sup servers aren't needed! They are. We could easily use *3 times* the number of sup sites we currently have since freefall clearly turns away more people than it's able to service these days, and even Paul Traina's sup2.freebsd.org has been full on more than one occasion. Even with a well-distributed load we'll still have more than we can handle, so if you'd like to create a sup server at your regional NAP (dream :) or well-connected ISP as a public service then please, by all means do so! How does it work? At the risk of repeating myself, here are the basic details: 1. You need to be willing to host at least 10 bandwidth-sucking connections from your machine. Sup is not a "light" service, and it would be dishonest of me not to point that out in advance to prospective server volunteers. You also need about 300-600MB of disk space, depending on how many of the collections you intend to offer. If you've got the CPU power and bandwidth to spare and this still doesn't scare you off, then your next step is: 2. Grab the following tarball: ftp://freefall.freebsd.org/pub/FreeBSD/sup-server-kit.tar.gz Unpacked, this will contain some instructions on setting up a sup server and preparing the "collections" that it provides to its clients. You should also mirror your own trees from sup.freebsd.org, and at some point we'll be restricting access to ONLY sup mirrors so that they can get in reliably. Part of the problem we have now is a chicken-and-egg transition problem: Most people want to use the sup mirrors but they're often incomplete, a result of the mirror site not being able to update itself. It can't update itself because there are too many users using the primary site due to the incomplete nature of the mirrors! :-) 3. Once your site is up and passing its initial client tests, send details to myself and Justin Gibbs , the supmeister. We'll figure out what "class" of site it is (based on which collections it provides and number of simultaneous users allowed) and then send a request to David Greenman who manages the name space for freebsd.org. He'll add in a new sup.freebsd.org entry pointing to the new sup site, with the lower numbers being allocated to the higher-bandwidth servers. We're also especially interested in foreign sup sites, since they prevent an otherwise expensive and slow hop across the pond to the U.S. sites. I believe we have sup.de.freebsd.org and sup.au.freebsd.org in operation now, though there's a conspicuous lack of entries for: sup.br.freebsd.org sup.ca.freebsd.org sup.dk.freebsd.org sup.fi.freebsd.org (*) sup.fr.freebsd.org sup.hk.freebsd.org sup.jp.freebsd.org (**) sup.nl.freebsd.org sup.ru.freebsd.org sup.uk.freebsd.org * May already have nic.funet.fi, but the DNS primary for fi.freebsd.org hasn't added this. ** These folks actually need at least 2 or 3 servers to start with. You'll note that I also haven't mentioned every major country here - no offense to those countries intended! :-) I'm merely pointing out the "higher traffic" countries here and suggesting that they could most immediately benefit from having a local sup server. Finally, a note to existing sup server maintainers: I have noticed myself that sup3.freebsd.org and sup4.freebsd.org have incomplete or small collections. I think that we should try and get everyone to offer at least -stable and -current now, especially since the CVS tree has been opened up and it's actually quite easy to offer multiple collections now. Simply sup only one tree, the CVS tree, and then use it locally from cron to check out your own -stable and -current trees. You don't have to sup all 3 trees from freefall! :-) Ideally, if we could get everyone to look and work identically to sup.freebsd.org then John wouldn't have his gripes at all - it would be transparent. Ideally.. :-) Volunteers? This is your resource, constructed for your benefit, after all! :-) Jordan ------- =_aaaaaaaaaa-- From owner-freebsd-stable Mon Feb 5 16:46:30 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA12523 for stable-outgoing; Mon, 5 Feb 1996 16:46:30 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA12513 Mon, 5 Feb 1996 16:46:25 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.6.12/8.6.9) id QAA01579; Mon, 5 Feb 1996 16:43:38 -0800 From: "Steven G. Kargl" Message-Id: <199602060043.QAA01579@troutmask.apl.washington.edu> Subject: Re: sup is broken? To: julian@ref.tfs.com (Julian Elischer) Date: Mon, 5 Feb 1996 16:43:38 -0800 (PST) Cc: fenner@parc.xerox.com, jkh@time.cdrom.com, rkw@dataplex.net, kimc@w8hd.org, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199602052319.PAA26558@ref.tfs.com> from "Julian Elischer" at Feb 5, 96 03:19:20 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@FreeBSD.ORG Precedence: bulk According to Julian Elischer: > > make it so.. > >> >> In message <26947.823390500@time.cdrom.com>you write: >> >That's one option, or as I also told Kim - PLEASE DON'T USE SUP.FREEBSD.ORG >> >TO UPDATE YOURSELF! >> >> Has anyone thought of not calling it sup.freebsd.org any more? Call it >> sup-master.freebsd.org, instead, and give sup.freebsd.org 3 A records, those >> of sup1, sup2, and sup3. That way, if someone doesn't know what they are >> doing, they will get a random one of sup1, sup2 or sup3; if they know what >> they are doing they will use sup[123] directly, and it would be really >> hard to hit freefall by accident. >> >> Bill >> >> Nice idea, but you have to do more work than that. Sup3 seems to disallow the supping of the export restricted parts of the tree. My supfile works fine with sup.freebsd.org (when I can get a connection). SUP Upgrade of src-secure-stable at Mon Feb 5 16:27:51 1996 SUP Fileserver 9.13 (4.3 BSD) 7891 on lucus.fsl.orst.edu at 16:27:51 SUP Fileserver supports compression. SUP: Invalid release stable for collection src-secure SUP: Upgrade of src-secure-stable aborted at Feb 5 16:27:52 1996 SUP Upgrade of src-eBones-stable at Mon Feb 5 16:27:52 1996 SUP Fileserver 9.13 (4.3 BSD) 7892 on lucus.fsl.orst.edu at 16:27:52 SUP Fileserver supports compression. SUP: Invalid release stable for collection src-eBones SUP: Upgrade of src-eBones-stable aborted at Feb 5 16:27:52 1996 -- Steven G. Kargl | Phone: 206-685-4677 | Applied Physics Lab | Fax: 206-543-6785 | Univ. of Washington |---------------------| 1013 NE 40th St | FreeBSD 2.x-stable | Seattle, WA 98105 |---------------------| From owner-freebsd-stable Mon Feb 5 19:17:57 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA21427 for stable-outgoing; Mon, 5 Feb 1996 19:17:57 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA21421 Mon, 5 Feb 1996 19:17:53 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id TAA24389; Mon, 5 Feb 1996 19:16:12 -0800 From: "Rodney W. Grimes" Message-Id: <199602060316.TAA24389@GndRsh.aac.dev.com> Subject: Re: sup is broken? To: julian@ref.tfs.com (Julian Elischer) Date: Mon, 5 Feb 1996 19:16:12 -0800 (PST) Cc: fenner@parc.xerox.com, jkh@time.cdrom.com, rkw@dataplex.net, kimc@w8hd.org, hackers@freebsd.org, stable@freebsd.org In-Reply-To: <199602052319.PAA26558@ref.tfs.com> from "Julian Elischer" at Feb 5, 96 03:19:20 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org Precedence: bulk > > make it so.. Please do not make it so unless these things are updated in a syncronous maner, otherwise strange results could happen due to sup1 != sup2 != sup3 as far as the state of the collection. It would very likely cause src-base to come from one machine, src-bin from another, and src-eBones from the third. This could be very very evil... > > In message <26947.823390500@time.cdrom.com>you write: > > >That's one option, or as I also told Kim - PLEASE DON'T USE SUP.FREEBSD.ORG > > >TO UPDATE YOURSELF! > > > > Has anyone thought of not calling it sup.freebsd.org any more? Call it > > sup-master.freebsd.org, instead, and give sup.freebsd.org 3 A records, those > > of sup1, sup2, and sup3. That way, if someone doesn't know what they are > > doing, they will get a random one of sup1, sup2 or sup3; if they know what > > they are doing they will use sup[123] directly, and it would be really hard to > > hit freefall by accident. > > > > Bill > > > > > > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-stable Mon Feb 5 19:31:16 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA22550 for stable-outgoing; Mon, 5 Feb 1996 19:31:16 -0800 (PST) Received: from asgard.bga.com (asgard.bga.com [198.3.117.20]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA22539 Mon, 5 Feb 1996 19:31:04 -0800 (PST) Received: (from faulkner@localhost) by asgard.bga.com (8.7.3/8.7.3) id VAA00592; Mon, 5 Feb 1996 21:25:26 -0600 (CST) From: Boyd Faulkner Message-Id: <199602060325.VAA00592@asgard.bga.com> Subject: Re: sup is broken? To: davidg@Root.COM Date: Mon, 5 Feb 1996 21:25:26 -0559 (CST) Cc: julian@ref.tfs.com, fenner@parc.xerox.com, jkh@time.cdrom.com, rkw@dataplex.net, kimc@w8hd.org, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199602052348.PAA03904@Root.COM> from "David Greenman" at Feb 5, 96 03:48:38 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-stable@FreeBSD.ORG Precedence: bulk According to David Greenman: > > >make it so.. > > Not until someone goes and verifies that all of the sup*.freebsd.org > targets are working correctly. Also, my experiance with multiple A records > is that it always comes up with them same one (not random). > > -DG And hopefully, there will be some guarantee that they will update at the same time. I would hate to sup once, change servers and actually go backwards because the new server was behind the old one. Boyd > > >> > >> Has anyone thought of not calling it sup.freebsd.org any more? Call it > >> sup-master.freebsd.org, instead, and give sup.freebsd.org 3 A records, those > >> of sup1, sup2, and sup3. That way, if someone doesn't know what they are > >> doing, they will get a random one of sup1, sup2 or sup3; if they know what > >> they are doing they will use sup[123] directly, and it would be really hard to > >> hit freefall by accident. > >> -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.bga.com Him who won't, they drag." http://asgard.bga.com/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________ From owner-freebsd-stable Mon Feb 5 20:00:11 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA25036 for stable-outgoing; Mon, 5 Feb 1996 20:00:11 -0800 (PST) Received: from Aspen.Woc.Atinc.COM (aspen.woc.atinc.com [198.138.38.205]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA24873 Mon, 5 Feb 1996 19:59:58 -0800 (PST) Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id WAA15076; Mon, 5 Feb 1996 22:58:36 -0500 Date: Mon, 5 Feb 1996 22:58:35 -0500 (EST) From: "Jonathan M. Bresler" X-Sender: jmb@Aspen.Woc.Atinc.COM To: David Greenman cc: Julian Elischer , Bill Fenner , jkh@time.cdrom.com, rkw@dataplex.net, kimc@w8hd.org, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: sup is broken? In-Reply-To: <199602052348.PAA03904@Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG Precedence: bulk On Mon, 5 Feb 1996, David Greenman wrote: > >make it so.. > > Not until someone goes and verifies that all of the sup*.freebsd.org > targets are working correctly. Also, my experiance with multiple A records > is that it always comes up with them same one (not random). sup2.freebsd.org is working better than reported. when i supped from sup2.freebsd.org this evening, my local copies of the commitlogs were deleted and replaced. the rest of the src was treated normally--selected files replaced as needed. Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-stable Tue Feb 6 07:48:19 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA19358 for stable-outgoing; Tue, 6 Feb 1996 07:48:19 -0800 (PST) Received: from FSL.ORST.EDU (root@FSL.ORST.EDU [128.193.112.105]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA19353 Tue, 6 Feb 1996 07:48:17 -0800 (PST) Received: from picea.FSL.ORST.EDU (hernanw@picea.FSL.ORST.EDU [128.193.112.3]) by FSL.ORST.EDU (8.6.9/8.6.9) with ESMTP id HAA19501; Tue, 6 Feb 1996 07:48:07 -0800 Received: (from hernanw@localhost) by picea.FSL.ORST.EDU (8.6.9/8.6.9) id HAA21530; Tue, 6 Feb 1996 07:48:05 -0800 Date: Tue, 6 Feb 1996 07:48:04 -0800 (PST) From: Wayne Hernandez To: "Steven G. Kargl" cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: sup is broken? In-Reply-To: <199602060043.QAA01579@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG Precedence: bulk On Mon, 5 Feb 1996, Steven G. Kargl wrote: > SUP: Invalid release stable for collection src-secure > SUP: Invalid release stable for collection src-eBones These two directories needed hand fixing, which have now been accomplished. Please give it a try to make sure it worked. I don't have logging enabled to know what kind of traffic I'm getting, and no one has mentioned these directories being a problem until now. Wayne From owner-freebsd-stable Tue Feb 6 12:13:47 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA07362 for stable-outgoing; Tue, 6 Feb 1996 12:13:47 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA07342 Tue, 6 Feb 1996 12:13:33 -0800 (PST) Received: by Sysiphos id AA23689 (5.67b/IDA-1.5); Tue, 6 Feb 1996 21:13:10 +0100 Message-Id: <199602062013.AA23689@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Tue, 6 Feb 1996 21:13:10 +0100 In-Reply-To: "Marc G. Fournier" "FIXED: NCR problem until -stable" (Feb 3, 21:49) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: "Marc G. Fournier" Subject: Re: FIXED: NCR problem until -stable Cc: current@freebsd.org, stable@freebsd.org Sender: owner-stable@freebsd.org Precedence: bulk On Feb 3, 21:49, "Marc G. Fournier" wrote: } Subject: FIXED: NCR problem until -stable Sorry, I'm late to join in ... (We had lots of hardware problems yesterday, and I finally had taken a free weekend on last Saturday and Sunday :) } Hi... } } After figuring out that scbus wasn't a known symbol, and } looking through the ncr.c code, I recompiled the kernel using gcc } 2.6.3 instead of 2.7.2, and the system is operational again. } } That's for the lesson in DDB, since without that, I would never } have figured this out on my own. } } One stupid question though...in ncr.c, the "offending" code } was where statements like: } } #if (__FreeBSD__ >= 2) } struct scsibus_data *scbus; } #endif } } happened. Where its checking to see if __FreeBSD__ >= 2...now, } I realize that if my 2.7.2 was proper, this wouldn't happen, but since } this is 2.1-STABLE, is there a reason why those statements aren't just } changed to } } #if (__FreeBSD__) } struct scsibus_data *scbus; } #endif The NCR driver is supposed to still work under 1.1.5.1 (with a little backporting effort), and changing the condition would make this harder ... But I think I'll change it as you suggest, anyway, if there are no complaints ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-stable Tue Feb 6 12:54:28 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA10610 for stable-outgoing; Tue, 6 Feb 1996 12:54:28 -0800 (PST) Received: from scrooge.ee.swin.oz.au (scrooge.ee.swin.oz.au [136.186.4.20]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA10604 for ; Tue, 6 Feb 1996 12:54:25 -0800 (PST) Received: (from dtc@localhost) by scrooge.ee.swin.oz.au (8.6.9/8.6.9) id HAA09994 for freebsd-stable@freebsd.org; Wed, 7 Feb 1996 07:56:00 +1100 From: Douglas Thomas Crosher Message-Id: <199602062056.HAA09994@scrooge.ee.swin.oz.au> Subject: Trouble with: 'process killed due to text file modification' To: freebsd-stable@freebsd.org Date: Wed, 7 Feb 1996 07:55:59 +1100 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-stable@freebsd.org Precedence: bulk I am running a freebsd stable kernel from a sup of a few days ago and find that emacs will regularly die with the following message: Process killed due to text file modification. I find this puzzling as, when running emacs, I don't have write permission (touch will fail) and I don't have write permission to the directory in which emacs is installed. But if I check the emacs executable its modification time will have been update to around the time the process was killed. I've verified that the emacs file does not actually change, just its access time. Emacs is nfs mounted, and the server was also a freebsd-stable system, which had nothing running on it. I think I have seen this happen even for an emacs session not being used. I was running emacs in one terminal but working in another when it died. I'm not sure if its related, but I have also seen the following kernel message on the console, after which the console locked up although the machine was still active: vnode_pager_output: I/O error 5 vnode_pager_output: residual I/O 4096 at 1691648 The server is an i486DX with 8M of ram, 3c509, and 2 IDE drives; the client is a P90 with P/I-P55T4 mother board, 16M ram, NE2000 compat. card, and 2 IDE dirves. Regards Douglas Crosher From owner-freebsd-stable Tue Feb 6 14:58:05 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA20829 for stable-outgoing; Tue, 6 Feb 1996 14:58:05 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA20804 Tue, 6 Feb 1996 14:58:01 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.3/8.6.9) id OAA07912; Tue, 6 Feb 1996 14:57:37 -0800 (PST) Date: Tue, 6 Feb 1996 14:57:37 -0800 (PST) Message-Id: <199602062257.OAA07912@silvia.HIP.Berkeley.EDU> To: rkw@dataplex.net CC: jdp@polstra.com, hackers@freebsd.org, stable@freebsd.org In-reply-to: (message from Richard Wackerbarth on Mon, 5 Feb 1996 15:48:59 -0600) Subject: Re: sup is broken? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-stable@freebsd.org Precedence: bulk * From: Richard Wackerbarth * John Polstra replied: * >When I try an experiment, and that experiment attempts to delete * >220 MB of my files, I lose my thirst for adventure very quickly. * >Nevertheless, if you or somebody else can give me some clue about * >how to switch to a different sup server without losing all my * >perfectly good files, I'll try again. * * As I have pointed out, the cvs tree that I am getting from sup2 also seems * to have problems. As a result, my distribution in the name of -stable, * reflects the same condition. I saw the same thing until yesterday, except the problem seemed to have been fixed today. Satoshi From owner-freebsd-stable Tue Feb 6 18:50:25 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA07224 for stable-outgoing; Tue, 6 Feb 1996 18:50:25 -0800 (PST) Received: (from dima@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA07201 Tue, 6 Feb 1996 18:50:22 -0800 (PST) Message-Id: <199602070250.SAA07201@freefall.freebsd.org> Subject: Re: sup is broken? To: davidg@Root.COM Date: Tue, 6 Feb 1996 18:50:22 -0800 (PST) Cc: julian@ref.tfs.com, fenner@parc.xerox.com, jkh@time.cdrom.com, rkw@dataplex.net, kimc@w8hd.org, hackers@freebsd.org, stable@freebsd.org In-Reply-To: <199602052348.PAA03904@Root.COM> from "David Greenman" at Feb 5, 96 03:48:55 pm From: dima@freebsd.org (Dima Ruban) X-Class: Fast Organization: HackerDome X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-stable@freebsd.org Precedence: bulk David Greenman writes: > > >make it so.. > > Not until someone goes and verifies that all of the sup*.freebsd.org > targets are working correctly. Also, my experiance with multiple A records > is that it always comes up with them same one (not random). Not all of them ... [burka]-p1:62> telnet sup2.freebsd.org supfilesrv Trying 171.69.60.233... telnet: Unable to connect to remote host: Connection refused [burka]-p1:63> > > -DG > > David Greenman > Core Team/Principal Architect, The FreeBSD Project > -- dima From owner-freebsd-stable Wed Feb 7 11:32:37 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA21541 for stable-outgoing; Wed, 7 Feb 1996 11:32:37 -0800 (PST) Received: from iaehv.IAEhv.nl (root@iaehv.IAEhv.nl [192.87.208.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA21532 for ; Wed, 7 Feb 1996 11:32:31 -0800 (PST) Received: from oasis.IAEhv.nl by iaehv.IAEhv.nl (8.6.12/1.63) id UAA27734; Wed, 7 Feb 1996 20:32:29 +0100 X-Disclaimer: iaehv.nl is a public access UNIX system and cannot be held responsible for the opinions of its individual users. Received: by oasis (8.6.12/1.63) id UAA02075; Wed, 7 Feb 1996 20:19:56 +0100 From: volf@oasis.IAEhv.nl (Frank Volf) Message-Id: <199602071919.UAA02075@oasis> Subject: Commit documentation for stable To: freebsd-stable@freebsd.org Date: Wed, 7 Feb 1996 20:17:15 +0100 (MET) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-stable@freebsd.org Precedence: bulk Hi, Now that I have the everything setup on my system to receive the CTM patches by email, I would like to know what each of these patches is supposed to do. For FreeBSD-current you can subscribe to the cvs-* mailing lists. However, I was unable to find a list for FreeBSD-stable. How, can I get this information. Regards, Frank ---------------------------------------------------------------------------- Frank Volf - Internet Access Eindhoven - Digitale Stad Eindhoven ---------------------------------------------------------------------------- || volf@oasis.IAEhv.nl - use for personal mail || || volf@IAEhv.nl - use for Internet Access Eindhoven related mail || || volf@dse.dse.nl - use for Digital City of Eindhoven related mail || ---------------------------------------------------------------------------- IAE Public Access Unix System - Dial +31.40.2439436 and login as new. ---------------------------------------------------------------------------- From owner-freebsd-stable Wed Feb 7 13:26:16 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA28027 for stable-outgoing; Wed, 7 Feb 1996 13:26:16 -0800 (PST) Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA28019 for ; Wed, 7 Feb 1996 13:26:10 -0800 (PST) Received: from lily.csl.sri.com (lily.csl.sri.com [192.12.33.201]) by csla.csl.sri.com (8.7.3/8.7.3) with ESMTP id NAA15737 for ; Wed, 7 Feb 1996 13:25:39 -0800 (PST) Received: from localhost.csl.sri.com (localhost.csl.sri.com [127.0.0.1]) by lily.csl.sri.com (8.7.3/8.7.3) with SMTP id NAA01716 for ; Wed, 7 Feb 1996 13:25:38 -0800 (PST) Message-Id: <199602072125.NAA01716@lily.csl.sri.com> X-Authentication-Warning: lily.csl.sri.com: Host localhost.csl.sri.com [127.0.0.1] didn't use HELO protocol To: stable@freebsd.org Subject: I can crash freebsd-stable reliably Date: Wed, 07 Feb 1996 13:25:37 -0800 From: Fred Gilham Sender: owner-stable@freebsd.org Precedence: bulk After troubleshooting a problem that was bringing one of our servers down, I've made the following discovery: I can reliably crash our systems using FreeBSD-stable, 3 disks and an adaptec 2940 controller. The system is a pentium 100 with an OPTI chipset motherboard. It has 32 megs of memory. It has 3 drives. Two are Seagate 4gig hawk drives, the other is a Fujitsu 512-meg drive. (The in-use server that caused my investigation is configured similarly except it has an IBM drive instead of the Fujitsu.) We found that the in-use system would crash every night during backups (we use amanda to do backups). The system will also crash during the parallel fsck when it reboots and tries to fsck all the drives at one time. Usually it finishes one or more drives before it crashes so rebooting again will succeed, as the fsck usually only tries to do one drive. I can reliably crash the system by doing dumps of the two seagate drives at the same time. It takes less than five minutes to do this. I do dump 0sf 100000 /dev/null /dev/rsd1s1e and dump 0sf 100000 /dev/null /dev/rsd2s1e at the same time. The symptoms are that the activity light on the system goes hard on as well as the light on one of the disk drives. Also, the console message starts repeatedly reporting ahc0: target 2 lun 0 (sd2) timed out and ahc0: target 1 lun 0 (sd1) timed out After that the whole disk subsystem seems to go south. I'm using FreeBSD 2.1-STABLE on these systems (the sup is from a week or two ago). I went to this version because 2.1R was having similar problems with this setup. I was under the impression that the adaptec driver had had some changes that would help with this. I've tried using the scsi-select utility to change the speed of the scsi bus to 5mb/sec, but that doesn't cure the problem. This is a big problem for me. Can anyone help? I can supply more information or cooperate in other ways if needed. -Fred Gilham gilham@csl.sri.com From owner-freebsd-stable Wed Feb 7 15:23:42 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA06819 for stable-outgoing; Wed, 7 Feb 1996 15:23:42 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA06814 Wed, 7 Feb 1996 15:23:39 -0800 (PST) Message-Id: <199602072323.PAA06814@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Fred Gilham cc: stable@freebsd.org Subject: Re: I can crash freebsd-stable reliably In-reply-to: Your message of "Wed, 07 Feb 1996 13:25:37 PST." <199602072125.NAA01716@lily.csl.sri.com> Date: Wed, 07 Feb 1996 15:23:39 -0800 From: "Justin T. Gibbs" Sender: owner-stable@freebsd.org Precedence: bulk >I can reliably crash the system by doing dumps of the two seagate >drives at the same time. It takes less than five minutes to do this. > >The symptoms are that the activity light on the system goes hard on as >well as the light on one of the disk drives. Also, the console >message starts repeatedly reporting > >ahc0: target 2 lun 0 (sd2) timed out > >After that the whole disk subsystem seems to go south. > >I've tried using the scsi-select utility to change the speed of the >scsi bus to 5mb/sec, but that doesn't cure the problem. This sounds very much like a cableing or termination problem. Are you using internal or external periferals? Are you using active termination? How long are your cables? >-Fred Gilham gilham@csl.sri.com -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-stable Wed Feb 7 23:16:36 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA02124 for stable-outgoing; Wed, 7 Feb 1996 23:16:36 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA02084 for ; Wed, 7 Feb 1996 23:16:12 -0800 (PST) Received: from prospero.physik.fu-berlin.de (lislip.physik.fu-berlin.de [130.133.3.126]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id IAA03783 for ; Thu, 8 Feb 1996 08:15:57 +0100 (MET) Received: (from news@localhost) by prospero (8.6.12/8.6.12) id AAA01645; Thu, 8 Feb 1996 00:37:43 +0100 To: stable@FreeBSD.org Path: graichen From: graichen@omega.physik.fu-berlin.de (Thomas Graichen) Newsgroups: local.freebsd-stable Subject: Re: Commit documentation for stable Date: 7 Feb 1996 23:37:43 GMT Organization: his FreeBSD box :-) Lines: 19 Distribution: local Message-ID: <4fbd47$1id@prospero.physik.fu-berlin.de> References: <199602071919.UAA02075@oasis> NNTP-Posting-Host: localhost.physik.fu-berlin.de X-Newsreader: TIN [version 1.2 PL2] Sender: owner-stable@FreeBSD.org Precedence: bulk Frank Volf (volf@oasis.IAEhv.nl) wrote: : Hi, : Now that I have the everything setup on my system to receive the CTM patches : by email, I would like to know what each of these patches is supposed to : do. For FreeBSD-current you can subscribe to the cvs-* mailing lists. : However, I was unable to find a list for FreeBSD-stable. How, can I get : this information. the same lists :-) t -- thomas graichen graichen@mail.physik.fu-berlin.de graichen@FreeBSD.org perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away antoine de saint-exupery From owner-freebsd-stable Thu Feb 8 06:20:09 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA22508 for stable-outgoing; Thu, 8 Feb 1996 06:20:09 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA22502 Thu, 8 Feb 1996 06:20:08 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199602081420.GAA22502@freefall.freebsd.org> Subject: Re: Commit documentation for stable To: graichen@omega.physik.fu-berlin.de (Thomas Graichen) Date: Thu, 8 Feb 1996 06:20:08 -0800 (PST) Cc: stable@FreeBSD.org In-Reply-To: <4fbd47$1id@prospero.physik.fu-berlin.de> from "Thomas Graichen" at Feb 7, 96 11:37:43 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-stable@FreeBSD.org Precedence: bulk > > Frank Volf (volf@oasis.IAEhv.nl) wrote: > > : Hi, > > : Now that I have the everything setup on my system to receive the CTM patches > : by email, I would like to know what each of these patches is supposed to > : do. For FreeBSD-current you can subscribe to the cvs-* mailing lists. > : However, I was unable to find a list for FreeBSD-stable. How, can I get > : this information. subscribe to cvs-all. you will receive a copy of EVERY cvs commit(?) message. if you are interested in only a couple subsystems (eg scsi, sys), then you can subscribe to those cvs lists in place of cvs-all (the "lists" command in majordomo returns a list of all mailing lists that our majordomo supports) FreeBSD-stable is indeed a list. just subscribe to it "subscribe frebsd-stable". From owner-freebsd-stable Sat Feb 10 14:58:07 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA15477 for stable-outgoing; Sat, 10 Feb 1996 14:58:07 -0800 (PST) Received: from s1.GANet.NET (s1.GANet.NET [199.18.201.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA15470 for ; Sat, 10 Feb 1996 14:58:05 -0800 (PST) Received: (from ec0@localhost) by s1.GANet.NET (8.6.11/8.6.11) id RAA20127; Sat, 10 Feb 1996 17:57:00 -0500 Date: Sat, 10 Feb 1996 17:56:59 -0500 (EST) From: Eric Chet To: stable@freebsd.org Subject: -stable make world fails this week Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org Precedence: bulk Hello I just supped the changes for -stable this week. There were some new files in usr.sbin/sup/. A make world fails with cc -O -DVAR_TMP -DHAS_DAEMON -I/var/usr/src/usr.sbin/sup/supfilesrv -I/var/usr/src/usr.sbin/sup/supfilesrv/../lib -DRENAMELOG=\"/var/log/sup.rename\" -o supfilesrv supfilesrv.o -L/var/usr/src/usr.sbin/sup/supfilesrv/../lib/obj -lsup -lcrypt -lutil supfilesrv.o: Undefined symbol `_setproctitle' referenced from text segment *** Error code 1 Stop. *** Error code 1 Stop. Has anyone else see this problem? I did a findgrep for setproctitle I did not see it in any of the libs. -- ejc work: ejc@nasvr1.cb.att.com home: ec0@ganet.net From owner-freebsd-stable Sat Feb 10 15:39:57 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA18616 for stable-outgoing; Sat, 10 Feb 1996 15:39:57 -0800 (PST) Received: from koala.scott.net (root@koala.scott.net [204.181.147.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA18604 for ; Sat, 10 Feb 1996 15:39:53 -0800 (PST) Received: from jason.scott.net (dialup88.scott.net [205.241.3.88]) by koala.scott.net (8.7.3/8.7.3) with SMTP id RAA29213 for ; Sat, 10 Feb 1996 17:39:14 -0600 Message-ID: <311D2CC5.41C67EA6@scott.net> Date: Sat, 10 Feb 1996 17:39:49 -0600 From: Jason Gilbert X-Mailer: Mozilla 2.0 (X11; I; FreeBSD 2.1-STABLE i386) MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: -stable make world fails this week References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org Precedence: bulk I ran into it too. I just commented out supfilesrv from the Makefile in the sup directory and then make world worked. I supppose this could be bad??? Jason Eric Chet wrote: > > Hello > I just supped the changes for -stable this week. There were some > new files in usr.sbin/sup/. A make world fails with > > cc -O -DVAR_TMP -DHAS_DAEMON -I/var/usr/src/usr.sbin/sup/supfilesrv > -I/var/usr/src/usr.sbin/sup/supfilesrv/../lib > -DRENAMELOG=\"/var/log/sup.rename\" -o supfilesrv supfilesrv.o > -L/var/usr/src/usr.sbin/sup/supfilesrv/../lib/obj -lsup -lcrypt -lutil > supfilesrv.o: Undefined symbol `_setproctitle' referenced from text segment > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > Has anyone else see this problem? I did a findgrep for setproctitle > I did not see it in any of the libs. > > -- ejc > work: ejc@nasvr1.cb.att.com > home: ec0@ganet.net From owner-freebsd-stable Sat Feb 10 16:23:13 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA23898 for stable-outgoing; Sat, 10 Feb 1996 16:23:13 -0800 (PST) Received: from s1.GANet.NET (s1.GANet.NET [199.18.201.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA23889 for ; Sat, 10 Feb 1996 16:23:09 -0800 (PST) Received: (from ec0@localhost) by s1.GANet.NET (8.6.11/8.6.11) id TAA21352; Sat, 10 Feb 1996 19:22:03 -0500 Date: Sat, 10 Feb 1996 19:22:03 -0500 (EST) From: Eric Chet To: Jason Gilbert cc: stable@freebsd.org Subject: Re: -stable make world fails this week In-Reply-To: <311D2CC5.41C67EA6@scott.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org Precedence: bulk > I ran into it too. I just commented out supfilesrv from the Makefile in > the sup directory and then make world worked. I supppose this could be > bad??? > > Jason > > Eric Chet wrote: Hello Thats what I did until I could find the proper fix. ejc > > > > Hello > > I just supped the changes for -stable this week. There were some > > new files in usr.sbin/sup/. A make world fails with > > > > cc -O -DVAR_TMP -DHAS_DAEMON -I/var/usr/src/usr.sbin/sup/supfilesrv > > -I/var/usr/src/usr.sbin/sup/supfilesrv/../lib > > -DRENAMELOG=\"/var/log/sup.rename\" -o supfilesrv supfilesrv.o > > -L/var/usr/src/usr.sbin/sup/supfilesrv/../lib/obj -lsup -lcrypt -lutil > > supfilesrv.o: Undefined symbol `_setproctitle' referenced from text segment > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > Stop. > > > > Has anyone else see this problem? I did a findgrep for setproctitle > > I did not see it in any of the libs. > > > > -- ejc > > work: ejc@nasvr1.cb.att.com > > home: ec0@ganet.net > From owner-freebsd-stable Sat Feb 10 17:14:30 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA26639 for stable-outgoing; Sat, 10 Feb 1996 17:14:30 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA26634 for ; Sat, 10 Feb 1996 17:14:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id RAA29447; Sat, 10 Feb 1996 17:13:41 -0800 To: Eric Chet cc: stable@freebsd.org Subject: Re: -stable make world fails this week In-reply-to: Your message of "Sat, 10 Feb 1996 17:56:59 EST." Date: Sat, 10 Feb 1996 17:13:41 -0800 Message-ID: <29444.824001221@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org Precedence: bulk I've been trying to fix this now for a day and cannot commit the bleedin' changes to -stable that would disable setproctitle()! Any CVS gurus know what to make of this? jkh@freefall-> cvs commit cvs commit: Examining . cvs commit: Examining lib cvs commit: Examining sup cvs commit: Examining supfilesrv cvs commit: sticky tag `RELENG_2_1_0' for file `supfilesrv/supfilesrv.c' is not a branch cvs commit: Examining supscan cvs [commit aborted]: correct above errors first! Jordan > Hello > I just supped the changes for -stable this week. There were some > new files in usr.sbin/sup/. A make world fails with > > cc -O -DVAR_TMP -DHAS_DAEMON -I/var/usr/src/usr.sbin/sup/supfilesrv > -I/var/usr/src/usr.sbin/sup/supfilesrv/../lib > -DRENAMELOG=\"/var/log/sup.rename\" -o supfilesrv supfilesrv.o > -L/var/usr/src/usr.sbin/sup/supfilesrv/../lib/obj -lsup -lcrypt -lutil > supfilesrv.o: Undefined symbol `_setproctitle' referenced from text segment > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > Has anyone else see this problem? I did a findgrep for setproctitle > I did not see it in any of the libs. > > > -- ejc > work: ejc@nasvr1.cb.att.com > home: ec0@ganet.net > From owner-freebsd-stable Sat Feb 10 18:09:07 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA29581 for stable-outgoing; Sat, 10 Feb 1996 18:09:07 -0800 (PST) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA29566 for ; Sat, 10 Feb 1996 18:09:00 -0800 (PST) Received: (from kimc@localhost) by moonpie.w8hd.org (8.6.12/8.6.12) id VAA00829; Sat, 10 Feb 1996 21:08:51 -0500 Date: Sat, 10 Feb 1996 21:08:51 -0500 (EST) From: Kim Culhan To: stable@freebsd.org Subject: making devs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org Precedence: bulk How can I make all the drivers in /dev with the MAKEDEV in -stable? kim -- kimc@w8hd.org From owner-freebsd-stable Sat Feb 10 18:43:20 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA02977 for stable-outgoing; Sat, 10 Feb 1996 18:43:20 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA02972 for ; Sat, 10 Feb 1996 18:43:16 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id SAA29633; Sat, 10 Feb 1996 18:42:13 -0800 From: "Rodney W. Grimes" Message-Id: <199602110242.SAA29633@GndRsh.aac.dev.com> Subject: Re: -stable make world fails this week To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 10 Feb 1996 18:42:13 -0800 (PST) Cc: ec0@s1.GANet.NET, stable@freebsd.org In-Reply-To: <29444.824001221@time.cdrom.com> from "Jordan K. Hubbard" at Feb 10, 96 05:13:41 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org Precedence: bulk > > I've been trying to fix this now for a day and cannot commit the > bleedin' changes to -stable that would disable setproctitle()! > > Any CVS gurus know what to make of this? > > jkh@freefall-> cvs commit > cvs commit: Examining . > cvs commit: Examining lib > cvs commit: Examining sup > cvs commit: Examining supfilesrv > cvs commit: sticky tag `RELENG_2_1_0' for file `supfilesrv/supfilesrv.c' is not a branch > cvs commit: Examining supscan > cvs [commit aborted]: correct above errors first! > > Jordan Can you send me the output of: cvs status supfilesrv/supfilesrv.c > > > Hello > > I just supped the changes for -stable this week. There were some > > new files in usr.sbin/sup/. A make world fails with > > > > cc -O -DVAR_TMP -DHAS_DAEMON -I/var/usr/src/usr.sbin/sup/supfilesrv > > -I/var/usr/src/usr.sbin/sup/supfilesrv/../lib > > -DRENAMELOG=\"/var/log/sup.rename\" -o supfilesrv supfilesrv.o > > -L/var/usr/src/usr.sbin/sup/supfilesrv/../lib/obj -lsup -lcrypt -lutil > > supfilesrv.o: Undefined symbol `_setproctitle' referenced from text segment > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > Stop. > > > > Has anyone else see this problem? I did a findgrep for setproctitle > > I did not see it in any of the libs. > > > > > > -- ejc > > work: ejc@nasvr1.cb.att.com > > home: ec0@ganet.net > > > > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD