251–260 of 415 posts
Earlier quoted context omitted.
Thanks, just donated, I use openssh every day so it just makes sense.
[scott_s@local ~] history | wc -l 500 [scott_s@local ~] history | grep ssh | wc -l 191 Donated.
> The OpenBSD project uses a lot of electricity for running the > development and build machines. A number of logistical reasons > prevents us from moving the machines to another location which might > offer space/power for free, so let's not allow the conversation to go > that way. I don't understand this comment. If the choice came down to moving versus shutting down entirely, why is moving an unacceptable answer?
> why is moving an unacceptable answer It seems likely that they don't trust anyone else to have physical access to the machines for security reasons. Their threat model probably includes national governments.
Earlier quoted context omitted.
A somewhat related note about branding. My first "real" job was in the mid-90's; I was the first technical hire at a small Chicago ISP (EnterAct) that grew into a relatively large ISP (when I left, we were default-free peered to several tier-1 providers and had more POPs than I can name). It was great, and the team that started it --- two Big-5 accounting firm programmers --- was inspiring, particularly when it came…
I know OpenBSD's reputation is primarily security, but I use it for a different reason. It's simple, stable, and doesn't break. Back when I was in high school and I had a lot of free time and all that, the various incarnations of Linux were a delight. Even after that, I still went with it out of inertia and spent many evenings tweaking Gentoo. I eventually just goddamn gave up. I got sick of every upgrade breaking so…
In 2009, our development team lost a whole 10 hours to a degraded Linux mdadm RAID1 that wouldn't rebuild due to an obscure error after a digger severed our power and internet connection. No internet access as power came up first so no access to online help. mdadm is buggy. Documentation sucks. Error messages suck. Only recourse was a full restore from tape which took a long time. This was the last straw after over a decade of dealing with this crap from network dropouts, laziness, half-arsed features, distro wars, politics and churn.
Some previous Unix experience in the late 1990s with OpenBSD on an old SparcStation 5 (the only thing that would run on that machine nicely) jumped into my mind on the way home. It had that warm, fuzzy, well-engineered, well-documented feeling about it, like an old HP RPN calculator. Got home, downloaded it and installed it on my laptop, replacing Ubuntu.
4 years down the line: one happy person with the same laptop running 5.4 still with that warm, fuzzy, well-engineered, well-documented feeling.
Not once has it let me down. Not for a minute in the 4000+ hours I've been using it. It just works.
Earlier quoted context omitted.
> why is moving an unacceptable answer It seems likely that they don't trust anyone else to have physical access to the machines for security reasons. Their threat model probably includes national governments.
A somewhat related note about branding. My first "real" job was in the mid-90's; I was the first technical hire at a small Chicago ISP (EnterAct) that grew into a relatively large ISP (when I left, we were default-free peered to several tier-1 providers and had more POPs than I can name). It was great, and the team that started it --- two Big-5 accounting firm programmers --- was inspiring, particularly when it came…
Earlier quoted context omitted.
Seriously? What's not to understand? He said they had reasons that prevent them from moving and didn't want to discuss it further. Why push it? Isn't he in a better position to decide what's unacceptable than you are?
If I'm donating I would like to know exactly where the money is going, and what options have already been explored. OpenBSD should have referenced, full documentation about these things if they want to maximize donations. Apparently, there isn't very much documentation/open accounting, and they aren't willing to discuss options to reduce the bill. That doesn't inspire confidence.
So your feeling is similar to that toward a homeless dude? You'll give him a sandwich but not cash? If they're saying power is the shortfall, maybe we just need to buy them some solar panels or wind generators or something.
Earlier quoted context omitted.
Correction: OpenSSH, not SSH at all.
Name another free ssh implementation. On every* UNIX and UNIX-like OS ssh is OpenSSH. OpenSSH is why we don't telnet everywhere anymore. *- Honestly, I don't know of anything that ships with something that is not OpenSSH.
Earlier quoted context omitted.
Yes, that's an important point. The Linux manpages are a joke, they're half useless almost all the time.
The most offensive man pages are GNU project pages that effectively say, "for real documentation read the info page". Which, as someone that can never remember how to use info, is frustrating and just serves to piss me off...my first thought is "and a big fuck you to you, too". And then I look it up online so I don't have to read how to use info before I can read how to use the command I was looking for docs on. I do…
Earlier quoted context omitted.
The most offensive man pages are GNU project pages that effectively say, "for real documentation read the info page". Which, as someone that can never remember how to use info, is frustrating and just serves to piss me off...my first thought is "and a big fuck you to you, too". And then I look it up online so I don't have to read how to use info before I can read how to use the command I was looking for docs on. I do…
Info pages are hypertext, and because of that they are better suited for a complete manual for a complex program than man pages. But we have other hypertext formats available. It'd be better if GNU started using some format that everybody already usees and knows how to write.
If you need a complex manual for a complex program, something is wrong.
Earlier quoted context omitted.
[scott_s@local ~] history | wc -l 500 [scott_s@local ~] history | grep ssh | wc -l 191 Donated.
The shell history really ought to have some sort of de-dupe feature. Too many lines of history get taken up by duplicate entries!