Re[2]: Enlighten me about jigdo ..
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! MW real image. The issue was not the load on the debian mirrors but on the MW debian iso mirrors that kept the real isos available for rsyncing. This MW rsync ate a lot of cputime. And not to forget: memory usage - I've some experience in rsyncing complete images against another, here at my server and mirror this is a bit of work for the server. If there are some rsyncs running for images this machine runs out of memory and rsyncing only works with choosen blocksize to 8092 (took sometime to find this). So jigdo is just a better way for distributing images, works fine at most of the time and does not produce high load. So thanks Richard for this great tool, even it takes much time to build a file database for my local mirror ;-) Jan - -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (MingW32) Comment: Benutzt PGP! Fragen? [EMAIL PROTECTED] iD8DBQE/uhu1vvmCkIIgH8QRAi63AKCaYwZPu4NCuIFuaxBxHDug6W00PQCgqswz B0RoDSUWFBGtwC79+OTe8I4= =qfv9 - -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (MingW32) Comment: Benutzt PGP! Fragen? [EMAIL PROTECTED] iD8DBQE/uh16vvmCkIIgH8QRAn3xAKCWBiY1NGiueW1+HqSzcYLkqYpIfACfVO1d JnmV6ytrIJEhvExXH02kZpw= =Ax/0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation der offiziellen testing Distribution
At the time I wrote it, this was true for all testing/unstable CDs. Does anybody know whether the CDs became installable again with the old installer later? I don't know, but today I tried to install testing using jigdo (the jigdo file that's referenced from the Debian web page, I think it's from the .hu site) and got an error configuring the keyboard. I don't remember the error message, but I did a web search and found that the error was reported months ago. Did anyone not have that problem? I ignored the error, got a lot more errors, then gave up and installed stable and upgraded. Sorry I don't remember more detail, but I can say that I have been unable to install testing by using jigo, downloading a CD image from the .hu site, or using netinstall. I was reluctant to install stable first, due to often having trouble upgrading, but this one went smoothly. Perhaps that's because I did the upgrade immediately, without running dselect first, unlike my other systems that have gone through multiple upgrades over the years. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems with Sarge netinst and Yaboot
Hi, I've just bought a PowerBook G4 12. I have downloaded the Beta1 of Sarge NetInst for PowerPC (November 9th) and I have got a problem at the beginning of the installation. I enter Open Firmware, and then boot with: boot cd:\\yaboot And then I get: /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:0,yaboot.conf: Unknown or corrupt filesystem Can't open config file Welcome to yaboot version 1.3.10 Enter help to get some basic usage information boot: Enter Please wait, loading kernel... :0,/vmlinux: Unable to open file, Invalid device The ISO image is correct (I have checked the MD5sum) and I've burned it a couple of times with the same results. After trying some things (it was the first time I used yaboot) I've got it working with: boot: cd:0,/install/powermac/vmlinux initrd=/install/powermac/root.bin ramdisk_size=8192 init=/linuxrc Well, it is not working yet, now it boots the kernel but it can't mount the root partition or initrd, it says (after detecting mouse, pci devices, etc ...): VFS: Cannot open root device or 16:01 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 16:01 0Rebooting in 180 seconds.. If I specify root=/dev/ram0 then it says (earlier than without specifying it): cramfs: wrong magic Kernel panic: VFS: Unable to mount root fs on 01:00 ... I've tried several combinations of these options without any good result. Thanks for your help (please, keep me in CC because I'm not subscribed to the lists) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with Sarge netinst and Yaboot
[EMAIL PROTECTED] writes: Hi, I've just bought a PowerBook G4 12. I have downloaded the Beta1 of Sarge NetInst for PowerPC (November 9th) and I have got a problem at the beginning of the installation. I enter Open Firmware, and then boot with: boot cd:\\yaboot And then I get: /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:0,yaboot.conf: Unknown or corrupt filesystem Can't open config file Welcome to yaboot version 1.3.10 Enter help to get some basic usage information boot: Enter Please wait, loading kernel... :0,/vmlinux: Unable to open file, Invalid device The ISO image is correct (I have checked the MD5sum) and I've burned it a couple of times with the same results. After trying some things (it was the first time I used yaboot) I've got it working with: boot: cd:0,/install/powermac/vmlinux initrd=/install/powermac/root.bin ramdisk_size=8192 init=/linuxrc Well, it is not working yet, now it boots the kernel but it can't mount the root partition or initrd, it says (after detecting mouse, pci devices, etc ...): VFS: Cannot open root device or 16:01 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 16:01 0Rebooting in 180 seconds.. If I specify root=/dev/ram0 then it says (earlier than without specifying it): cramfs: wrong magic Kernel panic: VFS: Unable to mount root fs on 01:00 ... I've tried several combinations of these options without any good result. Thanks for your help (please, keep me in CC because I'm not subscribed to the lists) My branch of d-i has the following yaboot.conf: debian-installer/build% cat boot/powerpc/yaboot.conf ## This yaboot.conf is for CD booting only, do not use as reference. ## Debian GNU/Linux PowerPC (woody) # It is important not to have a comma after cd: device=cd: default=install timeout=100 # FIXME: will this be the correct path? message=/install/powermac/boot.msg image=/install/powermac/linux label=install initrd=/install/powermac/root.bin append=devfs=mount,dall initrd-size=8192 read-only # some machines have wonky framebuffer support image=/install/powermac/linux label=install-safe initrd=/install/powermac/root.bin initrd-size=8192 append=video=ofonly devfs=mount,dall read-only You might or might nor need root=/dev/ram. The beta-1 images are done by debian-cd so the yaboot.conf and actual image names and locations might differ but you should be able to compare them. MfG Goswin PS: bugs in the beta-1 yaboot.conf should be filed against debian-cd, not much debian-boot can do about it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re[2]: Enlighten me about jigdo ..
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! MW real image. The issue was not the load on the debian mirrors but on the MW debian iso mirrors that kept the real isos available for rsyncing. This MW rsync ate a lot of cputime. And not to forget: memory usage - I've some experience in rsyncing complete images against another, here at my server and mirror this is a bit of work for the server. If there are some rsyncs running for images this machine runs out of memory and rsyncing only works with choosen blocksize to 8092 (took sometime to find this). So jigdo is just a better way for distributing images, works fine at most of the time and does not produce high load. So thanks Richard for this great tool, even it takes much time to build a file database for my local mirror ;-) Jan - -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (MingW32) Comment: Benutzt PGP! Fragen? [EMAIL PROTECTED] iD8DBQE/uhu1vvmCkIIgH8QRAi63AKCaYwZPu4NCuIFuaxBxHDug6W00PQCgqswz B0RoDSUWFBGtwC79+OTe8I4= =qfv9 - -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (MingW32) Comment: Benutzt PGP! Fragen? [EMAIL PROTECTED] iD8DBQE/uh16vvmCkIIgH8QRAn3xAKCWBiY1NGiueW1+HqSzcYLkqYpIfACfVO1d JnmV6ytrIJEhvExXH02kZpw= =Ax/0 -END PGP SIGNATURE-
Problems with Sarge netinst and Yaboot
Hi, I've just bought a PowerBook G4 12. I have downloaded the Beta1 of Sarge NetInst for PowerPC (November 9th) and I have got a problem at the beginning of the installation. I enter Open Firmware, and then boot with: boot cd:\\yaboot And then I get: /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:0,yaboot.conf: Unknown or corrupt filesystem Can't open config file Welcome to yaboot version 1.3.10 Enter help to get some basic usage information boot: Enter Please wait, loading kernel... :0,/vmlinux: Unable to open file, Invalid device The ISO image is correct (I have checked the MD5sum) and I've burned it a couple of times with the same results. After trying some things (it was the first time I used yaboot) I've got it working with: boot: cd:0,/install/powermac/vmlinux initrd=/install/powermac/root.bin ramdisk_size=8192 init=/linuxrc Well, it is not working yet, now it boots the kernel but it can't mount the root partition or initrd, it says (after detecting mouse, pci devices, etc ...): VFS: Cannot open root device or 16:01 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 16:01 0Rebooting in 180 seconds.. If I specify root=/dev/ram0 then it says (earlier than without specifying it): cramfs: wrong magic Kernel panic: VFS: Unable to mount root fs on 01:00 ... I've tried several combinations of these options without any good result. Thanks for your help (please, keep me in CC because I'm not subscribed to the lists)
Re: Problems with Sarge netinst and Yaboot
[EMAIL PROTECTED] writes: Hi, I've just bought a PowerBook G4 12. I have downloaded the Beta1 of Sarge NetInst for PowerPC (November 9th) and I have got a problem at the beginning of the installation. I enter Open Firmware, and then boot with: boot cd:\\yaboot And then I get: /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]:0,yaboot.conf: Unknown or corrupt filesystem Can't open config file Welcome to yaboot version 1.3.10 Enter help to get some basic usage information boot: Enter Please wait, loading kernel... :0,/vmlinux: Unable to open file, Invalid device The ISO image is correct (I have checked the MD5sum) and I've burned it a couple of times with the same results. After trying some things (it was the first time I used yaboot) I've got it working with: boot: cd:0,/install/powermac/vmlinux initrd=/install/powermac/root.bin ramdisk_size=8192 init=/linuxrc Well, it is not working yet, now it boots the kernel but it can't mount the root partition or initrd, it says (after detecting mouse, pci devices, etc ...): VFS: Cannot open root device or 16:01 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 16:01 0Rebooting in 180 seconds.. If I specify root=/dev/ram0 then it says (earlier than without specifying it): cramfs: wrong magic Kernel panic: VFS: Unable to mount root fs on 01:00 ... I've tried several combinations of these options without any good result. Thanks for your help (please, keep me in CC because I'm not subscribed to the lists) My branch of d-i has the following yaboot.conf: debian-installer/build% cat boot/powerpc/yaboot.conf ## This yaboot.conf is for CD booting only, do not use as reference. ## Debian GNU/Linux PowerPC (woody) # It is important not to have a comma after cd: device=cd: default=install timeout=100 # FIXME: will this be the correct path? message=/install/powermac/boot.msg image=/install/powermac/linux label=install initrd=/install/powermac/root.bin append=devfs=mount,dall initrd-size=8192 read-only # some machines have wonky framebuffer support image=/install/powermac/linux label=install-safe initrd=/install/powermac/root.bin initrd-size=8192 append=video=ofonly devfs=mount,dall read-only You might or might nor need root=/dev/ram. The beta-1 images are done by debian-cd so the yaboot.conf and actual image names and locations might differ but you should be able to compare them. MfG Goswin PS: bugs in the beta-1 yaboot.conf should be filed against debian-cd, not much debian-boot can do about it
Re: Installation der offiziellen testing Distribution
At the time I wrote it, this was true for all testing/unstable CDs. Does anybody know whether the CDs became installable again with the old installer later? I don't know, but today I tried to install testing using jigdo (the jigdo file that's referenced from the Debian web page, I think it's from the .hu site) and got an error configuring the keyboard. I don't remember the error message, but I did a web search and found that the error was reported months ago. Did anyone not have that problem? I ignored the error, got a lot more errors, then gave up and installed stable and upgraded. Sorry I don't remember more detail, but I can say that I have been unable to install testing by using jigo, downloading a CD image from the .hu site, or using netinstall. I was reluctant to install stable first, due to often having trouble upgrading, but this one went smoothly. Perhaps that's because I did the upgrade immediately, without running dselect first, unlike my other systems that have gone through multiple upgrades over the years.
