[newbie] Adding dirs to the path
/etc/profile has a comment that PATH is taken care of by Mandrake Security. Removing the # and adding dirs has no affect on the path. Could someone point out: 1) Where Mandrake hides the ability to update the path 2) Where this and other differences in Mandrake vs popular Linux how-to books are documented 3) Is it a standard *nix security configuration to not search the current directory? Most annoying for an OS/2, Win32, DOS based person. 4) Where should I set other env vars so I don't have to run *.sh scripts to set / export env vars before running programs I've installed. Thanks! Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/
Re: [newbie] Adding dirs to the path
/etc/profile has a comment that PATH is taken care of by Mandrake Security. Removing the # and adding dirs has no affect on the path. Could someone point out: You didn't say why you wanted to change the path but I think you're looking in the wrong place. 1) Where Mandrake hides the ability to update the path Who's path? If you want the default user path changed, change /etc/bashrc. If you want to change your user path, make changes to .bashrc in your home directory. 2) Where this and other differences in Mandrake vs popular Linux how-to books are documented I've found that most of what you read in Red Hat books applies to Mandrake as well. They don't cover stuff like DrakConf of course but all the "real" system stuff is there. 3) Is it a standard *nix security configuration to not search the current directory? Most annoying for an OS/2, Win32, DOS based person. grin...I recall an explanation of this at one point but I can't recall it. For my user account, I've got .: as the first entry in my path (in my .bashrc file) 4) Where should I set other env vars so I don't have to run *.sh scripts to set / export env vars before running programs I've installed. Two things here. The path change will cause them to be "available" but if you want to run them as though they are executable, you have to make sure they have their execute bits set. Quite often shell scripts are distributed without this being the case. If you're only going to run it once (like during an install), it might be easier to use "sh install.sh" Cheers --- Larry
Re: [newbie] Adding dirs to the path
3) Is it a standard *nix security configuration to not search the current directory? Most annoying for an OS/2, Win32, DOS based person. grin...I recall an explanation of this at one point but I can't recall There's an answer to this in the comp.unix.questions faq. The example they give is that in a publicly available directory like /tmp, there *might* be an executable named "ls". If the current directory is in your path you would execute that, with unexpected results. Paranoia, unless your sysop on a large system with many playful lusers. See item 2.13 in http://www.cs.ruu.nl/wais/html/na-dir/unix-faq/faq/part2.html for further details. Be sure to read http://www.cs.uu.nl/wais/html/na-dir/sysadmin-recovery.html as well. We're all sysops now, at least for ourselves. What are you using as your LART? __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/
Re: [newbie] Adding dirs to the path
On Mon, 16 Oct 2000 09:10:01 -0400 (EDT), Larry Marshall wrote: /etc/profile has a comment that PATH is taken care of by Mandrake Security. Removing the # and adding dirs has no affect on the path. Could someone point out: You didn't say why you wanted to change the path but I think you're looking in the wrong place. Well, Red Hat 6 Unleashed pointed me in that direction. Thus why I asked Q #2 below. 1) Where Mandrake hides the ability to update the path Who's path? If you want the default user path changed, change /etc/bashrc. If you want to change your user path, make changes to .bashrc in your home directory. I'd like to updated what in the Win2K world would be the system's path so that all users get updated. I am installing the Object Rexx language which I will want to be active for all users. 4) Where should I set other env vars so I don't have to run *.sh scripts to set / export env vars before running programs I've installed. Two things here. The path change will cause them to be "available" but if you want to run them as though they are executable, you have to make sure they have their execute bits set. Quite often shell scripts are distributed without this being the case. If you're only going to run it once (like during an install), it might be easier to use "sh install.sh" IBM provides a script to modify the env vars, run export on those vars, and you are all set until you logoff. I would like to modify all of those vars at a system level. IBM must have set the execute bit as I have no problem running the file. Thanks! Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/
