emaste

12 ms·

91.
by emaste 12y ago
64-bit ARM as a Tier 1 FreeBSD architecture is on the roadmap. 32-bit ARM will get there too, I think, bit it's not being pushed as aggressively.
92.
by emaste 12y ago
From https://openconnect.itp.netflix.com/software/index.html : For the operating system, we use FreeBSD version 10. This was selected for its balance of stability and features, a strong development community and staff e
93.
by emaste 12y ago
It is very good that the bug was found and fixed in -CURRENT, but it's also important not to be dismissive of the issue. It is unfortunate that some recent posters are clearly confusing -CURRENT with the stable branch from which releas
94.
by emaste 12y ago
I can understand the terminology may be confusing to someone new to FreeBSD, but the handbook clearly documents the meaning of -CURRENT and -STABLE, and explains that -CURRENT is the "bleeding edge" of FreeBSD development.
95.
by emaste 12y ago
A lot of non-Free software also disallows redistribution, so it's not permissible to put it in the binary repository. It's possible that free but not Free (e.g., zero-cost binary-only software) software could be included in the re
96.
by emaste 12y ago
I agree that this is much worse than a crash if you care about your keys, and I'm not trying to suggest otherwise. My point is that -CURRENT may be rather unstable at any given time, and is explicitly not supported. One should not be u
97.
by emaste 12y ago
There's a lot of public evidence of NetFlix's use of FreeBSD and their desire to generally stay up-to-date. I'm not aware of any credible statement that they're actually on -CURRENT though, and even if they were at some
98.
by emaste 12y ago
Or as Juli Mallett put it on Twitter, "If you can deal with FreeBSD -CURRENT crashing, you can deal with the RNG being b0rked for a few months." This is indeed a serious issue, and I'm disappointed it was in the source tree f
99.
by emaste 12y ago
This is a very good point, one that I missed in my followup on the FreeBSD-CURRENT mailing list. See also https://www.imperialviolet.org/2013/06/15/suddendeathentropy...
100.
by emaste 12y ago
There is much less entropy than there should be, but more than none.
101.
by emaste 12y ago
Note that this is FreeBSD-CURRENT only, i.e. the development branch. This does not affect FreeBSD releases.
102.
Is LLDB a threat to GDB's success?(sourceware.org)
4 points by emaste 12y ago|0 comments
103.
by emaste 12y ago
In the case of drivers, a lot depends on the specific hardware. Some drivers are written by employees of the hardware manufacturer, some are written by employees of companies using FreeBSD, and some are written by interested volunteers. Har
104.
by emaste 12y ago
Spacing major releases out by five years doesn't guarantee that the bug fixes and driver updates you want will make it into the stable release. It's completely plausible that volunteers will instead develop on HEAD and commit thei
105.
Changes to the FreeBSD Support Model(lists.freebsd.org)
66 points by emaste 12y ago|40 comments
106.
by emaste 12y ago
This change was written by Landon Fuller, one of the founders of MacPorts. There's an explanation for it in a comment on the pull request: https://github.com/freebsd/pkg/pull/1113#issuecomment-680639...
107.
Baseline Mac OS X Support merged into FreeBSD package manager(github.com)
229 points by emaste 12y ago|59 comments
108.
Get started with FreeBSD: A brief intro for Linux users(infoworld.com)
14 points by emaste 12y ago|1 comments
109.
by emaste 12y ago
To date the FreeBSD Project has benefited from the generosity of a number of users of FreeBSD who donate data center space and connectivity. Some examples are Yahoo!, NYI, ISC, and Sentex. The point about the need for and value of marketing
110.
by emaste 12y ago
The Foundation's financials are open, so you can see how the money has been used in the past. The short version is that our 2014 budget was on track to spend about half that amount (i.e., approaching half a million) on funded project d
111.
by emaste 12y ago
The main issues are: * Does not work with certain hardware / UEFI firmware implementations (due to bugs in either our implementation, or the firmware). * No support for UEFI nvram variables. * No integration or documentatio
112.
by emaste 12y ago
The actual release announcement itself is here: https://lists.freebsd.org/pipermail/freebsd-announce/2014-No...
113.
by emaste 12y ago
You can use the memstick image to boot and check hardware without installing.
114.
by emaste 12y ago
I don't follow; fixes making it only into -CURRENT is certainly an issue, but slowing down the major release cadence will make it take even longer for those to reach you. Ensuring fixes make it into release branches is something we nee
115.
by emaste 12y ago
That is the 10.0 release announcement. The directory linked here is not-yet-released 10.1. As always, until the release announcement comes out, the release is not done. Until that time, there's always a possibility the release builds w
116.
by emaste 12y ago
FreeBSD has made great strides in the last couple of years with binary package management tools. While there are a few things still to be done, in general if you're familiar with Debian you'll be right at home. Have a look at htt
117.
by emaste 12y ago
The hwpmc support Brendan's using here is in stock FreeBSD, but the default callchain capture depth is only 8 frames in FreeBSD 10.0, so you'd want to set in loader.conf: kern.hwpmc.callchaindepth=32 The default is 32 in FreeBSD-C
118.
Catching Your CPUs Napping(brendangregg.com)
28 points by emaste 12y ago|1 comments
119.
FreeBSD July-September 2014 Status Update(freebsd.org)
6 points by emaste 12y ago|0 comments
120.
by emaste 12y ago
This investigation starts from the tested in the DragonFly report. You can see the shape of the red line in the graph on page 13 ("stock") is equivalent to the DragonFly report.

More ›