Search Results: "ag"

12 January 2007

Ian Murdock: Babies, bath water and open platforms

Steve Jobs: “You don t want your phone to be an open platform.” More Steve Jobs: “These are devices that need to work, and you can t do that if you load any software on them. That doesn t mean there s not going to be software to buy that you can load on them coming from us. It doesn t mean we have to write it all, but it means it has to be more of a controlled environment.” It’s widely understood that Microsoft beat Apple in the PC game because Apple was a tightly integrated, closed platform, whereas Microsoft was an open ecosystem where anyone could play (albeit at their own peril). Clearly, the strategy has not adapted well to digital media players. Why? Because people are tired of products that don’t work. Anyone who has ever had to glue a PC back together for a family member knows what I mean. Does “open” have to mean “poorly integrated” though? Clearly, I don’t think so, given how much I’ve invested in Linux over the years and how much I’m investing in the LSB now. And the job the distributions do in the Linux world is nothing short of amazing, if you think about it—taking thousands of moving parts written by thousands of different people and crafting them into what appears, for the most part, to be an orchestrated whole. Personal experience bears this out too—it’s not that the entire Windows Media ecosystem produces bad products (iTunes pales in comparison to Rhapsody), it’s that the integration points are extremely fragile (e.g., I tried Rhapsody To Go with a Plays For Sure device, which was an awful experience). In other words, just like a chain, an open ecosystem is only as strong as its weakest link, because it’s the links where things break. Sure, there are bad products. I’ve owned no less than two MP3 players in the last few years, and they were pretty terrible. It’s the very, very simple things too. For example, I listen to a lot of podcasts. There’s (gasp!) a Podcasts menu on the iPod, whereas on every other device I’ve owned, podcasts are interspersed with the music, making them difficult to find and, adding insult to injury, mixing gobbledygook into my otherwise well organized collection. Furthermore (gasp!), the iPod keeps track of which podcasts I listen to, and in concert with iTunes, automatically deletes the ones I’m done with. Them’s lasers! Ah, iTunes. Despite the fact that anyone in the world can write a podcatcher (it’s just RSS with enclosures, fer godsakes), the only one I’ve ever used that works worth a damn is iTunes. Everything else is just “integrated” with bailing wire—create a Windows Media playlist, drop it in this directory, etc. The situation on Linux is a bit better, but guess what—Rhythmbox, Banshee, etc. didn’t work with either of the open media players I owned, even though the integration point for one of them was the file system. No, the players on Linux support the iPod best because that’s what everyone has, and if I’m going to pay extra for the iPod, aren’t I primarily buying the integrated experience? (On a related note, I’ve never understood why people pay top dollar for Macs and install Linux on them. But I digress..) Once you taste the fruit of the integrated experience, it’s easy to get sucked in all the way. I eventually tired of all the wasted time and money trying to use an open media player and broke down and bought an iPod. Not too long after, I canceled my Rhapsody subscription. Why? Because I couldn’t use it with my iPod. My overall music experience is diminished (I’m a big believer in the celestial jukebox), but I want one music platform, not two. And the iPod is the one with critical mass. Anything else is swimming upstream. Are open platforms doomed then? I think that’s, as they say, throwing the baby out with the bath water. The key is to have open interfaces, and the key to having open interfaces that work is cooperation between the vendors that implement them. Perhaps surprisingly, the iPod is a good example of how it can be done. The biggest reason for my iPod purchase: I can hook it directly into my car stereo instead of using an FM transmitter. Apple isn’t getting into the car business—it’s decided to cooperate with other companies to make this work. And you don’t hear too much about people calling their technophile relatives to come glue their cars back together. (And talk about the importance of not crashing..) The lesson here, it seems to me, is that an ecosystem is never the sum of its parts—it’s either a whole lot more or a whole lot less. Furthermore, it’s the responsibility of the vendors (and community) that make up that ecosystem to ensure the result comes up on the right side of the equation in the final analysis.

Thijs Kinkhorst: The famous Belgian hospitality

Belgium has decided on a € 60,- flat rate tax to use their highways. I'm not opposed at all against paying more for scarce resources, like asphalt, but prefer a system where there's more differentiation: pay extra for using roads at peak hours. The thing is that Belgians are compensated for the 60 euros but foreigners are not; a visitor is therefore punished to come to Belgium. I never expected that the Vlaams Blok-xenophobia would extend even in this direction. Thanks for the hospitality guys!

Erich Schubert: Tomcat shutdown problems - resolved

I had trouble with tomcat. It started fine, but shutdown took a very long time (enough for eclipse to suggest killing it, for example). Some people suggested I try the tarball from Apache, instead of using the Debian package, but that didn't help either. By not running tomcat from eclipse and waiting a long time for the shutdown, I finally managed to get some actual error messages: This was usually the last message I was seeing:
INFO: Pausing Coyote HTTP/1.1 on http-8080
After some timeout, I now got these messages:
Protocol handler pause failed
java.net.NoRouteToHostException: No route to host
No route to localhost? WTF? I resolved it by putting all hostnames it might try (localhost.localdomain, although I use that nowhere, as well as the FQDN I'm using) into my /etc/hosts and forcing them to point to 127.0.0.1 - and voila, tomcat actually shuts down instead of pausing and then failing to notice it has successfully paused...

Uwe Hermann: New Unmaintained Free Software logo

New Unmaintained Free Software logo Thanks to the great work of Matthias we now have a great new logo for the Unmaintained Free Software wiki. Thats' all.

Daniel Stone: xdc, menlo park, 7th-9th february

Just a quick reminder: if you were planning on going to the X.Org Developers' Conference in the Bay Area, from the 7th-9th of February, then please make sure you've registered on the page. If you weren't planning to come and you work on X or related fields of endeavour (toolkits, desktops, maybe you're an IHV), then you should consider coming along as well. There'll be a mix of scheduled talks, random freestyle hacking, corridor schmoozing, dinners, after-dinner fun, and a whole world more.

If you'd like to come but your pockets don't go quite that deep, please consider applying for sponsorship. The Foundation is willing to pay for travel and accommodation to developers who couldn't otherwise attend.

Hope to see you in sunny(ish) California!

Gustavo Franco: iPhone random thoughts and multitouch on iMacs someday?

iPhone is cool in a lot of ways (except in the freedom side, but not too different than the current iPods). I wish to buy one until the xmas and replace my now obsolete looking LG model. I think if Apple is trying to promote this product as 'more an iPod than a phone' - as Steve Jobs said in an inteview. They give it the wrong name, it should be called: iPod Phone. Yes, same deal as they did with the iPod video thing until they 'merged' the feature on the iPod brand. Remember that it would save them from the current trouble with Cisco/Linksys too.

The multitouch screen on that thing looks promising. I'm sure that there are a lot of cooler screens in development out there right now, but if Apple (or the real manufacturer behind the screen) can manage to make larger ones, i can see some time in the next year the motto: "Do you remember where did the computer go?" "Where did the keyboard and mouse go now?". Ok, maybe a bit too optimistic (they could keep the keyboard and throw away the mouse), but i think the iMacs could be a interesting target for the multitouch thing. Considering they've iSight already in place, with a larger multitouch screen in a good position and shiny cool gestures software, there we've minority report ready desktops, some time after laptops. Can you hear chairs?

Erinn Clark: Sweet & Sour

According to this blog, I am one of the top 10 living girl geeks! How flattering. In other news, Robert Anton Wilson has died. He's one of my favorite authors, and I found this news to be rather tragic and upsetting, but it seems he remained in good spirits until the end. May he rest in peace.

Bastian Blank: APT security and buildds

For etch, we will have apt security in place, so we can be sure that the stuff comes from the correct archive. But it is not possible to disable that checks only for one source, just for anything. Buildds uses at least one mirror: incoming.debian.org aka ftp-master.debian.org. There are two queues, the accepted autobuild queue and the main archive. The accepted autobuild queue is not signed at all, it does not provide a Release file. The archive needs some time to generate the Packages files each dinstall run and have broken sigs during this time. This means: buildds can't use APT security at all. And no, there is no other mechanism to ensure data integrity.

Bastian Blank: Wishlist for DAK: automatic signing keys

