Search Results: "ag"

21 December 2008

Kurt Roeckx: Debian and (non-free) firmware: where to put it?

One of the discussion that always seems to come back is what to do with firmware. It's mostly about freedom versus usability. I think the main question is where do we want to put non-free firmware in our archive. The opinion seems to range from that it should be in the non-free archive to that it should be in the main archive, with many opinions in between, and they all have good arguments. We have 3 options that are related to it in our current vote that seem to come down to: I don't see the point of that second option, and really have to wonder if there is any firmware under a license that would comply with the DFSG except that the source isn't available. The third option can make sense for some of the blobs in the kernel that are basically settings that are written to the device. You could write an editor for it, assuming there is documentation for it. But I doubt that they're all settings, and it just seems to ignore the problem. I find Theodore Ts'o' suggestion about creating a new section for firmware the best idea so far, specially if we can agree that our official CD/DVD images will have that section on it. It has the advantage that all software in our main archive can comply with the DFSG, that you don't need to add the non-free section just to be able to use hardware that requires firmware and that you can just take a CD/DVD that works.

Uwe Hermann: 256 Creative Commons Christmas Songs

Christmas Tree Yes, it's that time of the year again... it's almost Christmas, which means that I once again updated my 10 + 100 Creative Commons Christmas Songs blog article I originally wrote in 2005. That's a collection of a lot of freely downloadable, Creative Commons licensed Christmas music. Some of the older entries in the list are no longer available unfortunately, some only needed a URL update, and I also added more than 30 new songs this year. This currently makes a total of 256 CC Christmas songs (more will probably be added over the next few days), so head over to the full song list and get those downloads started... (Photo: Wikipedia. Author: Malene Thyssen. License: GFDL 1.2 / CC-BY-SA 2.5)

Gustavo Franco: Debian Project 2.0 (rc bugs and site).

The title of this post sucks, so that's up to you help me come with an alternative. It's also a bit sarcastic to remember that Debian is around for ages, Internet was smaller and poor, web wasn't a hit on the streets. Debian GNU/Linux is successful being an universal operating system. The question is: What's next? Lenny is the short term answer, but we can do more...

Do we really need to stop and discuss everything? Let's discuss everything yeah, but always do the fun work in parallel. Let's force ourselves to much higher standards.

Please remember that in many cases it isn't that easy to contribute with more than ideas when an alternative implementation requires additional privileges. Higher standards doesn't mean lock everything even more, no. It involves release the keys and make sure we can revert any changes that are clearly bad.

Flame a new installer idea (remember that? nobody does...) or initial code is easy. Give it some room and see what happens later... Ask yourself now: Do I have any privileges in Debian that may be forbidding people to help this project? Well, if you answered yes please post in your blog, come out on IRC and talk to others. Make sure you act as an useful bridge not as a blocker. If you don't have enough time, share your privilege with a secondary (hint: Maintain a package is a privilege).

I'm on vacation from my regular job and committed to help Debian full-time on the following tasks, if folks from the respective projects are interested, drop me a comment. Those who disagree, please keep working on whatever you are. It will be much more productive to us. There we go:

RC bugs - Do downgrades/removals from packages with less XXX users (as in popcon) now. Higher standards! I can't do that by myself since I have no access, if you are a release team member and is happy with that, we define the number and I prepare the list based on BTS.

Site - I would like to help the team working on the web site to split it in two. "current" and "legacy". current would be a very small one with content related to a few topics such as: Lenny, download, documentation, how to contribute and more. It would have a new UI (multiple languages yes), use XHTML or whatever the team feels ok. The key detail is that current would be www.debian.org on the day we release Lenny and after. current would have a link (or multiple links) to legacy website. People are free to cross-post current content to legacy website as well, but the best would be move from legacy to current.

I have some more ideas, but let's focus on a few things so I can deliver. release team and www, it's your turn now.

Christian Perrier: Samba "backports" to lenny

