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 [EMAIL PROTECTED] http://www.webcom.com/richw/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
