[lfs-support] udev problem
My system was working fine, until I decided that I needed to add an additional Network interface card (turned on the previous deactivated onboard NIC). Now my network card names are all messed up. I've edited the 70-persistent-net.rules file, but udev seems to be ignoring it and naming devices as it pleases. I have 4 Ethernet Devices and 2 wlan Devices, is that too many for udev to rename properly? Thank You, Casey -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Howto keep track....
...of changed/new files on http only sites like sourceforge.net? Keeping track of changed and new files on FTP sites is relative easy. However, HTTP sites is differently and made complicated because no page is the same and directory listings are not easy. In fact, I do not remember anymore how to get directory listings from HTTP servers. If that is possible and if it works mostly the same on every HTTP server, I can make a script to get it done. Since authors on LFS are probably using such a tool, what tool or mechanism I can try? Regards, Frans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Grateful
Op Fri, 18 Oct 2013 23:42:03 +0200 schreef Dan McGhee beesn...@grm.net:
I decided to write this since even in my old age I like receiving
feedback that my efforts are not in vain.
Hats off to you {,B}LFS editors, maintainers, developers and list
supporters. The job you do is almost insurmountable, yet you do it with
aplomb. The LFS book is exactly what it says it is: a follow the
directions exactly learning experience to build an operation system.
That takes work and attention to details. Not only that, but you take
care of broken links on the web site, e-mails not automatically going to
those who need them--yes, I follow the list--and all sorts of other
housekeeping chores.
But given all of this, you take the time to aid people. I know I can be
a pest because I like to have things right in my mind before I go
ahead. It's worse right now since I'm scouring the rust from my
building skills. Just this week, Ken Moffat, Bruce Dubbs and Pierre
Labastie have taken the time to point me in the right direction so I can
do things the way I want to.
I remember from my working days that the trenches can get so deep I
wanted to throw in the towel. I urge you not to lose your attitudes.
Thanks to you all.
Dan
Hear, hear
I was pondering such action, but Dan beat me. I stray into support-sites now
and then, but none of them comes near to the quality, politeness and
thouroughness of this site!
Thank you from me too.
Hans.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] udev problem
Casey Daniels wrote: My system was working fine, until I decided that I needed to add an additional Network interface card (turned on the previous deactivated onboard NIC). Now my network card names are all messed up. I've edited the 70-persistent-net.rules file, but udev seems to be ignoring it and naming devices as it pleases. I have 4 Ethernet Devices and 2 wlan Devices, is that too many for udev to rename properly? No. Can you post your 70-persistent-net.rules file? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Howto keep track....
Frans de Boer wrote: ...of changed/new files on http only sites like sourceforge.net? Keeping track of changed and new files on FTP sites is relative easy. However, HTTP sites is differently and made complicated because no page is the same and directory listings are not easy. In fact, I do not remember anymore how to get directory listings from HTTP servers. If that is possible and if it works mostly the same on every HTTP server, I can make a script to get it done. Since authors on LFS are probably using such a tool, what tool or mechanism I can try? It's not easy. I have custom scripts that basically address each package. Sometimes upstream blocks directory listings completely. Sometimes you get into a situation where odd releases are stable and even development or vice versa. You can look at http://anduin.linuxfromscratch.org/~bdubbs/lfs-latest-files.phps but that is just an example and slightly out of date. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Grateful
Op Sun, 20 Oct 2013 15:53:50 +0200 schreef hans kaper spaky...@xs4all.nl:
Op Fri, 18 Oct 2013 23:42:03 +0200 schreef Dan McGhee beesn...@grm.net:
I decided to write this since even in my old age I like receiving
feedback that my efforts are not in vain.
Hats off to you {,B}LFS editors, maintainers, developers and list
supporters. The job you do is almost insurmountable, yet you do it with
aplomb. The LFS book is exactly what it says it is: a follow the
directions exactly learning experience to build an operation system.
That takes work and attention to details. Not only that, but you take
care of broken links on the web site, e-mails not automatically going to
those who need them--yes, I follow the list--and all sorts of other
housekeeping chores.
But given all of this, you take the time to aid people. I know I can be
a pest because I like to have things right in my mind before I go
ahead. It's worse right now since I'm scouring the rust from my
building skills. Just this week, Ken Moffat, Bruce Dubbs and Pierre
Labastie have taken the time to point me in the right direction so I can
do things the way I want to.
I remember from my working days that the trenches can get so deep I
wanted to throw in the towel. I urge you not to lose your attitudes.
Thanks to you all.
Dan
Hear, hear
I was pondering such action, but Dan beat me. I stray into support-sites now
and then, but none of them comes near to the quality, politeness and
thouroughness of this site!
And patience, of course.
Thank you from me too.
Hans.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] udev problem
Casey Daniels wrote:
On 10/20/2013 10:36 AM, Bruce Dubbs wrote:
Casey Daniels wrote:
My system was working fine, until I decided that I needed to add an
additional Network interface card (turned on the previous deactivated
onboard NIC). Now my network card names are all messed up. I've edited
the 70-persistent-net.rules file, but udev seems to be ignoring it and
naming devices as it pleases.
I have 4 Ethernet Devices and 2 wlan Devices, is that too many for udev
to rename properly?
No.
Can you post your 70-persistent-net.rules file?
-- Bruce
# 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 e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth3
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth0
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth1
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth2
# net device iwlwifi
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==wlan*, NAME=wlan0
# net device iwlwifi
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==wlan*, NAME=wlan1
MAC Address replaced with X's, if you need the actual address let me know.
Are these lines split for email or are they that way in the file? I
think you need to escape some newlines. For example,
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*, \
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0, \
ATTR{type}==1, KERNEL==eth*, NAME=eth0
You can also try:
udevadm test --action=ADD /sys/class/net/device
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] udev problem
On 10/20/2013 11:25 AM, Bruce Dubbs wrote:
Casey Daniels wrote:
On 10/20/2013 10:36 AM, Bruce Dubbs wrote:
Casey Daniels wrote:
My system was working fine, until I decided that I needed to add an
additional Network interface card (turned on the previous deactivated
onboard NIC). Now my network card names are all messed up. I've edited
the 70-persistent-net.rules file, but udev seems to be ignoring it and
naming devices as it pleases.
I have 4 Ethernet Devices and 2 wlan Devices, is that too many for udev
to rename properly?
No.
Can you post your 70-persistent-net.rules file?
-- Bruce
# 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 e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth3
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth0
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth1
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth2
# net device iwlwifi
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==wlan*, NAME=wlan0
# net device iwlwifi
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==wlan*, NAME=wlan1
MAC Address replaced with X's, if you need the actual address let me know.
Are these lines split for email or are they that way in the file? I
think you need to escape some newlines. For example,
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*, \
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0, \
ATTR{type}==1, KERNEL==eth*, NAME=eth0
You can also try:
udevadm test --action=ADD /sys/class/net/device
-- Bruce
They are 1 line in the file, its just what email did to them.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] udev problem
On 10/20/2013 11:25 AM, Bruce Dubbs wrote:
Casey Daniels wrote:
On 10/20/2013 10:36 AM, Bruce Dubbs wrote:
Casey Daniels wrote:
My system was working fine, until I decided that I needed to add an
additional Network interface card (turned on the previous deactivated
onboard NIC). Now my network card names are all messed up. I've edited
the 70-persistent-net.rules file, but udev seems to be ignoring it and
naming devices as it pleases.
I have 4 Ethernet Devices and 2 wlan Devices, is that too many for udev
to rename properly?
No.
Can you post your 70-persistent-net.rules file?
-- Bruce
# 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 e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth3
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth0
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth1
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth2
# net device iwlwifi
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==wlan*, NAME=wlan0
# net device iwlwifi
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==wlan*, NAME=wlan1
MAC Address replaced with X's, if you need the actual address let me know.
Are these lines split for email or are they that way in the file? I
think you need to escape some newlines. For example,
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*, \
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0, \
ATTR{type}==1, KERNEL==eth*, NAME=eth0
You can also try:
udevadm test --action=ADD /sys/class/net/device
-- Bruce
Is there a way to see if Udev is even reading the
70-persistent-net.rules on boot?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Howto keep track....
On 10/20/2013 04:43 PM, Bruce Dubbs wrote: Frans de Boer wrote: ...of changed/new files on http only sites like sourceforge.net? Keeping track of changed and new files on FTP sites is relative easy. However, HTTP sites is differently and made complicated because no page is the same and directory listings are not easy. In fact, I do not remember anymore how to get directory listings from HTTP servers. If that is possible and if it works mostly the same on every HTTP server, I can make a script to get it done. Since authors on LFS are probably using such a tool, what tool or mechanism I can try? It's not easy. I have custom scripts that basically address each package. Sometimes upstream blocks directory listings completely. Sometimes you get into a situation where odd releases are stable and even development or vice versa. You can look at http://anduin.linuxfromscratch.org/~bdubbs/lfs-latest-files.phps but that is just an example and slightly out of date. -- Bruce Thanks Bruce, Like I said no page is the same and I noticed that you handle every site in a different way using customized regex's. That is exactly the thing I try to avoid, but given the nature of things I assume that would be hard to accomplished using HTTP. I stay on the lookout of a more generic tool and am happy that my scripts can handle normal FTP transfers. I augmented the tables in my scripts to handle also the LFS site, since that can be reached by FTP too. Regards, Frans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] udev problem
On 10/20/2013 11:25 AM, Bruce Dubbs wrote:
Are these lines split for email or are they that way in the file? I
think you need to escape some newlines. For example,
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*, \
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0, \
ATTR{type}==1, KERNEL==eth*, NAME=eth0
You can also try:
udevadm test --action=ADD /sys/class/net/device
-- Bruce
Found out something interesting. As long as I don't try to assign
anything except the onboard NIC to eth0, it will let me do as I please.
I can even name the onboard NIC to something other than eth0, but
anytime I try to name something eth0 (besides the onboard nic) udev just
does what ever it wants to do.
Casey
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Howto keep track....
On Sun, 20 Oct 2013 18:33:53 +0200 Frans de Boer fr...@fransdb.nl wrote: Like I said no page is the same and I noticed that you handle every site in a different way using customized regex's. That is exactly the thing I try to avoid, but given the nature of things I assume that would be hard to accomplished using HTTP. I just had a flashback to Gopher. Gopher proponents usualy cite that exact reason as the reason the World should use Gopher instead of HTTP. Even though that is not HTTPs fault. It's really HTMLs fault. As for automated package tracking, I did an experiment using the source revision tools that various packages use (git, subversion, mercurial and others..) but had the mother of mixed success. While for some packages this works so well you would swear God gave his personal blessing, for other packages this is the worst kind of a nightmare. Using source revision tools also adds the aditional problem that in most cases you need to rebuild the ./configure script and that is often very difficult, if not impossible. And then there is the problem of both initial seeding and continuous maintenance of the 350+GB repository of repositories containing 300+ individual packages. Definitely not for the faint of heart. -- You don't need an AI for a robot uprising. Humans will do just fine. signature.asc Description: PGP signature -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] udev problem
Casey Daniels wrote:
On 10/20/2013 11:25 AM, Bruce Dubbs wrote:
Are these lines split for email or are they that way in the file? I
think you need to escape some newlines. For example,
# net device e1000e
SUBSYSTEM==net, ACTION==add, DRIVERS==?*, \
ATTR{address}==XX:XX:XX:XX:XX:XX, ATTR{dev_id}==0x0, \
ATTR{type}==1, KERNEL==eth*, NAME=eth0
You can also try:
udevadm test --action=ADD /sys/class/net/device
-- Bruce
Found out something interesting. As long as I don't try to assign
anything except the onboard NIC to eth0, it will let me do as I please.
I can even name the onboard NIC to something other than eth0, but
anytime I try to name something eth0 (besides the onboard nic) udev just
does what ever it wants to do.
Just a thought. I believe a system sets up to preset values and then
renames what's required when it processes the rule. If something is
already named to the value requested, then the rename fails.
What are the values in /sys/class/net/ with no rules? Then what if you
just try to change one of the problem interfaces to say, eth1, does that
work?
One thing to try is to skip the udev sections in the boot sequence
completely and then run udevd with --debug after boot. Another thing to
try is setting udev.log-priority=debug on the kernel command line.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
