From owner-freebsd-questions Sat Oct 25 22:27:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA18872 for questions-outgoing; Sat, 25 Oct 1997 22:27:54 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA18865 for ; Sat, 25 Oct 1997 22:27:48 -0700 (PDT) (envelope-from font@Jupiter.Mcs.Net) Received: from Jupiter.Mcs.Net (font@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id AAA15635; Sun, 26 Oct 1997 00:27:47 -0500 (CDT) Received: from localhost (font@localhost) by Jupiter.Mcs.Net (8.8.7/8.8.2) with SMTP id AAA24995; Sun, 26 Oct 1997 00:27:47 -0500 (CDT) Date: Sun, 26 Oct 1997 00:27:46 -0500 (CDT) From: Font To: Doug White cc: questions@FreeBSD.ORG Subject: Re: option NETATALK in 2.2.5R In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I double-checked the kernel config file I used that generated the odd unbootable kernel, and found nothing unexpected. Running it through /usr/sbin/config and making it a third time resulted in a usable kernel. It's possible that something very strange happened, because I no longer can repeat the problem (which only happened twice). So I concede it could be one of the top two problems: operator error or hardware malfunction. Yike on me. Bully for FreeBSD! If it happens again, I'll try it on a different machine for verification before posting! A bug in my MUA causes news.announce.newusers font to be sent to beneficiaries and senders of UCE/SPAM. @ mcs.net Wishes are like dishes. On Fri, 24 Oct 1997, Doug White wrote: > Date: Fri, 24 Oct 1997 22:13:22 -0700 (PDT) > From: Doug White > Reply-To: Doug White > To: Font > Cc: questions@FreeBSD.ORG > Subject: Re: option NETATALK in 2.2.5R > > On Fri, 24 Oct 1997, Font wrote: > > > FYI: > > > > I added "option NETATALK" to a kernel configuration file that, aside from > > having a number of network and disk devices commented out, was > > substantially unchanged from GENERIC. This resulted in a kernel file that > > was 2512988 bytes, a much larger number than was expected (GENERIC is > > 1457189). This resulting kernel file hung as soon as the kernel was > > loaded (it never got to process -c flags). I haven't yet compiled the > > netatalk software itself on this system (P200, 32M, 3C509, wd0 only). > > I can't say I'm having the same problem. I'm running a well changed > GENERIC with NETATALK. > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > >