Are you using NET_PROFILES in rc.conf? If so, please attach your rc.conf so I can see it.

NET_PROFILES=(menu)

I have the same problem. When my system boots, network tries to load /etc/network-profiles/ATI-LICENSE.txt. I think the problem is in /usr/bin/netcfg from package initscripts. I think that the bugged (?) code is here (line 201 to 208):

ANSWER=`mktemp`

if [ "$TIMEOUT" != "" ]; then
dialog \
--timeout $TIMEOUT \
--default-item $DEFAULT \
--menu "Select the network profile you wish to use\n\n (timeout in $TIMEOUT seconds)" \
13 50 6 \
"${profiles[@]}" 2>$ANSWER
ret=$?
else
dialog \
--default-item $DEFAULT \
--menu "Select the network profile you wish to use" \
13 50 6 \
"${profiles[@]}" 2>$ANSWER
ret=$?
fi

At boot $ANSWER is wrong. When I restart network (/etc/rc.d/network restart) sometimes It's correct, sometimes not (and not always ATI-LICENSE.txt..). If I don't use "menu" but I put a network profiles name in /etc/rc.conf It always works.
I hope to have been useful, archlinux is great! Bye bye

Strabla Ruggero (Ermak)

/etc/network-profiles is only supposed to contain actual network profiles. Why is ATI-LICENSE.txt in there?

He doesn't have a /etc/network-profiles/ATI-LICENSE.txt file just as I dont have a /etc/network-profiles/bin file but that is what the menu is looking for. This loading of uncalled for files is the initial problem.

Hi, ATI_LICENSE.TXT (this is the correct filename, not ATI-LICENSE.txt) was in my root filesystem (/ not /root) (I know, that file must not to be there, I have moved it). In /etc/network-profiles I have:

[root@orion ~]# ls /etc/network-profiles/
Casa Crema template
[root@orion ~]#

I can confirm that the problem appears on boot time, when the system is up and I restart network It usually works.

My profiles and rc.conf is attached.

Uh, a specification: dialog only showed (correctly) Casa & Crema profiles but, when I selected one of these, console told that /etc/network-profiles/ATI_LICENSE.TXT file was missing. That's why I think that $PROFILE_DIR in /usr/bin/netcfg is correct and $ANSWER, at boot time, not. Bye

Perhaps mktemp is not working at boot-time. Try replacing the mktemp line with this:

ANSWER=`mktemp` || exit 1

ANSWER is correct at boot time, I verificated that with some "echo $ANSWER > file" for debugging purpose. However I fixed the problem in two ways:
1)Upgrading gpm (and dialog) to last version (see http://bugs.archlinux.org/task/3568). That version contain a patch that, correctly, doesn't redirect to stderr a debug message when a dialog is launched. In old version of gpm, in the file created by mktemp there was that debug message (... 2>$ANSWER) plus the profile name, instead of only profile name.
2)With old version of gpm, It possible to work around the stderr problem lauching dialog with --stdout option and redirect stdout to $ANSWER: "${profiles[@]}" >$ANSWER

Bye bye.

Ah, excellent. I knew about the gpm issue, but didn't think the two were related.

I'll close this bug now.