Not quite. The UNIX wars were basically "Hardware" wars. Basically, you bought your workstation from Sun, or HP, or SGI, or IBM or whoever, and you got the version of UNIX that was shipped for that hardware. You could compile your own BSD (/usr/ucb) or GNU (/usr/local) utils if you didn't want to pay a king's ransom for a compiler, but basically, the idea of running any type of software on any hardware, a la Linux or OpenBSD, hadn't really caught on.
I know it's cool to be all blase about this, but this is different.
the kid's dad was right. I've done construction, drywalling, welding, and even retail. It is HARD. Your whole body aches at the end of every day, you become prematurely aged with injuries to your knees, and your back, and your elbows. Yes, I've put on nearly 100lbs, and I sit in front of a computer all day, but I'd rather do that than wear out my body and dull my mind by putting together fiddly bits on an assembly line all day
rpm, dpkg, windows MSI file, .App folder on Mac. These will all work with any language that you want, plus, you get the added benefit of standardized placement and having the USERS of each platform know what to expect when they install whatever you've decided to throw on their machine.
This is actually a list of obscure (20 years of Linux use here, and I haven't heard of most of them) command-line utilities. Definitely going to explore calcurse
yes, well, mostly. python has subprocess.Popen which is an awesome way to call out shell cmds, but I do most of my SA work in ruby. I just find it more pleasant to write.
Some of us remember learning to program before SO existed. Hell, when I started to learn to program the WWW was still pretty new, and still looked on as something of a fad. You had to read books, and man pages to figure anything out.
Interestingly, I worked there when there were 4 engineers. They had most of the product worked out back then. The Pandora website the last time I checked is not terribly functionally different from the internal Savage Beast website from 2001. Pick a song, and it generates a playlist based on that song. The barriers were legal and monetary, more than technical.
I remember working at an Optical Networking startup in Ottawa, where my boss, in particular, was extremely passionate, and believed deeply in the company, and consequently worked weekends and 18 - 20 hour days regularly. The company never got a customer, and went bankrupt. My boss got laid off with everyone else.
They still provide all the sources, as well as easy means to build them ( a source rpm ). This is far more than what the GPL requires them to do. What they don't distribute is the srpm with all of the patches neatly broken out by bug number and CVE (if applicable).
It makes it harder to figure out what sources came from RH, and what are vanilla kernel sources, but there's nothing in the GPL that says you have to detail the provenance of every line of source code distributed
Mostly it's a matter of picking your poison. dpkg allows some things that RPM doesn't, and vice-versa. dpkg does have some nice features (well, features I can't remember, except for I went "Ooo, I want rpm to have that" when I saw it)
One thing that dpkg has that really annoys the hell out of me is allowing for user input during the transaction. It makes unattended upgrades impossible
That is the exact same argument that KK was making in that Wired piece.
Quote:
How many times in the history of mankind have we wired the planet to create a single marketplace? How often have entirely new channels of commerce been created by digital technology? When has money itself been transformed into thousands of instruments of investment? It may be that at this particular moment in our history, the convergence of a demographic peak, a new global marketplace, vast technological opportunities, and financial revolution will unleash two uninterrupted decades of growth.
Oddly enough, that's exactly what people were saying last time there was a tech bubble. "This isn't a bubble, it's a paradigm shift!" See http://www.wired.com/wired/archive/7.09/zeros.html for kk's version of this post from Sept. 99, only months before the bubble burst. Also about when I stopped reading Wired.
In 1995 lots of people cared, Me, for one. And it was nice when companies like SGI and Sun put real care and thought into the design of their workstations. I could never afford one for myself, but I ooh-ed and aah-ed whenever I got to work on one of those fantastic machines. I guess it took Apple to notice that a well designed computer at a good price point would sell well enough to make it worth it
OpenSSH 4.3 is likely the most popular because it is the version that comes with (redhat|centos|scientific|oracle) linux 5. It's still widely in use. 4.3 had a lot of bugs, but redhat has been backporting fixes to it since it came out.
This is funny
HN headline: google is changing its logo
Source Headline: Is google changing its logo?
Source conclusion: No, google is not changing its logo.
umm, iptables is a part of the kernel, and is exactly the same, regardless of distribution. I've used a bunch of different distros and iptables is always the same. What is this guy talking about??