From: jmk@plan9.att.com jmk@plan9.att.com
Subject: Problems with #m interface in pcdist
Date: Wed, 11 Oct 1995 09:38:13 -0400 [thread overview]
Message-ID: <19951011133813.dBPNlOhlPQ7AKgew_tMbyJ9AivkJq5e2a86rtnBQqGo@z> (raw)
#m was not included in one of the kernels on the floppies.
it has been added to the as yet unfinished new set.
------ original message follows ------
>From cse.psu.edu!9fans-outgoing-owner Wed Oct 11 06:00:49 EDT 1995
Received: by psuvax1.cse.psu.edu id <34030>; Wed, 11 Oct 1995 05:36:17 -0400
Received: from unios.rz.Uni-Osnabrueck.DE ([131.173.17.7]) by psuvax1.cse.psu.edu with SMTP id <34047>; Wed, 11 Oct 1995 05:19:37 -0400
Received: from thor.informatik.Uni-Osnabrueck.DE ([131.173.161.1]) by unios.rz.Uni-Osnabrueck.DE with SMTP id <189487>; Wed, 11 Oct 1995 10:03:53 +0100
Received: from styx by thor.informatik.Uni-Osnabrueck.DE (4.1/SMI-4.1)
id AA02981; Wed, 11 Oct 95 10:03:51 +0100
Message-Id: <9510110903.AA02981@thor.informatik.Uni-Osnabrueck.DE>
Received: by styx (NX5.67e/NX3.0X)
id AA04919; Wed, 11 Oct 95 10:03:50 +0100
Content-Type: text/plain
Mime-Version: 1.0 (NeXT Mail 3.3 v118.2)
Received: by NeXT.Mailer (1.118.2)
From: Hans-Peter Bischof <bischof@thor.informatik.Uni-Osnabrueck.DE>
Date: Wed, 11 Oct 1995 05:03:47 -0400
To: 9fans@cse.psu.edu
Subject: Re: Problems with #m interface in pcdist
References: <wx91msspto.fsf@stone.lib.uchicago.edu>
Sender: owner-9fans@cse.psu.edu
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
The question is: includes your kernel the cdrom server?
Take a look into /sys/src/9/pc/pc.
-hp
next reply other threads:[~1995-10-11 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-11 13:38 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-10-12 18:37 jmk
1995-10-12 18:14 Tod
1995-10-11 9:03 Hans-Peter
1995-10-11 2:43 Tod
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=19951011133813.dBPNlOhlPQ7AKgew_tMbyJ9AivkJq5e2a86rtnBQqGo@z \
--to=jmk@plan9.att.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 NNTP newsgroup(s).