By the way, when you change the number of concurrent non-root users using either of the three methods mentioned in the previous post, you must reboot your system for this change to take effect. The command "shutdown -Fr" issued as root, of course, would be just the ticket.
To increase the number of concurrent non-root users, either: a) invoke the command "chlicense -u NN" where NN is some number greater than 2; b) edit the file "/etc/security/login.cfg" and change the variable definition "maxlogins=2" to "maxlogins=NN" where NN is some number greater than 2; c) use "smitty" or "wsm" to accomplish the same thing.
Rack-mounted RS/6000 SMP machines like these usually default to running extra diagnostic checkout of the usually largish amount of RAM during bootup. This is a good thing for production systems. I've seen a pair of R40 RS/6000 boxes, lashed together with HACMP/6000, where one of the active system images failed due to a memory parity error, that system image was able to reboot itself and resume operation. Thank the BUMP code. On the other hand, if you want to live with quicker reboots (and less insurance) you can turn off the BUMP code memory checkout by selecting an option of the AIX diag command, or by using the following command: mpcfg -cf 11 1 This turns off the BUMP code processing for the next reboot only. Can save the half an hour you were complaining about. Realistically, only useful if you are installing some software and want to save a little time before turning the system over to production use. Sure, you can get your plane in the air sooner if you don't bother to pack your parachute.
VM supported TCP/IP daemons as virtual machines in the late 1980's. I know, I installed it then to support a network which included RS/6000 machines running AIX, IBM's version of UNIX, connecting to the mainframe via an 8232. On MVS, in the early 1990's, you had a choice of running TCP/IP in outboard controllers, or (somewhat later in the 1990's) running TCP/IP in address spaces on the mainframe itself. In the early 1990's, IBM's proprietary System Network Architecture evolved to support flowing TCP/IP over VTAM (Virtual Terminal Access Method, or something like that), and VTAM itself became a marketing item called "AnyNet"...charming, no? AIX continues to have an SNA-compatible networking product, but the die has long been cast, TCP/IP is now and has been for a long time, the lingua franca of networking. I also worked with the Amdahl UTS product mentioned in these posts and it worked with 3270 controllers, in the same late 1980's timeframe. AIX/370 ran on IBM 370 mainframes in the late 1980's. AIX/ESA ran on 380 or 390 mainframes in the late 1980's. The MVS operating system, since MVS/ESA 5.3, now known as Open Edition/390 or whatever the current marketeering name for it is, since the mid 1990's has included the "omvs" command, which, issued from a TSO session, will bring up a POSIX shell. You can use the standard command line interface; your directories and files are stored in an MVS dataset called a PDS/E; even though you can store NFS-mountable ASCII data in these essentially EBCDIC operating system datasets, they can be backed up and managed via standard MVS/ESA job control language batch jobs. In other words, with the exception of specialized super computers like Asia Pacific - Blue (which is a large cluster of RS/6000 boxes, by the way), the largest UNIX file server you ever saw is probably an IBM mainframe. Of course, you may never have seen a mainframe. They are still kept inside the raised-flooring area, minded by systems programmer gurus who dwell in closed offices. No one talks to the gurus, we just shove food under their doors with our paltry requests for guidance. Or so the story goes. Although new mainframes are expensive to purchase or lease, the vast number of users they can support actually make the total cost of ownership lower than our favorite mini-computer boxes running proprietary operating systems. That's been documented, you could look it up. You could get an older, water-cooled mainframe for the cost of hauling it away. The maintenance costs on water-cooled mainframes, and the proprietary software charges, will kill you though. Maintenance costs on air-cooled mainframes are much lower, but the software is still expensive... not just the operating system, but the extremely high cost of products sold by vendors. I know an organization that got a freebie mainframe, set it up, and found to their amazement that they were spending almost a million dollars a year on software charges (most of it going to application vendors) and maintenance contracts (oops, it was a water-cooled unit). Enter Linux/390, and the opportunity to replace some proprietary software applications with Linux based solutions. Hey, you can run these in a virtual machine with your regular mix of second-level virtual machines on top of the VM/ESA Control Program, or if you are Open Edition/390 based already, you can partition off part of your RAM and run Linux/390 on the bare metal. That's a pretty attractive proposition.
One might also find interesting the emphasis on rare and fine mechanical watch collecting in ATP. Some months before the book came out, William Gibson wrote a piece for Wired magazine about his eBay experiences bidding on collectable wrist watches. Perhaps a writer can declare such purchases as tax deductible research expenses. By the way, find a rental copy of the "Wild Palms" videos... there's a walk-on role Gibson plays as himself at a cocktail party.
Re:"Boire du petit lait/", a french expression...
on
The Post-Microsoft Era
·
· Score: 1
Try "as satisfied as a cat with a saucer of cream."
Slashdot Mirror
By the way, when you change the number of concurrent non-root users using either of the three methods mentioned in the previous post, you must reboot your system for this change to take effect. The command "shutdown -Fr" issued as root, of course, would be just the ticket.
To increase the number of concurrent non-root users, either: a) invoke the command "chlicense -u NN" where NN is some number greater than 2; b) edit the file "/etc/security/login.cfg" and change the variable definition "maxlogins=2" to "maxlogins=NN" where NN is some number greater than 2; c) use "smitty" or "wsm" to accomplish the same thing.
Rack-mounted RS/6000 SMP machines like these usually default to running extra diagnostic checkout of the usually largish amount of RAM during bootup. This is a good thing for production systems. I've seen a pair of R40 RS/6000 boxes, lashed together with HACMP/6000, where one of the active system images failed due to a memory parity error, that system image was able to reboot itself and resume operation. Thank the BUMP code. On the other hand, if you want to live with quicker reboots (and less insurance) you can turn off the BUMP code memory checkout by selecting an option of the AIX diag command, or by using the following command: mpcfg -cf 11 1 This turns off the BUMP code processing for the next reboot only. Can save the half an hour you were complaining about. Realistically, only useful if you are installing some software and want to save a little time before turning the system over to production use. Sure, you can get your plane in the air sooner if you don't bother to pack your parachute.
Of course, to a disk drive manufacturer, a megabyte is one million bytes.
VM supported TCP/IP daemons as virtual machines in the late 1980's. I know, I installed it then to support a network which included RS/6000 machines running AIX, IBM's version of UNIX, connecting to the mainframe via an 8232. On MVS, in the early 1990's, you had a choice of running TCP/IP in outboard controllers, or (somewhat later in the 1990's) running TCP/IP in address spaces on the mainframe itself. In the early 1990's, IBM's proprietary System Network Architecture evolved to support flowing TCP/IP over VTAM (Virtual Terminal Access Method, or something like that), and VTAM itself became a marketing item called "AnyNet" ...charming, no? AIX continues to have an SNA-compatible networking product, but the die has long been cast, TCP/IP is now and has been for a long time, the lingua franca of networking. I also worked with the Amdahl UTS product mentioned in these posts and it worked with 3270 controllers, in the same late 1980's timeframe. AIX/370 ran on IBM 370 mainframes in the late 1980's. AIX/ESA ran on 380 or 390 mainframes in the late 1980's. The MVS operating system, since MVS/ESA 5.3, now known as Open Edition/390 or whatever the current marketeering name for it is, since the mid 1990's has included the "omvs" command, which, issued from a TSO session, will bring up a POSIX shell. You can use the standard command line interface; your directories and files are stored in an MVS dataset called a PDS/E; even though you can store NFS-mountable ASCII data in these essentially EBCDIC operating system datasets, they can be backed up and managed via standard MVS/ESA job control language batch jobs. In other words, with the exception of specialized super computers like Asia Pacific - Blue (which is a large cluster of RS/6000 boxes, by the way), the largest UNIX file server you ever saw is probably an IBM mainframe. Of course, you may never have seen a mainframe. They are still kept inside the raised-flooring area, minded by systems programmer gurus who dwell in closed offices. No one talks to the gurus, we just shove food under their doors with our paltry requests for guidance. Or so the story goes. Although new mainframes are expensive to purchase or lease, the vast number of users they can support actually make the total cost of ownership lower than our favorite mini-computer boxes running proprietary operating systems. That's been documented, you could look it up. You could get an older, water-cooled mainframe for the cost of hauling it away. The maintenance costs on water-cooled mainframes, and the proprietary software charges, will kill you though. Maintenance costs on air-cooled mainframes are much lower, but the software is still expensive... not just the operating system, but the extremely high cost of products sold by vendors. I know an organization that got a freebie mainframe, set it up, and found to their amazement that they were spending almost a million dollars a year on software charges (most of it going to application vendors) and maintenance contracts (oops, it was a water-cooled unit). Enter Linux/390, and the opportunity to replace some proprietary software applications with Linux based solutions. Hey, you can run these in a virtual machine with your regular mix of second-level virtual machines on top of the VM/ESA Control Program, or if you are Open Edition/390 based already, you can partition off part of your RAM and run Linux/390 on the bare metal. That's a pretty attractive proposition.
One might also find interesting the emphasis on rare and fine mechanical watch collecting in ATP. Some months before the book came out, William Gibson wrote a piece for Wired magazine about his eBay experiences bidding on collectable wrist watches. Perhaps a writer can declare such purchases as tax deductible research expenses. By the way, find a rental copy of the "Wild Palms" videos... there's a walk-on role Gibson plays as himself at a cocktail party.
Try "as satisfied as a cat with a saucer of cream."