From owner-freebsd-questions Thu Apr 18 04:20:28 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA29851 for questions-outgoing; Thu, 18 Apr 1996 04:20:28 -0700 (PDT) Received: from bsd.tseinc.com (bsd.tseinc.com [199.217.203.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA29846 for ; Thu, 18 Apr 1996 04:20:25 -0700 (PDT) Received: from ws2.tseinc.com (ws2.tseinc.com [199.217.203.22]) by bsd.tseinc.com (8.7.5/8.6.12) with SMTP id GAA04048 for ; Thu, 18 Apr 1996 06:23:09 -0500 (CDT) Date: Thu, 18 Apr 1996 06:23:09 -0500 (CDT) Message-Id: <199604181123.GAA04048@bsd.tseinc.com> X-Sender: jlwest@bsd.tseinc.com X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-questions@freebsd.org From: "Jay L. West" Subject: sup problems Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I installed sup 2.0 on 2.1R and tried to use it to update to stable. Most went fine, but there were two groups that would hang up during the sup. I commented those two groups out of my supfile and tried again and all went well. I then uncommented those two and commented the rest and tried sup again (to re-try just the two that failed). Both groups locked up at exactly the same file. I don't remember which groups were causing the lockup, but I know one of them was usrsbin. I was using sup2.freebsd.org, but tried others as well. This is not a critical problem; my workaround was to get the two dirs from freebsd.org via ftp (get usrsbin.tar.Z for example) and then the make world went fine. Two questions: 1) Does anyone know why two groups would consistently lock up at the same file? 2) I want to use sup in the future, but I suspect it doesn't know that I 'went around it's back' and got the two missing dirs. Is there a way I can let sup on my end know that my end is up to date so it will just track changes from now on? Thanks in advance! Jay West