From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot with 2.4.27 kernel: Network problems
Date: Sun, 30 Jan 2011 13:43:35 +0100 [thread overview]
Message-ID: <877hdmy32g.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110130130131.10c3fcf5@x41> (Simon Kagstrom's message of "Sun, 30 Jan 2011 13:01:31 +0100")
>>>>> "Simon" == Simon Kagstrom <simon.kagstrom@gmail.com> writes:
Hi,
Simon> PING 192.168.1.104 (192.168.1.104): 56 data bytes
Simon> ping: can't create raw socket: Function not implemented
>>
Simon> g2 trunk 6869 Island:# ./busybox telnet localhost
Simon> telnet: socket: Function not implemented
>>
>> Is this with a complete rootfs built by buildroot, or just with the
>> busybox binary copied over to an existing system? If the last, don't
>> forget that uClibc doesn't have a stable ABI, so you need to link
>> busybox statically if you want to run it in a rootfs with another
>> uClibc version.
Simon> I've tried both. I've compiled a static busybox to be able to chroot
Simon> into the buildroot rootfs, but both behave the same way.
So you get this with a statically built busybox as well? Odd. Ping needs
to be setuid root to work. Are you root?
Simon> I know 2.4 is ancient. However, I don't have the sources to even
Simon> attempt a port to 2.6 (a request to Philips have been sent
Simon> though), and also would like to avoid bricking my system, so I'd
Simon> like to stay with the current kernel.
Ok. I would expect a buildroot generated rootfs to work with the 2.4
kernel without too much trouble.
What kind of hardware is this (CPU type)? How have you configured
buildroot?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-01-30 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 7:44 [Buildroot] Buildroot with 2.4.27 kernel: Network problems Simon Kagstrom
2011-01-30 9:36 ` Peter Korsgaard
2011-01-30 12:01 ` Simon Kagstrom
2011-01-30 12:43 ` Peter Korsgaard [this message]
2011-01-30 13:55 ` Simon Kagstrom
2011-01-30 15:11 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877hdmy32g.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox