Search Results: "ag"

6 October 2008

Russell Coker: RPC and SE Linux

One ongoing problem with TCP networking is the combination of RPC services and port based services on the same host. If you have an RPC service that uses a port less than 1024 then typically it will start at 1023 and try lower ports until it finds one that works. A problem that I have had in the past is that an RPC service used port 631 and I then couldn’t start CUPS (which uses that port). A similar problem can arise in a more insidious manner if you have strange networking devices such as a BMC [1] which uses the same IP address as the host and just snarfs connections for itself (as documented by pantz.org [2]), this means that according to the OS the port in question is not in use, but connections to that port will go to the hardware BMC and the OS won’t see them. Another solution is to give a SE Linux security context to the port which prevents the RPC service from binding to it. RPC applications seem to be happy to make as many bind attempts as necessary to get an available port (thousands of attempts if necessary) so reserving a few ports is not going to cause any problems. As far as I recall my problems with CUPS and RPC services was a motivating factor in some of my early work on writing SE Linux policy to restrict port access. Of course the best thing to do is to assign IP addresses for IPMI that are different from the OS IP addresses. This is easy to do and merely requires an extra IP address for each port. As a typical server will have two Ethernet ports on the baseboard (one for the front-end network and one for the private network) that means an extra two IP addresses (you want to use both interfaces for redundancy in case the problem which cripples a server is related to one of the Ethernet ports). But for people who don’t have spare IP addresses, SE Linux port labeling could really help.

Patrick Schoenfeld: Where do find help for commands?

