Jesse’s Holodeck

I have set up a mercurial publish server for a group recently. All members in this group use Windows.
The server is accessed via ssh, and the ssh server listen on a port other than 22. With google’s help, I found a lot of documents about how to setup mercurial with putty (plink). But things go wrong when you’re not using port 22…
Openssh uses “-p” to specify server port to connect to, but plink uses “-P” instead. Mercurial fails with

remote: plink: unknown option “-p”

when it invokes ssh.
With a small modification, mercurial should work fine with plink. Or you can specify the server port in mercurial.ini instead of in URL.

If you’re using an Intel video card and Debian Lenny/Sid currently, you may like to take a look at the section on Debian Wiki.
Although I have no external monitor to test, “virtual 2048 2048” seems to work on my laptop (i830m) with its LCD only. But when I try to start beryl 0.2.1, there’s no luck. All desktops become blank…

When I try to upgrade my sid tonight, aptitude stops at linux-sound-base upgrading. With top, I found that update-modules.modutils eats all my CPU power. Same symptom appears when I try to downgrade it.
In the beginning, I though it’s due to the fail of upgrading module-init-tools to 3.3-pre11-3. But I have downgraded it to 3.3-pre11-1, so it should not be the case. Anyway, I upgrade module-init-tools to 3.3-pre11-3 again, but the update-modules.modutils problem doesn’t go away.
So I took a peek at the /sbin/update-modules and /sbin/update-modules.modutils, they have the same content.

1 #!/bin/sh -e
2 if [ -x /sbin/update-modules.modutils ]; then
3 exec /sbin/update-modules.modutils “$*”
4 fi
5 exit 0

If a maintainer script invokes update-modules or update-modules.modutils, it becomes an infinite loop…
I also found this bug report on BTS…

With the first solution that Graham <graham.knap_[at]_gmail.com> provided, finally I get the linux-sound-base installed again.

# chmod a-x /sbin/update-modules.modutils