cnst

30 ms·

361.
by cnst 6y ago
> https://marc.info/?l=openbsd-bugs&m=124425104531501&w=2 Love it! No conversation about SUS is complete without Theo bashing up the absurdity of some historic bugs being documented as features. :-) --- I do lik
362.
by cnst 6y ago
Exactly! It's so upsetting that the narrative has been so distorted that most folk don't even understand that it's not the manufacturer that intentionally makes the device unusable, but instead the website operators, and tho
363.
by cnst 6y ago
> The issue here is not due to Let's Encrypt, it's due to these devices, like so many others, not being designed to be maintained for the long term. How so? Is www.google.com or www.bing.com doesn't work on those devices?
364.
by cnst 6y ago
> Apple devices have the same issue. Let's be real here -- is this a problem with the device, or with site operators? All the major players that promote TLSv1.2 -- Mozilla, Microsoft, Google -- serve their websites over TLSv1.0 just
365.
by cnst 6y ago
Which exact projects do you have in mind? Because none of the issues you identify seem to apply to the BSDs. We don't really have the notion of "maintainers", either, so, I'm guessing your comments aren't as a BSD
366.
by cnst 6y ago
What's wrong with mailing lists? Is there anything better for general discussion than the mailing lists? The problem with forums is that you can't really trust them. They're generally not archived well, UI is poor, editing o
367.
by cnst 6y ago
Isn't the reason for the problem is that multiple branches and tags may have any given commit? Same as in CVS? It seems like the problem is the UI that assumes that only a single branch may have any given commit. --- BTW, whilst at i
368.
by cnst 6y ago
To add to that: learn how to use git-reflog. It's the most fantastic thing ever, let's you have a complete control over the local revision history to undo anything you want. I think Git is a real pleasure to use. Personally, wi
369.
by cnst 6y ago
Prior discussion from a week ago: https://news.ycombinator.com/item?id=25460544 I'm glad it's finally been done! Looks like GitHub still has the old export as of 2020-12-24T15:30Z, but 5ef5f51d2 dated 2020-12-23T0
370.
by cnst 6y ago
Which ones? DragonFly BSD has transitioned from CVS directly into Git back in 2008. OpenBSD probably has no plans to transition. NetBSD has been testing Fossil, Git, Mercurial, for about over a decade now, yet somehow as of 2020 the sight
371.
FreeBSD src repository has transitioned from Subversion to Git(cgit.freebsd.org)
123 points by cnst 6y ago|58 comments
372.
by cnst 6y ago
Wow, that makes it even more hilarious! :-)
373.
by cnst 6y ago
> The story was introduced in 1968 by the New York Times picking up on the NEJM article. And I think that's ultimately the culprit for this hoax. Just because a reporter at a NYTimes lacks the most basic scientific knowledge to unde
374.
by cnst 6y ago
It wasn't a trader who didn't know the price could go negative, it was a passive retail investor: https://archive.is/33zf6#selection-3201.1-3205.1 >>>> “It didn’t occur to us” oil could go negative, A
375.
by cnst 6y ago
I can't imagine that OpenBSD's got has anything to do with FreeBSD's transition. Replacing GPL'ed Git with a BSD alternative sounds interesting -- if not for anything else, then simply to combat the monoculture -- but as
376.
by cnst 6y ago
NetBSD has been exporting into Fossil since 2011, it's really nice; in fact, the export into GitHub Git is done through an intermediary read-only Fossil repository: http://wiki.netbsd.org/github/ https:/&#x2
377.
by cnst 6y ago
Is it really the improvements, though, or is just that Git has less resistance now in 2020 than it did in 2008? DragonFly BSD has a smaller src, but it's been using Git since November 2008, converting away from CVS directly into Git, o
378.
by cnst 6y ago
FWIIW, Matthew Dillon has converted DragonFly BSD from CVS directly into Git back in 2008, or, more specifically, on 2008-11-26: https://leaf.dragonflybsd.org/mailarchive/commits/2008-11/ms... It would appear
379.
by cnst 6y ago
Almost hard to believe it's finally happening! Couldn't we have gone with Git all along, without Subversion as an intermediary step for about a decade? Anyhow, per https://wiki.freebsd.org/git , looks like GitHub&
380.
FreeBSD src repository is transitioning from Subversion to Git this weekend(lists.freebsd.org)
212 points by cnst 6y ago|74 comments
381.
by cnst 6y ago
I think this part is particularly interesting: > Note: The OpenSSL project has published publicly available patches for versions included in FreeBSD 12.x. This vulnerability is also known to affect OpenSSL versions included in FreeBSD 1
382.
OpenSSL NULL pointer de-reference (CVE-2020-1971)(lists.freebsd.org)
3 points by cnst 6y ago|2 comments
383.
by cnst 6y ago
Anyone's using this in production? Or any other unikernels? tl;dr: a unikernel means there's no standard OS other than the runtime execution environment specifically just for Golang in this instance; which means it should be much
384.
by cnst 6y ago
That's unexpected and mysterious! Any reason a question couldn't be fielded in public at HN? :-)
385.
by cnst 6y ago
Mozilla the last to learn they need a lobbyist in Washington?
386.
by cnst 6y ago
That's basically what most of these "security" solutions are really all about -- about disrespecting your privacy, having no regard for inclusivity, CPU time and user time. It's kind of sad that they've taken over t
387.
by cnst 6y ago
> Most sites are not transacting currency or private information. > Almost all sites should be HTTP and HTTPS. This. Most people aren't even aware that Google.com is still both HTTP and HTTPS; you can easily test with curl or ly
388.
by cnst 6y ago
> It also uses High-Performance graphics for whatever reason when connected and can completely drain a full MacBook Pro battery in under an hour. Disconnecting does not free the GPU. Which is ultimately a bug, or a missing feature, in M
389.
by cnst 6y ago
Time flies. I still remember starting with OpenBSD in early noughties, I think 3.5 and 3.6 in 2004, which seemed like a mature and exciting project at that time already; fast-forward 2020, and it's amazing how far we've come. Gr
390.
by cnst 6y ago
This is really a problem with the US banking system as a whole, the check-prevalent culture where people are still willing to deal with such ancient financial instruments, plus the US society where people live paycheck-to-paycheck. When you

More ›