Eliminating "permission denied" when /dev/null also gives 'permission denied'

Question

I am new to *nix and I am trying to find some files that I know are supposed to be somewhere on the system, but I am not sure where they might be or if they were even ever copied over from another project.

I was getting way too many “permission denied” messages to make sense of when using find. I searched and found this How can I exclude all “permission denied”-messages from “find .”? , but now I have a new problem.

find / -name trim*  -print 2>/dev/nul

gives me

bash: /dev/nul: Permission denied

I searched a bit for someone with a similar issue, but I couldn't find one amid all the posts talking about 2>/dev/nul as a solution to the “permission denied”-messages

This question appears to be off-topic because it is about misspelling `/dev/null` as `/dev/nul` and not expecting error messages. — devnull, Oct 29 '13 at 08:10
Sorry about the silly question then. http://stackoverflow.com/questions/1296843/what-is-the-difference-between-null-0-and-0 — Seraphya, Oct 29 '13 at 13:25

score 1 · Answer 1 · answered Oct 29 '13 at 08:11

1

As Barmar said, you spell nul instead of null

find / -name trim*  -print 2>/dev/null

answered Oct 29 '13 at 08:11

Thomas Ayoub

29,063
15
95
142

1

...and since /dev/nul doesn't exist, the shell tries to create it, and that's what gives the permissions error. – Gordon Davisson Oct 29 '13 at 15:40

Eliminating "permission denied" when /dev/null also gives 'permission denied'

1 Answers1