Tagged “ubuntu”

s/gentoo/ubuntu/

Published by cybso on

This is a post from my original site, which was hosted by the former blog service of the University of Osnabrück. I have moved it to the new site for archiving. Pages linked in this article may no longer work today, and the blog comments under the article no longer exist. Opinions expressed in this article reflect the point of view of the time of publication and do not necessarily reflect my opinion today.

Probier ich es aus? Ich weiß nicht... Eventuell. Aber vielleicht doch nicht. Ich bin so unentschlossen. Hat jemand ne Meinung dazu?

Change

Published by cybso on

This is a post from my original site, which was hosted by the former blog service of the University of Osnabrück. I have moved it to the new site for archiving. Pages linked in this article may no longer work today, and the blog comments under the article no longer exist. Opinions expressed in this article reflect the point of view of the time of publication and do not necessarily reflect my opinion today.

Ich habe habe dem unerschrockenen Steinbock eine Chance gegeben, und mein Gentoo-System auf eine Backup-Festplatte ausgelagert. Aktuell bin ich von KDE 4.1 ziemlich begeistert, aber ob dieser Zustand anhält, werden die nächsten Wochen zeigen müssen. Insbesondere Portage werde ich vermutlich bald vermissen.

Was mir besonders positiv aufgefallen ist, ist die sehr gute Unterstützung für verschlüsselte Systeme. Nicht nur, dass ich ohne großen Aufwand meine gesamte Festplatte verschlüsselt habe - auch im Schlafzustand ist der Rechner nun geschützt. Und das, ohne dass ich irgendwas dafür tun musste. Bisher war es so, dass mein Homeverzeichnis zwar verschlüsselt war, aber nicht der Auslagerungsspeicher. Dadurch ist es theoretisch möglich, den Schlüssel dort zu extrahieren, was natürlich das ganze Konzept über den Haufen wirft.

So, nun muss ich aber erstmal ein paar fehlende Programme nachinstallieren. Wo ist Opera?

Eclipse: Keine Bevormundung durch Ubuntu

Published by cybso on

This is a post from my original site, which was hosted by the former blog service of the University of Osnabrück. I have moved it to the new site for archiving. Pages linked in this article may no longer work today, and the blog comments under the article no longer exist. Opinions expressed in this article reflect the point of view of the time of publication and do not necessarily reflect my opinion today.

Unter Ubuntu fragt Eclipse beim Starten nicht, welcher Workspace verwendet werden soll, sondern wählt immer $HOME/workspace - selbst wenn in den Einstellungen explizit festgelegt wurde, dass er fragen soll.

Woran das genau liegt, kann ich nicht sagen, aber es hat wohl was mit der verwendeten Java-VM zu tun, der Standard ist java-gcj. Umgehen lässt sich dieses Problem, indem die Pakete sun-java6-jdk bzw. sun-java6-jre installiert werden und die Verwendung dieser mithilfe der Umgebungsvariablen JAVA_HOME erzwungen wird:

JAVA_HOME=/usr/lib/jvm/java-6-sun eclipse

Oder dauerhaft, indem man diese in die Datei $HOME/.profile einträgt:

export JAVA_HOME=/usr/lib/jvm/java-6-sun

Nun erscheint bei jedem Start von Eclipse wie gewohnt der "Workspace auswählen"-Dialog.

Nachtrag 10.12.2008:

Der richtige Ort, um diese Änderung global festzulegen, ist /etc/environment:

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
JAVA_HOME=/usr/lib/jvm/java-6-sun

Zusätzlich gibt es unter https://help.ubuntu.com/community/Java eine kleine Anleitung, wie man die vom System verwendete Java-VM ändern kann.

Enhance Intrepid Ibex with TuxOnIce

Published by cybso on

This is a post from my original site, which was hosted by the former blog service of the University of Osnabrück. I have moved it to the new site for archiving. Pages linked in this article may no longer work today, and the blog comments under the article no longer exist. Opinions expressed in this article reflect the point of view of the time of publication and do not necessarily reflect my opinion today.

Ubuntu 8.10 ("Intrepid Ibex") uses the kernel's default suspend system, swsusp, but lacks support for TuxOnIce (formally known as "suspend2"). TOI has some advantages to the classic suspend system, for example "suspend to file", "LZW compression" (for faster resuming) and the ability to cancel any suspend request by pressing ESC. Have a look at the feature list for a comparison of these systems.

Espacially "suspend to file" is extremly important to me, because it allows to resume from an encrypted root partition. Of course, this also works with swsusp by using an encrypted swap device, but then you can't use a random password (or a password file stored on root) and have to enter at least two passwords when booting or resuming: one for root (/) and one for swap.

