pixelbeat__

9 ms·

1.
by pixelbeat__ 5mo ago
A direct link to the Ubuntu post https://discourse.ubuntu.com/t/an-update-on-rust-coreutils/8...
2.
Updating yes(1) to run at 175GiB/s(github.com)
6 points by pixelbeat__ 6mo ago|0 comments
3.
by pixelbeat__ 7mo ago
Some of this elegance discussed from a programmatic point of view https://www.pixelbeat.org/docs/utf8_programming.html
4.
by pixelbeat__ 9mo ago
LOL (I used to work for Meta, so appreciate the facetious understatement)
5.
by pixelbeat__ 11mo ago
It seems dotslash would complement uv well https://dotslash-cli.com/docs/ DotSlash to get the interpreter for your platform, and uv to get the dependencies. Perfect for corporate setups with custom mirrors etc.
6.
by pixelbeat__ 11mo ago
GRUB is mentioned but not detailed. Here are some details: https://www.pixelbeat.org/docs/disk/
7.
by pixelbeat__ 11mo ago
https://github.com/coreutils/coreutils/commit/14d24f7a5 That bring GNU date(1) line coverage from 79.8% to 87.1%
8.
by pixelbeat__ 1y ago
I see you use flags to determine if a file needs syncing. When we used fiemap within GNU cp we required FIEMAP_FLAG_SYNC to get robust operation. (We have since removed the fiemap code from cp, and replaced it with LSEEK_DATA, LSEEK_HOLE)
9.
by pixelbeat__ 1y ago
The benchmark is against unibyte text. You would get more accurate results by doing `export LC_ALL=C` in your benchmark script
10.
by pixelbeat__ 1y ago
Note the terminal -> HTML conversion used to serve wttr.in is based on https://github.com/pixelb/scripts/blob/master/scripts/ansi2h...
11.
by pixelbeat__ 2y ago
A similar tool for ini files https://www.pixelbeat.org/programs/crudini/
12.
by pixelbeat__ 2y ago
I wrote about ASCII and UTF-8 elegance at: https://www.pixelbeat.org/docs/utf8_programming.html
13.
by pixelbeat__ 2y ago
rxzec
14.
by pixelbeat__ 2y ago
The commit with more details on that perf change is: https://github.com/coreutils/coreutils/commit/fcfba90d0d27a1... A summary of other changes just released in GNU coreutils 9.5 are: - mv accepts --exchange
15.
by pixelbeat__ 3y ago
(Hi Giuseppe!) Right, the standard centos system binaries are used to provision services and manage hardware. The internal services linking against the runtime libs you mention, are actually linking against about 2000 built from source pack
16.
by pixelbeat__ 3y ago
Use ldd on any service binary to see that it's linked against a separate distro. (It's best to use the ldd from the corresponding platform). There are actually three distros on each host. Current runtime platform, previous runtime
17.
by pixelbeat__ 3y ago
It's worth noting that this discusses the centos based provisioning and hardware management platform. The actual distribution used to _run_ all Meta backend services is completely separate and built from source (it does share the (non
18.
by pixelbeat__ 3y ago
Reminds me of my website from 2006 (not entirely reproduced) at https://web.archive.org/web/20060208131821/http://www.pixelb...
19.
by pixelbeat__ 3y ago
Definitely not
20.
by pixelbeat__ 3y ago
All the main platforms have realpath(1). It was added to GNU Linux over 10 years ago now, to aid portability, and be a more natural command to access this functionality than readlink(1)
21.
by pixelbeat__ 3y ago
Yes, macos takes its utils from FreeBSD. An interesting factoid is that FreeBSD/macos sort(1) was using GNU code until recently, since this is quite tricky to implement. Eventually it was reimplemented for GPL avoidance reasons. We do
22.
by pixelbeat__ 3y ago
czkawka is basically a rust port of my python FSlint tool, which I no longer have time to maintain: https://www.pixelbeat.org/fslint/
23.
by pixelbeat__ 3y ago
Padding is only required if concatenating / streaming encoded data. I.e. when there are padding chars _within_ the encoded stream. Padding chars at the end (of stream / file / string) can be inferred from the length already p
24.
by pixelbeat__ 3y ago
We generally give credit if at all possible. Even if a patch is extensively adjusted, we'll commit under the original author's name
25.
by pixelbeat__ 3y ago
I optimized yes because: * The fast version is still simple enough * The general functionality being provided is to output arbitrary data repeatedly, and it can be useful to do this as fast as possible
26.
by pixelbeat__ 3y ago
The gnulib manywarnings module is useful to add as many warnings as appropriate in a portable manner https://www.gnu.org/software/gnulib/manual/html_node/manywar... That's used in dev mode for vario
27.
by pixelbeat__ 3y ago
There have been various attempts to improve on strcpy() etc. The current thinking is that strscpy() is the best general interface to this functionality. See the "improving ... strcpy" section at https://www.pixelbeat.or
28.
by pixelbeat__ 3y ago
String handling in C has many gotchas indeed. Here are some of my notes on the subtleties: https://www.pixelbeat.org/programming/gcc/string_buffers.htm...
29.
by pixelbeat__ 4y ago
Oh I will reference this from https://www.pixelbeat.org/programming/shell_script_mistakes.... where I also advise against this common archaic idiom
30.
by pixelbeat__ 4y ago
This technique is useful for running things that normally run quickly, but sometimes need more time. The technique is used extensively in the GNU coreutils test suite, as detailed in the "performance" section at https:/&#x2F

More ›