lol . . . way off the point by now. But since we're way off point I will make my disappointment known. First, Linux is purportedly know as the developers OS by developers, yes ? So with that in mind it's probably a good assumption that many people are going to be developing software on it. So . . .anyone care to take a stab at what the most common executable name will be for test applications ?
Could I have checked for "test" as an existing executable ? Yes, certainly, but would I in any right state of mind even think that I should check ? No, probably not . . . So yes, I could probably be a better user and look before I leap, but why in hell would an default *anything* named test exist on any Linux system ? Guess we'll either have to ask the maintainer(s) of bash and ask them wtf they were thinking, or just move on . . . On Fri, Mar 25, 2016 at 7:01 PM, Mike <[email protected]> wrote: > On 03/25/2016 09:44 PM, William Hermans wrote: > > ooops forgot to add this. > > william@beaglebone:~/ramfs$ which test > william@beaglebone:~/ramfs$ sudo su > root@beaglebone:/home/william/ramfs# which test > root@beaglebone:/home/william/ramfs# exit > exit > > > On Fri, Mar 25, 2016 at 6:42 PM, William Hermans <[email protected]> > wrote: > >> william@beaglebone:~/ramfs$ cat test.c >> #include<stdio.h> >> >> >> int main() >> { >> printf("hello world !\n"); >> return 0; >> } >> william@beaglebone:~/ramfs$ gcc test.c -o test >> william@beaglebone:~/ramfs$ la -al test >> -bash: la: command not found >> william@beaglebone:~/ramfs$ ls -al test >> -rwxr-xr-x 1 william william 5047 Mar 25 18:31 test >> william@beaglebone:~/ramfs$ umask 022 >> william@beaglebone:~/ramfs$ test >> william@beaglebone:~/ramfs$ umask 0137 >> william@beaglebone:~/ramfs$ test >> william@beaglebone:~/ramfs$ ./test >> hello world ! >> william@beaglebone:~/ramfs$ chmod u+x test >> william@beaglebone:~/ramfs$ test >> william@beaglebone:~/ramfs$ umask 022 >> william@beaglebone:~/ramfs$ test >> william@beaglebone:~/ramfs$ sudo test >> sudo: test: command not found >> william@beaglebone:~/ramfs$ umask 0137 >> william@beaglebone:~/ramfs$ sudo test >> sudo: test: command not found >> william@beaglebone:~/ramfs$ export PATH=$PATH:/home/william/ramfs/ >> william@beaglebone:~/ramfs$ test >> william@beaglebone:~/ramfs$ echo $PATH >> >> /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/william/ramfs/ >> >> At this point I decided that the executable "test" is a bad choice for >> some reason unknown to me. >> >> >> william@beaglebone:~/ramfs$ mv test.c hello.c >> william@beaglebone:~/ramfs$ rm test >> william@beaglebone:~/ramfs$ ls -al >> total 8 >> drwxrwxrwt 2 root root 60 Mar 25 18:36 . >> drwxr-xr-x 4 william william 4096 Jan 3 16:16 .. >> -rw-r--r-- 1 william william 74 Mar 25 18:26 hello.c >> william@beaglebone:~/ramfs$ gcc hello.c -o hello >> william@beaglebone:~/ramfs$ hello >> -bash: /home/william/ramfs/hello: Permission denied >> william@beaglebone:~/ramfs$ chmod +x hello >> william@beaglebone:~/ramfs$ hello >> -bash: /home/william/ramfs/hello: Permission denied >> william@beaglebone:~/ramfs$ sudo hello >> sudo: hello: command not found >> william@beaglebone:~/ramfs$ ./hello >> -bash: ./hello: Permission denied >> william@beaglebone:~/ramfs$ chmod u+x hello >> william@beaglebone:~/ramfs$ sudo hello >> sudo: hello: command not found >> >> oops forgot about umask . . >> >> william@beaglebone:~/ramfs$ umask 022 >> william@beaglebone:~/ramfs$ sudo hello >> sudo: hello: command not found >> >> d'oh, of course this wont work . . . the executable is not in roots path. >> >> william@beaglebone:~/ramfs$ hello >> hello world ! >> william@beaglebone:~/ramfs$ ./hello >> hello world ! >> william@beaglebone:~/ramfs$ >> >> So yes, really weird the executable "test" is not working correctly on >> this system, and yes, I ran which test, and in fact . . . >> > Your not getting the usage of umask at all. It doesn't change permissions > on an existing file.. > > I'd suggest man umask... > > Mike > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