To add TOI support to Ubuntu, you have to build your own kernel. It's pretty easy, but if you use restricted kernel modules (drivers for your graphic card, VMWare/VirtualBox, ...) you will have to recompile them. So, here we go. First of all, download the kernel source and install some additional packages required at compile time:

(continue reading)

Integrate TuxOnIce into Ubuntu's hibernation process

Published by cybso on

This is a post from my original site, which was hosted by the former blog service of the University of Osnabrück. I have moved it to the new site for archiving. Pages linked in this article may no longer work today, and the blog comments under the article no longer exist. Opinions expressed in this article reflect the point of view of the time of publication and do not necessarily reflect my opinion today.

Warning: At the moment I can not recommend to use this script in conjunction with filewriter if you use a journaling filesystem for your root partition (ext3, reiser, ...). The reason is that when using filewriter the initramfs-script in /etc/initramfs-tools/scripts/local-premount/resume_tuxonice mounts this partition read-only to get the hibernation file's target. Unfortunately, the journal will be replayed in any case, so "mount -r /dev/hdX" does not mean "mount /dev/hdX, but don't make any changes on it". And this may result in a filesystem corruption because the resumed system things that these open transaction have not been handled yet. I'll do some changes to the scripts during the weekend, so please be patient of you want to "suspend to file". Yesterday, I described how to patch TuxOnIce-support into Ubuntu's kernel image. Today we will learn how to integrate this into Ubuntu's default hibernation framework, pm-hibernate. By doing this, you'll benefit from TuxOnIce' features without modifying your bootloader's configuration file and will be able to use your desktop's "Suspend to Disk"-command without changing any system file (because a customized system file might be overwritten on your next update). Furthermore, you will be able to combine suspend to disk with encrypted swap devices or (I prefer this) suspend to a file on your encrypted root partition.

Please note that the scripts I'll introduce are tested only by myself (yet), and they still lack of some features. I would be happy about every improvement. And of course I do not provide any warranty, you'll do this on your own risk. I think that the worst thing that might happen is that data on your root partition gets lost. But of course you're doing backups, don't you?

So, let's start. Oh, wait... did you ensure that you have a suitable backup? Ok. First I'll introduce what has to be done, and at the end I'll provide the scripts that implements this. Well, the first thing we have to do is to add resume support into Ubuntu's initramfs-Image. That is the file stored in /boot, starting with ' initrd.img' and ending with your kernel's version. If you're curious: it's a gzip'd cpio-archive, you can extract it using the following command:

(continue reading)

nVidia + Intrepid: Install Linux driver version 180

Published by cybso on

This is a post from my original site, which was hosted by the former blog service of the University of Osnabrück. I have moved it to the new site for archiving. Pages linked in this article may no longer work today, and the blog comments under the article no longer exist. Opinions expressed in this article reflect the point of view of the time of publication and do not necessarily reflect my opinion today.

If you experience problems or poor performance using Ubuntu's latest nVidia driver nvidia-glx-177 (as I did with a "nVidia Quadro NVS 160M"), try to upgrade to version 180. A package has been build for the next version of ubuntu (called "Jaunty Jackalope"), but sadly it has not been backported to Intrepid yet.

Who cares, I'll explain how to use Jaunty's repository with Intrepid to install this driver. First, make sure that you installation is up to date:

sudo apt-get update
sudo apt-get upgrade

Now, add Jaunty's "universe" repository to Apt's sources:

echo 'deb http://de.archive.ubuntu.com/ubuntu/ jaunty universe' | \
 sudo tee /etc/apt/sources.list.d/jaunty-universe.list

Prohibit an unmeant package replacement using Apt pinning. Edit /etc/apt/preferences (which might not exist yet) and put the following lines into it:

Package: *
Pin: release a=jaunty
Pin-Priority: 40

Multiple entries have to be separated by blank lines. If you want to know what this entries mean: there is an excellent (german) article at FedoraWiki.

Now run apt-get update again. If you upgraded before, apt-get upgrade should report zero updates. If there is a bunch of updates now that has not occured before, cancel and check wether you've edited /etc/apt/preferences correctly.

Last step: install the driver.

sudo apt-get install nvidia-glx-180

If you did not used the proprietary driver before, you have to edit /etc/X11/xorg.conf. Or, what I would suggest, install and run envyng to replace your current driver.

Beware

Unfortunately, Suspend-To-Disk-Support seems to be completely broken in this version. X crashes on resume. I was not able to get this working, neither with 180.06 nor with 180.11. At the moment, I've installed nvidia-glx-173 again.