| To: | "'brett holcomb'" <brettholcomb@xxxxxxxxxxx>, devfs@xxxxxxxxxxx |
|---|---|
| Subject: | RE: SCSI Tapes and devfs |
| From: | Borzenkov Andrey <Andrey.Borzenkov@xxxxxxxxxxx> |
| Date: | Fri, 17 Jan 2003 09:27:32 +0300 |
| Importance: | Normal |
| In-reply-to: | <web-1837187@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | devfs-bounce@xxxxxxxxxxx |
> > Okay, then what is supposed to tell devfs that there is > now a scsi tape drive/changer ready to use. This is the sole responsibility of corresponding driver. If we speak about SCSI tape, this happens in driver attach method. In the case > of st being a module and me loading it at startup time > causes devfs to see it. But what SHOULD trigger this if > the st support is built into a kernel - what is the > mechanism there for Linux? > The same modulo bugs. St's attach should run in exactly the same fashion and register tape (if found). Are you sure you have not built driver for your SCSI adapter as module? Then when st is initialized at boot time it can't find any tapes because there is no adapter yet. This would perfectly explain why tape was not there initially but appeared later (due to module autoloading). -andrey |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: SCSI Tapes and devfs, Borzenkov Andrey |
|---|---|
| Next by Date: | RE: SCSI Tapes and devfs, Steven Lembark |
| Previous by Thread: | Re: SCSI Tapes and devfs, brett holcomb |
| Next by Thread: | Re: SCSI Tapes and devfs, brett holcomb |
| Indexes: | [Date] [Thread] [Top] [All Lists] |