notes/bugs on recent alpha install
Here are a couple of things I noticed while installing with boot floppies from a few days ago: - I tried accessing the base distribution via NFS and got a "Malformed release file ..." error. I was able to determine that the problem was that the file wasn't readable. It would be really nice if there were a more helpful error message. - I made the file above readable, but I still kept getting the same error message. It's almost as if this error is "sticky"--once you get it you're stuck. (see below) - I tried, in a different attempt, to grab the base distribution via the FTP method. This also failed with the "Malformed release file ..." error after a few seconds (perhaps due to a network problem?). When I repeated the attempt, I got the same error message, but immediately, as if the network weren't even being checked. At this point, I removed a file that looked like state, named 'debootstrap.invalid_dists_woody_Release'. After this, I tried again, as above, and the attempt succeeded. It almost seems like something's not being cleaned up correctly when an attempt fails. - There is text on one of the dialogs that says "alt-F4 to debug". It seems like it should say alt-F3, as that's where the bootstrap output is. F4 has kernel messages. - I also had the busybox wget vs ftp problem documented elsewhere. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#124107: boot-floppies: needs rebuild upon busybox bug #124068 (blocks ftp.us.debian.org) fix
Package: boot-floppies Version: N/A; reported 2001-12-15 Severity: important As soon as a fix for http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=124068 is in, boot-floppies needs a rebuild, as the access method ftp://ftp.us.debian.org is blocked by this bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#123782: acknowledged by developer (Re: Bug#123782: boot-floppies: dbootstrap's wget should use passive ftp)
[EMAIL PROTECTED] (Debian Bug Tracking System) writes: > Anyhow, it's irrelevant. Since busybox wget doens't support this > argument, the user's request to use this argument is hereby denied. > :) > > Bug submitter, if busybox wget is not using ftp in the right way, > please file a bug on busybox, not on the boot-floppies. Thanks. Turns out that busybox wget *does* use passive ftp by default, which it should, but that there's a bug in the way it's doing name lookups. (The problem is that it does a second DNS lookup for the PASV connection, which won't necessarily return the same IP for a round-robin DNS situation like ftp.us.debian.org, so the download fails.) A workaround is to use a specific IP address instead of the hostname. I'll file against busybox. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#123782: boot-floppies: dbootstrap's wget should use passive ftp
Package: boot-floppies Version: 3.0.17; reported 2001-12-12 Severity: important If I'm reading net-fetch.c correctly, its call to 'wget' doesn't use passive ftp. This will fail for people behind many firewalls. Shouldn't it use --passive-ftp by default? AFAIK, turning it on should (virtually) never cause a problem, and will be a lot better on balance. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
alpha boot disk report, plus q: where is base tarball?
I tried installing on a DS10 just now with the latest testing boot floppies. It went fine up to trying to access the archive via ftp. The machine is behind a NAT firewall that blocks port 80 access. There's a web proxy, but it requires authentication, which the boot floppies seem not to support. I tried ftp access, but I immediately get the "corrupted Packages (Release?)" message, which I gather means a network error. I can ping the ftp server, but I'm not sure how to tell whether the ftp is failing or whether it's trying to access in active mode, which would fail through the firewall. It'd be nice if a specific explanation for the failure was given. Any ideas? Also, in the past I would have pulled down the base tarball and grabbed it locally (e.g., via NFS). The base tarball seems no longer to exist, though (I guess because of package pools). How can I get the same effect under the new regime? That is, how do I pull down the base packages only? I can't seem to find this documented anywhere. Any hints appreciated, Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#67722: me, too -- PCMCIA/network conflict (cf #66284)
Adam Di Carlo <[EMAIL PROTECTED]> writes: > Could you do 'depmod -a' on a newly installed system? I did this just now and there was no output. (The system has been rebooted and some packages added since I installed it.) > Could you please determine exactly which version you are using? I > expect it's 2.2.20. 'uname -a' and 'ls /lib/modules' would help as > well. # uname -a Linux mathpup 2.2.18pre21 #1 Sat Nov 18 18:47:15 EST 2000 i486 unknown # ls /lib/modules 2.2.18pre21 > > At least part of the problem seems to be that doing a '/etc/init.d/pcmcia > > stop' doesn't work flawlessly. That script is trying to remove modules in a > > way that fails. That problem combined with some module insertion or removal > > that dbootstrap is trying to do causes failure. > > We need exact output of that failure. It might suffice to send to > this bug the /var/log/installer.log that was created during > installation, after you've rebooted into your system. I've appended installer.log below (ignore the dates). If needed, I'm willing to reinstall this system to gather data, but I need to know quickly, as I'm putting this laptop into service very soon. --Mike Dec 23 08:39:14 (none) syslogd started: BusyBox v0.43 (2000.11.30-14:58+) Dec 23 08:39:47 (none) user.info dbootstrap[108]: Dec 23 08:40:42 (none) user.info dbootstrap[108]: turning off swap on /dev/hda2 so we can re-partition Dec 23 08:40:47 (none) user.info dbootstrap[108]: running cfdisk to partition /dev/hda Dec 23 08:43:21 (none) user.info dbootstrap[108]: partition program returned 0 Dec 23 08:43:49 (none) user.info dbootstrap[108]: formatting partition /dev/hda3 as ext2 for kernel 2.2 or better Dec 23 08:44:15 (none) user.info dbootstrap[108]: mounting /dev/hda3 at /target Dec 23 08:44:30 (none) user.info dbootstrap[108]: formatting partition /dev/hda1 as ext2 for kernel 2.2 or better Dec 23 08:44:44 (none) user.info dbootstrap[108]: mounting /dev/hda1 at /target/boot Dec 23 08:44:53 (none) user.info dbootstrap[108]: installing kernel and modules from /dev/fd0 Dec 23 08:46:09 (none) user.err dbootstrap[108]: That doesn't look like the right floppy. Dec 23 09:04:38 (none) user.info dbootstrap[108]: kernel and modules install successful Dec 23 09:04:38 (none) user.info dbootstrap[108]: moving away /lib/modules to /lib/modules.old Dec 23 09:04:39 (none) user.info dbootstrap[108]: making /lib/modules a link to /target/lib/modules Dec 23 09:07:46 (none) user.info dbootstrap[108]: No /var/run/cardmgr.pid, cardmgr not needing to be stopped Dec 23 09:07:47 (none) user.info dbootstrap[108]: rmmod: module ds is not loaded Dec 23 09:07:47 (none) user.info dbootstrap[108]: rmmod: module i82365 is not loaded Dec 23 09:07:47 (none) user.info dbootstrap[108]: rmmod: module pcmcia_core is not loaded Dec 23 09:07:48 (none) user.info dbootstrap[108]: Starting 'cardmgr ' Dec 23 09:07:49 (none) daemon.info cardmgr[206]: starting, version is 3.1.22 Dec 23 09:07:49 (none) daemon.info cardmgr[206]: watching 1 sockets Dec 23 09:11:04 (none) daemon.info cardmgr[206]: initializing socket 0 Dec 23 09:11:04 (none) daemon.info cardmgr[206]: socket 0: Linksys Ethernet Dec 23 09:11:04 (none) daemon.info cardmgr[206]: executing: 'modprobe 8390' Dec 23 09:11:05 (none) daemon.info cardmgr[206]: executing: 'modprobe pcnet_cs' Dec 23 09:11:06 (none) daemon.info cardmgr[206]: executing: './network start eth0' Dec 23 09:11:07 (none) daemon.info cardmgr[206]: + /var/lib/misc/pcmcia-scheme: No such file or directory Dec 23 09:14:14 (none) user.info dbootstrap[108]: configured modules; modconf returned 25 Dec 23 09:24:17 (none) user.info dbootstrap[108]: Stopping cardmgr Dec 23 09:24:17 (none) daemon.info cardmgr[206]: executing: './network check eth0' Dec 23 09:24:18 (none) daemon.info cardmgr[206]: + /var/lib/misc/pcmcia-scheme: No such file or directory Dec 23 09:24:18 (none) daemon.info cardmgr[206]: shutting down socket 0 Dec 23 09:24:18 (none) daemon.info cardmgr[206]: executing: './network stop eth0' Dec 23 09:24:19 (none) daemon.info cardmgr[206]: + /var/lib/misc/pcmcia-scheme: No such file or directory Dec 23 09:24:19 (none) daemon.info cardmgr[206]: + /etc/resolv.conf: No such file or directory Dec 23 09:24:20 (none) daemon.info cardmgr[206]: + sed: can't read /etc/resolv.conf: No such file or directory Dec 23 09:24:20 (none) daemon.info cardmgr[206]: executing: 'modprobe -r pcnet_cs' Dec 23 09:24:20 (none) daemon.info cardmgr[206]: executing: 'modprobe -r 8390' Dec 23 09:24:21 (none) user.info dbootstrap[108]: ds: Device or resource busy Dec 23 09:24:21 (none) user.info dbootstrap[108]: i82365: Device or resource busy Dec 23 09:24:21 (none) user.info dbootstrap[108]: pcmcia_core: Device or resource busy Dec 23 09:24:22 (none) daemon.err insmod: insmod: a module named pcmcia_core already exists Dec 23 09:24:22 (none) user.err dbootstrap[108]: An error encountered while trying to load and configure the PCMCIA modules. Dec 23 09:24:22 (none) daemo
Bug#67722: me, too -- PCMCIA/network conflict (cf #66284)
I'm not the original submitter, but I also seem to have just tripped over this bug. I was using the vanilla floppies downloaded through the links in the instructions. I don't know the exact version, but I grabbed them within the last week or so. At least part of the problem seems to be that doing a '/etc/init.d/pcmcia stop' doesn't work flawlessly. That script is trying to remove modules in a way that fails. That problem combined with some module insertion or removal that dbootstrap is trying to do causes failure. In particular, the initial "configure PCMCIA" step seem to work fine. The the "configure network" steps ends with a failure, although the information entered seems to be used/remembered correctly. If I then redo "configure PCMCIA", networking is then up and working. If I then redo "configure network", it breaks networking again. --Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#82024: install doc typo
Package: boot-floppies There's a minor typo in the install doc (web page, etc.) At the end of the section "Installing from a Linux Partition", the direction is to skip down to "Booting the Installation System, Chapter 6", which is the current chapter. --Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
