Search Results: "ag"

22 April 2008

Benjamin Mako Hill: Only Frozen Water

Grave In Just Ice Thanks to Matt Lee for helping SVGizing my drawing.

Pablo Lorenzzoni: Considering git...

It has been some time since I ve blogged about Subversion and how I was finding it useful. I ve been using subversion and svk since about that time and I love it. Svk is really great and although it is more an off-line version control than a distributed one, it goes a long way for a former cvs user like myself. Lately, I ve been considering git (isn t everyone?). It was not until I moved to my own hosting (thus having to maintain two subversion trees: the new one and my company s old one) that the whole having a central repository started bothering me. Merging became complex, since now I have two central repositories, and while svk makes it a lot simpler (I just keep a mirror of the two repositories and use svk to merge between them), I began to realize that there should be a better way I ve watched (again) Linus git lecture at Google Tech Talks and decided I was going to try it. First thing that called my attention was how easy it is to share a repository: just copy the .git directory somewhere public (an http server, for instance), and there you have it. This is much easier than configuring modules for apache, or configuring svnserve (and I ve done that a lot in the past 3 years!). For the subversion-only user (one that has never used svk), the carry-all-the-repository-with-you thing may sound strange, but with svk, I was used to mirror the repository, so that s not an important change to me. I could not compare space utilization (and git is advertised for being more space-efficient) yet, but so far the git repositories seems to be a little smaller. I already found it easy to branch using svk (in fact, I used to do that a lot), but git branching is really a plus! You can switch back and forth inside the same working copy (actually I don t think it s correct to call that a working copy) and merging is rocket-fast! Maybe if svk could easily merge between two distinct users without requiring a subversion repository (think about the defunct svl), I would not have been trying git, but One thing that is really missing is the partial checkout. Actually I liked very much that svn/svk feature , and the clean and natural way which they treat directories and files. I understand git is designed with other priorities in mind, but, right now, that feels like missing to me. Maybe it s just a svn/svk habit. All in all, I found git very interesting I am not ready to switch from svn/svk yet, but I ll try git in small new projects and see if I can get used to it.

Matthew Garrett

Oh, and for the love of christ. Australian cultural norms are the correct standard for determining what's acceptable for posting on a site that has clear guidelines against offensive content? Baby Jesus cries with as much pain as if he'd been suddenly violated in an utterly inappropriate way.

Christine Spang: Summer Plans

Last week, eight pounds of Perl books arrived at my doorstep, courtesy of deciding to work for Best Practical this upcoming summer. They’re cool people, very free software friendly, and conveniently located in Davis Square. They are also the makers of RT among other things, which Debian uses for a variety of purposes. It should be a good time. (No, I probably won’t actually be hacking on RT, but exactly what I’ll be working on is as yet undetermined.) Speaking of the summer, I have a vague plan to make a West-coast visit for a week or so at some point. I’ll be hitting at least Seattle and San Francisco; if you’re around either of these areas or possibly even somewhere in between and would like to hang out, drop me a line in comments or via email.

David Welton: To a good home: Linux Incompatibility List

I originally had the idea for a list to keep track of stuff that doesn't work with Linux something like 12 years ago. I built an initial version, that proved reasonably popular at the time, but then the place it was hosted had some problems, and I was busy with other things. I finally got around to building a new version four or five years ago, and it's been doing ok since then, but with a baby on the way, I've been thinking of things to get rid of, and this is not something I do active work on, so maybe it would be best to find a new home for the site, located at http://www.leenooks.com. Here's the catch: It currently runs on my own server, and uses DedaWiki, an open source, Rails-based Wiki, as well as PostgreSQL. You would have to relocate it to your own server. So, if you're interested, contact me: davidw@dedasys.com. If I don't find the right person, no worries; I'll keep maintaining it for a while yet.

Evan Prodromou: 3 Flor al CCXVI

I'm happy to point to the announcement that Wikitravel Press now has a guide to Paris. Paris has long been a targeted city for Wikitravel Press, and I'm really happy we were able to get this book out. Bonus: the Wikitravel Guide to Paris includes maps from OpenStreetMap, the Open Content geo database and mapping system. We've got some new software to overlay Wikitravel listings onto the maps, and it's working really well. Thanks to OSM, editor Mark Jaroski, and managing editor Jani Patokallio for getting this great book out... just in time for Paris spring! tags:

