From owner-freebsd-hackers Sun Apr 26 18:44:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19401 for freebsd-hackers-outgoing; Sun, 26 Apr 1998 18:42:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19136 for ; Sun, 26 Apr 1998 18:39:53 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id SAA01364; Sun, 26 Apr 1998 18:39:51 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Kaleb S. KEITHLEY" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 3.0-980311-SNAP "upgrade" post mortem In-reply-to: Your message of "Sun, 26 Apr 1998 19:46:17 EDT." <3543C749.167EB0E7@opengroup.org> Date: Sun, 26 Apr 1998 18:39:50 -0700 Message-ID: <1360.893641190@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > First I tried to upgrade, but the new snap didn't like the superblocks > in my filesystems. Nothing in any of the .TXT files warned me about > this. The only apparent solution was to newfs all my partitions. After That's bizarre - I've heard of no one else with such a problem. Are you positive it was the superblocks it didn't like? > like my file systems. They'd fsck'ed fine under the prior snap. Oh, BTW, > the new snap could mount the old / (as root_device, read-only) just > fine, but when it tried to remount it read-write then it would fail. And this was most definitely *not* the problem described in: ftp://ftp.freebsd.org/pub/FreeBSD/2.2.6-RELEASE/ERRATA.TXT ? Just making sure here before we go off on a chase. > But at boot time I get this message: > > /kernel: changing root device to wd0s3a You must have upgraded to a 3.0 SNAP that's still not entirely current. This cosmetic bogon was fixed last month sometime. > Third, on all prior releases, including the prior snap, I could set my > default route at boot in /etc/rc.network (route add default > 130.105.39.20) and it would "stick" until such time as I brought up my > ppp link. This doesn't work anymore. Should it? It is/was convenient. I don't think it should, if it's the tun0 device you're really talking about here. > Using "add default HISADDR" in the ppp.conf doesn't work either as it > tries to set it before the link is up, and that's no better than setting > it at boot. Which is why you put it in /etc/ppp/ppp.linkup Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message