Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: rms46 on May 16, 2012, 07:29:02 AM
-
To whom it may concern:
May I know how the busybox resolve a domain since /etc/resolv.conf (from dhcp) is empty?
I would like to "wget" an https address and therefore I replaced wget (busybox) with the
real wget. However, the real wget can not resolve since /etc/resolv.conf is empty.
Therefore, I would like to know how/from where the busybox resolves the domain.
Is there any step that I have missed?
Or, should I fill /etc/resolv.conf manually?
Regards,
-
my /etc/resolv.conf is not empty.
-
Hi rms46
My resolve.conf is filled in by the script that sets up my network card, which was created by the
Network applet in ControlPanel. It contains nameserver 192.168.1.1 which is the IP address
of my modem. If you fill in the file yourself, don't forget to add it to your .filetool.lst file so it
gets backed up.
-
Well, since my /etc/resolv.conf IS empty; but wget (of busybox) can resolve the domain.
May I know how that resolves?
I am running TC on a virtualbox (Kubuntu); where everything works/resolves fine,
including apps. I am just wondering, where they resolve the domain...
Hi Rich: should I fill the resolv.conf manually and add it the .filetools.lst?
regards,
-
Hi rms46
I don't know how the busybox version resoves it.
Hi Rich: should I fill the resolv.conf manually and add it the .filetools.lst?
Either that, or better yet, have bootlocal.sh fill it in on startup.
-
All,
Thanks for all the clues. I will fill /etc/resolv.conf manually.
regards,
-
I still have no idea on: why wget (busybox) CAN resolve the domain and why the "real" wget CAN NOT.
However, now "/etc/resolv.conf" exists on the virtual box.
What I did was switching the virtual network adapter position.
The first is attached to the "Host Only Adapter" (vboxnet0); and
the second is attached to the "NAT Adapter".
tc@box:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:27:44:23:3E
inet addr:192.168.56.101 Bcast:192.168.56.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:175 errors:0 dropped:0 overruns:0 frame:0
TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20672 (20.1 KiB) TX bytes:14866 (14.5 KiB)
eth1 Link encap:Ethernet HWaddr 08:00:27:5B:EB:87
inet addr:10.0.3.15 Bcast:10.0.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1528 (1.4 KiB) TX bytes:878 (878.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:600 (600.0 B) TX bytes:600 (600.0 B)
tc@box:~$ cat /etc/resolv.conf
nameserver 10.0.3.2