From: Patrick <nawtyness@gmail.com>
To: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
Cc: Eric Sandeen <sandeen@sgi.com>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com,
Andrew Morton <akpm@osdl.org>,
"Kristofer T. Karas" <ktk@enterprise.bidmc.harvard.edu>,
Jeff Garzik <jgarzik@pobox.com>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: Unknown Issue.
Date: Mon, 13 Dec 2004 19:27:20 +0200 [thread overview]
Message-ID: <3fff1a710412130927268a445a@mail.gmail.com> (raw)
In-Reply-To: <2E314DE03538984BA5634F12115B3A4E01BC417A@email1.mitretek.org>
Hi,
> So your problem was only temporary?
No, it happened randomly though, and all the time. Generally within an hour.
> After I began having the problem, I was trying to edit some files and
> then I got the same errors as you, ie: /usr/bin/vi Input/Ouput error,
> and then I tried to run or edit different programs and files and nothing
> was working.
>
> Were you also forced to re-install, or does this only happen sometimes?
I moved to freebsd as i require the box to actually work, which it
seems to be doing at the moment, even after a bit-o-nailing, but that
still doesn't solve the problem.
P
next prev parent reply other threads:[~2004-12-13 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 17:20 Unknown Issue Piszcz, Justin Michael
2004-12-13 17:27 ` Patrick [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-06 13:33 hard__ware
2004-12-13 18:57 Piszcz, Justin Michael
2004-12-13 17:14 Piszcz, Justin Michael
2004-12-13 17:17 ` Patrick
2004-12-13 17:50 ` Eric Sandeen
2004-12-13 17:56 ` Eric Sandeen
2004-12-13 13:57 Piszcz, Justin Michael
2004-12-13 17:04 ` Eric Sandeen
2004-12-13 17:13 ` Patrick
2004-12-12 21:14 Patrick
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=3fff1a710412130927268a445a@mail.gmail.com \
--to=nawtyness@gmail.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=justin.piszcz@mitretek.org \
--cc=ktk@enterprise.bidmc.harvard.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=sandeen@sgi.com \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.