>On 9/28/06, UNIX admin <[EMAIL PROTECTED]> wrote:
>>
>> On Solaris, generic 32-bit kernel modules (drivers) go under /kernel/drv/;
>> 64-bit kernel modules go under /kernel/drv/amd64/ or /kernel/drv/sparcv9/
>> kernel module .conf file *always* go under /kernel/drv/, *regardless* of
>> whether the module is 3
2- or 64-bit.
>>
>> Finally, CPU or achitecture specific kernel drivers/modules go under
>> /platform/`uname -i`/kernel
/drv/.
>>
>
>I think the convention for drivers for add-in devices is that they
>should be placed in /usr/kernel rather than /kernel - but I think that
>convention is largely ignored.
No; /kernel vs /usr/kernel split is largely to keep "/" small; though
at 2MB vs 38MB is seems that it really doesn't matter much.
Drivers not needed early in boot should go under /usr/kernel;
device drivers needed early in boot should go under /kernel; this includes:
- network drivers
- disk/fabric drivers
- bootable filesystems
- filesystems needed for /usr
- scheduling classes needed for the initial processes.
not needed should be things like:
- audio
- X/framebuffer
- pcfs
but the distinction is largely ignored.
Casper
_______________________________________________
opensolaris-discuss mailing list
[email protected]
