Search Results: "ag"

28 November 2006

Antti-Juhani Kaijanaho: Upgrading WordPress the sane way

I finally got around to upgrading the bunch of WordPress blogs that I administer. I do not use the the Debian package, instead each blog is a separate copy, some with customizations. The official instructions make it a pain to upgrade customized WordPresses, so I have used another technique for a while now. This technique assumes a Unix-style system with all the usual goodies installed and command-line access, as well as Unix competence of the person performing this operation. I leave it to others to write step-by-step instructions for people lacking such competence (feel free to leave a comment). Step 0: Back up all your WordPress installations! Step 1: Make sure that you have a copy of the vanilla WordPress directory (unpacked from the zip or tarball and not changed afterward) for the version that you are currently running. I have it (in this case version 2.0.4) as the directory wp-2.0.4. Step 2: Download the new version, unpack it and rename the unpacked directory to include the version number (in this case, wp-2.0.5). Step 3: Create a patch file for this upgrade by running diff -Naur wp-2.0.4 wp-2.0.5 > ~/wp-2.0.4-2.0.5.diff. Step 4: Eyeball the patch to see if it looks sane. (I have on one occasion created a patch that deletes the whole WordPress installation. That is not fun. So check that the diff is sane!) Step 5: Apply the patch to your WordPress installation by changing to the WordPress installation’s directory and running patch -p1 -i ~/wp-2.0.4-2.0.5.diff. Step 6: If patch rejected some hunks, eyeball the .rej files to see if you need to manually merge the changes in. This should only happen if you have customized the installation. Step 7: Run the database upgrade script by going to the admin page and following the instructions. Step 8: Verify that it all works. *** It is also possible to manage the installations in darcs or in other version control systems. I haven’t bothered with that yet.

Stefano Zacchiroli: vim ctrl r

Vim's Feature of the Day #1: i_CTRL-R I'm really astonished of how much there's to learn about Vim and how much you can forget about it, especially because I consider myself a rather power user of my beloved editor. Digging into my ~/.vim/after/ftplugin/tex.vim I found some mappings that were laying there from quite a while (I think I wrote them something like 4 years ago):
vmap ,b "zdi\textbf <C-R>z <ESC>
vmap ,e "zdi\emph <C-R>z <ESC>
vmap ,t "zdi\texttt <C-R>z <ESC>

Looking at them I went through :help i_CTRL-R ... and it's wonderful! Hitting CTRL-R in insert mode Vim enters in a "waiting for a register name" mode and when received it inserts its content without leaving insert mode. That's amazingly quick, and I'm already addicted to two combos:

Uwe Hermann: German people: do you care about democracy and your right to vote?

If yes, please consider signing this online petition which asks the government to completely prohibit the usage of voting machines in Germany. Actually, you should sign this replacement petition, as the first one was getting "too big", a.k.a the software or server they use couldn't handle the sheer numbers of recorded votes anymore (ironic, isn't it?)... Note: the deadline for the petition is today, i.e., November 28, 2006! Ca. 45.000 people have signed already. If 50.000 signers are reached, there's sort of a guarantee that the government has to formally put this issue on their agenda (or something in that direction, I don't remember the exact details right now). If you haven't followed the latest news regarding the voting machine issues, I urge you to get informed by reading the recent blog entries of Frank Rieger and Tim Pritlove (for example). The Chaos Computer Club (CCC) has a very good collection of information and further readings. Take a look.

Norbert Tretkowski: Planet Debian

tretkowski@rollcage:~% dog http://planet.debian.org/ grep -c -i ubuntu
28
tretkowski@rollcage:~% dog http://planet.debian.org/ grep -c -i canonical
12

MJ Ray: Bad Accessibility Loses Sales

