Summary: | wireless problem baselayout-1.12.0_pre17-r2 (I've found the solution) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joseph <j.goncalves> |
Component: | [OLD] baselayout | Assignee: | Roy Marples (RETIRED) <uberlord> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mobile+disabled |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch rc-daemon.sh to only remove what we asked for |
Description
Joseph
2006-04-16 06:55:09 UTC
Problem confirmed. The proposed solutions works for me, thank you for investigating this. Created attachment 84888 [details, diff]
Patch rc-daemon.sh to only remove what we asked for
Attached is a patch to /lib/rcscripts/sh/rc-daemon.sh that should correct this issue. The patch references sbin/rc-daemon.sh so it can easily be applied to the ebuild - to manually patch it, change it to reference /lib/rcscripts/sh/rc-daemon.sh
Please test and report back. (In reply to comment #3) > Please test and report back. Appears to work here as well (tested with the original proposed fix reverted, of course). Joseph, does this work for you as well? (In reply to comment #4) > Appears to work here as well (tested with the original proposed fix reverted, > of course). > > Joseph, does this work for you as well? > I've re-emerged this baselayout package, applied the patch to the rc-daemon.sh script and performed the original tests that led me to discover the problem. /var/lib/init.d/daemons/net.eth1 had the correct information this time around and the connection was re-established with my wireless access point after I switched it off and on, without restarting the service on my laptop. Classic == bug hey... Someone once gave me a great C tip which may apply to bash: He said to use the form constant == variable instead of the conventional method of variable == constant. This way, if human nature sucumbes then a compile error will occur instead of a phantom intermittent type bug. (In reply to comment #5) > Classic == bug hey... Someone once gave me a great C tip which may apply to > bash: He said to use the form constant == variable instead of the conventional > method of variable == constant. This way, if human nature sucumbes then a > compile error will occur instead of a phantom intermittent type bug. Ah no, bash treats quoting differently with RHS vs LHS. Besides, that makes code more unreadable imo. Fixed in pre17-r3 |