|smbclient -L localhost||Lists the available shares on your host|
|useradd oracle -d /opt/oracle -g oinstall -G sysdba,sysoper,dba -m||As root: This will add user oracle making his home dir /opt/oracle with his
primary group being oinstall but also a member of sysdba,sysoper and dba.
-m means the users home dir will be created from the skeleton available.
On some versions of Linux (RedHat 6.0) I found that an empty dir with the username had to be created first. So just be aware that all versions are not neccessarily the same or something was missed in the installation.... or the version is just to old.
|groupadd sysoper||As root: This will add the group sysoper.|
|userdel -r oracle||As root: This will completely remove the user oracle.|
|passwd oracle||As root: You can set or change the password of user oracle.|
|chown oracle.oinstall oraInventory||AS root: Thsi will set the owner to oracle and the group to oinstall for the directory or file oraInventory. In this case it is a dir.|
|export ORACLE_HOME=/opt/oracle;||This command will create a global var ORACLE_HOME and set it to /opt/oracle. It can be performed, and usually is, from the users home dir.|
|For some commands:||On the Linux system use "man xxxx" (without the quotes) where xxxx is the command that you want information on. If the man pages were not installed on the Linux machine then I guess you will have to try the WEB:|
|chmod 4555 vmware||Make vmware suid root. Which means a regular user will be able to run a program as root
if it is set to SUID root:
-r-sr-xr-x 1 root root 2157216 2004-12-27 21:37 vmware*
All programs and files on your computer with 's' bits appearing on their mode, have the
SUID -rwsr-xr-x or SGID -r-xr-sr-x bit enabled.
SUID and SGID Programs - Because this is extremely important, more info:
There are two additional permission bits associated with a file--the SUID and SGID bits. SUID stands for Set User ID and SGID is Set Group ID. Programs with these permissions behave as if they were owned by different UIDs when they are run. When an SUID program is run, its effective UID is set the same as the user that owns the program on the file system, 'regarless' of who is actually runing the program. SGID is similar except that it changes the group ID instead. Although the SUID/SGID feature can be useful, it can present a big security hole. SUID programs are generally used when a program needs special permissions, such as root permission, in order to run.