Ludwig Mises wrote:
This is very probable. Actually, it gets more complex than this...
No, it doesn't.
Once you 'upgraded' from -current to -release, you guaranteed that you'd
see problems that the developers don't care about. You may have any
number of such problems, all stemming from kernel, userland, and build
tools not matching each other.
At that point, I had to boot bsd.old because it simply refused to boot.
Based on the incorrect assumption that the snapshot was pre -release I
decided to download the kernel from 3.8-release and install that. The kernel
now booted but wi didn't work.
See above.
Now, after having the versions straight, I am running 3.8-release and wi is
working, after changing the #define for SIOCSWAVELAN to that which is in
3.8-current.
That's because you're not actually running 3.8-release. I'll bet quite
a bit that wi(4) works just fine in 3.8-release, *and* in the 10/14
snapshot, without anyone recompiling anything to change the #define for
SIOCSWAVELAN.
You've completely voided the reason a person might choose to run
-release or -stable instead of -current, your best bet is to use the
snapshot and not 3.8-release as built on top of the snapshot.
Sorry to have wasted your time and for not providing a proper dmesg.
Nobody wants that dmesg.
--
Matthew Weigel
