I think that you have made your installation attempt at an unfortunate time in the FreeBSD evolution. The FreeBSD manual is usually very good, but FreeBSD is currently transitioning to a new packaging toolkit (pkgng) and the docs are still some way from completely catching up.
Also, with the recent security issues within the project infrastructure, the binary packages are not being generated in the usual fashion and may be lagging behind. Hopefully these issues will be resolved soon.
As a regular user of Gentoo and (less so) Ubuntu, I find FreeBSD to be the most consistent and easiest to get around, particularly the packaging. But as you say, I've used it since version 3, so I'm immersed in the logic of it.
Posted Jan 3, 2013 0:42 UTC (Thu) by Lukehasnoname (subscriber, #65152)
[Link]
WOW, I typed a long response but the page crashed. Awesome.
The summary was that apt-get's tools (update, upgrade, install, remove, autoremove, purge) along with dpkg and apt-cache's search functions are a Goliath compared to BSD's pkg_add, pkg_delete, etc. tools.
Basically, apt-get was a lot more intuitive in its search assistance and its connectivity to default repos, among many other aspects.
I hope FreeBSD has looked at Debian's system for some binary package inspiration.
"The page crashed"
Posted Jan 3, 2013 0:56 UTC (Thu) by corbet (editor, #1)
[Link]
Pardon the digression, but could you fill us in as to what "the page crashed" means? We've received no crash reports here, so it wasn't a site code crash. But we don't like having people lose their work typing in comments, so I'd like to know what happened so we can maybe try to address it.
"The page crashed"
Posted Jan 10, 2013 0:06 UTC (Thu) by Lukehasnoname (subscriber, #65152)
[Link]
Sorry to mislead you, it wasn't LWN's fault.
The web proxy at work occasionally prompts for HTTP authentication erroneously, and I can't escape/hit back to my text. It takes me to a 403, and my comment is gone.
Happens on Reddit and Slashdot, too. Thanks for the concern!
"The page crashed"
Posted Jan 10, 2013 11:56 UTC (Thu) by cesarb (subscriber, #6266)
[Link]
You could try using https (https://lwn.net/). That way, you can be sure the proxy will not interfer, unless the proxy does a MITM attack on the SSL/TLS connection. If it does MITM, you have bigger problems (check the certificate to be sure; for me, it is showing as being from GeoTrust).