Hi When i tried to run install.sh -I -R /
5 blocks Processing package instance <iscsi> from </tmp/1047> Engines devices(i86pc) 1.0 Copyright 2004 ... Current administration requires that a unique instance of the <iscsi> package be created. However, the maximum number of instances of the package which may be supported at one time on the same system has already been met. No changes were made to the system. Im no more getting this following error that i mentioned: grep: can't open /export/etc/name_to_major can you please help us. Thanks. On Jan 31, 2008 11:38 AM, uddaraju varma <[EMAIL PROTECTED]> wrote: > Hi > > What do you have mounted at /export? > /dev/dsk/c1d0s7 32G 2.3G 29G 8% /export/home > > A root filesystem that should get the > new ITU driver installed? > Does "install.sh -I -R /export" work? > > No, did not work. It popped up the following errors: > ## Installation of part 1 of 1 is complete. > > ## Executing postinstall script. > > grep: can't open /export/etc/name_to_major > > pkgadd: ERROR: postinstall script did not complete successfully > > Basically, What is this /etc/name_to_major in the postinstall script? > What should be done for the postinstall script to be executed successfully. > > Can you please help us with a solution. > > > > On Jan 30, 2008 6:39 PM, Juergen Keil <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > I was able to build the DU.img successfully using ./build. But when im > > > running ./build im getting the following " Warnings ". > > > > > > /itu/beiscsi/iscsi/install/postinstall > > > ## Validating control scripts. > > > WARNING: script <postinstall> may require user interaction at line > > <30>. > > > > Yes, I get this warning, too. > > > > It's because of the postinstall script, which parses a file with > > something > > like this: > > > > exec < /tmp/bge.$$ > > > > while read pci_id desc > > do > > ... > > done > > > > > > I think the warning is printed by the pkgmk(1) command, because it has > > found the "read" shell command and thinks that the postinstall could > > stop here and waits for input by the user on stdin (=user interaction). > > A "postinstall" shouldn't prompt the user, it shouldn't have user > > interaction. > > > > But due to the "exec < some_file" it is not reading from the terminal, > > so it doesn't stop waiting for user input. > > > > > > This kind of warning can be ignored. > > > > > > I'm not sure, maybe the postinstall script could be re-written so that > > pkgmk(1) doesn't warning any more... > > > > > > > Secondly, The system is unable to identify and load the driver in the > > > driver-diskette provided through the floppy during the installation > > > process. So, When i tried to run install.sh in DU.img to check > > weather it > > > loads driver correctly, im getting the following error: > > > > > > ## Installation of part 1 of 1 is complete. > > > ## Executing postinstall script. > > > grep: can't open /export/etc/name_to_major > > > pkgadd: ERROR: postinstall script did not complete successfully. > > > > > > How did you invoke the "install.sh" script? > > "install.sh -R /export" ? > > > > What do you have mounted at /export? A root filesystem that should get > > the > > new ITU driver installed? > > > > Does "install.sh -I -R /export" work? > > > > > > > > > > > > > Can anyone please help. > > > > > Thanks > > > > > > > > > > > > > > > On Jan 28, 2008 5:07 PM, Juergen Keil <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > Hmm, I think the problem starts with the > > > > "Requested size is too small for FAT16" message. > > > > > > > > That message must be from a failed "mkfs -F pcfs ..." command. > > > > > > > > But I'm unable to reproduce this error. I've tried the > > > > following commands (which are part of the make_itu_floppy_image() > > > > function in the "build" script): > > > > > > > > # mkfile 1440k /tmp/floppy.img > > > > # lofiadm -a /tmp/floppy.img /dev/lofi/99 > > > > # mkfs -F pcfs -o > > > > b=msdoslabel,nofdisk,fat=12,spc=1,nsect=18,ntrack=2,size=2880 > > /dev/rlofi/99 > > > > Construct a new FAT file system on /dev/rlofi/99: (y/n)? y > > > > # > > > > > > > > Can you please try these commands on your system? > > > > > > > > Does that report the "Requested size is too small for > > > > FAT16." error? > > > > > > > > > > > > Btw. on which OS version of Solaris are you trying to > > > > build the ITU floppy? OpenSolaris on x86? > > > > > > > > > > > > > > > > > > > > > > > > > Date: Mon, 28 Jan 2008 00:59:14 +0530 > > > > > From: "uddaraju varma" <[EMAIL PROTECTED]> > > > > > To: "Juergen Keil" <[EMAIL PROTECTED]> > > > > > Subject: Re: [driver-discuss] iscsi driver disk > > > > > > > > > > Hi > > > > > > > > > > I just provided pci-ids as be.ids and i've put my driver in > > kernel/drv/ > > > > and > > > > > when i ran ./build im getting the following error's: > > > > > > > > > > > > > > > ** build ITU floppy/cd directory hierarchy > > > > > > > > > > ** merging driver beiscsi > > > > > ## Building pkgmap from package prototype file. > > > > > ## Processing pkginfo file. > > > > > WARNING: parameter <PSTAMP> set to "solaris-devx20080126182311" > > > > > ## Attempting to volumize 0 entries in pkgmap. > > > > > part 1 -- 14 blocks, 6 entries > > > > > ## Packaging one part. > > > > > /itu/beiscsi/beiscsi/pkgmap > > > > > /itu/beiscsi/beiscsi/pkginfo > > > > > /itu/beiscsi/beiscsi/install/copyright > > > > > /itu/beiscsi/beiscsi/install/postinstall > > > > > ## Validating control scripts. > > > > > WARNING: script <postinstall> may require user interaction at line > > <30>. > > > > > ## Packaging complete. > > > > > 6 blocks > > > > > > > > > > ** create ITU floppy/cd image > > > > > Requested size is too small for FAT16. > > > > > mount: I/O error > > > > > umount: warning: /tmp/DU.mnt.691 not in mnttab > > > > > umount: /tmp/DU.mnt.691 not mounted > > > > > rmdir: directory "/tmp/DU.mnt.691": Directory not empty > > > > > ** done, new ITU floppy image: /tmp/DU.img > > > > > > > > > > Can anyone help us please. > > > > > > > > > > Thanks. > > > > > On Jan 24, 2008 8:48 PM, Juergen Keil <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > 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.binboot > > > > code. > > > > > > You can ignore bef_name / real_modepath. > > > > > > > > > > > > _______________________________________________ > > > > > > driver-discuss mailing list > > > > > > driver-discuss@opensolaris.org > > > > > > http://mail.opensolaris.org/mailman/listinfo/driver-discuss > > > > > > > > > > > > Juergen Keil [EMAIL PROTECTED] > > Tools GmbH +49 (228) 9858011 > > Vorgebirgsstraße 37-39 http://www.tools.de > > 53119 BONN > > > > Sitz- und Registergericht HRB Bonn 4026 > > Geschäftsführung Wolfgang Franke & Wolfgang Solfrank > > > > >
_______________________________________________ driver-discuss mailing list driver-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/driver-discuss
