Looks like this tool is going away, it’s not in squeeze or sid anymore, but hey, I needed a newer JDK…

make-jpkg cannot create packages for Java 6 update 10 or newer, to fix this, edit /usr/share/java-package/sun-j2sdk.sh.

Add this stanza:

       "jdk-6u"[0-9][0-9]"-linux-x64.bin") # SUPPORTED
            j2se_version=1.6.0+update${archive_name:6:2}${revision}
            j2se_expected_min_size=130
            found=true
            ;;

right after

        "jdk-6u"[0-9]"-linux-x64.bin") # SUPPORTED
            j2se_version=1.6.0+update${archive_name:6:1}${revision}
            j2se_expected_min_size=130
            found=true
            ;;

Then try again, should be golden.

Something seems to have changed in the debmirror prorgam on lenny:

gpgv: Signature made Sun Mar  1 16:27:33 2009 CET using DSA key ID 1F41B907
[GNUPG:] ERRSIG 07DC563D1F41B907 17 2 00 1235921253 9
[GNUPG:] NO_PUBKEY 07DC563D1F41B907
gpgv: Can’t check signature: public key not found

This error turned up when I tried to mirror debian-multimedia.org after upgrading debmirror. Apparently the new version looks for the keys in ~/.gnupg/trustedkeys.gpg. If you installed the debian-multimedia-keyring package, you can use the following:

 gpg –no-default-keyring -a –keyring /usr/share/keyrings/debian-multimedia-keyring.gpg –export 07DC563D1F41B907 | gpg –no-default-keyring –keyring ~/.gnupg/trustedkeys.gpg –import –

This imports the current key into the new file.

If you get the following error in your linux-vserver guest after upgrading it to lenny:

Feb 21 14:03:22 ftp sshd[18392]: error writing /proc/self/oom_adj: Permission denied

Adjust /etc/default/ssh ‘s SSHD_OOM_ADJUST=-17 into SSHD_OOM_ADJUST= then restart ssh to get rid of it.

For people running into this and not knowing how to easily fix:

Feb 20 09:15:19 tequila sshd[18110]: pam_env(sshd:setcred): Unable to open env file: /etc/default/locale: No such file or directory

tequila:~# ls /etc/default/locale
ls: cannot access /etc/default/locale: No such file or directory
tequila:~# update-locale
tequila:~# ls /etc/default/locale
/etc/default/locale

Or just fill it yourself:

tequila:~# cat /etc/default/locale
#  File generated by update-locale
LANG=en_US
 

I can’t help but think there is something terribly wrong with Debian’s security process. New securityfix WordPress package came out 4 weeks aftter the actual software release. 🙁

[08|23:38:05] [-] [:] Jeeves_ [mark@213.154.229.12] has quit [Quit: "Etch is uit, als ik over 10 minuten niet terug ben is het stuk"]

That was 8-Apr-2007, 23:38. To date, Jeeves still has not returned. Oops. 😉

Debian Etch has been released!

If you’re running Debian Sarge, have a >2TB ext3 volume and your fsck.ext3 exits with signal 11 leaving the damn thing all dirty and stuff, get 1.39+1.40-WIP from backports.org . This fixed the problem for me on my home box (2.4T) and one of the servers here at work (4.7T). Takes a long while to fsck, but at least it gets through instead of crashing somewhere half way!

I just set up FreeNX on my Sarge machine and it works really nice! I was hoping it would be able to "receive" remote desktop (rdc) connections and channel it to an X server (to use standard Windows CE/TS thin clients with a Linux server). I found the .deb’s too late, and as such followed another howto for Ubuntu .

Here’s how I did it on Sarge:

apt-get install cdbs autotools-dev patchutils autoconf bzip2 zlib1g-dev libpng12-dev libjpeg-dev xlibs-dev libfreetype6-dev libmikmod2-dev libssl-dev libxaw7-dev automake1.9 automake1.4 expect tcl8.4 netcat ssh build-essential dpatch

Add the following to /etc/apt/sources.list: deb-src http://debian.tu-bs.de/project/kanotix/unstable/ sid nx

apt-get source nx freenx
cd nx-1.4.92+1.5.0

sed -i s/debhelper\ \(\>=\ 5.0.0\)/debhelper\ \(\>=\ 4.2.0\)/ debian/control
export DH_COMPAT=4
dpkg-buildpackage

cd ../freenx-0.4.4+0.4.5

sed -i s/debhelper\ \(\>=\ 5.0.0\)/debhelper\ \(\>=\ 4.2.0\)/ debian/control
sed -i s/openssh-server,\ openssh-client/ssh/ debian/control
dpkg-buildpackage

cd ..; dpkg -i *deb 

Edit /etc/nxserver/node.conf and add the following line:

COMMAND_XAUTH=/usr/bin/X11/xauth

If you want to use SSH authentication instead of FreeNX’s own passdb backend put the following lines in there as well:

ENABLE_PASSDB_AUTHENTICATION="0"
ENABLE_SSH_AUTHENTICATION="1" 

Fetch the 1.5 client for Windows (2.0 from Nomachine doesn’t work). Enter the correct details (enable "encrypt all data" if you want it to work through firewalls and NATs — that way you just have to open up SSH and be done with it). Enjoy!