Displaying 2 results from an estimated 2 matches for "204d".
Did you mean:
2048
2007 Feb 24
0
1.4.0 spews garbage on CLI, crashes
...350\304\372S\260\264\267\342\205jS\216#7\323\326v\264\344\225D\267[eGy\335^D+b#\231\333\333Dj\210\316zf\217E\326\214\223\245-\324\326V\271\232\221\303^EF\220\331X\217\243\234%\342GZ\217\204w#q\272\316\221\344\326l\221\310'\326X.\371\222\327&X\244\357\221$J\332^A\233\372\331\343$^L+L\362\333\204D\234\243Tt\325\227F\375\221\223\243G^_\211-\213\335\243I=,\354\\225d\263'\212I"\341#\207oj\272\352\325^T\206\275D\343$\214\363\262KQ\233^D^K#u\334\225\352\242\355\\227\346[Feb
24 16:07:20] WARNING[777]: codec_gsm.c:140 gsmtolin_framein: Invalid
GSM data (1)
[Feb 24 16:07:20] WARNING[777]: t...
2008 Jul 14
5
EOL in stderr of ssh - Linux
Hello everyone,
recently I've found something I consider a bug.
Correct me if I'm wrong, but I always thought that Linux' EOL is 0x0A.
Imagine my surprise when I saw that all messages that are being output
on to the stderr (on any Linux I've tested - Fedora and Ubuntu) are
terminated with 0x0D, 0x0A.
Maybe that's standard behaviour of all stderr messages in all Linux