Search Results: "beh"

6 May 2007

Michal Čihař: Gammu test version 1.10.6

I just released new version of Gammu, you can download it from download server. The biggest change is improved gnappled and it's support in Gammu. It also had to became incompatible with previous versions, so you have to upgrade it in your phone. Full list of changes: I currently do not plan further testing release before next stable one, but in case some serious problem is found, this can change. This time really :-).

Alastair McKinstry: The God Delusion, by Richard Dawkins

The God Delusion by Richard Dawkins is an 'Atheism Consciousness-raising book', according to the author. It makes the case for Atheism, saying Atheists should stand up and be counted, and stand against the growing tide (in the U.S. in particular) of irrationality and belief. Although as one of Atheisms most visible proponents Dawkins has 'make converts' to the cause, in this book he is mostly speaking to the converted, presenting the evidence. The book documents the main arguments in favour of God. These are dismissed fairly abruptly; while a lot of pages are taken up going into them, they are probably not a comprehensive list. A book by a theologian or believer would probably be a better source for such a list. Nevertheless, Dawkins as a scientist does consider and list the opposing arguments. As presented however, they are extremely threadbare and easily dismissed. Mostly they are backed up by a willingness for people to take God (and Theology!) seriously: since so many people believe in God, it must be taken seriously, or so the reasoning goes. Not so: the proofs of Gods existence don't stand up and should be dismissed. Dawkins makes the case that we should instead of investigating God, investigate why people believe in God, given the lack of evidence. He gives some good hypotheses in terms of Darwinian thinking: reasons why faith, accepting what your parents said without evidence, has survival benefits, that in other circumstances lead people to believe nonsense stories with faith. Another under-estimated problem is the different definitions people have for 'God' and 'religion'. Most people from a Christian / Judaic background have a habit of framing belief and Religion in terms of the religion they grew up in. They may accept that you have a different God(s), but still view God(s) as something you pray to, that intercede on your behalf, etc. By confusing all the different aspects given to 'God' in the Christian tradition, they think that if you have 'proved' one of them, all the rest follow. If you prove / claim that something created the Universe, and label that God, then, they imply, there must be one overall, kind, monotheistic God, Jesus died on the Cross for your sins, that God will change the laws of physics to suit you (miracles), etc. Not so: all you have done is label something, not proved your religion. Dawkins (rightly) dismisses Buddhism, etc. as 'principles for living' rather than religions for the purposes of this book, and we need to be careful what we call religion, too. Dawkins also makes a good case against Agnosticism. He argues we should be more forthright and say we are Strongly Atheistic rather than Agnostic. Agnosticism was created by Thomas Huxley to explain his beliefs. He defined Athiesm is a positive belief in the lack of God, a proposition for which there is no evidence. He argued that, until we have proof that God does not exist, scientifically correct to consider ourselves 'sceptics' on this matter, and neither believe nor disbelieve in God. This sounds good, however in Science there are huge numbers of theories that in practice we have no evidence for either way that Occams razor mows down for us. We don't claim to be agnostic about them, we simply ignore them until they are actually needed to explain something. Which, given modern science and Darwins explanation of evolution in particular, God no longer is. The later chapters of the book cover whether, despite the lack of evidence, belief in God or Religion is a good thing, whether religion gives a moral purpose and direction to life, and defines a sense of "Good" that Atheists cannot have. For this he goes through the Bible with a disbelieving eye, pointing to the horrors of genocide that it promotes in the Old Testament, etc. He points out that we don't actually use the bible for moral guidance, but instead decide our own morality: we pick examples from the Bible a la carte to defend our choices. We don't decide, as an Old Testament interpretation would put it, that murder of an non-Jew is acceptable; that rape of an enemy is acceptable, that killing non-believers and witches necessary. Instead we pick examples to back up what we've decided already. If you're going to do that, stop pretending the Bible is giving you moral guidance and instead accept that we decide. Dawkins underestimates the social and ethnic aspects of religion. He is overly critical of religion, blaming it for much of the worlds violence, genocides, etc. It would be truer to say that Northern Ireland, etc. are examples of ethic rather than religious strife. "God says so" is just the ultimate argument. But conversely religion is a cohesive element in most societies. I suspect that a cause of the growth of christianity in the U.S. is that its proselytising nature goes out to be inclusive in Americas highly mobile society. When work, etc. causes people and families to move across the continent, they will find a church to welcome them into the community. Its against this background that atheists are the most distrusted minority. Shared beliefs, whatever those beliefs, bring neighbours closer. James Lovelock, (co-creator with Lynn Margulis of the Gaia Hypothesis) proposes that atheists can treat Gaia as an alternative religion, something to celebrate and to give moral direction to life. This I have sympathy with, that life is important, and to be celebrated, but not to be confused with something to be prayed to, or imagine that it is biased towards towards our existence. In these times when people are again using religion as a justification for war, claiming a "clash of civilisations", this is a book worth reading, but beyond deciding whether gods exist we need to understand why people believe. The Darwinian arguments are as Richard Dawkins points out, just a start, but I think more is needed to explain religion. Tags , ,

