linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: ian reinhart geiser <geiseri@msoe.edu>
To: Rand <rand@mail.org>,
	"linuxppc-dev@lists.linuxppc.org"
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: nsfd problem after building 2.2.10
Date: Thu, 01 Jul 1999 11:55:42 -0500	[thread overview]
Message-ID: <377B9D8E.FFDC6EB2@msoe.edu> (raw)
In-Reply-To: 199907011645.MAA23749@mail1.lig.bellsouth.net


Rand wrote:

> ian reinhart geiser geiseri@msoe.edu
>
> Thanks Ian,
>   Maybe someone will have an answer..or maybe there is a bug in 2.2.10.
> I tried building NFS and NFSD both with modules and not and get the error
> in either case.  Not using nfs so it doesn't really matter, but I'm
> curious as to why it doesn't work.  My kernel is about 1MG smaller than
> the one delivered on the CD, so there is lots of other things that they
> selected that I didn't need.  Maybe one of them has something to do with
> this.
>
> Rand
>

    i have noticed that network transfers are also not as stable as they use to
    be.  i kernel paniced when my rommate tried to FTP a 40Meg file off of my
    box.  it finished the download and died....


    i am startig to think it is network related



[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

           reply	other threads:[~1999-07-01 16:55 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <199907011645.MAA23749@mail1.lig.bellsouth.net>]

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=377B9D8E.FFDC6EB2@msoe.edu \
    --to=geiseri@msoe.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=rand@mail.org \
    /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).