Samba in unstable is 3.2.5 currently, while upstream published 3.2.6 a few days ago. This is mostly because 3.2.6 has too many changes that make it unsuitable for lenny, which will have 3.2.5. As we want to keep the "update through unstable" path, we can't upload 3.2.6 to unstable. Simultaneously, we are using experimental for 3.3.* releases. Upstream recently published 3.3.0-rc2 which I uploaded yesterday to experimental. So, we don't have any easy way to make post-3.2.5 releases available to our users. I briefly imagined using backports.org for this, but: Finally, I opened http://pkg-samba.alioth.debian.org/packages/ as a private repository to hold these packages. You can use the following in sources.list:
deb http://pkg-samba.alioth.debian.org/packages/ ./
deb-src http://pkg-samba.alioth.debian.org/packages/ ./
The packages are signed with my own GPG key, which you need to add to "trusted" keys for APT" (be sure to read http://wiki.debian.org/SecureApt first). They are numbered the same way they would be if they were on backports.org. These packages are maintained in the Samba packaging team SVN. Please take this as a commitment to try providing up-to-date packages for lenny during its release cycle. Of course, the security support will be done on a best effort basis but should at least not be worse than upstream's (which is known to be good and very reactive). I hope that samba users will enjoy....and if some of you could join the team and help triaging bugs, that would be appreciated..:-)

Holger Levsen: Please show some respect while standing on the shoulders of giants

I unsubscribed from -devel and -vote the other day, as the pain/gain ratio was just not worth it anymore (and -project is very much pending). Sadly, I still could not escape from what I wanted to escape from, as some people bring up those discussions and "their style" on planet.

Please show some fscking respect to your peers! Debian is not about freedom (whether you like it or not, and no matter how you define freedom), it's not about freedom of speech or being open minded, it's just about creating the greatest free operating system. The free operating system, that's why we are here.

