mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nick Bartos" <spam99@2thebatcave.com>
To: "Marcos D. Marado Torres" <marado@student.dei.uc.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/partitions not done updating when init is ran?
Date: Thu, 12 Feb 2004 18:40:25 -0600 (CST)	[thread overview]
Message-ID: <52044.192.168.1.12.1076632825.squirrel@mail.2thebatcave.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402121715310.27694@student.dei.uc.pt>

>
> Well, does it still happen with 2.4.25-rc2 ?
>

yes it does, and it does for 2.6.2 as well.

I did a couple of dmesg's and it looks like the usb device is not being
detected until after init is ran.  I would think that the kernel would
have done all the device detection before running init but I guess not.

Is there a way to check somewhere to make sure it is done detecting
devices?  I cannot just check to see if any of the usb/scsi stuff exists
since some systems may be booting off ide and have no usb bus enabled.

Here are a few of the lines that get added after I wait for a few seconds
in my init script:

+scsi0 : SCSI emulation for USB Mass Storage devices
+  Vendor: OEI-USB2  Model: CompactFlash      Rev: 1.04
+  Type:   Direct-Access                      ANSI SCSI revision: 02
+Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
+SCSI device sda: 250880 512-byte hdwr sectors (128 MB)
+sda: Write Protect is off
+ /dev/scsi/host0/bus0/target0/lun0: p1 p2
+WARNING: USB Mass Storage data integrity not assured
+USB Mass Storage device found at 2




  reply	other threads:[~2004-02-13  0:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12  2:42 Nick Bartos
2004-02-12  4:58 ` Marcos D. Marado Torres
2004-02-12 12:47   ` Nick Bartos
2004-02-12 13:00     ` Nick Bartos
2004-02-12 17:16       ` Marcos D. Marado Torres
2004-02-13  0:40         ` Nick Bartos [this message]
2004-02-13  3:28           ` H. Peter Anvin

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=52044.192.168.1.12.1076632825.squirrel@mail.2thebatcave.com \
    --to=spam99@2thebatcave.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marado@student.dei.uc.pt \
    /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®