public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin-announce@cygwin.com
Subject: Updated: util-linux 2.33.1-2
Date: Tue, 14 Apr 2020 02:19:37 -0700 (PDT)	[thread overview]
Message-ID: <Pine.BSF.4.63.2004100021530.19019@m0.truegem.net> (raw)


The following packages have been uploaded to the Cygwin distribution:

* util-linux-2.33.1-2
* libblkid1-2.33.1-2
* libblkid-devel-2.33.1-2
* libfdisk1-2.33.1-2
* libfdisk-devel-2.33.1-2
* libsmartcols1-2.33.1-2
* libsmartcols-devel-2.33.1-2
* libuuid1-2.33.1-2
* libuuid-devel-2.33.1-2
* uuidd-2.33.1-2

This is a re-spin of Cygwin's current util-linux release 2.33.1 that
adds a 'taskset' executable.  Taskset takes advantage of the recent
addition of cpu affinity support to Cygwin.  It allows one to assign
Cygwin processes to a specific cpu or cpus.

I'd like to thank Cygwin user Eliot Moss for his encouragement in
getting cpu affinity support added to Cygwin, and his patches that
made possible the clean building of this util-linux update.

Questions and/or comments to the Cygwin mailing list please:
cygwin (at) cygwin (dot) com

..mark

                 reply	other threads:[~2020-04-14  9:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.BSF.4.63.2004100021530.19019@m0.truegem.net \
    --to=mark@maxrnd.com \
    --cc=cygwin-announce@cygwin.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).