On Fri, Aug 13, 2010 at 3:34 PM, Suraj Linux
wrote:
> unable to open device '/sys/class/net/*'
I think you don't have /sys mounted in the chroot environment. To
check to see if it is mounted, run ls /sys in the chroot environment.
If /sys is mounted, you should see a good number of directories. If
On 14/08/10 22:36, linux fan wrote:
> On 8/13/10, Suraj Linux wrote:
>>
>> add_matching_files: unable to open '/dev/.udev/rules.d': No such file
>> or directory
>
> Without knowing anything, I wonder why '/dev/.udev/rules.d' is
> missing. What creates it?
Udev creates it, the udev running on the
On 8/13/10, Suraj Linux wrote:
>
> add_matching_files: unable to open '/dev/.udev/rules.d': No such file
> or directory
Without knowing anything, I wonder why '/dev/.udev/rules.d' is
missing. What creates it?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromsc
Suraj Linux wrote:
> Hi Bruce,
>
> I do have an another WIFI adapter. Would you consider that as another
> NIC card ?
If you only have one in the system at a time, no. The purpose of the
udevadm instruction is to always assign the same interface to the same
card when more than one card is in t
Hi Bruce,
I do have an another WIFI adapter. Would you consider that as another
NIC card ?
Thanks for the help.
-Suraj.
On Sat, Aug 14, 2010 at 2:00 AM,
wrote:
> Send lfs-support mailing list submissions to
> lfs-supp...@linuxfromscratch.org
>
> To subscribe or unsubscribe via the World
On 13/08/10 21:34, Suraj Linux wrote:
> Hi,
>
> I have a doubt at section 7.13.1.
>
> Then I run the following command
>
> for NIC in /sys/class/net/* ; do
> INTERFACE=${NIC##*/} udevadm test --action=add $NIC
> done
>
> I get the below output. The file "
> /etc/udev/rules.d/70-persistent-net
