search for: 206d

...653d 7369 gnature;.name=si 0x0110: 676e 6174 7572 652e 6173 630d 0a43 6f6e gnature.asc..Con 0x0120: 7465 6e74 2d44 6573 6372 6970 7469 6f6e tent-Description 0x0130: 3a20 5468 6973 2069 7320 6120 6469 6769 :.This.is.a.digi 0x0140: 7461 6c6c 7920 7369 676e 6564 206d 6573 tally.signed.mes 0x0150: 7361 6765 2070 6172 740d 0a0d 0a2d 2d2d sage.part....--- 0x0160: 2d2d 4245 4749 4e20 5047 5020 5349 474e --BEGIN.PGP.SIGN 0x0170: 4154 5552 452d 2d2d 2d2d 0d0a 5665 7273 ATURE-----..Vers 0x0180: 696f 6e3a 2047 6e75 5047 2076 312e...

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

...270_7!\300\325a\216\264U\000\000\067\017u(\302\177\000\000\000\375\000\000\000\000\000\000y\246\021\002\000\000\000\000\001\000\000\000\000\000\000\000\244\201", '\000' <repeats 22 times>, "U\b\000\000\000\000\000\000\000\020\000\000\000\000\000\000\060\333a\216\264U\000\000\206d-[\000\000\000\000\241\375\065\001\000\000\000\000\340\314&[\000\000\000\000\272~[1\000\000\000\000`._\216\264U\000\000\340\314&[\000\000\000\000\060\333a\216\264U\000\000`P\033(\302\177\000\000`"... status = <optimized out> gensec_security = 0x55b48e5f4380...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, this is a new attempt to improve the output of the command "btrfs fi df". The previous attempt received a good reception. However there was no a general consensus about the wording. Moreover I still didn''t understand how btrfs was using the disks. A my first attempt was to develop a new command which shows how the disks