9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
From: nemo@plan9.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] now for something completely devfs :)
Date: Thu, 10 Jul 2003 10:10:17 +0200	[thread overview]
Message-ID: <bb74b5378b5feef474cd8f0f1d0fa90e@plan9.escet.urjc.es> (raw)
In-Reply-To: <20030709233215.25363.qmail@g.bio.cse.psu.edu>

[-- Attachment #1: Type: text/plain, Size: 255 bytes --]

The kernel does print messages. Doesn't it?
from devfs.c:
			if (waserror()){
				// if a read fails we let the user know and try
				// another device.
				print("#k: mread: (%llx %d): %s\n",
					c->qid.path, i, up->errstr);
				continue;
			}

[-- Attachment #2: Type: message/rfc822, Size: 1958 bytes --]

From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] now for something completely devfs :)
Date: Wed, 09 Jul 2003 19:32:15 -0400
Message-ID: <20030709233215.25363.qmail@g.bio.cse.psu.edu>

| How do you know if a disk in a mirror has died?  The kernel should
| print I/O-error messages on the console.

Maybe /dev/fs/status could do the job, too.

      parent reply	other threads:[~2003-07-10  8:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 15:42 andrey mirtchovski
2003-07-09 16:01 ` andrey mirtchovski
2003-07-09 17:06 ` Fco.J.Ballesteros, nemo
2003-07-09 17:19   ` andrey mirtchovski
2003-07-09 18:43     ` Fco.J.Ballesteros, nemo
2003-07-09 22:52 ` Geoff Collyer
2003-07-09 23:02   ` Geoff Collyer
2003-07-09 23:32   ` Scott Schwartz
2003-07-09 23:44     ` boyd, rounin
2003-07-10  8:10     ` Fco.J.Ballesteros, nemo [this message]

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=bb74b5378b5feef474cd8f0f1d0fa90e@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --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).