Tschüß StudiVZ ich werde dich nicht vermissen. Mein Account dort ist jedenfalls Geschichte, und nein, ich habe keinen Facebook/Twitter/sonstwas Account.
I’ve just spent far too much time trying to install voyage linux on my new ALIX.2D13. Everything was fine, the only problem was that I did try to use GRUB and that wasn’t working. After changing to LILO it works like a charm. The problem is probably caused by a huge version gap between etch and sid. Etch has some something like 0.9x and sid 1.9x. I thought that the Voyage installer would use the shipped grub inside a chroot. Anyway, LILO works and this is fine. I have no special requirements for this box’s bootmanager. As soon as everything is set up and tested the box is going to be deployed.
The installation of voyage linux itself is covered in detail in the Getting Started guide.
Very usefull information can be found at networksoul and this chaos wiki.
I recommend picocom to connect to the serial console:
picocom –baud 38400 –flow n –databits 8 /dev/ttyUSB0
If your computer doesn’t have a serial port anymore, like mine, I recommend the LogiLink “USB2.0 to Serial Adapter” (UA0043 v.2.0). It’s cheap and works flawlessly. Another great LogiLink product I can reommend in this context is the LogiLink “USB2.0 Aluminum All-in-one Card Reader” (CR0001B v.2.0). Why I mention these two here? I find it hard to find cheap linux compatible adapters of which I know that they work on linux, so here is the information I would have like had before I bought those. The USB-Serial-Adapter is recognized as “Prolific Technology, Inc. PL2303 Serial Port”. The Card-Reader is shown as four separate drives.
I just got me some DS18S20 (1-wire Temperature sensors) and a DS2940 (1-wire to USB adapter). The first two did work like a charm, but the third one gave me CRC errors.
CRC Failed. CRC is 63 instead of 0×00
The reason was just that, after running the first two for a while, I did just disconnect them and attached the thrid one. My mistake was not to delete/re-initialize the .digitemprc. After moving the .digitemprc out of the way and re-initializing the new one the thrid one did also work.
Show all devices on the 1-wire bus:
digitemp_DS2490 -sUSB -w
Initialize the .digitemprc:
digitemp_DS2490 -sUSB -i
Read all sensors:
digitemp -sUSB -a -r750
Thanks to Marc for the hint.
Some usefull links:
Here are some pictures of my 1-wire bus:
Quick-Note: cat /boot/initrd.img | gzip -d | cpio -i -H newc
It looks like Qt 4.6.2 is ready to upload. That means the upload of KDE 4.4 to Debian unstable should be very close.
I looks like some major confusion on the debian-release and debian-devel lists led to the upload of broken version of libjpeg8, the successor of libjepeg62. This could delay the freeze of squeeze further and lead to some breakage in unstable. Be warned and alert.
Is the EMV PIN check really so bad, eh I mean BAD (Broken as Designed)?
Perhaps I should lock up my cards somewhere safe …
Sometimes, at least. I did just want to look up some term I’ve read somewhere and of course … it’s already deleted. Löschhölle at its best. It was there once, but now it’s gone.
Why do they have to do this?
Is the wikipedia database so overloaded that they have to throw out everything that is not 100% fine or are these just selfish, stupid and jealous people trying to show others how great they are?
Really, Wikipedia-Admins, I don’t quite get it …
Have you ever tried to move your Debian root filesystem to a RAID? Ok, no problem so far. What about LVM-on-RAID? Still no trouble? Then what about Root-on-LVM-on-Crypto-on-RAID? Sounds funny. Debian has several helpscripts which are able to create a suitable initrd file for this kind of setup. This is good and bad at the same time. The good thing is that they can detect a correct setup and create an appropriate initrd. The bad about this is that it won’t work if you just moving your system to this kind of setup. Imagine you’re still on an ordinary partition without all this fancy crypto, raid and LVM stuff. If you just execute update-initramfs -k <kernel> -u/-c the initramfs tools and the supplied hook scripts won’t know about your intentions. So you’ll have to create a full equipped chroot, set everything up like it would be on a realy Root-on-LVM-on-Crypto-on-RAID-System and run update-initramfs there. Of course you could build the initrd by hand, but I’m not going this Gentoo way.
So, what do you have to do? First you’ll have to create your RAID, luks Volume and LVM on top of each other. See the Gentoo tutorial above for these steps. This should be pretty straight forward. The interesting part starts as soon as you try to boot from your new root. If you did follow the tutorial you should have a working Grub but it won’t be able to boot your system since it can’t unlock your root fs.
So, after you’re back into your good ol’ system setup the chroot. This includes assembling the RAID, unlocking your luks Volume and mounting the LV. So these are the steps, assuming sane defaults for folders, partitions and device names:
mdadm --assemble /dev/md2 /dev/sdc2 /dev/sdd2 cryptsetup luksOpen /dev/md2 cryptoroot pvscan vgchange -ay vg mount -t ext3 /dev/mapper/vg-root /mnt mount -t ext2 /dev/sdc1 /mnt/boot mount -t proc proc /mnt/proc mount --bind /dev /mnt/dev LANG=C chroot /mnt /bin/bash
So, now you’re inside your proper chroot. You could just run update-initramfs, but that’ll probably fail. You need to setup mdadm first and create your crypttab.
Your /etc/mdadm/mdadm.conf should at least contain the partitions to scan and your array.
The command mdadm –detail –scan >> /etc/mdadm/mdadm.conf should do it. But verify the file yourself!
Next you have to tell the mdadm-initramfs-script to start this array on boot. This is set in the file /etc/default/mdadm. Insert the full name of your array (e.g. /dev/md2) into the INITRDSTART variable in this file.
Now define a proper crypttab and you should be ready to create a working initrd. Make your crypttab look something like this:
cryptoroot /dev/md2 none luks,tries=3
Just generate a new initramfs, update grub (if necessary) and reboot.
update-initramfs -k all -u update-grub
In case you encounter any error let me know, I’ll try to help.
Letzte Kommentare