Re: Cdrecord

[Walker West <wwest@dalcon.com>]

For security reasons (someone could create a replacement 'rm' command
and install it in your working directory, etc.), the working directory
is not normally in the path.  You can enter:  

	PATH=$PATH:./; export PATH

to put the current working directory in the path if you're using bash. 
Alternatively, you can enter a ./ in front of the name of the program
you want to run (i.e.: ./cdrecord).

--Walker

Matt Wehland wrote:
> 
> Ok, I found part of my problem with CDrecord, it seems to be a path
> problem.  If I am in the program directory '/opt/schily/bin' with the file
> cdrecord with full permissions, and issue 'cdrecord' I get 'command not
> found'.  If I issue the command with the full path
> /opt/schily/bin/cdrecord I at least get cdrecord to run, now I just need
> to see if I can actually get it to work, haven't gotten that far yet. Why
> doesn't the command work without the full path name, even if I am in the
> program directory.
> Since I can't remember the path search order (I though it was current
> directory then the paths in order), I even checked all search paths for an
> instance of cdrecord that might not be executable.  No luck. I really
> don't know why I have to give the full path to the program, but oh well,
> now to see what else doesn't work.
> 
> Matt Wehland
> 
> --
> To unsubscribe, send email to majordomo@silug.org with
> "unsubscribe silug-discuss" in the body.


--
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.