Date: Sun, 9 Jun 2002 22:21:37 -0400 From: "Matthew Emmerton" <matt@gsicomp.on.ca> To: <freebsd-hackers@freebsd.org> Subject: Questions about kernel/userspace backwards compatibilty between minor revisions Message-ID: <00c801c21025$8d61dab0$1200a8c0@gsicomp.on.ca>
next in thread | raw e-mail | index | archive | help
I' m working on getting OpenAFS working 100% on FreeBSD, and while reviewing the first set of my patches with the OpenAFS maintainer, some questions about kernel/userspace backwards compatibility came about. More specifically, OpenAFS was first ported on FreeBSD 4.2, and as a result, all config files (autoconf and 3 static files) are configured to look for FreeBSD 4.2. The CVS maintainer's current idea is is to duplicate all of these config files and autconf logic for FreeBSD 4.[013456]. This will add a bunch of _identical_ files to the CVS repo and add a whole lot of unneccessary autoconf checks that IMHO, are unneeded. This begs the question, is a check for FreeBSD 4.x sufficient enough from a userland perspective? What about from a kernel perspective (for kernel modules)? From my observations (I compiled the userland on 4.[236] with no problems), I think that a check for 4.x should be sufficient for userland and kernel modules, but if any kernel hacking is involved (as is done in net/arla), finer-grained checking will be required. Can anyone confirm or deny this? -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00c801c21025$8d61dab0$1200a8c0>