Sometimes I don't want to fork, e.g., if there's nothing waiting for input, e.g., the last program in a pipe.
prog |prog |exec prog
The usual way to do this is to put it in a shell script, then run the shell script. Though it would be nice in some instances, you can't run exec from a shell prompt or you'll exit the shell. I was thinking that if I'm in the kona console, executed from a parent shell, then I could type exec from the console and run programs without forking, because it's not going to cause kona to exit. Wishful thinking.
To stop forking, you would have to add an option to call execve() instead of system() in the kona source.
Interesting to read the comments. They should just rewrite the C resolver library for UNIX. Let's face it, the Plan 9^W^WGo team would probably produce a more elegant result than what we're using now, which has had its share of bugs over the years.
Has anyone read the motion (available from an economist.com server)? This what the Rolling Stone article is based on.
Is the issue whether and how GS makes money from the practice of naked short selling? Maybe the issue is that feeding the market with info about short sales that are never actually cleared (but which the market assumes will be cleared), can destroy the value of a company's stock.
Obviously if you can sell something without ever having to own or deliver it (is that really a sale?), you can do a lot of selling; and you can exert considerable influence on the market for a stock.
Maybe what happened here is a company, Overstock, believes they got screwed by naked short selling.
I need to read the motion to get a better idea of what happened.
The blog at miek.nl says that Go had a DNS library written in Go in the provided samples for a while, then they removed it.
It would be interesting to know why.
Mirror replies: That's a tough question, Nathan, because you just keep creating new ones. No single company can accumulate that much hate and they can't be easily linked to a single source. Disperse the hate. I must admit, you are one clever guy.
There are already some very good stub resolvers and resolver libraries available to users (e.g. dnsqr and the djbdns library). I have a hard time believing Google is going to do better than djb.
Of course I have no problem with them or anyone else writing another one. Have at it. The more attention brought to name resolution the better -- because it can be so easily abused for questionable purposes, it is something that deserves user oversight.
But why does Google need to place theirs _inside the browser_? That is a very curious design decision.
You are right, of course. Perhaps I momentarily forgot the context. I am reading his words on HN, not listening to them at a commencement. Big difference.
I confess I have not read Moneyball. I mistook it as the work of a baseball fan and not a metaphor for something more than an appreciation for baseball. My mistake.
Perhaps we could draw it as the difference between "would pay" and "paid".
You can put a price on something, but until someone has paid it, it seems difficult to argue that the thing is "worth" your price... to anyone. But people routinely argue this, and others believe them.
Anything that cannot boot from USB, SD card, or some externally connected media, should be approached with caution.
If you can boot from external media, then generally you can dual boot. Someone may have to show you how to prepare media for booting, but it's quite easy once you have been shown. Today's PC's all seem to have good support for booting from external media. Are we going to see this removed in ARM devices?
You do not have to shop for devices that have an "open" bootloader. You have to shop for devices that can boot from external media. (For today's PC's, that's quite easy.) If you have a device that can boot from external media, we can show how to do the rest.
prog |prog |exec prog
The usual way to do this is to put it in a shell script, then run the shell script. Though it would be nice in some instances, you can't run exec from a shell prompt or you'll exit the shell. I was thinking that if I'm in the kona console, executed from a parent shell, then I could type exec from the console and run programs without forking, because it's not going to cause kona to exit. Wishful thinking.
To stop forking, you would have to add an option to call execve() instead of system() in the kona source.