The buildd admin job is a rather dumb one. You get between 20 and 60 mails per day; most of them build logs. This logs, which are mostly sent unsecured through the public internet, have to be signed and the only available key is the personal key of the admin. So on one hand you have to make sure that the key is secure, on the other hand you have to find a way to sign a rather large amount of stuff. For the debian-kernel archive, which I operate, and the pkg-voip/pkg-gnome/pkg-kde-extras archive, which is operated by Kilian, we decided to sign the uploads automaticaly. Each buildd get its own key and the used DAK includes a patch which restricts this keys to do uploads of only binaries of the correct arches. This drasticaly reduces the time until a new package is uploaded; this means much less failed builds because a build dep is not yet built. Also it reduces the places where it is possible to do harm; you have to attack the buildd machine itself instead of the complete mail setup between buildd and admin.

Andreas Schuldei: Dear Lazyweb: Gnome Power Management hooks for suspend

I am trying to figure out how to hook in a homegrown script into the gnome power management. I read the source to gnome-power-manager and it seems to make dbus calls to accomplish what it wants. This is where I get lost as i dont know the first thing about dbus. So: where can I add scripts for suspend or hibernate actions?

Martin-Éric Racine: Copywrong: Media Moguls versus Artists

One recurrent theme in discussions about Copyrights and Digital Rights Management is that the Media Industry allegedly represents the interests of the Artists. Yet, recent actions in Canada and elsewhere prove that Artists who benefited from the wider exposure of their creations via the Internet in fact oppose laws that would preserve and further entrench the monopoly of the Industry. Finland's case is no different: as reported by Jaakko Kuivalainen in the Tekij noikeuslaki blog [in Finnish], a number of Finnish Artist Coalitions are currently opposing the transfer of copyright issues from the Ministry of Education (who also handles cultural affairs) to the Ministry of Commerce, because they fear that the interests of the Media Industry would suddenly have precedence over those of the Artists and small Independent Cultural Producers. Yet another proof that, no, Media Moguls do not speak on behalf of the Artists.

11 January 2007

Russell Coker: ps and security

A post by Scott James Remnant describes how to hide command-line options from PS output. It's handy to know that but that post made one significant implication that I strongly disagree with. It said about command-line parameters "perhaps they contain sensitive information". If the parameters contain sensitive information then merely hiding them after the fact is not what you want to do as it exposes a race condition!

One option is for the process to receive it's sensitive data via a pipe (either piped from another process or from a named pipe that has restrictive permissions). Another option is to use SE Linux to control which processes may see the command-line options for the program in question.

In any case removing the data shortly after hostile parties have had a chance to see it is not the solution.

Apart from that it's a great post by Scott.

Evan Prodromou: 20 Niv se CCXV

So, like everybody else in the world, I was intrigued by the announcement of the iPhone. But like most Open Source folks, I was unhappy with the OS and the general closed format of the dang thing. What options are there for people who believe in Freedom but still want a cool phone? I currently own a Treo 650, which is fine, and which runs the venerable Palm OS. However, the once-thriving Palm Open Source community has pretty much dried up, leaving me without much in the way of interesting apps for my phone device. Thanks to Mike Linksvayer's notes on the subject, I got a link to the OpenMoKo project -- an effort to make a standard, Linux-based phone OS that uses ipkg for application installation and update. The first phone supporting the platform will be the FIC Neo1973, which looks pretty awesome and fairly similar to the iPhone (see this review from Linux Devices for some photos). OpenMoKo isn't the only game in town. TrollTech has a Linux-based Greenphone running their funky Qtopia platform, although it apparently doesn't work with their Qtopia Open Source version. And Nokia has this weird Maemo platform, but it only seems to run on their Internet tablet thingies. Mike gave a good link to an article about Open phones on PC Magazine. But I'm going to be looking out for availability of the OpenMoKo-enabled phone. I guess I'll have to switch phone providers -- Telus, my provider, only has CDMA service, and the FIC phone uses GSM. So, I dunno. But it'd be cool to have a mobile device that was fun and interesting and that I could believe in and want to hack on. tags:

