SUMMARY: odd syntax error in bge.conf

The solution is to either put everything on one line or just don't
escape the new lines.  This is working: 

bash-2.03# cat /platform/sun4u/kernel/drv/bge.conf 
adv_autoneg_cap=0
adv_1000fdx_cap=0
adv_1000hdx_cap=0
adv_100fdx_cap=1
adv_100hdx_cap=0
adv_10fdx_cap=0
adv_10hdx_cap=0;
bash-2.03#

Drew

On Tue, 2004-10-26 at 11:12, Andrew Hall wrote:
> Greetings,
> 
> I setup a new v210 yesterday, and went to force duplex in my bge.conf. 
> I setup bge.conf like so: 
> 
> bash-2.03# cat /platform/sun4u/kernel/drv/bge.conf 
> adv_autoneg_cap=0 adv_1000fdx_cap=0 \
> adv_1000hdx_cap=0 adv_100fdx_cap=1 \
> adv_100hdx_cap=0 adv_10fdx_cap=0 adv_10hdx_cap=0;
> bash-2.03#
> 
> and I get the following error on boot:
> 
> WARNING: Unexpected token '\' on line 1 of
> /platform/sun4u/kernel/drv/bge.conf
> WARNING: Unexpected token '\' on line 2 of
> /platform/sun4u/kernel/drv/bge.conf
> 
> I had to reboot in single user mode and put it all on one line to get
> the box to boot w/ a working network.  Anyone know why this syntax does
> not work?  Seems pretty standard for every unix env I've worked in, in
> the past :).
> 
> Thanks,
> 
> Drew
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers