From owner-freebsd-stable Wed Aug 23 11: 3: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.66.63.23]) by hub.freebsd.org (Postfix) with ESMTP id 1393037B422 for ; Wed, 23 Aug 2000 11:03:01 -0700 (PDT) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id LAA03481; Wed, 23 Aug 2000 11:02:46 -0700 (PDT) (envelope-from richw) Date: Wed, 23 Aug 2000 11:02:46 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: Re: 4.1-STABLE kernel with 4.1-RELEASE userland? Message-ID: <200008231701226.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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). 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). Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message