> Fuckers:
> BSD
All the shit posts about Tor and you talk BSD.
You guys are fags.
> On Sep 16, 2016, at 7:46 PM, Zenaan Harkness wrote:
>
> On Fri, Sep 16, 2016 at 02:56:11PM -0400, John Newman wrote:
>> At least you can easily build your entire user land and kernel (and
>> ports) on FreeBSD. It's very straight forward compared to Linux
>> distros
On Fri, Sep 16, 2016 at 02:29:53PM -0400, grarpamp wrote:
> Nevermind that they still [1] don't have their release iso's and everything
> else fully reproduceable and cryptographically traceable back to
> their source repository, in part because their silly choice of repo (svn)
> isn't capable of
On Fri, Sep 16, 2016 at 02:56:11PM -0400, John Newman wrote:
> At least you can easily build your entire user land and kernel (and
> ports) on FreeBSD. It's very straight forward compared to Linux
> distros (Gentoo/arch some what excluded I guess). I suppose this
> isn't much consolation if
On Fri, Sep 16, 2016 at 03:12:23PM -0400, grarpamp wrote:
> If a given port doesn't have a package, maybe invest in committing the
> build bits to your OS of choice so that it does.
Actually, I am talking about stuff out of /usr/ports. What has gotten
my system kind of fucked up is changing
On Fri, Sep 16, 2016 at 2:56 PM, John Newman wrote:
> Generally I trust that svn updates are not pulling down back doored code.
> I don't have the time (or the capacity) to read though all of /usr/src
Only about that in part, but also just taking random corrupted bits.
If
At least you can easily build your entire user land and kernel (and ports) on
FreeBSD. It's very straight forward compared to Linux distros (Gentoo/arch some
what excluded I guess). I suppose this isn't much consolation if you're
worried about the upstream svn repo itself. Generally I