From owner-freebsd-questions@FreeBSD.ORG Thu Nov 11 02:46:16 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 87F6116A4CF; Thu, 11 Nov 2004 02:46:16 +0000 (GMT) Date: Thu, 11 Nov 2004 02:46:16 +0000 From: Kris Kennaway To: Boris Spirialitious Message-ID: <20041111024616.GD99189@hub.freebsd.org> References: <20041110222133.GC77354@hub.freebsd.org> <20041111011610.27824.qmail@web61304.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041111011610.27824.qmail@web61304.mail.yahoo.com> User-Agent: Mutt/1.4.1i cc: Kris Kennaway cc: questions@freebsd.org Subject: Re: inetd problem with 5.3-RELEASE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2004 02:46:16 -0000 On Wed, Nov 10, 2004 at 05:16:10PM -0800, Boris Spirialitious wrote: > > inetd[xxx]: unknown rpc/udp6 rpc/tcp6 > > Any modification of GENERIC from 5.3 seems to have the > > problem. I have another config that I ported from 4.x that > > works fine (with lots of stuff turned off). It must be some > > driver that has a dependency that isn't working. Note that > > INET6 is enabled. > > > > What causes this error? > > Perhaps your inetd.conf is bad; can you show it to us? > > kris > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to freebsd-questions-unsubscribe@freebsd.org > only ftp and telnet are enbled. Everything below here is disabled. Are you *absolutely certain* about this? Note that there's no mention of rpc/udp6 or rpc/tcp6 in what you posted; it does appear later on in the sample inetd.conf, but in a way that isn't a syntax error. > As I said, it works fine with a config copied from 4.x. Here is a > kernel that doesn't work. Sorry about the format, but yahoo is no > good. I don't see what could cause this in your kernel config (even in theory), but if you have a kernel that works on the same machine you could diff them to find out what it is. Kris