Re: Installation bug (4.0-19991227-CURRENT)
In message <[EMAIL PROTECTED]>, Forrest Aldrich writes : >Did a test install against the latest snapshot. > >The network configuration comes up with "dc0" (we have de0), this >"works" in that we were able to perform the network install (so it >must be a typo somewhere). No, dc0 is the new and improved driver for the newer tulip chips. >However, it results in multiple entries in /etc/rc.conf (three, >total), which have to be removed before the network will come up >correctly after rebooting. > >NB, this was an install over a previous 4.0 instance, so there's >the possibility that the rc.conf file was edited rather than written >over -- though I would doubt that (?). That is probably what happened here. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installation bug (4.0-19991227-CURRENT)
On Mon, Dec 27, 1999 at 02:14:29PM -0500, Forrest Aldrich wrote: > Did a test install against the latest snapshot. > > The network configuration comes up with "dc0" (we have de0), > this "works" in that we were able to perform the network > install (so it must be a typo somewhere). If you had been following -current, you would know that Bill Paul has written the dc driver, that works with much of the same cards that the de driver does. If both the de and dc driver are available, the dc driver wins. > However, it results in multiple entries in /etc/rc.conf (three, > total), which have to be removed before the network will come > up correctly after rebooting. > > NB, this was an install over a previous 4.0 instance, so there's > the possibility that the rc.conf file was edited rather than written > over -- though I would doubt that (?). That is probably the case ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk Work:Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek@ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Installation bug (4.0-19991227-CURRENT)
The 'de' driver has been obsoleted for the 21143 part by the 'dc' driver. You should be using 'dc' for those devices that it supports. > Did a test install against the latest snapshot. > > The network configuration comes up with "dc0" (we have de0), this "works" in that we >were able to perform the network install (so it must be a typo somewhere). > > However, it results in multiple entries in /etc/rc.conf (three, total), which have >to be removed before the network will come up correctly after rebooting. > > NB, this was an install over a previous 4.0 instance, so there's the possibility >that the rc.conf file was edited rather than written over -- though I would doubt >that (?). > > FYI. > > > > _F > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Installation bug (4.0-19991227-CURRENT)
Did a test install against the latest snapshot. The network configuration comes up with "dc0" (we have de0), this "works" in that we were able to perform the network install (so it must be a typo somewhere). However, it results in multiple entries in /etc/rc.conf (three, total), which have to be removed before the network will come up correctly after rebooting. NB, this was an install over a previous 4.0 instance, so there's the possibility that the rc.conf file was edited rather than written over -- though I would doubt that (?). FYI. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
