Search Results: "ag"

25 June 2007

Adeodato Sim : Reminiscence

During the landing of my flight back to Alicante, I had my powered off laptop lying on my legs. A stewardess approached me and asked me to place it on the bag in the seat in front of me. I looked at her, and said: “Does not fit.”

Adeodato Sim : Debconf7 report

So Debconf7 has come to an end, and I’m pretty sure this has been my best Debconf so far. Although I did not manage to attend many talks and discussions, and did not socialize as much as I would’ve wanted with the people I did not already know (does Mao count as socializing?), I’ve on the other hand felt good throughout all its duration, which is great. On the productivity side, I think I’ve done okay. Strangely enough it’s not been Debian the main target of my hack hours, God only knows why. Instead, I made a couple of contributions to Bazaar, one of the new generation distributed version control systems. But I’m sure my Debian work will gain momentum in the near future, so no worries. Finally, I must say I’m in debt with a bunch of people who thought it was worth having me attend, and brought me here when it seemed it was too late. I’m very grateful for that, really. As always, thanks to the orga team for their terrific work, and hope to make it to Argentina next year. Update 1: Forgot to say, I went to the Genderfuck party in The Forest. It was pretty cool, and a first. Update 2: Brittish Airways lost my luggage (and I seem not to be alone in this). P.S.: I think I’ve got the Debconf flu. \o/

James Morrison: Bike Pictures

Here are the pictures I promised a while ago.




Christine Spang: New Hackergotchi?

I feel like this picture would make a decent new hackgotchi (with up-to-date hair!). I wonder if I could bribe someone with better GIMP-fu to make this happen. <twiddle>

Christoph Berg: Debconf: Home Again

I'm finally home again. Thanks to all the people who make DebConf such a great experience.

24 June 2007

Jon Dowland: DebConf7

I want to write a blog entry about DebConf but I'm simply lost for words. Thank you to everyone for coming and making it such an incredible two weeks. Thanks to the rest of the orga team for working so hard; thanks to all of the non-orga people who have pitched in and saved the day countless times. For those of you I have not met in person before, it was a pleasure to do so: for those I have, it has been fantastic getting better acquainted. I am now back home and back online for the first time in months. Its now time to dust off my Debian todo list (NM; packaging etc.) and see what needs doing... I have at least one objective for the next DebConf (or possibly the next Debian UK BBQ): get the doom stuff in Lenny to a suitable quality that we can have much larger and more reliable deathmatches. I think the teviot building would make an excellent doom map, too.

Adam Rosi-Kessel: Twitter s Value

I’m still figuring out whether Twitter is more than a distraction. It occurs to me that it has perhaps the three most important design elements for a successful new web-based (and particularly social-networking) technology:
  1. Twitter works as a simple general-purpose tool with very little structure determining how, exactly, people are supposed to use it. Compare, for example, with the many social networking sites (Friendster, LinkedIn, Tribe.net, etc.), each of which have a fairly specific idea about how people should use it (dating, professonal networking, and, um, whatever they do on Tribe, respectively). The only limitations on how Twitter can be used are a few aspects that are defined by the medium — basically, messages short enough to fit into an unextended cell phone text message.
  2. Twitter doesn’t duplicate any existing system or medium for communication. Compare, again, the social networking sites, each of which has some version of “email” that is internal to the site. Would I ever want to “send someone a message through LinkedIn” if I actually had their email address? Twitter, on the other hand, doesn’t have an exact one-to-one correspondence with any existing email, text messaging, or instant messaging systems. It’s a sui generis form of communication.
  3. Twitter doesn’t require everyone to sign up to participate. Anyone can follow my Twitter feed without actually having their own Twitter account. This is essential to solving the “critical mass” problem. Of course there are benefits to establishing an account, but as far as I can tell, the only features that you don’t get without an account are those which necessarily would require an account. (Compare, again, most of the networking services mentioned above, where you need an account to view people’s profiles.)
(Add to this, of course, the now standard requirement that Twitter is free, at least as in beer.) Now, I’m still not exactly sure how best to use Twitter, but there are some interesting commercial and non-commercial applications featured on the Twitter blog, e.g, this promotion from Dell, and this guy “Twittering My Diabetes.”

Jose Carlos Garcia Sogo: iPhone and the corporate environment

Enrique Dans writes about the "The Coming Battle: Apple's iPhone vs. Corporate IT Departments". He makes an interesting point on how this new gadget can be a point of friction between managers of IT departments and their employees using this kind of gadgets, usually corporate executives. Syncing the database with RIM devices, or redirecting email accounts (iPhone is not capable of using corporate Blackberry or MS Exchange servers), can be a problem in corporate world. If you read those articles, they blame iPhone for not supporting all these enterprise-class software.
Incompatible technology has become an increasing problem for businesses as hand-held email and phone devices are evolving into minicomputers that can do such things as download music, take pictures and surf the Web. In the past, businesses have been unwilling to support certain devices, like those with cameras, for instance, because of concerns employees could use them to document company secrets. ... A business email system can use a popular email standard known as IMAP to sync with an iPhone. While many large companies have the ability to activate IMAP, they have chosen not to because they are worried about exposing their mail servers to the public.
Basically, IT departments are blaming iPhone for not supporting their competition systems, and they are not requiring all them (and themselves) to be using standards, which were just designed to avoid this kind of problems. They are afraid. No more comments.

Jose Carlos Garcia Sogo: iPhone and the corporate environment

Enrique Dans writes about the "The Coming Battle: Apple's iPhone vs. Corporate IT Departments". He makes an interesting point on how this new gadget can be a point of friction between managers of IT departments and their employees using this kind of gadgets, usually corporate executives. Syncing the database with RIM devices, or redirecting email accounts (iPhone is not capable of using corporate Blackberry or MS Exchange servers), can be a problem in corporate world. If you read those articles, they blame iPhone for not supporting all these enterprise-class software.
Incompatible technology has become an increasing problem for businesses as hand-held email and phone devices are evolving into minicomputers that can do such things as download music, take pictures and surf the Web. In the past, businesses have been unwilling to support certain devices, like those with cameras, for instance, because of concerns employees could use them to document company secrets. ... A business email system can use a popular email standard known as IMAP to sync with an iPhone. While many large companies have the ability to activate IMAP, they have chosen not to because they are worried about exposing their mail servers to the public.
Basically, IT departments are blaming iPhone for not supporting their competition systems, and they are not requiring all them (and themselves) to be using standards, which were just designed to avoid this kind of problems. They are afraid. No more comments.

Steve Kemp: Unknown, even to its own employees, its massive profits are generated by military technology, genetic experimentation and viral weaponry

The scanning of the Debian source archive for security bugs has begun. I've wrote about this previously and there was some interest in how it worked, so I've put up a simple webpage describing the process. There are a lot of results to go through, but so far I've managed to find one local root exploit and many many many trivial problems. Sample bugs: Unfortunately my usertags seem to be broken. This was working a day or two ago. Not sure if I fucked up or if the BTS is broken ..?

Nico Golde: colored manpages

Last Friday we had a small but pretty cool linux event at University. There was also a presentation about grml and when Valentin showed that the manuals on grml are in color there were alot of people saying "wow I want that too" :-)

grml includes this feature since version 0.1 (thanks to Matthias Kopfermann who brought this up and had the initial idea) but alot of people don't know how that works (without using most as PAGER, most has some disadvantages over less).

So here is how it works:

colored manpage
$ mkdir ~/.terminfo/ && cd ~/.terminfo
Now get the terminfo description:
$ wget http://nion.modprobe.de/mostlike.txt
Now compile it using tic (the terminfo entry-description compiler)
$ tic mostlike.txt
(you may want to delete the mostlike.txt file after compiling)

And then just define an alias in the rc file of your favorite shell.
alias man="TERMINFO=~/.terminfo/ LESS=C TERM=mostlike PAGER=less man"

That's it!

If you want to modify the terminfo file, use infocmp mostlike to get the content of it later.