I for one, disagree with many debian contributors ideas and believes, whether (those ideas are) Debian related or not. To give one example, I think religion is hillarious and believing in (a) higher being(s) is a sure sign of an ill (or weak, or both, or whatever) mind. (Quite similar to smoking btw, and for those who don't know, I do smoke.) But I'm not shoving this down all the time to anybody who makes a religious reference in Debian (nor in real life). Quite the contrary, I do admire quite some people who take motivation out of their religious believes to do things they think are good. I belive this is quite common the other way round too, eg when religious and human-rights motivated groups work together to help immigrants. They dont share (all) the same beliefs, and in some they have huge disagreements (eg. I think religion is the root and a means^wcontributor to many of the worlds evils) but they choose to respectfully disagree on these views to be able to work together on the common goal they share: help immigrants.

And in the same way I (try to) (dis)agree with my fellow Debian peers about their insane or great ideas. I try to respectfully disagree (or respectfully agree). And I do acknowledge that I sometimes fail, eg the above words about religion might have hurt some peoples feelings. I do give a damn about having hurt those people (so I ment to say sorry with that in cheek damn joke), even though I dont give a damn about religion. And I think the last sentence might have been too sharp to be respectful while I belive the above paragraph is fine. I also think its fine to be disrespectful (in or outside Debian) once in a while, since we are all humans and make mistakes once in a while, but I dont think it's fine to have those people in Debian who fail all the time (or too often), be it because they are incompetent to treat fellow peers with respect or because they dont care (or because they think they do something good with their kindergarten rhetoric).

Contributing to Debian is not a human right (and suppressing some voices (and esp. noise) in Debian is not censorship, for fucks sake!). We are only here, because we are standing on the shoulders of giants (except for the very few giants among us) and because we want to create/improve a great operating system. And thats why I think it's perfectly acceptable and desirable to not allow those messages here, which are distracting and/or blocking of from reaching this goal. An occasional outburst (and be that a 2-4 weeks long or a single big outburst) doesnt qualify in my book for being kicked out, no matter how harsh or unreasonable it was. Constant disruption IMO is. Where to draw the line is tricky (and I'm convinced there can't be a single written "line" covering everything in Debian), but not to draw any lines will result in only the vocal and thick-skin minorities to stay.

And with nice, respectful communities (which have policies quite a lot like the DFSG) like fedora and ubuntu available, failing to be(come again) a respectfull community might really contribute a lot to the end or slow decline of Debian. Sure, "the end of Debian!11" is a somewhat constant meme, but it is (sadly) not like Debian is undestroyable. Debian is very certainly much easier to destroy than to rebuild.

We need to take measures to prevent some peoples ideas of freedom from harming or destroying the project. And I don't mean some peoples ideas of Debian police state or Debian teletubby county - I'm very confident those ideas will not win here. But sadly I can see the results of poisonous people, or rather, their behaviour win.

And undoubtfully I also can see many great people in Debian making sure this will not happen.

The future is unwritten and I wish we show our fellows the respect they deserve. Debian wasn't made by you, more than 99,99999% of it was made by other people. And if you have to, attack ideas, not people. And usually it's also unneeded to _attack_ an idea (merely challanging it is usually enough), because usually the Debian person proposing it is not so stupid not to take your criticism into consideration.

That's why I'm still in favor of a social committee, even though I see very much the dangers of power abuse and the cultural norms in a world wide project. But I see much more danger in not stopping unrespectful assholes from urinating into our living rooms and work benches, using the waiver of "free speech" and "we all have different standards of whats acceptable."

Simpler said: either you respect the community or this community shall not be yours.

That said, I wish you all a very merry xmas, whether you celebrate and believe, or one of the two, or none. Be happy and let it be. And may we have a great 2009, despite we'll release lenny that late! ;-)
P.S.: I'll post this to -project as well, so you can reply more easily.

Cyril Brulebois: The Ugly, the Bad, the Good

This blog post is brought up to you by Sergio Leone. The Ugly See somebody propose the following change to a Depends line to make sure that a proper versioned dependency is set:
-Depends: $ shlibs:Depends , $ misc:Depends , $ xserver:Depends 
+Depends: libts-0.0-0 (>= 1.0-5), $ shlibs:Depends , $ misc:Depends , $ xserver:Depends 
While the obvious fix is to read Policy 8.6.5 and to use a debian/shlibs.local file accordingly. The Bad See the same person blog about his own competences: I m not expecting people to have to match my levels of output [ ] : He s a he , no point in using some gender-neutral thingy. The Good I ve been proposed to become an Application Manager, which I accepted. Time to get back to my first NM!

Joerg Jaspert: Planet I18N

And there it is. We now can have Planet Debian in other languages than english. The first one is Spanish but the framework allows for any number. In case you do want to have Planet Debian in a different language, follow this steps: (2LETTER means the 2char ISO Code of your language. Like es for the spanish one, de for a german, etc.) You need to have 10 feeds ready and filled in in the file you send us. All the feeds should provide a category that has entries with only the language for this new instance. (Otherwise it won t make sense to create a Planet instance for a language ) Planet now features a link section called Planet I18N right above the Subscriptions. That will always list the currently active other language Planets. The various planets share the common files like CSS, graphics and all the hackergotchis.
It was a bit of work to get to the point where we are able to add multiple planets to the system. First I had to upgrade the code behind it to a newer one, Planet Venus instead of Planet Planet. Main advantage being that it uses multi-threading to fetch the feeds, greatly speeding up that part. And this weekend I had to rewrite all the templates, going away from old (and simple) htmltmpl format to one based on Django. Htmltmpl simply has no way to deal with our Planet now anymore, especially as it has no way to access all config file values. Which I need for the translated strings, or I would need one template per language. Which would be insane. Various other things in Django also make Django templates a way easier thing to deal with, for example simply saying
  % firstof var1 var2 var3 "nothing" % 
instead of having a huge if-then-elsif-elsif-lalala chain. And we do have that multiple times.

Neil Williams: Debian Quality and Releases

Sticking with the theme that blogs are all about completely biased and probably controversial opinion and not much else, I'm glad that Thomas has made his thoughts clear. Thomas - I fully agree (but your blog doesn't support comments, so I'm putting it here).

Debian, to me, needs to about Quality over quantity (being very aggressive over orphaned packages and their reverse dependencies) and about everyone working towards the releases. Not to pick arbitrary time-based deadlines for releases but actively fixing release-critical bugs, so that the release can proceed smoothly with stable, reliable packages. Debian developers who feel unable to fix release critical bugs maybe should not be developers any more - or at least be banned from mailing lists on lists.debian.org which appear to be the only "contribution" being made.

There's no reason to continue using Gtk1.2 and no point in complaining about it because there is no prospect of anyone stepping up to maintain gtk1.2 itself. There is therefore no point in the long threads complaining about removing gtk1.2 because nobody is going to do any work to retain gtk1.2.

If you aren't prepared to do the work, you should not feel you have any rights to complain about the lack of such work being done. We're all volunteers - don't expect someone else to sift the wheat from the chaff, get rid of your own cruft. Debian needs to be an association of people who do, not the current association of people who complain, moan and generally fight amongst themselves. The answer to this negativity is a can-do attitude - it is not as if there aren't enough problems out there to fix, get out there and raise the quality. (First though, get Lenny released.)

Not everyone can do the same amount of workload but within the work that you are able to do, there must be a balance between the work you do for yourself and the work you do for the distribution. I'm not expecting people to have to match my levels of output, I am expecting people to match the proportion of time that they allocate to fixing problems outside their own limited niche. If that proportion approaches zero then maybe Debian doesn't need you any more.

There is no reason to have project members who do not contribute to either quality or releases - that doesn't just mean not fixing bugs, it means not being a part of any team or other group in Debian that provides support for general quality or the release.

If you aren't fussed about the quality of packages (in general, not just your own) and aren't willing to contribute just a small amount of your time to use your privileges to fix release-critical issues, then those privileges should be removed - you obviously don't need them. (Also, if you aren't a DD yet and you want sponsorship, these rules apply to you too. I won't sponsor people who have no feel for quality or want to help Debian make releases. I'm beginning to wish other sponsors would do the same. Quality is far more important than quantity - merely adding packages because they exist and because someone posts a request for a sponsor is insufficient. Completely insufficient, counter-productive too. See my sponsorship requirements.)

