On 2012-11-21 07:42 (GMT+0100) Oddball composed:
EeePc-Rob-SFN9:~ # cat /dmesg > /home/oddball/Documenten/dmesg_output.txt cat: /dmesg: Bestand of map bestaat niet (=file or directory does not exist) EeePc-Rob-SFN9:~ #
EeePc-Rob-SFN9:~ # cat /bin/dmesg > /home/oddball/Documenten/dmesg_output.txt EeePc-Rob-SFN9:~ #
Btw, the output is, like you say, completely unreadable, while #dmesg -x shows a normal, humanly readable output in the terminal window. But i can copy and paste this into a textfile to study.
EeePc-Rob-SFN9:~ # cat dmesg > /home/oddball/Documenten/dmesg_output.txt cat: dmesg: Bestand of map bestaat niet (=file or directory does not exist) EeePc-Rob-SFN9:~ #
Catting a binary file into a text file is a nonsense process. If you want to look inside a binary file, just use a file viewer (e.g. F3 running MC). That way you'll be able to see the whole thing instead of whatever content proceeds the EOF marker, not that you'll make sense of more than a few bunches of text strings. Dmesg is a command. You don't cat it. Catting is for combining files, and viewing human readable files. OTOH, 'dmesg > /home/oddball/Documenten/dmesg_output.txt' is all human readable, just like what's already in /var/log/messages. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org