Meanwhile, in São Paulo, the mayor is trying very hard to remove bike lanes already built, and are passing laws that make it a lot harder to build new ones.
398 karma · joined February 24, 2014
great to see you are including OpenSSH as part of your own OS, it's a carefully crafted piece of software that has a lot of appeal among users.
A nice follow-up is to generously contribute back to The OpenBSD Foundation. You were already a donor and, doing so, are helping further developments while being much cheaper than hiring a team all by yourself.
Thank you.
That being said, I wonder in what safe language the OS you used to write this is written.
# ifconfig iwn0 lladdr random
For those interested, the whole discussion about adding it is here [2].
[0] https://github.com/cmcaine/keyboard-api [1] https://github.com/Koushien/keyboard-shortcut-api [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1215061
It is not a license problem. Nor Mr. Tanenbaum position on "being glad" of MINIX being used on billions of x86 computers. Intel hiding code on all chips is the problem. Intel opening backdoors (maybe not intentionally, due to bugs) is the problem. Not being able to easily disable or update this code is the problem.
If it wasn't the MINIX, Intel would use something else. If there wasn't, they would write their own OS for it.
Even if you power cycle every day. If you ACPI sleep (and it works great), you I'll have to boot your machine once every 6 months, when there is a new OpenBSD release.
I would much rather "spend 30 seconds" every 6 months to boot the OS I want to run for 12 hours/day than to "save some seconds" in months to run an OS that I don't for the same amount of time.
I'm not sure people realize how much complexity you have to add to make a system boot even a couple of seconds faster. If you somehow have to diagnose a problem in a system like this, all the seconds you saved in a lifetime will be spent on a single debugging session.
It's sad they will deprecate the old extension interface and make Vimperator a no-no. I understand the reasons behind WebExtensions, specially those related to security, and reckon the benefits of the multiprocess paradigm, but the flexibility of the old extensions API was a big advantage in my pov.
No, Vimperator won't be ported (I wish it could), because WebExtensions is a much more limited API. And no, Vimium and VimFx doesn't come even close to it. They are not alternatives.
https://events.yandex.com/events/ruBSD/2013/talks/103/
I would recommend, however, watch from the beginning.
This is a misconception.
Of course that there are some wi-fi devices that require blobs, and I'm glad OpenBSD do not support these. However, I learned that no support at all is better than half support of some crap drivers.
http://www.openbsd.org/cgi-bin/man.cgi?query=arc4random&apro...