Search Results: "will"

1 January 2008

Russell Coker: Low Power - They Just Don t get it

For a while I’ve been reading the Lenovo blog Inside The Box [1], even though I plan to keep my current laptop for a while [2] (and therefore not buy another Thinkpad for a few years) I am interested in the technology for it’s own sake and read the blog. A recent post concerns a new desktop machine billed as “our greenest desktop ever” [3]. The post has some interesting information on recycling plastic etc, and the fact that the machine in question is physically small (a volume of 4.5L and no PCI expansion slots) means that less petro-chemicals are used in manufacture (and some of the resins used are recycled). However the electricity use is 47W when idle!!! On my documents blog I have a post about the power use of computers I own(ed) [4] which includes my current Thinkpad (idles at 23W) and an IBM P3 desktop system which idles at 38W. Both machines in question were manufactured before Lenovo bought Thinkpad and IBM’s desktop PC business (so they technically aren’t Lenovo machines) and they weren’t manufactured with recycled resins. But the claim that the new machine is the greenest ever is at best misguided and could be regarded as deceptive. I think that the machine is quite decent, but it’s obvious that they can do a lot better. There’s no reason that a low-power desktop machine (which uses some laptop technology) should take more than twice the power of what was a high-end laptop a few years ago. Also comparing power use with P3 machines (which are still quite useful now, my IBM P3 desktop runs 24*7 as a server) is quite relevant - and we should keep in mind that before the Pentium was released no system which an individual could afford had anything other than a simple heat-sink to cool it’s CPU. This is largely a failing of Intel and AMD to make power efficient CPUs and chipsets. It’s also unfortunate that asymmetric multi-processing has not been implemented in recent times. A system with a 64bit CPU core of P3 performance as well as some Opteron class cores that could be suspended independently would be very good for power use with correct OS support. For example when reading documents and email my system will spend most of it’s time idling (apart from when I use Firefox which is a CPU hog) and the CPU use will be minimal for scrolling - a P3 performing core would be more than adequate for that task (which comprises a significant portion of my computer use). Then when I launch a CPU intensive task (composing a blog post in Wordpress or compiling) the more powerful CPU cores could start. It would be good if Intel would release a Pentium-M CPU (32bit) with the latest technology (smaller tracks on the silicon means less power use as well as higher clock speeds). A Pentium-M running at 2GHz produced with the latest Intel fabrication technology would probably use significantly less power than the 1.7GHz Pentium-M that is in my Thinkpad. Put that in a desktop machine and you would have all the compute power you need for most tasks other than playing games and running vista and you could get an idle power less than 23W. The new Lenovo machine in question does sound like a nice machine, I wouldn’t mind having one for testing and running demos. But the claims made about it seem poorly justified if you know the history.

Joey Hess: leap second mystery

Clock: inserting leap second 23:59:60 UTC
Happy leap second, everyone. The earth's rotation slowed by another second, and the extra second was added just before the new year. Or did it? According to the NIST "NOTE: No leap second will be added at the end of December 2007" So why did some of my machines see one and some not? All are running NTP, all using pool.ntp.org. Perhaps some NTP servers in the pool falsely inserted a leap second? According to this thread I'm not the only one to notice spurious leap seconds, one also happened in July 07, and this page documents one in July 06 with some great graphs. Figuring out whodonit is tricky.. (Insert conspiracy theory,thriller plot here.)

Joey Hess: big storm coming

Somewhere at the beginning of the holiday madness, which seems like a long couple of weeks ago, my laptop crashed and came up with a bad superblock. That's Not Good, but fsck fixed it, and I was too busy preparing for company and parties and trips and stuff to do anything about it. And forgot about it. Of course it died. Right before new years, and with only 5 minutes advance warning from SMART before it started spewing IO errors and corrupting files. I have a new drive on order, and am running diskless from NFS over wireless, which is an amusing way to use a laptop, but acceptable if you don't plan to go anywhere for a few days. Maybe they'll be snowbound days. This seems less of a disaster than other times a laptop's disk has died on me. When did it start to become routine? Maybe this will be the second to last time -- I certianly hope that my next laptop has a flash disk. The Debian Live CDs were quite helpful before I set up the NFS, and I even managed to use the default gnome desktop for an evening with them, without utterly hating it. My mr and etckeeper setup made it easy to check everything back out from revision control. So the tools for dealing with a dead laptop disk are improved, though d-i still doesn't support installs over NFS, which would have saved me some time setting that up. The first snow is starting to fall..

