Re: New netinst iso
Am 2005-02-21 11:42:39, schrieb Dmitry Derjavin: Just to be clear: 1. If installed from sid-amd64-netinst.iso (apt is pointed to testing) -- is it sarge or sid? The curent amd64 is SID, SARGE, TESTION and UNSTABLE After the release of SARGE (without amd64) the amd64 Architekture has officially TESTING/ETCH and UNSTABLE/SID but the current debian-installer will point to SARGE/STABLE which IS a symling to TESTING/ETCH. 2. If I installed the system from sid-amd64-netinst.iso and want to use sarge -- do I need to downgrade libc6 or do something else? NO, it is curently the same. 3. What is the difference between installations from sarge and sid netinst iso. Nothing, it is curently the same for amd64. Thanks! Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: New netinst iso
Dmitry Derjavin [EMAIL PROTECTED] writes: On Sat, Feb 19 2005 at 19:18, Goswin von Brederlow wrote: D-I defaults to use sarge and complains if not found. For that reason even the sid CDs use sarge. I also added links for testing, sid, unstable to cover all bases. Just to be clear: 1. If installed from sid-amd64-netinst.iso (apt is pointed to testing) -- is it sarge or sid? The sid netinst contains sid base debs. Anything going beyond that depends on where you pointed apt to. By default D-I will put testing in your sources.list so if you pointed apt to /debian-pure64/ you get sarge, if you pointed it to /pure64/ you get sid. 2. If I installed the system from sid-amd64-netinst.iso and want to use sarge -- do I need to downgrade libc6 or do something else? Depends on what libc6 you have, which depends on the date you've gotten the image. You do not have to downgrade libc6 for any reason but that libc6-dev depends on an equal version of libc6. So when installing libc6-dev you might have to downgrade libc6 to match, apt-get will tell you. 3. What is the difference between installations from sarge and sid netinst iso. Hmm, good question. Mount them both and compare. Doing a quick diff on the Packages file I see 60 differences in versions. Thanks! PS: Thanks for uploading md5sums. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New netinst iso
the owner [EMAIL PROTECTED] writes: Goswin- I apologize for the mixup: Oops: That was actually an error reading the Release file not Packages file as previously here: The 18 Feb sarge-amd64-netinst.iso Installer error message said: error reading /cdrom/dists//Release I am fairly sure that would be the same as this showing the same type of failure: [EMAIL PROTECTED]:~ cat /mnt/iso9660/dists/sarge/Release attempt to access beyond end of device loop0: rw=0, want=260716, limit=224649 Buffer I/O error on device loop0, logical block 65178 That was more important. It indicates your iso is to small. I took the 18 Feb image downloaded from alioth and mounted that to loop iso9660 and found the above. That must be the same error as during the CDROM run of the Installer. Here is the 18 Feb image that caused the problem: 2cb2cc2fe9544547dac49d0b8a26dd31 sarge-amd64-netinst.iso [EMAIL PROTECTED]:~/archive/install-images$ cat sarge-amd64-netinst.iso.md5sum 530f958e147737a3c9fc372a36a3c233 sarge-amd64-netinst.iso And this prooves it is corrupt. Sorry, this is my fault I think. The file on Alioth is 18MB short of what it should be. Must have missed rsync dying on the upload. I should add an md5sum check after the upload to my script. sarge-amd64-netinst.iso 118516672 88% 15.46kB/s0:16:46 Try again in a few minutes. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New netinst iso
On Sat, Feb 19 2005 at 19:18, Goswin von Brederlow wrote: D-I defaults to use sarge and complains if not found. For that reason even the sid CDs use sarge. I also added links for testing, sid, unstable to cover all bases. Just to be clear: 1. If installed from sid-amd64-netinst.iso (apt is pointed to testing) -- is it sarge or sid? 2. If I installed the system from sid-amd64-netinst.iso and want to use sarge -- do I need to downgrade libc6 or do something else? 3. What is the difference between installations from sarge and sid netinst iso. Thanks! PS: Thanks for uploading md5sums. -- ~dd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New netinst iso
the owner [EMAIL PROTECTED] writes: Goswin wrote: Hi, the new sid netinst image is uploaded and moved into place. The sarge one is rsyncing with yesterdays updates. Sorry it took so long, I nearly forgot to downgrade the libc6 and base-files to unpatched versions and that took more doing than I expected. Enjoy. Goswin I burned the 18 feb sarge-amd64-netinst.iso to a CD. When booting the CD there was a dialog saying error reading the CDROM after the hardware was detected. The vt messages said 'error retrieving file: no such file or directory: /cdrom/dists//Packages. /cdrom/dists//Packages or /cdrom/dists/sarge/main/debian-installer/binary-amd64/Packages? I mounted to iso9660 and looked inside the CDROM and had no problems. The Packages file looks garbled inside the new sarge iso when easy to read in last weeks sid iso. The Packages file was in the /dists/sarge directory on both netinst except there was no error last week. D-I defaults to use sarge and complains if not found. For that reason even the sid CDs use sarge. I also added links for testing, sid, unstable to cover all bases. I think the Installer can't read the Packages file. The 18 feb sarge-amd64-netinst.iso seems broken. If cat can't read it then it is broken. I rebuild it and checked the packages files. Only change should be the D-I image being rebuild overnight. d2c37750d57c7bb315998c97b05ca6fc sid-amd64-netinst.iso MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: New netinst iso
Goswin- I apologize for the mixup: Oops: That was actually an error reading the Release file not Packages file as previously here: The 18 Feb sarge-amd64-netinst.iso Installer error message said: error reading /cdrom/dists//Release I am fairly sure that would be the same as this showing the same type of failure: [EMAIL PROTECTED]:~ cat /mnt/iso9660/dists/sarge/Release attempt to access beyond end of device loop0: rw=0, want=260716, limit=224649 Buffer I/O error on device loop0, logical block 65178 [EMAIL PROTECTED]:~ ls -al /mnt/iso9660/dists/sarge total 7 drwxr-sr-x 3 theme theme 2048 2005-02-18 13:02 . drwxr-sr-x 3 theme theme 2048 2005-02-18 13:02 .. drwxr-sr-x 4 theme theme 2048 2005-02-18 13:02 main -rw-r--r-- 1 theme theme 545 2005-02-18 13:02 Release [EMAIL PROTECTED]:~ I took the 18 Feb image downloaded from alioth and mounted that to loop iso9660 and found the above. That must be the same error as during the CDROM run of the Installer. Here is the 18 Feb image that caused the problem: 2cb2cc2fe9544547dac49d0b8a26dd31 sarge-amd64-netinst.iso I really apologize for writing Packages file when I should have written Release file. . must sleep [EMAIL PROTECTED] -- AMD Athlon64 @2.4Ghz Corsair TwinX1024-3200XL @480Mhz DDR ASUS A8V Deluxe Pro ASUS Radeon A9250Ge/Td/256 Creative SB Live WD Raptor SATA Maxtor PATA IBM/Okidata Color PostScript3 Lexmark Mono PostScript2 Debian GNU/Linux debian-amd64/pure64 sid Kernel 2.6.10 XFree86 4.3.0 Xorg X11R6.8.2 1.5 Mb DSL -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New netinst iso
Hi, the new sid netinst image is uploaded and moved into place. The sarge one is rsyncing with yesterdays updates. Sorry it took so long, I nearly forgot to downgrade the libc6 and base-files to unpatched versions and that took more doing than I expected. Enjoy. Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New netinst iso
Goswin wrote: Hi, the new sid netinst image is uploaded and moved into place. The sarge one is rsyncing with yesterdays updates. Sorry it took so long, I nearly forgot to downgrade the libc6 and base-files to unpatched versions and that took more doing than I expected. Enjoy. Goswin I burned the 18 feb sarge-amd64-netinst.iso to a CD. When booting the CD there was a dialog saying error reading the CDROM after the hardware was detected. The vt messages said 'error retrieving file: no such file or directory: /cdrom/dists//Packages. I mounted to iso9660 and looked inside the CDROM and had no problems. The Packages file looks garbled inside the new sarge iso when easy to read in last weeks sid iso. The Packages file was in the /dists/sarge directory on both netinst except there was no error last week. I think the Installer can't read the Packages file. The 18 feb sarge-amd64-netinst.iso seems broken. [EMAIL PROTECTED] --- AMD Athlon64 @2.4Ghz Corsair TwinX1024-3200XL @480Mhz DDR ASUS A8V Deluxe Pro ASUS Radeon A9250Ge/Td/256 Creative SB Live WD Raptor SATA Maxtor PATA IBM/Okidata Color PostScript3 Lexmark Mono PostScript2 Debian GNU/Linux debian-amd64/pure64 sid Kernel 2.6.10 XFree86 4.3.0 Xorg X11R6.8.2 1.5 Mb DSL -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New netinst iso
Oops: That was actually an error reading the Release file not Packages file as previously here: Goswin wrote: Hi, the new sid netinst image is uploaded and moved into place. The sarge one is rsyncing with yesterdays updates. Sorry it took so long, I nearly forgot to downgrade the libc6 and base-files to unpatched versions and that took more doing than I expected. Enjoy. Goswin I burned the 18 feb sarge-amd64-netinst.iso to a CD. When booting the CD there was a dialog saying error reading the CDROM after the hardware was detected. The vt messages said 'error retrieving file: no such file or directory: /cdrom/dists//Packages. I mounted to iso9660 and looked inside the CDROM and had no problems. The Packages file looks garbled inside the new sarge iso when easy to read in last weeks sid iso. The Packages file was in the /dists/sarge directory on both netinst except there was no error last week. I think the Installer can't read the Packages file. The 18 feb sarge-amd64-netinst.iso seems broken. [EMAIL PROTECTED] -- AMD Athlon64 @2.4Ghz Corsair TwinX1024-3200XL @480Mhz DDR ASUS A8V Deluxe Pro ASUS Radeon A9250Ge/Td/256 Creative SB Live WD Raptor SATA Maxtor PATA IBM/Okidata Color PostScript3 Lexmark Mono PostScript2 Debian GNU/Linux debian-amd64/pure64 sid Kernel 2.6.10 XFree86 4.3.0 Xorg X11R6.8.2 1.5 Mb DSL -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
