From: "matt" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] DHCP in version 4
Date: Wed, 31 Jul 2002 00:45:03 +0100 [thread overview]
Message-ID: <019001c23823$2190e530$6501a8c0@KIKE> (raw)
In-Reply-To: <Pine.LNX.4.44.0207300939030.2575-100000@harvest.rutgers.edu>
> Thanks to everyone who responded so quickly. A silly mistake about
> ip/httpd/httpd sorry.
I think the quick response it's testament to the ease at typing ip/httpd
and recognising that disk/kfscmd allow didn't cure mine either
both times
:)
M
next prev parent reply other threads:[~2002-07-30 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 13:30 Russ Cox
2002-07-30 13:40 ` Brian Hancock
2002-07-30 23:45 ` matt [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 13:13 Brian Hancock
2002-07-30 13:22 ` matt
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='019001c23823$2190e530$6501a8c0@KIKE' \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
/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).