mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>
Cc: Dag Nygren <dag@newtech.fi>, linux-kernel@vger.kernel.org
Subject: Re: Devfs strangeness in 2.4.18
Date: Thu, 6 Jun 2002 17:04:15 -0600	[thread overview]
Message-ID: <200206062304.g56N4Fg05480@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <Pine.LNX.4.44.0206062312530.16968-100000@sharra.ivimey.org>

Ruth Ivimey-Cook writes:
> On Thu, 6 Jun 2002, Dag Nygren wrote:
> 
> >The problems are tha the sg? links doesn't correspond to the real
> >devices shown by /proc/scsi/scsi (Which matches the real situation)
> >sg0 matches the first disk, OK
> >sg1 matches the Medium changer, OK
> >sg2 matches nothing...... There is no target 2 on host1 !!!
> >sg3 matches the DLT tape drive
> >sg4 matches the DAT tape drive
> >
> >The other problem is the st? links.
> >st0 is linked out into nothing ...
> >
> >Seems like 3 host adapters is too much for devfs......
> >Do I need an upgrade ?
> 
> In my experience, devfs doesn't create /dev/sg or /dev/st softlinks.

Indeed. It's devfsd that creates it.

> The only links it creates are from /dev/discs/... to /dev/ide/... or
> /dev/scsi/... as appropriate.
> 
> I would look into the mandrake boot sequence in detail.

Also check that you don't have bogus entries in your dev-state
area. Mandrake had some configuration problems a few months back.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  reply	other threads:[~2002-06-06 23:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06 20:57 Dag Nygren
2002-06-06 22:14 ` Ruth Ivimey-Cook
2002-06-06 23:04   ` Richard Gooch [this message]
2002-06-07  7:46     ` Dag Nygren
2002-06-07 16:34       ` Richard Gooch
2002-06-10  7:43         ` Dag Nygren

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=200206062304.g56N4Fg05480@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=Ruth.Ivimey-Cook@ivimey.org \
    --cc=dag@newtech.fi \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®