Public SourceMage Discussion List

[Hamish Greig <hgreig AT bigpond.net.au>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 11 Jul 2003 16:44, The Well-Beloved Bard wrote:
> Careful, Andrew - no need to flame someone who's trying to share knowledge
> here.  I know devfsd makes the links for you.  However, I have run into a
> problem with devfsd that I thought other people might want to be aware of
> so that it wouldn't bite them like it did me.
>

I think it has just been a long week for all of us, i hope you can forgive 
Andrews bluntness

> Devfsd _only_ creates links for the devices it knows about.  So, if it
> doesn't know about the device, it can't make a link.  If the SCSI driver
> is compiled into the kernel, it's not loaded when devfsd creates its
> links.  Since it's not loaded, /dev/sdAX aren't populated, so devfsd
> doesn't do anything with it.  Because devfs is mounting on /dev, it
> "hides" the /dev/sdAX entries, so when you get to the kernel (that has the
> driver statically compiled in), the driver tries to assign /dev/sdAX
> values to the drives connected to the SCSI adapter, but can't, because
> those special block devices are "hidden" by the mount, and aren't visible
> to the driver.
sorry i responded earlier this morning but i must have used the wrong reply 
and only andrew got my answer.
The  solution to this is to mount devfs at boot not via mount scripts then 
devfsd (if used for compatibility) will see existing kernel devices and make 
links as necessary.
I used to use only statically compiled aic7xxx and devfsd and had no such 
problems. 
Hamish
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/Dl/48fSufZR6424RAofgAJ0ZlqtiQxkTmE6U83gtQvqHXDRDiwCePHrf
h4DncS13BlLldPaO+vwysfU=
=xiil
-----END PGP SIGNATURE-----