Podcasts I asked a couple of days ago (Journal/30 Germinal CCXVI) about podcasts on the subject of Open Source and Open Content. I wanted to summarize a few that came in through comments on my blog: This has turned into a pretty decent list, but I'd love to see some more diverse discussion of Open Content and Open Source in general. Please, feel free to send more tips. tags:

Vinismo For some reason Vinismo went over some tipping point with StumbleUpon this weekend, and we had a real flood of users from that bookmarking site. I can't say why that happens; I find SU to be a totally opaque Web site and service. In other news, Stevey likes our business cards. Me too! I think they look great. M-C Doyon, the Montreal graphic designer who laid out our Web site, also did our paper branding, and I think she did a great job. tags:

Yay Firefox 3.0 I don't know when it happened, but Firefox 3.0 beta does non-ASCII characters in the address bar correctly. So, if you're reading this entry on my site with FF3, you'll see the in "Flor al" rather than the URL-encoded "Flor%c3%a9al". I also like seeing Japanese Wikipedia pages in the address bar showing up correctly. Nice job, FF3 team. tags:

Planet software should preserve categories So, apparently there's once again rising problems with content drift on Planet Debian. Personally, I think this is a problem with a technical solution. All three main flavours of RSS support post categorization. Many, many kinds of feed software provide categories (see, for example, this feed). If the Planet software would preserve these categories and pass them through to the output RSS feeds, then people who really only want to read about Debian could filter the output feeds for category "debian". People who wanted to know about other parts of their fellow Debianistas' lives would just leave the feeds unfiltered. I'm not sure if the Planet software doesn't support categories in output at all, or if it's just an option that's turned off on Planet Debian. If nobody else wants to take a look, I can look into making this work. It seems like a pretty simple fix. tags:

Uwe Hermann: coreboot projects for Google Summer of Code 2008

