Originally posted by: bbs.bull

With the installation of RPM coreutils-8.29-1 a link /usr/bin/dirname to /opt/freeware/bin/dirname is made.

But the AIX binary /usr/bin/dirname is used when we want create a spot and we have errors during the creation of a spot :

 Creating SPOT in "/ENIM/resources/spot/machines/sssqsi236-rss" on machine "master" from "sssqsi236-rss_mksysb_1" ...

 Restoring files from BOS image.  This may take several minutes ...

 Checking filesets and network boot images for SPOT "XXXXXXXXXX".
 This may take several minutes ...

warning: 0042-175 c_ckspot: An unexpected result was returned by the
    "/usr/lpp/bos.sysmgt/nim/methods/c_mkbooti" command:

warning: 0042-175 c_mkbooti: An unexpected result was returned by the
    "/usr/sbin/bosboot" command:

/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/usr/sbin/bosboot[6]: dirname:  not found
/tmp/bosboot_16580894_3231/usr/lib/drivers/if_en: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/krpc.ext: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/netinet: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/nfs.netboot.ext: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/nfs.load: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/nfs_kdes.ext: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/planar_pal_chrp: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/vlandd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/bentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/elxentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/goentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/kngentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/kxentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/lnc2entdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/shientdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/rrhbadd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/rrentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/pci_busdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/nmentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/musentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/msnentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/mlxentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/pci/mlxcentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/vrtentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/vdev_busdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/vioentdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/headd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/vnicdd: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/eth_demux: No such file or directory
/tmp/bosboot_16580894_3231/usr/lib/drivers/vrtcore: No such file or directory
Filesystem Helper: Implementation-specific error, code =  (112)

0301-155 bosboot: mkfs failed for /tmp/bosboot_16580894_3231/Bootram.fs.

Originally posted by: AyappanP

This is very bad. Just checked the SPEC file. Due to a mistake in the packaging of 8.29 version, this problem occurs.

We will fix this and publish it again in the AIX Toolbox. Thanks for reporting the issue.

Originally posted by: sanket

We have uploaded the fixed version of coreutils.

Please verify if your issue is fixed.

coreutils-8.29-2.aix6.1.ppc.rpm

This can not fix already broken /usr/bin/dirname by previous coreutil package.

But this will no more overwrite /usr/bin/dirname. 

If you want /usr/bin/dirname which is broken by previous coreutil back then you will have to install the corresponding lpp package.

Sorry for inconvenience and again thanks for reporting the issue.

Originally posted by: kmusil

Is this the lpp package I need to reinstall with the force option?  I have a broken /usr/bin/dirname, I can not get a good mksysb without this. I installed the bad version and it wiped out the /usr/bin/dirname

 lslpp -w /usr/bin/dirname
  File                                        Fileset               Type
  ----------------------------------------------------------------------------
  /usr/bin/dirname                            bos.rte.shell         File

Please advise.  Or can I just copy the executable from another server that's not broke?

Originally posted by: AyappanP

Yes, you can copy it from another server (running similar AIX OS level).