What Chris refuses to blog about So, talking to Chris last night at the yulblog First Wednesday, I found out he wants to quit blogging. "I don't really have anything I care about enough to blog," he said. "The only thing that's piqued my interest lately was the execution of Saddam Hussein. I just don't want to blog about the iPhone." I told him I thought it'd be a good idea to make a blog just listing the things he refuses to blog about. He wouldn't commit to the idea, so I guess now I've taken over that job. In other words: Chris won't blog about the iPhone. tags:

Eddy Petrișor: how to disable the pcspkr in Etch?

The new laptop I just bought had the bad habit of using the pc speaker at a loud level. It was deranging the coleagues at work when autocompletion yelded more than one result or none (it also scared me a few times during the last nights when I was configuring and testing the laptop).

So I unloaded the module (pcspkr) by hand and wanted to make the system not load it anymore.

So I thought that blacklisting it would do the trick. Probably some people know already that adding al line like:

blacklist pcspkr

in /etc/modprobe.d/blacklist doesn't work. The rest of you find out now. I found out at the next reboot, when I heard again the beep.

Ok, I googled a bit and found some info about restricting ipv6 modules being loaded so I though I could do the same for pcspkr. So I tried:

to change the line from /etc/modprobe.d/pnp-hotplug:

alias pnp:dPNP0800 pcspkr

into

alias pnp:dPNP0800 off

That didn't work either.

So, at this point I googled more and found some outdated information about update-modules.

That brought me to modprobe.conf(5) which pointed to the "right" solution.Write the following in some file in /etc/modprobe.d/ (I added it in blacklist, since it seemed the right place)

install pcspkr true

Which seems to do what I want.



Still something tells me that either:

1) there is a cleaner solution I am not thinking about

or

2) I could have told udev not to load the module... And I feel this solution should have to do something with these lines and "ACTION":

eddy@bounty /etc/udev $ grep -r pcspkr *
persistent-input.rules:DRIVERS=="pcspkr", ENV ID_CLASS ="spkr"
rules.d/z20_persistent-input.rules:DRIVERS=="pcspkr", ENV ID_CLASS ="spkr"



A clean solution would be appreciated.

David Moreno Garza: Fatherland! Socialism or death, I swear it!

From The New York Times:

CARACAS, Venezuela, Jan. 10 President Hugo Ch vez was sworn in to a new six-year term at a ceremony here on Wednesday in which he described Jesus as “the greatest socialist in history” and pledged to speed Venezuela s metamorphosis into a Socialist country. “Fatherland! Socialism or death, I swear it!” Mr. Ch vez yelled as he was sworn in and given the presidential sash and a golden key to the tomb where the remains of Sim n Bol var, the South American liberator, are interred.

/me cheers :)

Thijs Kinkhorst: Found a traffic light

bus lightHow often in life does one find a traffic light lying at the side of the road? And how many of those times does it concern a buslight? Well, it happened to me: I found the buslight shown here at the Archimedeslaan. It is the type of traffic light that only applies to busses, trams and their public transport friends. I believe this is specific to The Netherlands, so here's a diagram of the possible layouts (top row). It runs on 40V power, but as I had a maximum of 19V available (not counting the 230V from the wall) it looks a bit faint. The bulbs look like the same ones used in car lights, and everything you can do with the unit (open, replace lights, reconfigure light positions) can be done without tools. Nice design. I called the contractor that maintains the city's traffic lights, Dynamicon, and the guy on the phone said he'd pass my information on but didn't believe they needed it anymore. Now only to find a good use for it...

Martin F. Krafft: Destinationen

Just now on the Swiss hotline, a lady announced in the typical Swiss way of speaking "high German" that the airline now offers bla bla bla to over 200 "Destinationen". I had to snicker. English readers may wonder what the deal is, and even Germans might just yawn: "Destinationen" is not a German word, it's "destinations" germanified, and it's no news that the German language is seriously deteriorating as English words are creeping in. At the risk of being repetitive: it's not the English words per se, it's the fact that they are being conjugated or declinated according to German rules, which irritates me (and many others). The reason for this blog post was simply the humour: a Swiss lady speaking "high German" with her subtle Swiss accent, using words that don't exist as if there was nothing to it. I actually had to laugh out loud. Note that I have great respect for Swiss people speaking German, it being somewhat of a foreign language to them. I am perfectly aware that many are uncomfortable doing so, and this post is not trying to make fun of them, but rather expose the irony of the use of a non-German word. NP: Dream Theater / When Dream and Day Reunite Update: Christof Roduner informs me that "Destinationen" is actually a German word, or at least recognised by the Duden:
De s ti na ti on, die; -, -en <lat.> (Reiseziel; veraltet f r
Bestimmung, Endzweck)
Aus: Duden - Die deutsche Rechtschreibung, 24. Aufl. Mannheim 2006.
That must be the new orthography, which I won't comment on at this point.

Adrian von Bidder: The Day Debian Got Rid Of (most) Spam

This is just to say thank you once more to all who've made it possible. The circle in the graphic below marks the date when I made use of the newly available spam controls for my Debian mail account.

Miriam Ruiz: Connecting my MIDI keyboard to the laptop

Laptops don’t usually have as much ports as desktop computers. I used to connect my MIDI keyboard to the computer via a game port adapter. Now the game port has been to some extent replaced by USB connectors, especially in laptop computers, so I decided to get myself a MIDI-USB adapter. After searching the web investigating which device would be the best for my Debian system, I decided for the MidiSport Uno, which is elegant, compact, and compatible with Linux. Yesterday I was finally able to test it, and it works perfectly. The only thing I don’t like is that its firmware doesn’t seem to have a free license. After some initial trials with fxload, which didn’t work due to some pipe error, I realized that it wouldn’t work under the current udev system (I’m using a 2.6.18 kernel right now), but the rule for udev I added seems to work. Ubuntu’s package for it has also helped me a lot. After installing it, I was able to test that it worked both with a direct cat from the MIDI device and using rosegarden. There seems to be also an OSS driver supporting the MidiSport 1×1/2×2 with a GPL’d firmware, but I haven’t tried it yet. It would be nice to be able to have a GPL’d firmware in it.

John Goerzen: Dial Tone

Yesterday I went to activate phone service out at the farm. It got me to thinking a bit about how things change, and how they stay the same, too.

Before I go on, I'll have to say that every one of my history books is in storage, so if I get some details wrong, it's because I'm not remembering correctly.

Anyhow, phone service came to our community via an unusual route about 100 years ago. It wasn't Bell/AT&T or some other company that brought it there, as it was most places. I'm sure they figured that a small, scattered rural community would cost too much to support. So the community organized, built, and supported the phone system themselves.

Even today, roads around here can be impassible after a good rain. I'm sure that, in the early 1900s, before heavy road-maintaining machinery, things were worse -- and, of course, transportation was a lot slower then anyway. There were real problems: getting the word out about funerals, being able to summon a doctor when necessary, or letting people know that church was cancelled because of too much snow.

People in the community saw a phone system as a real need. So did the churches, which have left a legacy that is still reflected in phone company territories today.

Once phone service arrived, it was used for all the things that people expected, of course. But it also proved to be an important part of the social fabric of the community. Since party lines were the norm, it was possible to announce things to every listening subscriber pretty quickly. Older people remember announcements of fresh fruit arriving at the grocery store, funerals, or other news of the day.

To place a call, you would pick up your phone and turn your crank. That caused a bell to ring at the telephone office, which everyone called "Central." The operator would connect to your line and ask whom you wanted to talk to. The operator would then send the distinctive ring for your party down their party line, and patch -- manually -- your call through to them. And, if he was busy, the operator wouldn't listen in on your conversation -- but others on the party line very well might.

Central's hours were published. If you were making a call in the middle of the night, you were going to wake up someone at Central to do it -- plus everyone on the entire party line. So calls after hours were rare.

Fortunately, while some of the old Central operators were still around, some people in the community wrote down some of their stories.

There were some people in the community that were notorious for eavesdropping on other people's conversations. Two brothers one time figured that they knew somebody was listening to their conversations, so they devised a code. One called the other, and said, "I'll be going to McPherson in the morning for band practice." That meant something along the lines of going to town to buy groceries.

