Basically, a segfault is bad... There should be error checking, and an error message that says to configure the /etc/conf.d/net file Also, being stuck without a network means that the error message is even more important. bash-2.05b# /etc/init.d/net.eth0 start /sbin/runscript.sh: /etc/conf.d/net: line 221: syntax error near unexpected token `(' /sbin/runscript.sh: /etc/conf.d/net: line 221: `preup_macchanger() {' Segmentation fault bash-2.05b# /etc/init.d/net.eth0 stop /sbin/runscript.sh: /etc/conf.d/net: line 221: syntax error near unexpected token `(' /sbin/runscript.sh: /etc/conf.d/net: line 221: `preup_macchanger() {' Segmentation fault bash-2.05b# vi /etc/conf.d/net bash-2.05b# /etc/init.d/net.eth0 start * Bringing eth0 up... * eth0 192.168.0.3 [ ok ] * Adding routes * default gw 192.168.0.1 Reproducible: Always Steps to Reproduce: 1. upgrade.. and accidentally wipe out network settings... 2. try to manually bring up the interface 3. see it crash 4. wonder if my etc-update went arye (sp?) Actual Results: I was able to get everything working, and so would the average person... but always build for the n00bs is a good philosophy.. it also safes time and frustration, and gives a sence of quality. Expected Results: error message outlining possible errors ~x86
neglected to provide `emerge info` please try latest baselayout/bash