The coreboot project (previously known as LinuxBIOS) is taking part in the Google Summer of Code™ 2008 program. This year, the project has been assigned two slots/students who will work on the following projects:
This project aims to integrate into the coreboot BIOS a payload consisting of a minimalist KVM-aware Linux kernel along with an initrd image that contains the tools needed for creating and starting guest virtual machines installed on top of it. The resulting system could host any x86(or x86-64) OS that can run over KVM (almost any major OS does), and there is a great challenge to make it as small as possible, so that it can fit in a 2MB flash image.
  • SCSI booting in coreboot:
  • Currently coreboot can not boot from an arbitrary SCSI controller. There are two solutions for the problem: (1) Use Linux and Kexec. This requires to keep the SCSI driver in the flash chip. (2) Use x86emu/vm86/ADLO and the int13 method. This would allow to use the PCI option rom available on all modern SCSI controllers. So we obviously need a solution based on the latter. This could as well be implemented as a Linux program, as an intermediate payload, or as a shared library. At this point of time, I would like to implemente it as a daemon program. The program needs to catch the int13 interrupt vector that the SCSI option rom installs and make it available to arbitrary (firmware/payload) code trying to load something from disk.
    This should make for an interesting summer with nice improvements for coreboot.

    Jose Luis Rivas Contreras: rtorrent building with GCC 4.3

    The packages is already done, thanks to Bradley Smith for the patch, you can find it here.I'm working right now in the unstable versions but the GCC 4.3 issues remains, in rtorrent there seems the issue isn't solved with the actual patch but libtorrent does, I will ask someone to upload them to experimental as soon as I get something ready.

    Adrian von Bidder: Coffee

    Test successful: the new (and very nice) Apple keyboard (the wired one, if only because I need the numeric keypad regularly) is coffee-safe. Incidentally: Anyobdy has instructions for mapping the “fn” key to function as an insert key? On the console, it produces 00 83 d0, but in X it doesn't send anything (according to xev). Comments welcome. (Martijn proposes to use F13 instead, which I guess I'll do meanwhile.) Update: Hmm. Seems I lost the s key. q, a and y also stopped working for a time but are back again. I hope s will dry out soon, I need it. (and y is again not working. Drat.

    Joerg Jaspert: FTPMaster

    [Warning, long post ahead. If you aren’t interested in Debian or it’s internals or my work - skip it. :) ] So as you might have read here, I got the delegation of the debadmin AKA FTPMaster group lately. I’ve got some pressure to not accept this delegation, but the response to my blog post about it had been extremely positive, everyone said I should not deny it. Knowing to have such a support within Debian is something I really appreciate, making it worth to spent time on my various jobs. Now, lets take this and write a little about what happened since I gained that extra group: Work I did since then: The above should nicely sum up my work in the past few days. Most of it pretty trivial, but still things that have to be done. I plan to keep doing things, slowly going from the trivial stuff to more complicated ones, but there is lots of stuff ahead. Some ideas, and this is a very incomplete list just from my head, there are tons of things that one could do, include Now, do you have any time to kill? Do you want to help? Some things you could do:

    21 April 2008

    Tore S. Bekkedal: GNU Screen/vim love

    When I code, one of the tools I use which I like the most is GNU screen. My current project involves the editing of a bunch of different source files, and often jumping frequently between them. I was spawning windows and trying to edit files that I had already opened in a previous screen, and often ending up with a bunch of windows with files I wasn’t using much at the time. So I did some research on how to optimize use of vim and screen together. The first thing I came up with was getting screen to display a nice bar at the bottom by adding this to my .screenrc: (Thanks, Red Hat Magazine!) hardstatus alwayslastline
    hardstatus string '% = kG [ % G %H % g ][%= % = kw %?%-Lw%?% r (% W %n*%f %t%?(%u)%?% r )% w %?%+Lw%?%?%= % g ][% B %Y-%m-%d % W %c % g ]'
    This gives you a neat and coloured (mmmm… colours…) status bar at the bottom of your screen display, including some info on whether other terminals are attached to that window and such. One thing which would vastly improve the usefulness of this would be if I could get vim to set the screen window title. The escape sequence for doing this is the same as for other terminals, but vim’s terminal information database does not include the relevant entry for the “screen” termtype. So (with help from “frogonwheels” and “godlygeek” in #vim) I put an entry in my .vimrc specifying the escape codes for setting screen’s window title. In addition, I abbreviated the window title string to contain only the file. Here is the relevant snippet from my .vimrc: if $TERM=='screen'
    exe "set title titlestring=vim:%f"
    exe "set title t_ts=\<ESC>k t_fs=\<ESC>\\"
    endif
    A casual glance at my school grades chart will immediately reveal that I am not a structured learner; I’m not the type of user who will, when adopting a tool, begin by reading the manuals. I’m more of a gradual, ad-hoc learner, and I tend to prefer to stick to the defaults whenever possible. Since vim and screen are probably my primary tools for doing work, I should probably do some more research on things like this. These suggestions may be somewhat trivial, but I’ve found them to be quite useful, so I thought it might be useful to someone. Please leave a comment if it was, or if you have any comments (duh!) or suggestions.

    MJ Ray: Dangling the Bluetooth Dongle in front of the Penguin

    [Photo of Dongle]
    Tux likes this fish-like object. I finally got bluetooth file transfer working between my phone and laptop a little while ago. It wasn't particularly hard, although there were a couple of dead ends. The basic bluetooth layer is petty easy. Start dbus, start hcid, start passkey-agent if you've not paired the two. It seems to be a bit simpler to start the pairing from the phone. Then use sdptool browse to check the phone is seen clearly. After that, it got a bit complicated. obexftp worked well enough as far as it went, putting items onto the phone and getting files off the phone, but I couldn't work out how to get some items off the phone. They just didn't appear in the obexftp or obexfs listings. So I wondered if it night be easier to start the transfer from the phone. There's an obexftpd, but I didn't figure out how to send it files. I also tried to compile opd but I think it offer patching for modern gccs. (Anyone got these working?) What I did get to work was sobexsrv - just tell it a directory and it puts any files it's sent there. Works a treat. One other thing that has been really useful is anyremote. It's a command server for the GNU/Linux side and a Java client for the phone. The phone mostly picks from option menus or preprogrammed keys, but editable fields are also possible. You can run any commands that the server configuration allows, including starting file transfers. I think that's possible because remote control and object transfer are on different bluetooth channels, but I don't really understand it yet. I've improved the RSS reader to use xsltproc and added shell commands to it. Once I'm fairly sure it's reliable, I'll upload it near here. (Posted in part due to an ALUG thread which reminded me about this forgotten draft.)

    Erich Schubert: Debian in the Google Summer of Code 2008

    The Summer of Code wiki page in the Debian Wiki has been updated with an overview of the projects that made the race for the 13 slots we have.A separate press release (containing a short paragraph on what each project is about) is in preparation and will be out soonish.

    Joey Hess: planet technology

    We seem to keep having problems deciding what content to put on Planet Debian. I wonder to what extent this has to do with the software running the planet. My experience with using ikiwiki to run Planet Debian upstream is that if a particular feed annoys readers, a page can easily be created that omits that feed (or feeds) while keeping everything else. Anyone can do this by creating a new wiki page and putting something like "!feeds/richard_stallman/*" in the PageSpec. So there's no real reason to drop any feeds for excessive or annoying content. The Planet software makes this harder to do; you have to set up your own server running it, and manually keep your modified feed list up-to-date. So instead there's a general drive to more tightly limit what content is allowed on Planet Debian. The result is that interesting feeds are removed, and that other feeds are self-limited to only technical posts. None of this is making Planet Debian more interesting or useful.

    Holger Levsen: community planets

    The planets on planet.debian-community.org are up again, sorry for the delay in getting this fixed. The reason was a hardware failure of the raid controller, then it took some time to find a new machine and then I first got very busy and then ill.

    If you are interested in another language planet for Debian contributors, please contact us, setting one up is a matter of minutes. And after that, feeds can be added by editing a wikipage. Currently there are only English, Italian and German planets.

    If you want to help with adminstrating the site, please contact me.

    Kartik Mistry: Monday


    * Why Monday sucks? * I agree with Gunnar. +1 for it!

    Gunnar Wolf: What's a blog planet for?

    It seems everybody is ranting in Planet Debian about what our planet should be about, what content should be acceptable, whether technical-only, Debian-only, everything-goes... Even archiving the posts via a mailing-list interface has been mentioned. Besides, following the planet seems to have become mandatory to people linked to Debian, almost as mandatory as following debian-devel-announce.
    I won't bother linking to other posts in this topic, as they are far too many. The whole discussion seems childlike and sterile to me. For different people, Debian means different things - This topic has come up in the planet a couple of times in the past (funny, hah, using posts in mutually-unlinked personal blogs as a way to follow a discussion). And a planet should IMHO cover a specific use case: Providing a place for those of us who think of Debian as a social frame, and value knowing -exactly- the type of information each of us publishes in his/her blog: What's up with Debian-related people's lifes.
    Of course, a large fraction of this information should be somehow technical or Debian-related. But I do value having a place to learn about my peers' life accomplishments. To know if they are going through a hard time. To understand the personal interests of them. Maybe to learn I'm not the only DD who enjoys running (although I'm far under Dirk's or Christian's league) or cycling in a big city (although I lack MJ's political involvement and dedication). I actually like trying to find some logic in senseless Steve-like messages, there are some funny bits in his stuff. I like knowing I can share what I feel important about my life in a simple way with my peers, without having them drop over to my site. And yes, of course I do enjoy learning about the ongoing technical work of the bunch, even if it is often in fields I would not wander into at all (i.e. Simon's frustration with writing device drivers for Windows, Michal's advances on Gammu).
    So... Please stop over-regulation. Leave the planet as it is. If you don't like it, come up with a way to filter and maybe adjust its content based on user profiles. But don't try to censor it.

    Clint Adams: Those who seek power deserve it, right?

    A thousand years ago, I was paid to be an oper (at the time, the common term for an IRCop) on EFnet. I quickly grew to hate it. The unwritten code of ethics amounted to the following: you were entitled to do whatever it is you wanted with your power, so long as you did not step on the toes of your peers or anyone above you in the pecking order. In practical terms this usually meant that you could /kill anyone you wanted as long as he was connected to your IRC server, but to /kill someone on another IRC server was a grave political action. Most of the opers were territorial and petty. My theory on this, extrapolating from several I met in person, is that they were often the targets of abuse in the real world, either for their alternative lifestyle choices, their poor hygiene, or other reasons, and that EFnet was a place that they could feel extremely powerful without burdening themselves with any more responsibility than was sufficient to justify claims that they were maintaining order. People on power trips can very easily claim that they are selflessly acting in the public interest, and without their critical participation, the world would fall into chaos. What is far more likely is that if they bowed out or were removed, they would be replaced by the next set of power-hungry bullies quick enough on the draw. I think that, if they were good people, the EFnet opers of this era would have behaved differently. My painter friend Donald says that I am judgmental and a bad person for expecting them to live up to my moro-ethical standards. I guess he has a point.

    Russell Coker: The Purpose of Planet Debian

    An issue that causes ongoing discussion is what is the purpose of a Planet installation such as Planet Debian [1]. The discussion usually seems to take the less effective form of what is “appropriate” content for the Planet or what is considered to be “abuse” of the Planet. Of course it’s impossible to get anything other than a rough idea of what is appropriate is the purpose is not defined, and abuse can only be measured on the most basic technical criteria. My personal use of Planet Debian and Planet Linux Australia [2] is to learn technical things related to Linux (how to use new programs, tricks and techniques, etc), to learn news related to Linux, and to read personal news about friends and colleagues. I think that most people have some desire to read posts of a similar nature (I have received a complaint that my blog has too many technical posts and not enough personal posts), but some people want to have a Planet with only technical articles. In a quick search of some planets the nearest I found to a stated purpose of a Planet installation was from the Wiki to document Planet Ubuntu [3] which says ‘Subscribed feeds ought to be at least occasionally relevant to Ubuntu, although the only hard and fast rule is “don’t annoy people”‘. Planet Perl [4] has an interesting approach, they claim to filter on Perl related keywords, I initially interpreted this to mean that if you are on their list of blogs and you write a post which seems to refer to Perl then it will appear - but a quick browse of the Planet shows some posts which don’t appear to match any Perl keywords. Gentoo has implemented a reasonable system, they have a Universe [5] configuration which has all blog posts by all Gentoo bloggers as well as a Planet installation which only has Gentoo related posts. It seems to me that the a reasonable purpose for Planet Debian would be to have blog feeds which are occasionally specific to Debian and often relevant to Debian. Personal blog posts would be encouraged (but not required). Posts which are incomprehensible or have nothing to say (EG posts which link to another post for the sole purpose of agreeing or disagreeing) would be strongly discouraged and it would be encouraged to make links-posts rare. Having two installations of the Planet software, one for posts which are specific to Debian (or maybe to Debian or Linux) and one for all posts by people who are involved with Debian would be the best option. Then people who only want to read the technical posts can do so, but other people can read the full list. Most blog servers support feeds based on tag or category (my blog already provides a feed of Debian-specific posts). If we were going to have a separate Planet installation for only technical posts then I expect that many bloggers would have to create a new tag for such posts (for example my posts related to Debian are in the categories Benchmark, Linux, MTA, Security, Unix-tips, and Xen) and the tag Debian is applied to only a small portion of such posts. But it would be easy to create a new tag for technical posts. Ubuntu is also the only organisation I’ve found to specify conditions upon which blogs might be removed from the feed, they say: We reserve the right to remove any feed that is inaccessible, flooding the page, or otherwise interfering with the operation of the Planet. We also have the right to move clearly offensive content or content that could trigger legal action. That is reasonable, although it would be good to have a definition for “flooding the page” (I suggest “having an average of more than two posts per day appear over the period of a week or having posts reappear due to changing timestamps”). Also the “could trigger legal action” part is a minor concern - product reviews are often really useful content on a Planet… Some time ago my blog was removed from Planet Fedora for some reason. I was disappointed that the person who made that change didn’t have the courtesy to inform me of the reason for their action and by the fact that there is no apparent way of contacting the person who runs the Planet to ask them about it. Needless to say this did not encourage me to write further posts about Fedora. If a blog has to be removed from a feed due to technical reasons then the correct thing to do is to inform the blogger of why it’s removed and what needs to be fixed before it can be added again. If a blog is not meeting the content criteria then I expect that in most cases the blogger could be convinced to write more content that matches the criteria and tag it appropriately. Having criteria for some aspects of blog quality and encouraging the bloggers to meet the criteria can only improve the overall quality. Currently there is a Planet installation on debian.net being recommended which is based on Planet Debian, but with some blogs removed (with no information available publicly or on debian-private as to what the criteria are for removing the blogs in question). It seems to me that if it’s worth using Debian resources to duplicate the Planet Debian then it should be done in a way that benefits readers (EG by going to the Planet vs Universe model that Ubuntu follows), and that if blogs are going to be removed from the feed then there should be criteria for the removal so that anyone who wants their blog to be syndicated can make whatever changes might be necessary.

    Adam Rosi-Kessel: In Search of Low-Calorie Slashdot Replacement

    I reluctantly include Slashdot in my Google Reader subscriptions. I’ve yet to find another source with the same breadth of news coverage that approximately matches my personal and professional interests. The problem is that I’m increasingly annoyed by the editorial slant. The comments have always been hit-or-miss — mostly miss — but as I’ve gained expertise over the past six or seven years (particularly in legal topics), I’ve noticed that the article summaries themselves are invariably written by someone who has no idea what they are talking about. So I ask the blogosphere: what’s a good Slashdot substitute? I’m looking for something with a good mix of breaking science, technology, Internet, law, and free-speech type stories, but without everything that makes Slashdot irritating. Technorati Tags:

    Next.

    Previous.