I decided that my christmas gift will be a new notebook and as I'm always complaining of the weight of my HP dv6000 then my new notebook will be a ThinkPad x61 with a 8cell battery and extended battery life! :-) That gives up to 12 hours of use!! BTW, this version includes a weird antenna in the right side of the screen, I don't know if it's really useful but seems like if were from some movie and is outside of the borders but anyway, still little and light.
Now only rests to wait until it gets to my hand since all the custom houses of Venezuela decided to not admit more packages from outside of the country because they're full, so I will have to wait until january probably because of the inefficiency of my country custom officials.
But at least I'm gonna have it :-)!

Now is the time to join and give to Free Software Foundation. 2008 is going to be extraordinarily important year for free software. Eben Moglen likes to quote Gandhi's "first they ignore you, then they laugh at you, then they fight you, then you win" progression when describing the free software movement. As I pointed out when I joined the FSF board, we're beginning to see powerful interests fighting free software. It's going to increase in the next few years. Things will probably get a lot uglier for free software before they get better. We can win but things are far from settled. The FSF is the front-line organization in this fight and we need a robust and proactive foundation, and an active and involved membership, if we're going to win. Here are the issues that I'm going to pushing the FSF to pursue in the next year. Expanding activism outside our traditional technologist communities: In part through the work of projects like Defective By Design, we've seen the tide turn for DRM on music in what what may be the FSF's greatest success last year. I'm going to push the FSF to continue the campaign to attack DRM for video, eBooks, and the other places it is cropping up. The most remarkable thing to me about Defective By Design is that its participants and supporters are not, for the most part, people who develop or use GNU/Linux or even know what GNU is! If advocacy for software freedom involves a conversation we can only have with people who understand what POSIX is and how one uses it, we've already lost. Through DbD, BadVista, and other projects, the FSF has made major strides in the last year. It need to do much more and needs your support to do so. Get proactive about software patents: As a community, we've had our head in the sand about software patents for far too long. There are companies and patent trolls sitting on massive, growing piles of software patents. They are not our friends and they do not mean us well. One cannot write non-trivial software today without running a serious risk of infringing patents. The software patents minefield we've found ourselves in is a very fundamental threat to the success of free software and we've already begun to see the first casualties and costs. We must eliminate software patents. Now. The US is very important in this fight (much patent law is "exported" from the US) and almost no organization is working on software patent elimination there. Not enough people are thinking and acting strategically on this issue. The FSF is planning to make major steps in this fight in the coming year and we need your support to do so. Web services and the changing face of software: This last year, I worked to help launch the new version the AGPLv3. The license addresses the role of copyleft for software like web-services which, due to the legal particulars of the GPL, did not extend to the purveyors of web services. Of course, access to source code does not make the users of all web-services free (e.g., the GMails and the Facebooks). Nobody seems to know what freedom for webserver entails. There might not even be good answers. In the next year, I'm going to push the FSF to help start several conversation and to begin to follow up on what I think was an important first step with the AGPLv3. While this is not a major organizational priority yet, it's a major action item that I will be pursuing through the FSF. If you feel strongly about this issue, whatever your position, become a member, stay involved as these projects develop, and have your voice be heard. We don't know the answers yet and we need your input as much as we need your action.Please, support the FSF in the efforts listed above, and in others, by giving generously. If you're not a member, please join the FSF as an associate member. If you are already a member, please consider making a tax-deductible donation. The FSF is a very lean, very humble organization of passionate and dedicated individuals working tirelessly for software freedom. Every little bit helps. Members pays USD $120 ($10/month) and student members pay half that. FSF has members across the world -- where a weak dollar often makes it even cheaper. Member support and participation builds capacity and credibility for the foundation and keep the organization responsible, responsive, and in tune with our community.
ssh some.host ssh next.hostwhere some.host is your jumphost. Add as many some.host as you want into this chain. We are all lazy and don’t want to type that by hand, one ssh is enough for everybody. Hurray, ssh already provides what we need, namely the ProxyCommand directive, it’s just not known as much as it should be. For this example imagine I have to ssh via the following host chain to get out: kosh -> vir -> babylon5 -> sheridan and also want to have my local port 2525 forwarded to sheridans port 25. The following config snippet (.ssh/config) is doing that[2]
Host yay ProxyCommand ssh -q -A -X vir ssh -q -A -X babylon5 'nc -w1 sheridan 22' LocalForward 2525 localhost:25 Host vir ProxyCommand ssh -q -A -X kosh 'nc -w1 %h %p'The effect of this is:
I first heard about the Open
Source Jam Zurich somewhere at BlogCampSwitzerland
2.0 (which was more a TechCrunch7 than a BlogCamp — why
did the organisators call it BlogCamp?) and subscribed to its Google Group.
At Linuxday.at, hansmi (who seems to
As part of my research, I may have to
conduct a survey among Debian contributors. The word "survey" usually elicits
frowns because surveys are often misconducted. MJ has taken the time to draft
up some advice to surveyors.
Problems with surveys generally fall into one of two categories: content and
presentation. I'll refrain from making statements about content (Wikipedia has
some stuff on questionaire construction) and instead
concentrate on presentation in the following.
Commonly in the digital age, surveys are administered via a web page or
e-mail. In my recent Ph.D. transfer report,
I identified a number of shortcomings with these approaches:
Asking Debian contributors to click radio buttons on a web page is a bit like
expecting a mountain biking champion to ride a tricycle across a paddock:
painful, if not offensive. Furthermore, web surveys can only be taken while
on-line, when most of us have better things to do.
E-mail surveys address some of these problems, but create new ones: answers
cannot be constrained to a domain (think multiple-choice), character set and
formatting issues make evaluation difficult, and it's impossible to prevent
users from attaching comments or modifying responses.
In thinking about the issue, I came up with a third means to administer
a survey: a console tool. Think of a Debian package which provides a console
application controlled by a study-specific data file. The data file specifies
the questions and their answer domains, and the tool presents those to the
participant. Since most of Debian happens on the console anyway, such an
approach to surveys seems more appropriate.
Interaction with the survey tool would be as easy as pressing the 2 or
4 keys to select one of the multiple choices, and the tool would
immediately move on to the next question (and not wait for the user to hit
enter). Obviously, n and p should allow navigation back and forth
across the set, and c would spawn a text editor to give the user a chance
to attach a comment to his/her current response, in which s/he might criticise
the question or provide additional information. Finally, the tool should be
able to pick up where it left off, should the user chose to exit/suspend the
survey for now. Integration with debconf or another interface abstraction
is also worth consideration.
There is more to it: people change their minds and should thus be able to
amend responses. With their consent, it might be valuable to track such
changes and inquire about their motivations. As I was thinking about how to
realise this, I suddenly arrived at version control: use Git as a backend storage. The set of cool features this
would enable seems to be endless: it works off-line and can be used to track
aforementioned changes, but also offers the possibility to create a squashed
result in case the participant prefers to submit only the final result.
Furthermore, it's a trivial change between anonymous submissions, and
submissions authenticated by a GPG signature.
In addition, the survey tool should be able to display questions according to
previous responses (control flow). For instance, if the survey determines that
a given user is a contributor to the bug tracking system, but not a project
member, it wouldn't make sense to ask when s/he received his/her Debian
account. Furthermore, questions could be dynamically creatable from context,
so that the survey can drill into depth depending on previous responses,
rather than asking the same questions to all participants.
I am currently applying for funding to outsource the development of such
a tool. If you are interested in coding it up and getting paid for it, speak
to me. Here are some more specifications to keep in mind before jumping on:
It's now three weeks since I am officially a Ph.D. student at the University
of Limerick, but I've been too busy to do anything about it.
Today, I finally updated my research webpage and sat down to tell you the tale of how
I successfully defended my research, but failed to leave the country the next
day.
As is customary in the British system, I initially enrolled at UL as a Master
student. In October, I then applied for a transfer to the Ph.D. track,
submitted a transfer report
and prepared for a live defence, according to the UL code of practice.
On 23 November, I presented my research
to my examiners, Dr. P r gerfalk and Patrick Healy, who found my work to be at Ph.D. level
and approved of my transfer.
I was moderately nervous going into the presentation, not really knowing what
was expected of me. In the end, however, the presentation went well and the
ensuing discussion provided valuable feedback. Thank you, P r and Paddy, as
well as Norah (who chaired), and
Brian (my supervisor) for all your time,
help, and support.
After the defence, Mel waited outside with
a beer in hand, and it being Friday and all, I happily popped the cap and
drank. Plans to head to The Stables gave way
to chilling on the couch in 110 (my home away from home), before we headed to
town for the Kila gig.
We arrived early, had some beers, enjoyed the show, had some more beers, went
home, and had some more beers to Guitar Hero,
and when I crawled into bed, I was shocked to find out that I had lost all
track of time and it was in fact already 5:30 on Saturday morning, instead of
the perceived 2 o'clock.
See, the source of this shock was a plane that left Dublin the next day around
noon, and a rental car that was to get me there, leaving the house at 8. But
when my alarm shattered my drunk dreams at 7:30, it quickly became clear (or
well, everything was blurred, actually), that I would have a hard time getting
into the car, and I would certainly never manage to navigate it to Dublin,
a three hour drive. So I called up the airline and the rental company and
rescheduled for the next day (only one flight from Dublin to Zurich a day),
and went back to dreamland.
I am entirely unsure whether my Ph.D. transfer defence was enough of a reason
to get smashed. I still had a good time, though as always in Ireland,
especially with this crowd
NP: The Flower Kings: The Rainmaker
Yesterday, Lars and I were, for some
reason which I can't remember now, chatting about taking pictures over
at #debian-devel. As we were doing so, it came up that there are quite a
number of Debian Developers and/or users who have (a) digital camera(s)
these days, and that it might be a good idea to have a list for amateur
and/or professional photographers who want to use Debian with their
digital camera. After all, there's quite a bit of software to help with
that, but sometimes it can be a bit challenging to set it up
correctly.
So Lars sent in a bugreport on the
lists.debian.org pseudo-package, asking for the creation of a new
mailinglist to discuss anything closely or remotely related to using
Debian with a digital (or other?) camera. List creation procedure now
calls for people who think it's a good idea (or not...) to speak up and
let their voice known. So, if you have a digital camera or are thinking
of getting one, and want to share ideas about them, please follow up to
the bugreport!
We were hit pretty hard in Boston. My office was shut down and deserted by mid-afternoon, but I decided to stay until late afternoon — big mistake. You might think the trains wouldn’t be as affected by the snow. And they weren’t — it only took me twice as long to get home, while it took my brother over six hours to drive from Somerville to Roslindale.
Still, it was a pretty extraordinary scene at South Station around 4:30pm. It was packed inside and out. A few trains arrived, and no one got on or off. I was wondering if they were ghost trains until finally things started moving.
The odd color balance in this photo set is because these were all taken in the dark with very long exposure times. But the apocalyptic cast may actually be appropriate.
Earlier: Proof of Fall 2007, Blizzard 2007, Blizzard 2005, First Snow 2004, Winter Sunset 2005.
Technorati Tags: Boston, Roslindale, Snow, Blizzard
DeBaBaReTools seems to work good enough that writing an early-stage HOW TO seems to worth the time :)$ svn export https://neo.yahostme.com/svn/DeBaBaReTools/trunk/ DeBaBaReTools
$ cd DeBaBaReTools; dpkg-buildpackage -b; dpkg -i ../debabaretools_0.2_all.deb
$ dpkg -L debabaretools
/.
/etc
/etc/DeBaBaReTools
/etc/DeBaBaReTools/common.conf
/usr
/usr/bin
/usr/bin/wannaBuild
/usr/bin/needsBuild
/usr/bin/needsReBuild
/usr/bin/buildQueue
/usr/bin/checkSums
/usr/bin/wannaUpload
/usr/bin/processIncoming
/usr/share
/usr/share/doc
/usr/share/doc/debabaretools
/usr/share/doc/debabaretools/copyright
/usr/share/doc/debabaretools/ENV
/usr/share/doc/debabaretools/changelog.gz
/usr/share/doc/debabaretools/TODO
/usr/share/DeBaBaReTools
/usr/share/DeBaBaReTools/backends
/usr/share/DeBaBaReTools/backends/config
/usr/share/DeBaBaReTools/backends/config/reprepro.sh
/usr/share/DeBaBaReTools/backends/probe.sh
/usr/share/DeBaBaReTools/backends/fetch
/usr/share/DeBaBaReTools/backends/fetch/dget.sh
/usr/share/DeBaBaReTools/backends/verbosity.sh
/usr/share/DeBaBaReTools/backends/lock
/usr/share/DeBaBaReTools/backends/lock/default.sh
/usr/share/DeBaBaReTools/backends/setDefault.sh
/usr/share/DeBaBaReTools/backends/buildQueue
/usr/share/DeBaBaReTools/backends/buildQueue/plaintext.sh
/usr/share/DeBaBaReTools/backends/signature
/usr/share/DeBaBaReTools/backends/signature/gpgv.sh
/usr/share/DeBaBaReTools/backends/check
/usr/share/DeBaBaReTools/backends/check/default.sh
/usr/share/DeBaBaReTools/backends/build
/usr/share/DeBaBaReTools/backends/build/pbuilder.sh
/usr/share/DeBaBaReTools/backends/upload
/usr/share/DeBaBaReTools/backends/upload/dput.sh
/usr/share/DeBaBaReTools/backends/parsers
/usr/share/DeBaBaReTools/backends/parsers/default.sh
/usr/share/DeBaBaReTools/backends/repository
/usr/share/DeBaBaReTools/backends/repository/shared.sh
/usr/share/DeBaBaReTools/backends/repository/reprepro.sh
/usr/share/DeBaBaReTools/backends/misc.sh
/usr/share/DeBaBaReTools/backends/codenamesTable
/usr/share/DeBaBaReTools/backends/codenamesTable/release.sh
/usr/share/DeBaBaReTools/backends/codenamesTable/reprepro.sh
/usr/share/DeBaBaReTools/backends/config/default.sh
/usr/share/DeBaBaReTools/backends/fetch/default.sh
/usr/share/DeBaBaReTools/backends/buildQueue/default.sh
/usr/share/DeBaBaReTools/backends/signature/default.sh
/usr/share/DeBaBaReTools/backends/build/default.sh
/usr/share/DeBaBaReTools/backends/upload/default.sh
/usr/share/DeBaBaReTools/backends/repository/default.sh
/usr/share/DeBaBaReTools/backends/codenamesTable/default.sh
.:
./build:
./build/cache:
./build/data:
./build/data/logs:
./build/tmp:
./conf:
distributions
incoming
options
tiffany.py
uploaders
./db:
./debian:
./debian/dists:
etch
oldstable
sarge
sid
stable
testing
unstable
./debian/dists/...
./debian/pool/...
./incoming:
./incoming/accepted:
./incoming/new:
./incoming/rejected:
./pub:
./pub/UploadQueue:
$ cat conf/distributions
Codename: sid
Suite: unstable
Architectures: i386 amd64 source
Components: main contrib non-free
Uploaders: uploaders
DebIndices: Packages Release .bz2 .gz .
DscIndices: Sources Release . .gz .bz2
Contents: .bz2 .gz .
Tracking: minimal includechanges keepsources
$ echo 'HINT_ALL="reprepro pbuilder"' > $HOME/.DeBaBaReToolsrc
[local]
fqdn = localhost
method = local
incoming = /home/raphael/Deb/repository/pub/UploadQueue
allow_unsigned_uploads = 0
run_dinstall = 0
VERBOSE=1 processIncoming
processIncoming v0.1 started.
processIncoming v0.1 stopped.
$ dput local kcometen3_1.1-1_source.changes
Checking Signature on .changes
...
Uploading to local (via local to localhost):
Successfully uploaded packages.
Not running dinstall.
sh: /usr/bin/mini-dinstall: No such file or directory
Error while executing command.
Continuing...
$ VERBOSE=1 processIncoming
processIncoming v0.1 started.
Processing /home/raphael/Deb/repository/pub/UploadQueue/kcometen3_1.1-1_source.changes...
mv'ing "/home/raphael/Deb/repository/pub/UploadQueue/kcometen3_1.1-1.diff.gz" to "/home/raphael/Deb/repository/incoming/accepted/"
mv'ing "/home/raphael/Deb/repository/pub/UploadQueue/kcometen3_1.1-1.dsc" to "/home/raphael/Deb/repository/incoming/accepted/"
mv'ing "/home/raphael/Deb/repository/pub/UploadQueue/kcometen3_1.1-1_source.changes" to "/home/raphael/Deb/repository/incoming/accepted/"
mv'ing "/home/raphael/Deb/repository/pub/UploadQueue/kcometen3_1.1.orig.tar.gz" to "/home/raphael/Deb/repository/incoming/accepted/"
processIncoming v0.1 stopped.
$ VERBOSE=1 needsBuild
needsBuild v0.2 started.
Architectures: i386 amd64 all
Now processing /home/raphael/Deb/repository/incoming/accepted/kcometen3_1.1-1_source.changes
Adding kcometen3 to be built in i386 for the sid distribution
Adding kcometen3 to be built in amd64 for the sid distribution
mv'ing "/home/raphael/Deb/repository/incoming/accepted/kcometen3_1.1-1.dsc" to "/home/raphael/Deb/repository/incoming"
mv'ing "/home/raphael/Deb/repository/incoming/accepted/kcometen3_1.1.orig.tar.gz" to "/home/raphael/Deb/repository/incoming"
mv'ing "/home/raphael/Deb/repository/incoming/accepted/kcometen3_1.1-1.diff.gz" to "/home/raphael/Deb/repository/incoming"
mv'ing "/home/raphael/Deb/repository/incoming/accepted/kcometen3_1.1-1_source.changes" to "/home/raphael/Deb/repository/incoming"
needsBuild v0.2 stopped.
$ VERBOSE=1 processIncoming
processIncoming v0.1 started.
processIncoming v0.1 stopped.
$ INSTALL=1 VERBOSE=1 processIncoming
processIncoming v0.1 started.
No distribution found for 'kcometen3_1.1-1_source.changes'!
There have been errors!
No distribution found for 'kcometen3_1.1-1_source.changes'!
There have been errors!
No distribution found for 'kcometen3_1.1-1_source.changes'!
There have been errors!
making diffs between /home/raphael/Deb/repository/debian/dists/sid/main/source/Sources and /home/raphael/Deb/repository/debian/dists/sid/main/source/Sources.new:
generating diff
Exporting indices...
processIncoming v0.1 stopped.
$ VERBOSE=1 wannaBuild
wannaBuild v0.1 started.
Fetching list of packages to be built for unstable
Fetching source package kcometen3 v1.1-1
Use of uninitialized value in string eq at /usr/bin/dget line 377.
cat: /home/raphael/Deb/repository/build/data/needsBuild.unstable: No such file or directory
Starting build backend...
Executing sudo pbuilder --update --basetgz /var/cache/pbuilder/unstable.tgz
Starting build process
Verifying signature of /home/raphael/Deb/repository/build/kcometen3jb3362/kcometen3_1.1-1_i386.changes...
gpgv: no valid OpenPGP data found.
gpgv: the signature could not be verified.
Please remember that the signature file (.sig or .asc)
should be the first file given on the command line.
Fetching list of packages to be built for testing
Fetching list of packages to be built for stable
Fetching list of packages to be built for oldstable
wannaBuild v0.1 stopped.
$ VERBOSE=1 processIncoming
processIncoming v0.1 started.
Processing /home/raphael/Deb/repository/pub/UploadQueue/kcometen3_1.1-1_i386.changes...
mv'ing "/home/raphael/Deb/repository/pub/UploadQueue/kcometen3_1.1-1_i386.changes" to "/home/raphael/Deb/repository/incoming/accepted/"
mv'ing "/home/raphael/Deb/repository/pub/UploadQueue/kcometen3_1.1-1_i386.deb" to "/home/raphael/Deb/repository/incoming/accepted/"
processIncoming v0.1 stopped.
$ VERBOSE=1 needsBuild
needsBuild v0.2 started.
Architectures: i386 amd64 all
Now processing /home/raphael/Deb/repository/incoming/accepted/kcometen3_1.1-1_i386.changes
mv'ing "/home/raphael/Deb/repository/incoming/accepted/kcometen3_1.1-1_i386.deb" to "/home/raphael/Deb/repository/incoming"
mv'ing "/home/raphael/Deb/repository/incoming/accepted/kcometen3_1.1-1_i386.changes" to "/home/raphael/Deb/repository/incoming"
needsBuild v0.2 stopped.
$ INSTALL=1 VERBOSE=1 processIncoming
processIncoming v0.1 started.
No distribution found for 'kcometen3_1.1-1_i386.changes'!
There have been errors!
No distribution found for 'kcometen3_1.1-1_i386.changes'!
There have been errors!
No distribution found for 'kcometen3_1.1-1_i386.changes'!
There have been errors!
making diffs between /home/raphael/Deb/repository/debian/dists/sid/main/binary-i386/Packages and /home/raphael/Deb/repository/debian/dists/sid/main/binary-i386/Packages.new:
generating diff
Exporting indices...
processIncoming v0.1 stopped.
Debian-KDE && Debian-i18n meeting in extremadura. I’m attending. Yay.
Flight: on time for once, but apparantly Iberia has added one extra row of seats, so very little space.
After a lot of hacking I've now got chronicle displaying comments upon entries.
Since my blog is compiled on my home desktop machine and comment submission happens upon a remote machine the process involves a bit of a hack:
~/blog/ -- comments/ -- data/ -- output/ -- Makefile -- chroniclercHere I have a Makefile to automate the import of the comments from the live site to the local comments/ directory, rebuild, and finally upload. All this means that I can rebuild a blog created by a combination of plain text post files and plain text comment files. It also means that there is a fair lag between comment submission and publication - though I guess there is nothing stopping me from auto-rebuilding and syncing every hour or two via cron... I'll make a new release with this comment.cgi script and changes once the package hits Debian unstable...
My current mailfilter has two
features which increase my day-to-day productivity:
Since the queue is only processed on the server, I cannot register a mail with the tickler without going online and synchronising my mail before the timestamp expires. So if I am on my way to a conference on Monday and tell the tickler to resubmit a given message on the next day, but I don't connect before Wednesday, I won't get the mail on Tuesday (because the mail does not actually reach the tickler until Wednesday, when it's immediately resubmitted). I have not found an algorithm that would let me run a queue processor on the server and my laptop without the two causing mail duplication and potentially interfering with each other.
I keep all my mail in a single Maildir to make searches easy. Since mail registered with the tickler is stored in a separate Maildir, I often need to search two Maildirs if I am looking for a specific message. This is awkward.
The queue processor has to iterate the entire queue, which is fine for a hundred messages, but it does not scale.
I have not found a way to ask mutt to tickle me about a message I send without going to the sent messages folder and scheduling the message for tickling manually. One approach would be record=no and a custom sendmail script, which would store mail to the store or tickler Maildirs, depending on whether the X-Tickle header is present, but I want to avoid a custom sendmail script for reasons unknown. Another approach might be to set bcc to the appropriate tickle address, but this would result in duplicate mails, unless I set record=no individually.
When cloning a Linux/Debian system 1:1 you should have a checklist of what’s important to change on the cloned system.
For cloning I use the grml Linux Live-CD of course (the following tips are part of grml-tips as well). To create a 1:1 clone I boot grml on the systems (usually using the ssh=password bootoption to be able to access the system remotely as well) and use something like:
Listener: # nc -vlp 30000 > /dev/sda1 Source: # dd if=/dev/sda1 bs=$VALUE nc -vq 0 $IP_OF_LISTENER 30000When I have to leave the place where the clone process is running and if the CD-ROM doesn’t reinsert CDs on reboot automatically (usually that’s the case for server systems) I can use my remote-reboot procedure via ssh later on like:
eject &>/dev/null umount -l /cdrom eject /dev/cdrom echo b > /proc/sysrq-triggerBut stop: before executing the last steps to reboot the server you should take care of a few important steps, otherwise rebooting might fail and you won’t be able to login via SSH.
Next.