Note: this post is entirely opinionated and I don't care if you disagree. I will take a particularly brutal approach to comments that do not grasp this fact.

Julien Blache: This project should remain open and openminded

David, I m not saying it lightly: the end goal is censorship, no matter how nicely you try to put it. The goal is to discourage people from posting. They call it peer pressure , which is nothing else but the politically correct equivalent expression for intimidation . The end result is censorship. The idea of censoring the mailing lists has actually been mentioned very clearly in the recent discussions on -devel, and I never thought it would go past that, but it s actually happening. By the way, this could actually morph into a shitty karma system that wouldn t let you post past your monthly allowance and credit earned . How s that for you? You refer to those +1/-1 mails; I find them silly, annoying, useless and a waste of bandwidth and CPU time. That used to be called a me too and generally despised and frowned upon. If you actually want to score posts or posters, get a decent MUA and set up its scoring system the way you like. But keep that to yourself. As Aigars told, there are mail to web forum gateways (more like rendering engines for a mail archive, actually) that will present mails to a list in a crappy web forum of some sort that will come with all kind of crap like scoring, karma and whatever. There s an essential difference between web forums and our mailing lists, though: forums of this kind use nicknames all over the place, our mailing lists use real names. There are privacy issues involved, and I m not giving up on that, either. You want to stop flamewars? Stop replying, especially to tell how intolerable it is and other shit. Just let the damn thing die already. Funny how the well-meaning people are feeling harassed on the mailing lists when they, themselves, are harassing people they disagree with. We don t all have the same views, culture etc. We re not all friends, and we probably never will be. Guess what? It s OK! Get over it and work with each other, because that is what we are here for. If you (general) can t get over it, I m afraid this Project is not the appropriate place for you. Imposing a monoculture of politically correct crap is not an answer to the perceived problems .

