Hello all,
having spent one evening with the 3.1-beta2 image
and Qemu, I can report on one issue for this pair,
a matter which is working correctly if I make a
test with an identically configured 3.0-beta3 image.
Yes, there is a release of 3.0, but I happened
to have a handy copy of the older beta3!
Qemu is started using
qemu -fda /tmp2/Bering-uClibc_3.1-beta2.bin \
-net nic -net user \
-net nic,vlan=1,model=rtl8139 -net user
and Bering has been configured to load the correct
modules.
What happens is that ifup/dhcpcd never configures eth0/ne2k_pci,
although "ip ad sh" proves it to be present. However, a manual
command "# dhcpcd eth0" does indeed accomplish the correct
configuration step. Also, when issuing "# ifdown eth" immediately
after booting time with this malfunctioning dhcpcd service,
a strange message appears:
"ifdown: don't [sic] seem to have all the variables
for eth0/inet"
I have not managed to find the cause of this problem with
dhcpcd, but in contrast, the 3.0-beta3 image is fully
functional in this respect. Clearly, we do not normally
run Bering in Qemu, but this experiment does pinpoint
a definite issue in Bering-3.1-beta2.
Best regards and Merry Christmas to you all,
M E Andersson
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
