From: Brent Harding <bharding@doorpi.net>
To: blinux-list@redhat.com
Subject: dhcp problems with loopspk and redhat 7.2
Date: Sun, 19 May 2002 19:32:50 -0500 [thread overview]
Message-ID: <3.0.6.32.20020519193250.00a2b8e0@mail.doorpi.net> (raw)
I am on a network in the dorms at college here. Windows works fine online,
(however, barely much faster than a modem when my friend's system downloads
about 10 times my transfer rate). I try to boot linux up, and get dhcpcd
timed out in loopspk, and redhat just hangs at bringing up eth0, probably
unable to get the dhcp connection. I once could use linux on the network
awhile ago, but I goofed up the upgrade from 7.1 to 7.2 and had to
recompile my kernel. How do I get linux on the net so I can go online with
it? I wanted to see if I might be able to pull an iso image down before the
end of school at which time I got to go back to the dreaded dialup.
next reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Brent Harding [this message]
` Janina Sajka
[not found] ` <Pine.LNX.4.44.0205192034430.1448-100000@toccata.rednote.ne t>
` Brent Harding
` Janina Sajka
[not found] ` <Pine.LNX.4.44.0205192301430.1448-100000@toccata.rednote.ne t>
` Brent Harding
` A. R. Vener
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=3.0.6.32.20020519193250.00a2b8e0@mail.doorpi.net \
--to=bharding@doorpi.net \
--cc=blinux-list@redhat.com \
/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).