Linked by Thom Holwerda on Fri 20th Sep 2013 17:48 UTC

There has been a lot of maturing technologies in FreeBSD 10, with many new features which make this release, I think, the most exciting one in years. A lot of development has gone into virtualisation support. Virtualisation with FreeBSD Jails has been available for a long time, but not so much "full virtualisation".

Let's have a look at the some of the most talked about, most requested and most interesting features that have found their way into or are planned for 10.0, but may not make the deadline.

Thread beginning with comment 572636
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by drcouzelis
by Drumhellar on Fri 20th Sep 2013 19:33 UTC in reply to "RE: Comment by drcouzelis"
Member since:

IOW, if you wait until 10.0 is released, you can completely ignore the ports tree and never compile anything manually again. ;)

You actually can already do this with just the standard package tools. The default package location points a repo that has the packages that are current at the time of the release (Say, 9.1-RELEASE). These don't change, and are the same versions as the ports tree that is included on the install media.

There is also a pair of other repos, 9-CURRENT and 9-STABLE, with CURRENT being cutting edge and STABLE being a bit more settled-down. Currently, CURRENT and STABLE are the same, but this isn't always the point. If you point to STABLE, you get the same versions as found in the latest ports tree, with about a week or so of lag-time.

There is a minor problem with this, though. If you were to do pkg_add -r firefox, it'd look for a package All/firefox.tbz, which would be a symlink to, say, ../www/firefox-22.tbz. If the package gets updated to firefox-22.1.tbz, the symlink sometimes isn't updated completely (or might not be for some dependencies), and pkg_add will fail. If you point to the full and actual path, though, you won't have any problems.

Of course, you might still need the bsdadmin out of ports to make upgrading easier. These can be found elsewhere, though.

But, yeah, pkgng is a huge improvement. The traditional pkg tools are slow as molasses to install/remove packages, especially a bunch of them, while pkgng is quite fast.

Reply Parent Score: 3

RE[3]: Comment by drcouzelis
by phoenix on Fri 20th Sep 2013 19:36 in reply to "RE[2]: Comment by drcouzelis"
phoenix Member since:

Except, none of those repos currently exist, due to the security incident, infrastructure shuffling, and switch to pkgng.

There are older pkg_install repos available for older releases. But nothing current. And nothing available for pkgNG.

IOW, if one wants a completely ports-tree-free, compile-free system using binary packages and pkgNG, one needs to either wait for 10.0 or use alternative repos.

Reply Parent Score: 4

RE[4]: Comment by drcouzelis
by Drumhellar on Fri 20th Sep 2013 19:46 in reply to "RE[3]: Comment by drcouzelis"
Drumhellar Member since:

The binary repos are back, and have been since May 14th.

I don't think there was ever a pkgng repo planned for 9.x, since such large changes tend to be saved for major releases. Using the regular pkg tools currently works exactly as I described.

Also, like I said, there's always the PC-BSD repos if you want stock software. If you pull KDE from the PC-BSD repo, you won't get the PC-BSD customized version - you'll get stock KDE as if you built it in ports.

Reply Parent Score: 3