Argos are a total pain. Their web site is unnecessarily complicated. If you want to do the basic action of buying something then you need to have a browser with all the trimmings and relaxed security, but even then, you might not be able to find what you want where you want to buy it. When will people wake up to the fact that Sometimes amateurish websites just put you off entirely... [Digital-Scurf Ramblings] Odeon seem to have finally got its act together - I don't agree with their priorities, as the extra investment in the web site seems to have been balanced by reducing newspaper advertising, but I can finally find film information with any browser I've tried so far. Does that leave Argos as Britain's Biggest Bad Online Retailer?

MJ Ray: TPM/DRM and Creative Commons (2)

Rob Myers commented:
"Since all CC licences allow NC copying and distribution, any DRM that limits copying in any way is a breach. Or any DRM as it is also known. And since the CC licenses all support fair use and DreAm (an oxymoronic idea that I thought had died of lack of interest) restricts it, that's another problem. Not to mention how harmful electronic enforcement of CC licenses would be."
That's an argument I've heard from several CC supporters, but I don't accept it: fair use is inconsistent globally. What is fair use in the USA might not be fair dealing in England, or the other way around. As to whether any DRM is possible under CC licences, there's the small matter of Lessig's "praise for better DRM" which seems to acknowledge the existance of TPMs that restrict in a CC-OK way. Rob continues:
"Mako's arguments are a rehash of ones that were considered in depth when the debate was happening. Terry covered most of them [in an article on a magazine web site]"
Maybe the points Mako presents were considered, maybe they weren't, but it's very hard to tell from the limited transparency of CC. I think the points are clear, direct and difficult to argue against - that may be why it's so hard to get a good debate with CC about this. What's more, Terry Hancock's article is a rehash of his old list posts. I think Terry's points were all covered in mailing list discussions and they don't even try to make a case for the TPM-ban in CC-BY. I like recycling, but it's disappointing to see people use the press to recycle old threads. Also, I don't find it particularly surprising if someone writing for a magazine web site isn't entirely comfortable with some forms of redistribution. Rob finishes with:
"And I would add that, as someone who has installed GNU/Linux on my iPod, who has recently read the Yellow Dog Linux announcement for the PS3, who uses their PS2 as a CD and DVD player, and whose son seems to get MP3s, images and movies onto his PSP OK, I do not understand the argument that the best way of "helping" users is to help third parties trap them under DRM regimes rather than assisting users in installing and using free software."
Maybe that's not understandable because it's not an argument that's used, except as a straw man by pro-format-discriminators? Personally, I think it's a pretty poor show that you have an iPod, PSP and so on - weren't Apple's and Sony's DRM-mania well-known when they were bought? Which brings me on to why I feel locked-media distribution is worthwhile: educating people to make better device choices next time. I bought an Ogg player this time - hearing Cory Doctorow's talks as MP3 was partly why. If CC 2.0 had had an aggressive-patent ban similar to CC 3.0's TPM ban, maybe that wouldn't have happened.

Andreas Barth: Bug fixing

I have been away for 5 days without any net access (and had a few hours of mail reading on Sunday evening). On Monday morning, the trend on the RC-Graph didn't looked too good , so I invested resolving RC bugs. A couple of NMUs later the graph now looks better - but of course, there is much more that needs to be done. Beside fixing packages, I did the "usual" small jobs, including reviewing cyrus-sasl2, answering lots of mails, and so on.

Joey Hess: end to second-guesing

A couple of years ago I had a nice chance to be employee approximatly #10 at Caonical and work on Ubuntu. I turned them down at the eleventh hour, and have been second-guessing that decision on and off ever since. Today I realized I can stop worrying about whether I made the right decision back then, because it seems very likely that if I had joined them as employee #10, unless my contributions somehow made it develop much differently than it has, I would have left Canonical by now, for one reason or another.

Matthew Palmer: VLAN adventures

