Original message:
Hi Richard:
1. Where should the .orbitrc file live... in the root directory or in the home directory that needs a talking sysadmin?
The exact filename is "/root/.orbitrc". If you create this file as root, BTW, then I'm guessing the chmod/chown stuff will not be necessary. I just listed it for completeness in what I had done.
2. When I did chmod 644 .orbitrc I got an invalid mode message back. What do I do to get these permissions set?
"sudo chmod 644 /root/.orbitrc" should work. If that doesn't work, I'd guess /root/.orbitrc doesn't exist.
3. When I did chown root.root .orbit I got an invald message about that. Do I have my arguments backwards? Am I using these commands incorrectly or is it done differently in ubuntu?
"sudo chown root.root /root/.orbitrc"
Hope this helps,
Will
Richard Wells wrote:You said in part: SYS ADMIN:
1) Create root's ~/.orbitrc file (/root/.orbitrc, with and owner.group of root.root with a mode of 644 on my system):
ORBIIOPIPv4=1 ORBIIOPUNIX=0
2) Edit /etc/sudoers to add the following line after the line with "env_reset" in it:
Defaults env_keep+="GTK_MODULES"
A couple of probably stupid questions arise from this procedure. 1. Where should the .orbitrc file live... in the root directory or in the home directory that needs a talking sysadmin? 2. When I did chmod 644 .orbitrc I got an invalid mode message back. What do I do to get these permissions set? 3. When I did chown root.root .orbit I got an invald message about that. Do I have my arguments backwards? Am I using these commands incorrectly or is it done differently in ubuntu?
I know I am showing my ignorance here, but as you can see, I need a little hand-holding through this.
Thanks
--Email services provided by the System Access Mobile Network. Visit www.serotek.com to learn more about accessibility anywhere.