#coreutils
i mean all i've got to say is look at how coreutils in rust is going 🙃
November 17, 2026 at 5:25 PM
Microsoft distributes uutils Rust-based “Coreutils” as “Microsoft.Coreutils”. Engagement , invest in this project: close to #$NULL.

Coreutils is a pretty generic term, you say? So is “PowerShell”. Prove me wrong.
November 18, 2026 at 9:29 PM
coreutils-9.13/ChangeLog:

2026-11-16

version 9.13
- `whoami` now detects fronting headmate (~93% accuracy)
November 16, 2026 at 11:01 AM
Today, while cleaning up `fuq` for publishing, I learned that the Unix coreutils don't work very well on Classic Macintosh computers because they all assume that the line separator is LF, and MacOS V9 and prior used CR exclusively. Coreutils also leaves Window's CR (in CR/LF) as a non-sep char.
November 15, 2026 at 9:00 PM
Ubuntu 26.10 completes its move to the Rust uutils coreutils, cp, mv and rm included.

The top HN comment: uutils rm segfaulting on a 32K-deep directory that GNU rm deletes. Test your scripts on the new base images.

https://www.omgubuntu.co.uk/2026/09/ubuntu-2610-rust-coreutils-complete
November 17, 2026 at 9:12 AM
My first open source contribution got merged. A small fix in uutils/coreutils (the Rust rewrite of GNU coreutils): a test broke when /bin/sh is bash, because bash silently ignores SIGQUIT. Kinda cool.
github.com/uutils/coreu...
stdbuf: fix test_stdbuf_reports_signalled_command when /bin/sh is bash by lmilz · Pull Request #16355 · uutils/coreutils
The test fails because on CachyOS /bin/sh is bash. However, bash ignores SIGQUIT and exits with 0. I changed it to SIGKILL because it cannot be ignored. SIGKILL is signal 9 for every unix-based sys...
github.com
November 15, 2026 at 10:38 AM
nobody seems to think foundational libraries like this for universally needed logic are going away because of agents. or at least not all of them. would be interesting to try to articulate which have longevity and which get vendored out of existence
November 16, 2026 at 1:38 AM
#uutils #coreutils
Windowsならuutils-coreutils-lean入れておくと
coreutils cat .\tl.ps1
のように使える
busyboxと同じような考え方だね
既存コマンドはそのままがいいしね
November 13, 2026 at 6:03 AM
I haven't tried it on a share, but plain cp may do it. Since coreutils 9.0 cp calls copy_file_range, which the Linux cifs client sends as FSCTL_SRV_COPYCHUNK_WRITE and a vers=4.2 NFS mount as a COPY, if the server supports it. Apps that copy with read and write move every byte through you.
November 16, 2026 at 3:07 PM
Ubuntu 26.10 (Stoking Stingray) chegou com a transição completa dos Coreutils para Rust, as primeiras ferramentas de IA local sem envio de dados para a nuvem, o GNOME 51 com gerenciamento inteligente de memória youtu.be/mKltmObRrpc

#Ubuntu #Linux #Ubuntu2610 #OpenSource
Ubuntu 26.10: O Fim dos Problemas no Desktop Linux?🛠️
YouTube video by Rikerlinux
youtu.be
November 15, 2026 at 11:02 PM
1/5

Latest Slackware current update:

16 updates

Mon Nov 16 22:44:02 UTC 2026
a/coreutils-9.12-x86_64-4.txz: Rebuilt.
DIR_COLORS: add more media format extensions:
.3g2, .3gp, .apng, .avif, .cda, .m4a, .ts, and .weba.
a/gawk-5.4.2-x86_64-1.txz: Upgraded.
November 17, 2026 at 12:01 AM
uutils/coreutils の touch PR にメンテナから返事が来てた。rebase と未解決コメントへの対応を求められてる。ちゃんと見ないとクローズされちゃいそう。対応するのが楽しみのようなプレッシャーのような…まずは cargo fmt からかな
November 18, 2026 at 11:52 PM
The question is: do I go the extra mile for the Windows people and try to detect CR/LF (especially if the input is gonna be LF-sep'd and the output NULL-sep'd), or do I comply with the expectation of coreutils that only linefeed matters?
November 15, 2026 at 9:00 PM
Good news everyone!