Have you ever had a need for a large number of "real" network interfaces on a Linux box? For security reasons, you don't just want to hook everyone up to a single switch and use virtual interfaces (because it's too easy for one of the connected devices to play silly buggers with his neighbours). Up to a certain point, you can stuff more NICs into a box, and when it fills up you can switch to those outrageously expensive 2- and 4-port NICs. But eventually you're going to run out of space[1] or money. At that point, you need something more interesting. For me, this week, that "more interesting" has been Ethernet VLANs. Linux Journal has a good intro to the technical aspects of how to setup VLANs and Linux. VLANs are some crazy stuff. They're implemented by wrapping a little number around every Ethernet frame indicating which VLAN the packet is "on", and the switch (you need a higher-end device, appropriately configured) makes sure that packets don't roam onto ports they're not meant to be on. For a single switch, this isn't very interesting, and you don't really need an IEEE standard to make it work -- just a lot of little jumpers. However, VLANs are mostly useful on larger networks, which tend to use more than one switch. So you need a way for your VLANs to roam amongst your switches -- hence the packet tagging. You stick the tag onto the packets and fling them off to another switch, and packets coming in with the tag are corraled into their VLAN. Naturally, you don't want end-user devices whacking their own VLAN tags onto packets (untrusted data, and all that), so you define most of your ports as being "untagged". Packets that come in on these ports are treated as regular ethernet frames and tagged with the appropriate VLAN ID, and packets that go out have their VLAN IDs stripped before being sent. (This implies that you can tunnel VLANs in VLANs, and I'm pretty sure that is doable in most switches, modulo some nasty problems that can, and probably will, occur). The ports that aren't designated "untagged" spit out tagged packets -- and this is where my interest lies. Like most every other computer-related standard, Linux can decipher and work with VLAN tags (the 8021q module is what you're looking for). You just load up the module, hook your NIC into the appropriate port on your very expensive switch, define your VLAN tags with vconfig, and suddenly you've got vlanN interfaces, which map to real RJ-45 ports, and you can hang network devices off these and get lots and lots of "real" network interfaces on your Linux router. It's all so simple, right? Nothing ever is, of course. The trials and tribulations I've had over the past two days have included: Thankfully, once all those dramas were done, the whole thing just kind of fell into place, and now I've got a machine which has up to 2048(ish) network interfaces (with huge, glaring caveats on that upper bound, of course). With a bit of luck, the live installation in a couple of days will go smoothly. You can stop sniggering now.
1. In this case, there wasn't a lot of space to begin with, as it's a 1RU box I'm working on, and the 4-port NIC didn't want to place nice with me for some reason anyway.

Benjamin Mako Hill: Bring the Bling?

I'm been perplexed by the recent fracas around the possibility of Ubuntu shipping non-free drivers by default as part of the feisty release goal to bring the bling. The issue has been discussed by many people, most recently and eloquently in a blog post by Scott James Remnant. I have never been 100% comfortable with our (Ubuntu's) decision to ship proprietary drivers. The Ubuntu philosophy document -- which Mark Shuttleworth and I drafted originally -- says quite unambiguously:
Every computer user should have the freedom to run, copy, distribute, study, share, change and improve their software for any purpose, without paying licensing fees.
I believe this deeply. Consequently, I feel that binary drivers in Ubuntu are, and always have been, a failure to live up to our principles. If our philosophy document is still representative, most people in our community should be a little uncomfortable with them -- even if they think, as most of us do, that shipping them is the correct thing to do. Early on Ubuntu decided that binary firmware and hardware drivers would be distributed and quasi-supported in restricted. While not completely comfortable with the move, I could understand and defend it for three reasons:
  1. The drivers were easily removable and not enabled by default unless necessary to achieve functioning hardware.
  2. As part of this process, we promised to work with vendors to accelerate the freeing/open-sourcing of their drivers.
  3. Perhaps most importantly, I couldn't imagine not using them if it were the choice between non-free drivers or inoperable hardware.
