From: Cedric Blancher <cedric.blancher@gmail.com>
To: Mark Geisert <mark@maxrnd.com>,
Corinna Vinschen <corinna-cygwin@cygwin.com>
Cc: cygwin@cygwin.com
Subject: Re: /usr/bin/fallocate missing in Cygwin 3.5's "util-linux" ...
Date: Thu, 25 Jan 2024 10:37:42 +0100 [thread overview]
Message-ID: <CALXu0Ud8xEj4eeqAHpd53_iu1DdLeeGP0FL0bpVkktsABFaAPw@mail.gmail.com> (raw)
In-Reply-To: <cc15ff74-ccf1-40d3-bd6b-fe37fbb6aefa@maxrnd.com>
On Thu, 25 Jan 2024 at 04:53, Mark Geisert via Cygwin <cygwin@cygwin.com> wrote:
>
> On 1/23/2024 4:41 PM, Mark Geisert via Cygwin wrote:
> > On 1/23/2024 3:36 AM, Roland Mainz via Cygwin wrote:
> >> Small bug report:
> >> Cygwin 3.5. now has support for SEEK_HOLE (thanks! :-) ), but
> >> /usr/bin/fallocate is still missing in the "util-linux" package.
> >>
> >> Can someone please enable that tool ?
> >
> > I'll look into this.
>
> A new build of the util-linux package, 2.33.1-3, now includes fallocate
> and its man page. The updated package is now making its way to the
> Cygwin mirrors. fallocate requires Cygwin version >= 3.5.0.
Thank you.
The GNU coreutils package (cp, mv), GNU tar (tar), pax (pax) and
libarchive packages need to be rebuild, as they all support SEEK_HOLE.
@Corinna Vinschen Could you please include these updated packages as
'sparse file aware', as they support SEEK_HOLE?
Ced
--
Cedric Blancher <cedric.blancher@gmail.com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
next prev parent reply other threads:[~2024-01-25 9:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 11:36 Roland Mainz
2024-01-24 0:41 ` Mark Geisert
2024-01-25 3:53 ` Mark Geisert
2024-01-25 9:37 ` Cedric Blancher [this message]
2024-01-25 9:38 ` Cedric Blancher
2024-01-27 7:26 ` ASSI
2024-01-27 10:06 ` Mark Geisert
2024-01-27 15:47 ` Marco Atzeri
2024-01-28 9:08 ` Mark Geisert
2024-01-24 6:33 ` Cedric Blancher
2024-01-24 8:30 ` Sam Edge
2024-01-24 8:51 ` Cedric Blancher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALXu0Ud8xEj4eeqAHpd53_iu1DdLeeGP0FL0bpVkktsABFaAPw@mail.gmail.com \
--to=cedric.blancher@gmail.com \
--cc=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=mark@maxrnd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).