On 5/29/06, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
The problem is not "how" (which is already dealt with), but "why". I.e., one
could say that some sysfs attributes for SCSI devices are created after the
uevent is sent. That's why we have the WAIT_FOR_SYSFS rule that waits for
"ioerr_cnt".
But it will be certainly better to show where exactly this takes place (i.e.,
the scsi_sysfs_add_sdev() function from drivers/scsi/scsi_sysfs.c). This
function, in its very end, creates all sysfs attributes listed in the
scsi_sysfs_sdev_attrs[] array. Upon examining the contents of that array, it is
clearly seen that the "ioerr_cnt" is really the last attribute created.
(IMO) LFS is for building a Linux system (distribution) not a Linux
Kernel Internals Developers Guide. The information that you mention
above is more suibtable in a "Udev Developers Guide". Most of the
information that was mentioned at the start of the thread falls in the
same category. Now don't get me wrong, I would personally be
interested in that information, but it is not suitable for the LFS
book. As Matt mentioned those would be suitable to be sent upstream or
online magazines.
We install glibc and configure the linker cache. We also mention that
/lib and /usr/lib are automatically added to the linker path. But we
don't point to the part of the code which does that since that is not
relevant for us as system builders.
--
Tushar Teredesai
mailto:[EMAIL PROTECTED]
http://www.linuxfromscratch.org/~tushar/
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
