test:
admin = false
admgroups = system
ttys = !/dev/pts/0,ALL
結(jié)果是用戶test可以在除了pts/0以外的所有端口登錄,當(dāng)test在pts/0登錄時(shí),
系統(tǒng)報(bào)錯(cuò)You are not allowed to access the system via this terminal.
IBM pSeries和 RS/6000 哪些型號可以安裝SuSE linux?
環(huán)境 平臺:RS
問題 IBM pSeries和 RS/6000 哪些型號可以安裝SuSE linux?
解答 到2002年6月4日為止,RS6/6000 B50,150 和F50可以安裝SuSE Linux for PowerPC Version 6.4 (支持32位內(nèi)核);目前pSeries 和 RS/6000 中除p680外均可安裝SuSE Linux Enterprise Server (SLES) Version 7(支持64位內(nèi)核)。
高速的可靠的移動(dòng)網(wǎng)絡(luò)使得移動(dòng)用戶或IT人員能夠使用一個(gè)無線的構(gòu)架來管理其應(yīng)用和系統(tǒng)。AIX無線系統(tǒng)管理器(Wireless System Manager for AIX [WSMA])就是一個(gè)無線的系統(tǒng)服務(wù),它允許對系統(tǒng)資源進(jìn)行安全的和保密的管理(如 CPU, 磁盤, 設(shè)備和應(yīng)用)。
連接層的安全是通過利用PPP協(xié)議的Remote Access Service (RAS)來訪問企業(yè)的intranet。請參考如下的示意圖來理解不同的協(xié)議、安全組件、WAP手機(jī)間的關(guān)系、網(wǎng)關(guān)和在無線網(wǎng)絡(luò)中的被管理的服務(wù)器。
環(huán)境 RS6000
問題 夏時(shí)制問題
解答 每年四月到八月,AIX會(huì)缺省使用夏時(shí)制,可以用echo $TZ看時(shí)區(qū)來判斷,時(shí)區(qū)以DT結(jié)尾的就使用了夏時(shí)制。如果不想用,可以通過smit--system environment--change show date and time---change time zone using system defined values來改變,在彈出的USE DAYTIME SAVING對話框中選擇No,選好相應(yīng)的時(shí)區(qū)后重啟機(jī)器既可。
環(huán)境 產(chǎn)品: AIX
平臺: RS
軟件版本: AIX V4
問題 客戶有一個(gè)自己開發(fā)的應(yīng)用,其中需要對ctrl+y的響應(yīng),來完成特定功能。
但當(dāng)客戶實(shí)現(xiàn)時(shí),卻發(fā)現(xiàn)一按ctrl+y程序就退出了。
解答 客戶使用的是telnet終端,其中需要對pty的屬性進(jìn)行修改。
#smit pty
Change / Show Characteristics of the PTY
STATE to be configured at boot time ---------------available -----+
Maximum number of Pseudo-Terminals ---------[256]---------------- #
Maximum number of BSD Pseudo-Terminals -----[16]
其中并沒有象tty一樣的許多選項(xiàng):
#smit tty
POSIX special control characters:
INTERRUPT character ------------------------[^c]
QUIT character -----------------------------[^\]
ERASE character ----------------------------[^h]
KILL character -----------------------------[^u]
END OF FILE character ----------------------[^d]
END OF LINE character ----------------------[^@]
2nd END OF LINE character ------------------[^?]
DELAY SUSPEND PROCESS character ------------[^y]
SUSPEND PROCESS character ------------------[^z]
LITERAL NEXT character ---------------------[^v]
START character ----------------------------[^q]
xlC.aix43.rte 4.0.2.1 COMMITTED C Set ++ Runtime for AIX 4.3
xlC.cpp 4.3.0.1 COMMITTED C for AIX Preprocessor
xlC.msg.en_US.cpp 4.3.0.1 COMMITTED C for AIX Preprocessor
xlC.msg.en_US.rte 4.0.2.0 COMMITTED C Set ++ Runtime
xlC.msg.zh_CN.rte 4.0.2.0 COMMITTED C Set ++ Runtime
xlC.rte COMMITTED 4.0.2.0 COMMITTED C Set ++ Runtime
內(nèi)容
提要 本文將就AIX Affinity with Linux的發(fā)展以及在AIX操作系統(tǒng)下如何進(jìn)行Linux的開發(fā)和如何將自由開發(fā)的Linux應(yīng)用移植到AIX操作系統(tǒng)做介紹,目的是讓更多的朋友在AIX系統(tǒng)平臺上使用Linux, 并同時(shí)感受到AIX操作系統(tǒng)在整體性能上的魅力。我們期待著有更多更好的Linux應(yīng)用被移植到AIX操作平臺,使AIX操作系統(tǒng)更加豐富多彩,讓我們工作得更輕松自如。
第一部分 AIX Affinity with Linux 的發(fā)展情況
第二部分 AIX Affinity 的其本原理介紹
第三部分 AIX Toolbox for Linux 最新版的獲得、安裝、包含工具和基本使用
第四部分 對開發(fā)的建議
說明 任何機(jī)型,操作系統(tǒng) AIX 4.3.3 or AIX 5L
正文
第一部分 AIX Affinity with Linux 的發(fā)展情況
IBM對AIX Affinity with Linux的發(fā)展分為以下兩個(gè)階段。
第一個(gè)階段,發(fā)布AIX Toolbox for Linux Applications, 它主要包含GNU和其他一些常用開發(fā)工具,來幫助開發(fā)人員在AIX系統(tǒng)上編譯程序,并在兩種行業(yè)內(nèi)開放性最好的操作系統(tǒng)平臺,即AIX和Linux之間,進(jìn)行平滑技術(shù)移植。由于應(yīng)用程序運(yùn)行于AIX環(huán)境中,因此客戶可以同時(shí)得到Linux的靈活性和AIX操作系統(tǒng)的先進(jìn)性能,包括工作負(fù)載管理、先進(jìn)系統(tǒng)管理工具以及高安全性。
第二個(gè)階段是,在最新發(fā)布的AIX 5L Version 5.1 操作系統(tǒng)中提供更多的兼容Linux的API和頭文件,來支持源文件的兼容性,使兩個(gè)不同操作系統(tǒng)有更強(qiáng)的互操作性,從而達(dá)到更高程度的兼容。
那么我們能用AIX Affinity for Linux做什么呢?
1。在AIX系統(tǒng)上使用眾多Linux上開發(fā)的自由軟件,例如,運(yùn)行流行的 Gnome
and KDE 圖形桌面,運(yùn)行其他的多媒體工具,等等。
2。用功能強(qiáng)大的RedHat Package Manager包工具管理應(yīng)用。
3。在AIX 系統(tǒng)上,使用GNU和Linux開發(fā)工具進(jìn)行新應(yīng)用的開發(fā)。
第二部分 AIX Affinity 的其本原理介紹
AIX Affinity with Linux的目的并不是在系統(tǒng)中提供一個(gè)模擬層供Linux應(yīng)用來運(yùn)行,它的意義在于通過重新編譯Linux應(yīng)用后,得到AIX的兼容的二進(jìn)制本地代碼,并能使用所有系統(tǒng)的特性,如可靠性、擴(kuò)展性、以及可用性。這就是說,我們提供了一個(gè)強(qiáng)大的跨平臺編譯器以及眾多的兼容API來保證Linux應(yīng)用在AIX系統(tǒng)上的成功移植。
由于AIX的設(shè)計(jì)開發(fā)從網(wǎng)絡(luò)、主機(jī)硬件系統(tǒng),到操作系統(tǒng)完全遵守開放系統(tǒng)的原則,所以在目前的AIX 4.3.3 和 AIX 5L Version 5.0, 使用AIX Toolbox for Linux,只需通過簡單的編譯就能在AIX平臺上實(shí)現(xiàn)Linux的很多應(yīng)用。這樣,我們就不用浪費(fèi)許多人力、物力去重新開發(fā)很多已經(jīng)很成熟的應(yīng)用。我們不斷地重用經(jīng)典代碼,就可以把我們有限的精力投入到更精彩、更需要的地方。 當(dāng)使用AIX Affinity with Linux時(shí),我們還會(huì)想到的它對性能的影響。AIX Affinity with Linux在設(shè)計(jì)階段,就希望提供最優(yōu)化的性能給應(yīng)用,其中包括讓Linux應(yīng)用和本地應(yīng)用享有同樣訪問資源的權(quán)利。尤其是AIX 5L Version 5.1操作系統(tǒng),會(huì)提供更高級別的應(yīng)用與操作系統(tǒng)間的兼容性。當(dāng)我們考慮性能時(shí),還應(yīng)該想到我們要開發(fā)什么樣的應(yīng)用,前端的還是后臺的。后臺的大型應(yīng)用還是比較適合AIX應(yīng)用,但前端的人機(jī)界面用Linux則更能發(fā)揮其特長,也減少了可能的性能影響。
c20 Kernel debug program activated. An unexpected system halt has occured, and you have configured the system
to enter the kernel debug program instead of performing a dump.
---------Built-In Self Test (Bist) Indicators---------
100 BIST completed successfully. Control was passed to IPL ROS.
101 BIST started following RESET
102 BIST started following Power-on Reset
103 BIST could not determine the system model number.
104 Equipment conflict. BIST could not find the CBA.
105 BIST could not read the OCS EPROM.
106 BIST detected a module error.
111 OCS stopped. BIST detected a module error.
112 A checkstop occured during BIST.
113 BIST checkstop count is greater than 1.
120 BIST starting a CRC check on the 8752 EPROM.
121 BIST detected a bad CRC in the first 32K of the OCS EPROM.
122 BIST started a CRC check on the first 32K of the OCS EPROM.
123 BIST detected a bad CRC on the OCS area of NVRAM.
124 BIST started a CRC check on the OCS area of NVRAM.
125 BIST detected a bad CRC on the time-of-day area of NVRAM.
126 BIST started a CRC check on the time-of-day area of the NVRAM.
127 BIST detected a bad CRC on the 8752 EPROM.
130 BIST presence test started.
140 BIST failed: procedure error
142 BIST failed: procedure error
143 Invalid memory configuration.
144 BIST failed; procedure error.
151 BIST started AIPGM test code.
152 BIST started DCLST test code.
153 BIST started ACLST test code.
154 BIST started AST test code.
160 Bad EPOW Signal/Power status signal
161 BIST being conducted on BUMP I/O
162 BIST being conducted on JTAG
163 BIST being conducted on Direct I/O
164 BIST being conducted on CPU
165 BIST being conducted on DCB and Memory
166 BIST being conducted on interrupts
170 BIST being conducted on 'Multi-Processor
180 BIST logout failed.
182 BIST COP bus not responding
185 A checkstop condition occured during the BIST
186 System logic-generated checkstop (Model 250 only)
187 Graphics-generated checkstop (Model 250)
195 BIST logout completed.
888 BIST did not start
------- Power-On Self Test -------
200 IPL attempted with keylock in the SECURE position.
201 IPL ROM test failed or checkstop occured (irrecoverable)
202 IPL ROM test failed or checkstop occured (irrecoverable)
203 Unexpected data storage interrupt.
204 Unexpected instruction storage interrupt.
205 Unexpected external interrupt.
206 Unexpected alignment interrupt.
207 Unexpected program interrupt.
208 Unexpected floating point unavailable interrupt.
209 Unexpected SVC interrupt.
20c L2 cache POST error. (The display shows a solid 20c for 5 seconds
210 Unexpected SVC interrupt.
211 IPL ROM CRC comparison error (irrecoverable).
212 RAM POST memory configuration error or no memory found (irrecoverable).
213 RAM POST failure (irrecoverable).
214 Power status register failed (irrecoverable).
215 A low voltage condition is present (irrecoverable).
216 IPL ROM code being uncompressed into memory.
217 End of bootlist encountered.
218 RAM POST is looking for 1M bytes of good memory.
219 RAM POST bit map is being generated.
21c L2 cache is not detected. (The display shows a solid 21c for 5 sec)
220 IPL control block is being initialized.
221 NVRAM CRC comparison error during AIX.
IPL(Key Mode Switch in Normal mode).
Reset NVRAM by reaccomplishing IPL in Service mode. For systems with an internal, direct-bus-attached(DBA)disk,IPL
ROM attempted to perform an IPL from that disk before halting with this three-digit display value.
222 Attempting a Normal mode IPL from Standard I/O planar attached devices specified in NVRAM IPL Devices List.
223 Attempting a Normal mode IPL from SCSI attached devices specified in NVRAM IPL Devices List.
Note: May be caused by incorrect jumper setting for external SCSI devices or by incorrect SCSI terminator.
REFER FFC B88
224 Attempting a Normal mode restart from 9333 subsystem device specified in NVRAM device list.
225 Attempting a Normal mode IPL from IBM 7012 DBA disk attached devices specified in NVRAM IPL Devices List.
226 Attempting a Normal mode restart from Ethernet specified in NVRAM device list.
227 Attempting a Normal mode restart from Token Ring specified in NVRAM device list.
228 Attempting a Normal mode IPL from NVRAM expansion code.
229 Attempting a Normal mode IPL from NVRAM IPL Devices List; cannot IPL from any of the listed devices, or there are
no valid entry in the Devices List.
22c Attempting a normal mode IPL from FDDI specified in NVRAM IPL device list.
230 Attempting a Normal mode restart from adapter feature ROM specified in IPL ROM devices list.
231 Attempting a Normal mode restart from Ethernet specified in IPL ROM devices list.
232 Attempting a Normal mode IPL from Standard I/O planar attached devices specified in Rom Default Device List.
233 Attempting a Normal mode IPL from SCSI attached devices specified in IPL ROM Default Device List.
234 Attempting a Normal mode restart from 9333 subsystem device specified in IPL ROM device list.
235 Attempting a Normal mode IPL from IBM 7012 DBA disk attached devices specified in IPL ROM Default Device List.
236 Attempting a Normal mode restart from Ethernet specified in IPL ROM default devices list.
237 Attempting a Normal mode restart from Token Ring specified in IPL ROM default device list.
238 Attempting a Normal mode restart from Token Ring specified by the operator.
239 System failed to restart from the device chosen by the operator.
23c Attempting a normal mode IPL from FDDI specified in IPL ROM device list.
240 Attempting a Service mode restart from adapter feature ROM.
241 Attempting a Normal mode IPL from devices specified in the NVRAM IPL Devices List.
242 Attempting a Service mode IPL from Standard I/O planar attached devices specified in NVRAM IPL Devices List.
243 Attempting a Service mode IPL from SCSI attached devices specified in NVRAM IPL Devices List.
244 Attempting a Service mode restart from 9333 subsystem device specified in NVRAM device list.
245 Attempting a Service mode IPL from IBM 7012 DBA disk attached devices specified in NVRAM IPL Devices List.
246 Attempting a Service mode restart from Ethernet specified in NVRAM device list.
247 Attempting a Service mode restart from Token Ring specified in NVRAM device list.
248 Attempting a Service mode IPL from NVRAM expansion code.
249 Attempting a Service mode IPL from NVRAM IPL Devices List; cannot IPL from any of the listed devices, or there areno valid entries in the Devices List.
24c Attempting a service mode IPL from FDDI specified in NVRAM IPL device list.
250 Attempting a Service mode restart from adapter feature ROM specified in IPL ROM device list.
251 Attempting a Service mode restart from Ethernet specified in IPL ROM device list.
252 Attempting a Service mode IPL from standard I/O planar attached devicesspecified in ROM Default Device List.
253 Attempting a Service mode IPL from SCSI attached devices specified in IPL ROM Default Device List.
254 Attempting a Service mode restart from 9333 subsystem device specified in IPL ROM device list.
255 Attempting a Service mode IPL from IBM 7012 DBA disk'attached devices specified in IPL ROM Default Devices List.
256 Attempting a Service mode restart from Ethernet specified in IPL ROM default device list.
257 Attempting a Service mode restart from Token Ring specified in IPL ROM default device list.
258 Attempting a Service mode restart from Token Ring specified by the operator.
259 Attempting a Service mode restart from FDDI specified by the operator.
25c Attempting a normal mode IPL from FDDI specified in IPL ROM device list.
260 Information is being displayed on the display console.
261 Information will be displayed on the tty terminal when the "1" key is pressed on the tty terminal keyboard.
262 A keyboard was not detected as being connected to the system's
NOTE: Check for blown planar fuses or for a corrupted boot on disk drive
263 Attempting a Normal mode restart from adapter feature ROM specified in NVRAM device list.
269 Stalled state - the system is unable to IPL
271 Mouse port POST.
272 Tablet port POST.
277 Auto Token-Ring LANstreamer MC 32 Adapter
278 Video ROM Scan POST.
279 FDDI adapter POST.
280 3COM Ethernet POST.
281 Keyboard POST executing.
282 Parallel port POST executing
283 Serial port POST executing
284 POWER Gt1 graphadapte POST executing
285 POWER Gt3 graphadapte POST executing
286 Token Ring adapter POST executing.
287 Ethernet adapter POST executing.
288 Adapter card slots being queried.
289 GTO POST.
290 IOCC POST error (irrecoverable).
291 Standard I/O POST running.
292 SCSI POST running.
293 IBM 7012 DBA disk POST running.
294 IOCC bad TCW SIMM in slot location J being tested.
295 Graphics Display adapter POST, color or grayscale.
296 ROM scan POST.
297 System model number does not compare between OCS and ROS
(irrecoverable). Attempting a software IPL.
298 Attempting a software IPL (warm boot).
299 IPL ROM passed control to the loaded program code.
301 Flash Utility ROM failed or checkstop occured (irrecoverable)
302 Flash Utility ROM failed or checkstop occured (irrecoverable)
302 Flash Utility ROM: User prompt, move the key to the service in order to perform an optional Flash Update. LED
will only appear if the key switch is in the SECURE position. This signals the user that a Flash Update may be
initiated by moving the key switch to the SERVICE position. If the key is moved to the SERVICE position,
LED 303 will be displayed. This signals the user to press the reset button and select optional Flash Update.
303 Flash Utility ROM: User prompt, press the reset button in order to perform an optional Flash Update. LED
only appear if the key switch is in the SECURE position. This signals the user that a Flash Update may be initiated
by moving the key switch to the SERVICE position. If the key is moved to the SERVICE position, LED 303 will be
displayed. This signals the user to press the reset button and select optional Flash Update.
304 Flash Utility ROM IOCC POST error (irrecoverable)
305 Flash Utility ROM standard I/O POST running.
306 Flash Utility ROM is attempting IPL from Flash Update Boot Image.
307 Flash Utility ROM system model number does not compare between OCS and ROM (irrecoverable).
308 Flash Utility ROM: IOCC TCW memory is being tested.
309 Flash Utility ROM passed control to a Flash Update Boot Image.
311 Flash Utility ROM CRC comparison error (irrecoverable).
312 Flash Utility ROM RAM POST memory configuration error or no memory found ( iirecoverable).
313 Flash Utility ROM RAM POST failure( irrecoverable).
314 Flash Utility ROM Power status register failed (irrecoverable).
315 Flash Utility ROM detected a low voltage condition.
318 Flash Utility ROM RAM POST is looking for good memory.
319 Flash Utility ROM RAM POST bit map is being generated.
322 CRC error on media Flash Image. No Flash Update performed.
323 Current Flash Image is being erased.
324 CRC error on new Flash Image after Update was performed. (Flash Image is corrupted).
325 Flash Image successful and complete.
500 Querying Native I/O slot.
501 Querying card in Slot 1
502 Querying card in Slot 2
503 Querying card in Slot 3
504 Querying card in Slot 4
505 Querying card in Slot 5
506 Querying card in Slot 6
507 Querying card in Slot 7
508 Querying card in Slot 8
510 Starting device configuration.
511 Device configuration completed.
512 Restoring device configuration files from media.
513 Restoring basic operating system installation files from media.
516 Contacting server during network boot
517 Mounting client remote file system during network IPL.
518 Remote mount of the root and /usr filesystems failed during network boot.
520 Bus configuration running.
521 /etc/init invoked cfgmgr with invalid options; /etc/init has been corrupted or incorrectly modified
(irrecoverable error).
522 The configuration manager has been invoked with conflicting options (irrecoverable error).
523 The configuration manager is unable to access the ODM database (irrecoverable error).
524 The configuration manager is unable to access the config rules object in the ODM database (irrecoverable error).
525 The configuration manager is unable to get data from a customized device object in the ODM database
(irrecoverable error).
526 The configuration manager is unable to get data from a customized device driver objet in the ODM database
(irrecoverable error).
527 The configuration manager was invoked with the phase 1 flag; running phase 1 flag; running phase 1 at this point
is not permitted (irrecoverable error).
528 The configuration manager cannot find sequence rule, or no program was specified in the ODM database
(irrecoverable error).
529 The configuration manager is unable to update ODM data
(irrecoverable error).
530 The program "savebase" returned an error.
531 The configuration manager is unable to access PdAt object class
(irrecoverable eroor)
532 There is not enough memory to continue (malloc failure);
irrecoverable error.
533 The configuration manager could not find a configure method for a device.
534 The configuration manager is unable to aquire database lock. irrecoverable error.
536 The configuration manager encountered more than one sequence rule specified in the same phase. (irrecoverable error).
537 The configuration manager encountered an error when invoking the program in the sequence rule.
538 The configuration manager is going to invoke a configuration
539 The configuration method has terminated, and control has returned to the configuration manager.
551 IPL Varyon is running
552 IPL Varyon failed.
553 IPL phase 1 is complete.
554 Unable to define NFS swap device during network boot
555 Unable to define NFS swap device during network boot
556 Logical Volume Manager encountered error during IPL varyon.
557 The root filesystem will not mount.
558 There is not enough memory to continue the IPL.
559 Less than 2MB of good memory are available to load the AIX kernel.
570 Virtual SCSI devices being configured.
571 HIPPI common function device driver being configured.
572 HIPPI IPI-3 master transport driver being configured.
573 HIPPI IPI-3 slave transport driver being configured.
574 HIPPI IPI-3 transport services user interface device driver being configured.
576 Generic async device driver being configured.
577 Generic SCSI device driver being configured.
578 Generic commo device driver being configured.
579 Device driver being configured for a generic device.
580 HIPPI TCPIP network interface driver being configured.
581 Configuring TCP/IP.
582 Configuring token ring data link control.
583 Configuring an Ethernet data link control.
584 Configuring an IEEE ethernet data link control.
585 Configuring an SDLC MPQP data link control.
586 Configuring a QLLC X.25 data link control.
587 Configuring NETBIOS.
588 Configuring a Bisync Read-Write (BSCRW).
589 SCSI target mode device being configured.
590 Diskless remote paging device being configured.
591 Configuring an LVM device driver
592 Configuring an HFT device driver
593 Configuring SNA device drivers.
594 Asynchronous I/O being defined or configured.
595 X.31 pseudo device being configured.
596 SNA DLC/LAPE pseudo device being configured.
597 OCS software being configured.
598 OCS hosts being configured during system reboot.
599 Configuring FDDI data link control.
5c0 Streams-based hardware drive being configured.
5c1 Streams-based X.25 protocol being configured.
5c2 Streams-based X.25 COMIO emulator driver being configured.
5c3 Streams-based X.25 TCP/IP interface driver being configured.
5c4 FCS adapter device driver being configured.
5c5 SCB network device driver for FCS is being configured.
5c6 AIX SNA channel being configured.
600 Starting network boot portion of /sbin/rs.boot
602 Configuring network parent devices.
603 /usr/lib/methods/defsys
/usr/lib/methods/cggsys, or
/usr/lib/methods/cggbus failed.
604 Configuring physical network boot device.
605 Configuring physical network boot device failed.
606 Running /usr/sbin/ifconfig on logical network boot device.
607 /usr/sbin/ifconfig failed.
608 Attempting to retrieve the client.info file with tftp. Note that a flashing 608 indicates multiple attempts
to retrieve the client_info file are occuring.
609 The client.info file does not exist or it is zero length.
610 Attempting remote mount of NFS file system
611 Remote mount of the NFS filesystem failed.
612 Accessing remote files; unconfiguring network boot device.
614 Configuring local paging devices.
615 Configuring of a local paging device failed.
616 Converting from diskette to dataless configuration.
617 Diskless to dataless configuration failed.
618 Configuring remote (NFS) paging devices.
619 Configuration of a remote (NFS) paging device failed.
620 Updating special device files and ODM in permanent filesystem with data from boot RAM filesystem.
622 Boot process configuring for operating system installation.
650 IBM SCSD disk drive drive being configured
700 Progress indicator. A 1.1GB 8-bit SCSI disk drive being identified or configured.
701 Progress indicator. A 1.1GB 16-bit SCSI SE disk drive being identified or configured.
702 Progress indicator. A 1.1GB 16-bit SCSI differential disk drive being identified or configured.
703 Progress indicator. A 2.2GB 8-bit SCSI disk drive being identified or configured.
704 Progress indicator. A 2.2GB 16-bit SCSI SE disk drive being identified or configured.
705 The configuration method for the 2.2GB 16-bit differential SCSI disk drive is being run. If a irrecoverableerror occurs, the system halts. identified or configured.
706 Progress indicator. A 4.5GB 16-bit SE SCSI disk drive is being identified or configured.
707 Progress indicator. A 4.5GB 16-bit differential SCSI drive is being identified or configured.
708 Progress indicator: A L2 cache is being identified or configured.
710 POWER GXT150M graphics adapterbeing ientifyied or configured.
711 Unknown adapter being identified or configured.
712 Graphics slot bus configuration is executing.
713 The IBM ARTIC960 device is being configured.
714 A video capture adapter is being configured.
715 The Ultimedia Services audio adapter is being configured. This LED displays briefly on the panel.
720 Unknown read/write optical drive type being configured.
721 Unknown disk or SCSI device being identified or configured.
722 Unknown disk being identified or configured.
723 Unknown CDROM being identified or configured.
724 Unknown tape drive being identified or configured.
725 Unknown display being identified or configured.
726 Unknown input device being idenor configured
727 Unknown adync device being idenor configured
環(huán)境 產(chǎn)品: Netscape Communicator
平臺: AIX
問題 Netscape Communicator無法正常啟動(dòng)
解答 Netscape Communicator是使用自己獨(dú)有的AIX C library(libc.a)副本,早期隨AIX 4.3.1
的libc.a與現(xiàn)在通用的Communicator 4.0.4會(huì)存在兼容問題,系統(tǒng)會(huì)提示錯(cuò)誤如下: Could not load program /usr/local/netscape4/netscape_aix4
Symbol __malloc_postfork_unlock in /usr/lib/libpthreads.a is undefined
Symbol __malloc_prefork_lock in /usr/lib/libpthreads.a is undefined
Could not load library libC.a[shr.o]
Error was: Exec format error
要解決以上問題,到如下站點(diǎn)獲得幫助
ftp://aix.software.ibm.com/aix/efixes/netscape/
輸出舉例:
drwxr-xr-x 19 bin bin 1024 Dec 12 21:14 .
drwxr-xr-x 19 bin bin 1024 Dec 12 21:14 ..
lrwxrwxrwx 1 bin bin 8 Nov 22 09:37 bin ->; /usr/bin
drwxrwxr-x 4 root system 2048 Dec 12 21:12 dev
drwxr-xr-x 12 root system 2048 Dec 12 21:11 etc
drwxr-xr-x 5 bin bin 512 Nov 22 14:51 home
lrwxrwxrwx 1 bin bin 8 Nov 22 09:37 lib ->; /usr/lib
drwxr-xr-x 20 bin bin 512 Nov 22 13:33 lpp
drwxr-xr-x 3 bin bin 512 Nov 22 09:37 sbin
lrwxrwxrwx 1 bin bin 5 Nov 22 09:37 u ->; /home
drwxr-xr-x 20 bin bin 512 Nov 22 14:24 usr
drwxr-xr-x 12 bin bin 512 Nov 22 12:59 var
3. 執(zhí)行:
ls -ld /usr/bin /usr/lib /tmp
輸出舉例:
drwxr-xr-x 3 bin bin 10752 Nov 22 12:53 /usr/bin
drwxr-xr-x 28 bin bin 4096 Dec 15 17:08 /usr/lib/
drwxrwxrwt 8 bin bin 2560 Jan 22 14:46 /tmp/
4. 執(zhí)行:
ls -l /usr/bin/csh /usr/bin/ksh /usr/bin/bsh
輸出舉例:
-r-xr-xr-x 2 bin bin 341020 Nov 22 09:37 /usr/bin/bsh
-r-xr-xr-x 1 bin bin 154412 Nov 22 09:37 /usr/bin/csh
-r-xr-xr-x 4 bin bin 230148 Nov 22 09:37 /usr/bin/ksh
確定用戶的主目錄. 在這些步驟中, 假定用戶的ID和目錄為"user_one".
5. 執(zhí)行:
ls -ld u/user_one (use path of user's directory)
輸出舉例:
-drwxr-xr-x 9 user_one system 7680 Dec 24 15:00 /u/user_one
該目錄應(yīng)被此用戶所有, 并且此用戶應(yīng)對它有rwx權(quán)限.
6. 執(zhí)行:
cd /u/user_one
ls -al | pg
輸出舉例:
drwxr-xr-x 9 user_one system 7680 Dec 24 15:00 .
drwxr-xr-x 71 bin bin 1536 Dec 14 09:37 ..
"."目錄的所有者應(yīng)為該用戶. ".."目錄的權(quán)限對于組和其它用戶至少應(yīng)為r-x.
r --- 指讀目錄中文件列表的能力,如"ls"命令。
注 :如果只有讀目錄列表的許可,則不可以在目錄內(nèi)部執(zhí)行命令。
x ---目錄搜索能力?梢栽谝阎募麜r(shí)在目錄中執(zhí)行此文件。一般來說,大多數(shù)目錄操作都要求讀(r)和搜索(x)權(quán)限。
w---同搜索(x)權(quán)限共同使用時(shí),在目錄中產(chǎn)生或刪除文件的能力。如果目錄具有寫的權(quán)限,而沒有在文件寫的權(quán)限,你仍可以刪除文件,但不可以修改文件.
t ---指鏈接權(quán)限。設(shè)置鏈接權(quán)限可防止除文件所有者、根用戶和目錄所有者之外的所有用戶刪除文件,雖然目錄中的權(quán)限可能允許刪除這個(gè)文件。在這種情況下,可為“其他人”設(shè)置搜索(x)位。
* 如果系統(tǒng)出現(xiàn)以下幾種情況,則說明需要擴(kuò)大paging Space: 1. 下列任意錯(cuò)誤信息之一:
INIT: Paging space is low
ksh: cannot fork no swap space
Not enough memory
Fork function failed
fork () system call failed
Unable to fork, too many processes
Fork failure - not enough memory available
Fork function not allowed. Not enough memory available.
Cannot fork: Not enough space
2. 使用命令" lsps -a" ,其結(jié)果%USED 列的平均值大于80%.
3. 使用命令"lsps -s" 其結(jié)果%USED 列大于80%.
2. 安裝Web Server
==================
在AIX4.3.3 Bonus Pack中包含了IBM HTTP Server作為Web服務(wù)器,代替了以前版本的Netscape FastTrack Server(AIX4.2.1)和 Lotus Go Web Server(AIX4.3.2)。
用smit install_latest安裝在AIX4.3 Bonus Pack CD中提供的IBM HTTP Web Server。選擇以下的包: - http_server.base (IBM HTTP Server)
- http_server.admin (Administration Server - used to configure the IBM HTTP Server)
- http_server.msg.xx_XX.admin (where xx_XX is your country code)
- http_server.frca (AIX 4.3.3 or later, or AIX 4.3.2 with APAR IY01609. This APAR cannot be installed on AIX 4.2.1.)
- http_server.html.xx_XX (where xx_XX is your country code)
- http_server.man.en_US (Apache documentation)
- http_server.modules
3. 安裝Documentation Search Service
====================================
用smit install_latest安裝在AIX4.3 安裝盤中的所有bos.docsearch文件集。
4. 配置Documentation Search Service
====================================
用smit web_configure 來設(shè)置
- Default browser
這里選擇或鍵入起動(dòng)瀏覽器的命令,如netscape
- Documentation and Search Server
這里我們設(shè)置文檔和查詢服務(wù)器的位置為:Local - this coomputer 回車,
在Web server SOFTWARE中選擇IBM HTTP Server web server, 回車。
如果不是AIX 4.3.3,則沒有該選項(xiàng),請選擇"Other local server or above in non-default location",按回車,在以下的目錄中,根據(jù)你的web server 路徑設(shè)置改變相應(yīng)的值,(如下例為HTTP Server 1.3.6,對于HTTP Server1.3.3,路徑為/usr/lpp/HTTPServer/share/cgi-bin 和 /usr/lpp/HTTPServer/share/htdocs) Local web server PORT number [80]
Local web server cgi-bin DIRECTORY /usr/HTTPServer/cgi-bin
Local web server HTML document directory /usr/HTTPServer/htdocs
按回車
5. 安裝聯(lián)機(jī)手冊(Online Manuals)
================================
隨AIX 安裝CD, 有兩張文檔CD:
The AIX Version 4.3 Base Documentation CD
The AIX Version 4.3 Extended Documentation CD
用smit install_latest將CD中的聯(lián)機(jī)手冊按需安裝到硬盤。對了,別忘了安裝bos.docregister,它是使用所有聯(lián)機(jī)文檔的先決條件。
6. 激活Documentation Search Service
====================================
配置完Documentation Search Service后,需要log out并重新log in,使得環(huán)境變量生效。
7.使用下面的命令檢查文件是否被修改或是否有權(quán)限上的問題.
ls -al /.profile /etc/environment /etc/profile
輸出舉例:
-rw-r--r-- 1 root system 158 Dec 14 1993 /.profile
-rw-rw-r-- 1 root system 1389 Oct 26 1993 /etc/environment
-rw-r--r-- 1 root system 1214 Jan 22 1993 /etc/profile
1.用瀏覽器打開:http://service.software.ibm.com/rs6k/fixdb.html ( AIX Version 4
AIX Version 3
CATIA for AIX ).
2.選擇使用的數(shù)據(jù)庫
3.選擇檢索選項(xiàng), 并輸入相應(yīng)的字串:
( APAR Number ---- 如:IX85874,IY00411
Fileset Name --- 如:bos.net.tcp.server
PTF Number ---- 如:U464245
APAR Abstract -- 如:HACMP),