A few days later, their prime suspect came up to him and said, "What on earth are you going to band practice for? I didn't know you knew how to play an instrument!" Apparently she realized she was had when he burst out laughing uncontrollably.

The Central operators learned to know the habits of telephone users. Sometimes they would connect calls without even bothering to ask who people wanted to talk to -- and seemed to always get it right.

The phone system supported itself for about 50 years. But as the rest of the world moved on provide direct dialing, this proved a controversial subject in the community. People liked having their operators. The people that worked at Central were everybody's friend. They were people that were there, 24 hours a day, to assist with any emergency. They would gather volunteer firefighters to help fight a fire, or be able to spread community news quickly. This wouldn't be available with the newer phone systems. How would the community be informed of events quickly now? Who would just happen to know whose house the doctor was at when he was urgently needed?

The change was resisted for some years, but eventually the finances of the telephone cooperative turned out to be in deep trouble. Operators grew to be much more expensive than automation, and in the late 1960s, the telephone cooperative was no more -- sold to a phone company from a small town more than twice our size, and a for-profit company at that! Central no longer existed. I remember reading about this event -- it seems people were sad about that for quite some time. They felt that they had really lost an important part of the community when Central went away. Some machine locked in a cabinet doesn't care for people the way Central did. Even today, the older people in the community sound a little sad when they remember telephone modernization, and get the wistful look of somebody that has just remembered something that they miss.

The phone company that bought the system wasn't an AT&T, though. It was a small, independent phone company. To this day, that phone company serves only the two communities. And it was this company that I called yesterday to establish service out at our house.

They had already upgraded our lines -- over a mile of new copper, benefiting only us, at no charge to us -- last fall. The box was already on the outside of the house. Just need to get it activated.

So I called the phone company. They said I needed to drop by their office and sign some papers. Uh-oh, I think -- this is a bad sign. Sounds like a bunch of phone company bureaucracy.

But not so much. I went to the office and signed up. They asked the usual questions: name, address. Plus a few that bigger companies wouldn't ask: who used to have service at that address? Of course, most people would know that answer in our community. I couldn't have told you in Wichita, Dallas, or Indianapolis.

Then they asked when I'd like service to be activated. "As soon as possible," I say, figuring that this would be a couple of weeks like it is with AT&T or Sprint. "Well, we probably can't get out there for a couple of hours. Would it be OK if it's on at about 3?" Yes, that would be fine!

Now, how about DSL? "Well, we're a little backed up on that right now." Uh-oh. Sprint took several weeks when they *weren't* more backed up than usual. "So it'll probably be Monday or Tuesday before we can get out there. Should I just have the installer call you and arrange a time when it gets closer?" Yes, that would be fine, too!

Now, how about finding a phone number.

Out comes a large paper book. Yep, paper. They paged through it, and told me that my grandpa's old number would be available if I wanted it. I said yes -- after all, we've got his old address, so might as well keep the same phone number. OK, no problem. She whips out some white-out, whites out grandpa's name, and writes ours in. Done.

Now, do we want any optional services? Caller ID, call waiting, voicemail? How much is caller ID, I ask. $5 a month. We'll try it for now. "OK". A box was checked on the form and that was that. No high-pressure sales pitch on taking "the works" for some poorly-disclosed price, providing a ton of services I'll never use and don't want. No confusing "discounts" for having The Works and DSL at the same time.

Then I ask about an unlisted number, or at least an unlisted address. We figure that anybody that we really want to be able to reach us will figure out how without using a phone book, and these things get in so many databases these days. Sprint charged almost $10/mo for a fully unlisted number, but only a few dollars a month to just keep our address off the directories.

Our new company charged 50 cents a month for a fully unlisted number. Done.

Now it's time to pay for the first month's fees and the setup. Oops, I've forgotten my checkbook in the car. No problem, the secretary says, I'll watch your baby while you go get it! Jacob was with me, but had fallen asleep, so I brought him inside in his car seat. I went to get the checkbook -- just out the door and close by. I was back in a few seconds later, and the secretary was already on the other side of her desk talking and playing with Jacob. "My baby's 12 now," she said, and for a second, looked like a person that was remembering Central.

Next.

Previous.