Re: Bug#121177: boot-floppies: can't install dpkg
In message 20011127015622.B209@Obsession, Chris Tillman writes: 8MB RAM is not be enough for woody, it's a 12MB minimum according to the install manual for i386. Have you tried the potato installation? I guess it would be nice if dbootstrap caught this situation early and told the user that they need to visit the hardware store. Anyone know a remotely portable method of checking the amount of RAM? I suppose you could parse the MemTotal line out of /proc/meminfo fairly easily. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#121177: boot-floppies: can't install dpkg
#include hallo.h Philip Blundell wrote on Tue Nov 27, 2001 um 07:15:16PM: I guess it would be nice if dbootstrap caught this situation early and told the You get a warning if you did not create some swap space. What additional things do you wish? Something like Continue? - Yes - Sorry Dave, I cannot let you do this? user that they need to visit the hardware store. Anyone know a remotely portable method of checking the amount of RAM? I suppose you could parse the MemTotal line out of /proc/meminfo fairly easily. Yes, could be done. I even imagine to ask about creating a swap FILE, let the user input the size and make one on the mounted root partition. But no spare time for hacking yet. Gruss/Regards, Eduard. -- Der Wahnsinn hat Methode! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#121177: boot-floppies: can't install dpkg
In message [EMAIL PROTECTED], Eduard Bloch writes: #include hallo.h Philip Blundell wrote on Tue Nov 27, 2001 um 07:15:16PM: I guess it would be nice if dbootstrap caught this situation early and told the You get a warning if you did not create some swap space. What additional things do you wish? Something like Continue? - Yes - Sorry Dave, I cannot let you do this? I was thinking more along the lines of a warning like Your computer only has 8MB of RAM, but a minimum of 12MB is recommended for Debian 3.0. Consider fitting more memory, or installing an older version of Debian instead. It does seem a bit unfriendly if installs just blow up in some mysterious fashion on machines where potato didn't have a problem. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#121177: boot-floppies: can't install dpkg
Package: boot-floppies Version: 3.0.17-2001-11-18 Severity: critical trying to install debian woody on my test machine (386DX-40, 8mb ram) results in this error (on tty4): -- snip -- Preparing to replace dpkg 1.9.18 (using .../archives/dpkg_1.9.18_i386.deb) ... Unpacking replacement dpkg ... dpkg-deb: subprocess paste killed by signal (Broken pipe) dpkg: error processing /var/cache/apt/archives/dpkg_1.9.18_i386.deb (--install): subprocess dpkg-deb --fsys-tarfile returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/dpkg_1.9.18_i386.deb -- snip -- the installation system reports: Failure trying to run: chroot /target dpkg then: debootstrap exited with an error (return value 1) at which point it takes me back to the b-f menu where i can try to install the base system again. i'm installing on to a 4gb ide drive; it's partitioned with a 50mb /boot, a 16mb swap partition, and the rest on the root. i'm installing over the network with a 3c509 isa board, from bigfoot.eecs.umich.edu. i'm connected to the 'net via dsl. this bug may actually belong to dpkg. incidentially, it would be _great_ if the .debs that were downloaded were used if i tried the installation again; i got the error once, then tried it again. the installer downloaded all the packages _again_. this is not a Nice Thing(tm) to do, considering that it takes well over an hour to download verify all those packages on such a slow system. -- System Information Debian Release: testing/unstable Kernel Version: Linux proton 2.2.19-udma100-ext3 #1 SMP Fri Sep 28 22:56:58 CEST 2001 i686 unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
