Search Results: "ag"

14 October 2008

Peter Van Eynde: Vista assymmetical speed problems

My wife has a laptop running Vista because she wanted to try out the operating system before having to decide on using it at work.

I called her various names because of it, but that didn't help :-).

So we have this setup with an SMC wireless router/AP talking to a Cisco 837 router that does the internet part. Upstairs we have a 'server' that is connected via Powerline IP-over-power, downstairs we have the Dreambox that is connected via a normal Cat5 connection.

In the last few days my wife complained that it was very slow to download media from Frost. Working at TAC having a network problem at home is almost a personal offence :-) so I decide to take a look and I find using iperf the following speeds:

frost (debian) --cat5--> sharrow (debian): 35 Mbit/sec
frost (debian) ---WL-cat5-> sharrow (debian): 18 Mbit/sec
sharrow (debian) ---WL-cat5-> frost (debian): 18 Mbit/sec
sharrow (debian) --cat5---> frost (debian): 35 Mbit/sec
frost (debian) ---WL---> martha-jones (vista): 0.2 Mbit/sec
sharrow (debian) ---WL---> martha-jones (vista): 12 Mbit/sec
sharrow (debian) ---cat5-SMC-WL--> martha-jones (vista): 6 Mbit/sec
martha-jones (vista) --WL-cat5-> frost (debian): 18 Mbit/sec
martha-jones (vista) --WL--> sharrow (debian): 18 Mbit/sec
martha-jones (vista) --WL-cat5-> sharrow (debian): 18 Mbit/sec


This made no sense at all. The speed halved going from a WL->WL to a WL->cat5 connection but only in one direction!

So having isolated the problem to the Vista machine I started looking round and I found a note saying that running netsh interface tcp set global autotuninglevel=disabled in an 'Administrator' cmd window will fix the problem.

Now I'm very weary of changing the TCP/IP options of the operating system. In most cases the 'tips' you see flying round the internet have no meaning at all and sometimes make the situation worse rather then better.

However I did find this on a Microsoft Technet site.... Hmm

So in the end I try it and modify the setting, disconnect and reconnect to the wireless and:

frost (debian) ---WL---> martha-jones (vista): 18 Mbit/sec
sharrow (debian) ---WL---> martha-jones (vista): 18 Mbit/sec
sharrow (debian) ---cat5-SMC-WL--> martha-jones (vista): 18 Mbit/sec


Aah, finally I could tune Vista so that it has the same speed as an untuned Debian machine. I only took me 2 evenings worth of work...

Dirk Eddelbuettel: RPostgreSQL 0.1.0

As part of the Google Summer of Code program for 2008 (which I mentioned here and here), Sameer and I are happy to announce that RPostgreSQL is now on the CRAN mirror network for R. RPostgreSQL provides a (DBI-compliant) interface between R and the Postgresql database system. I also just sent this short announcement to the r-packages list.

Joey Hess: NC car curse, part 4

I'm getting to the point that I fear driving in North Carolina, because an exceptional percentage of car breakdowns happen to me there. The most recent one actually didn't happen in state, I'd just passed the TN border and was coming down the exceedingly twisty road to Shady Valley when I lost the engine on Mom's car. About the time I gave up on letting it cool down and trying things, a white convertable pulled up and I got a lift down to Shady. Since this was a beautiful Sunday, the country store there had at least 500 motorcycles out front. I borrowed one of the bikers' cell phones, called a tow, and sat in a rocker on the porch and watched the insanity for an hour. The good thing about driving old cars that sometimes break down is that you do get used to dealing with it. I actually enjoyed 95% of the incident. Oddly, the car started without problems the next morning. Curse indeed.

Joey Hess: electic bike

I decided to get an electic bike when my car died. Couldn't quite stomach buying a new gasoline vehicle at this point in time, didn't really feel like another used car, and the available electic cars are still too new/expensive/hard to find. While there are some neat NEVs that are not too expensive, they're too limited to be worth my money, and electic bikes fit into the same general niche. (So do electic scooters, but I didn't want to spend that much money on an experiment..) My first try was a disaster. I was thinking that a large cargo capacity would be a good thing, so I gravitated toward trikes. However, the one I tried turned out to be a lemon in several ways, and suffered a catastropic and dangerous controller burnout. So I learned that this electic bike industry is pretty rough and ready with a lot of junk to avoid. I also learned that I don't enjoy riding trikes. The second try was a R Martin LX1, which my dad had researched. I got it yesterday, and have ridden it some now, and I agree that it's a good one. As a bike, it's well built, has a good back disc brake and decent front brake (will be better once I bring it to a bike shop to adjust it better), has a good derailer, and rides well. I'm no expert but it seems about as good as the bike I used to commute with, though the frame is a bit heavier. (IIRC, it was also at least $200 cheaper than that bike!) On the electic side, it has a relatively small and light lithium ion battery; the motor is mounted in the hub. It's strong enough to go up hills on its own if you really want it to, but you will end up pedaling to assist, which is good. I'm undecided whether the six gears are enough ... Seems like I might want a faster gear, to be able to assist the motor more at high speed. I haven't wanted a lower gear yet, but I've not tried to do any hills without the motor's help. The electic controls are ok, but not perfect. I worry about accidentially twisting the throttle, although it has to be turned quite far to engage the motor. Ideally, the pedal assist would turn the motor on exactly when you pedal, and porportionally to how hard. Instead, there'a a lag, and doesn't care how hard you pedal. This can present problems coming up to an intersection or other hazard, where pedal assist kicking in can unexpectedly be more speed than is needed. Seems a waste to have to brake to cut the assist off. The motor is audible when accellerating, and especially complains when trying to get me up a hill on its own. At speed, or if given a human power assist, it's quieter than the chain, if not silent. So there's room for improvement (and this would be a fun thing to do some hacking on to improve its response), but it's still a lot of fun. I'd forgotten how much I enjoy riding a bike and getting a nice workout. And it's especially nice to go up a hill pedaling only as hard as you like, to be able to accellerate quickly without standing on the pedals, and to be able to "coast" a long, long, way.

Vincent Fourmond: Another bzr2git example

Today, I tried to switch one of my personal repositories for debian-related scripts from bzr to git, just like I've done for pmount. The trick was that this time, I wanted to only move a part of the repository, not the full repository. I had only been working before with CVS and SVN who have the idea of modules, which is not the case for bzr or git. So I made the mistake of using a single bzr for several projects, which I realize now is not a very good idea... In any case, I managed to drop some parts and here is how I did it; the trick was precisely to use SVN as an intermediate storage medium, using the following configurations files. First, bzr2svn.conf
[DEFAULT]
verbose = True
patch-name-format = ""
[project]
source = bzr:source
target = svn:target
start-revision = INITIAL
state-file = tailor.state
[bzr:source]
repository = /home/vincent/debian-devel/bzr/scripts
[svn:target]
repository = file:///tmp/testtai
module = biniou
and svn2git.conf:
[DEFAULT]
verbose = True
patch-name-format = ""
[project]
source = svn:source
target = git:target
start-revision = INITIAL
root-directory = /home/vincent/tmp/debian-mr-copyright-mode
state-file = tailor.state
[svn:source]
repository = file:///tmp/testtai
module = biniou/debian-mr-copyright-mode
[git:target]
git-command=/usr/bin/git
Then, all that is left to do is to run tailor on the resulting configuration files:
~ tailor -D -c bzr2svn.conf
~ tailor -D -c svn2git.conf

Francesco P. Lovergine: OSM and N810

I finally managed to use my Nokia N810 to do some GPS logging for OSM. The Nokia internal GPS is quite slow, so I used an external antenna and the well known Maemo Mapper tracking capability to log my first 60 kms in my area. I'm not too much happy with the result, because it seems the Nokia tablet is quite slow in tracking points: other trackers are someway configurable on those regards, but Mapper seems not taking in account any user preference about data sampling. Too bad, even if it is able to use OSM maps as default background, which is a great plus for a mapper. Definitively it needs a look to sources to understand what happens under the cover.

