On 14.9.2014 22:42, Alan Feuerbacher wrote:
On 9/14/2014 2:40 PM, Armin K. wrote:
On 14.9.2014 20:20, Alan Feuerbacher wrote:
Having gotten my systemd booted up, I found that networking is not
working. It looks to me like it sort of starts, with these messages:
systemctl start dhclient@eth0
Eventually this came back with:
A dependency job for [email protected] failed. See 'journalctl -xn'
for details.
This means that your interface isn't called eth0. Under systemd, it has
a rather odd name and that's mentioned under LFS's Configuring Network
page. Examine "ip l" to see what your interface name is as I highly
doubt that it's eth0. That needs to be run from a booted system.
Ok, that worked. My interface name turned out to be enp3s0.
I'll admit that I was a bit confused by the instructions in the LFS and
BLFS books.
In the instructions in the LFS book for "7.2. General Network
Configuration" there is the Note:
"Udev may assign network card interface names based on system physical
characteristics such as enp2s1. If you are not sure what your interface
name is, you can always run ip link after you have booted your system."
But the implications are not especially clear to newbies like me, who
have become used to the non-systemd LFS which uses "eth0". Perhaps a bit
more explanation would be helpful, such as in Section "7.2.1.2. DHCP
Configuration" mentioning that you *most likely* will have to put off
creating the configuration file until after the reboot, and that this is
normal. Otherwise a newbie is left wondering, What am I missing?
Something else I found: In the instructions in the BLFS book for
DHCP-4.3.1 under "Configuring ISC DHCP", having found the correct name
for my interface, I went back to the host chroot environment to see if
these two commands worked:
systemctl start dhclient@enp3s0
systemctl enable dhclient@enp3s0
Both gave this message:
Running in chroot, ignoring request.
After a bit of experimenting, I found that running the commands in the
booted system appears to be necessary.
Comments?
Alan
What would be the point of starting any service in a chroot environment
(that does not count individual service's chroot for security and
stuff)? In chroot, you use your host's networking setup and it would be
pointless to let chrooted system override that.
And as a matter of fact, while LFS is all done in chroot, BLFS does not
assume that. It assumes exactly the opposite: That they are being run
from a running system (more or less).
systemctl enable will work fine, but systemctl start won't as you have
seen. And I think it gives a clear message of why not.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
