Cleaned up quiz questions

[Rich Simms]

1) What is the numeric version of [b]rw-rw-r-–[/b] that you could use on a chmod command?

2) What command could you use to get an approximate count of all the files on Opus and ignore the permission errors?

3) For the command: [b]sort names > dogsinorder[/b] is sort getting its input from:
a) stdin
b) the command line
c) opening and reading a file called [b]names[/b]

Feel free to work the answers out on the forum,

- Rich

[Michael Wicherski]

1.
just remember
421 421 421
rw- rw- r --

4+2 4+2 4

664

2.
find /* 2>/dev/null | wc -l

(find all files in the root and pipe it into wc and count the lines
Since the display is 1 line per file, the line count tells you how many files
and 2>/dev/null redirects stderr into the bitbucket or aka THE VOID --eerie area 51 music--)

could also do

ls -lR / 2>/dev/null | wc -l
______________________


(if you leave out the redirect to bit bucket (/dev/null) you would get a more accurate idea of how many files are on the server because you would also get 1 line of "error" per file that you cannot access ... but this question specifically says to omit errors - so use the bitbucket to dump stderr (2>) into bit bucket)

3. **edit** the answer is C (didn't specify the letter of the answer before)**
the sort program opens and reads the file
(notice that stdin is not redirected, therefore the program handles the file itself.
sort <names ... would cause stdin to be redirected to the file and sort would never know it just read from a file in which case the answer for the question would be stdin)

[bobbi whitfield]

You rock,thanks!!!!!

[collin seaton]

[quote="Michael Wicherski"]
2.
find /* | wc -l 2>/dev/null

(find all files in the root and pipe it into wc and count the lines
Since the display is 1 line per file, the line count tells you how many files
and 2>/dev/null redirects stderr into the bitbucket or aka THE VOID --eerie area 51 music--)

could also do

ls -lR / | wc -l 2>/dev/null
[/quote]

The output redirection doesn't help there, you still get all the 'permission denied' errors. The reason is because 2>/dev/null is put after wc -l, which isn't throwing errors, rather find or ls is putting out the errors. The correct syntax, to just get a count, would be
[code]
find /* 2>/dev/null | wc -l
[/code]
or
[code]
ls -lR / 2>/dev/null | wc -l
[/code]

-collin

[Marcos Valdebenito]

Thanks Michael...again....

[Michael Wicherski]

[quote="collin seaton"][quote="Michael Wicherski"]
2.
find /* | wc -l 2>/dev/null

(find all files in the root and pipe it into wc and count the lines
Since the display is 1 line per file, the line count tells you how many files
and 2>/dev/null redirects stderr into the bitbucket or aka THE VOID --eerie area 51 music--)

could also do

ls -lR / | wc -l 2>/dev/null
[/quote]

The output redirection doesn't help there, you still get all the 'permission denied' errors. The reason is because 2>/dev/null is put after wc -l, which isn't throwing errors, rather find or ls is putting out the errors. The correct syntax, to just get a count, would be
[code]
find /* 2>/dev/null | wc -l
[/code]
or
[code]
ls -lR / 2>/dev/null | wc -l
[/code]

-collin[/quote]

yea good catch collin; that was just a brainfart on my part - i've fixed it - thanks