| ??? 06/04/08 22:43 Read: times |
#155503 - CWD not in path Responding to: ???'s previous message |
Having the current working directory in the default path is considered a security no-no in most Unix variants. Consider what happens on a multiuser machine if I drop an executable in /tmp named "ls", and you have "." before /bin in your default path. You type "ls -l" and run my program, which I would have rigged to fork and exec the real ls before happily going on it's way causing whatever havoc I wanted using your credentials. That's the world Unix comes from. So most sysadmins make it the default to not search "." in the path. The fix in this case is to call it absolutely: ./prog89S52 -p name.hex or /some/path/where/it/resides/prog89S52 -p name.hex Rob |
| Topic | Author | Date |
| Programmer for at89s52 | 01/01/70 00:00 | |
| google pointed me to 8052.com | 01/01/70 00:00 | |
| Thanks | 01/01/70 00:00 | |
| check PATH | 01/01/70 00:00 | |
| Path dusnt work | 01/01/70 00:00 | |
| when will they ever learn (PP&M) | 01/01/70 00:00 | |
| CWD not in path | 01/01/70 00:00 | |
| still not working | 01/01/70 00:00 | |
Exec bit not set? | 01/01/70 00:00 | |
| Is a Linux tool | 01/01/70 00:00 |