linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Roberts <tjroberts@lucent.com>
To: Daris Nevil <Daris.Nevil@snmc.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Do you have your minimum ramdisk image which can provide basic network services ?
Date: Wed, 31 May 2000 08:45:37 -0500	[thread overview]
Message-ID: <39351781.B4B61265@lucent.com> (raw)
In-Reply-To: 39340AC7.689BFF86@snmc.com


Daris Nevil wrote:
> The quick-and-dirty way of enabling your loopback device
> is:
>     ifconfig lo 127.0.0.1

Yes, I did that; I get:
	$ ifconfig lo 127.0.0.1
	127.0.0.1: Resolver Error 0 (no error)
	Usage: ifconfig [-a] [-i] [-v] interface
	                [inet address]
	                [hw] [ax25 address]
	                [metric NN] [mtu NN]
	                [trailers] [-trailers]
	                [arp] [-arp]
	                [netmask aa.bb.cc.dd]
	                [dstaddr aa.bb.cc.dd]
	                [mem_start NN] [io_addr NN] [irq NN]
	                [[-] broadcast [aa.bb.cc.dd]]
	                [[-]pointopoint [aa.bb.cc.dd]]
	                [up] [down] ...

I have no idea what "Resolver error 0" is, nor why ifconfig thinks
that is an invalid command line....

	$ ping 127.0.0.1
	ping: unknown protocol icmp.

I think I need to be running inetd to implement the ping protocol, and
so far I have been unable to find a PowerPC image of inetd.

My /etc/protocols has icmp listed (copied from a working i386 linux).
I may have more serious errors, like incompatible libraries....


Tom Roberts	tjroberts@lucent.com

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-05-31 13:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-29  7:27 Do you have your minimum ramdisk image which can provide basic network services ? SangTae Ha
2000-05-29  7:56 ` Wolfgang Denk
2000-05-30 18:29 ` Tom Roberts
2000-05-30 18:39   ` Daris Nevil
2000-05-31 13:45     ` Tom Roberts [this message]
2000-05-31 15:35       ` Daris Nevil

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=39351781.B4B61265@lucent.com \
    --to=tjroberts@lucent.com \
    --cc=Daris.Nevil@snmc.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).