Julian Andres Klode: Bye, 2007 - Welcome 2008!


April 2007, I joined the Fellowship of the Free Software Foundation Europe. I also became involved in the development of Debian GNU/Linux with my first package, aufs, sponsored by Daniel Baumann. This was the starting point for my Debian stuff. Now I maintain 6 packages in Debian. One of the most interesting packages is gnome-app-install, which will be part of the gnome-desktop task (already added to tasksel’s list). Users will be able to install applications easily. It also activates the automatic codec installation, so users will be able to play most multimedia files easily. 30th December, I finally got assigned my AM, Martin Zobel-Helas (zobel), and I’m happy to be able to continue the NM process now. On the Ubuntu side, some things have happened, too. I merged several new versions of dir2ogg and a new aufs version, and became an Ubuntu Member on the 29th November. In 2008, I plan to complete the New Maintainer process and become an Ubuntu MOTU. I will continue my packaging stuff, and will merge new features from Debian to Ubuntu and from Ubuntu to Debian. A happy new year to everyone and sorry for blogging this such late.

Russell Coker: Fluorescent vs Incandescent lights

Glen Turner writes about silly people who think that fluorescent lights don’t save energy over their lifetime [1]. A compact fluorescent light (one that is designed for the same socket as an incandescent globe) is not the most efficient light source, the Luminous Efficiency page on Wikipedia [2] lists a CFL as having an efficiency of between 6.6% and 8.8% while fluorescent tubes can be up to 15.2% efficient and low pressure sodium lamps are 27% efficient! But given that low pressure sodium lights are unsuitable for most uses due to being monochromatic and having a long warm-up time and the fact that fluorescent tubes are often not suitable due to design an 8.8% efficiency is pretty good. LEDs can give up to 10.2% (and prototypes offer 22%) but don’t seem to be available in a convenient and reliable manner (they are expensive and the ones I’ve tried have been unreliable). When comparing fluorescent with incandescent one factor to consider is the power used. While high-temperature incandescent lights are quoted as having 5.1% efficiency and a 100W 110V tungsten incandescent globe is quoted as having 2.6% efficiency a 40W 110V globe will only have 1.9%. If you want to save energy then you probably don’t want to use 100W globes, using less light is the first way of saving energy on lighting! So the efficiency of incandescent lights used for the comparison should probably be closer to 1.9% than 2.6%. Now the theoretical performance won’t always match what you get when you buy globes. There is some variation of quality between manufacturers and there are at least two distinct “colours” of fluorescent lights (one is about 5800K - similar to our sun, the other is something over 8000K - blue-white), I expect some difference in efficiency between lights of different colour range. I see CFL lights marketed as being 5 times more efficient than incandescent lights, my observation is that they appear to be about 4 times more efficient (IE I replace a 40W incandescent with a 10W CFL or a 60W incandescent with a 14W CFL). Glen claims that an 8W CFL can replace a 60W incandescent globe, the only possibility of getting a factor of 7 or more efficiency improvement (according to the data on the Wikipedia page) would be to replace some 5W incandescent globes with CFL. In my experience (converting two houses that I lived in to CFL and the conversions of some friends) such an efficiency benefit is not possible on direct electricity use. However in a hot climate any waste heat needs to be removed with an air-conditioner. So when a 60W incandescent light is replaced by a 14W CFL there is 46W of waste heat removed, with an ideal efficiency of a heat-pump it would take 15W to remove that heat from a building (and possibly more if it’s a large building). So in summer we are not comparing 60W to 14W, it’s more like 75W to 14W. The issue of economics that Glen raises is more complex than it seems because governments often give companies significant discounts on electricity costs, EG in Australia aluminium refineries are subsidies heavily so they pay much less than home users. So hypothetically it could be possible to manufacture a device made entirely of aluminium which saves electricity (and therefore money for the user) but not enough to cover the electricity used in aluminium refining. However when we consider the margins of the various middle-men it seems quite unlikely that such a hypothetical situation could actually happen. As for the issue of mercury in fluorescent lights there are two things to consider. One is that it is possible to recycle mercury (in Australia at least), the other is that coal fired power plants have a lot of mercury in their smoke…

