70-persistent-net.rules No such file or directory

noizar · 05-07-2013, 12:35 PM

hello
when i run comment in 7.2.1. Creating stable names for network interfaces

Code:

cat /etc/udev/rules.d/70-persistent-net.rules

the result is

Code:

cat: /etc/udev/rules.d/70-persistent-net.rules: No such file or directory

please help me to fix it ??

spiky0011 · 05-07-2013, 12:46 PM

Hi

Did you complete this chapter
http://www.linuxfromscratch.org/lfs/...er06/udev.html
or maybe something went wrong

Do you have dir /etc/udev/rules.d

noizar · 05-07-2013, 05:55 PM

version-check

Code:

bash, version 4.2.37(1)-release
/bin/sh -> /bin/bash
Binutils: (GNU Binutils) 2.23.1
bison (GNU Bison) 2.5
/usr/bin/yacc -> /usr/bin/bison.yacc
bzip2,  Version 1.0.6, 6-Sept-2010.
Coreutils:  8.13
diff (GNU diffutils) 3.2
find (GNU findutils) 4.4.2
GNU Awk 4.0.1
/usr/bin/awk -> /usr/bin/gawk
gcc (Ubuntu/Linaro 4.7.2-2ubuntu1) 4.7.2
(Ubuntu EGLIBC 2.15-0ubuntu20.1) 2.15
grep (GNU grep) 2.12
gzip 1.5
Linux version 3.5.0-28-generic (buildd@panlong) (gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) ) #48-Ubuntu SMP Tue Apr 23 23:03:38 UTC 2013
m4 (GNU M4) 1.4.16
GNU Make 3.81
patch 2.6.1
Perl version='5.14.2';
GNU sed version 4.2.1
tar (GNU tar) 1.26
Texinfo: makeinfo (GNU texinfo) 4.13
xz (XZ Utils) 5.1.0alpha
/usr/local/bin/ld: this linker was not configured to use sysroots
collect2: error: ld returned 1 exit status
gcc compilation failed

dir /etc/udev/rules.d

Code:

55-lfs.rules  81-cdrom.rules  83-cdrom-symlinks.rules

stoat · 05-07-2013, 08:49 PM

Your missing file (70-persistent-net.rules) is created (usually, for me anyway) in the LFS book's Udev chapter (as pointed out by spiky0011) when that script at the end of that section (init-net-rules.sh) is run. It searches through /sys/class/net of your host for devices, does its thing, and ends up calling another script (write_net_rules) which creates the file you need.

Who knows what happened. Maybe you exited and then re-entered the chroot environment and botched the mounting of the host's virtual file systems before you did the Udev section. Maybe it's a network hardware related thing. I don't know. But for me, this might shake up my confidence in how well I did the steps in the Udev section.

You could consider carefully re-doing the Udev steps after properly re-entering the chroot environment. Or, if you're convinced everything else about Udev was properly done, then try copying the network device's udev rule from your host to the LFS system as 70-persistent-net.rules (tweaking if needed). Finish the network setup and see if it connects. It won't harm anything and it's reversible.

P.S.: That version-check stuff is part of spiky0011's signature and probably wasn't specifically meant for you. But there is sort of some weirdness in yours. I don't really know what it means or what to do about it. Maybe somebody else will. Anyway, it's sort of late in the game to find out about bad stuff in the version-check.

never2far · 10-29-2013, 06:31 AM

I know it's a late answer but maybe someone will find this useful.

I had the same problem and from what i see in the /sources/systemd-206/udev-lfs-206-1/init-net-rules.sh script, if you are using a KVM machine and your interface have MAC '52:54:00:', the script will ignore your interface.

I have commented #VENDORS_IGNORED['52:54:00:']="kvm" and now the file looks like this:

Code:

# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# net device module
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="52:54:00:11:b9:aa", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"