Antti-Juhani Kaijanaho: Serendipity breaks an important Internet standard and is proud of it

Originally posted on 2006-04-16. Clarification 2006-04-19: The misfeature discussed below applies to feeds only, as far as I know, not to regular HTML serving. Update 2007-05-06: I have just learned that the option in question is Activate strict RFC2616 RSS-Feed compliance. I have no idea when it was added. While investigating (wearing my hat as the Planet Haskell editor/technician) John Goerzen’s Planet floods, I stumbled on a very strange misfeature in Serendipity. A HTTP/1.1 client can ask a server to send a file over only if the file has been modified since some date. What Serendipity does is send only those entries dated after the provided timestamp. Now, this might seem like a triviality, but it isn’t. The HTTP/1.1 feature is there to make proxy caching work. It is very important for caching that the file sent is the same, regardless whether the request is “since this timestamp”, or a regular request. Serendipity’s behaviour breaks this very important caching invariant! What’s more is that Serendipity’s developers seem rather proud of this misfeature. While the feature this misuse of HTTP/1.1 is intended to create is certainly useful, it should be implemented as a separate mechanism, and not by misusing HTTP/1.1 caching! (A separate protocol is probably necessary, perhaps specifying a URI query syntax for this is enough; obviously, one needs to get the aggregators to support this.) Serendipity will apparently have a configuration option to fix this, but it will be off by default. Serendipity users, upgrade (as soon as it is possible) and mark that option On, to remain compatible with the rest of the Internet.

Evan Prodromou: 15 Flor al CCXV

Today is my one-year blogging anniversary. I started this blog on Journal/15 Flor al CCXIV, kind of trepidatiously and with ambiguous intentions. Now, a year later, I feel much more confident in the format and clear in my purpose. I've varied between an almost maniacally consistent one-post-per-day regimen to a more impressionistic, when-I-feel-like-it once-a-week schedule. I'll admit that I'm happier with the more frequent update schedule; I feel like I deliver more to the reader that way. I think the main thing I've enjoyed from having this blog has been the personal satisfaction in frequent and informal writings on my own schedule and to my own whim. Working with wikis makes a lot of my life about careful collaboration and consensus gathering, and having a place where I can speak out with my own voice on my own thoughts is really refreshing... and addictive. Most of all, I've enjoyed how having this blog has connected me with new people, and with friends I already had, in new and different ways. This year of blogging has been contemporaneous with a deepening of my connection with the Montreal technology community, and I can't help but think there's some causation involved. I think that my blogging is bringing me into a common medium and a common language with a group of people I want to spend time with. I've had some side effects I didn't anticipate, either. My family has started reading this blog, which means they know how I'm doing and what I'm up to more often than when I do once-a-week phone calls. And my more extended family -- aunts, uncles, cousins -- also read regularly. I can only wonder what they think about my complaints over various, say, Scheme module formats, but they seem to like it, too. Even Maj's mother reads it (hi Rita!). I think that m-c's 10 reasons to blog really hold true for me; it's good reading with a year's perspective behind me. I'm looking forward to the next year and what it has in store. tags:

Great day It was actually a great day for a blogiversary. Last night, Maj went out with her friend Sam for Sam's birthday, so this morning Amita June had a very quiet breakfast and then went out to Best Buy to do some shopping. I just bought a Canon MP600 printer, and toner cartridges weren't included in the package, so I had to go buy more. (Later, while configuring the printer, I found the toner packages in the bottom of the box. D'oh!) Amita fell asleep on the way home, so I just dropped her in bed. Maj and I walked through a brisk but sunny Montreal weekend afternoon down to the me dia offices, where Creacamp was already in full swing. There were lots of old friends and new ones, and the offices were light and airy and nicely connected. There was a talk by Guylaine Couture about her painted books, and by Luce Beaulieu about her awesome codesigner business, POSCH. Both really interesting. Of course my favourite talk was Anne-Marie's, about her great video series Music Spins the World (or La musique spin le monde). It's an incredible first-person series about her travel adventures with various rockstars to obscure and dangerous parts of the globe. A-M is becoming quite the rock diva, but I'm glad she's staying down-to-earth about it. You can check her work on 33mag.tv. Tonight I had a great time, too. Alex Roberts and Jon Phillips of Creative Commons are in town for the awesome Libre Graphics Meeting being held at the cole Polytechnique this weekend. The event seems great -- bringing together developers from all the great Open Source/Open Content graphics projects together in one room to talk. Jon and Alex met me and Niko at Concordia to see the Montreal premiere of the Helvetica movie. Helvetica is a great documentary about the history of this ubiquitous, unassuming font that epitomizes the modernist view of typography and design. The movie gives Helvetica a personality all its own, and in the process explicates the history of graphic design over the last fifty year. It also introduces us to a rogue's gallery of design and typography legends, all of whom are amusingly and passionately opinionated about design in general and Helvetica in particular. It has that characteristic of great documentaries: it illuminates the camera obscura of global culture through the pinhole of its narrow subject, a single font. Incredible. After the movie the four of us went to La Banquise, the landmark 24-hour poutine parlour right near my house. Alex and Jon indulged deeply in the local specialty -- they each got poutines with lots of bacon and ground beef -- and we all chatted about San Francisco, Web culture, Creative Commons and the cast of characters that surround it. A great, fun time. tags:

5 May 2007

Erich Schubert: OpenSolaris negative publicity

It's scary how much negative publicity a single user can cause for a whole project...90% of the time when I read about OpenSolaris, it's by a highly aggressive troll, also known as the "author" of cdrecord (the term "current upstream maintainer" is probably more appropriate).And it's always the same blah-blah, how much superior Solaris is to Linux.But what is much worse is the way he posts and hist persistence. (I'd link some postings, but they're all in german at Heise). At Heise News, whenever there is a posting related to Linux (e.g. because of Berlin considering a Linux migration, or a posting about ZFS), he reiterates that you shouldn't be using Linux but OpenSolaris. And then flames anybody who again mentions Linux or GNU. Because as we all know, GNU tar is bad, and POSIX tar is the only god...One reason to avoid OpenSolaris is just to keep a distance from him. I'm sure that there are some good things in OpenSolaris, too. And that there are some smart people working on it. But you have to understand: I'd be more willing to setup a FreeBSD, NetBSD or OSX system (or even a windows system) than maybe having to deal with him when I run into some problem where I might need assistance. When doing FL/OSS development, I want a nice community around me, and the part I see of the OpenSolaris community is not very well-behaved.You might want to read this blog posting on Linux and Solaris scalability by DaveM for some comments on similar Solaris FUD. Seems like J.S. isn't the only aggressive advocate who prefers to flame instead of trying to impress with technical issues, professionalism and personality.

3 May 2007

Martin F. Krafft: LPI or not?

The Linux Professional Institute offers all its exams at a discounted price at debconf7. That's definitely good news and should earn Klaus Behrla another round of gratitude for his efforts (assuming he's behind this again). However, it also gets me thinking again: I've been meaning to complete my certifications for years but never could be bothered to spend the money (even at a discount) or actually devote the time to the exam itself. At FOSDEM 2007, I had signed up but then skipped the exams to do more important stuff. The reason? During the conference, someone responded with something like "LPI? Why? I am a Debian developer" when I brought up the subject. Good point. I think I could just sit down and pass the second and third stage exams (having contributed to the exams themselves), and do even better with a bit of studying for it. But is it worth it? Does the LPI certification actually prove something that isn't already obvious from my online track record. What do you think? I'd be interested specifically to hear from fellow developers who decided to take the exams. NP: Anekdoten - Monolith Update: thanks, Joerg, for your thoughts. I am not looking for employment, and if I was, I'd certainly not want to work at a company that thinks certifications are the true proof of capabilities. So I guess that leaves me with a 'no' still. But I also want to say that this post is not to discredit the LPI. I think their exams are fair and definitely not trivial. Even looking at some study notes for LPIC1, I learnt some new stuff, so I bet just preparing for LPIC2 and 3 would teach me things I did not know yet. Compared to other certifications by more commercial vendors, LPIC definitely ranks very high, so don't let my blog post discourage you: there are plenty of reasons to take the exams; I was just looking for reasons why I would want to continue taking them. Update: Mario, I would not be a DD if before I had not been and continue to be a system administrator. And I think you'll have problems finding a hand full of DDs who've never touched an ISA card.

1 May 2007

Ross Burton: For Sale: Discworld Novels

In order to make some space and a little cash, I'm selling my collection of Discworld novels. I have the first 24 in paperback, but sadly not Lords and Ladies. They are all in very good quality and I'm offering the lot for about £60. Reasonable offers accepted, and this is for collection or personal delivery if I'm feeling nice (say, you live in Cambridge). I can provide photographic evidence of the books if required, I just need to get them out from behind another pile of books. Anyone interested? If so, mail me. NP: Soulmates, Nobody

30 April 2007

Kai Hendry: Etrex plotting

Etrex via a USB interface This morning I thought I couldn’t get my GPS tracklog from my bike ride through London off my Etrex GPS device as I didn’t have:
  1. A serial port on my X40
  2. Google plus (20USD for getting data off my GPS!) on my Windows desktop at work
As I left work, a colleague suggested I try an USB serial adaptor that was lying around. He also gave me a CD with the drivers. I said I don’t need drivers! I run Debian, much to my colleague’s bemusement. Anyhoo, the USB/Serial interface works well, it comes up like so:
Apr 30 22:56:53 monty kernel: usbcore: registered new driver usbserial
Apr 30 22:56:53 monty kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
Apr 30 22:56:53 monty kernel: usbcore: registered new driver usbserial_generic
Apr 30 22:56:53 monty kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core
Apr 30 22:56:53 monty kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
Apr 30 22:56:53 monty kernel: pl2303 2-1:1.0: pl2303 converter detected
Apr 30 22:56:53 monty kernel: usb 2-1: pl2303 converter now attached to ttyUSB0
Then I ran: gpsbabel -t -i garmin -f /dev/ttyUSB0 -o gpx -F tracklog.gpx To download the track log from the Garmin. Then I converted the GPX into KML with this Gpsvisualizer Web application. Then I load up the KML with Google Earth to see where and when I have been cycling London. Google Earth really needs the package libgl1-mesa-dri installed to get DRI working on my X40 machine. Google earth showing my track log Though I prefer not to use Google Earth. I wish I could load the data with this Google maps animator, though the service doesn’t seem to accepting new accounts. Grrr… Update: Just a couple of comments about riding in London:

Enrico Zini: tg-quirk

Turbogears form quirk I had a great idea:
@validate(model_form)
@error_handler()
@expose(template='kid:myproject.templates.new')
def new(self, id, tg_errors=None, **kw):
    """Create new records in model"""
    if tg_errors:
        # Ask until there is still something missing
        return dict(record = defaults, form = model_form)
    else:
        # We have everything: save it
        i = Item(**kw)
        flash("Item was successfully created.")
        raise redirect("../show/%d" % i.id)
It was perfect: one simple method, simple error handling, nice helpful messages all around. Except, check boxes and select fields would not get the default values while all other fields would. After two hours searching and cursing and tracing things into widget code, I found this bit in InputWidget.adjust_value:
# there are some input fields that when nothing is checked/selected
# instead of sending a nice name="" are totally missing from
# input_values, this little workaround let's us manage them nicely
# without interfering with other types of fields, we need this to
# keep track of their empty status otherwise if the form is going to be
# redisplayed for some errors they end up to use their defaults values
# instead of being empty since FE doesn't validate a failing Schema.
# posterity note: this is also why we need if_missing=None in
# validators.Schema, see ticket #696.
So, what is happening here is that since check boxes and option fields don't have a nice behaviour when unselected, turbogears has to work around it. So in order to detect the difference between "I selected 'None'" and "I didn't select anything", it reasons that if the input has been validated, then the user has made some selections, so it defaults to "The user selected 'None'". If the input has not been validated, then we're showing the form for the first time, then a missing value means "Use the default provided". Since I was doing the validation all the time, this meant that Checkboxes and Select fields would never use the default values. Hence, if you use those fields then you necessarily need two different controller methods, one to present the form and one to save it:
@expose(template='kid:myproject.templates.new')
def new(self, id, **kw):
    """Create new records in model"""
    return dict(record = defaults(), form = model_form)
@validate(model_form)
@error_handler(new)
@expose()
def savenew(self, id, **kw):
    """Create new records in model"""
    i = Item(**kw)
    flash("Item was successfully created.")
    raise redirect("../show/%d"%i.id)
