For bash keywords, don't look in the man page, try "help <word>".
The Bash man page does not contain a complete description of Bash, only a brief summary. "man <builtin>" provides a generic builtins page usually, since the builtins can vary between shells so one man page can't cover all of the different shell behaviors. However, bash has a "help" command which will give you the bash-specific description of a given builtin.
Other than that, I usually find the HTML Bash documentation easier to read and navigate than the info, so I just use that instead.
After ragequitting the builtins manpage, created a hack/bash script that checks the type of the command and alternates between manpage, help <cmd> or alias.
Sometimes, Googling can be a lot quicker than finding the answer in the documentation. Sometimes, the documentation does not exist. Sometimes, the documentation is wrong and Googling finds a discussion that corrects it. Sometimes, you don't actually know what documentation to start with because a system is so new to you that you don't know what you need to know.
When I answer questions on Stack Overflow/Stack Exchange, if the answer is in the documentation, I always try to link to it, while also providing a brief and clear explanation in the answer in case the documentation might be hard to interpret. I hope that helps with some of those people who don't know where to start in the documentation, or may have had trouble understanding it.
For example, in this case, the documentation is hidden away in the kernel source tree. If you don't have a kernel source checkout, you may not have this documentation available on your system at all; and even if you did, you may not think to look there. This should be documented in a man page somewhere, but there's a long list of things that should be documented in man pages which are not: https://www.kernel.org/doc/man-pages/missing_pages.html
It is a good idea to learn how to find information in common documentation sources that are available on your system. One problem is that Google frequently winds up being a better answer than local documentation because it offers a single interface to find all kinds of documentation, rather than having to learn dozens of different interfaces and places to look, only some of which are easily searchable. Off the top of my head, here are a few places that I've needed to look for documentation recently: man pages, /usr/share/doc, kernel source, perldoc, pydoc, rdoc, info, Gnome Devel Docs, and so on.
Gurus haven't always read more docs than you have. Sometimes they had to read the source. Sometimes they've just learned through trial and error, and reasoning about how stuff probably works. Sometimes they learned by word of mouth from someone else with experience. Reading the docs can definitely help; it can let you know about functionality that you've never thought to look for. But it's not the only tool for learning about a system, and how effective it is depends heavily on how thorough and good the documentation for the system is.
So, I've had a tendency to roll my eyes at the "agile" movement, and how much faith people put in it that it must be the best thing since slice bread. I've frequently said that a lot of it is just common sense, some of it is just needless process that just happens to be different, not worse or better, than traditional processes, and there are a couple of good points that agile methodologies have brought about.
But then I look at something like this, and I realize that common sense isn't necessarily so common in a big bureaucracy like this. They have tried three times to automate this, and failed each time? They've spent 7 years on one attempt, with absolutely nothing to show for it? I can't imaging going seven years without some kind of incremental release that you can use to gauge whether it's working or not.
I mean, why do they seem to think that it's necessary to solve the whole problem in one big, opaque project? You would think they could do it incrementally, automating the easiest pieces or automating one step of the process while leaving a fallback for manual processing for the more complex cases or the other steps.
The counterintuitive thing that many people don't understand about government software projects is that failure is the norm. There are relatively few "big" consultancies that win these projects, and their numbers include Oracle, IBM, Accenture, Computer Sciences Corp, SAIC, Booz-Allen Hamilton, and a few others.
Their goal in government procurements is not to deliver working software, it's just to win the contract, and then staff it with as many people as they can. We've known since The Mythical Man-Month and other books such as Peopleware that high staffing levels does not help most software projects, in fact it hurts them. But if the project fails, which most do, they all still get paid. And they will still win other contracts. Delivery of working software is just not high on the priority list--winning contracts and staffing them is.
There are all the usual problems with big software projects, and add to it that most government procurement is still based on the experience of building physical things (jet fighters, ships, highways, etc.) which really doesn't work for software.
But the big reason governments spend millions of dollars and waste years of time on software projects is because the contractors are not incented to deliver working software. In fact their incentives are to deliver failed projects, so that they can bid on them again.
Even crazier is that the government Often creates these situations by requiring that bidders bid the same number of positions, and then picks the one with the lowest rates. Lowering cost with fewer, better people just does not compute to them at all, because they have tried that strategy and been stuck with fewer just as bad people in the past. They then just use these people as staffing resources and attempt to manage the delivery themselves.
The major companies in the space (including many you listed) are trying to push incremental, iterative delivery, but the customers won't get out of their own way long enough to let it work.
I work in a state government and personally failed at least twice to consolidate agency email systems -- a slam dunk if ever there was one. We made progress... Eventually getting about 55% of the target. It went nowhere until someone had the balls to consolidate the staff along with the email.
The issue here is the same. The people examining these records need to figure out where everyone worked, who was a veteran, who is entitled to X or disqualified for Y. All of this data requires records kept by another agency, and the folks between the retirement people and the records don't really give a shit.
The difference between the private sector and government is that the people "in charge" can't change the rules. Think:
Does it make sense for people processing retirement paperwork to work in a CAVE a few hundred miles from that Capitol? No. But congress said put it there. Does it make sense to have a system so complex that you need thousands of people to figure out what to pay a retiree? No.
But at the end of the day, the political appointees come in and say "Wow, the old crew was a real bunch of muppets!" Then they try to fix a people and organizational problem with computers and consultants. Then it happens again.
> I can't imaging going seven years without some kind of incremental release that you can use to gauge whether it's working or not.
That's because you don't work for the government. For the government spending millions and years on something and have nothing or worse to show for it is completely normal. It can not go bankrupt, it can not (excluding very rare cases) be destroyed by the competition, it can only drag along. Surely, people at the top can change, but the bureaucracy only expands, and changes very little whoever is at the top. It requires very determined idealist, powerful skills and huge amount of luck to change anything there. Failure to change is routine and normal.
No, look: this is not about lack of common sense. The people in this cave -- the Office of Personnel Management or whatever -- know very well that the system they are a part of is inefficient as hell. But they also know that, if the system was automated with modern day standards, their office of 600+ people would be cut down to less than 50. Can you imagine having to lay off all those people?
In other words, resisting and rejecting modernization in this particular case demonstrates the existence of common sense, not lack of it.
The thing is, you can do that today with Apple's Mail.app, and have been able to do so for years. I sign my email using S/MIME, and while that wound up causing problems with a few outdated mail clients 5 or 10 years ago (sometimes, the fact that it was signed would make certain clients with poor MIME support show the body of the email as an attachment, which confused people), it doesn't cause much problem these days.
Cool. Still not as convenient as it could be, though. "If the intended recipient is outside the sender's Exchange environment or if the sender is not using an Exchange account, the recipient's certificate must be installed on the device."
What that means is by default any email you send would never appear "trusted" so... It's not a great marketing device. A green address bar does more to market SSL than its own advantages, sometimes. I'd argue that certificate trust -- even to say that the email address belongs to gmail.com, for instance, would do wonders to promote the technology.
Sadly, no support on Android, since apparently on Gmail everyone only emails within Google services and never for businesses? ;-) Microsoft should promote SMIME in its online Exchange offerings more, to compete with Gmail.
Wow, I love that sign! It has such a classic Soviet propaganda feel, it's appears to be entirely hand-painted despite the fact that it's offering computer courses (hand done sign lettering is a dying art in the West), and it has an awesome retro-futuristic robot!
Now I'm wondering what those dates on the bottom refer to.
The writer of the headline and of the article are often not the same person; this may be a fine article which had a poor headline attached by someone else.
At least it is the same CA, DigiCert (AFAIK). DigiCert has fairly high standards so they probably examined closely when a different org requested an EV cert for that domain. For what that's worth.
Yes, you're probably right, I just recall very clearly that they had emphasized in all of their security warnings to check for the certificate from Tibanne Co, and the current certificate is not.
Dude, it's really not hard to have a technical conversation with someone and not come off as creepy. If you feel like you have to worry about this all the time, there's something seriously off about your interpersonal instincts. I'm a pretty socially awkward nerdy guy, and I've never had a problem with being able to have a technical conversation with a woman without being accused of "mansplaining", "being overly aggressive", being "screamed about on twitter" or the like. If all of those things are happening to you, you're probably going about it wrong.
Remember, you hear about the worst incidents online. The things that make it to the news do so because they're newsworthy, not because they're commonplace.
Since many of us are socially awkward nerds here, let me give you a few hints:
Inviting someone for beers after a conference is not hitting on them. But if you're really worried it appearing that way, make sure you invite more than one person; it feels much more like an after-conference beer than an invitation to a date if there's a group of people.
Complementing someone on what they're wearing? I complement my male coworkers on their new sneakers or spiffy new jackets sometimes; it's no more creepy to do the same for a female coworker. But I wouldn't do that to some guy I just met, only someone I've known for a while and already have a professional relationship with. If the first thing I said to a guy was a complement on his shoes, that would sound a little weird, wouldn't it, like I might be hitting on him? Same rule goes. Don't make a complement on a woman's clothes or appearance be the first thing you say to her, that makes it sound like you're hitting on her. But if you've known her a while and you notice that she's gotten a new haircut or new jacket, it's not a problem to mention it.
Asking about someone's projects? How would you imagine that would sound like flirting? Just make sure you're actually interested in someone's projects, and not just using it as a "get to know you" before trying to ask them on a date.
We are literally on the exact same page. You're enumerating my point.
Inviting somebody for beers isn't hitting on them, but I have been told by women exactly why this is not okay. (In conversations like this one. This sort of "hey that's not okay" doesn't ever seem to actually come up in real life)
I agree that it's totally normal to compliment people on what they're wearing, and I, like you, do this to my coworkers all the time.
Except, again, there are lots of vocal people screaming how this is not okay.
That's my point. "Normal" human interactions are being cast as not okay by some vocal tech writers, which is what can create a mental minefield.
> Inviting somebody for beers isn't hitting on them
That's not true. It can be hitting on them, or it can not be. If you think you might be in a grey area, maybe err on the side of making it feel safer by making it a group outing rather than putting them on the spot. Don't use that doubt about the grey area as an excuse for avoiding talking to women at all, however.
> Except, again, there are lots of vocal people screaming how this is not okay.
I have never heard someone scream such a thing. Jesus, if I complimented someone and they screamed at me, I'd think they were crazy. Do people really scream about that at you?
Remember, don't confuse vocal debate on Twitter or HN with screaming. It's really not the same. People are frequently more blunt online than they are in real life. This happens in all directions. But don't act like it's the end of the world when a few people are overly vocal on the internet.
Also, don't respond to legitimate, reasonable complaints, like "I'm the technical person coming to this conference and people ignore me and talk to my fiance instead" with "well yeah, but this other thing over here blew up way out of proportion on the internet, so I can't treat you like a normal person in real life."
Yes, there is occasional overreaction that has real life consequences, like the unfortunate PyCon "dongle" incident. That's really the exception rather than the rule, however, and the real-life consequences happened in both directions. Note that many, many prominent feminist writers came out against both Adria Richard's actions and those of the the company that fired the guy making the joke.
> That's not true. It can be hitting on them, or it can not be.
Isn't that the point of many beer invites? It's a chance to socialize, and if you don't have an established relationship, it's a chance to establish one.
> If you think you might be in a grey area, maybe err on the side of making it feel safer by making it a group outing rather than putting them on the spot.
Safer?
I'm sorry, are we talking about children or adults? If someone can't manage a potentially ambiguous beer invite -- for instance, by inviting other people along themselves -- they ought to keep it to themselves and just say "no thanks"
> That's really the exception rather than the rule, however, and the real-life consequences happened in both directions.
Yes, it is the exception, but angry rhetorical baseball bats like "mansplaining" and "privilege" are being plastered all over the tech community these days, and it stops seeming like the exception.
I already feel uncomfortable attending an event that has adopted Ada Initiative-derived code of conduct, or otherwise aligned themselves with that vocal sector of the technology community.
It's clear that focus is being redirected to politics, and when people start using hostile language to describe my gender and race in broad strokes, I'm clearly in the cross-hairs for a small, vocal, and highly volatile minority; there are safer and more comfortable places for me to be.
(warning: strong, potentially triggering language contained in this post)
> I'm sorry, are we talking about children or adults? If someone can't manage a potentially ambiguous beer invite -- for instance, by inviting other people along -- they ought to keep it to themselves and just say "no thanks"
I was responding to someone who was acting as if he had to be on his toes any time he invited a woman for a beer, as if he'd be immediately be branded a sexist for ever thinking about inviting her for beer.
Yes, I'm making this sound childish, because his complaint was childish. I was giving him some advice, in case he actually believed that there was a risk of being branded a sexist for inviting someone to a beer, for how to resolve such situations that he seems to be so afraid of safely, without any potential hint of ambiguity. I was only half serious. It is fine advice if you really are so socially inept as to not know where that line is; however, I suspect that his argument was more of a strawman, built up so he could complain about some perceived wrong online, rather than an actual legitimate explanation for why he thinks that men frequently ignore women at technical conferences.
> Yes, it is the exception, but angry rhetorical baseball bats like "mansplaining" and "privilege" are being plastered all over the tech community these days, and it stops seeming like the exception.
Hm? The fact that people are bigger assholes online than they are in real life is news to you? I was pointing out that real life consequences are relatively rare, while online rhetoric can be much more heated, so your response about heated online rhetoric doesn't really contradict what I was saying.
And think about this for a minute. People who are criticizing sexism online and go over the line use such horrible "rhetorical baseball bats" as "mansplaining" and "privilege", while those who criticize perceived over-sensitivity to sexism use things like murder and rape threats: http://www.dailydot.com/news/adria-richards-fired-sendgrid-v... If you are going to complain about "rhetorical basebal bats", I think that death threats are a bit more severe than being accused of "mansplaining."
> I already feel uncomfortable attending an event that has adopted Ada Initiative-derived code of conduct
Really? This code of conduct makes you feel uncomfortable?
What part of that makes you feel uncomfortable? I think it's pretty unobjectionable.
> when people start using hostile language to describe my gender and race in broad strokes, I'm clearly in the cross-hairs for a small, vocal, and highly volatile minority
No, you really aren't in any cross hairs. Come on. Unless you are actively harassing people, or making inappropriate jokes in professional venues, there is no one who is against you or out to get you.
None of the people proposing these codes of conduct are against white men at all (I'm assuming that's the "gender and race" you are referring to, please correct me if I'm wrong); if they were, why would they be going to programming conferences in the first place, which are full of white men? What they are looking for is recognition that there are other people at the conference, who may not feel the same sense of safety as you do.
One problem is that without a code of conduct, it can be hard to know where to draw the line, or hard to adequately enforce that line as there is no written guideline for how to deal with such situations. With the code of conduct, it becomes more clear; blatantly sexual language is over the line, and it can be dealt with by expulsion from the conference. It's simple, and it lets you not worry about it; as a conference organizer, you don't have to worry about how prominent in the community someone is when they make a porn-based presentation, you can just firmly say "no."
"Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention."
That's extremely open ended, based on perception rather than objectivity, and how we got donglegate.
As for physically threatening language online -- that's not being codified as a cultural ideal.
Also, trigger warnings? Really? The amount of coddling of easily bruised egos here is mindboggling.
Every race, creed, gender, and nation has members who have seen events that are a burden on the psyche and could "trigger" on any number of imaginable things. You, however, are focused on first world, tech industry, mostly white women.
Are you going to also post trigger warnings for discussions of Soviet era politics? Lots of people lived through some pretty horrendous stuff. What about apartheid? Rwanda? Serbia? Growing up with a single parent? Childhood bullying? Poverty? Substance abuse? Where does it end? How do you even keep track of it all?
You don't. You're selfishly focused on a comparatively wealthy, privileged subgroup that apparently has nothing better to do -- despite a world filled with real problems, including sexism -- than bludgeon people for failing to highlight "triggers".
This sort of disproportionate nonsense is exactly why I can't feel safe or comfortable around your segment of the tech industry. Your sense of ethics and rectitude is skewed far outside the norm, objectively unsupportable and irrational.
> That's extremely open ended, based on perception rather than objectivity, and how we got donglegate.
You realize that the PyCon organizers talked to the attendee in question to let him know that some of his comments had cause offense and left it at that, right? It was the internet hate machine (on both sides), his employer, and her employer, who took any actions. You can't really blame the policy for what happened; as far as I can tell, the conference did everything right, it's everyone else who overreacted.
> As for threatening language online -- that's not being codified as a cultural ideal.
I have no idea what you're talking about. What are you saying is being "codified as a cultural ideal"? What are you saying isn't?
> Also, trigger warnings? Really? The amount of coddling of easily bruised egos here is mindboggling.
And yet you're so afraid that someone might accuse you of mansplaining? I can't imagine how you can complain about a thin skin while in the same breath complaining about that term. If your mind boggles at coddling, maybe you should complain about such terms being used as rhetorical baseball bats; because all you're really doing there is asking for the same coddling in return.
By the way, I had added the trigger warning when I had originally planned on actually including some of the rape and death threats in my post; I then decided against it, and to only mention them, but neglected to remove the warning.
> Every race, creed, gender, and nation has members who have seen events that are a burden on the psyche and could "trigger" on any number of imaginable things. You, however, are focused on first world, tech industry, mostly white women.
Um, we're talking about first world tech industry stuff, among a first world tech industry audience, about topics that are more likely to be sensitive for such an audience as they involve rape and death threats against members of the first world tech industry. I don't know why the fact that other groups have other triggers has anything to do with this; it's something that's generally considered polite to do in these kinds of discussions, as someone following the discussion may be someone fairly directly affected by the topics discussed.
The comments I was considering quoting are not things that I would likely repeat in person to a group of people without knowing who was around and listening, as there are some people who are more sensitive to such things than others (I've had a friend faint at a graphic description of a medical procedure before; you never know when someone will be more affected by your words than you had expected). On the internet, you can never know who will be listening, so it's polite to provide at least a warning so those people who may be affected can skip over it or prepare themselves if necessary.
> This sort of disproportionate nonsense is exactly why I can't feel safe or comfortable around your segment of the tech industry.
Exactly what makes you feel unsafe? That I'm trying to show a certain amount of respect for other people? Or that you're being asked by the code of conduct to act in a polite and professional manner? I'm not really sure how that's supposed to make you feel unsafe.
> Um, we're talking about first world tech industry stuff, among a first world tech industry audience, about topics that are more likely to be sensitive for such an audience as they involve rape and death threats against members of the first world tech industry.
So do you adjust your trigger warnings for all contexts and all people? Stay up-to-date so you can avoid the "trigger" du jour?
Or do you accept that nannying people in all contexts and all subjects is beyond any reasonable ken, and people are responsible for their own welfare?
> I have no idea what you're talking about. What are you saying is being "codified as a cultural ideal"? What are you saying isn't?
Rape and death threats are not being codified into conference codes of conduct, are not considered to be, by any rational observer, acceptable behavior, and -- let's be perfectly honest -- are not actually strong threats. Public figures receive hateful correspondence, often from unbalanced or broken people, and especially regarding more controversial topics.
That occurrence is not representative of the population at large, nor is it representative of the industry, and occurring outside the bounds of the industry and without any acceptance as part of our culture, it's certainly not relevant to the conversation other than as a footnote on the broader lack of cultural civility.
On the other hand, when members of the industry, with their name attached, with a large following, who participate in conferences by setting or helping form codes of conduct, women-only conference services, and otherwise inhabit a privileged industry position that gives them the opportunity for discrimination, use sexist, racist, and exclusionary words, terms, and language, then I'd say it's being codified in industry culture.
> On the internet, you can never know who will be listening, so it's polite to provide at least a warning so those people who may be affected can skip over it or prepare themselves if necessary.
That's ridiculous. You can never know what will be a "trigger", either, and you're myopically focused on a narrow and selfish definition.
> Exactly what makes you feel unsafe? That I'm trying to show a certain amount of respect for other people? Or that you're being asked by the code of conduct to act in a polite and professional manner? I'm not really sure how that's supposed to make you feel unsafe.
That perceived offensive is now more important than objective truth, and alone is enough to cause one to be pulled aside at a conference, lose your job, or libel a company or person publicly.
That's more than enough to be made to feel unsafe and unwelcome, and "trigger" warnings only serve to reinforce the appearance of Orwellian groupthink, with-us-or-against-us, that your position embodies.
Twisted is a pretty big dependency. The entire stack that I work on depends heavily on Twisted, and we use a lot of it, so until it's ready on Pyhon 3, it'll be hard for us to move.
We also depend on Paramiko, which is also red on the WOS.
Twisted is a bit of a bigger matter. A lot of the Python 3 tasks have been closed, but it's a pretty big beast, with lots of corners for bugs to hide in.
Erlang has Distel, which is a pretty powerful SLIME like mode: https://github.com/massemanet/distel (and written by Luke Gorrie, the same guy who wrote SLIME).
I haven't used either Distel or SLIME extensively enough to say if it's comparable, but it looks fairly similar.
The Bash man page does not contain a complete description of Bash, only a brief summary. "man <builtin>" provides a generic builtins page usually, since the builtins can vary between shells so one man page can't cover all of the different shell behaviors. However, bash has a "help" command which will give you the bash-specific description of a given builtin.
Other than that, I usually find the HTML Bash documentation easier to read and navigate than the info, so I just use that instead.
And yes, the sudoers man page is pure evil.