From owner-freebsd-current Tue Sep 8 09:26:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27040 for freebsd-current-outgoing; Tue, 8 Sep 1998 09:26:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns11.rim.or.jp (ns11.rim.or.jp [202.247.130.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27017 for ; Tue, 8 Sep 1998 09:26:31 -0700 (PDT) (envelope-from masafumi@aslm.rim.or.jp) Received: from rayearth.rim.or.jp (rayearth.rim.or.jp [202.247.130.242]) by ns11.rim.or.jp (8.8.5/3.5Wpl2-ns11/RIMNET-2) with ESMTP id BAA17186; Wed, 9 Sep 1998 01:26:23 +0900 (JST) Received: (from uucp@localhost) by rayearth.rim.or.jp (8.8.5/3.5Wpl2-uucp1/RIMNET) with UUCP id BAA13677; Wed, 9 Sep 1998 01:26:23 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by mail.aslm.rim.or.jp (8.9.1/3.5Wpl3-SMTP) with ESMTP id BAA21481; Wed, 9 Sep 1998 01:21:42 +0900 (JST) To: current@FreeBSD.ORG Cc: max@wide.ad.jp Subject: any working elf snapshot available? From: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= X-Mailer: Mew version 1.92.4 on Emacs 20.2 / Mule 3.0 (MOMIJINOGA) X-PGP-Fingerprint: 00 D8 2C CA C7 75 D4 40 5C 34 39 BA A5 46 C0 CC Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980909012141L.masafumi@aslm.rim.or.jp> Date: Wed, 09 Sep 1998 01:21:41 +0900 X-Dispatcher: imput version 971024 Lines: 28 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been struggling with aout-to-elf upgrade. At the beginning, it seemed to be running ok, but as I updated my box to -current as of about 12 hours ago, it looks miserable. Actually, -current from about 80 hours ago acted oddly, but not much as it is now. So, I'm looking for snapshot of ELF system that is known to be work without problem. Here's my situation in case anyone is interested in, or hopefully can help me out. The -current as of three days ago had problem with kernel that has firewall support configured in. Once I removed it and started using LKM for that functionality, it worked fine, though. Now, the -current as of 12 hours ago doesn't even boot. Well, it does, but it doesn't stay up even for a minute. I cannot remember what exactly the panic was, but it was something like, dereferencing page that are in use. This was a case with the GENERIC kernel and it happend to me when I started vi in the single user mode. When I used mu custom kernel, which I've been using more than a few months, it didn't even get to the single user mode. I will take note what exactly all those messages are if I'm still suffering from this tomorrow. Cheers, Max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message