968 karma · joined July 20, 2013
That seems like it would be the easiest thing for them to get working out of all the wireless stuff, did you report that issue to them?
block in on egress proto tcp to port { 25, 80 }Unfortunately you may need to just try a few and see who you click with. It's not uncommon to do a preliminary session with one and either they decide to refer you to someone else (based on your situation) or you just don't like them. This is why it's hard to go by reviews from other patients.
The CVS that OpenBSD uses is still GNU CVS - https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/gnu/usr.bin/cv...
The irony of course is that this was posted on a mailing list (so clicks are meaningless) by a developer of free software who has to spend his time working around these bugs that Intel caused. He has every right to be outraged and vent all he wants. He is actually doing the hard work while you watch kitten videos and chuckle-memes.
http://en.community.dell.com/techcenter/os-applications/f/46...
A motherboard change and a BIOS update (2.4.2) are supposed to lower the noise as much as they can, while still deeming it "working within specification". Users report the 2.4.2 update didn't help much or even made it worse.
I guess one of these HN-comment-e-mailing websites needs to apply to YC to actually have a chance of getting integrated into the site.
> I don't like the closed culture
What good is an "open" culture if you can't patch things yourself anyway?
I wonder if or when Rails will settle down and stop changing everything between major releases causing all documentation to be out of date, gems to break, developer habits to break, etc. Not to mention all of the related tooling like Bundler which seems to spit out new and uninteresting warnings and errors every time I update it.
It would be great to be able to write an application using a framework and not have to constantly change the application just to get long-term updates to the framework like bug fixes, security patches, compatibility with new versions of Ruby, etc.
Basically Rails-LTS but not from a 3rd-party (and embraced by the ecosystem).