November 10th, 2011

Stupid Fedora tricks

I decided to make the F17 jump early here Chez AdamW, and just for laughs, I hereby present the following Stupid Fedora Trick:

Neverball in Shell in a VM, oh my

That’s Neverball, running inside GNOME Shell, running in a Fedora 17 VM, on a Fedora 17 host. Unstable enough for ya?!

Impressively, it’s just about playable, though the graphics are bit messed up, there’s some flickering that shouldn’t happen. Looks like about 8fps. This is using the current F17 kernel rebuilt with debugging disabled on both guest and host – it’s a lot slower with the
‘stock’ F17 kernel, as that has debugging enabled.

F17 more or less works at the moment, probably because no-one’s changed much vs. F16, though PolicyKit seems to be broken; I’m looking into that.

November 7th, 2011

do…what?

listening to the end of Dancing with the Stars before Castle came on:

“The impressive part [of tomorrow's show]…Andrea Bocelli and Flo Rida!”

*blink blink*

November 3rd, 2011

Fedora 16 is gold, but more importantly…

EDIT: A previous version of this post listed the release as 2011-11-10, it’s actually 2011-11-08, my error! We did not delay two days or anything.

So we just got done signing off on the Fedora 16 release. It’ll be going out according to the (post-Beta) schedule, on 2011-11-08. Mark your calendars! It’ll be a fun release. Huge thanks to the anaconda team, ajax, releng, and all the awesome people on the QA team – Andre, Jayson, Sandro, Athmane, John, Konrad from Oracle, and RH’s Kamil (and his merry band of interns), Tao, Hongqing, Tim, and everyone else – for the incredible effort you all put in to get this thing done, it’s utterly absurd that we made the date for this thing with all the fixing and testing that was necessary.

But never mind that! That’s not the coolest news of the day, not by a long shot. The coolest news of the day is:

GNOME Shell running in a KVM

As well as contributing one of the vital F16 fixes at one of the earlier ‘last minutes’ in the process, ajax has only been and gone and got GNOME Shell running in a KVM. Oh, hell yes.

That’s Shell running on software OpenGL, llvmpipe specifically. Still very early, but should be committed to Rawhide soon and therefore available in Fedora 17. Amazing work. As well as making it work in VMs, this should allow Shell to work on just about any system with a reasonable amount of CPU power, even if it doesn’t have hardware accelerated 3D. Almost no need for fallback mode any more!

October 25th, 2011

Random pontification: The end of work?

There’s a very interesting (if entirely wrong-headed) article over on Slashdot right now, and an even more interesting comment thread again.

It’s essentially the classic Luddite argument brought back yet again: increasingly smart automation is going to make all human employment obsolete. We’ll have robots not just to grow food and make cars but “flipping burgers, cleaning your house, approving your loan, handling your IT questions, and doing your job faster, better, and more cheaply.”

The implied questions are “will this happen?” and “will it matter?”, and the answers are “it’s been happening for centuries” and “not really, no”.

An interesting place to start with this is America in the early-to-mid-20th century, in which the Luddite argument was frequently re-framed in a positive way. Industrial automation, it was expected, would essentially kill ‘work’. People wouldn’t have to work 40 hours a week. They’d barely have to work at all. Robots would do all the work, leaving people to laze about and have fun.

Now, an interesting question: has this happened? You might, at first, be tempted to say “no”. Most people still have full-time jobs, after all.

I’d argue, however, that on a deeper level the answer is “yes”, it’s just not immediately obvious. Furthermore, it’s something that’s been happening for much longer than is often recognized; really, throughout human history.

We can just abstract the question to one of the basic attributes of humanity, one of the things we consider to define an ‘intelligent’ species: tool use. We use tools. Why? To increase the efficiency of our labor.

Let’s take the most basic, cliched example imaginable: knives. A knife’s a tool. What does it let us do? A human with a stone knife can kill an animal more easily. They can eat a dead animal, or most other types of food, more easily. They can construct shelter more easily.

So: it makes their labor more efficient.

Let’s throw 20th century political thinking back to the stone age: did the introduction of stone knives render stone age humans unemployed and lead to massive social problems? Well, no. It meant stone age humans had to spend less time and effort killing animals and cutting up food and constructing shelter. So it meant rather more of them didn’t die in inconvenient ways, and gave them a bit more time to do things like get around to inventing *more* tools.

And so we fast-forward, extremely damn quickly, to, let’s say, the middle of the last millennium or so.

Somewhere around there – it’d be interesting to pick an example society and try and pinpoint roughly where – humanity passed a kind of tipping point where the effect of our ability to increase the efficiency of our own labor changed.

Up until then, humans were still pretty much in a struggle for bare survival. As a species we had very little in the way of luxury. Inventing new tools was downright essential to enable more people to actually live full lives without dying of starvation or disease or exposure or whatever. A significant majority of the labor that most people did could be characterized as essential. Of course, no picture is perfect, and some forms of non-essential labor have been around a long time. You could argue we passed the tipping point as soon as we were able to make our labor efficient enough that human social groupings could support people who’d passed the age of practical reproductive ability. Or singers. Or, hell, prostitutes. All of which has been true for a long time.

But still, I think it’s reasonable to say this effect became far far more obvious and significant in the last few hundred years. We became so efficient at the work of growing food and building shelter and protecting ourselves from predators and so forth that it took substantially less than the total amount of potential work that all human beings could do in order to support the basic necessities of life for all human beings. We didn’t need all 500 million people on Earth, or whatever it was at that time – or, if you want to simplify to a single country, let’s say the 5 million people in England, or whatever it was – to actually support the bare necessities of life for those 5 million people.

We had, in effect, a labor surplus – we had more potential labor than we actually, strictly speaking, needed.

Not coincidentally, this is the point in history at which the Luddite argument first emerged. When you’re a stone age hunter you’re probably not really going to be worried about the consequences of some bright spark inventing the wheel; it’s not as if you’re going to wonder what you’re going to do now your ‘job’ of transporting things around agonizingly slowly and inefficiently has disappeared. It’s still pretty painfully obvious on any scale that there’s going to be Other Stuff For You To Do. Finding Stuff To Do is not going to be a problem.

It’s when we hit this situation of a labor surplus that it can start to look like a problem. Because you can look around and think, hey, there isn’t actually anything else that really needs doing, so…what now? The steam hammer came along and took my job! And on a micro scale, you’re often actually right. New inventions do take away people’s jobs.

On a macro scale, though, you’re wrong, in general. Why? Because of what human societies seem to do when they hit the labor surplus case.

It’s very interesting, and it’s where the early-20th-century American framing of the Luddite argument – no-one will have to work so hard any more! – goes slightly wrong. Because instead of adjusting things so that each person has less labor to do, it seems like what human societies end up doing is inventing more labor.

We come up with utterly non-essential things to do, and have people do those instead. And we call them ‘work’. But really, they aren’t.

Most jobs aren’t really jobs. They’re occupations. Pastimes. Professions, perhaps. So really, the future that the American robot utopians predicted has come to pass, but by stealth. Most of us do things that anyone from the past would consider recreational pursuits, but call them ‘jobs’.

For an entirely random and not-at-all-pointed example, let’s look at advertising, or TV. If you look at it in a certain way, people who ‘work’ in those fields aren’t really working at all. No-one in the entire world needs the Big Bang Theory to exist. There is no fundamental reason why hundreds of people should be paid to write, act out, film, produce, edit, promote and transmit that television show. It’s entirely non-essential labor, and what really is the difference, at a fundamental level, between ‘non-essential labor’ and ‘recreational activity’? It’s a tricky hair to split.

In case it’s not clear, I don’t really think this is a bad thing. I think it’s an interesting thing – the way people don’t seem wired to accept a world in which they ‘don’t work’, so instead of ‘not working’, we play little mind games with ourselves in order to call utterly frivolous pursuits ‘work’, so we can have people spend their whole time doing stuff that isn’t really necessary but not get mad at them for ‘not working’. Really, we’re all living in the future and have been for decades, centuries: the robots came and took almost all the really essential labor over years ago. It takes a microscopic percentage of humanity to grow our food and build our houses. All the stuff the rest of us do is just fun and games, and we’ve built a wonderfully intricate Heath Robinson device of a society to misrepresent it as ‘work’ so we don’t feel like we’re slacking off. Aren’t people amazing?

October 24th, 2011

Getting It Rite

Reading this neat guide to writing git commit messages, a random thought occurred to me which I hadn’t actually seen written down anywhere before…

I wonder how many guides to getting started in open source (whatever) include the single most important instruction I’ve ever come across, which applies to just about any action you can take in a F/OSS project?

#0: Look and see how other people do it

Want to learn to write a git commit message? Well, you can read Danni’s awesome post, but what did you do before it was there? Go find some git commit messages by established developers – ideally, the other contributors to the project you want to commit to – and see what they look like. Figure out the structure, and copy it.

This applies to _everything_. It’s almost always easier, and usually will give you a better result, to copy what everyone else does instead of trying to figure it out from first principles. Don’t stand out from the crowd! Don’t innovate! Don’t think outside the box! Don’t blaze your own trail! Copy shamelessly!

I exaggerate, of course, but remember, even the most incredible innovators are coming up with amazing new stuff 0.01% of the time, and writing git commit messages 99.99% of the time. And you really don’t want to invite an amazing new way of writing git commit messages every time you write one.

October 18th, 2011

Getting it not-quite-right

I always think it’s fun when you can catch those nearly-there-but-just-not-quite-right ideas which always look so funny ten years down the line, right when they actually happen.

Motorola’s Lapdock is an absolutely textbook example of the genre.

You can kind of see how they got there from here, after all. “Man,” they thought, “it’s a pain when you’re out working, and you get something on your cellphone that you’d like to look at on your laptop, and you pull out your laptop, and all the stuff from your cellphone just isn’t there. You have to send yourself an email or re-type the link or whatever. That’s stupid!”

They’re right. It is. Things are so much more convenient if you have the same information accessible on your phone and your laptop (and, the jump they did not make, everything else too).

Then they thought “hey, what if we just made your phone the canonical repository of all that information, and turned all your other devices into dumb shells that do nothing until you plug the Phone Brain into them?”

Well, congratulations: you just hit on exactly the wrong solution to the problem.

No-one wants the Nerve Centre of all their information to be their cellphone. That’s just silly. You don’t want a ‘laptop’ whose power is artificially limited by the battery and heat envelope of an itsy-bitsy cellphone frame. You don’t want a ‘desktop’ you have to plug your phone into for it to be any use. You don’t want to have to use a headset to take calls when your phone is powering your laptop shell. You don’t want to trust all your vital data to a $2 memory chip inside your phone and have it locked into that phone so things get very awkward when you want to upgrade. None of those things are good things.

It gets outright sad to see Motorola continue to plug away at this loser of a strategy when it’s painfully obvious that just about everyone else managed to arrive at the *right* answer: use a framework which synchronizes all that data across all your devices via this crazy thing called ‘packet data transfer’. You know, the Internet. The Cloud. And junk. Whether it’s iCloud or Firefox Sync or Google calendar/contacts/Chrome sync or whatever the hell Microsoft calls their thing, everyone else figured it out. Motorola, for some bizarre reason, continues to doggedly push at their approach which just about answers the original need but provides nothing but limitations in comparison to the other way of fixing the problem…

October 12th, 2011

Test Day time again: Eclipse Fedora packager stuff

It’s Test Day time again tomorrow (2011-10-13)! This week’s Test Day is a bit of a special interest one: it’s mostly going to be interesting to Fedora packagers. We’ll be testing the Fedora Packager for Eclipse plugin, an extensive plugin for the Eclipse IDE which turns Eclipse into an ideal environment for maintaining Fedora packages: it integrates with the Fedora git repos and the fedpkg tool to make it super-easy to branch, modify, and test build Fedora packages. So if you’re a Fedora packager or you’re learning about packaging, this could be a great event for you. If you haven’t tried this Eclipse method before it’s great fun to give it a shot – even if you don’t wind up sticking with it you’ll probably have a good time, maybe learn some tricks, and help test the environment for those who do use it full time.

As always the event will be happening on Freenode IRC in the #fedora-test-day channel, and you can use WebIRC if you’re not a regular IRC user. All the testing instructions are on the Test Day page. Please come along and help the team test and improve this great plugin!

October 12th, 2011

Oh snap

I’m generally happier working on projects which are small and sort of grassroots-y and generally held together with duct tape, which is why if you ask anyone who works with me at RH they’ll tell you I recoil instinctively whenever anyone asks me anything about RHEL (which I’ve still never actually run). But this is a fascinating dispatch from the Really Freaking Huge Code Systems side of the fence, talking about Google and Amazon architecture. Also has the best tech zinger of the decade:

“But I’ll argue that Accessibility is actually more important than Security because dialing Accessibility to zero means you have no product at all, whereas dialing Security to zero can still get you a reasonably successful product such as the Playstation Network.”

Oh, owch.

October 11th, 2011

Thanks to HP and Canonical Simple Scan team

I’d just like to say a huge thanks to HP and the folks at Canonical who work on Simple Scan – at long last, HP fixed up the ADF support for my 1212nf multifunction printer in hplip, and Simple Scan has completely awesome multiple document scanning / saving capabilities. So I can just load up a stack of pages into the ADF, run Simple Scan, and very easily turn them into a set of properly-sized PNGs on my NAS drive. This is going to help me clean up my filing cabinet no end. You folks rock! Thank you!

October 10th, 2011

Protip

If you ever find yourself looking at the four or five spam mails you get daily and wondering if SpamAssassin actually does anything any more, try rebooting your mail server and forgetting to start the SA service. When you wake up the next morning to 56 spam mails, you’ll have your answer…

 

Bad Behavior has blocked 2124 access attempts in the last 7 days.