Linux is not Posix compliant. A _few_ parts of it are, but last I checked the Windows 2000 Posix subsystem were more Posix.1 compliant than Linux. (Posix.1e springs to mind)Quote:
Ok, learning Linux to me is a good idea. After you have it down pretty well, it's POSIX compliant so using another UNIX based OS is usually pretty easy to do.
I believe the only Posix certified OS is still AIX, others just have bits and pieces. Also keep in mind that Posix is primarily focused toward standardized programming for the system (which well all know how well Linux software runs on FreeBSD and how well FreeBSD software runs on HP-UX and how well HP-UX software runs on Linux, etc, etc) so from an administration view point this is of little impact.
True, but SSHD uses more resources than a local users as well. ;)Quote:
I have heard that running anything other than the command line in linux chews up resources, and I've found this first hand. My hope is to get everything setup, and then disable the GUI, take away the keyboard and mouse, and just access the box via ssh.
On a more serious note, I think for a new Linux user in a production environment, leaving a gui and the local hardware UI intact is a good idea. Despite whatever elitists like to say, the gui is a more productive interface and is likely to save you _significant_ time in the event that anything breaks. This is at virtually no cost to the system as the gui only uses resources when it is running and when it is running will be times when you are fixing stuff, so it is unlikely the computer will be in use otherwise then anyhow. Following this advice until you are more familair with the system will save you many headaches and much downtime.
catch
