emaste

9 ms·

31.
by emaste 7y ago
Mostly, we still have a couple of binutils hanging around: - ld.bfd on 32-bit powerpc (should go when lld 10.0 is in FreeBSD) - GNU as on i386 and amd64 (expected by some ports, and needed to assemble one file in the base system on amd64) -
32.
by emaste 7y ago
In fact for the vast majority of FreeBSD users (those on i386 or amd64), this happened years ago. Old GCC was kept in the tree for some Tier-2/Tier-3 archs (like MIPS), and is now removed because it's no longer used for those.
33.
by emaste 7y ago
The mic doesn't work yet, actually an array of MEMS mics and needs firmware for an onboard DSP. The trackpad driver isn't yet in the tree and needs to be built separately. Overall it provides a decent experience for someone with a
34.
by emaste 7y ago
There are certainly some, but "most" is unsupported by evidence.
35.
by emaste 7y ago
I've got a Lenovo X1 Carbon 7th gen for FreeBSD development; there are many options besides ancient hardware. Buying a non-name $200 laptop isn't likely to result in a good experience, but if you're willing to do a little res
36.
by emaste 7y ago
As I've said elsewhere, that document is a combination of useful tidbits, outdated information, and unactionable (and often incorrect) commentary. As long as you can identify the useful bits and ignore the rest it might help you.
37.
by emaste 7y ago
Netflix has used Linux in EC2 for their C&C infrastructure and FreeBSD on their OCA content serving appliances since the beginning.
38.
by emaste 7y ago
What about vsyscalls?
39.
by emaste 7y ago
Exactly this. I use FreeBSD exclusively for my development, but there are a few pieces of proprietary software that are only available as Linux binaries (like FPGA toolchains), and having a viable Linux ABI layer means that I do not need to
40.
by emaste 7y ago
TLS keeps your viewing history private from third parties (e.g. your ISP).
41.
Add kernel-side support for in-kernel TLS [FreeBSD code review](reviews.freebsd.org)
2 points by emaste 7y ago|0 comments
42.
by emaste 8y ago
What's required for something to be a shell? IMO a minimal shell would have some command line editing and parser, the ability to launch applications, job control, scripting ability, and I/O redirection. These can all be done in
43.
by emaste 8y ago
This isn't about nc's pledge call, this is about the thing that might call nc. A shell that is prevented from calling socket or connect, but can exec nc, is still able to establish a network connection.
44.
by emaste 8y ago
"Towards oblivious sandboxing with Capsicum" describes a capability-aware shell: https://www.engr.mun.ca/~anderson/publications/2017/towards-...
45.
by emaste 8y ago
Al Viro's a long time Linux kernel developer with an interest in at least filesystem and related code.
46.
by emaste 9y ago
FreeBSD's patch runs red, a change we picked up from DragonFly BSD. That said OpenBSD's change to internally handle ed-style diffs is the best approach and I expect FreeBSD will migrate to that.
47.
by emaste 9y ago
I think the long-standing impression left by 5.0 (despite carrying explicit warnings about being appropriate for early adopters) carries a good lesson for us: this sort of lore is surprisingly sticky. It doesn't matter that 5.0 was ver
48.
by emaste 9y ago
> The most frustrating thing for me are the many Bugzilla entries for issues that I'm having, with patches, that are sitting there for years. For example this one https://bugs.freebsd.org/bugzilla/show_bug.cgi?i
49.
by emaste 9y ago
The FreeBSD Foundation's projects update from earlier this year has an introductory summary: https://www.freebsdfoundation.org/blog/february-2017-project...
50.
by emaste 9y ago
> It is very appropriate that you remember the 4.x days like that since that is the last time there was a long term, stable target for FreeBSD development (and investment). > Unless your organization, after wasting a year and tens of
51.
by emaste 9y ago
This is very similar to an idea introduced in FreeBSD's Capsicum sandboxing framework[1] some time ago. Google's David Drysdale proposed a patch in 2014 to add this to Linux but it didn't go anywhere; I'm hopeful that th
52.
by emaste 10y ago
Many FreeBSD utilities support a --libxo flag that produces structured output, although there isn't special handling in shells yet. % ls --libxo json {"__version": "1", "file-information": {&quot
53.
by emaste 10y ago
I ordered a pair of SD cards from a FBA Amazon seller which turned out to be counterfeit. I used Amazon's contact form to report these, and was told to just initiate a return. I think I chose "Item not as described" as the re
54.
by emaste 10y ago
Part of the reason this is feasible is that a number of dependencies were already ported to CloudABI -- from the blog post: leveldb boost (though boost::filesystem is problematic) libevent LibreSSL Ed Schouten's bl
55.
Porting Bitcoin Core to CloudABI(laanwj.github.io)
4 points by emaste 10y ago|1 comments
56.
by emaste 10y ago
I'm sorry that we seem to be talking past each other. I don't disagree with what you write, my point is only that the reproducible builds effort has no real effect on aspects of it (such as binary diversity). Of course there'
57.
by emaste 10y ago
> That's a red herring. The diversity I referred to came from compiler transformations that provably enhance security No. The work to get to a state where packages build reproducibly, in general, consists of removing timestamps, pro
58.
by emaste 10y ago
> The other problem is that making all binaries come out equal creates more of a monoculture that aids attacks on endpoints. This is a red herring, for two reasons. First, even if the build is not reproducible, the distribution produces
59.
by emaste 10y ago
There's a fairly comprehensive list at https://reproducible-builds.org/docs/ . Debian has a detailed list of reproducibility issues and affected packages at https://tests.reproducible-builds.org/deb
60.
by emaste 10y ago
> not due to morals, but due to it being the best option for themselves Indeed, and this is why the same thing happens in the BSD world. There are many examples of large and small companies, competitors, working on the same parts of Free

More ›