From: Scott Schwartz schwartz@galapagos.cse.psu.edu
Subject: questions
Date: Tue, 1 Aug 1995 02:23:04 -0400 [thread overview]
Message-ID: <19950801062304.bMxAcBKkiSnZYHo33bi5UWvIcg0_DMI55WL3mtyzGaA@z> (raw)
Andreas writes:
| Not to be rude, but I see nothing BUT questions here.
| Will there eventually be answers?
In response to the questions I posted I've gotten answers via private
email. Thanks to Jim and Dave for their help!
I was going to post a summary once things were stablized a bit, but
here's a quick rundown:
My ss2 didn't like the new scsi driver. Replacing src/fs/ss/scsi.c
with the code from the first edition fixed the disk problems I was
seeing.
Also, the ss fs gets the clock wrong. In toy.c, I fixed it by
incrementing rtc.year by 68 after reading the clock. After doing that,
I noticed that the terminal version of the kernel fixes this problem
slightly differently, but I haven't tried making that change to the
fileserver yet.
On a (sparc, at least) auth server, boot dies if you tell it that its
ip address is 0.0.0.0; use the real ip number instead.
next reply other threads:[~1995-08-01 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-01 6:23 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-01 6:12 questions Boyd
1995-07-31 5:26 questions Andreas
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=19950801062304.bMxAcBKkiSnZYHo33bi5UWvIcg0_DMI55WL3mtyzGaA@z \
--to=9fans@9fans.net \
/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).