Comments (9)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 UrbanBiel commented Permalink

I agree definitely. <br /> #4 is really pain, I hate it <br /> #6 was really beautiful idea <br /> And for #1 please, at least allow us to run awk!

2 RCeleste commented Permalink

I totally agree with this defects list , worst of all #4 . <br /> IHHO #3 is trivial but it would be so comfortable..if it was real . <br /> HMC related issues are really limiting too.

3 UrbanBiel commented Permalink

If #4 is not going to die, please, at least bring "sort" command to padmin. I have to switch to oem_setup_env to sort something...

4 niella commented Permalink

- Install SSH by default (and disable telnet). <br /> - Built-in support for terminal colours, at leaste for grep and ls. For heaven's sake, Linux has been doing this for a long time. <br /> - I agree with #3, the ksh93 'g' release is apparently needed for this support. I don't want a emacs hack for this, I want this to work in vi mode... <br /> - Replace or simplify the utterly silly manual VIO VSCSI disk mapping scheme. It is counter-productive, and does not rhyme with "fast provisioning". <div>&nbsp;</div>

5 AnthonyEnglish commented Permalink

Remove the requirement for firmware updates to be disruptive. It's hard to explain why a fully-redundant, million dollar enterprise system needs to have a scheduled outage once a year for firmware. Hopefully, you'll have another fully redundant, million dollar system ready so you can use Live Partition Mobility for the 30 minutes, once-a-year firmware update. <div>&nbsp;</div> Some minor suggestions to do with file systems: <div>&nbsp;</div> When a file system gets created in SMIT, the default is for it not to mount after a reboot. That's a bit like having a volume group not activate after a reboot and making that the default. And make INLINE logs the default. <div>&nbsp;</div> Allow users to change a file system from external to INLINE logs (chfs and logform should work) without having to rebuild the whole file system and copy the data. <div>&nbsp;</div> In SMIT, when creating a file system on a previously defined logical volume, allow the user to type in the LV name. At the moment you have to hit F4 to list available LVs.

6 EricDiepvens commented Permalink

Recently I encoutered a situation, which could result in a 7°point: <br /> When installing a full system AIX partition on a Power7 server that was not connected to a HMC and had no PowerVM, I had a some problems to get a system console working properly on my PC. <br /> The trouble making the cables, connectors and serial-to-USB convertors work was a pain in my ass. <div>&nbsp;</div> So I would like to request System console access through the ASMI web interface for server that are not connected to a HMC <div>&nbsp;</div> Eric

7 brian_s commented Permalink

Eric - I agree, having system console access through the ASMI web interface would be a very useful feature!

8 lillracksingen commented Permalink

I agree with all points, especially #5. Really a pain to configure a dual VIO setup when only one SATA DVD drive available. Would be really neat if the second VIO could mount vtopt media from the first one. BTW: did you notice IBM i LPARs can act as both VIO clients AND servers?

Regarding #3: There is a poorly documented way of enabling the cursor keys if you select emacs command line editing. Check out
Note the first answer on the linked page, the cursor and Home keys will work in an xterm with the aliases defined. The End key will work if you change the last alias to:
alias __F=`echo "\005"`
File name completion works with <Esc>+<Esc></Esc></Esc>

9 CGroen commented Permalink

From the bottom of my heart........#4!!!!! I see no good reason to have such aliases for common AIX commands. It serves no purpose but to make administration difficult.