Can you say "identity theft"? Any nut with a scanner can walk past you, take your info and replace his own chip with your info. You wont feel a thing, although your bank account may feel it.
Re:Fantastic , more bloatware eyecandy
on
KDE 3.0 is Out
·
· Score: 2, Insightful
And this is the beauty of using Linux, if you do not like the interface....don't use it! Use gnome or command line or any one of the other windowing interfaces.
Unlike Windows. If you must use XP but don't like XP well then you have no choice you use XP.
Ain't free software beautifull? Not only is it free but it gives you variety and choice... it gives you freedom. (I can see a geek running through a field of flowers jumping over fallen XP users laptop in hand, laughing like a love sick maiden)
aaagh... just use something else if you don't like KDE!
My intention was not to rewrite the IBM manuals.
But ok...lets be more accurate then.
The exact command to "vary" a CPU online is :
"cf cpu(1),online,vfon" (there is some more parms.. but you can consult the manual for them).
You were right, this is actually a "cf" command,
(cf is short for configure) and not a "vary" command, although the vary commands are the more commonly used ones.
About the console. This is from the MVS
System Commands manual: "You can enter the CONFIG command only from a console with master authority. "
Not IBM's term but the users and media's term for Mainframes.
How a Mainframe works
on
Linux On Big Iron
·
· Score: 4, Informative
I note that there is quite a few peoples that do not know how things are done
on a mainframe. I will TRY and clarify.
If you have an average box, say 400 mips, there will be a couple of things happening on this box. Starting of with the OS, OS/390 (or z/OS, VSE, VM). Then a network server VTAM and TCP/IP, a Security server, the some DB's DB2, IMS/DB(or some vendor DB). Then transaction servers CICS or/and IMS serving 4000+ concurrent online
users logged on to CICS or IMS. Then you may have oh lets say 500+ programmers, system programmers, DBA, Administrators etc, logged on to the OS "shell" TSO doing programming,
compiling, admin, editing and in general doing what these kinda people do, maintaining the
monster. The there may be a MQSeries or two running handling client connections and messaging
applications and client (pc's, server's *nix's) connections to DB2..
(i'm touching the surface here!)
So in general there is a little more happening on a mainframe than on you average wintel box. So in order to separate the production and development, and test environments you can go and partition this one little box up into three logical partitions, called LPAR's in dinosaur speak. Each LPAR can be IPL'd (BOOT in dino speak) without affecting any one of the other LPAR's. So now you have one IBM 2064 400MIP box, 3 LPAR'S and still have room to breathe.
Add another LPAR, install VM, Load LINUX/390 and reboot the LINUX LPAR. But still only one Linux server on the box? But we have 250 NT boxes to replace? Not to Worry!! under VM on your brand new LPAR on your mainframe box you can begin to start Linux images at will.
So in the end we have 1 Box, 3 OS/390 Mainframe partitions, 1 VM partition with 250 Linux servers running. But now the 400 mips is kinda running out of steam. Call up IBM and they will come and add another cpu. And if you were planning ahead the IBM 2064 should have an idle couple of CPU's under the hood not being used. So you call IBM, they give you the code and you go to the master console and issue a "very cpu online" command and off you go. No IPL required, no downtime.
Do that on your duel XEON Intel with Windows... any kind of Windows.
I'm not going to go into Parallel Sysplex'ing, syscon's and CICSPlexing etc.
And so the end begins.
Finally the whole Linux mess will come to a deserving halt and crash to pieces.
2.4 was and still is a disaster.
And seeing that nobody are wimpy enough to use source control it is to be expected.
Do you people really expect a normal run of the mill user to try Linux? Intall XP or even W2K, and see what users want. They do not care about
holly OS wars and ESR's ranting's nor do they want to care if Linus will fix the next kernel.
The user want's to play his DVD, record his MiniDV videos on CD using firewire or USB 2.0.
He/She can do all that and more with Apple or Microsoft.
And you, the "hollier than though " kernel geeks can fight on how to do source control.
Linux will never be a major on the desktop nor the server if this is how dev is done. The more growth the higher the demands on the kernel will be. Can Linux handle that?
It does not look like it.
Slashdot Mirror
Can you say "identity theft"? Any nut with a scanner can walk past you, take your info and replace his own chip with your info. You wont feel a thing, although your bank account may feel it.
And this is the beauty of using Linux, if you do not like the interface....don't use it! Use gnome or command line or any one of the other windowing interfaces. Unlike Windows. If you must use XP but don't like XP well then you have no choice you use XP. Ain't free software beautifull? Not only is it free but it gives you variety and choice... it gives you freedom. (I can see a geek running through a field of flowers jumping over fallen XP users laptop in hand, laughing like a love sick maiden) aaagh... just use something else if you don't like KDE!
Oh yeah...no "power reset".
My intention was not to rewrite the IBM manuals. But ok...lets be more accurate then. The exact command to "vary" a CPU online is : "cf cpu(1),online,vfon" (there is some more parms.. but you can consult the manual for them). You were right, this is actually a "cf" command, (cf is short for configure) and not a "vary" command, although the vary commands are the more commonly used ones. About the console. This is from the MVS System Commands manual: "You can enter the CONFIG command only from a console with master authority. "
Not IBM's term but the users and media's term for Mainframes.
I note that there is quite a few peoples that do not know how things are done on a mainframe. I will TRY and clarify. If you have an average box, say 400 mips, there will be a couple of things happening on this box. Starting of with the OS, OS/390 (or z/OS, VSE, VM). Then a network server VTAM and TCP/IP, a Security server, the some DB's DB2, IMS/DB(or some vendor DB). Then transaction servers CICS or/and IMS serving 4000+ concurrent online users logged on to CICS or IMS. Then you may have oh lets say 500+ programmers, system programmers, DBA, Administrators etc, logged on to the OS "shell" TSO doing programming, compiling, admin, editing and in general doing what these kinda people do, maintaining the monster. The there may be a MQSeries or two running handling client connections and messaging applications and client (pc's, server's *nix's) connections to DB2.. (i'm touching the surface here!) So in general there is a little more happening on a mainframe than on you average wintel box. So in order to separate the production and development, and test environments you can go and partition this one little box up into three logical partitions, called LPAR's in dinosaur speak. Each LPAR can be IPL'd (BOOT in dino speak) without affecting any one of the other LPAR's. So now you have one IBM 2064 400MIP box, 3 LPAR'S and still have room to breathe. Add another LPAR, install VM, Load LINUX/390 and reboot the LINUX LPAR. But still only one Linux server on the box? But we have 250 NT boxes to replace? Not to Worry!! under VM on your brand new LPAR on your mainframe box you can begin to start Linux images at will. So in the end we have 1 Box, 3 OS/390 Mainframe partitions, 1 VM partition with 250 Linux servers running. But now the 400 mips is kinda running out of steam. Call up IBM and they will come and add another cpu. And if you were planning ahead the IBM 2064 should have an idle couple of CPU's under the hood not being used. So you call IBM, they give you the code and you go to the master console and issue a "very cpu online" command and off you go. No IPL required, no downtime. Do that on your duel XEON Intel with Windows... any kind of Windows. I'm not going to go into Parallel Sysplex'ing, syscon's and CICSPlexing etc.
And so the end begins. Finally the whole Linux mess will come to a deserving halt and crash to pieces. 2.4 was and still is a disaster. And seeing that nobody are wimpy enough to use source control it is to be expected. Do you people really expect a normal run of the mill user to try Linux? Intall XP or even W2K, and see what users want. They do not care about holly OS wars and ESR's ranting's nor do they want to care if Linus will fix the next kernel. The user want's to play his DVD, record his MiniDV videos on CD using firewire or USB 2.0. He/She can do all that and more with Apple or Microsoft. And you, the "hollier than though " kernel geeks can fight on how to do source control. Linux will never be a major on the desktop nor the server if this is how dev is done. The more growth the higher the demands on the kernel will be. Can Linux handle that? It does not look like it.