RamKishoreV wrote:
> Javen Wu <[EMAIL PROTECTED]> wrote:
> > You need ITU image. I assume you are working on X86. Please try the
> > below link:
> > http://www.tools.de/opensource/solaris/itu/newboot/
>
> I looked into the ITU directory. It doesn't contain any scsi device
> specific driver disks. Do we have to do anything different for scsi
> specific driver disks.
I don't think anything special is needed for scsi itu drivers.
We need a standard package that installs the new driver to the
ramdisk root filesystem, and a postinstall script in the package
that registers the new driver with the kernel (add_drv ...).
scsi drivers do register themself in /etc/driver_classes, so you
probably need to use the "-c scsi" option for add_drv...
One thing that might be broken (I havn't verified this yet): I think my
"install.sh" ITU install script needs a small update for current
opensolaris, now that the multiboot binary is gone and grub directly
loads the kernel (the new directboot feature, added when xen / xvm was
integrated). I think this breaks the is_newboot() function that I'm
using in "install.sh":
#
# Detect a "newboot" target OS.
#
is_newboot() {
[ -f $basedir/platform/i86pc/multiboot ] || return 1
[ -d $basedir/boot/grub ] || return 1
return 0
}
> I did not understand bef_name and real_modepath entries in the driver
> disks provided by you. Can you please help me.
realmode drivers are not used any more, since Solaris / OpenSolaris
bootstrap was changed to use GRUB instead of the old boot.bin boot code.
You can ignore bef_name / real_modepath.
_______________________________________________
driver-discuss mailing list
driver-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
