Picasa
Just to let people know that the new Picasa for Linux from Google (http://picasa.google.com/linux/) works fine in AMD64; just download the .deb from http://picasa.google.com/linux/thanks-deb.html and install it with dpkg -i --force-architecture .deb_file. All you should need is the ia32-libs package installed. -- Nelson Menezes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Tyan Europe
Any experience with Tyan Europe technical support ([EMAIL PROTECTED])? I posed a question to the above address about raid1 support by the mainboard Tyan KWE 2895. The question was unanswered. Although I do not need anymore a reply, having setup raid1 through the OS amd64 debian testing, I am still curious if that address exists. Perhaps more than curious, should one day I need it. Cheers francesco pietra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Why is amd64 sid and testing broken?
Hi I would like to do an update but I get this fault ---% --- Fehl http://ftp.de.debian.org sid/main Packages 404 Not Found Ign http://security.debian.org stable/updates/contrib Packages/DiffIndex Ign http://security.debian.org stable/updates/non-free Packages/DiffIndex Fehl http://ftp.de.debian.org sid/contrib Packages 404 Not Found Fehl http://ftp.de.debian.org sid/non-free Packages 404 Not Found Fehl http://ftp.de.debian.org sid/main Sources 404 Not Found Fehl http://ftp.de.debian.org sid/contrib Sources 404 Not Found OK ftp://ftp.nerim.net sid Release OK http://spello.sscnet.ucla.edu sid/main Packages Fehl http://ftp.de.debian.org sid/non-free Sources 404 Not Found ---%--- --% Konnte http://ftp.de.debian.org/debian-amd64/debian/dists/sid/main/binary-amd64/Packages.gz nicht holen 404 Not Found Konnte http://ftp.de.debian.org/debian-amd64/debian/dists/sid/contrib/binary-amd64/Packages.gz nicht holen 404 Not Found Konnte http://ftp.de.debian.org/debian-amd64/debian/dists/sid/non-free/binary-amd64/Packages.gz nicht holen 404 Not Found Konnte http://ftp.de.debian.org/debian-amd64/debian/dists/sid/main/source/Sources.gz nicht holen 404 Not Found Konnte http://ftp.de.debian.org/debian-amd64/debian/dists/sid/contrib/source/Sources.gz nicht holen 404 Not Found Konnte http://ftp.de.debian.org/debian-amd64/debian/dists/sid/non-free/source/Sources.gz nicht holen 404 Not Found %--- and on ftp.de.debian.org/debian-amd64/debian/dists/sid I found a README with this content amd64 is now available on ftp.debian.org Please use your nearest ftp.debian.org mirror now for the etch or unstable version of the amd64 port of Debian. The sarge version continues to be available from amd64.debian.net and its mirrors until sarge is archived. but I don't found a Packages.gz or something else is that a mirror fault? greetings Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is amd64 sid and testing broken?
Alexander Syring wrote: Hi I would like to do an update but I get this fault ---% --- Fehl http://ftp.de.debian.org sid/main Packages 404 Not Found Ign http://security.debian.org stable/updates/contrib Packages/DiffIndex Ign http://security.debian.org stable/updates/non-free Packages/DiffIndex Fehl http://ftp.de.debian.org sid/contrib Packages 404 Not Found Fehl http://ftp.de.debian.org sid/non-free Packages 404 Not Found Fehl http://ftp.de.debian.org sid/main Sources 404 Not Found Fehl http://ftp.de.debian.org sid/contrib Sources 404 Not Found OK ftp://ftp.nerim.net sid Release OK http://spello.sscnet.ucla.edu sid/main Packages Fehl http://ftp.de.debian.org sid/non-free Sources 404 Not Found ---%--- --% Konnte http://ftp.de.debian.org/debian-amd64/debian/dists/sid/main/binary-amd64/Packages.gz nicht holen 404 Not Found Konnte http://ftp.de.debian.org/debian-amd64/debian/dists/sid/contrib/binary-amd64/Packages.gz nicht holen 404 Not Found Konnte http://ftp.de.debian.org/debian-amd64/debian/dists/sid/non-free/binary-amd64/Packages.gz nicht holen 404 Not Found Konnte http://ftp.de.debian.org/debian-amd64/debian/dists/sid/main/source/Sources.gz nicht holen 404 Not Found Konnte http://ftp.de.debian.org/debian-amd64/debian/dists/sid/contrib/source/Sources.gz nicht holen 404 Not Found Konnte http://ftp.de.debian.org/debian-amd64/debian/dists/sid/non-free/source/Sources.gz nicht holen 404 Not Found %--- and on ftp.de.debian.org/debian-amd64/debian/dists/sid I found a README with this content amd64 is now available on ftp.debian.org Please use your nearest ftp.debian.org mirror now for the etch or unstable version of the amd64 port of Debian. The sarge version continues to be available from amd64.debian.net and its mirrors until sarge is archived. but I don't found a Packages.gz or something else is that a mirror fault? greetings Alex Debian uses a mirror structure of the format deb http://ftp.XX.debian.org/debian RELEASE main contrib non-free. Anything different, especially containing debian-amd64 is *NOT* Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
SOLVED: Software-RAID1 on sarge (AMD64) (was: Re: install-mbr on amd64?)
In the last few days, I was struggling to convert a remote machine with two identical SATA disks (sda and sdb) to a Software RAID 1. Especially the boot-part was tricky as I had no console access to the machine. The whole procedure was done remotely via SSH. I use the md tools (mdadm) and lilo as bootloader. I chose LILO because IMHO it's more straightforward in this setup than GRUB and I have no other Operating Systems I would want to boot. The system was installed on the first disk, the second one has not been used before. Those are the steps I went through: 1. Install a Software-RAID capable kernel and boot the system with it; Install the md tools: 'apt-get install mdadm'; 2. partition the second harddrive (sdb). I created two partitions, a large one at the beginning of the disk (sdb1) and a small swap-partition at the end (sdb2). I do not use separate /boot partitions. NOTE: I do not use two swap spaces on the two disks; instead, I create a RAID array consisting of the two smaller partitions on the two discs and create the swap space on it. In case of a disk failure, I don't need to reboot the system because the swap space is also on RAID. Otherwise, a disk failure would toast one swap space, probably leaving the system in a unusable state until rebooted. Important: both partitions need to be of the type 0xFD Linux raid autodetect 3. Create the RAID arrays: $ mdadm --create /dev/md0 --level=1 --raid-disks=2 missing /dev/sdb1 $ mdadm --create /dev/md1 --level=1 --raid-disks=2 missing /dev/sdb2 4. Create filesystems $ mkfs -t xfs /dev/md0 $ mkswap /dev/md1 I use XFS as filesystem because it has such nice features as online resizing etc and is, IMHO, very stable and mature. Of course you can use whatever you like. 5. Copy the existing Debian system to the new RAID $ mkdir -p /mnt/newroot $ mount /dev/md0 /mnt/newroot $ cd / $ find . -xdev | cpio -pm /mnt/newroot 6. To see if the the new RAID array comes up properly after a reboot, add the following line to /etc/fstab of the system still running from sda: /dev/md0 /mnt/newroot xfs defaults 0 0 Reboot and check with mount if /dev/md0 is mounted properly. 7. I now modified /etc/lilo.conf of the system still running from sda so that on the next reboot, /dev/md0 would be mounted as root filesystem while lilo would still access /boot on sda: # START /etc/lilo.conf lba32 delay=50 map=/boot/map boot=/dev/sda image=/boot/vmlinuz-2.6.16.18 label=RAID root=/dev/md0 read-only alias=1 image=/boot/vmlinuz-OLD label=LinuxOLD root=/dev/sda1 read-only alias=2 # END /etc/lilo.conf This way, we still have a working boot (LinuxOLD) which uses /dev/sda1 as root in case anything goes wrong (NOTE: sda1 is the root partition of the old, non-RAID system). 8. Run LILO First, run $ lilo -t -v to see what lilo would do. If everything is OK do: $ lilo -v $ lilo -v -R RAID This way, lilo chooses the image labeled RAID on the next reboot. On every subsequent reboot, the next entry will be used (so the image specified with -R gets used only one time). So if the system doesn't come up, you can reset it and lilo will boot the other image. 9. Edit the new fstab The new fstab, located at /mnt/newroot/etc/fstab, must now be changed so that /dev/md0 gets mounted as root filesystem: # START /mnt/newroot/etc/fstab /dev/md0 / xfs defaults0 0 /dev/md1 swapswap proc /proc proc # END /mnt/newroot/etc/fstab 10. Reboot the system. If it comes up, check with mount if /dev/md0 is mounted as root filesystem. If it doesn't come up properly, just reset the machine / reboot it and it will boot the other image. 11. Integrade sda into RAID array First, repartition sda exactly as sdb. The partitions must either be of the exact size or greater than those on sdb. Also, the partition type must be 0xFD. Then, integrate the partitions into the existing RAID array: $ mdadm --add /dev/md0 /dev/sda1 $ mdadm --add /dev/md1 /dev/sda2 Now the arrays are being synchronized. Check with $ watch cat /proc/mdstat that the sync proccess is running. You must wait for this process to complete on both arrays. 12. Modify lilo.conf Now we want to boot completely from /dev/md0: # START /etc/lilo.conf lba32 boot=/dev/md0 root=/dev/md0 install=/boot/boot-menu.b map=/boot/map prompt delay=50 timeout=50 vga=normal raid-extra-boot=/dev/sda,/dev/sdb default=RAID image=/boot/vmlinuz-2.6.16.18 label=RAID read-only root=/dev/md0 alias=1 image=/boot/vmlinuz-OLD label=LinuxOLD read-only
Software RAID5
Hi, I've a system with a software raid1 on 2 sata drive 80 GB I've all my system on LVM on this underlying raid. For performances reasons (video editing), I'm thinking if a RAID5. Is there somebody with some experience with raid5: - performances - behaviour in case of a crash Is there an easy process to migrate from raid1 to raid5 without reinstalling everything? Regards Jean-Luc pgpDDYrPlHxVO.pgp Description: PGP signature
Re: Lots of packets are missing in amd64/etch...
Goswin von Brederlow wrote: For etch to have all amd64 packages every package has to migrate to etch. That just takes time. And if packages happen to have RC bugs, then that takes an even longer time. ;-) -- Please ignore previous fortune. Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SOLVED: Software-RAID1 on sarge (AMD64)
Kilian [EMAIL PROTECTED] writes: In the last few days, I was struggling to convert a remote machine with two identical SATA disks (sda and sdb) to a Software RAID 1. Especially the boot-part was tricky as I had no console access to the machine. The whole procedure was done remotely via SSH. I use the md tools (mdadm) and lilo as bootloader. I chose LILO because IMHO it's more straightforward in this setup than GRUB and I have no other Operating Systems I would want to boot. The system was installed on the first disk, the second one has not been used before. Those are the steps I went through: 1. Install a Software-RAID capable kernel and boot the system with it; Install the md tools: 'apt-get install mdadm'; Meaning any Debian kernel. :) 2. partition the second harddrive (sdb). I created two partitions, a large one at the beginning of the disk (sdb1) and a small swap-partition at the end (sdb2). I do not use separate /boot partitions. NOTE: disk speed differs by around a factor of 2 between start and end. Which one is the fast one can depend on the disk but usualy the start is. Better swap there. NOTE: I do not use two swap spaces on the two disks; instead, I create a RAID array consisting of the two smaller partitions on the two discs and create the swap space on it. In case of a disk failure, I don't need to reboot the system because the swap space is also on RAID. Otherwise, a disk failure would toast one swap space, probably leaving the system in a unusable state until rebooted. It would cause processes to segfault all over and take down the system. Important: both partitions need to be of the type 0xFD Linux raid autodetect Actualy not. mdadm can work just as well without it. Doesn't hurt though. 3. Create the RAID arrays: $ mdadm --create /dev/md0 --level=1 --raid-disks=2 missing /dev/sdb1 $ mdadm --create /dev/md1 --level=1 --raid-disks=2 missing /dev/sdb2 4. Create filesystems $ mkfs -t xfs /dev/md0 $ mkswap /dev/md1 I use XFS as filesystem because it has such nice features as online resizing etc and is, IMHO, very stable and mature. Of course you can use whatever you like. As does ext3, even more so. 5. Copy the existing Debian system to the new RAID $ mkdir -p /mnt/newroot $ mount /dev/md0 /mnt/newroot $ cd / $ find . -xdev | cpio -pm /mnt/newroot Fun, fun. A copy of /proc. That's a few Gig wasted depending on the size of /proc/kcore. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Software RAID5
Jean-Luc Coulon (f5ibh) [EMAIL PROTECTED] writes: Hi, I've a system with a software raid1 on 2 sata drive 80 GB I've all my system on LVM on this underlying raid. For performances reasons (video editing), I'm thinking if a RAID5. Is there somebody with some experience with raid5: - performances Slower on write (takes cpu power). Better use a striped lvm on plain disks for temp storage and raid only for the source and final product. You also want PCIe or PCI-X for the disk controler. A simple PCI slot is a serious bottleneck. - behaviour in case of a crash It hangs for a while (up to minutes sometimes) before accepting the disk as dead and then goes on. Or the hardware or disk driver crash and take down the kernel depending on the hardware and luck. Is there an easy process to migrate from raid1 to raid5 without reinstalling everything? degrade the raid1, setup a degraded raid5, copy the FS, kill the raid1, resync the raid5. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lots of packets are missing in amd64/etch...
Eduardo M KALINOWSKI [EMAIL PROTECTED] writes: Goswin von Brederlow wrote: For etch to have all amd64 packages every package has to migrate to etch. That just takes time. And if packages happen to have RC bugs, then that takes an even longer time. ;-) Time is ageless. :) MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is amd64 sid and testing broken?
On Sun, 28 May 2006 12:30:16 +0200, Jo Shields wrote: Anything different, especially containing debian-amd64 is *NOT* Debian. Not anymore, at least. -- Best Regards, Jack Linux User #264449 Powered by Debian GNU/Linux on AMD64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Lots of packets are missing in amd64/etch...
Koen Vermeer wrote: So, what is the right way to handle things if one has a running etch system (based on debian-amd64, with a line in sources.list such as 'deb ftp://ftp.nl.debian.org/debian-amd64/debian/ testing contrib main non-free')? For etch/testing the mirror is: ftp://ftp.XX.debian.org/debian/ testing main contrib non-free Do nothing until the full official etch repository is available? ftp://ftp.XX.debian.org/debian etch main contrib non-free =) ___ Navegue com o Yahoo! Acesso Grátis, assista aos jogos do Brasil na Copa e ganhe prêmios de hora em hora! http://br.yahoo.com/artilheirodacopa/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tyan Europe
Francesco Pietra wrote: Any experience with Tyan Europe technical support ([EMAIL PROTECTED])? I posed a question to the above address about raid1 support by the mainboard Tyan KWE 2895. The question was unanswered. Tyan USA blew off a recent question as soon as I mentioned Linux (the question really was particular to Linux) - they apparently don't see Linux users as important to support. - That being said, they do better support than most MB providers. Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 What is, is; What was, was; What might of been; never will be. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Bulk] Re: Why is amd64 sid and testing broken?
Jo Shields wrote: Anything different, especially containing debian-amd64 is *NOT* Debian. But stable/sarge is ftp.XX.debian.org/debian-amd64/debian/ RELEASE main contrib non-free ___ Abra sua conta no Yahoo! Mail: 1GB de espaço, alertas de e-mail no celular e anti-spam realmente eficaz. http://mail.yahoo.com.br/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SOLVED: Software-RAID1 on sarge (AMD64)
Goswin von Brederlow wrote: Kilian [EMAIL PROTECTED] writes: 5. Copy the existing Debian system to the new RAID $ mkdir -p /mnt/newroot $ mount /dev/md0 /mnt/newroot $ cd / $ find . -xdev | cpio -pm /mnt/newroot Fun, fun. A copy of /proc. That's a few Gig wasted depending on the size of /proc/kcore. Umm, that's prevented by the -xdev option, isn't it? Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tyan Europe
On Sun, 2006-05-28 14:02:43 -0500, Karl Schmidt [EMAIL PROTECTED] wrote: Francesco Pietra wrote: Any experience with Tyan Europe technical support ([EMAIL PROTECTED])? I posed a question to the above address about raid1 support by the mainboard Tyan KWE 2895. The question was unanswered. Tyan USA blew off a recent question as soon as I mentioned Linux (the question really was particular to Linux) - they apparently don't see Linux users as important to support. - That being said, they do better support than most MB providers. I bought the very first 2x Athlon board they build and had hear problems in the case (basically, the board was killed by head, twice) They promptly shipped new boards, even where basically I was guilty of killing them. So (in Germany), I'm quite satisfied with their support. MfG, JBG -- Jan-Benedict Glaw [EMAIL PROTECTED]. +49-172-7608481 _ O _ Eine Freie Meinung in einem Freien Kopf| Gegen Zensur | Gegen Krieg _ _ O für einen Freien Staat voll Freier Bürger | im Internet! | im Irak! O O O ret = do_actions((curr | FREE_SPEECH) ~(NEW_COPYRIGHT_LAW | DRM | TCPA)); signature.asc Description: Digital signature
Re: Tyan Europe
Karl Schmidt wrote: ..as I mentioned Linux (the question really was particular to Linux) That should have read ..as I mentioned Linux (the question really _wasn't_ particular to Linux) Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Give me four parameters and I can fit an elephant. Give me five and I can wag its tail'' (The source of the above quote?? Variants have been attributed to C.F. Gauss, Niels Bohr, Lord Kelvin, Enrico Fermi.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XGL
On Sat, 27 May 2006 19:00:08 +0200, valeanu.a wrote: ich have Xgl cvs running for at least 7 days uptime with no big problems at all. Lucky you :D I am trying to make the bloody thing work, and it dies complaining about the FontPath. Needless to say, starting my normal X server works beautifully. I even tried to specify the -fp option when starting XGL but no luck. Could anyone please post the Files section of their xorg.conf? Thanks! -- Best Regards, Jack Linux User #264449 Powered by Debian GNU/Linux on AMD64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SOLVED: Software-RAID1 on sarge (AMD64)
Michal Schmidt wrote: Goswin von Brederlow wrote: Kilian [EMAIL PROTECTED] writes: 5. Copy the existing Debian system to the new RAID $ mkdir -p /mnt/newroot $ mount /dev/md0 /mnt/newroot $ cd / $ find . -xdev | cpio -pm /mnt/newroot Fun, fun. A copy of /proc. That's a few Gig wasted depending on the size of /proc/kcore. Umm, that's prevented by the -xdev option, isn't it? It is, since -xdev prevents find from descending directories on other filesystems, which is exactly what /proc is. -- Kilian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SOLVED: Software-RAID1 on sarge (AMD64)
Goswin von Brederlow wrote: Kilian [EMAIL PROTECTED] writes: In the last few days, I was struggling to convert a remote machine with two identical SATA disks (sda and sdb) to a Software RAID 1. Especially the boot-part was tricky as I had no console access to the machine. The whole procedure was done remotely via SSH. I use the md tools (mdadm) and lilo as bootloader. I chose LILO because IMHO it's more straightforward in this setup than GRUB and I have no other Operating Systems I would want to boot. The system was installed on the first disk, the second one has not been used before. Those are the steps I went through: 1. Install a Software-RAID capable kernel and boot the system with it; Install the md tools: 'apt-get install mdadm'; Meaning any Debian kernel. :) True, mine had it as a module though, which meant initrd, and since I was working remote, I didn't want to bring in another pitfall which meant compiling the kernel with RAID support built into it. 2. partition the second harddrive (sdb). I created two partitions, a large one at the beginning of the disk (sdb1) and a small swap-partition at the end (sdb2). I do not use separate /boot partitions. NOTE: disk speed differs by around a factor of 2 between start and end. Which one is the fast one can depend on the disk but usualy the start is. Better swap there. I didn't know that, thanks for the hint! NOTE: I do not use two swap spaces on the two disks; instead, I create a RAID array consisting of the two smaller partitions on the two discs and create the swap space on it. In case of a disk failure, I don't need to reboot the system because the swap space is also on RAID. Otherwise, a disk failure would toast one swap space, probably leaving the system in a unusable state until rebooted. It would cause processes to segfault all over and take down the system. I knew there was a reason ;-) Important: both partitions need to be of the type 0xFD Linux raid autodetect Actualy not. mdadm can work just as well without it. Doesn't hurt though. Didn't know that either, thanks. [...] I use XFS as filesystem because it has such nice features as online resizing etc and is, IMHO, very stable and mature. Of course you can use whatever you like. As does ext3, even more so. Let's not start a filesystem flamewar, you'd propably win ;-) 5. Copy the existing Debian system to the new RAID $ mkdir -p /mnt/newroot $ mount /dev/md0 /mnt/newroot $ cd / $ find . -xdev | cpio -pm /mnt/newroot Fun, fun. A copy of /proc. That's a few Gig wasted depending on the size of /proc/kcore. As pointed out by Michael Schmidt, -xdev takes care of that. Of course if there are several filesystems on the original disk, you'd have to copy each separately. Thanks for your suggestions! -- Kilian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XGL
Hello all, as requested the howto: http://blue.dyn-o-saur.com/debianxgl/debianxglhowto.html for [EMAIL PROTECTED] my File section in the xorg.conf Section Files FontPath /usr/share/fonts/type/gsfonts FontPath /usr/share/fonts/truetype/freefont FontPath /usr/share/fonts/truetype/openoffice FontPath /usr/share/fonts/X11/Type1 FontPath /usr/share/fonts/X11/misc FontPath /usr/share/fonts/X11/75dpi FontPath /usr/share/fonts/X11/100dpi EndSection -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SOLVED: Software-RAID1 on sarge (AMD64)
Michal Schmidt [EMAIL PROTECTED] writes: Goswin von Brederlow wrote: Kilian [EMAIL PROTECTED] writes: 5. Copy the existing Debian system to the new RAID $ mkdir -p /mnt/newroot $ mount /dev/md0 /mnt/newroot $ cd / $ find . -xdev | cpio -pm /mnt/newroot Fun, fun. A copy of /proc. That's a few Gig wasted depending on the size of /proc/kcore. Umm, that's prevented by the -xdev option, isn't it? Michal Oh, my bad. I tought it was -xdir to exclude the dev directory from udev. But yes, it will omit proc and any other mounted filesystems. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SOLVED: Software-RAID1 on sarge (AMD64)
Kilian [EMAIL PROTECTED] writes: Goswin von Brederlow wrote: Kilian [EMAIL PROTECTED] writes: In the last few days, I was struggling to convert a remote machine with two identical SATA disks (sda and sdb) to a Software RAID 1. Especially the boot-part was tricky as I had no console access to the machine. The whole procedure was done remotely via SSH. I use the md tools (mdadm) and lilo as bootloader. I chose LILO because IMHO it's more straightforward in this setup than GRUB and I have no other Operating Systems I would want to boot. The system was installed on the first disk, the second one has not been used before. Those are the steps I went through: 1. Install a Software-RAID capable kernel and boot the system with it; Install the md tools: 'apt-get install mdadm'; Meaning any Debian kernel. :) True, mine had it as a module though, which meant initrd, and since I was working remote, I didn't want to bring in another pitfall which meant compiling the kernel with RAID support built into it. Important: both partitions need to be of the type 0xFD Linux raid autodetect Actualy not. mdadm can work just as well without it. Doesn't hurt though. Didn't know that either, thanks. If raid is buildin into the kernel and all the disk drivers for the raid too then the type 0xFD causes the kernel to already detect and start the raid. So you need no initrd and no mdadm to boot. So in your case you DO need that. (PS: I prefer non initrd boot too and have the same). MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lots of packets are missing in amd64/etch...
Koen Vermeer [EMAIL PROTECTED] writes: On Sun, 2006-05-28 at 09:34 -0300, Eduardo M KALINOWSKI wrote: For etch to have all amd64 packages every package has to migrate to etch. That just takes time. And if packages happen to have RC bugs, then that takes an even longer time. ;-) So, what is the right way to handle things if one has a running etch system (based on debian-amd64, with a line in sources.list such as 'deb ftp://ftp.nl.debian.org/debian-amd64/debian/ testing contrib main non-free')? Do nothing until the full official etch repository is available? Or should one add a line to sources.list that includes the new, official stuff? Koen The old archive is discontinued. You should also remove any sarge line as that confuses apt-get (sarge and etch/sid have some packages with the same version but debian has different debs). Just put the official etch in there and things will upgrade as they move into etch. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why is amd64 sid and testing broken?
Jack Malmostoso [EMAIL PROTECTED] writes: On Sun, 28 May 2006 12:30:16 +0200, Jo Shields wrote: Anything different, especially containing debian-amd64 is *NOT* Debian. Not anymore, at least. Never was. debian-amd64 was always the inofficial archive. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Bulk] Re: Why is amd64 sid and testing broken?
Gleidson Echeli Leopoldo [EMAIL PROTECTED] writes: Jo Shields wrote: Anything different, especially containing debian-amd64 is *NOT* Debian. But stable/sarge is ftp.XX.debian.org/debian-amd64/debian/ RELEASE main contrib non-free Which is not Debian. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tyan Europe
On Sun, 28 May 2006, Karl Schmidt wrote: Francesco Pietra wrote: Any experience with Tyan Europe technical support ([EMAIL PROTECTED])? I posed a question to the above address about raid1 support by the mainboard Tyan KWE 2895. The question was unanswered. Tyan USA blew off a recent question as soon as I mentioned Linux (the question really was particular to Linux) - they apparently don't see Linux users as important to support. - That being said, they do better support than most MB providers. Just for another data point, we have gotten Linux-specific bios fixes from Tyan, so it all depends on who you are talking to and when. /Mattias Wadenstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
