/titanic_41/usr/src/pkg/manifests/ |
H A D | system-flash-fwflash.mf | 42 dir path=usr/lib/fwflash/identify 47 file path=usr/lib/fwflash/identify/hermon.so 48 file path=usr/lib/fwflash/identify/sd.so 49 file path=usr/lib/fwflash/identify/ses.so 50 file path=usr/lib/fwflash/identify/tavor.so 62 link path=usr/lib/fwflash/identify/sgen.so target=ses.so
|
H A D | network-iscsi-initiator.mf | 50 driver name=iscsi class=scsi-self-identify perms="* 0600 root sys"
|
H A D | system-kernel.man9e.inc | 35 file path=usr/share/man/man9e/identify.9e
|
/titanic_41/usr/src/cmd/fm/dicts/ |
H A D | GMCA.po | 41 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 57 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 73 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 89 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 105 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 121 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 137 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 153 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 169 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 185 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… [all …]
|
H A D | PCI.po | 41 msgstr "Ensure latest drivers and patches are installed. Use fmdump -v -u <EVENT_ID> to identify t… 57 …ocedure to replace the affected device. Use fmdump -v -u <EVENT_ID> to identify the device or con… 73 msgstr "Use fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s)or driver(s).\n\nCheck for… 89 msgstr "Use fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).\n\nSchedule a repair pro… 105 msgstr "Use fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s)or driver(s).\n\nCheck for… 121 msgstr "Use fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).\n\nSchedule a repair pro… 137 msgstr "Use fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s)or driver(s).\n\nCheck for… 153 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t… 169 …a repair procedure to replace the affected device. Use fmadm faulty to identify the device and bu… 185 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… [all …]
|
H A D | AMD.po | 57 … procedure to replace the affected memory module. Use 'fmadm faulty' to identify the memory module… 73 … procedure to replace the affected memory module. Use 'fmadm faulty' to identify the memory module… 89 …epair procedure to replace the affected memory module. Use 'fmadm faulty' to identify the module." 105 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 121 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 137 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 153 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 169 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 185 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 201 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… [all …]
|
H A D | INTEL.po | 41 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 57 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 73 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 89 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 105 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 121 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 137 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 153 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 169 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 185 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… [all …]
|
H A D | PCIEX.po | 41 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t… 57 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… 73 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… 89 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… 105 …a repair procedure to replace the affected device. Use fmadm faulty to identify the device and bu… 121 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… 137 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… 153 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… 169 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… 185 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… [all …]
|
H A D | SUN4U.po | 58 … procedure to replace the affected memory module. Use 'fmadm faulty' to identify the memory module… 74 …ocedure to replace the affected memory module. Use fmdump -v -u <EVENT_ID> to identify the module." 266 …e a repair procedure to replace the affected CPU. Use fmdump -v -u <EVENT_ID> to identify the CPU." 602 …rocedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or con… 618 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of … 634 …rocedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or con… 650 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of … 666 …rocedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or con… 682 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of … 698 …rocedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or con… [all …]
|
H A D | STORAGE.po | 89 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 105 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 121 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 137 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 153 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 169 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 185 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 201 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 217 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 249 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… [all …]
|
H A D | SUN4.po | 43 …rocedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or con… 91 …-eV -u\nEVENT_ID to collect information to \nhelp Sun Service personnel identify the device in nee… 107 …rocedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or con… 123 msgstr "Ensure latest driver and patch are installed. Use fmdump -v -u <EVENT_ID> to identify the … 155 …rocedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or con… 171 msgstr "Ensure latest driver and patch are installed. Use fmdump -v -u <EVENT_ID> to identify the … 203 …rocedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or con… 235 …rocedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or con… 251 …rocedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or con… 267 …-eV -u\nEVENT_ID to collect information to \nhelp Sun Service personnel identify the device in nee…
|
H A D | FMD.po | 114 msgstr "Use fmdump -v -u <EVENT-ID> to identify the repaired components." 130 msgstr "Use fmadm faulty to identify the repaired components, and any suspects that still need to b… 146 msgstr "Use fmdump -v -u <EVENT-ID> to identify the repaired components."
|
H A D | DISK.po | 42 …epair procedure to replace the affected disk.\nUse fmdump -v -u <EVENT_ID> to identify the disk.\n" 74 …epair procedure to replace the affected disk.\nUse fmdump -v -u <EVENT_ID> to identify the disk.\n"
|
H A D | SUNOS.po | 89 …rocedure to replace the affected device. Use fmdump -v -u <EVENT_ID> to identify the device or con… 137 …rocedure to replace the affected device. Use fmdump -v -u <EVENT_ID> to identify the device or con… 153 …rocedure to replace the affected device. Use fmdump -v -u <EVENT_ID> to identify the device or con… 169 msgstr "Ensure latest drivers and patches are installed. Use fmdump -v -u <EVENT_ID> to identify th…
|
/titanic_41/usr/src/cmd/fwflash/plugins/ |
H A D | Makefile.targ | 61 $(HERMON-MELLANOX_LIB):= DYNFLAGS += -R/usr/lib/fwflash/identify 62 $(HERMON-MELLANOX_LIB):= LDLIBS += -L. $(ROOT)/usr/lib/fwflash/identify/hermon.so
|
/titanic_41/usr/src/cmd/fwflash/ |
H A D | Makefile.com | 40 ROOTUSRLIBFWFLASHIDF= $(ROOTUSRLIBFWFLASH)/identify
|
/titanic_41/usr/src/cmd/mdb/common/mdb/ |
H A D | mdb_main.c | 387 int (*identify)(const char *, int *); in identify_xvm_file() local 392 identify = (int (*)())dlsym(RTLD_NEXT, "xkb_identify"); in identify_xvm_file() 394 if (identify == NULL) in identify_xvm_file() 397 return (identify(file, longmode)); in identify_xvm_file()
|
/titanic_41/usr/src/cmd/zic/ |
H A D | tzselect.po | 13 msgid "Please identify a location so that time zone rules "
|
/titanic_41/usr/src/cmd/tic/ |
H A D | mapfile-intf | 42 # tic interposes on progname[], so identify this as an interposer.
|
/titanic_41/usr/src/cmd/infocmp/ |
H A D | mapfile-intf | 42 # infocmp interposes on progname[], so identify this as an interposer.
|
/titanic_41/usr/src/man/man9e/ |
H A D | Makefile | 39 identify.9e \
|
/titanic_41/usr/src/cmd/sgs/elfedit/modules/common/ |
H A D | ehdr.msg | 445 used to identify it as being an ELF object. This information\n\ 454 identify it as an ELF object.\n" 460 used to identify it as being an ELF object. This information\n\ 469 fail to identify it as an ELF object.\n" 475 used to identify it as being an ELF object. This information\n\ 484 fail to identify it as an ELF object.\n" 490 used to identify it as being an ELF object. This information\n\ 499 fail to identify it as an ELF object.\n"
|
/titanic_41/usr/src/cmd/print/printmgr/com/sun/admin/pm/client/ |
H A D | help-l10n-comments.txt | 38 each Article's Tag to form the keys which identify the 41 The strings used as keys to identify the various parts of the 47 The suffixes used to identify the Tag, Title, Content, Keywords,
|
/titanic_41/usr/src/cmd/Adm/ |
H A D | mime.types | 2 #Do not delete the above line. It is used to identify the file type.
|
/titanic_41/usr/src/cmd/lp/model/ |
H A D | netstandard | 227 # identify them here. 275 # identify them here.
|