If someone else stumbles on the same problem, I hope they'll find this post and they won't have to spend another two awful hours tracking it down again.

27 April 2007

MJ Ray: Daddy or Chips? MJ Ray or Sony?

Julien Blache: MacBook Pro status update: now this is weird

I’ve just built a 2.6.21 kernel for my machine, only to realize that the machine doesn’t behave like some other similar (if not identical) MacBook Pro do. Facts: So, now I’m really confused. A colleague here has got the exact same machine, except he bought it in mid-february and I bought mine back in november (the day after they were announced by Apple, so my machine is one of the “very first” Core2 Duo MacBook Pro). Either there has been a new hardware revision, or there’s something weird happening. I’m running an x86-64 kernel and my colleague is running an i386 kernel, but I really can’t believe it makes any difference at all. I guess I’ll have to find out what’s going on …

26 April 2007

Steve Kemp: He was in a bind 'cos he was way behind

My girlfriend who was returned from hospital on Friday learnt a couple of days later that she'd managed to suffer a fractured skull. Apart from that shocking news I've been doing little. Lots of travelling, lots of tidying up ~/bin, little else. One new toy is release which will allow me to easily release projects. The idea is you run "~/bin/release" inside a project directory and it will: Very simple, almost trivially so, but it has a lot nicer than having to do all the bits manually. (sample .release file.) I had a piece of code for triggering new freshmeat announcements working a while back - but it was a little too fragile when it came to reading the ChangeLog files I use so I've killed it for the moment. (Probably "$EDITOR fresmeat.tmp &" would be a better idea anyway!) Connectivity is bad right now, since I'm in the middle of changing home ISP, but hopefully that will be resolved in the next week or two. (Switching from Telewest/Virgin -> Sky for people in the UK who might care.)

25 April 2007

Julien Blache: pommed v1.3: enhancements and fixes

This is mainly an enhancement release as far as pommed itself is concerned: This last item is probably the most important one for quite a few pommed users; hope it’ll behave better after suspend and will no longer get “stuck”. Gpomme has got 2 new themes, the elegant-bright and elegant-dark themes, along with a configuration GUI which will let you set the theme and the timeout. Enjoy!

24 April 2007

Kartik Mistry: Now this is strange!

* 38 C is OK but, now this is strange!! Strange behaviour of weather applet!

23 April 2007

Bastian Venthur: New queries for reportbug-ng

Instead of the boring “package” queries, rng used to support ’till now, rng now supports all the queries our BTS supports:
package
Returns all the bugs belonging to the PACKAGE
bugnumber
Returns the bug with BUGNUMBER and loads it into the built in browser immediately
maintainer@foo.bar
Returns all the bugs assigned to MAINTAINER
src:package
Returns all the bugs belonging to the SOURCEPACKAGE
from:submitter@foo.bar
Returns all the bugs filed by SUBMITTER
severity:foo
Returns all the bugs of SEVERITY. Warning this list is probably very long. Recognized are the values: critical, grave, serious, important, normal, minor and wishlist
tag:bar
Returns all the bugs marked with TAG
Those queries are available on the command line too and behave exacly as if entered in the program: The syntax is: rng [QUERY], where query is one of the above (and rng a convenient shortcut to reportbug-ng). An example: if you start rng from:venthur@debian.org, you’ll get the full list of all bugreports I’ve ever reported. Now you can filter the list to find all bugreports I’ve filed against, say: qgo… voila. It doesn’t get any easier than that, does it? Those new queries and a few changes under the hood required quite a lot of refactoring in the code and I’m somewhat scared that I’ve introduced some new bugs. So I guess I should stop releasing so often (or for at least 10 days so rng can finally enter testing) and use the time to start writing some unit tests.

22 April 2007

Michael Prokop: Booting from USB pen: troubleshooting and pitfalls