Gustavo R. Montesino: bug-triage 0.1

Yet another GSoC release; it's the first release of the real tool this time. From the release announcement sent to bug-triage-devel:

----

I'm pleased to announce the release of bug-triage 0.1.

bug-triage is a tool to help triaging Debian bugs.

Current features:

* Show all bugs which match a given bug number, source package,
package, maintainer or submitter

* Show details about one of the returned bugs on the user's
web browser

The source code for bug-triage is available at
http://bug-triage.alioth.debian.org/

Debian packages are being worked on and should be available soon.

Julien Valroff: Iceweasel is not Firefox!

capture-virginmega-iceweasel.pngVirginMega.fr is a one of the French music download service which offers MP3 files (without DRM). They previously prevented all the browsers except MS Internet Explorer on MS Windows platform from accessing their website. I (we) used to change the browser id thanks to the FF User Agent Switcher plugin.
It now seems they have changed their mind under the pressure of Linux users. However, it seems there is still a problem for me (us) to access their website as they do not use the engine (Gecko in our case), but the user agent name… No, Iceweasel is not Firefox! Nor is Galeon! But why blocking access to a website which works perfectly with these browsers which share the same engine?

Russell Coker: Xen and Heartbeat

Xen (a system for running multiple virtual Linux machines) and has some obvious benefits for testing Heartbeat (the clustering system) - the cheapest new machine that is on sale in Australia can be used to simulate a four node cluster. I’m not sure whether there is any production use for a cluster running under Xen (I look forward to seeing some comments or other blog posts about this). Most cluster operations run on a Xen virtual machine in the same way as they would under physically separate machines, and Xen even supports simulating a SAN or fiber-channel shared storage device if you use the syntax phy:/dev/VG/LV,hdd,w! in the Xen disk configuration line (the exclamation mark means that the volume is writable even if someone else is writing to it). The one missing feature is the ability to STONITH a failed node. This is quite critical as the design of Heartbeat is that a service on a node which is not communicating will not be started on another node until the failed node comes up after a reboot or the STONITH sub-system states that it has rebooted it or turned it off. This means that the failure of a node implies the permanent failure of all services on it until/unless the node can be STONITH’d. To solve this problem I have written a quick Xen STONITH module. The first issue is how to communicate between the DomU’s (Xen virtual machines) and the Dom0 (the physical host). It seemed that the best way to do this is to ssh to special accounts on the Dom0 and then use sudo to run a script that calls the Xen xm utility to actually restart the node. That way the Xen virtual machine gets limited access to the Dom0, and the shell script could even be written to allow each VM to only manage a sub-set of the VMs on the host (so you could have multiple virtual clusters on the one physical host and prevent them from messing with each other through accident or malice). xen ALL=NOPASSWD:/usr/local/sbin/xen-stonith Above is the relevant section from my /etc/sudoers file. It allows user xen to execute the script /usr/local/sbin/xen-stonith as root to do the work. One thing to note is that from each of the DomU’s you must be able to ssh from root on the node to the specified account for the Xen STONITH service without using a password and without any unreasonable delay (IE put UseDNS no in /etc/ssh/sshd_config. The below section (which isn’t in the feed) there are complete scripts for configuring this. (more…)

Mike Hommey: Playing more with LVM, LUKS and the device mapper

Following my previous entry about playing around with LVM, LUKS and the device mapper, I documented myself about internals involved in pvmove, which is more of a challenge, considering there is no such documentation. I could find no useful documentation for either the device mapper or LVM. A bit of good old UTSL later, I could elaborate how to do what I wanted, and realized it was even possible to do in shell script. So here you are : a shell script to transform an LVM physical volume to a LVM over LUKS physical volume,. I’ll detail in between how it works. As the previous script, use at your own risk, it comes with no warranty.
Note you theorically can still access the filesystems underneath without problems. It’s an in-place and live conversion. Also note this is more a proof of concept than a proper, risk-less and well-written solution.

set -e
dev=$1
luks=$(mktemp)
cryptdev=$(basename $dev)_crypt
pvsize=$(pvs -o pe_start,pv_size --units s --noheadings --nosuffix "$dev" awk ' print $1 + $2 ')
devsize=$(blockdev --getsz "$dev")
mchunk=8
The script takes the physical volume device to convert as an argument. Note there is no check for the validity of its value.

dd of="$luks" seek=$devsize count=0 bs=512 2> /dev/null
luksdev=$(losetup -f)
losetup "$luksdev" "$luks"
trap "losetup -d \"$luksdev\"; rm -f \"$luks\"" EXIT
Next, we create a sparse luks file the same size as the device (in case luksFormat would use the size somehow, but I believe it doesn’t), and a loopback device on this file. The trap is here to avoid leaving the loopback device and the file when an error occurs later (though during the conversion itself, it will be pointless).

cryptsetup luksFormat -q "$luksdev"
cryptsetup luksOpen "$luksdev" $ cryptdev _real
read start length crypt format key IVoff cdev offset <<EOF
$(dmsetup table $ cryptdev _real)
EOF
We create a LUKS device, so that we can get the encryption key ($key), and the size of the LUKS header ($offset). Note you need to add –showkey to the dmsetup table command on sid.

if [ $(expr $devsize - $pvsize) -lt $offset ]; then
  echo Not enough free space after LVM physical volume
  cryptsetup luksClose $ cryptdev _real
  exit
fi
Check we have enough space after the LVM physical volume to offset everything by the size of the LUKS header. If not, you can still try again after you reduce the size of the LVM physical volume by an extent.

if [ $(expr $devsize % $offset % $mchunk) -gt 0 ]; then
  echo Last
  cryptsetup luksClose $ cryptdev _real
  exit
fi
This is another check to avoid surprises at the end, when dealing with the last chunk. As the script is written for the moment, it doesn’t support cases where this last chunk is not a multiple of $mchunk. So we need to abort in these.

read major minor <<EOF
$(stat -t "$dev" awk ' print $10,$11 ')
EOF
maps=$(dmsetup deps awk -F: "/\($major, $minor\)/ print \$1 ")
dmsetup create $cryptdev <<EOF
0 $length linear $dev 0
EOF
dmsetup reload $ cryptdev _real <<EOF
$start $length crypt $format $key $IVoff $dev $offset
EOF
dmsetup resume $ cryptdev _real
for map in $ maps ; do
  dmsetup table "$map" sed s,$major:$minor,/dev/mapper/$cryptdev, dmsetup reload "$map"
  dmsetup resume "$map"
done
Here, we create the dev_crypt device mapper that is our fake LUKS device, which starts as a simple linear mapper and will end as a complete crypt mapper. This fake LUKS device is inserted as an intermediate mapper between the LVM device mapper and the real device. So, the LVM device mapper will have this fake LUKS device as backend, and, at the beginning, the fake LUKS device maps linearly to the real device. Note we look for all device mappers using the real device as backend before creating the fake LUKS device to avoid finding the fake LUKS device in the list. Also note dmsetup reload only loads a new table in the INACTIVE slot, and dmsetup resume makes this inactive table LIVE.

cursor=$length
chunk=$offset
while [ $cursor -gt 0 ]; do
  cursor=$(expr $cursor - $chunk)
  if [ $cursor -lt 0 ]; then
    chunk=$(expr $chunk + $cursor)
    cursor=0
  fi
  (
  [ $cursor -ne 0 ] && echo 0 $cursor linear $dev 0
  echo $cursor $chunk mirror core 1 $mchunk 2 $dev $cursor /dev/mapper/$ cryptdev _real $cursor
  [ $cursor -lt $(expr $length - $chunk) ] && echo $(expr $cursor + $chunk) $(expr $length - $cursor - $chunk) crypt $format $key $(expr $IVoff + $cursor + $chunk) $dev $(expr $offset + $cursor + $chunk)
  ) dmsetup reload "$cryptdev"
  dmsetup resume "$cryptdev"
  chunks=$(expr $chunk / $mchunk)
  while ! dmsetup status "$cryptdev" grep "$chunks/$chunks"; do
    true
  done
done
This is where the main work is done : moving the data around. We actually just let the device mapper deal with the data duplication, $offset blocks by $offset blocks ($offset being the LUKS header size), using a mirror target for the chunk being moved. So our disk looks like the following:

We use the extra dev_crypt_real device (the previously remapped LUKS device) as the encryption backend for the mirror.
I haven’t figured a better way to wait for the end of the mirroring than to do a loop checking with dmsetup status, dmsetup wait doesn’t seem to be very helpful here.
Anyways, this is the part of the script where you don’t want a crash to occur. Because if it does, all you can do is start on a rescue system, and try to find where the encrypted part of the disk start to setup a device mapper by hand.
And you’d better have the luks temporary file in a directory that is neither in RAM (think tmpfs) nor in the LVM you are converting (/tmp in a default etch install is, for instance ; note the script works nevertheless fine in this case). Also note the trap will remove the luks temporary file if the script exits…

dmsetup reload "$cryptdev" <<EOF
$start $length crypt $format $key $IVoff $dev $offset
EOF
dmsetup resume "$cryptdev"
dmsetup remove "$ cryptdev _real"
dd if="$luks" of=$dev count=$offset bs=512 2> /dev/null
Final steps of the conversion : our dev_crypt device becomes a full LUKS volume, so we can remove dev_crypt_real and add the LUKS headers at the top of the device we converted. At this moment, the LUKS volume is setup just as if it had been setup by cryptsetup. For LVM to recognize the change properly, you need to run pvscan. Once you ran it, you can do whatever you want with LVM. Now, you may want to add the following to your /etc/crypttab file:

$cryptdev $dev none luks
i.e. hda5_crypt /dev/hda5 none luks if the device was /dev/hda5. And if the LVM volume you converted contains your root filesystem, you should run (for Debian systems):

update-initramfs -u
I tested this successfully under qemu and will give it a shot on my laptop some time soon. Now, because I had a hard time not finding much about the mirror target of the device mapper, here is what I could gather about it. The target syntax is as follows:

<logical_start_sector> <num_sectors> mirror [ core disk ] <num_params> <param> ... <num_mirrors> [ <destination > <start_sector> ] ...
logical_start_sector, num_sectors, destination and start_sector have the same meaning as in other targets.
core and disk are two different log types (to track differences between mirrors), respectively in memory and on disk.
num_params and params depend on the log type: num_mirrors is the number of mirrors and for each mirror, we have a pair destination and start_sector. [ Update: after a quick look at the device mapper source code in Linus’s git tree, updated the mirror target description ]

Mike Hommey: Videos of Debconf 7

The good thing about not being able to attend Debconf is that you can still watch the talks online. Well, when you can find the videos. While it’s pretty easy to find the video streams, that, when you’re a working european, are pretty much of no use, I couldn’t find a single link to the video archives that were supposed to be available the same day. Why oh why does the debconf7 homepage lack such an important link ? Why does video.debconf.org show a phpmyadmin login form ? Anyways, for those who, like me, haven’t found a link, here’s one : Video archives for Debconf 7.

Dirk Eddelbuettel: New OpenMPI packages

Debian had OpenMPI package since early last year when Florian Ragwitz made some initial stabs at packaging. The package has seen a number of NMU and patches since then, but was generally getting cobwebs ... which was too bad because OpenMPI seems to have some wind behind its sails upstream. Unfortunately, little of that got packaged for Debian. After some discussions on and around the debian-science list, a new maintainer group was formed on Alioth under the pkg-openmpi name. Tilman Koschnick (who had already helped Florian with patches), Manuel Prinz, Sylvestre Ledru and myself have gotten things in good enough shape in reasonably short time. And I have just uploaded a lintian-clean package set openmpi_1.2.3-0 to Debian, where it is expected to sit in the NEW queue for a little bit before moving on to the archive proper. The changelog entry (which will appear here eventually) shows twelve bugs closed. Our plan is to provide a stable and well maintained MPI implementation for Debian. OpenMPI is the designated successor to LAM, and apart from MPICH2, everybody seems to have thrown their weight behind OpenMPI. So we will try to work with the other MPI maintainers to come up with sensible setups, alternatives priorities and the likes. If you are interested in MPI and would like to help, come join us at the Alioth project pkg-openmpi. Last but not least, thanks to Florian for the initial packaging, and to Clint Adams, Mark Hymers, Andreas Barth, and Steve Langasek (twice even) for NMUs.

23 June 2007

John Goerzen: This week's discovery: mpix.com

Back in 2000, I started to get back into photography. I bought a Canon Elan IIe 35mm SLR camera, some lenses, and a flash. I took color photos various places, and then bought some standard Kodak T-Max black and white film. I shot some photos, and then tried to get this film processed.

Turns out it's not terribly easy to pay someone to process black and white film. Very few of the local photo places will do it. The place I usually used was willing to send it off to Kodak for me. Lacking a darkroom at home, and any interest in doing darkroom work myself, I sent it off to Kodak.

Kodak processed my film just fine, but the prints they made were terrible. It looked as if their enlarger was seriously out of focus. Everything was fuzzy on the prints. The local shop agreed to send them back for re-printing. On try 2, they were somewhat better but not much.

Now, B&W photos should normally be sharper than color photos, so this was nanoying.

I kept looking, and nobody locally could print B&W photos. I even tried one roll of B&W C-41 film (that's color-process film that takes photos in black and white). It stank about as much as I thought it would. I did eventually find one local lab that could take B&W negatives and, via a digital process, print the photos on color paper. They came out far more crisp than Kodak's processing on real B&W paper!

Now, 7 years later, I've been shooting some photos with my Canon Digital Rebel XTi digital SLR camera that I want to print in black and white. There are any number of color labs that I can send them off to, and get results as sharp as one would expect from a color photo. I'd been doing that with reasonable results. But I wasn't satisfied with "reasonable", so I searched some B&W groups on Flickr to see what people were doing to make B&W prints from a digital source.

It was there that I learned of mpix.com, the online service of the USA's largest pro photo lab. They offer printing on true B&W photo paper from digital (or film) sources. They're a pro lab, so they ought to do this really well. They of course also do color printing. Plus all the other things you'd expect from a pro lab, such as red-eye removal, glasses glare removal, color retouching, choice of photo paper, etc.

I sent off my first order for B&W prints to them yesterday. I can't wait to see how they turn out. I'm excited -- I think they'll be great.

Andrew Pollock: [debian] Huzzah for Debconf 7

So Debconf 7 has been good. Very good. I suck at writing up such events, but I found it a great opportunity to hack on my packages. I got my laptop setup so I could work moderately effectively offline (there's still more I can do), and I was able to work on the DHCP 3 packages fairly heavily. I'm particularly pleased that I fixed two long-standing bug-bears: the fact that the package only complied with a Standards-Version from about 5 years ago, and that the DHCP client udeb for the installer didn't work. I've fixed both of those issues, and done a pile of bug triage. Very happy. Due to various talks about git, I've also gotten over my fear of it, and had a play. It still fries my brane big time, but at least I've had a play. Onward to Dublin. Let's see if I can successfully reapply for my visa.

Junichi Uekawa: apt-listbugs changes for easier use by clients.

Having had a little discussion with Stefano Zacchiroli aboutdebian/changelog editing and bug number completion, Idecided I'll make the 'apt-listbugs list' command a bit moreuseful.It now has two new features.--severityall option to specify all severities, and you canspecify the current version with PACKAGE/VERSIONsyntax. These functionalities should be available in the0.0.79 upload.It also uses the shiny new BTS SOAPinterface, and no longer relies on merkel.debian.org, thanks to help from Don Armstrong.To find a bug that is not yet closed on apt-listbugs 0.0.79, you'll ask for it like this: apt-listbugs list -s all apt-listbugs 0.0.79

Next.

Previous.