The proposal to include proprietary nVidia driver in place of the existing free nVidia driver is important because it changes, or eliminates, the first and third justifications. Since the first issue has been discussed in depth, it seem appropriate to focus on the third and final point. The point is perhaps best introduced with an observation:
While I have met many people who research and buy hardware to avoid the need for non-free drivers, something I do myself, I have never met anyone who voluntarily chooses inoperable hardware on a computer they use over working hardware through a non-free driver.
While not airtight, this observation is precisely why the old policy of using non-free drivers only when no free drivers exist works so well. By effectively synonymizing use of the non-free driver with use of the hardware, the crisis created by non-free drivers is rendered paradoxical: anybody using a piece of hardware that only works with non-free drivers is, by definition, either using non-free drivers or not using the hardware. The only way to not use non-free drivers in situations where no free drivers exist is to not use hardware that requires them. If you use different hardware, you will not need to use non-free drivers. This important justification is completely inapplicable to the proposal to include non-free drivers in place of free (but not perfect) alternatives. Second, while shipping non-free drivers is wrong because we lose our freedom and violate our philosophy, the desire for basic hardware support is universal and important enough that it's defensible. One reason that the "binary by default for bling" situation alarms me is that I don't believe that the desire for desktop bling is as universal, or as strong, as the desire for working hardware. An analogy might be stealing food to feed your family and stealing a CD from the record store. Both are wrong because stealing is wrong, but I have a lot more sympathy for the hungry thief in the first example because CDs are not as necessary as food and because many people would rather go without a new CD than steal. We can ask: "Which is worse: selling your soul for a decent job or selling your soul for a PS3?" In an absolute sense, neither is worse; but it's easier to support the former than the latter. I'm very impressed with Beryl -- but I have trouble empathizing strongly with the need for a spinning desktop cube. New users may be impressed and attracted to an Ubuntu desktop powered by proprietary drivers. They might also be impressed by proprietary applications. However, it is self-defeating to attract new users to our free platform and principles by compromising our core values. Many users already make the decision to use non-free video drivers and Ubuntu makes it very easy to do so once they have made that choice. Installing binary drivers by default is choosing for the large number of users who will stick with any default. It may be a conservative stance but as long as we believe that a non-insignificant number of users would choose to live without bling before compromising Ubuntu's philosophy and goals, we should make the difficult decision to side with freedom by default. When discussing this issue, many people say, it's not my decision or it isn't my call. Regardless of whether anyone agrees with me and regardless of who the final decision is up to -- and it's not clear to me now -- I believe that the Ubuntu community has the power to inform and shape the development of their distribution. As the Ubuntu community, we can make our position heard. The best place to do that right now seems to be the Accelerated X specification comments page. One can also email the the Technical Board (for technical comments) and the Community Council (for principle or philosophy related issues).

Sven Mueller: Canonical and Debian - friend or foe?

