October 31st, 2004, 13:13
Looks like they are pushing rc2 out to the ftp servers today. Was really hoping for 5.3 release but i'm d/l'ing rc2 as I type. Question for you fbsd'ers in the know. Is project evil incorporated into the base build or is it something that needs to be added?

November 1st, 2004, 01:09
# cp foo.sys foo.inf /sys/modules/if_ndis
# cd /sys/modules/ndis
# make; make load
# cd /sys/modules/if_ndis
# ndiscvt -i foo.inf -s foo.sys -o ndis_driver_data.h
# make; make load

From google

November 1st, 2004, 01:10
Sorry, thanks to my great suggestion I can't edit. This should preceede that

If you have a system with one of these chipsets, please give the
NDISulator a try. Note: you do NOT have to recompile your kernel to
test it. Find the .sys and .inf files from your Windows driver media
and do the following:

November 1st, 2004, 02:30
Oh yea (ignore the tripple post) heres the release announcement:
The FreeBSD Release Engineering Team is proud to announce the
availability of FreeBSD 5.3-RC2. Two critical issues came up
during RC1 testing and it is felt the fixes warrant one more RC
so they receive widespread testing. If no more show-stopper
problems are found this will be the last test release done before

See the previous BETA and RC announcements if you are upgrading a
system and have not been keeping up with each of the test releases.
You should be aware that things like BIND and various system libraries
have been updated through the test cycle.

Fixes and enhancements since RC1:

- A situation where processes being debugged using a debugger
(e.g. gdb) could be left in an unkillable state has been fixed.
- A situation where a machine under severe network load could
stop responding for periods of time due to SACK issues has
been fixed.
- A change was made to some network locking data structures that
will prevent ABI breakage during the lifetime of 5.X. This will
require you to rebuild all modules related to the network stack.
- The ULE scheduler has been completely disabled to discourage
its use during the early phases of 5.X. The problems with its
stability are being worked on and it is hoped it can be re-enabled
for a future 5.X release.
- A problem with extremely large memory allocations on amd64 was fixed.
- Fix a panic at shutdown time for machines with vr(4).
- Update the floppy disk driver resource layout.
- Fix a problem with read-only mounting diskless client root partitions.


For people wishing to upgrade older systems using cvsup(1) and the
procedure described in src/UPDATING the CVS tag to use is RELENG_5_3
at this point.

As of this writing the following are available on
along with some of the mirror sites:

alpha: build still in progress, probably available Monday
amd64: all images available
i386: all images available
ia64: build still in progress, available later today
pc98: build complete, loading in progress, available later today
sparc64: build complete, loading in progress, available later today

MD5s for the builds that are complete at this time are:

MD5 (5.3-RC2-amd64-bootonly.iso) = 4515831861026c88a83c6077cbbcb27e
MD5 (5.3-RC2-amd64-disc1.iso) = aa55c7ce7522db445d11fcef7858227d
MD5 (5.3-RC2-amd64-disc2.iso) = 1642973ba54f9e83249c6c318df987c4
MD5 (5.3-RC2-amd64-miniinst.iso) = 676c5f1dea5a8384764277c31b7419fd

MD5 (5.3-RC2-i386-bootonly.iso) = 99dd7e92702eb43d2cf60a8f213ec0ff
MD5 (5.3-RC2-i386-miniinst.iso) = 47180529153a82855b3b5c4bfddeab74
MD5 (5.3-RC2-i386-disc2.iso) = 4ebe6dc95b61f1ee5ad511c7f0342bef
MD5 (5.3-RC2-i386-miniinst.iso) = 2792395a6e47332750a0af4ac9fb96f0

MD5 (5.3-RC2-pc98-disc2.iso) = 507436c8d00692a90beb37a9ab121db5
MD5 (5.3-RC2-pc98-miniinst.iso) = 39330e1f44bb81e032cedafe6c90ba22

MD5 (5.3-RC2-sparc64-bootonly.iso) = 5257d530c7a7fe9bea0885396d01eba1
MD5 (5.3-RC2-sparc64-disc1.iso) = fd2136eb5ad6db830fdf9cb1ae0e42fc
MD5 (5.3-RC2-sparc64-disc2.iso) = dfb05dc299712df7d1cace8f30a4c121
MD5 (5.3-RC2-sparc64-miniinst.iso) = b434d6af9af802e95a8d6273551177a1

November 1st, 2004, 11:41
I think this another RC is kinda funny since I'm running 5.3-STABLE and UPDATING already had an update for 5.3-RELEASE in it. Someone screwed up apparently.




If you need to have a screwed up post fixed, let a moderator know and they can clean it up for you. :squarewin