Bruce Dubbs wrote:
Peter Ennis wrote:
Does it automatically get sent to the dev list when entered
via Trac
Yes.
More accurately, Peter, Trac notifications go to the lfs-book list, as
do Subversion commits. Practically speaking, there is no difference as
editors are subscribed to both lf
Peter Ennis wrote:
> Does it automatically get sent to the dev list when entered
> via Trac
Yes.
or should I do that also?
No.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Dan Nicholson gmail.com> writes:
> Maybe
> Alexander knows better. Here's one way to do it.
>
> $ ls -l /sys/class/net/*/device
> lrwxrwxrwx 1 root root 0 2006-08-29 06:50 /sys/class/net/eth0/device
> -> ../../../devices/pci:00/:00:0f.0
>
> $ udevinfo -a -p /class/net/eth0
...>
> loo
Matthew Burgess linuxfromscratch.org> writes:
>
> Peter,
>
> Would you mind putting this issue in Trac [0] please? > [0]
http://wiki.linuxfromscratch.org/lfs/newticket
>
OK. I will go through the posts and add them as "Enhancement",
or whatever seems appropriate, to Trac.
Does it automati
On 8/29/06, Peter Ennis <[EMAIL PROTECTED]> wrote:
LFS 6.2
Capitalization Issue:
=
7.13.1. Creating stable names for network interfaces
^ ^ ^ ^
Thanks.
Udev Stuff:
===
Reading section 7.13.1 it mentions
"If you are going to
Peter Ennis wrote:
LFS 6.2
Capitalization Issue:
=
7.13.1. Creating stable names for network interfaces
^ ^ ^ ^
Udev Stuff:
===
Reading section 7.13.1 it mentions
"If you are going to use the bus position as a key, create Udev r
LFS 6.2
Capitalization Issue:
=
7.13.1. Creating stable names for network interfaces
^ ^ ^ ^
Udev Stuff:
===
Reading section 7.13.1 it mentions
"If you are going to use the bus position as a key, create Udev rules
similar to the
