The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: Re: xPL Developers


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Tivo problems


  • Subject: Re: Tivo problems
  • From: Steve Cooper
  • Date: Tue, 09 Sep 2003 17:56:00 +0000

I get exactly the same info both eth0 and lo running below is the
bash details

bash-2.02# /var/hack/xplhub &
[1] 164
bash-2.02# bash: /var/hack/xplhub: Cannot allocate memory

[1]+ Exit 126 /var/hack/xplhub

bash-2.02# /var/hack/tivoosd &
[1] 163
bash-2.02#
bash-2.02# BUG IN DYNAMIC LINKER ld.so: dynamic-link.h: 46:
elf_get_dynamic_info
: Assertion `! "bad dynamic tag"' failed!

[1]+ Exit 127 /var/hack/tivoosd

--- In <a
href="/group/ukha_xpl/post?postID=_1YaEhW8CQTtxmntVCAfgffXbSc_GzmNgSe-wEfiuhGiSC3Ik0MWbST9zrOzEzXrJ_-b-39LtgD2HdW9N8jccdsjBA">ukha_xpl@xxxxxxx</a>,
"Ian Lowe" <ian@w...> wrote:
> Steve, if you do an ifconfig (no parameters) do you get something
like this?
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
> UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
> RX packets:5993 errors:0 dropped:0 overruns:0 frame:0
> TX packets:5993 errors:0 dropped:0 overruns:0 carrier:0
coll:0
>
> eth0 Link encap:Ethernet HWaddr 00:0B:AD:69:C6:67
> inet addr:192.168.1.3 Bcast:192.168.1.255
Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:4758448 errors:0 dropped:0 overruns:0 frame:0
> TX packets:7167957 errors:0 dropped:0 overruns:0
carrier:0 coll:0
> Interrupt:29
>
> I have seen the problem you have there, when the loopback interface
wasn't
> up (you only get the eth0 interface listed)
>
> Ian.
>







xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.