https://bugzilla.novell.com/show_bug.cgi?id=230213#c48
--- Comment #48 from Dieter Jurzitza 2007-07-27 03:04:36 MST ---
Hi Christian,
I see your words but still think that if what you say refers to what is
currently in opensuse factory the bug I referred to in #38 is present:
- If trhgger_firmware_loading.sh is started you set NOMACK_HACK_APPLIED=no
- at the end you ask if [ "${MAC_ADDRESS%00:00:00}" != "$MAC_ADDRESS" ]; then
IMHO you *should* set NOMACK_HACK_APPLIED=yes immediatly not only if you enter
the delay-loop and find the condition once again. On my system this exactly was
the bug why wrong entries found their way into /etc/udev/rules/30... - and it
actually doesn't matter whether you write to 30.... or to whatever ... in
/etc/udev/rules.d.
The appropriate way how this ought to look is depicted below:
--- trigger_firmware_loading.sh.original 2006-11-10 13:09:39.000000000
+0100
+++ trigger_firmware_loading.sh 2007-07-27 11:00:57.000000000 +0200
@@ -25,11 +25,11 @@
ip link set up dev $INTERFACE
ip link set down dev $INTERFACE
+ NOMAC_HACK_APPLIED=yes
# Do we have to wait some time?
for i in 0 1 2 3 4 5 6 7 8 9; do
MAC_ADDRESS=`cat /sys/class/net/$INTERFACE/address`
info_mesg "waiting for a usefull mac address: $MAC_ADDRESS"
if [ "${MAC_ADDRESS%00:00:00}" != "$MAC_ADDRESS" ] ; then
- NOMAC_HACK_APPLIED=yes
break
fi
sleep 1
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
