On Wed 28 Nov 2007 00:21, Aleksandr Koltsoff <[EMAIL PROTECTED]> writes:
> For some reason can't find the mail that had the below quoted part, but > anyways: > >>> On 11/27/07, Tomi Ollila <[EMAIL PROTECTED]> wrote: >>>> >>>> Why can not the loopback interface be up all the time ?? > > Tested on N810 just a moment ago: > 1) put device in flight mode > 2) /sbin/ifconfig > 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:38 errors:0 dropped:0 overruns:0 frame:0 > TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:14929 (14.5 KiB) TX bytes:14929 (14.5 KiB) > > The lo interface is UP and running. > > If by "inet socks not working" you mean "localhost" not resolving to > 127.0.0.1, then say so. The lo interface seems to be running and well. You're right! By a coincidence I have both 770 and 800 on my desk now, neither running the latest OS version and both, indeed, have localhost interface up like the above (/sbin/ifconfig gives same output) So I remember incorrectly -- the real reason is (probably) that when socket(2) system call is started, these Internet Tablets tries to make internet connection up (either via wlan, or bt-connected phone....) and if that cannot be made, socket(2) fails. There is no way knowing at socket(2) time that user wants to connect(2) 127.0/8 addresses. There is probably good reason to wrap socket() instead of connect(), bind() (and some other system calls.. timeouts maybe...). Well, I'm (quickly) writing this without checking earlier discussion of the matter. The situation is probably well-explained there (?). > ak. Tomi _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
