Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 498126 - Ethernet
Summary: Ethernet
Status: RESOLVED WORKSFORME
Alias: None
Product: [OLD] Docs on www.gentoo.org
Classification: Unclassified
Component: Installation Handbook (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Docs Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-15 05:09 UTC by James Horton
Modified: 2014-01-16 05:27 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Horton 2014-01-15 05:09:04 UTC
Section 3 talks all about eth0 in the configuration of the ethernet,
which is fine and matches the minimal iso install disc. But we are 
now installing UDEV 2.x, which reassigns the the eth0 name to something
like enp5s0. So after reboot the ethernet does not work and much be reconfigured
manually to get the sytem up. So a section on setting up the udev named
eithernet (dmesg discovery or ifconfig) including the rc default portion
is needed.  It would be best to patch the minimal iso install to use
the current udev name for the interface and not assume it's going to
be eth0. Or show folks in the install documentation how to set/change the
ethernet interface name to eth0, dispite newer version of UDEV.
Comment 1 Ben Kohler gentoo-dev 2014-01-15 15:03:22 UTC
If you're using a recent gentoo minimal install cd, it already has the new udev with new naming.  It has been this way for a while.  How old is your install cd where you still see eth0?
Comment 2 James Horton 2014-01-15 17:01:21 UTC
The installation CD is OK, including the new udev naming scheme. I'm talking about the handbook, needs to use the udev assigned name to the ethernet interface, not eth0. Were talking about Section 3 of the handbook.
Comment 3 Ben Kohler gentoo-dev 2014-01-15 17:02:36 UTC
From Section 3:

"The interface name on your system can be quite different from eth0. Recent installation media might show regular network interfaces names like eno0, ens1 or enp5s0. Just seek the interface in the ifconfig output that has an IP address related to your local network."
Comment 4 James Horton 2014-01-15 17:50:04 UTC
(In reply to Ben Kohler from comment #3)
> From Section 3:
> 
> "The interface name on your system can be quite different from eth0. Recent
> installation media might show regular network interfaces names like eno0,
> ens1 or enp5s0. Just seek the interface in the ifconfig output that has an
> IP address related to your local network."

OK. Now put those sorts of comments into the handbook. I see not discussion
on the ethernet naming scheme, either udev defined or the traditional
eth0 and how udev WILL change that name, eventually. We're talking about
what is in the Handbook. I have no installation issues.

Not to mention how to override udev if one has preferential names
or multiple ethernet interfaces, with udev/systemd in the mix.

It's just a suggestion to make the handbook better, act on it
or close the bug. I'm done.
Comment 5 Ben Kohler gentoo-dev 2014-01-15 17:53:21 UTC
My above quote was from the current english amd64 handbook, maybe you are looking at a different one that hasn't been updated?  I'm not trying to attack you here, I'm not clear as to where there is an actual problem.

http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?full=1#book_part1_chap3
Comment 6 nm (RETIRED) gentoo-dev 2014-01-16 05:27:33 UTC
(In reply to Ben Kohler from comment #5)
> My above quote was from the current english amd64 handbook, maybe you are
> looking at a different one that hasn't been updated?  I'm not trying to
> attack you here, I'm not clear as to where there is an actual problem.
> 
> http://www.gentoo.org/doc/en/handbook/handbook-amd64.
> xml?full=1#book_part1_chap3

ben is correct; the handbooks all have this text already.