Today an discussion rised up in #debian-devel on the OFTC IRC Network. It started because someone noted the bug report #501318 which is, to summarize it, just a user mistake, because someone obviously read the man page (time(1)) for the /usr/bin/time command, while time is also a shell builtin (which does not accept the same arguments as the time command. Certainly this bug reports appears to be funny at the first sight, but on the other hand, there is a suboptimal situation that leads to this.

  1. There are some builtin commands that also have binary equivalents (like time, printf, echo). Its quiet easy to tell weither the one or the other is used, by using the which command, but thats not really a realistic workflow, so its better to know this. The difference between these commands is often causing problems, which we have to cope with. For example bashs builtin echo behaves different as /bin/echo and people who use the bash as their default shell tend to use what bash provides, which in turn causes problems if other people who use a different default shell try to work with these scripts. But this is another problem, because...
  2. ... every program, utility and function in Debian has to provide a manpage, as said by our policy: "Each program, utility, and function should have an associated manual page included in the same package." I guess that the rationale behind that is that 'man' is a very common tool in the Un*x world, which is wide-spread and which usage is much recommended to find out how specific tools behave. It is always referred to in Documentation, weither it is Debian specific or not, e.g. in books.

    The time package, which is of priority Standard and which includes /usr/bin/time, does conform to that policy by providing a manpage for the time command. The various shells don't do that, because they usually don't have a man page for each and every command (usually they have a more generic manpage which includes the builtins or in some seldom cases a special manpage for such and similar things (as for zsh, which has zshmisc(1)) and because its not that easy, because the man command cannot (AFAIK) distinguish between the user joey_average calling 'man time' in a bash, while the user schoenfeld calls the command 'man time' in a zsh, or if joey_foobar calls 'man read' in a shell which does not have a builtin time command and uses /usr/bin/time instead.
So whats wrong about this situation? Would you say that users that expect 'man time' (or similar examples) to do the right thing are making wrong assumptions? I disagree. Its what they've always been told to do. And if it does not show anything eventually run info, or look at HTML documentation or what else. But they haven't been prepared for the case where the manpages does show something, something wrong. The good thing is that the manpage for time includes a sentence:

"Users of the bash shell need to use an explicit path in order to run the external time command and not the shell builtin variant."

The bad thing about it is, that it is at approx. 70-80% of the manpage.

Clint, the maintainer of zsh, mentioned run-help which seems to be a part of the zsh, but not of any other shell, and does more or less the right thing (at least for the builtins) but not for external commands and not even for itself (it opens the code of the function instead of something user-readable like a manpage). I guess "one tool for a specific need" is a good maxime, but is it really a good maxime for finding documentation?

But how could the situation be bettered? I could think of a wrapper for man, similar to run-help but as a more generic solution. Any ideas for it? Is it the right way at all to better the users experience? Any other ideas? Other opinions?

Christian Perrier: It's definitely unreasonable to...

...try to compile three packages simultaneously (with pbuilder/cowdancer), read mail and chat on IRC at the same time on a Dell latitude X1. Note to self: try to remember this next time you stupidely launch cowbuilder in three different windows. It's fun to see mutt counting messages in mailboxes one by one but not really productive, indeed.

Chris Lawrence: Choosing the wrong denominator

Matthew Yglesias demonstrates innumeracy in action:
We got an interesting experiment this weekend as Bill Maher’s anti-religious screed Religulous and David Zucker’s right-wing satire An American Carol both opened. The two films were about tied in terms of total revenue but Carol was on three times as many screens, so basically Religulous was far more successful. I think this mostly reflects something I wrote about a couple of years ago — the moviegoing audience is very demographically similar to the Democratic Party voting audience. It’s disproportionately young, disproportionately childless, and tilted toward residents of big cities and away from residents of rural communities. Conversely, the audience for television news is demographically very conservative (older, white, and a bit more prosperous than average) which is one major reason TV news coverage tilts right. The big screen audience for what looks like a witless screed against God is just a lot bigger than the big screen audience for what looks like a witless screed against Michael Moore.
Actually, since total revenue for both movies was about the same, it would appear that the “big screen audience” for crappy polemical Bill Maher movies is about the same as the “big screen audience” for crappy polemical David Zucker movies. Further, since I’d guess Carol probably played in theaters with lower ticket prices on average than Religulous, the former probably did a little better in terms of the total audience. Yglesias also makes the rather faulty assumption that the per-screen average revenue would remain flat as screens increased. This result only obtains if moviegoers don’t select theaters based on what movies are playing at them or if screens are very distant from each other geographically; while surely there are some people who just go to the movies to see something without deciding beforehand which movie to see, I doubt there are enough of these people to ensure Maher’s movie would gain a substantially larger audience, except in the relatively uncommon cases where the film just isn’t on at any theater in a metropolitan area and there is a substantial number of people who want to see it. Besides, all the discerning moviegoers were at Nick and Norah’s Infinite Playlist this weekend anyway.

Russ Allbery: Config management and bundle

Today, among all the other things I accomplished, I converted the rest of the system templates for the eyrie.org systems to Git and tweaked my personal configuration management system to make better use of Git's features to push data around. I was feeling on a productive roll, so I also wrote up the system I use. This system has a long history. The first commit in the underlying repository for my personal workstation is dated September of 1998, and the underlying system was already in use at Stanford before I started working here more than 15 years ago. It survived several major OS changes and several significant reorganizations and only recently has been replaced for day-to-day server management by Puppet. We still use bundle to do some of the initial system configuration inside FAI before the system is put together enough to run Puppet. Puppet is overkill for a few personal systems, so the system I'm using is based on our previous revision of our server template system, with some modifications to not depend on AFS and to make remote deployment of changes easier and simpler. It's not as fancy as some of the new ideas for managing all of /etc in a VCS, but it's been reliable and capable enough for me that the core of the system remains unchanged after ten years.

5 October 2008

Christian Perrier: More boring stats: inhabitants per DD per country

Following my last blog post, Moritz Muehlenhoff sent me another statistical list in a desperate attempt to prove that there is no german cabal. As usual, when counting antyhing per inhabitant in IT, Finland wins:
   241890 Finland
   361500 Switzerland
   398766 Norway
   401033 Sweden
   426800 New Zealand
   489205 Austria
   492322 Germany
   612857 Australia
   713415 Netherlands
   795965 France
   814194 Belgium
   834800 Canada
   871071 United Kingdom
   912631 Denmark
  1102457 Spain
  1196289 Ireland
  1255125 Hungary
  1369233 United States
  1456400 Israel
  1484500 Croatia
  1737487 Czech Republic
  1738889 Uruguay
  1806645 Italy
  1910059 Bulgaria
  2270700 Latvia
  3369600 Lithuania
  3539191 Portugal
  3640956 Japan
  3811600 Poland
  4133884 Costa Rica
  5379455 Slovakia
  5608354 Greece
  6779558 Argentina
 10410773 Brazil
 11975000 South Africa
 14695666 Colombia
 12261197 Korea, Republic of
 16598074 Chile
 20042551 Madagascar
 20286976 Russian Federation
 22246862 Romania
 28199822 Venezuela
 28220764 Peru
 35293128 Turkey
 53341250 Mexico
 75360000 Egypt
226489200 India
330462972 China
Indeed, the best proof that there is no german cabal is that, IIRC, "they" never succeeded in having one of "theirs" elected a DPL. This is probably the best proof that there isn't ONE german cabal, but probably more... Beware of "them", "they" are everywhere.

Anand Kumria: How to solve a credit crisis ...

Apologies to anyone bored of this topic but it is something I have been thinking about recently. You have people commenting on why Banks are special and need government funded bailouts. Others arguing that the Free market is not dead. We have even have a few solutions from some people within the Free Software community. I think the first thing is to identify who should lose, and who should win. Much of the annoyance about the rescue from ordinary people is that it seems that investors are not losing (enough). They took some risks, those gambles failed, and now everyone else is paying the price. If IBM were to go bankrupt, would the government step in? Unlikely. Investors would lose (money), staff -- another word for investors -- would lose (jobs), but customers would win (their computers would keep working). Some customers would win more than others (especially those who had the equipment on lease); if no one is collecting, why pay?. So let's apply the same set of outcomes to banks. But hang on, you rightly ask, - a bank has the title deed (a mortgage is a promise to pay amount X over Y year in return for the deed) - why would customers (depositors), realising a bank is no longer viable, since remove their funds I think that those two issues can be addressed fairly simply. The government would guarantee all depositors money. Customers never lose. They never have to worry about their funds. For banks, who enter into administration, the standard laws about possession should apply. If a borrower is utilising (living in) the asset to which the bank has title for over Z years (where Z equals 5 or 7), then the possesor now owns it outright. That is plenty of time for a bank to either be bought, have the underlying asset value recalibrated, or to completely go bust. All without a detrimental effect.

Andrew McMillan: Apology Accepted

It is nice to see someone apologising for their planned failure to consider Linux users. It's ridiculous that they even have to. It seems to me that these people have spent way too much effort on making the logo and menus scroll in from the left and right of the screen, and not enought effort on the actual functionality of their website. I fail to understand what benefit they have gained from using the Pizza UI for their logo & menus (yes, really) rather than using simple links - or CSS-based menus, if they needed fancy. The page layout doesn't actually need anything more than simple text links. The logo (thankfully) does nothing after it's page-load scroll. For extra 'fail' marks they substitute graphics when I initially arrive with Javascript disabled (and wearing my tinfoil hat) but the graphics give me the appearance of a menu without actually performing a useful function. The user-interface situation gets worse later, when I am taken through five successive screens to upload and classify some new media. It seems that in order to bore people who are foolishly trying to upload their home movies over "poorband" they attempt to display a progress bar. A better approach would be to ask me all of the questions about the media I am uploading on one single page and let me get on with something useful. This might be news, but it seems that such an interface could be done in plain HTML, and wouldn't actually require me to enable javascript for a site which is riddled with cross-site scripting flaws. Since it's the school holidays at the moment we took advantage of Te Papa's excellent institution of "Late Night Thursday" last week and visited the other end of the website in person. My disappointment in the website was then entirely eclipsed by my disappointment in the real-life part of the exhibit. The "walk on the map and see photos of the area" component was decidedly clunky, with no clear feedback between stepping on a tile and media appearing on the wall In fact it seems most tiles don't actually do anything, and there are only a few small screens in the walls to display the images. The "postcards blowing in the wind" gimmick amused the kids for about 20 seconds, tops. The 'wall' was quite a lot more successful, amusing me and the kids for nearly half an hour, though we're unlikely to go back next time we're there. There were plenty of annoyances also, in particular that it doesn't appear to use the full resolution of uploaded photos, the interface is slow and it is difficult to see what you are doing at times. It's good that they've started practising their apologies, firstly targeting the small (but geeky :-) segment of New Zealanders who are Linux users trying to help them out by providing them with free content. Now I am looking forward to their further apologies to larger groups of justifiably annoyed people, culminating with the ultimate one, where they apologise to all of the taxpayers of New Zealand who funded this incredible waste of money. I can imagine that something interesting could be done with a lot of media of New Zealand and now that Te Papa has started to amass a collection in this way, perhaps they will.

Andrew McMillan: Apology Accepted

It is nice to see someone apologising for their planned failure to consider Linux users. It's ridiculous that they even have to. It seems to me that these people have spent way too much effort on making the logo and menus scroll in from the left and right of the screen, and not enought effort on the actual functionality of their website. I fail to understand what benefit they have gained from using the Pizza UI for their logo & menus (yes, really) rather than using simple links - or CSS-based menus, if they needed fancy. The page layout doesn't actually need anything more than simple text links. The logo (thankfully) does nothing after it's page-load scroll. For extra 'fail' marks they substitute graphics when I initially arrive with Javascript disabled (and wearing my tinfoil hat) but the graphics give me the appearance of a menu without actually performing a useful function. The user-interface situation gets worse later, when I am taken through five successive screens to upload and classify some new media. It seems that in order to bore people who are foolishly trying to upload their home movies over "poorband" they attempt to display a progress bar. A better approach would be to ask me all of the questions about the media I am uploading on one single page and let me get on with something useful. This might be news, but it seems that such an interface could be done in plain HTML, and wouldn't actually require me to enable javascript for a site which is riddled with cross-site scripting flaws. Since it's the school holidays at the moment we took advantage of Te Papa's excellent institution of "Late Night Thursday" last week and visited the other end of the website in person. My disappointment in the website was then entirely eclipsed by my disappointment in the real-life part of the exhibit. The "walk on the map and see photos of the area" component was decidedly clunky, with no clear feedback between stepping on a tile and media appearing on the wall In fact it seems most tiles don't actually do anything, and there are only a few small screens in the walls to display the images. The "postcards blowing in the wind" gimmick amused the kids for about 20 seconds, tops. The 'wall' was quite a lot more successful, amusing me and the kids for nearly half an hour, though we're unlikely to go back next time we're there. There were plenty of annoyances also, in particular that it doesn't appear to use the full resolution of uploaded photos, the interface is slow and it is difficult to see what you are doing at times. It's good that they've started practising their apologies, firstly targeting the small (but geeky :-) segment of New Zealanders who are Linux users trying to help them out by providing them with free content. Now I am looking forward to their further apologies to larger groups of justifiably annoyed people, culminating with the ultimate one, where they apologise to all of the taxpayers of New Zealand who funded this incredible waste of money. I can imagine that something interesting could be done with a lot of media of New Zealand and now that Te Papa has started to amass a collection in this way, perhaps they will.

Biella Coleman: The OpEd Project, take 2

I just got back from the OpEd project/workshop. In short, it was worth every penny and if you are interested in writing an OpEp and riding the public debate bandwagon, this is the perfect place to start. Why? Well, first because the world of punditry and debate needs more diversity and women and this project is fundamentally geared toward getting more women into the system and in a no nonsense, accessible, inspiring, and yet utterly pragmatic fashion. First, if you don’t know the stats concerning women, they are depressingly dismal. For example, 9 out of 10 submissions are from male writers and 88% of published pieces are from male authors (and this is matched by all sorts of other disturbing figures about the lack of women non-fiction writers, TV producers etc). In the OpEd field, the main problem, in short, is that women are not even trying. Today’s full-day workshop was enlivening and engaging. Catherine Orenstein, the founder and dynamic leader of the project, dusts away a lot of the mystery of this writing genre and equips participants with some basic skills and tactics to get you started (then, in my opinion, it takes a fair bit of work and persistence to master, just like any type of writing but it is not rocket science either). What I like most about the project is its utter pragmatism. Cathy knows that once there are enough women in the system, the project can close shop, for it will be other women who will take over the reigns and inspire other women to write them (and informally mentor them as well). It is well known, for example, that once there is a critical mass of women, let’s say in the work place, then these women are the point people for recruitment so that the company does not need to actively recruit women. I have heard this argument before and have had a number of personal experiences that confirmed this fact. Last year, for example, a student from my department was organizing a conference and he could not, for the life of him, find any female speakers or discussants, despite asking a number of them who declined because of other commitments. He had ran out of options, that is, until he talked to me. In less than a minute, I rattled off like 5-7 other possible choices and within a day, we had 2 on board. It is clear that women know other women (and many are friends) so the best person to go to to tap into are other women. In terms of the actual writing of an OpEd, I am not sure I will be writing one anytime soon in so far as I need to really pump out a few more academic articles as the future of my jobs depends on them. But I may write a draft version of one that I will hammer into finer shape if a timely news event arises. Otherwise, I look forward to spending more time on this genre, especially once my book is done and know that if I am going to stay in academia, I will for sure make space for this type of thinking and writing. Finally if you are interested in attending one of the public, women-only seminars and you know me, let them know you learned about the project through me, and you will get discount.

Biella Coleman: If you complain

One thing I am known to do is complain how the public/academic discourse surrounding/around technology/computers is overwhelmingly male (Lessig, Benkler, Zittrain, Shirky and I can go on and on). But one day I realized that if I am bothered by it, I should do more than talk the (often) empty talk of complaint. So I decided to enroll in a day long training for writing OpEds, which kicks off tomorrow. I am not sure if engaging in public debate is what I want to do, mostly because of piling more work and time commitments on a very full plate but I am starting to explore what it means and what it may take to leave the Ivory Tower. Here is a little more info about the OpEd Project:
The OpEd Project - featured by The New York Times, Feministing.com and Katie Couric on CBS News - is an initiative to expand public debate, with an immediate focus on targeting and training women experts across the nation to project their voices on the op-ed pages of major newspapers, online sites and other key forums of public discourse. The lack of diversity on the op-ed pages - which are a source for all other media - deprives the public of robust, democratic debate, especially important in this space which is intended to showcase divergent opinions. It also means we are only hearing from a tiny sliver of the nation’s best thinkers. Imagine a baseball team of only pitchers - how well would it do?

Russ Allbery: Updated Debian notes

Some time back, I wrote up our current best practices in the Stanford central UNIX support group for managing Debian servers, and some time before that, I wrote up some notes on useful Debian package build tools. Both of those pages had become hopelessly out of date. Over the past week, I've been revising them, and they should now reflect reality somewhat better. Notable in the changes to the build tools document is a switch from debarchiver to reprepro. I haven't finished doing that migration for my personal repository, but I'm most of the way through and hope to be able to pull the trigger fairly soon. I like debarchiver and have used it for years, but reprepro supports a pool structure and package migration between distributions, both of which are killer features. We're going to be switching to reprepro for Stanford's internal archives as well, although probably not until sometime in November or December. I also moved the documentation I had for packaging individual scripts into a separate document and updated it to reflect the fact I use Git now instead of Subversion. Most of the details here are fairly straightforward and obvious, but I find it useful to read through something like this and see how someone else approaches a problem. Maybe someone else will find bits of it useful.

Russ Allbery: podlators 2.2.0

While incorporating some of the podlators fixes into the Perl that will be released with lenny, Niko Tyni found more problems with the current implementation. I'd written the test suite to force the output encoding on the file handle used by Pod::Man and Pod::Text, but pod2man and pod2text weren't doing that, and hence the output wasn't properly encoded. I'm finding Perl's Unicode support very tricky, particularly if I want to support the PERL_UNICODE option that adds input and output encodings on all file handles. I can't use encode before output because PERL_UNICODE encoding layers will then double-encode. The approach taken in this release is to force the appropriate output encoding on the output file handle (possibly destroying caller state). This works, but it's ugly. Pod::Text had another problem. Its historic behavior is to copy the input encoding to the output, but doing that with properly-tagged UTF-8 POD input means printing out wide characters in the internal encoding, resulting in Perl warnings. This version now, in the absence of the utf8 option, forces the output encoding to match the input encoding if possible. This seems like the best compromise and matches its historic behavior. pod2text now supports a --utf8 option since it's now useful to force a different output encoding. I wanted to get something out to stop the bleeding, but there are a few problems with the current approach. As mentioned above, I'm forcing file handle encoding layers, which may destroy encoding layers created by the caller that were intentional. This implementation also depends on PerlIO support, which is an optional Perl feature and not always enabled. I think the right long-term approach is to probe for PerlIO support, and if present, use it to check the encoding layer on the output file handle. If PerlIO is not set, or if no encoding layer is present, I can safely use encode before output, which doesn't mess with the file handle state and is much cleaner. If PerlIO is present and an output encoding is set, just trust that output encoding (although if the utf8 option is set and the output encoding is something else, it may be a good idea to throw a warning). I'm not sure when I'll have time to implement this, though, since it will require another reworking of the code and more testing, and I'm behind on a number of other projects. In any event, the current version will work for most people in most cases. You can get it from the podlators distribution page.

Christian Perrier: Developers per country

A small discussion on IRC triggerred this (from Debian LDAP): Number of DDs per country:
United States : 348
Germany : 197
United Kingdom : 97
France : 96
Canada : 56
Australia : 56
Spain : 49
Japan : 41
Italy : 40
Netherlands : 38
Sweden : 34
Finland : 27
Austria : 22
Switzerland : 21
Brazil : 19
New Zealand : 14
Poland : 13
Norway : 13
Belgium : 13
Hungary : 12
South Africa : 8
Denmark : 8
China : 8
Russian Federation : 7
Ireland : 7
Argentina : 7
Korea, Republic of : 6
Israel : 6
Czech Republic : 6
India : 5
Portugal : 4
Bulgaria : 4
Croatia : 3
Greece : 3
Colombia : 3
Uruguay : 2
Turkey : 2
Romania : 2
Mexico : 2
Egypt : 2
Venezuela : 1
Thailand : 1
Slovakia : 1
Peru : 1
Madagascar : 1
Latvia : 1
Lithuania : 1
Costa Rica : 1
Chile : 1
Number of active DDs per country:
United States : 223
Germany : 167
France : 81
United Kingdom : 70
Spain : 41
Canada : 40
Japan : 35
Australia : 35
Italy : 33
Sweden : 23
Netherlands : 23
Finland : 22
Switzerland : 21
Brazil : 18
Austria : 17
Belgium : 13
Norway : 12
Poland : 10
New Zealand : 10
Hungary : 8
Russian Federation : 7
Denmark : 6
Czech Republic : 6
Argentina : 6
India : 5
Israel : 5
Ireland : 5
South Africa : 4
Korea, Republic of : 4
China : 4
Bulgaria : 4
Portugal : 3
Croatia : 3
Colombia : 3
Uruguay : 2
Turkey : 2
Mexico : 2
Greece : 2
Venezuela : 1
Slovakia : 1
Romania : 1
Peru : 1
Madagascar : 1
Latvia : 1
Lithuania : 1
Egypt : 1
Costa Rica : 1
Chile : 1

Wouter Verhelst: Belgian electronic ID card and security

I received some feedback on my previous BeID post, where I explained how to log in to a remote system by use of your digital ID card. Philip and Guy both claim it possible or likely that the crypto keys on eID cards are stored on a system of the government somewhere and that you therefore should not be using them. I find this to be jumping the gun a little. Security is always a trade-off; indeed, if you want to hide stuff from the government, then using eID-based authentication might not be a very good idea. However, there are other cases where eID-based authentication really is the correct option; and it is nice to know that this kind of thing is possible. Security always is a trade-off; and if you make an informed choice, there's nothing wrong about giving someone else access to your server. The fun bit is that Philip actually advocates carrying a clear-text printout of a list of still-valid passwords. Now that, I feel, is unacceptable, security-wise. Personally, I'd rather use a smartcard that only some secret government agency might be keeping copies of rather than a list that any random thief might make use of. The question really boils down to this, I think: how likely do you think it is that someone else will be able to get at your password by guessing or stealing it? What I mean by that last bit is that you should always generate your passwords with a tool that generates fully-random passwords ('pwgen -s', for example), and never write them down in cleartext anywhere. That of course makes it slightly hardish to memorize them; what I do is to store the password encrypted to my GPG key on my laptop, and I memorize the password by changing it on a remote server that I need to access fairly often (Debian's systems will do), but leaving my GPG passphrase and laptop password as is for the time being. Every time I need to log in to the remote server, I first try to remember the passphrase. If I can't remember it, I look it up in the encrypted file (again taking care not to store the file on disk). Once I start being able to log in to the remote server without having to look it up in the file, I change all my other passwords. This process usually takes a few weeks. Then, the only way someone can get my password is either by coercing me or by killing me and disecting my brain. And then still. Unfortunately, in the real world, I realize that many people do not wish to go through all this trouble just to get a secure login, and instead just choose a weak password. I guess that's why I think the next best thing might be slightly better than using strong passwords...

Biella Coleman: Slowly Blogging Away

The students in my Hacker Culture and Politics have now been at the question of politics and ethics in the world of hacking for over a month. I think a pretty solid foundation has been built and now we are getting into much nittier grittier issues, like intellectual property law. The latest entry is on IP and provides an excellent sense of what we talked about and what we covered in class and in the readings. I am excited to see the class blog develop, if nothing else, because it gives a pretty good sense of the topics we cover and what conversations we have. I used to find it frustrating to have classes literally vanish away after they were done and yet so much labor and time had been put in them! This type of blogging is important as it can provide a tangible and somewhat fixed medium for capturing and preserving what happened (and then free you from having to save boxes of notes that you can collect during college). I know there were a number of times I really really wanted to recall something from one of my undergraduate classes, but since I had finally thrown away the big old boxes of notes and readings from those days, there was no place to look. It was just not practical to lug my boxes of notes from place to place, move to move especially when I only wanted to take a look every few years for maybe one thing. With this type of blog, there is a record of what happened for everyone to share. That said, I am faced with a problem when I teach this class again. Since we provide what I think is a pretty decent account of what we are doing, I will most probably have to put down the blog for a period of time when I am teaching it again though of course the syllabus and readings will also change to some degree.

Biella Coleman: Slowly Blogging Away

The students in my Hacker Culture and Politics have now been at the question of politics and ethics in the world of hacking for over a month. I think a pretty solid foundation has been built and now we are getting into much nittier grittier issues, like intellectual property law. The latest entry is on IP and provides an excellent sense of what we talked about and what we covered in class and in the readings. I am excited to see the class blog develop, if nothing else, because it gives a pretty good sense of the topics we cover and what conversations we have. I used to find it frustrating to have classes literally vanish away after they were done and yet so much labor and time had been put in them! This type of blogging is important as it can provide a tangible and somewhat fixed medium for capturing and preserving what happened (and then free you from having to save boxes of notes that you can collect during college). I know there were a number of times I really really wanted to recall something from one of my undergraduate classes, but since I had finally thrown away the big old boxes of notes and readings from those days, there was no place to look. It was just not practical to lug my boxes of notes from place to place, move to move especially when I only wanted to take a look every few years for maybe one thing. With this type of blog, there is a record of what happened for everyone to share. That said, I am faced with a problem when I teach this class again. Since we provide what I think is a pretty decent account of what we are doing, I will most probably have to put down the blog for a period of time when I am teaching it again though of course the syllabus and readings will also change to some degree.

4 October 2008

Dirk Eddelbuettel: World Marathon Majors

Last Sunday's Berlin Marathon was my fifth and final piece in completing the World Marathon Majors during 2007/2008: after running Boston, Chicago and New York in 2007, and then London and now Berlin in 2008, the set is complete. The idea was born after having run Chicago a few times, qualifying for Boston and winning a New York lottery entry. With friends to visit in New York, London and Berlin, it became feasible. It's been a great experience to run these famous courses in front of large crowds. Conditions ranged from cold, windy and rainy in Boston to way too hot in Chicago, had mixed conditions including a solid rain shower in London and were just perfect in both New York and Berlin. The crowds were awesome in all five places. All in all, these races were a blast -- if you're into long-distance running, give each or all of them a shot.

Kapil Paranjape: Will I be at FOSS.in 2008?

The Omelette Post by Atul Chitnis provoked a lot of discussion and Christian Perrier's response explains the objections clearly. I disagree with them both in different ways. Hence this post. Atul Chitnis is not known for his politeness (unfortunately, like many in the FLOSS community). In such cases, it is best to try to understand the (positive) intent behind the words written rather than concentrate on the words themselves --- the current kabab mein haddi seems to be "low-hanging fruit". I agree with Christian that finding, analysing and fixing bugs ranks up there along with writing programs; especially since many of today's programmers continue to be ''bug-generators'' in the sense of (and in spite of) Dijkstra's article. My reading of the Omelette Post is that hacking should take precendence over talking at FOSS.in 2008 --- a sentiment that I find quite palatable and even tasty! So let's see if we can have a Debian Workout at FOSS.in 2008.

Biella Coleman: If you complain

One thing I am known to do is complain how the public/academic discourse surrounding/around technology/computers is overwhelmingly male (Lessig, Benkler, Zittrain, Shirky and I can go on and on). But one day I realized that if I am bothered by it, I should do more than talk the (often) empty talk of complaint. So I decided to enroll in a day long training for writing OpEds, which kicks off tomorrow. I am not sure if engaging in public debate is what I want to do, mostly because of piling more work and time commitments on a very full plate but I am starting to explore what it means and what it may take to leave the Ivory Tower. Here is a little more info about the OpEd Project:
he OpEd Project - featured by The New York Times, Feministing.com and Katie Couric on CBS News - is an initiative to expand public debate, with an immediate focus on targeting and training women experts across the nation to project their voices on the op-ed pages of major newspapers, online sites and other key forums of public discourse. The lack of diversity on the op-ed pages - which are a source for all other media - deprives the public of robust, democratic debate, especially important in this space which is intended to showcase divergent opinions. It also means we are only hearing from a tiny sliver of the nation’s best thinkers. Imagine a baseball team of only pitchers - how well would it do?

Next.

Previous.