Just in time for Ubuntu if they go on another bender and decide to go with an arbitrary coreutils port in a new programming language, I present coreutils in BASIC.

https://github.com/fbxl-sj0/fbxl_gnu_coreutils
November 10, 2026 at 8:44 PM
Published my blog post about Info-ZIP, the project behind the zip and unzip utilities on most Linux distros that had their last stable release in 2009. Ended up being really long, I hope it is an interesting read:

https://voxelmanip.se/2026/11/13/info-zip-widespread-and-unmaintained/

#blog #linux
Info-ZIP - Widespread and Unmaintained
On every Linux system, is it very likely that you have the zip and unzip commands available. They are so commonplace that you may assume they are part of the GNU coreutils, or some other GNU project such as gzip. However, these utilities are actually part of a project called Info-ZIP, which saw its last stable release in 2009. In the absence of public announcements from Info-ZIP or a primary third-party fork, Linux distributions have each maintained their own set of patches to address the increasing amount of vulnerabilities and other issues in the tools. However, there is a question of how long this can be sustained as the last stable releases continue to age. It also begs the question, what actually happened to Info-ZIP?
voxelmanip.se
November 14, 2026 at 12:07 AM
1,600 words hard
Piping Hot: how hard can it be to have a realtime, unbuffered, streaming, non-newline-delimited regex filter pipeline in Bash?
I have spent hours on this problem more than once. I hope this saves someone from a bad afternoon. ### The problem We are used to piping things to `grep` or `sed`, and getting output. But, sometimes, the source isn't a list of lines. Sometimes, the text you want to run a regex replace on is a _stream_. Two real-life examples: 1. A stream of dictated text 2. Streamed output from Llama.cpp server Here, we run into two issues: 1. Many coreutils buffer input and/or output 2. Many of the Unix coreutils operate on lines by default. Sed is the most obvious example. ### Test case Here's an example that will let us test our solutions, and prove that most of them don't work. Create a file: touch /tmp/realtimestream Now, tail it: tail -f /tmp/realtimestream Now, in a new terminal, append something to it, without a newline: echo -n "Hello, tail. How are you?" >> /tmp/realtimestream ... and watch it arrive in terminal #2, as intended, the moment you hit enter. Now, open another terminal, and try to filter the output of tail in realtime: tail -f /tmp/realtimestream | sed 's/([,;:.?!])/\1\n/g' ... and watch nothing come out when you run the echo command. This is, like, a really dumb problem to have. We are trying to replace punctuation with newlines (or anything else), to feed into xargs. But sed, also, requires a newline before it starts processing the input, and there _aren't_ any _._ And sed is strictly linewise: it doesn't let you set the delimiter. ### Solutions people suggest that don't work Yes, pipelines are buffered, often. That can be part of the problem, but the main problem is that you can't use linewise tools on streaming input. You will see many mentions of `stdbuf -o0 command`. It won't help, because that's not the problem. But once you fix the newlines problem, buffering might be your new problem. You'll also likely encounter the more comprehensive `stdbuf -i0 -o0 -e0 command` (that's setting the stdin, stdout, and stderr buffers to 0, rather than just stdout like the first example). As far as I can tell, you can have a space between the flag and the value, or not, so you might also see people write `stdbuf -i 0 -o 0 -e 0 command`) `stdbuf` works for things that use LD_PRELOAD, which isn't everything. If that doesn't work you can try `unbuffer command` (from the expect package), which is easier to remember, but may have side effects. `sed -u` or `sed --unbuffered` doesn't help either, because it still needs newlines. `tr` doesn't need newlines. It operates on characters. So you can do `tr ',.:?!;' '\n\n\n\n\n\n'`, but it's not what we want, because it swallows the characters it matches against, replacing them, and doesn't support regex. (For more, read Julia Evans's fantastic post on buffering.) But, solving buffering still doesn't solve our problem. ### The one that got away I thought this one was going to work. I've never grokked awk, and have only used snippets other people write. AI pointed me to Record Splitting with Gawk, and I adapted the example, by trial and error, to this: gawk 'BEGIN { RS = "([,.;:!?—])" } { print $0RT;} ' This _looks_ like it's going to work. However, if you try it, you will find that though it outputs the first two split lines correctly, it it swallows the last line, and saves it and outputs it at the _next_ echo. So the first time you get: Hello, tail. ... and each subsequent echo: How are you? Hello, tail. This is, I gather, because there's never a terminator, so gawk remains hopeful/uncertain about whether more input is coming that might match the regex. No amount of `system("")` `fflush("")`ing will save you. (Believe me, I flushed everything: even paper towels.) ### Dinosaur riding 101 I have never used Perl much. I thought Perl was dead! It turns out, it's not: it just _looks_ that way. (I jest.) This approach was first recommended by AI. Then I threw out what the AI gave me and started from scratch with the sources it had pointed me to, so I would understand it better. Here's the final snippet: tail -f /tmp/realtimestream | perl -pe '$| = 1; $/ = \1; s/([,;:.?!])/\1\n\n/g' | sed 's|are you|art thou|g' Let's break it down: We call perl with the `-pe` flags. This basically lets us write a script as an argument, and automatically prints the results. I found an explanation of flags in paxdiablo's answer here (read it, it's funny: "_`-p`: Places a printing loop around your command so that it acts on each line of standard input. Used mostly so Perl can beat the pants off Awk in terms of power AND simplicity :-)_"). I think of -e as "eval", though I don't know if that's what it means. AI recommended a BEGIN block. I'm not sure why, but it doesn't seem to be necessary, so I skipped it. See Eric Strom's answer here if you want to know what BEGIN means. I recognized this from awk; I didn't know it was a Perl thing. I assumed that Awk got it from Perl, but no: Awk pre-dates Perl (more things I didn't know!), and according to an eight year old Reddit comment by a deleted user, Perl copied BEGIN from Awk. _And_ , Awk is a full blow programming language (I always though of it as one of the coreutils, not a programming language; but maybe Kernighan did also?). There's just so much I don't know, and that I would have never learned if I hadn't gone to the sources. If there's one thing we've learned, it's that almost all the coreutils buffer input/output, and most of them have a flag to disable it. `$| = 1` is how you tell Perl not to buffer stdio, according to _Automating System Administration with Perl, 2nd Edition_ by David N. Blank-Edelman (O'Reilly, 2009) — which AI provided me with a free PDF of, hosted on a Chinese website — and also to perlvar's section on output autoflush ("_Mnemonic: when you want your pipes to be piping hot_."), and a StackOverflow thread that I lost. Then, we tell Perl to read input one character at a time, using the `$/ = \1` "special construct" described here, which is also discussed in this perlmonks thread, and in the perlvars section on the input record separator. Apparently this is really inefficient and there are better ways to do it, but for my use case, it doesn't matter, and I chose the simple solution that I could understand. _(Fun fact: make sure the slashes are going opposite directions, like a pyramid. When I typoed that first slash (_`$\ = \1` _), it worked, but kept spitting out_`SCALAR(0x637398f65be0)` in with the output, which had me very confused until I noticed my mistake._)_ Another gotcha: if we are reading one character at a time, what about unicode? Can we regex an em-dash? I thought this wouldn't work. But it _partly_ works. It appears to match the em-dash. However, the capture group replacement doesn't work with em-dashes, so they can be passed through without getting matched, or they can be matched, but they get swallowed. However, you can use a literal em-dash in the replacement, so you could match them in a separate Perl snippet, and replace them with "—\n". Unwieldy, but it would work! There's likely a better solution that I am not motivated enough to find. `s/search/replacement/g` Finally, we get to the thing we have been trying to do, in order to the the thing we have been trying to do. And the syntax is just like `sed`, so I immediately felt at home. (Who got it from who?!) I have `s/([,;:.?!]{1,4})/\1\n/g`, which appends a newline after punctuation (excepting em-dashes, ellipses, and actual interrobangs). This means sed gets what it wants: newline delimited data. Finally, we can filter our stream! `sed 's|are you|art thou|g'` which just `s`ubstites search with replacement `g`lobally (ie, not just first match). Now, try it. Run the whole thing: tail -f /tmp/realtimestream | perl -pe '$| = 1; $/ = \1; s/([,;:.?!])/\1\n\n/g' | sed 's|are you|art thou|g' And then, in another terminal: echo -n "Hello, tail. How are you?" >> /tmp/realtimestream It works! We are done. We are _so_. _done._ * * * **Appendix** There's a lot of choice humor to be found in the primary sources on this stuff, which you might expect to be dry and academic. From the Wikipedia page on Perl: > It has been nicknamed "the Swiss Army chainsaw of scripting languages" because of its flexibility and power.[21] In 1998, it was also referred to as the "duct tape that holds the Internet together", in reference to both its ubiquitous use as a glue language and its perceived inelegance.[22] And, perusing _The GNU Awk User's Guide_ ¶ 9.1.5 Input/Output Functions, we find this paragraph: > In the past, `awk`’s `system()` function simply returned the exit status value divided by 256. In the normal case this gives the exit status but in the case of death-by-signal it yields a fractional floating-point value.56 POSIX states that `awk`’s `system()` should return the full 16-bit value. And, way down yonder, in footnote 56: > In private correspondence, Dr. Kernighan has indicated to me that the way this was done was probably a mistake.
www.autodidacts.io
November 17, 2026 at 10:44 PM
Strip apt, dpkg, bash and coreutils from your Debian runtime image after install to cut attack surface. Here's the Dockerfile RUN block: #container #attack-surface #ValtersIT https://www.valtersit.com/vault/reduce-image-attack-surface-by-removing-package-manager-and--da8625/
Reduce Image Attack Surface by Removing Package Manager and Shell
www.valtersit.com
November 12, 2026 at 9:40 AM
Everything is part of your interface, mkdir edition: if mkdir (the program) races with something else on the directory creation (starts out with the directory not there, both do mkdir(2)), Coreutils mkdir apparently exits status 1 while the Ubuntu 26.04 Rust uutils mkdir exits status 0 even […]
Original post on mastodon.social
mastodon.social
November 11, 2026 at 9:10 PM
uutils/coreutilsのsortで、外部ソート中の一時ファイル書き込みが失敗したときにpanicで落ちる問題を直した話をZennに書きました。unwrapをやめてCLIとして正しくエラーを返す経路にする修正で、tmpfsを使った回帰テストの設計もまとめてます。 https://zenn.dev/tasodoufu/articles/rust-sort-temp-write-errors
November 12, 2026 at 12:59 AM
⚒️ FIXED IN iOS and iPadOS 27.2.1 ⚒️