René Mayorga: Hello planet Debian!

just saying hi, if you read this post my name is Ren Mayorga, I live in San Salvador the capitol city from El Salvador, that was my raw introduction. So, hello, this is my first post on planet Debian, there is nothing more to tell about me, I m just following the tradition to say hello here :) I m currently at the NM process, and I here at this planet just to try to get to you guys the point of view from a random guy at central america :)..

20 December 2008

Andrew Pollock: [tech] The Bad Block HOWTO hurts my brain

Seriously. It reads more like a worked example, without enough of the underlying theory. It doesn't help that I have a slightly more complicated situation, in that I have a filesystem on a logical volume that spans 6 physical volumes. So maybe writing all of this down will help... I know the disk with the problem: /dev/sdc I know the LBA of the sector where the rot starts: 754238963 I know that the physical volume is on /dev/sdc1 and that the partition starts at sector 63 (via sfdisk -luS /dev/sdc) Therefore, within /dev/sdc1, we're talking about block number 754238899 (754238963 - 64) I know the physical extent size is 4096 Kb (via pvdisplay -c /dev/sdc1 awk -F: ' print $8 '). In LBA block size this becomes 8192 (2 x 4096) I know the physical extents start 192K (into the partition, presumably) (via pvs -o+pe_start /dev/sdc1) This is where the Bad block HOWTO starts to quicken the pace a bit on me... I'm supposed to take the physical partition's bad block number (754238899) and divide it by the size of the physical extent (in LBA block size) (8192). So that'd be 92070. This is where I think I end up completely departing the HOWTO, because my filesystem spans multiple physical volumes. Here's my general musings... lvdisplay --maps /dev/data/srv tells me this about /dev/sdc1:
  Logical extent 272326 to 391559:
    Type                linear
    Physical volume     /dev/sdc1
    Physical extents    0 to 119233
So I'm inferring from this, given that I know I want physical extent 92070 of this device, that this corresponds to logical extent 92103 (again, I'm expressing this in LBA block size, so that's (272326 / 8192) + 92070 So now I supposedly know the logical extent (in LBA size) of the bad block. Now what? I think I'm wandering up too many layers, closer to the physical filesystem, but I'll continue wandering around... So presumably at this point, I just want to convert the logical extent to an actual filesystem block number. Maybe the logical extent number divided by the extent filesystem block size divided by the LBA block size? 92070 / (4096 / 512) = 11508. That feels awfully low though. The dd test suggests this is incorrect. At this point I'm feeling fairly lost. If someone out there is reading this, and they've done this before, I'd love to hear from you.

Joey Hess: two parties and a story

Happy solstice! High point of the season for me, and today was a two party day. My sister has reached the point where a good b-day present for her is merging the blog style comments branch into ikiwiki and installing linux on yet another laptop. So we had a little installation party with cake and Carcassonne. Except for wireless it was a success. Since I outsourced the other present to the UK, perhaps someone can sort out Christmas by telling me how to get Intel 5100 wireless working in Debian? ;-) At the solstice party tonight, all three of the recent inhabitants of the bottom of Wortroot washed up on the porch, each of us looking a bit scraggly (especially the current resident). Jeremy told this story:
His friend decided to drive his SUV down the driveway to the farm, without consulting with him first. (This driveway was blasted out of the hillside by amateurs, using dynamite, in an earlier era of life at the farm. It has been basically unmaintained since, progressively more eroded and rutted, and over the last 20 years only the Yellow Truck (with no brakes) has had free reign over it.) He got down the hill ok, and he passed the small field, and then he got to the narrow place. (Where the creek is eroding the driveway away faster than we can cut into the hill to widen it.) And Jeremey told him to stop, but he kept on going.. sliding right off the driveway, and rolling the SUV into the creek. (The creek here is, now that I think of it, exactly as wide as your average SUV is tall, and in a gully exactly as deep as your average SUV is wide. It must have fit perfectly.) They tried winching it out. That didn't work. They didn't even think to ask neighbor Jimmie to once again haul a vehicle up the driveway. His tractor couldn't have gotten this one out. They had to rent a "small backhoe on treads, like a tank" to do the job.
Ok, maybe you have to have lived there to appreciate this. :-)

