public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: Network errors
Date: Mon, 10 Feb 2003 14:49:20 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0302101449040.19046-100000@igueths> (raw)
In-Reply-To: <20030210170901.GA23081@tomass.dyndns.org>

Make sure you also have inetd installed, as it is called upon somewhere in
your rc scripts.

May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.

On Mon, 10 Feb 2003, Thomas Stivers wrote:

> Did you do a full install of slackware? It looks like you don't have
> some networking packages. You will need either the dhcp package or the
> dhcpcd package for setting up your ip address. The slackware
> initialization files use dhcpcd, so you probably want that one. Once
> this is installed you should be able to type (as root) dhcpcd and get
> things running.
>
> On 02/10/03 11:23 AM -0500, erik burggraaf wrote:
> > Greetings all.  I decided to get a little work done on my toy linux box today, and the subject of my curiosity happened to be network connectivity.  Specificly, I wanted to make slackware see and use my cable modem.
> > In netconfig, I entered my host and domain as requested, using my dynamic host address for the domain.  Then I chose the second option, which said it was recomended for cable and DSL users that had a dynamic IP.  Then it asked for a DHCP host if any.  I called cogeco and they said they didn't use it.  Then, of course, I let it autodetect my card, and just like that I was in.
> > Then I hooked up the cable modem to the computer, and rebooted.
> > When I try to get any address using the links command, it says host not found.  So, I rebooted, and had a listen to the litiny of startup messages that here-to-fore, I ignored.   I copied some of this business down, and wondered if it's relavent?  How do I fix the errors below? are they responsible for my not being able to connect to the net?
> > ***Begin output from linux***
> > 8139too fast ethernet driver 0.9.24
> > PCI: assigned IRQ 10for device 00:0B.0
> > eth0: RealTekRTL8139 fast ethernet at 0xc3823000, 00:40:f4:15:12:3d,IRQ 10
> > scsi0 : SCSI host adapter emulationfor IDE atapi devices
> > Using /etc/random-seed to initialize /dev/urandom.
> > Init: entering RunLevel:3
> > Going Multiuser...
> > Attempting to configure eth0 by contacting a DHCP server...
> > /etc/rc.d/rc.M: /sbin/dhcpcd:No such file or directory
> > Mounting remote (nfs) file systems: /sbin/mount -a -t nfs
> > Mounting remote (smb) file systems: /sbin/mount -a -t smbfs
> > Starting sysclogd daemons: /usr/sbin/syslogd /usr/sbin/klogd-c 3 -x
> > Activating IPV for packet forwarding:
> > Warning:/usr/sbin/inetd not found.
> > I'd be greatful for any direction on this you can give me.
> > Thanks,
> > Erik
>
> --
> Thomas Stivers
> e-mail: stivers_t@tomass.dyndns.org
> PGP Public Key ID: 45CBBABD
> http://stivers-home.dyndns.org
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 erik burggraaf
 ` Thomas Stivers
   ` Igor Gueths [this message]
 ` Patrick Turnage
 igueths

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=Pine.LNX.4.44.0302101449040.19046-100000@igueths \
    --to=igueths@attbi.com \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).