As grml supports booting from usb devices (harddisk installation via grml2hd as well as booting from usb pens via grml2usb) and I helped many people at debugging booting problems I think I stumbled upon every existing pitfall. 8-) There are several situations where booting might fail. So here we go with a summary of the most common pitfalls and possible solutions:
  1. The Bootsplash is displayed, the kernel loads but you very soon get a:
  2. ran out of input data
    System halted
    
    Reason: everything OK, except for the filesystem used on your usb device. So instead of fat16 you use for example fat32. Fix: use the appropriate filesystem (fat16 for usb pens usually).
  3. When trying to boot from USB you get something like:
  4. Invalid operating system
    
    Possible reason: the partition layout is not ok. Very probably there’s no primary partition or none has the flag ‘bootable’ set. (Read on for further details.)
  5. When trying to boot from USB you get something like:
  6. No operating system found.
    
    Possible reason: you forgot to set the boot-flag on the partition. Or you did not install an operating system at all. ;-)
  7. When trying to set up the partition(s) on the USB device cfdisk reports something like:
  8. FATAL ERROR: Bad primary partition 0: Partition ends in the final partial cylinder
    
    Reason: the partition layout is not ok. Either use fdisk (requires detailed knowledge about partition setup!) or better: use a fronted of libparted, like gparted. gparted does an excellent job at setting up an appropriate partition layout for booting from USB (read on for details about the correct setup). As long as cfdisk has problems with the layout - it will exit on errors - your usb pen very probably does not have a valid partition setup for booting. Please notice that fdisk very often uses defaults which are not OK, whereas gparted uses the appropriate heads, sectors/track and cylinders settings. So if you really want to use fdisk for setting up the appropriate partition layout you might have to enter the ‘extra functionality (experts only)’ menu of fdisk.
  9. The system never displays the bootsplash of the usb device at all? Checklist:
    • does your system support booting from USB at all? Check settings in BIOS.
    • do you use the correct USB mode in BIOS? Check BIOS again, usually you want to use USB-HDD mode. Not possible? See USB-ZIP mode.
    • is "booting from USB" in the appropriate order of the booting sequence? Check the "boot"-section in your BIOS.
    • is the bootable flag set on the boot-partition? Check for example with cfdisk.
    • is the partition used for booting the first partition and a primary one on your device? Check with cfdisk again.
    • is the partition layout ok? The first partition (the one used for booting) has to start at cylinder 1/sector 63, otherwise booting will fail on most (all?) x86 systems. Check with ‘cfdisk -P s /dev/..’ or ‘fdisk -l -u /dev/…’. Do *not* trust the output of ‘fdisk -l /dev/…’. Really.
  10. syslinux does not work on your system (b0rken BIOS for example)? Possible solution: use grub instead.
  11. Kernel boots but fails to find the root filesystem with something like:
  12. kernel-panic: unable to mount root-fs...
    
    Yes? Then the root= argument in your kernel commandline (specified in the bootloader, usually lilo, grub or isolinux/syslinux) is pointing to the wrong device. Solution: adjust the root=-option in your bootmanager’s configuration. Tip: use root=UUID instead of root=/dev/[hs]d…
  13. All of the above tips don’t work? Maybe your USB pen is even larger than 1GB?
  14. Possible reason: Some BIOSes offer different modes for USB booting. The proper mode to boot a USB stick is USB-HDD. If that doesn’t work or is not supported by your system, you need to format your USB-Stick as USB-ZIP. To do this, the syslinux source distribution contains an utility called mkdiskimage, which you can use to re-format your USB stick in USB-ZIP format. For more information refer to the USB-webpage in the grml-wiki and Bootable USB Key in the knoppix-wiki.
I mentioned the correct partition layout several times. Reminder: a first, primary partition with fat16 (as filesystem as well as partition’s system id!) with bootable-flag set. The partition should start behind MBR at 1st cylinder and 63rd sector (see www.ata-atapi.com/hiwmbr.htm and thestarman.pcministry.com/asm/mbr/index.html for more details about MBR). So how does a correct partition look like? Output in several formats as reference:
# fdisk -l -u /dev/sda
Disk /dev/sda: 1039 MB, 1039663104 bytes
255 heads, 63 sectors/track, 126 cylinders, total 2030592 sectors
Units = sectors of 1 * 512 = 512 bytes
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63     2024189     1012063+   6  FAT16
# fdisk -l /dev/sda
Disk /dev/sda: 1039 MB, 1039663104 bytes
255 heads, 63 sectors/track, 126 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         126     1012063+   6  FAT16
# sfdisk -d /dev/sda
# partition table of /dev/sda
unit: sectors
/dev/sda1 : start=       63, size=  2024127, Id= 6, bootable
/dev/sda2 : start=        0, size=        0, Id= 0
/dev/sda3 : start=        0, size=        0, Id= 0
/dev/sda4 : start=        0, size=        0, Id= 0
Tip: if you have a working stick, store your partition layout using ’sfdisk -d /dev/sda > sfdisk.sda’ for later restore (via ’sfdisk /dev/sda < sfdisk.sda’). This is also very useful for cloning a working setup to other devices (though you might have to adjust cylinder/units later on). And of course you can use it as backup if you ran [sc]fdisk-commands on the wrong device. ;-)

20 April 2007

Jan Wagner: Is DNSSEC ready for wild life?

Today the RIPE DNS for LIRs Training Course did take place. (some not up to date course material can be found here)
Managing some thousands of zones inclusive nameserver infrastructure behind since several years, I thought it would be neat to provide a secure dns chain to our costumers.
After going deeper into the material within the course, I recognized the following impacts: Since the last issue isn’t solved (yet), it doesn’t make any sence for me to invest resources into setting up DNSSec infrastructur, cause the end user would not recognize if the communication with the resolving nameserver or the resolving nameserver itself is taken over. Any complaints and/or hint? Did I missed something? , , ,

19 April 2007

Adam Rosi-Kessel: Adam s Super Simple Guide to mbox->maildir conversion

There are a lot of pages out there explaining how to convert your mail from mbox to maildir. I’m going to add one more, resurrecting the “tips” section of my blog. (All the tips from my blosxom days are grouped together on one page — someday I’ll get around to breaking those up properly.) If nothing else, I’ll never have to write these instructions in an email to someone again, instead I’ll just send them the link to this entry. I hope these steps are specific enough so anyone savvy enough to even have this problem in the first place will be able to follow them. One thing I find consistently concerns people when converting to maildir is how to make sure no mail is lost in the transition. The steps below address that concern. It’s really not hard at all once you understand how maildir works. First, I’m assuming you have mb2md installed and procmail support. Also, if you plan to access your mail through IMAP, your IMAP server needs to know to use ~/Maildir if ~/Mail does not exist. This is often default behavior (at least it is for Dovecot). Finally, I assume that your inbox is in /var/mail/username, and your other mail folders are in ~/mail. So, here goes:
  1. Edit your .procmailrc. The first two lines should read:
    MAILDIR=$HOME/Maildir
    DEFAULT=$MAILDIR/

    This will cause all new mail to be delivered (after you save your .procmailrc) to be stored in maildir format under ~/Maildir. The key for procmail to know to use the maildir format is the trailing slash in the “DEFAULT” line. Note that under the new system, your inbox and all your folders are kept in ~/Maildir, rather than having an inbox in /var/mail and your folders under your home directory. (This is nice because it makes it easier to back up all your mail together, among other things).
  2. If you have any specific procmail rules in your .procmailrc, you’ll also need to change the target folders for that. For example, if you have a spam filtering rule like this:
    :0 H
    * ^X-Spam-Level: *****
    spam
    It needs to be changed to this:

    :0 H
    * ^X-Spam-Level: *****
    .spam/

    The trailing slash, again, tells procmail to use maildir rather mbox format for delivery. The leading dot will make the folder appear properly for your IMAP client (there’s a trick I suggest below for making “dot” folders easy to access with a command line client like mutt).
