Phoronix IRC Log: 2009-04-25
Bartman007: do the phoronix-test-suite maintainers care about non-critical errors during test compilation?
michaellarabel: Bartman007: Depends what it is
Bartman007: michaellarabel: first example is the failure of a flac example app when using gcc 4.3
Bartman007: the example is worthless but makes compilation look a bit ugly
Bartman007: I'm putting together a patch series that adds missing external deps for packages, fixes compilation errors, and if desired fixing failures like this
michaellarabel: Bartman007: Great, thanks :D
jt_: hi guys..
jt_: i was hoping someone could help me with my *nix homework..
Milyardo: hahah :)
Milyardo: *nix homework huh?
jt_: yer a few commands i dnt understand
Milyardo: oh like?
jt_: rm -f $(find / -name core) &> /dev/null
Milyardo: So what part don't you understand?
jt_: oretty much da whole thing
Bartman007: $(echo foo) will evaluate to "foo"
Bartman007: $( ) runs the command inside and returns the result
Milyardo: so it will first file any and all files with the patter "core" in them
Milyardo: and run the resulting command
Bartman007: Milyardo: it you find any files named exactly 'core' filenames containing core will not match
jt_: oh ok..but rm -f ir removing a file right
Milyardo: well thats still the pattern right Bartman007?
Milyardo: the pattern is exactly core
Milyardo: not core*
Milyardo: or ^core or anything else
Milyardo: that you could put in there
Bartman007: Milyardo: right, but since this guy is just starting out I wanted to make it explicitly clear :)
Milyardo: and yes jt_ rm -f is removing the file
Milyardo: the -f option is force
Bartman007: jt_: it will remove any result found from the command within $( )
jt_: and whats the dev null at the back
Milyardo: The ampersand &, forks the process to the background, and the > redirects STDOUT to null( dunno why they did that, there wouldn't be any output anyways since you suppressed any prompts with -f and didn't use the -v option)
Milyardo: for example
Bartman007: no. &>/dev/null redirects stdout and stderr to /dev/null
Milyardo: if you did `echo foo > ~/somefile.txt
Milyardo: right, thought there was a space there
Bartman007: it isn't stanard POSIX syntax, it's a bashism (ksh may handle it too)
Bartman007: yeah, it's a bashism. ksh redirects stdout but uses the & to fork it into the background
Bartman007: so you were right depending on the shell :)
jt_: oh kool thnx guys..i got it..
jt_: wat bout this one ls -l > ls-l
jt_: i know ls -l is long listing but whats the switch >
jt_: cudnt find it in man ls
Bartman007: > redirects stdout to the file after it, in this case "ls-l"
Bartman007: 2> redirects stderr
Bartman007: and >> appends to the file instead of replacing it
jt_: oh yer i did that in web..
jt_: last one ==ls -l | sed -e "s/[aeio]/u/g"
jt_: ls -l long listing..
jt_: sed -e stream editor ..
jt_: in this case -e measn adding a script
jt_: and the last part im lost
Milyardo: its a search and replace command for sed
jt_: lol ur kidding
Milyardo: replace [aeio] with u
Milyardo: so it replaces all vowels with u
jt_: ir replaces all aeio vowels with u...
Milyardo: I guess y isn't replaced
Milyardo: to techincaly its not all vowel
jt_: thnx a lot guys..
jt_: i got it down..
jt_: i should know these by now..
jt_: ive been running Arch for at least2 years..
jt_: i guess i never went intot he nitty gritty :)
jt_: does grep "\.txt$" mean filter for \.txt with anything after txt
Milyardo: the \. part is an esacpe for the . charater
Milyardo: so the . is interpreted literaly, instead of as a special character
Milyardo: so it would filer for anything with .txt in it
Milyardo: at then end I mean
Milyardo: the $ means the pattern before must come at the end of a sting
jt_: ohh ok
Milyardo: ^ means the beginning
jt_: i dont get the \ though..
jt_: does that represent the filename without extension/
Milyardo: \ is the escape character
jt_: wats dat
Milyardo: like if wanted to search for a file that had a " in it
Milyardo: but " is a special character
Milyardo: I'd use \" to escape it and make the " be interpreted literaly
Milyardo: the same thing applies to \.
jt_: oh k
Milyardo: it makes the period literal, and not a special character
jt_: i got it...
jt_: thnx a lot Milyardo..
Milyardo: indeed it is late
Milyardo: and I should goto bed
jt_: wat time is it ?
jt_: where are you?
Milyardo: 3:30 AM
jt_: which country u in?
peppo: any news or hints of an updated fglrx that works OK with compositing and xorg 1.6?
Ivanovic: muhaha, good joke...
Ivanovic: that is: depends on what "kind" of compositing you want (compiz or kwin, xrender or opengl, ...)
Ivanovic: and what exactly you mean with this (if you eg mean "handling of xv while composite is active" or stuff like this)
Ivanovic: in general composite with fglrx works a lot better under gnome (with compiz) than under kde (with kwin and xrender)