*2: After the installation and reboot, the two network adaptors were
detected in the opposite order, so that the wired card (that was eth0
during install) was now eth1, and the wireless card (that was eth1 during
install) was now eth0. This problem was easy to fix with appropriate
entries in /etc/
Package: installation-reports
INSTALL REPORT
Debian-installer-version:
http://people.debian.org/~manty/testing/netinst/i386/20040107/
uname -a: Linux feathers 2.4.22-1-386 #9 Sat Oct 4 14:30:39 EST 2003 i686
GNU/Linux
Date: Jan. 7, 2003, 18:00 EST
Method: Burned and booted i386 netinst iso; remai
Quoting Falk Hueffner <[EMAIL PROTECTED]>:
> That's really good news. I couldn't get bootp to work, so I couldn't
> test it. There were some suspicious hacks in the previous version...
Bootp is a lot easier to get going using a dhcp server rather than a bootp
server. Much better log messages.
I have used the boot floppy images from
ftp://134.2.15.134/boot-floppies/disks-alpha/ to attempt an install from scratch
on a Bret (AlphaStation 500/500).
The good news? bootp/tftp boot works great! In SRM, you need to select bootp
via console variable ('set ewa0_protocol bootp' or somethi
4 matches
Mail list logo