Adeodato Sim : Le petit Nicolas is made of awesome

Every night I can, I sit with my sister and we read half a chapter of Le petit Nicolas, in French. I read aloud, and she fixes my pronunciation. She says I’m doing well! I’m also getting to understand increasingly more and more (she helps along the way with that). I’m not sure whether it’s the magic of being written in French, or what, but I’m finding it very nice, and we laugh a lot. Maybe if I’d be reading it in a language I was fluent in it would not be the same. But, if you ever end up learning French, be sure to give it a try!

Andreas Barth: bts.turmzimmer.net with delayed queue again

Thanks to Thomas Viehmann for the patch on both ftp-master side (aka http://ftp-master.debian.org/deferred/ and on "client side" (and for nagging me enough to activate it), http://bts.turmzimmer.net/details.php shows now again when bugs are fixed in delayed. Thanks!

Bdale Garbee: YikStik

As some of you know, the first weekend in October was a big deal for me, because it was NCR's Oktoberfest launch event. My son and I spent the weekend camped out on the prairie with Keith Packard and many of our other friends. Keith successfully went from nothing to a "level 2" high power certification, which was pretty cool. I wasn't quite so lucky. On Saturday morning, I flew my custom-designed rocket YikStik for a "level 3" certification attempt. The name comes from the word my wife uses to describe lipstick. The rocket was built from a mixture of custom and Giant Leap parts, including 98mm Dyna Wind airframe, a 98-75mm tail cone retainer, and a Pinnacle nose cone. All the centering rings were cut on my 3-axis CNC milling machine, and the fins were custom 7-layer composite layups using plywood, carbon fiber, fiberglass, and epoxy... all vacuum bagged using a kitchen food saver appliance. Painted red, gold, and black, with a custom 8 foot main parachute sewn by my wife Karen from the Team Vatsaas design in red and black rip-stop nylon. The motor selected was an Aerotech M1297W reload. This is a 75mm diameter motor 66.5cm in length with 2722 grams of propellant yielding 5417 Newton-seconds of total impulse. It was also on sale earlier this year for cert attempts. My simulations said YikStik should have flown to about 14,800 feet above ground level at the NCR north site on this motor. The launch went perfectly, and the rocket was stunningly beautiful under boost. It disappeared into some high clouds, but we continued to have strong signals from the two tracking transmitters installed in the payload bay behind the nose cone. About the anticipated time after launch, we saw a rocket descending under chute in the distance, and headed in that direction. A few minutes later, we abruptly lost both tracking signals, and that's when things took a turn for the weird. In hindsight, I think we suffered an apogee deployment of the main chute, and the rocket we saw descending was someone else's. YikStik was designed to deploy a streamer at apogee, then descend fairly quickly to about 1500 feet above ground where a second set of ejection charges would fire to separate the nose cone on a 3 foot drogue parachute that would pull a deployment bag containing the main chute out of the airframe and then pull the bag off the chute. The nose cone, payload bay with the tracking transmitters, and deployment bag would then descend under the drogue chute and the remainder of the rocket would descend under the big chute. In the world of deployment bags, this is called a 'free bag' configuration. With deployment at 1500 feet, the two bits should have landed within sight of each other. But that didn't happen. It wasn't until late Sunday afternoon, after we had to leave to get Keith to the airport, that some friends finally located the nose cone assembly about 3.5 miles down range from the launch site, over a couple rises and past an area of rough terrain. By then it was cold, windy, and rainy, and so I really appreciated the effort they put in locating the nose, and wasn't too surprised that they didn't immediately see the rest. Since the bulk of the rocket under the main should have had a slightly higher descent rate than the nose cone, I expected to find the rest of the rocket somewhere near a line between the launch rail and where the nose cone was discovered. So last Wednesday I spent about 5.5 hours walking around the area searching... but no luck. Since then, several other people have been out looking for my rocket, including two friends who flew over the area today in a light plane looking down into all the washes. Still nothing. I posted some signs in the area with a photo of the rocket and my contact info, I hope someone calls eventually. In the meantime, the bulk of YikStik remains missing, and of course I did not achieve a successful level 3 certification. Lessons learned for next time are that tethering the deployment bag to the main chute instead of flying in a "free bag" configuration might have been a better choice, and it's kind of silly having two tracking transmitters in one of the two pieces of your rocket and none in the other... Ray LaPanse took some stunning photos of the launch. He will likely post better versions with color correction and so forth at some point, but in the meantime, I've put a few up on my Garbee Rockets web site. She sure was a beauty!

Runa Sandvik: Singing in the shower, dancing on the floor

In June I wrote the post I’m being published. What I can say now is that the book, or the anthology, is finally in the stores. The title is “Vi skal forandre verden en dag”, (translates to something like “We are going to change the world one day”), and yes, there’s a picture of me and the other writers on the cover. Buy it, read it, love it or hate it.

Decklin Foster: The cradle rocks above an abyss

In related news: with sup out of the way, I have returned to packaging Mnemosyne, the program that powers this blog. It is also in NEW, so expect to see it soon. (Like sup, which is packaged as sup-mail since sup is the Software Update Protocol, it is mnemosyne-blog since mnemosyne is the program formerly known as PyQt MemAid.) If you're just joining us, Mnemosyne compiles a Maildir into a static site. You can use it for a blog or just about anything else where a traditional CMS would be overkill. It's all XML and Python-extensible. The documentation kind of sucks, though, so I'm also hoping I get some more users from this to tell me what to fix. It hasn't otherwise seen much action since the beginning of 2006. Drop me a line if you have any feedback! (If it's not obvious, I think blog "comments" in general are pretty worthless. But with some craftiness, they could certainly be implemented within Mnemosyne as it stands. As could a general mailing list archive, etc...)

Patrick Schoenfeld: Extending Debian with customizable packages

In my previous post I drafted a rough idea how to add a feature to Debian that would bridge the gap between Debian as a Binary Distribution and any Source Distribution. The feature in question is giving users the chance to build customized Debian packages for specific feature sets. The possible use cases are simple:

Lets say Anthony User needs super-duper-tool with postgresql support. However this is a not so common use case and so the archive only has postgresql support. If he now wants to build a custom package, the process is "as simple" as:

apt-get source super-duper-tool
cd super-duper-tool-*
apt-get build-dep super-duper-tool OR sudo mk-build-deps -r -i
(possibly try out which ./configure options are supported by super-duper-tool)
vi debian/rules
edit debian/rules
dpkg-buildpackage -us -uc
sudo debi

That is, to be honest lot of work. And the biggest problem about it is that you need to know all this, which is not really user knowledge.

The basic idea is that Anthony can do something like
export DEB_BUILD_OPTIONS=nomysql,postgresql
deb-build-tool build super-duper-tool

and is done.
So the question is how could this be achieved?

  1. Define a set of common options (options should be consistent through all source packages, otherwise it makes not that much sense) that every package should support, if it is a supported feature by the package in question. This includes flags like mysql, postgresql, ldap and its no-equivalents (nomysql, nopostgresql) to negate it.
  2. Enable use of this common options in the package build process and that is really the hardest part. Defining a lot of ifneq..findstring constructs for 2-10 options per source package in any available source package is.... not.... a good approach. Luckily a lot of packages uses autoconf where enabling and disabling features is as easy as adding a --with-foo or --enable-foo option to the ./configure parameters. So we could write a wrapper that would handle these options. The debhelper scripts already have dh_auto_configure: Maybe this could get enhanced.
  3. If it does not exist: Write a tool to auto-build packages with DEB_BUILD_OPTIONS set by the user. Should automatically get the source, (optional: setup/update a pbuilder environment) and build it and optional install/upload it (to a user repository for example) .
Still, the idea is only a rough draft. There are still a lot of open questions/issues, for example:
Is anybody interested in pushing this idea forward? I'm happily interested in it and I know people who like the idea, too. But I can't push this forward on my own all alone. Certainly the work won't affect Lenny anymore, but considerable the time frame that is planned for Lenny+1 by the release team, this could be a feature for Lenny+1.

Kartik Mistry: See you in KDE 4.2!


* Since, We have done translation of kdebase > 75% for KDE. Gujarati will be include in KDE 4.2. We still have time to do more work. Thanks a lot to Pragnesh and Sweta for very hard work and hidden thanks to dear Pradeepto for encouraging me :P My .gu blog entry for this news.       

Sune Vuorela: Skolelinux/Debian-edu gathering infiltrated by Gnash people

Gathering
I spent this weekend at a Skolelinux/Debian-edu gathering in Oslo. 8.5 hours by bus each way. I got to meet some of the people shipping a customized Debian for schools. As it was a gathering related to educational software, looking at the KDE4 kdeedu packages seemed most appropriate. I’ve tested step packaging and hopefully it is going to end up on your local debian archive one day, along with some fixes to where kvtml files are packaged, much awaited by Annma and others. Apparantly, in Brazil, they have their own debian based kde distribution and 130 GB of free as in public domain free educational movies. Some people discussed an application to view, tag and search the movies. I quickly thought of a mixup of nepomuk and phonon in a nice userinterface. So if anyone feels like implementing that, you are more than welcome. Gnash
The gathering was together with a Gnash hackathon, and apart from gnash getting more and more usable, the gnash people are also thinking about integration with the desktop environments. For KDE 4 they have plans of a KPart easy embeddable anywhere, including in KHTML. (Maybe another use of the KPartLoader dfaure wrote recently). The gnash team are unfortunately quite short on KDE knowledge and they asked for help. I’m probably not myself the right one to help here, but maybe some of you out there feel like helping. There is already a patch set around that some people claims works, but others haven’t figured out to make it work. Feel free to comment here and I will forward to the Gnash people - or just contact them directly on the gnash-dev@gnu.org maillist. Trolls
I left the gathering a bit early to get to a Troll picnic in a Oslo park and got stuffed with p lse and lompar. (sausages and pancake like bread) I was by bus all night back home and then a shower and straight to work. After work, I slept for 14 hours or so.

Y Giridhar Appaji Nag: Proud to be an official part of Debian

I am proud to be officially a part of what is quite possibly the largest free software project on the planet. To all the people (few of you don't even use Debian - you know who you are) who have been motivating and helping me, and some that actually spent time working in past few days/weeks towards making this happen: hazaar thanks!

13 October 2008

Mike Hommey: Iceweasel display corruptions, maybe a real fix?

Thanks for the feedback on the xulrunner-1.9 packages I posted yesterday. They led me to find a possible fix for the issue. Wasn’t the package fixed? will you ask. Well, yes and no. Actually, it was built using the internal copy of cairo in the mozilla source tree. And this internal copy is (guess what) not vanilla. And we don’t want to be using the internal copy because it’s hell for stable security. I took a deeper look into the changes and spotted something that looks like a workaround for exactly this corruption issue. So if people having the corruptions before installing the test package could downgrade to the current version in unstable (apt-get install xulrunner-1.9=1.9.0.3-1 should do), install the following cairo package: for i386 and for amd64, and tell me if the corruptions are gone, that would be very helpful :).

Russell Coker: Some RAID Issues

I just read an interesting paper titled An Analysis of Data Corruption in the Storage Stack [1]. It contains an analysis of the data from 1,530,000 disks running at NetApp customer sites. The amount of corruption is worrying, as is the amount of effort that is needed to detect them. NetApp devices have regular “RAID scrubbing” which involves reading all data on all disks at some quiet time and making sure that the checksums match. They also store checksums of all written data. For “Enterprise” disks each sector stores 520 bytes, which means that a 4K data block is comprised of 8 sectors and has 64 bytes of storage for a checksum. For “Nearline” disks 9 sectors of 512 bytes are used to store a 4K data block and it’s checksum. These 64byte checksum includes the identity of the block in question, the NetApp WAFL filesystem writes a block in a different location every time, this allows the storage of snapshots of old versions and also means that when reading file data if the location that is read has data from a different file (or a different version of the same file) then it is known to be corrupt (sometimes writes don’t make it to disk). Page 3 of the document describes this. Page 13 has an analysis of error location and the fact that some disks are more likely to have errors at certain locations. They suggest configuring RAID stripes to be staggered so that you don’t have an entire stripe covering the bad spots on all disks in the array. One thing that was not directly stated in the article is the connection between the different layers. On a Unix system with software RAID you have a RAID device and a filesystem layer on top of that, and (in Linux at least) there is no way for a filesystem driver to say “you gave me a bad version of that block, please give me a different one”. Block checksum errors at the filesystem level are going to be often caused by corruption that leaves the rest of the RAID array intact, this means that the RAID stripe will have a mismatching checksum. But the RAID driver won’t know which disk has the error. If a filesystem did checksums on metadata (or data) blocks and the chunk size of the RAID was greater than the filesystem block size then when the filesystem detected an error a different version of the block could be generated from the parity. NetApp produced an interesting guest-post on the StorageMojo blog [2]. One point that they make is that Nearline disks try harder to re-read corrupt data from the disk. This means that a bad sector error will result in longer timeouts, but hopefully the data will be returned eventually. This is good if you only have a single disk, but if you have a RAID array it’s often better to just return an error and allow the data to be retrieved quickly from another disk. NetApp also claim that “Given the realities of today’s drives (plus all the trends indicating what we can expect from electro-mechanical storage devices in the near future) - protecting online data only via RAID 5 today verges on professional malpractice“, it’s a strong claim but they provide evidence to support it. Another relevant issue is the size of the RAID device. Here is a post that describes the issue of the Unrecoverable Error Rate (UER) and how it can impact large RAID-5 arrays [3]. The implication is that the larger the array (in GB/TB) the greater the need for RAID-6. It has been regarded for a long time that a larger number of disks in the array drove a greater need for RAID-6, but the idea that larger disks in a RAID array gives a greater need for RAID-6 is a new idea (to me at least). Now I am strongly advising all my clients to use RAID-6. Currently the only servers that I run which don’t have RAID-6 are legacy servers (some of which can be upgraded to RAID-6 - HP hardware RAID is really good in this regard) and small servers with two disks in a RAID-1 array.

Vincent Fourmond: Sanitizing bad UTF-8

I've hit a problem recently where statsvn does not manage to generate statistics on one of my repositories. After investigation, it turned out that there are some raw latin1 sequences in the XML log file (from a conversion from latin to UTF-8 long time ago), and that makes logfile parsing fail. To sanitize this, I use the following filter:
iconv -c -f UTF-8 -t UTF-8
This way, obnoxious sequences are dropped and processing can go on. (or, at least, could go on if it was not failing just a little later with a Null pointer exception...).

Julian Andres Klode: I am a Debian Developer now!


14 months after applying for the NM process, I’m a Debian Developer. On Mon, Oct 13, 2008 at 10:51:43PM +0000, Martin Zobel-Helas wrote:
> [ This is a long mail with important information, so please read it all
> carefully. ]
>
> Dear Julian Andres Klode!
>
> Your account ‘jak’ has just been created in the central LDAP
> database of the Debian project. [...] Thank you everyone (in chronological order):
  • Daniel Baumann (daniel) - Sponsored my first packages
  • Joerg Jaspert (joerg) - The first DD who signed my key
  • Niv Sardi-Altivanik (xaiki) - Advocated me for NM
  • Martin Zobel-Helas (zobel) - My first AM
  • Alexander Reichle-Schmehl (tolimar) - The second DD who signed my key (at CeBIT)
  • Bernd Zeimetz (bzed) - Took over in June, because zobel was very busy
  • Christoph Berg (myon) - For checking the AM report and requesting the account creation
  • Jonathan McDowell (noodles) - For adding me to the keyring
  • Martin Zobel-Helas (zobel) - This time for creating my account
And many thanks to Google - for helping me to find answers to important questions. Without you, I would know nothing. And of course all the others who helped to make this possible. Posted in Debian      

Decklin Foster: What's sup?

After some weeks of final testing, I've just uploaded packages for sup-mail to NEW. I'm pretty excited about this. Sup is a console-based MUA, like mutt (which I have used for many years). A few things distinguish it from most mail readers targeted at geeks like us:
  • Sup has no folders, a la Gmail. After watching many friends and even fellow hackers switch to Gmail, I have to admit: this literal hierarchical organization thing doesn't scale. I was planning to totally redo my mail folder system Any Day Now for about six months prior to starting on this. It was never going to happen.
  • Sup uses a Ferret full-text index to make this approach plausible. Search is super fast and beats (for me) both any kind of "organization" I could have disciplined myself into and the fine-grained control of something like mutt's search. It's sort of like git: until you do it, you don't realize how much more productive you can be when previously-expensive operations become instantaneous.
  • Sup works with threads, not messages; this is another thing Gmail got right. I used to waste brain cells thinking about which messages in a thread were worthwhile enough to save or not. Given the absurdly cheap price of disk relative to what we can type out in plain text since, like, a decade ago, this is crazy. In the index, I only have to look at whether a thread has new chatter or not, not its size, shape, or where the new messages are relative to it. All that's in the thread-view buffer where I actually read content.
  • Sup is written in Ruby. Back in the dawn of time, I used Gnus, and while I wasn't very good at elisp, the hackability afforded by being written in a high-level language was very nice compared to programs mostly implemented in C (even if they had a tacked-on scripting language). Plus, I love Ruby right now.
Despite all of those wins, sup currently has many drawbacks, and I don't recommend it for everyone. (And I mean everyone who thinks that the above are good ideas and are interested in using it; plenty of people, I'm sure, already think everything about this is idiotic, not new, or inferior to their preferred MUA. That's fine! You can ignore it all.) Here's what's still problematic:
  • At version 0.6, sup is very much not-yet-1.0. While it handles insanely large amounts of email without breaking a sweat, I still keep an additional backup of everything. (If Ferret crashes, the original copies of mail will be untouched, but it never hurts to be paranoid.)
  • The flow of data from your physical mail store to the sup index is currently one-way only. Actually removing deleted/spam messages is a big hack (if it works at all), and labels/flags/etc live entirely in Ferret-land. If you want to manipulate an actual mailbox, mutt is still the tool for the job (and then, you need to re-sync sup). This is probably the deal-breaker for most of us. I jumped in anyway because I feel like it can be solved (or more likely, made irrelevant) later.
  • William (upstream) is currently re-designing the whole thing from scratch, replacing the index library with Sphinx, and decoupling the index from the console frontend. As a result, the previous item is pretty much a non-priority (and bugs in general are not going to get the same amount of love as usual). I am hoping that we end up dumping mail into the index directly, then writing more frontends to write to Maildir backup, serve as webmail/whatever, but this is a long way off. On the plus side, thanks to Thrift, they will not be limited to Ruby.
  • Ruby's ncurses library still doesn't handle Unicode correctly. It can be patched (still doesn't work totally right), but I'm trying to find a more permanent solution for Debian.
So, if you're interested enough that you want to deal with these warts for now, apt-get install sup-mail (as soon as it hits the archive) and join us! Hopefully being in Debian will increase the userbase and get things fixed faster. If you're unsure, stay tuned for the next-generation version later. (There are screenshots and a few introductory docs over at Rubyforge that illustrate and explain all this in more depth, which I recommend checking out if you're still saying, "...huh." Me, I'm a sucker for any piece of software with a manifesto.)

Next.

Previous.