Friday, 16 December 2011

Need help understanding chroot environment

Need help understanding chroot environment

I am trying to use chroot to configure a broadcom 4306 wireless card. Some of the things I cannot explain is when I do uname -a I get what I think is the kernel from the system rescue disk which I just downloaded, not the kernel in my running system. Another example when I do ifconfig -a :

wlan0 LInk encap: Ethernet HWaddress 00:11:50:0c:e4
Broadcom Multicast MTU:1500 Metric 1
Rx packets =0 there are some more lines but I am hand typing this.

When I try this without rescue disk on my system. I get the following:

ifconfig -a

eth0 Link encap:Ethernet HWaddr 00:0d:56:1f:7b:67
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20d:56ff:fe1f:7b67/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4774 errors:0 dropped:0 overruns:0 frame:0
TX packets:5055 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2760732 (2.6 MiB) TX bytes:1280204 (1.2 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Why is the system rescue disk able to detect my wireless card mac address and my system cannot?

If I continued in chroot and configured the kernel would I get its version when I typed uname -a ?

No comments:

Post a Comment