e lfs bootscripts in section 7.6 are installed.
>
>> I proceeded with the rest of the page, and when it came to doing "cat
>> /etc/udev/rules.d/70-persistent-net.rules"., I found I had no "cat
>> /etc/udev/rules.d/70-persistent-net.rules" as well. The on
ard, but I wanted to see what the
> symlinks were, this is when I discovered I had no /etc/rc.d
This is created when the lfs bootscripts in section 7.6 are installed.
> I proceeded with the rest of the page, and when it came to doing "cat
> /etc/udev/rules.d/70-persistent-net.rules&qu
version='5.10.1';
GNU sed version 4.2.1
tar (GNU tar) 1.22
Texinfo: makeinfo (GNU texinfo) 4.13
xz (XZ Utils) 4.999.9beta
gcc compilation OK
tipaye@ubuntu:~$
I noticed the problem when I got to chapter 7.2. General Network Configuration
The first part suggests removing network symlinks if
Yes the /sys directory is mounted.
# ls /sys/net/class
eth0 lo pan0
I will take a snapshot and continue.
On 15 July 2011 07:00, wrote:
> Re: What has happened to 70-persistent-net.rules
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/
D. Birch wrote:
> This is my first time reaching this far with LFS.
>
> I'm using version 6.8, haven't deviated at all. Am running within
> vmware using debian as the host.
>
> In "7.13.1 Creating stable names for network interfaces" - I am told
> t
This is my first time reaching this far with LFS.
I'm using version 6.8, haven't deviated at all. Am running within
vmware using debian as the host.
In "7.13.1 Creating stable names for network interfaces" - I am told
to inspect /etc/udev/rules.d/70-persistent-net.rules bu
rules file
parse_file: reading '/lib/udev/rules.d/80-drivers.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-udev-late.rules' as rules file
udev_rules_new: rules use 10524 bytes tokens (877 * 12 bytes), 6917 bytes buffer
udev_rules_new: temporary index used 69
On Sunday 22 August 2010 09:20:29 Mike Johnston wrote:
> Thank you.
> That would work however, I want to make 30 instances for 30 machines. I
> need to generate the 70-persistent-net.rules file so each machine has fixed
> interface names. What I don't understand is that if its a
Mike Johnston schrieb:
> Thank you.
> That would work however, I want to make 30 instances for 30 machines. I need
> to generate the 70-persistent-net.rules file so each machine has fixed
> interface names.
you don't need a 70-persistent-net.rules file.
as you are writing in
Thank you.
That would work however, I want to make 30 instances for 30 machines. I need
to generate the 70-persistent-net.rules file so each machine has fixed
interface names.
What I don't understand is that if its a symlink on read/write partition it
consistently keeps adding to the file
Mike Johnston schrieb:
> Hello,I have a LFS system with a read only file system. I have
> /etc/udev/rules.d a symlink to a read/write partition. The
> 70-persistent-net.rules file gets generated and keeps on growing for every
> reboot. If i make the root filesystem read/write, th
Hello,I have a LFS system with a read only file system. I have
/etc/udev/rules.d a symlink to a read/write partition. The
70-persistent-net.rules file gets generated and keeps on growing for every
reboot. If i make the root filesystem read/write, this file does not get
re-generated and
On Fri, Apr 9, 2010 at 8:57 PM, jumbophut wrote:
>> After running the code in section 7.13, viz:
>>
>> "for NIC in /sys/class/net/* ; do
>> INTERFACE=${NIC##*/} udevadm test --action=add $NIC
>> done"
>>
>> I cannot find the /etc/udev/rules.d
On April 8, 2010 03:17:38 am jumbophut wrote:
> After running the code in section 7.13, viz:
>
> "for NIC in /sys/class/net/* ; do
> INTERFACE=${NIC##*/} udevadm test --action=add $NIC
> done"
>
> I cannot find the /etc/udev/rules.d/70-persistent-net.rules file
On April 8, 2010 03:17:38 am jumbophut wrote:
> After running the code in section 7.13, viz:
>
> "for NIC in /sys/class/net/* ; do
> INTERFACE=${NIC##*/} udevadm test --action=add $NIC
> done"
>
> I cannot find the /etc/udev/rules.d/70-persistent-net.rules
On 08/04/10 10:17, jumbophut wrote:
> After running the code in section 7.13, viz:
>
> "for NIC in /sys/class/net/* ; do
> INTERFACE=${NIC##*/} udevadm test --action=add $NIC
> done"
>
> I cannot find the /etc/udev/rules.d/70-persistent-net.rules file that
>
After running the code in section 7.13, viz:
"for NIC in /sys/class/net/* ; do
INTERFACE=${NIC##*/} udevadm test --action=add $NIC
done"
I cannot find the /etc/udev/rules.d/70-persistent-net.rules file that
is supposed to have been generated.
I have spent some time trying to trac
INTERFACE
environment variable was not being exported to /lib/udev/write_net_rules.
i was able to alleviate the issue by creating a rules file that
explicitly exports INTERFACE in /etc/udev/rules.d/69-jmscott.rules.
Ths content of that file follows:
ENV{INTERFACE}=="",ACTION==&qu
On Tue, 2010-01-12 at 21:55 -0600, Bruce Dubbs wrote:
> jmsc...@setex.ipcallback.com wrote:
>
> > by the way, one of the conditions for setting the value of INTERFACE
> > is that
> >
> > udev_device_get_subsystem(dev), "net") == 0
>
> That seems like it is looking for /dev. If it errors, th
jmsc...@setex.ipcallback.com wrote:
> by the way, one of the conditions for setting the value of INTERFACE
> is that
>
> udev_device_get_subsystem(dev), "net") == 0
That seems like it is looking for /dev. If it errors, the expression is
false. I wonder if dev above is a shorthand for /s
On Tue, Jan 12, 2010 at 10:02:02AM -0500, linux fan wrote:
> On 1/12/10, jmsc...@setex.ipcallback.com wrote:
> > so, in the name of progress, i like to solict advice on what to do next,
>
> LFS-6.4 and earlier had:
> for NIC in /sys/class/net/* ; do
> INTERFACE=${NIC##*/} udevadm test --actio
x27;.
i'm tracing down what syspath is now.
-j
>
> $ for NIC in /sys/class/net/* ; do \
> INTERFACE=${NIC##*/}; echo $INTERFACE; done
> eth0
> lo
> sit0
>
> I then edited /lib/udev/write_net_rules and put the following at the top
> of the file:
>
>
> so, in the name of progress, i like to solict advice on what to do next,
> before my hacking corrupts the still unbooted lfs filesystem.
> since i have only one eth0 nic, is it safe to simply ignore the generation
> of /etc/udev/rules.d/70-persistent-net.rules and move on to chapte
te_net_rules start" > xxx
env >> xxx
exit
I renamed /etc/udev/rules.d/70-persistent-net.rules and ran:
# INTERFACE=eth0 /sbin/udevadm test --action=add /sys/class/net/eth0
# cat xxx
write_net_rules start
SUBSYSTEM=net
DEVPATH=/devices/pci:00/:00:19.0/net/eth0
ACTION=add
PWD=/etc
On 1/12/10, linux fan wrote:
> Just experimenting ...
It almost seems like export/import is fouled up.
The following block should print:
bar
..
foo="" &&
echo 'echo $foo' > fubar &&
chmod 755 fubar &&
foo=bar ./fubar &&
echo ".$foo."
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
F
quot;
done
Here is the output of 'sh fubar'
INTERFACE=eth0 udevadm test --action=add /sys/class/net/eth0
INTERFACE=lo udevadm test --action=add /sys/class/net/lo
I remove the rule in my /etc/udev/rules.d/70-persistent-net.rules
pertaining to eth0 (the only rule in the file).
I execute the
On Tue, Jan 12, 2010 at 10:02:02AM -0500, linux fan wrote:
> On 1/12/10, jmsc...@setex.ipcallback.com wrote:
> > so, in the name of progress, i like to solict advice on what to do next,
>
> LFS-6.4 and earlier had:
> for NIC in /sys/class/net/* ; do
> INTERFACE=${NIC##*/} udevadm test --actio
On 1/12/10, jmsc...@setex.ipcallback.com wrote:
> so, in the name of progress, i like to solict advice on what to do next,
LFS-6.4 and earlier had:
for NIC in /sys/class/net/* ; do
INTERFACE=${NIC##*/} udevadm test --action=add --subsystem=net $NIC
done
I wonder why subsystem was later remov
so, in the name of progress, i like to solict advice on what to do next,
before my hacking corrupts the still unbooted lfs filesystem.
since i have only one eth0 nic, is it safe to simply ignore the generation
of /etc/udev/rules.d/70-persistent-net.rules and move on to chapter 8?
won
On Mon, Jan 11, 2010 at 01:08:35AM -0600, Bruce Dubbs wrote:
> jmsc...@setex.ipcallback.com wrote:
> > On Sun, Jan 10, 2010 at 10:37:13PM -0600, Bruce Dubbs wrote:
> >> jmsc...@setex.ipcallback.com wrote:
> >>
> >>> the standard output to /lib/udev/write_net_rules is
> >>> caught and filtered by u
jmsc...@setex.ipcallback.com wrote:
> On Sun, Jan 10, 2010 at 10:37:13PM -0600, Bruce Dubbs wrote:
>> jmsc...@setex.ipcallback.com wrote:
>>
>>> the standard output to /lib/udev/write_net_rules is
>>> caught and filtered by udevadm, so examining the env list to execve()
>>> seemed a bit more direc
On Sun, Jan 10, 2010 at 10:37:13PM -0600, Bruce Dubbs wrote:
> jmsc...@setex.ipcallback.com wrote:
>
> > the standard output to /lib/udev/write_net_rules is
> > caught and filtered by udevadm, so examining the env list to execve()
> > seemed a bit more direct.
>
> Where is standard output caught
jmsc...@setex.ipcallback.com wrote:
> the standard output to /lib/udev/write_net_rules is
> caught and filtered by udevadm, so examining the env list to execve()
> seemed a bit more direct.
Where is standard output caught? I don't see it. After options, udevadm
just calls udevadm-test(argc, ar
On Sun, Jan 10, 2010 at 08:38:09PM -0600, Bruce Dubbs wrote:
> jmsc...@setex.ipcallback.com wrote:
>
> > from examining the udevadm source, it appears the environment variable list
> > is rebuilt for the execve call to /lib/udev/write_net_rules.
> > i do see the INTERFACE env variable being pass
jmsc...@setex.ipcallback.com wrote:
> from examining the udevadm source, it appears the environment variable list
> is rebuilt for the execve call to /lib/udev/write_net_rules.
> i do see the INTERFACE env variable being passed to udevadm in main(),
> as expected, but not being included in the e
On Sat, Jan 09, 2010 at 12:48:42PM -0600, Bruce Dubbs wrote:
> jmsc...@setex.ipcallback.com wrote:
>
> > i see the error
> >
> >util_run_program: 'write_net_rules'
> >util_run_program: '/lib/udev/write_net_rules' (stderr) 'missing
> > $INTERFACE'
> >util_run_program: 'write_net_rules
On Sat, Jan 09, 2010 at 12:48:42PM -0600, Bruce Dubbs wrote:
> jmsc...@setex.ipcallback.com wrote:
>
> > i see the error
> >
> >util_run_program: 'write_net_rules'
> >util_run_program: '/lib/udev/write_net_rules' (stderr) 'missing
> > $INTERFACE'
> >util_run_program: 'write_net_rules
jmsc...@setex.ipcallback.com wrote:
> i see the error
>
>util_run_program: 'write_net_rules'
>util_run_program: '/lib/udev/write_net_rules' (stderr) 'missing $INTERFACE'
>util_run_program: 'write_net_rules' returned with exitcode 1
>
> amongst the voluminous output.
>
> i tried expo
On Sat, Jan 09, 2010 at 12:04:41PM -0600, Bruce Dubbs wrote:
> jmsc...@setex.ipcallback.com wrote:
> >
> >> If you do
> >>INTERFACE=eth0 udevadm test --action=add eth0
> >>
> >> Do you get anything?
> >>
> > now i'm seeing the error
> >
> > unable to open device '/syseth0'
>
> My fault.
jmsc...@setex.ipcallback.com wrote:
>
>> If you do
>>INTERFACE=eth0 udevadm test --action=add eth0
>>
>> Do you get anything?
>>
> now i'm seeing the error
>
> unable to open device '/syseth0'
My fault. It should be
INTERFACE=/sys/class/net/eth0 udevadm test --action=add /sys/class/ne
On Fri, Jan 08, 2010 at 11:36:19PM -0600, Bruce Dubbs wrote:
> jmsc...@setex.ipcallback.com wrote:
>
> > Nope, appears that /etc/udev/rules.d/70-persistent-net.rules is missing.
> > I see many but no obvious errors in the output of of the 'for' loop in the
&
INTERFACE=${NIC##*/} udevadm test --action=add $NIC
>>> done
>>>
>>> followed by the blurb to inspect the 70-persistent-net.rules file.
>>>
>>> cat /etc/udev/rules.d/70-persistent-net.rules
>>>
>>> The problem is that
jmsc...@setex.ipcallback.com wrote:
> Nope, appears that /etc/udev/rules.d/70-persistent-net.rules is missing.
> I see many but no obvious errors in the output of of the 'for' loop in the
> blurb in paragraph 7.13.1:
>
> for NIC in /sys/class/net/* ; do
>
On Thu, Jan 07, 2010 at 11:15:23PM -0600, Bruce Dubbs wrote:
> jmsc...@setex.ipcallback.com wrote:
> > Hello,
> >
> > I'm having a problem with configuring the network scripts in the
> > LFS book 6.5. The file /etc/udev/rules.d/70-persistent-net.rules
>
jmsc...@setex.ipcallback.com wrote:
> Hello,
>
> I'm having a problem with configuring the network scripts in the
> LFS book 6.5. The file /etc/udev/rules.d/70-persistent-net.rules
> doesn't appear to be created. In particular, in chapter 7.13.1 is
> the blurb of c
s in the
>>> LFS book 6.5. The file /etc/udev/rules.d/70-persistent-net.rules
>>> doesn't appear to be created. In particular, in chapter 7.13.1 is
>>> the blurb of code to pre-generate the udev rules file
>>>
>>> for NIC in /sys/class/
On Thu, Jan 07, 2010 at 04:30:13PM -0800, Justin P. Mattock wrote:
> On 01/07/10 16:07, jmsc...@setex.ipcallback.com wrote:
> > Hello,
> >
> > I'm having a problem with configuring the network scripts in the
> > LFS book 6.5. The file /etc/udev/rules.d/70-persist
On 01/07/10 16:07, jmsc...@setex.ipcallback.com wrote:
> Hello,
>
> I'm having a problem with configuring the network scripts in the
> LFS book 6.5. The file /etc/udev/rules.d/70-persistent-net.rules
> doesn't appear to be created. In particular, in chapter 7.13.1 is
&
Hello,
I'm having a problem with configuring the network scripts in the
LFS book 6.5. The file /etc/udev/rules.d/70-persistent-net.rules
doesn't appear to be created. In particular, in chapter 7.13.1 is
the blurb of code to pre-generate the udev rules file
for NIC in /sys
49 matches
Mail list logo