Aigars Mahinovs: Voting on emails?

What does it sound like when a commission is reinventing a wheel? Much like this. Guys, the technology you are looking for is called (*gasp*) a forum, with moderators and poster carma and such It would not be too hard to implement a gateway that would receive emails posted to any list and republish then in a web forum where then moderation and voting can take place. Email is unsuited for this because it is impossible to moderate and vote after the message has been sent out (and delaying emails for moderation/voting is a huge burden on communication).

Biella Coleman: Crumble Away

I consider myself a fairly creative thinker but not even close to outrageously creative. I do have a few friends that fit that later category and one of them is my ex-roommate, Zack Brown (of kernel traffic fame. After many, really too many months of not seeing him, I met him for dinner last night under very snowy NYC conditions and as is always the case, he opened our evening meeting with an unusual and compelling story (and I usually am skeptical of his claims but my skepticism is most often totally unwarranted). Last night, his declaration was the following. He let me know that he has been working on a game, since before we met in 2001, which I was never knew about, and just recently all the pieces and this is metaphorical and literal for there are many pieces in the game have come together and has filed a patent for the game (news to me that you could patent a game). After thinking about it for 7 years(!!!), he has invented a game that I have to say looks stunningly interesting Crumble. It is simple in its rules and format but the strategy is quite demanding and complex. It is requires deep thought but also, it seems, a very visual mind. If you are interested in following its development and marketing (he is looking for manufacturers), you can keep track of developments on his blog. If you are a daring and patient soul (who can refrain from sneezing and laughing) you can make your own pieces and play sooner. And if you work at Google (NYC office) apparently, people are already playing, so you can join and Crumble Away!

Biella Coleman: Crumble Away

I consider myself a fairly creative thinker but not even close to outrageously creative. I do have a few friends that fit that later category and one of them is my ex-roommate, Zack Brown (of kernel traffic fame. After many, really too many months of not seeing him, I met him for dinner last night under very snowy NYC conditions and as is always the case, he opened our evening meeting with an unusual and compelling story (and I usually am skeptical of his claims but my skepticism is most often totally unwarranted). Last night, his declaration was the following. He let me know that he has been working on a game, since before we met in 2001, which I was never knew about, and just recently all the pieces and this is metaphorical and literal for there are many pieces in the game have come together and has filed a patent for the game (news to me that you could patent a game). After thinking about it for 7 years(!!!), he has invented a game that I have to say looks stunningly interesting Crumble. It is simple in its rules and format but the strategy is quite demanding and complex. It is requires deep thought but also, it seems, a very visual mind. If you are interested in following its development and marketing (he is looking for manufacturers), you can keep track of developments on his blog. If you are a daring and patient soul (who can refrain from sneezing and laughing) you can make your own pieces and play sooner. And if you work at Google (NYC office) apparently, people are already playing, so you can join and Crumble Away!

Biella Coleman: What to make of the other half?

Many people ask me why there are such few female hackers. While I think this is an important/interesting question (that is also extraordinarily hard to answer), there is another one which has captivated me for much longer, which is the followingL why are there such few females represented in the academic/activist world of free software/free culture, etc.? It seems like every turn I take, there are books galore, talks galore, essays galore being written by men with females sprinkled on top, like some confectionery after thought. Take for example Joi Ito s recent photograph collection, Free Souls (women are represented in the beautiful array of photographs) but in the essays which reflect on freedom/free culture/the souls of freedom, there is (I think, correct me if I am wrong), not a single female voice, despite the fact that there were clearly females authors/activists that could have potentially contributed.
Essays 1. Lawrence Lessig
Foreword by Lawrence Lessig
2. Christopher Adams
Share this book
3. Joi Ito
Just another free soul
4. Howard Rheingold
Participative Pedagogy for a Literacy of Literacies
5. Lawrence Liang
Free as in Soul: The Anti-image Politics of Copyright
6. Cory Doctorow
You Can t Own Knowledge
7. Yochai Benkler
Complexity and Humanity
8. Isaac Mao
Sharism: A Mind Revolution
9. Marko Ahtisaari
Intelligent Travel
Now, am I overreacting here; or is this reason for worry?

Andrew Pollock: [tech] On efficient shell scripting

Mike Hommey took some inefficient shell scripting to task. I feel obligated to point out that more $file wc awk ' print $1 ' is not the same as wc -l $file. To get the same output, you're going to need one of:
cat $file   wc -l
or
wc -l $file   awk ' print $1 '
I suspect cat is going to have a faster startup time than awk... (On my system, gawk is an order of magnitude bigger than cat)

David Paleino: Free software yes, free speech too!

Dear Julien, that proposal is not about censoring mails sent in by people. Think to it as that "karma" thing many sites have. And yes, I'm one of those in favour of such project. I'm a free software,speech guy, but just hate all the flames seen lately on -devel. We must find a way to stop that, or at least to control it. Again, it's not censorship, as I read it, all messages would go in. Citing:
I have also seen opinions that other "obvious" ways of addressing the issue,
such as moderation of the lists or a new organizational entity, which
would act as a list watchdog, is not the way to go, as it adds yet
another layer of bureacracy and raises the usual questions of choosing
the "right" people for the privileged position.
It's just an alternative way of expressing opinions about a mail. Consider it as those "+1"/"-1" mails that you can often see.

Miriam Ruiz: Interesting proposals on how to make Debian a better world

I have been positively surprised to find out that some people are taking seriously the fact that some people are being put off from actively participating in Debian s discussions because doing so would lead to offensive behaviour and personal attacks, and to try to find a solution to the fact that a very vocal minority is dominating the silent majority. Of course, some people are happy with the statu quo and strongly opposes to changing anything in that direction, not very surprisingly. The part about I m really starting to think that this Project could do a lot better without some people is crystal clear and needs no comments. I m not really sure that the current social environment can be fixed just with technical measures. Another proposal talks about some mailing lists extracted from the official ones but with the offending comments filtered out. I must confess that I find this idea very interesting and that I might think about rejoining such a list. Of course, technical details on how to properly and effectively implement any of this methods, or even a mixed one, can be very tricky.

Julian Andres Klode: Filesystems


In the last months, I noticed that it was a bad decision to use XFS as my filesystem; and before I realized that ext3 was a bad choice as well. File systems have problems. I can t use ext3 on my laptop, because it would check the whole disk (120GB) every 30 boots. And this check takes a very long time (15 or 30 minutes, I do not know it exactly). XFS is better, but also problematic because deleting a big directory with a deep hierarchy takes a very long time like 1.5 minutes , whereas ext3 needs a few seconds. Also I still wonder why XFS needs no checks. Therefore I might go with ext4. The time needed to check the partition seemed to be much shorter and the speed is about the same as with ext3. The installation will probably be: Install Lenny on a ext3 partition, install kernel with ext4 support (which is kernel 2.6.28), add ext4 to /etc/initramfs-tools/modules, tar the partition, format it as ext4, and untar the contents again; because converting does not bring the advantags of ext4 to already existing files. BTW, I did some benchmarking with bonnie++, and XFS had about 20,000 operations per second, whereas ext3 had 60,000. ext4dev from Kernel 2.6.27 was a bit slower than ext3 I also tested BTRFS, but BTRFS is 1) not stable enough 2) as slow as XFS. It also shows horrible write performance of 19MB/s using dd, whereas XFS reached 42MB/s. BTW, benchmarking btrfs with bonnie++ only works using -s 0 , i.e. without I/O performance test, else you receive a kernel bug. I subscribed to the btrfs mailing list, and sent my bug report email 4 times, but it never reached the list it seems. This bug also happens in other cases. Posted in General

Next.

Previous.