- 2 bugs in CoreUtils
- 2 bugs in Messages
- 1 bug in AirPlay
- 1 bug in App Intents
and 3 other vulnerabilities fixed
https://support.apple.com/en-us/149715

#apple #infosec
November 9, 2026 at 8:16 PM
The discourse about Rust replacements of coreutils and other unix utilities is really unhinged and overblown. These replacements not hitting 100% compliance is not a crisis and no one expected that! I think it's mostly cranky greybeard change-haters and rust-fearers
November 7, 2026 at 12:28 AM
(Full disclosure, am a former Ubuntu Security Team members, but wasn't involved in either the sudo or coreutils decisions.)
November 7, 2026 at 12:59 AM
As someone who works on GNU coreutils, I find it annoying that Ubuntu has made their selling point replacing our project for the past 2 years while never participating in GNU coreutils upstream. As mentioned in the release notes, uutils has also copied our code: github.com/uutils/coreu...
Release 0.12.0 · uutils/coreutils
Rust Coreutils 0.12.0 Release: We are happy to announce the release of Rust Coreutils 0.12.0 - a release focused on compatibility fixes for our Ubuntu friends. Ubuntu ships uutils coreutils as its ...
github.com
November 7, 2026 at 7:31 AM
iPhoneに多数の脆弱性発覚。Bluetooth経由でメモリ破損の恐れなど9件、一挙修正アプデ配信へ
Appleは11月9日(米国時間)、iOS 27.2.1とiPadOS 27.2.1を配信しました。対象はiPhone 11以降と、iPad(第9世代)以降などのiPadです。 Bluetoothの通信範囲にいる攻撃者にメモリを破損させられる恐れがある脆弱性など、9件の脆弱性に対処。iPhoneの利用者は早めに更新しておきたいところです。 修正されたBluetoothの脆弱性(CVE-2026-113970)は、解放済みのメモリを使ってしまう「use-after-free」と呼ばれる問題。Bluetoothの通信範囲にいる攻撃者によって、プロセスのメモリを破損させられる可能性があったと説明されています。 また、Bluetoothのペアリングに関わる問題も複数修正されました。CoreUtilsでは、悪意のあるBluetooth機器が利用者の操作なしにペアリングを確立できる恐れがある問題(CVE-2026-113965)を修正しています。 加えて、Bluetoothの通信範囲にいる攻撃者がペアリングコードの試行回数の制限を回避し、利用者の操作なしにペアリングできる恐れがある問題(CVE-2026-113964)も修正されました。 さらにAirPlayでも、Bluetoothの通信範囲にいる攻撃者がペアリングコードの試行回数の制限を回避できる恐れがある問題(CVE-2026-113968)を修正。rapportdでも、同じネットワーク上の攻撃者がAirPlayのペアリングコードの試行回数の制限を回避できる恐れがある問題(CVE-2026-113969)が直されています。 メッセージアプリでは、リモートの攻撃者がiMessageのグループチャットに参加し、そのメッセージを受信できる恐れがある問題(CVE-2026-113961)を修正。グループに追加された人が、参加前に送られたメッセージを見られる恐れがある問題(CVE-2026-113960)も直されています。 このほか、アプリが利用者の機密データにアクセスできる恐れがあるApp Intentsの問題や、細工された入力の処理でメモリが破損する恐れがあるbrotliの問題も修正されました。一方、Appleは今回の脆弱性について、悪用の報告には触れていません。 同じ日には、iOS 27に更新していないiPhone 11以降向けのiOS 26.7.3も配信され、Bluetoothやペアリング、iMessageのグループの問題などを修正しています。 そしてiOS 27やiPadOS 27に対応しないiPhone XS、iPhone XS Max、iPhone XRやiPad(第7世代)向けにもiOS 18.7.12とiPadOS 18.7.12が配信され、Bluetoothやペアリングに関わる問題が修正されました。 MacやApple Watch、Apple Vision Pro向けにも、macOS Golden Gate 27.2.1やwatchOS 27.2.1、visionOS 27.2.1などが同時に配信されています。iPhoneは「設定」→「一般」→「ソフトウェアアップデート」から更新可能です。 Bluetoothの通信範囲という条件は、満員電車やカフェなど、知らない人と至近距離に居合わせる日常の場面では決して狭くありません。利用者の操作なしに勝手にペアリングされたり、iMessageのグループに外部から侵入されたりする恐れがあるだけに、Appleが悪用の報告に触れていない今のうちに更新を済ませておきたいところです。
smhn.info
November 11, 2026 at 1:50 AM