--- Begin Message ---
- To: Jim Westveer <jwest@netnw.com>, joey@debian.org
- Cc: Adam Di Carlo <adam@onshore.com>
- Subject: Re: FW: dpkg_multicd_0.13 and boot-disks 2.1.6 still broken..
- From: Martin Schulze <joey@tapiola.Infodrom.North.DE>
- Date: Sun, 31 Jan 1999 17:27:23 +0100
- Message-id: <19990131172723.B23815@tapiola.infodrom.north.de>
- Reply-to: Martin Schulze <joey@infodrom.north.de>
- In-reply-to: <000001be4d35$4527e340$02c5b4d1@fysm.netnw.com>; from Jim Westveer on Sun, Jan 31, 1999 at 08:18:00AM -0800
- References: <000001be4d35$4527e340$02c5b4d1@fysm.netnw.com>
Jim Westveer wrote: > FYI...... > > > -----Original Message----- > From: Jim Westveer [mailto:jwest@netnw.com] > Sent: Saturday, January 30, 1999 9:02 PM > To: debian-cd@lists.debian.org > Subject: dpkg_multicd_0.13 and boot-disks 2.1.6 still broken.. > > > Let me preface this with "I may have done something wrong" > > --------- > > I downloaded the boot-disks 2.1.6 from Incomming (on medco.net) > > dpkg_multicd_0.13 was already updated earlier this week... > > So, I burned a set of release disks (disk 1 & 2) > > ------ > > I booted from the disk, and the initial install went well.... > > I rebooted to the kernel now on the hard disk.... > > Observations: > > 1. The defaults [Y/n] Create user account and Remove PCMCIA packages > still default to NO. > 2. I selected the multi-cd install method. > 3. I selected (with Y) one of the pre-selected packages..in this case > the std-server. and the first pass of dselect ended with errors > on apache and ph3...so I restarted (I)nstall...and received > the message: > > Wrong Disk. I need "Debian GNU/Linux slink" but I found > "Debian GNU/Linux slink (2.1) 1/5 main binary section 1 SAM1990130 > Please change the disks and press enter > > ...hummmm... > me thinks we be calling the same things > by different names ;-) Can you please check the source of dpkg-multicd? I remember that I removed the restriction that only the first two words as cd identifier were recognized. I wonder why I received the same report from another person already... > 4. When I checked the /dev/loop? none were found...not that it > may matter much, I think dpkg-multicd_0.13 is not using them > now. It is, but only if one uses /foo/bar/cd.img which isn't a block device. In that case it would try to mount it via loopback. > 5. I could install a rudimentary system by selecting the > old "cdrom" installation method... > > This information may be incorrect if I goofed up the download of > the new boot-disks....although a quick glance at the CDROM shows > the correct (new) files. > > Anyhoooo....thanks and goodnight....off to drink beer with my woman. > > Jim > -------------------------------------------------- > So far, no one has been killed in a computer crash. > -------------------------------------------------- > Jim Westveer ------------- jwest@netnw.com > phone -------------------- 425-392-0141 > http://www.netnw.com > http://www.linux-cd.com/gif/box-debian.gif > -------------------------------------------------- Regards, Joey -- Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald E. Knuth
--- End Message ---