Pointed at the issues by Josselin Mouette’s post, I got aware of a list of issues posted by JP Rosevear, which is a reply to Mark Shuttleworths post to the opensuse mailinglist. Note especially point 2, which is: “Preventing the Debian GNOME maintainer from updating GNOME packages until after Ubuntu LSO had shipped because you had hired him.” If this issue is true, it’s the worst thing I ever heard of regarding Canonical. I mean it’s bad enough that points 1 (“Having a stated policy of not funding any significant new software development because the Return on Investment is not good enough”) and 3 (“Not releasing any source code for launchpad/rosetta/malone to maintain a competitive advantage”) certainly are true (even though I can’t prove and therefor don’t 100% believe the second part of #3). But unless there is a very good reason to delay the submission of the patches developed to “upstream”, Debian.
It’s bad enough that Canonical hired the most active Debian Developers, depriving Debian of much of their time, while not really supporting Debian (i.e. while not actively submitting patches to Debian). It would have been better for the community if Canonical had hired less active DDs (or even non-DDs). Sure it would have been harder to select some sufficiently qualified people for the jobs, but the total outcome whould have been better IMHO (getting time from previously uninvolved people, while keeping the existing contributors). Anyway, I really would like to know wether the mentioned point #2 is true, and if so wether any valid reason for doing so could be given before I set my opinion about this issue in stone. One thing is sure however, I’m becoming more and more critical regarding Ubuntu and Canonical over time while I once hoped that the opposite would become true for those criticizing Canonical at that time. Actually I still hope so (and thus I hope reason to become less sceptical again).
Another thing is also sure: If Canonical wants to use Debian as a base for much longer, it should make damned sure to work with Debian more actively instead of seemingly working against it (more or less openly). Update: As also pointed out in a comment below, a post by Scott James Remnant proves point 1 from the the aforementioned list and gives a further hint that point 3 might be true. More precisely it says “we have a policy of not doing our own software development, but only packaging what others have developed”, which probably means “not doing our own major software development”, since - as a comment to that post also says - Canonical did some software development, like launchpad/rosetta/malone and some other relatively small projects.

27 November 2006

Biella Coleman: Thomas Szasz

I just finished a pretty good article The Myth of Thomas Szasz, about the man who most famously attacked the psychiatric profession in part by claiming mental illness was manufactured, a myth. In a nutshell here is the point of the article:
“It is hard to doubt the reality of mental illness, especially when the suffering of affected individuals is so complete and the impairment so extreme, when psyche and identity are crippled almost beyond repair. But it is also remarkable how much of modern psychiatry is still theoretical rather than empirical, and how many of the supposed mental illnesses that appear (and multiply) in the Diagnostic and Statistical Manual of Mental Disorders have no known biological underpinnings or explanations. Although Szasz s critique often became a caricature, his intuition about the limits and deformations of modern psychiatry cannot be ignored. Many sick people have surely benefited from psychiatric treatment, both talk therapy and pharmacotherapy. But psychiatry s long history of error from snake pits to ice baths to spinning chairs to electroshock to lobotomy should give us pause. Skepticism is not backwardness, even if Szasz often took his skepticism to rhetorical extreme”
The part I found most interesting (and now I must read it):
A piece in The New York Times Magazine[by Szasz] titled Mental Illness Is a Myth reportedly induced more reader response than any article in the magazine s history. If he had preached from the pulpit with The Myth of Mental Illness, he had now nailed his thesis to the church s front door.
I must must check out the reader response! For those who know little about what came to be known as anti-psychiatry, this article is worth reading. It is written well and presents the virtue of skepticism, even if extreme, which is what Thomas Szasz, was all about. My only complaint is that if you know nothing of anti-psychiatry or the visible and patient-led challenge to psychiatry that followed in the 1970s, you would think that Thomas Szasz was entirely in a class of his own. While he may be the most famous figure, and may have certainly led the charge in many resepcts, there were others (that is critical psychiatrists like him (and not just in the US) not to mention wide spread critique from various social quarters. But a great great article otherwise.

Russell Coker: when you can't get along with other developers

Many years ago I was involved in a free software development project with write access to the source tree. For reasons that are not relevant to this post (and which I hope all the participants would regard as trivial after so much time has passed) I had a disagreement with one of the more senior developers. This disagreement continued to the stage where I was threatened with expulsion from the project.

At that time I was faced with a decision, I could have tried to fight the process, and I might have succeeded and kept my position in that project. But doing so would have wasted a lot of time from many people, and might have caused enough productivity loss for enough people to outweigh my contributions to the project for the immediate future. But this didn't seem very productive.

So I requested that my write access to the source tree be removed as I was going to leave the project and unused accounts are a security risk.

I never looked back, I worked on a number of other projects after that time (of which SE Linux is one) and the results of those projects were good for everyone. If I had stayed in the project where things weren't working out then it would have involved many flames, distraction from productive work for everyone, and generally not much good.

The reason I mention this now (after many years have passed) is because in another project I see someone else faced with the same choice I made who is making the wrong decision. The people who are on the same private mailing list as me will all know who I am referring to. The individual in question is appearently suffering health problems as a result of stress caused by their inability to deal with the situation where they can't get along with other people.

My advice to that person was to leave gracefully and find something else to work on. If you don't get along with people and make a big fuss about it then they will only be more glad when they finally get rid of you. Running flame-wars over a period of 6 months to try and get accepted by a team that you don't get along with will not do any good, but it will convince observers that removing you is a good idea.

Ben Armstrong: Home video hub on a shoestring

In our family, we have centralized all our best entertainment technology in a single system, a white box amd64 with PVR, 3D graphics, 1G, a 21” monitor, DVD burner and VCR. A number of older, far less capable systems have always surrounded this “hub”. A K6-2/400 with a less-than wonderful ATI Rage IIc graphics card presently serves as my wife’s system, and my PII/300 laptop roams the house on wireless B. This has always been the model for our home network, dating back to the late 90’s when the hub in our cramped apartment was a P/100 delivering sound through a $30 pawn-shop stereo to two main rooms, and the satellite node in the family room was a DEC VT-420 on a long serial cable. So, house-wide delivery of sound has always been possible. But doing the same for video remained unsolved until just this weekend. Kudos to the Videolan team for making it possible. A number of years ago, I recognized their vlc player was ideal for playing DVDs on my K6-2, handling the job with less CPU and less frame drop than other alternatives at the time. Not too long afterwards, though, we upgraded our hardware so saving CPU cycles was no longer an issue, and switched to other players to take advantage of features they offered over vlc. But a recent email from a friend brought me back. This friend asked if I had seen a certain Linux documentary video he had found. I hadn’t, and was intrigued. But since the hub was tied up by the kids at that moment, I figured I’d try watching on the old PII laptop. I didn’t really think it would work, but remembering how well vlc did on my other old hardware, I gave it a try. It worked! No frame drop at all. Buoyed by that victory, I recalled that I had downloaded the Debconf 6 DVD ISOs some days ago, but had not yet been able to watch them. You probably can guess why … yup, the single hub system, the only one really capable of doing a good job displaying video, was pretty much always tied up by various other family members. Now, I knew there was no way I could get those DVDs onto the laptop, as it has no drive and only a 4G hdd. Nor was I willing to go to the bother of ripping individual tracks to transcode and send over one at a time. But I then recalled that vlc, as well as being an excellent standalone player, is primarily the client for a streaming video system. So I set out to learn how to stream video. Back when I was first introduced to Videolan, I knew there was a server program, vls. I had a quick look at that and was overwhelmed by the wide variety of possible MRLs and codecs, and a bit mystified as to which magic spells were needed to make it stream to the laptop. It then occurred to me I had probably plunged in too quickly, and should back off and go look for more docs than just the man pages. Sure enough, they have plenty of excellent docs, leading to the discovery that the vlc gui itself has easy to use Wizard and Open dialogs to set up streaming. With that sorted out, I was streaming in no time. At this point, I was delighted to discover that I could successfully stream a 1024 kbps mp4 stream across wireless B form the basement to any other room of our two-story semi. And ever since then, I’ve been having great fun with the family, trying a wide variety of other video sources lying around: music videos, home videos made by friends, TV shows recorded from the PVR, DVDs direct from disc, and yes, finally, those Debconf 6 ISOs. I tell you, it’s like Christmas come early! Thanks, Videolan. You’ve made my week.

MJ Ray: Satellite TV Scanner

Replaced satmania with satscan on my TV guides page.

Steve Kemp: Blame it on rock and roll

I spent a while on IRC today, rare for me, and one of the repeatable topics of conversation was showing mugshots of people in chat. I wrote a trivial /showface command for irssi which just spawned mozilla to show a hackergotchi from planet.debian.org and that was neat. However it suffers from the problem that you cannot spawn a graphical application from inside Screen easily. So I came up with a cunning alternative: using the DBUS notification deamon. So now I have face.c which uses wget to download an image, then dbus to display it. Compile it like this:
apt-get install libnotify1 notification-daemon dbus
apt-get install libgtk2.0-dev libglib2.0-dev libnotify-dev
	
gcc  pkg-config --cflags gtk+-2.0  \
     pkg-config --cflags glib-2.0  \
 face.c -lnotify -o face
	
Now copy the face script to drive it and you can run /showface skx and it will show you my image. Neat hack. (I suspect it will fail if I logout of X and restart - then reattach to screen since my DBUS identifier/session will be different. But I’m still pleased that I didn’t have to quit the currently open screen session and I can make graphics appear from within it) Update: now with caching and error detection. It will also disable itself for channels not matching ^#debian*

Jon Dowland: Thecus

Yesterday I installed debian on my thecus n2100. Thanks to Martin Michlmayr for putting up with my neurotic questions during this process. Normally, this would take about 2 hours. Unfortunately I hit a bug in the r8169 network driver (or the hardware) which made the process excruciatingly slow: over 8 hours. I did delay the process somewhat by going for a stable installation first time through. You need to go for etch, for anyone following along at home. I have two hard discs in this box and I wanted to use RAID-1 for the root filesystem. Actually, the two discs were already in a linux RAID-1 set, with superblocks, an ext3 filesystem and some files, from when I was using the default thecus firmware. The following approach lets you setup RAID in the installer and preserve any existing data. You will need to have at least one connection to the installer running a shell, in addition to the one running the installer. When you enter the disc partitioner stage, you will need to fetch the udeb which gives you the md module. For the current thecus installer image, that's md-modules-2.6.18-3-iop32x-di_1.5_arm.udeb. wget it from a mirror (path pool/main/l/linux-kernel-di-arm-2.6) and udpkg -i it. Then restart the partitioner. To preserve the contents of the RAID-1, you might be able to select "don't wipe this partition", and just make sure nothing on it would clash with the directories that Debian will create. I didn't take this approach. Instead, you can drop one of the discs from the mirror, continue with the installation as normal, copy the data back across after, and re-add the disc to the mirror set. Before you select your filesystems in the partitioner: Now feel free to let the installer stick a new filesystem on the RAID set, and install the base system etc. Once the thing has booted: Periodically check on the rebuild status with mdadm -D /dev/md0. One other thing I would strongly advise is getting the installer's debconf priority to medium or lower before you get the base system installed, so you can skip the bootloader / flashing stage. Update: I've clarified the following paragraphs. At present, the default etch kernel is 2.6.17. The network device in the Thecus is not supported by this kernel, so you have to manually install a particular 2.6.18 kernel prior to rebooting, or you will not be able to communicate with the machine once it boots. Martin makes this very clear in his instructions. However, if you have no experience using a d-i which flashes the kernel (as appose to say, the bootloader prompts you get when doing an x86 install, for example) you may not be aware that by default, the flash stage proceeds without prompts. That means that if you do not prevent it from doing so, there will be a window between the installer flashing 2.6.17, and you manually installing 2.6.18, where the thecus will be in an unbootable state, should you suffer a power cut or similar problem. In my case, I left the base system being unpacked overnight (due to the fact the network was so slow). So, that window was several hours wide. This is only a temporary situation, as the release team plan to have 2.6.18 available for Etch, and the patches for the Thecus hardware are steadily working their way into the mainline kernel.

Ian Murdock

Me: “[T]here are some pretty significant problems with the new [del.icio.us] extension, the biggest in my view being that there s no way to change the sort order of the bookmarks within your favorite tags.” An update came across the wire over the holiday weekend, and it is now possible to sort bookmarks alphabetically within your favorite tags.

Holger Levsen: tag your packages in no time

The new web-editor for debtags is amazing! Very intuitive and easy to use, I just tagged my packages in less than five minutes :) Try it.

You'll get quite sensible suggestions for tags and the interface to view and choose from all existing tags is, well, very intuitive and easy to use! :) Choose 'view all tags' to get a view on all facets (a la categories)...

Try it! :)

And if you're bored (which I'm not...), there is a nice overview of the 150 most popular packages without tags. Great work!

MJ Ray: MacDonalds Patent Sandwiches

I wouldn't usually link an article from the Metro free paper but this is beyond belief:
"The fast-food chain has applied for a patent relating to the 'method and apparatus' used to prepare the snack."
They claim their novel and inventive step is 'simultaneous toasting of a bread component'. You know, like the bun toaster on top of my electric grill.

Next.

Previous.