31 December 2007

Erich Schubert: Google results WTF

It seems like Google broke something in their search. For example, searching for "iTunes-library-xml Python" (I've just written a parser which will turn Apple PropertyList Pseudo-XML into a useable Python object consisting of hashes, arrays, integers etc. btw.) actually gives me results (at least the one around #4) that don't contain "iTunes" (and I'm pretty sure also never contained).OUCH:Looking at the cached version of the result when searching for "iTunes library xml python" contains the notice "The word iTunes is only found on pages linking to this page". Google knows two pages linking there, neither contained the word iTunes.This is not what I understand as an "exact phrase match".

Kartik Mistry: Looking back at year..

* It has been really good (and bad) year for us. I managed to achieve 60% of my wishlist in 2007 and yes, Kavin is our great achievement of the year ;) I was almost 1/2 year away from home and looks like that 2008 will be almost same for first quarter :( * We had great new year party at office. K and Kavin also enjoyed some moments! The best part was movie The school of Rock. Event management was very well done (TM of our HR :)). * Not going to outside for any party. Listening: Us and Them (Pink Floyd) and trying to fix dupload issue(s) with my damn slow connection.

Meike Reichle: Happy new year!

The year is almost over and a lot has happened. I finished my studies and got engaged, (Again, thank you very much for the many, many congratulations and warm wishes!) now, just before the year is really over I decided to finally make another commitment. Now, I guess the first thing I'll turn to will be Tasks and Sp tzle. ;)

Mark Brown: Security here we come

The IMAP client provided with the version of Symbian on my phone has an interesting way of verifying certificates used for encrypting IMAP connections. As one would expect the client verifies the signatures on the certificate offered by the IMAP server and will prompt the user if it sees signatures that it can’t trace back to an authority it trusts. Unfortunately it is not possible to tell the device to remember the decision which means that when the device prompts it will prompt every time it connects to the server in question. The result of this is user irritation and a reduction in security since there is much less chance that a changed server certificate will be noticed. You would expect that there would be a lot of users encountering this given that so many sites don’t use a signed certificate but it turns out that this is not the case. Someone must have realised how many systems would be affected and so a solution was provided - if the server is using an unsigned certificate then the phone will accept it without warning the user at all. Only servers with signatures from an unknown trust source like a private certificate authority will cause the user to be prompted to verify the server certificate. This avoids both user irritation and any chance that the user will actually verify the fingerprint of the server they are connecting to, exposing users to spoofing and redirection based attacks. Clearly someone hasn’t thought through what they’re doing here - it all rather defeats the point of signing in the first place. On the bright side, this is the first Symbian phone I have seen where the native IMAP client encrypted connections at all so having this problem is progress.

Masayuki Hatta: What I did in 2007, What I will do in 2008

I just came back from Taiwan(went there basically for TWDebCamp2007) tonight. I met lots of great people down there and had lots of fun. I'll write about it later. Theoretically speaking, I was supposed to have decent Internet connections everywhere, but in most cases it didn't work or I was away from it anyway(and we had busy schedule!). So now I'm kinda catching up things quickly, especially what happend on the Net lately. Anywise, it would be a good time to look back 2007 and foresee 2008. Personally, these things were significant for me in 2007:
Finished GPLv3
GPLv3 is finally out, and I'm proud I took part in the revision process. Also I could manage to finish my Japanese translation of GPLv3/LGPLv3. Now my translations are being reviewed by lawyers and other legal professionals, so it will be more sophisticated soon.
Establishing MIAU
As I wrote before, we founded a little organization called MIAU, in hope of becoming a Japanese version of EFF. At the copyright war front in Japan, we are partly losing the battle since the Japanese government essentially ignored our 1800+ unique public comments and seems dare to go the wrong direction somehow. However, we are not going to give up easily -- next year, we will sophisticate our tactics and try to get more people involved. Chris Salzberg wrote up a series of great articles on these or related issues in English, and also submitted his story to Slashdot.
Joined Wikimania 2007
This was also a great fun in Taiwan. I gave a talk at there and also met many great people.
Released GNU a2ps 4.14
Well, this is far less significant, but the new release is now out. I hacked up this release in my hotel room just before I left, so may contain stupid bugs. anyway, as usual, enjoy.
So, now we seem to be in 2008 now. Happy New Year or whatever. I'm gonna do the following this year, at least:
Finish my PhD thesis
This will be the highest priority, of course. I'm planning to make it be a comprehensive study on FLOSS from management/organizational theorists' view. Will contain some math. Maybe not.
Finish my book
I'm still writing a book on Open Source licensing. This was supposed to be done within 2007, so it's long overdue now.
Finish translations
I'm still translating Peter Seibel's great book Practical Common Lisp into Japanese. Also, I guess I should update my Japanese translations of www.gnu.org.
Reduce weight
I'm obviously overweight. I'm gonna go to swim, cycling, or even jogging, and do my best not to eat too much. I'm serious!
Anyway, again I'd say Happy New Year to all, and enjoy your life.

Tag this post with del.icio.us!

Evan Prodromou: 10 Niv se CCXVI

My friend Hugh McGuire asked me if there were any privacy concerns with OpenID. Since this is kind of a complex question, I decided to answer it with an essay, OpenID Privacy Concerns, which I think is pretty useful to anyone thinking about using OpenID. tags:

Weight weight don't tell me So, I'm in Los Altos at my parents' house for the holidays, and I've been working out at the Page Mill YMCA. Today I went in for my last weight-lifting session of the year. I also weigh myself on weight-lifting days (about once every 4 days), so this was my last weigh-in of the year, too. I'm glad to say that I've now got a body mass index of 29.4 -- down from a measured value of 38 in September. That was a little bit under my goal weight for the year-end, which was nice to hit. It's been a really precipitous drop in weight and increase in fitness this year, which I've been pretty proud of. There's still more ahead -- a "normal" weight is about 25. But I'm feeling healthier, and I look better, than I have in years and years. I think 2008 will see a slower weight loss, more stabilization, and exploration of some different sports and activities to keep the exercise fresh. tags:

Joerg Jaspert: HTML output for packages in NEW

You may remember that, short before the release, Aj had a HTML page for packages in NEW, living in his ~/ajt/new/ on our ftp-master host. It was based on a patch from Thomas Viehmann and got lost with the ries crash. Today I reimplemented it, putting it directly into dak and the ftp-master codebase and webtree. My work is also based on Thomas patch, but I reworked the whole thing a bit. I’ve written a new dak command, show-new, which is based on process-new, the command I always use when I process NEW packages. Obviously not with all that functionality, it doesn’t need any reject capability, but it still has some nice parts. Like To not duplicate code too much this also meant that various code blocks had to be moved into daklib/ files. If you want to look at it - the NEW Overview, something that I wrote long ago, has links to the per-package-version files. Just click on the version number. I have plans to enhance it even more, like having the lintian output use colors too. To make that easy I filed a bug against lintian asking for it. For the other changes - well. I think the layout can be enhanced, possibly going a bit in the direction of the removals summary page, but that will take some time, as I need to talk to my CSS-masters for it. And while I was changing dak code I did some more changes to it. One patchset already got applied from James, removing the obsolete non-US support. I have a large number of other changes, but have to redo them, much more using bzr branches, so James can more easily pick single changes out of them. The changelog for those applied changes is pretty impressive with its length, I think…
2007-12-30  Joerg Jaspert  joerg@debian.org>
        * dak/dak.py (init): add show-new. This is based on a patch
        submitted by Thomas Viehmann in Bug #408318, but large parts of
        handling it are rewritten and show-new is done by me.
        * dak/queue_report.py (table_row): Add link to generated html page
        for NEW package.
        * dak/show_new.py: new file, generates html overview for NEW
        packages, similar to what we see with examine-package.
        * config/debian/cron.hourly: Add show-new call
        * config/debian/dak.conf: Add HTMLPath for Show-New
        * dak/examine_package.py (print_copyright): ignore stderr when
        finding copyright file.
        (main): add html option
        (html_escape): new function
        (escape_if_needed): ditto
        (headline): ditto
        (colour_output): ditto
        (print_escaped_text): ditto
        (print_formatted_text): ditto
        - use those functions everywhere where we generate output, as they
        easily know if we want html or not and just DTRT
        (do_lintian): new function
        (check_deb): use it
        (output_deb_info): Use print_escaped_text, not print_formatted_text.
        Also import daklib.queue, determine_new now lives there
        Also add a variable to see if we want html output. Default is
        disabled, show_new enables it for its use.
        Most of html, besides header/footer are in examine_package instead
        of show_new, as it makes it a whole lot easier to deal with it at
        the point the info is generated.
        * dak/process_new.py (determine_new): Moved out of here.
        (check_valid): Moved out of here.
        (get_type): Moved out of here.
        * daklib/queue.py (determine_new): Moved here.
        (check_valid): Moved here.
        (get_type): Moved here.
        * dak/init_db.py (do_section): Remove non-US code
        * dak/make_overrides.py (main): ditto
        * dak/process_new.py (determine_new): ditto
        * daklib/queue.py (Upload.in_override_p),
        (Upload.check_override): ditto
        * daklib/utils.py (extract_component_from_section):,
        (poolify): ditto
        * dak/import_archive.py (update_section): ditto
        * dak/symlink_dists.py (fix_component_section): ditto
        * scripts/debian/mkmaintainers: ditto
        * scripts/debian/update-mirrorlists (masterlist): ditto
        * config/debian-non-US/*: Remove subdir
        * scripts/debian/update-readmenonus: Removed.
In the recent past I did some more dak changes. Just to list them here, they are (Most patches applied by James. Can’t remember if someone else applied one. If so that would be Aj). And - at the end of all this - I will finally update my dak package again. Im not sure I get it uploaded this year, as I’m away tomorrow, but it will get an update fairly soon! Ha.

Matthew Palmer: Cowboys

I am very saddened by the state of the IT industry. It seems like nearly everyone who works in or around IT is, to put it bluntly, a cowboy. There appears to be very little desire for actually helping people; instead all I see is a very large number of people circling around looking for the next person they can make a quick buck off. In short, most of the IT industry is composed of people who are little better than shysters and conmen. As a case in point, I recently had contact with someone who is trying to get an online store running. They've been trying, unsuccessfully so far, for several months. They've been screwed over by basically every IT-related person they've had contact with so far. Now, after all of their suffering, they've finally gotten in contact with me. Most of their money is gone, and they're deeply behind schedule. So I'm left trying to pull a miracle job in little time and with little money. Yes, I could shoo them away, because they're asking for more than they can afford, but there's a little spark of helpfulness left in me, and I'll try to get them going as best they can with what they've got. If they'd found someone competent right at the beginning, they'd have been fine. They started with sufficient cash and time to produce a good end result. But chancing upon someone decent doesn't have good odds in IT; it's a bit like winning the lottery. This story isn't unique in my personal experience, by any stretch. There seems to be a near-endless procession of non-technical people who come out of their encounters with the IT industry battered and bruised, whether it be on the web, in their business infrastructure, or their personal computing needs. While it's easy to blame the customer for not managing themselves and their computing properly, I don't think it's fair to lay the blame on them -- to me, that's like blaming the patient for dying on the operating table, when the responsibility must lie, prima facie, with the surgeon. It's the surgeon, after all, who is the (presumably) trained and experienced professional in the relationship, and it is his responsibility, primarily, to ensure that everything goes smoothly[1]. Depressingly, I don't see much of a way around this problem. The few IT people who did care could try and group together, build some sort of a rating or "membership implies quality" system, educate the consumer, and try and drive the cowboys out, but guilds and trade associations are frowned upon these days, smacking (as they do) of restraint of trade and collusion. Government regulation never seems to produce anywhere near the desired result, while hoping that the consumer will either rise up and demand quality, or will gain sufficient knowledge to be able to pick a cowboy is a complete non-starter, for the same reason as teaching everyone basic surgical techniques isn't going to improve the quality of hospitals.
There's an ad that used to be on Australian TV for a certain bank, where a guy is at a party and he's asked by another of the partygoers what he does for a living. As he replies, "I work in banking", the entire party goes silent and stares at him in horror. It's only when he says, "It's OK, I'm with $BANK_BEING_ADVERTISED" that everyone looks happy again and continues on with their party. Although I've never had that particular experience, I'm almost getting to the point where I'm not happy telling people what I do for a living. This is because in any non-trivial collection of people, there's almost certainly going to be at least one person who has had such a poor experience with the IT industry that they're either going to take it out on me, ask me interminable questions about computers, or will just hate me on principle. It's unfortunate that brothels don't have pianos any more; if I were to say "I play piano in a whorehouse" I'm pretty sure the response would be "lawyer or sysadmin?". As Edsger Dijkstra said back in 2001, "The average customer of the computing industry has been served so poorly that he expects his system to crash all the time, and we witness a massive worldwide distribution of bug-ridden software for which we should be deeply ashamed." Are you?
1. That isn't to say that the patient (or client) has no responsibility in ensuring a positive outcome -- if you go bungee jumping the day after open heart surgery, or never send your web developer any content, you're very unlikely to have a positive outcome. However, it seems to me as though the only customer consultation done by most IT "professionals" on taking on a project is a Homeresque "I only have two questions. 'How much?' and 'give it to me'".

30 December 2007

Steve Kemp: I just don't understand

Whilst I'm very pleased with my new segmented network setup, and the new machine, I'm extremely annoyed that I cannot get a couple of (graphical) Xen guest desktop guests up and running. The initial idea was that I would setup a 64-bit installation of Etch and then communicate with it via VNC - xen-tools will do the necessary magic if you create your guest with "--role=gdm". Unfortunately it doesn't work. When vncserver attempts to start upon an AMD64 host it dies with a segfault - meaning that I cannot create a scratch desktop environment to play with. All of this works perfectly with a 32-bit guest, and that actually is pretty neat. It lets me create a fully virtualised, restorable, environment for working with flash/java/etc. The bug was filed over three years ago as #276948, but there doesn't appear to be a solution. Also, only on the amd64 guest, I'm seeing errors when I try to start X which mention things like "no such file or directory /dev/tty0". I've no idea whats going on there - though it could be a vt (virtual terminal) thing?. The upshot of all this is that I currenly have fewer guests than I was expecting:
skx@gold:~/blog/data$ xm list
Name                                      ID Mem(MiB) VCPUs State   Time(s)
Domain-0                                   0     3114     2 r-----   1180.6
cfmaster.services.xen                      1      256     1 -b----      1.0
etch32.desktop.xen                         2      256     1 -b----      1.4
etch32.security-build.xen                  3      128     1 -b----      1.4
etch64.security-build.xen                  4      128     1 -b----      1.4
sarge32.security-build.xen                 5      128     1 -b----      1.0

Erich Schubert: Waiting for a process

Some people will have come across this: They've started some long-running process, e.g. some computation for their thesis, and want to be notified when it's done. Depending on the setup, they can't just background it and run wait in the shell.Or you might want to run some expensive process somewhere, but there is some larger thing going on right now, so you want to wait for that to finish (you know, it's often better when people don't fight for memory and put all the load on the swap drive...).Or you need to monitor some process that might crash, and want to schedule a notification or restart.Here's how I'm doing that now:
busywaitpid command-of-process && notify-send "Computation is finished!"
Which will singnal a popup bubble when the process is finished.Here's the script:
#!/bin/sh
mypid=$$
pid= pgrep -of $@   grep -vE "^$mypid$" 
if [ -z "$pid" ]; then
  echo "No pid found." >&2
  exit 2
fi
echo "Waiting for pid $pid."
while test -d "/proc/$pid"; do
  sleep .1
done
# Make sure it's gone...
test -d "/proc/$pid"   exit 1
exit 1
Note that it will wait for the oldest (-o) process where the full command line (-f) matches the given parameter.Bugs: it doesn't handle when there are multiple processes matching the query - it will use the oldest (as given my pgrep).[Update: Specto, aptitude install specto, is a GNOME GUI application that you should be able to use for this purpose (amongst others such as website change monitoring)]

Erich Schubert: The 'iwlwifi' driver

I've switched back to the Debian stock kernel 2.6.23 from a self-compiled 2.6.23.9. The reason: I wanted to give the iwlwifi driver for my Intel 3945 wireless a try.I think the 'iwlwifi' driver will be included upstream in 2.6.24, I guess the Debian people have added it to the 2.6.23 package themselves. At least I didn't come across it when configuring my 2.6.23.9, and I've seen it in the 2.6.24rc changelogs.So far, the iwlwifi driver has been clearly superios, except it still lacks support for the LED. There seems to be a patch around for that though. So maybe my wireless is still disconnecting from time to time and I'm just not noticing it because I don't see the LED flashing. :-)

29 December 2007

Wouter Verhelst: NBD 1:2.9.9-3

I just uploaded the Debian packages versioned 1:2.9.9-2 (almost immediately followed by 1:2.9.9-3, because I forgot to test part of it, and obviously that part turns out to be broken), containing some updates: The two combined should allow for running a root filesystem on an NBD device. Note that the initramfs scripts haven't received any testing beyond my system yet; it's not impossible that they're broken in some regard. Treat them with some caution. Having said that, testing would be welcome... Next, I've also started work on partman-nbd. This is in an even more experimental and unfinished state, but the eventual goal is to support installing to an NBD device. Wouldn't that be nice.

Steve Kemp: You are the witness of change

As I wrote yesterday I've recently ordered, and now received a new desktop machine. For completeness I've now finished juggling machines around and installed etch twice - so now I have two working desktop machines:
gold.my.flat (unstable)
This is my personal machine, fitted with 4Gb of RAM. It is currently running 6 xen instances of 256Mb each leaving me with more meory free than I have ever had upon my desktop machine - so the upgrade was definitely worthwhile!. (The previous machine had bad sockets and couldn't take more than 1Gb of RAM - hence the replacement rather than mere upgrade.)
vain.my.flat (etch)
This, reinstalled, machine is now running only backuppc and those programs that Meg/random guests wish to run.
In terms of networking I've now split things up into three well-defined ranges. Knowing how things develop I'll not expect this to contining, but right now I'm pleased with: All in all I'm very happy with the work of the day even if I did have to rsync stuff all over the place, juggle power cables and install Etch upon both the new machine, and the re-purposed backup machine. (Since that was previously my mahcine and was running sid.) The following links were helpful. All being well tomorrow will be spent tidying the flat, drinking with my erstwhile cat-sitter, and getting ready for work on Monday.

Joerg Jaspert: SSH “triggers”

Following my post about SSH jumphost I have another SSH feature to share with you, which IMO isn’t known or used enough. Imagine you have some data on one host which gets regenerated every now and then and you also need this data on other hosts too. There are multiple ways to sync the data to other machines. You can The problem of the first option is that you need to make the data available via http/ftp, which needs an extra daemon to run. And then you need to cron a script fetching it, which wastes resources if the data is updated infrequently. The problem of the second option is that you need some daemon available which allows you to write to the host. Depending on what you chose that might be with passwords transferred unencrypted. Or you aren’t able to set it up yourself, as you are not the admin of the machine. So, lets take the third solution. Its safe to assume that SSH is available on the hosts you login to (don’t tell me you still use telnet/rlogin on remote machines), so lets use SSH features. I assume that usage of basic SSH public key authentication is known, if not you first want to google for it and learn about that. Using SSH keys to trigger actions on remote hosts is basically the same as a login to the machine and manually running a command - except you don’t need to do it yourself, a script is doing it. Which leads to one big difference for a “trigger” key compared to a “login” key: You do not set a passphrase for that SSH key! As a consequence of that you use such a key only for exactly one purpose, nothing else. Generate a new key for another trigger. Never, ever, use such a passphrase-less SSH key for normal logins to other machines… Having generated a passphrase-less key on host a (let it have IP 1.2.3.4) we copy the .pub file over to the target host b and put it into the authorized_keys file (usually in ~/.ssh/). The difference to normal login keys is the large line of options we put in front of it:
command="rsync --server -vlHogDtprz --delete --delete-after --ignore-errors . /org/backup/something",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,from="1.2.3.4" ssh-key-here
or
command="/var/mirror/ftpsync &",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty,from="1.2.3.4" ssh-key-here
Both commands allow to use the SSH key from host a with its IP 1.2.3.4 and will run the command thats defined here. No matter what command or options are are specified on the commandline on host a, host b will only do the above. There wont be any port, X11 or agent forwarding and due to the forced command there also wont ever open a shell. With the first command we trigger the remote hosts rsync to write the data we send into that path, using the given options. Of course that means we send data using rsync from our host. The SSH connection stays available for the whole time the command runs. The second command instead runs the given binary, a shell script in this case, in background. As we also forbid tty allocation the SSH connection is closed right after the script is started. To avoid DOSing the remote machine such a script should have some kind of lockfile check and abort if a second copy is already running. SSH also allows to use such limited SSH keys for the root user, while disallowing normal root logins: Change PermitRootLogin in sshd_config from no to forced-commands-only and you wont be able to login to the remote host as root but you can trigger actions that should be run as root. If you want to know what else you can do using options specified in the authorized_keys file then read its man-page, it has some details how you can use it to limit port forward requests, use more than just one IP in the from= parameter, … Some users of the above way of automating tasks on remote machines are

Jeff Licquia: Christmas Gadgets: Creative Zen, LCD Monitor

So it’s a few days after Christmas, and like most of us tech-heads, I’ve got a few more gadgets to play with. First up: the Creative Zen 4GB. This one was a little bit of a saga. Last year, we got the kids no-name MP3 players, on the theory that we didn’t want to spend megabucks on something they wouldn’t use. They made valiant attempts to use them, but the little machines just weren’t up to the job. So, it seemed prudent to buy them iPods this year. Well, except for Apple’s attempts to break all non-iTunes iPod software, which had the side effect of making the devices unusable under Linux. Still, this was what they wanted, and they had been good this year, and very patient with my ever-more-convoluted schemes to get the old players working. So, iPod Nano 3Gs for both of them. My heart sank as I watched some of my hard-earned money go to reward such behavior. As part of the deal, I vowed to find a non-Apple player that would be good for when the iPods gave up the ghost or became “uncool”. And my dear wife, upon hearing this, went online, did some research, and bought me the aforementioned Creative Zen 4GB. From a Linux perspective, it’s in the “not quite ready for prime time” mode. Rhythmbox and Banshee are working on support; I tried a prerelease of Rhythmbox, and found its support to be very unstable. The only usable app is Gnomad2, which has a terrible UI and also occasionally crashes, but can manage to upload audio, video, and photos without too much hassle. Still, this is a problem of fine-tuning, and not of a hostile hardware vendor; I’m confident that these devices will be well-supported in the near future. The Zen is picky about what video files it will play, but I managed to figure it out: DivX or XviD video, 320×200 or smaller image size, encoded at a 480 kbit/sec video bitrate or less. Other video files might work, too, but you’ll have to find them on your own. My Zen has a little problem with the button locking feature: after unlocking, the screen comes up to all-white, and you have to power-cycle it to get the display back. I’m assuming this is a firmware bug, as the screen is still visible for a short time after engaging the lock. Other than this, the Zen is a delight, and every bit as functional as the iPod. The other nice gadget: a 24-inch LCD from Envision, bought after Christmas with a combination of gift cards, exchanges, and some of my own money. It was an open-box, and I saved about $80 for that; the only problem turns out to be a single dead pixel in the corner of the screen which is barely visible. It does 1920×1200 in very nice, bright color. Here, too, an improvement on my life only came after some effort. Debian 4.0’s drivers for the Intel graphics chipset are not capable of driving a widescreen LCD; the best I could get was 1600×1200, a normal-width resolution stretched across the wide display. I booted an Ubuntu Gutsy live CD to verify that the problem wasn’t with the monitor, and then set to the task of backporting everything I needed from lenny. Happily, before I started, I found that someone (Holger Levsen, to be exact) had done the work for me. Things are now about 90% there. The new drivers still don’t have everything figured out for running both Compiz desktop effects and XVideo acceleration at the same time, so I’ve had to turn XVideo off. My computer can render video without hardware support, but the quality isn’t as high. But, I have my nice wide screen, with crisp fonts and lots of room. I figure I’ll live with what I have until lenny releases, and then see what progress has been made.

Next.

Previous.