Theodore Ts'o dixit:
>That being said, a quick Google search would have turned up this
>explanation of the orphan_file feature, from the kernel documentation:
>
>
> https://www.kernel.org/doc/html/latest/filesystems/ext4/globals.html#orphan-file
Yes, that’s what I found later as well, when I was still wondering
what it was good for.
The use case I was thinking of when looking in manpages was to
figure out the exact syntax for tune2fs from a rescue system of
some kind while offline.
>The TL;DR is[…]
Right, it does make sense.
>So first of all, I very much doubt that the Debian Release Managers
>would consider a documentation addition to be critical enough to
>warrant a backport to Debian Stable, since that seems to be reserved
>for critical bug fixes, especially those that are security related. I
Right… but perhaps if you have to update it anyway, or so…
>Secondly, while I do backport from Debian Testing (trixie) to Debian
>Backports (bookworm-backports), there is certainly no policy which
>mandates that a package be backported.
Of course not, but given you already backported from testing(bookworm)
to bullseye, Backports policy indicates that the backport should be
kept in sync with later updates to then-testing or at least be brought
up to the version now in bookworm-as-stable.
>I suppose if I had time I could try to wrangle an upload to
>bullseye-backports-sloppy, although I've generally not bothered to do
>backports to Debian oldstable.
That gets old really soon, yes, but the existing backport in
bullseye-backports (not -sloppy) should be updated at least.
This would give the world a slightly better-than-average chance
at obtaining a tune2fs and e2fsck capable of working with that.
(For example, I can install most bullseye packages on the live
ISO I use as it was cut from testing not too long before the
release… I actually have been considering trying to re-roll it
based on the bullseye release, with all security and other fixes
applied and a few more packages included.)
I do know that adding changes unrelated to backporting is also
frowned upon, but the second-to-last entry in /u/s/d/e/c.D.gz
will at least contain the two magic words needed, and that may
be enough.
Thanks,
//mirabilos
--
08:05⎜<XTaran:#grml> mika: Does grml have an tool to read Apple
⎜ System Log (asl) files? :)
08:08⎜<ft:#grml> yeah. /bin/rm. ;) 08:09⎜<mrud:#grml> hexdump -C
08:31⎜<XTaran:#grml> ft, mrud: *g*