If you have mail being delivered to a nested mail folder, an additional change is needed because maildir has a flat hierarchy. So if your mail was being delivered to “misc/other/spam” the new target should be “.misc.other.spam/”.
  • Save your .procmailrc. From this point forward, all mail will be delivered to your maildir folders. You can now import all your old mail to the new folders without concern. Since maildir stores each individual message as a separate unique file, you don’t need to worry about any overwriting issues while you are making the transition. New mail will be delivered to newly named files; old mail will be imported to other, unique, newly named files.
  • Import your mail folders:
    mb2md -s ~/mail -R
    The -R just means to import recursively through all your folders; if your mail folder is Mail rather than mail, use that instead. No destination is needed because mb2md uses ~/Maildir by default.
  • Import your inbox:
    mb2md -m
  • Move your old inbox out of the way. Most people won’t actually be able to move or delete files in /var/mail (since they don’t have directory write privileges), so the easiest thing is probably to just open the inbox in your IMAP client or with mutt and save or delete all the messages.
  • Move your old mail folder out of the way:mv ~/mail ,.bak Once you’ve confirmed that everything is okay, you should be able to delete ~/mail.bak (or compress it and move it elsewhere.) If you saved your inbox to mail folder in step 6, that will get moved out of the way here as well.
  • That’s it, you’re done.
  • Okay, so you’re not quite done if you access your mail with mutt rather than an IMAP client. (You could just point your mutt at your local IMAP server, of course). I’ve found the most convenient way to access the “dot” folders with mutt is to create a parallel symlinked folder structure without the dots. Here’s a hacked-together shell script that will do that. This could obviously be rewritten to be much more elegant (probably in perl). But we all have our messy scripts, right?

    #!/bin/bash
  • cd ~/Maildir for x in .*
    do
    y=$ x##.
    if ( echo $y grep -q ‘.’ )
    then
    mkdir -p ~/mymail/$ y%.*
    fi
    ln -s ~/Maildir/$x ~/mymail/ echo $y sed “s/.///g”
    done for x in *
    do
    ln -s ~/Maildir/$x ~/mymail
    done
    Then, just add these lines to your .muttrc file:
    set folder="~/mymail"
    set spoolfile=”~/mymail”
    Any questions?

    18 April 2007

    Jordi Mallach: Debian's GNOME 2.18: are we there yet?

    The short answer is no, but as our status page easily reflects, there has been lots of work going on during the last two weeks, once etch's release unblocked the way to upload new versions to unstable. This post intends to resume the trend of updating on the status of GNOME in Debian, after we ended up deciding we'd ship etch with 2.14 for a number of reasons, most notably some complications with the GTK 2.10 transition at that time. You'll be able to find other related news items in Debian GNOME team's website. What has the Debian GNOME team up to during the last 6 months? Our first priority was to focus on unstable's GNOME 2.14 packages again, in an attempt to fix any outstanding remaining bugs from our packaging, and get them in the best shape possible to deliver a polished GNOME desktop for etch. I think the result is really good, and Debian's default GNOME desktop is both very usable and attractive. In parallel, the preparations for a complete set of GNOME 2.16 packages continued in our Subversion repository and kept appearing, little by little, in experimental. The most visible consequence of our 2.16 efforts translated into nobse's backport of 2.16 for etch, which can be found in the corresponding repository. And then, with etch deep frozen and nearly ready to be released, GNOME 2.18 was released, and of course the GNOME team didn't wait too much to start working on it. Our current status is looking good: the Developer Platform is already available in unstable, although buildd's are fighting the builds on various architectures. When the dust settles (GTK 2.10's landing has generated quite a big cloud; we have a list of packages that still haven't completed the GTK+ 2.10 transition), we'll be able to prepare and upload the more complex Desktop components like the panel, nautilus, evolution or control-center. Unstable users should probably be seeing daily progress on this front, so keep an eye on your package managers! Although Debian 4.0 released with an old version of GNOME, vast amounts of time and work have been invested to release it with the necessary backported fixes and enhancements. The newer GNOME versions have been available in Debian official ftp archives in very reasonable timeframes; this has only been possible thanks to the restless efforts of the (fortunately) growing Debian GNOME team members: giskard, feedback, HE, lool, np237, slomo, shaka, sjoerd, xaiki and not forgetting our incredible bug triager, svena. Thanks! On the behind the scenes department, it's a pleasure to report that Lo c Minier and Jordi Mallach very recently joined the GNOME Foundation's board of advisors in representation of the Debian Project, replacing Matthew Garrett, who has been representing us for the last few years until he left the project. Thanks, Matthew!

    Ben Armstrong: The children of Debian

    Who are the next generation of Debianists? Are they all still coming to us out of different OS backgrounds, or do we now have the significant beginnings of a home grown generation, born and raised in Debian-using families and now making their voices heard? I hope that Debian Jr. will encourage this kind of generational growth of the project. When recently I rewrote the guiding principles of Debian Jr., my vision was a Debian that children would identify as their own. I expect they will be eager to add their own ideas as they grow up with it. It was pointed out to me today that there is some evidence that this is already happening (thanks for the link, Matthew Wilcox). As for my own kids, ages 16, 15, 12, 9 and 5, only the oldest have ever used some system at home other than Debian1. They all comfortably use our Debian systems daily, discussing regularly with me what they need. This leads to filing bugs and patches on their behalf2, and inspires further development of the Debian Jr. project. So, in at least this sense, the children of Debian are already contributing members of Debian, if not voting members. The ideas of families are improving Debian for everyone. As the project grows, I expect the ways in which families will change Debian will be more significant, not only technically but also in Debian’s character.

    1 Before we started using Debian in 1995, the family system was a VT-420 terminal connected to the Solaris system running our community freenet. At that time our kids would sit in my lap and play at typing into pico for their amusement.

    2 For instance, I was pleased to discover the other day that my egoboo patch was accepted. That was a direct result of my kids asking me to make it work for them.

    Next.

    Previous.