From owner-freebsd-stable Wed Aug 23 11: 9:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 114C037B424 for ; Wed, 23 Aug 2000 11:09:17 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 7D27E1C76; Wed, 23 Aug 2000 14:09:16 -0400 (EDT) Date: Wed, 23 Aug 2000 14:09:16 -0400 From: Bill Fumerola To: Rich Wales Cc: freebsd-stable@freebsd.org Subject: Re: 4.1-STABLE kernel with 4.1-RELEASE userland? Message-ID: <20000823140916.X57333@jade.chc-chimes.com> References: <200008231701226.richw@wyattearp.stanford.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200008231701226.richw@wyattearp.stanford.edu>; from richw@webcom.com on Wed, Aug 23, 2000 at 11:02:46AM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 11:02:46AM -0700, Rich Wales wrote: > OK, I did a bit more research on this problem. > > The reason 4.1-RELEASE "ipfw" fails with a 4.1-STABLE kernel appears to > be because struct ip_fw (in netinet/ip_fw.h) has had two new elements > added in the middle (u_char fw_tcpopt, fw_tcpnopt). As a result, the > "setsockopt" calls in "ipfw" failed with EINVAL (invalid argument). Speaking as the guilty party, I don't think that's a problem. Read on. > I haven't tried yet to figure out why CD-ROM file systems stopped > working when I tried a 4.1-STABLE kernel with a 4.1-RELEASE userland. > When I mounted a CD on /cdrom and tried "ls /cdrom", the kernel said > "RRIP without PX field?" (isofs/cd9660/cd9660_rrip.c), and nothing > at all was visible in the /cdrom directory. When I tried to unmount > the CD, "umount" failed with an "invalid argument" message. > > I understand now that if I'm going to track -STABLE, I can't just track > the kernel. For the moment, I think I'll have to stick with -RELEASE > and wait to track -STABLE until I have time to deal with a more involved > upgrade (including being able to back it out in case something doesn't > work -- the machine in question is a semi-production system and I can't > afford to have it stay broken for long). We've never supported a different userland then kernel, so this entire e-mail is old news. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message