Has there been a change in Policy or configuration to prevent using MUUG web/ftp site for Fedora updates? I started to get error messages a week ago when trying to use redhat-update (reconfig'd to point to MUUG site as per newletter).
Brock
Brock Wolfe ______________________________________ Expect problems and eat them for breakfast. -- Alfred A. Montapert (American Author) ______________________________________
According to Brock Wolfe:
Has there been a change in Policy or configuration to prevent using MUUG web/ftp site for Fedora updates? I started to get error messages a week ago when trying to use redhat-update (reconfig'd to point to MUUG site as per newletter).
Gilbert told me there were problems with a couple of the mirror disks, causing the whole system to hang after the upgrade to FC3 on the server. They've been taken offline until he can get to the bottom of the problem or replace them. For now, you should probably use the U. of Calgary mirror.
http://mirror.cpsc.ucalgary.ca/mirror/fedora/linux/core/
I was trying to do a fresh install of Debian Sarge today on a HP NetServer LH3 (dual Pentium II 450 MHz). The install started okay, except that it seemed to be unable to correctly identify the network card. It appeared to load the "e100" driver, but I think the "eepro100" is the correct one. At any rate, it was unable to get a lease from our DHCP server no matter what I did. No network connectivity.
Here's the catch: Debian Sarge lets you install a 2.4 or 2.6 kernel. When I go with the 2.4 kernel, it works! When I start the install with "linux26" to select the 2.6 kernel, I get the above behaviour.
Is there any way to get the Debian 2.6 install to detect my NIC properly? Or should I just give up and stick with 2.4?
Kevin
I was trying to do a fresh install of Debian Sarge today on a HP NetServer LH3 (dual Pentium II 450 MHz). The install started okay, except that it seemed to be unable to correctly identify the network card. It appeared to load the "e100" driver, but I think the "eepro100" is the correct one. At any rate, it was unable to get a lease from our DHCP server no matter what I did. No network connectivity.
Here's the catch: Debian Sarge lets you install a 2.4 or 2.6 kernel. When I go with the 2.4 kernel, it works! When I start the install with "linux26" to select the 2.6 kernel, I get the above behaviour.
Is there any way to get the Debian 2.6 install to detect my NIC properly? Or should I just give up and stick with 2.4?
Hi Kevin,
I tend not to use the distro kernels, so that may be an option for you as well. You could just use the 2.4 to get going, then rebuild a custom 2.6 kernel at your leisure.
Cheers, Tim
-
Brock Wolfe -
Gilles Detillieux -
Kevin McGregor -
Tim Lavoie