or how to cheat and support a Nokia 352×416 using “normal” S60 (176×208).
Either in the manifest file or the jad file enter these two lines. (thus making it possible to use a Nokia S60 file on a Nokia N80 (et al)
Nokia-MIDlet-Original-Display-Size: 176,208
Nokia-MIDlet-Target-Display-Size: 352,416
This parameter works on all S60 3rd ed (or later).
Had a slight issue with samba.
It didn’t see an upper case name as different from a lower case, i.e. it didn’t let me rename file to File (directly, I could rename it to ile first and then to File). Adding the following line in smb.conf (and restarting Samba) allowed me to do this.
case sensitive = yes
(The manual says, controls whether file names are case sensitive. If they aren’t then Samba must do a file name search and match on passed names. Default no)
Installing Pine on Debian might seem a bit tricky, but it isn’t as hard as it might look.
Due to the licensing rules of Pine (and Pico) these are not included as deb packages in the mirrors.
However the source of these two are.
Step 1 is to ensure that you have a deb-src in /etc/apt/sources.list (for instance)
deb-src http://http.us.debian.org/debian stable main contrib non-free
deb-src http://non-us.debian.org/debian-non-US stable/non-US main contrib non-free
To make Debian install from sources:
If you have never installed from source before we need to install a compiler and dpkg-dev
$apt-get install dpkg-dev
$ apt-get install gcc
Done, now we can start compiling Pine
A short note now: When building from source apt will download the source (and compile) to the directory where you start from. I think it is nice to make sure you are in a new directory that is clean from other files (and at a logical location if you intend to save the compiled package (like for instance /src/pine)
$ apt-get -b build-dep pine
$apt-get –only-source -b source pine
(now it will download and compile Pine. Be patient.
$ dpkg -i pine_4.64-3_i386.deb
Another option is downloading a deb package directly from Washington University here
Any program in the Debian archive can be compiled from sources using the steps above, important to note is that in “apt-get -b build-dep” -b means build from source and build-dep that apt should download any libraries that is needed at the same time.
If you want apt to remove the config files as well when you uninstall a program (or maybe as I have removed them manually and is unable to reinstall using apt-get install)
$apt-get –purge remove pkg-name
This is a command i had to learn the hard way as I (accidenly) removed the /etc/munin (a server monitor tool) directory. After I had done this I was unable to get apt-get install to make any new config files in the /etc/ directory. Turns out that removing without using –purge (normaly) leaves the old config files (if I wish to re install later I assume).
After updating my installation to etch I ran into a sligt problem with apt-get.
I just got an odd error message from apt-get update
GPG error: ftp://www.se.debian.org unstable Release:
The following signatures couldn’t be verified
because the public key is not available:
NO_PUBKEY F1D53D8C4F368D5D
W: You may want to run apt-get update to correct these problems
Well, running apt-get update again (and again…) has no effect;)
What it (tries to) tell me is that the key used to verify the files in the archive was not found
The solution to this is simply
$ gpg --keyserver wwwkeys.eu.pgp.net --recv-keys F1D53D8C4F368D5D $ gpg --armor --export F1D53D8C4F368D5D | apt-key add - $ apt-get update |
The wwwkeys.eu.pgp.net can be exchanged for any other key server that hosts the key, the only thing to note is that you should only use a key server that you feel is trusted.