public inbox for initramfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	debian-kernel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org,
	kernel-team-nLRlyDuq1AZFpShjVBNYrg@public.gmane.org
Subject: initramfs-tools 0.130 release
Date: Wed, 26 Apr 2017 02:16:46 +0100	[thread overview]
Message-ID: <1493169406.2474.8.camel@decadent.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]

This update, together with the unannounced 0.129, fixes more bugs than
you might imagine possible in a <40-line script:

- Setting the RESUME variable anywhere other than
  /etc/initramfs-tools/conf.d/resume was ignored
- Setting the RESUME variable to UUID=something or LABEL=something
  was ignored
- The fallback to automatic selection of the biggest swap partition
  actually sorted by dictionary order, not numeric order, of size
- There was no way to disable this automatic selection

All of which went largely unnoticed, since most systems have no more
than one swap partition, and if the resume device wasn't available at
boot we would (until version 0.128) ignore that.

I would like to automatically filter out swap device types that we know
won't be available at boot (e.g. zram).  But I think this will have to
do for now.  The resume hook will report when it fixes up a blank or
invalid RESUME value, and the NEWS file also explains the changes and
the new option of RESUME=none.

Ben.

Ben Hutchings (12):
      hooks/resume: Use correct sort options to select the biggest swap partition
      initramfs.conf(5): Clean up split between general and NFS variables
      Support setting of RESUME in initramfs.conf or anywhere in conf.d/
      initramfs.conf(5): Document the RESUME variable
      hooks/resume: Check for chroot earlier
      Allow disabling resume from disk at build time by setting RESUME=none
      Support requesting automatic selection of resume device with RESUME=auto
      hooks/resume: Report when we might be doing something surprising
      NEWS: Add entry explaining the need for RESUME=none on some systems
      Releasing version 0.129.
      hooks/resume: Fix validation of resume devices specified by UUID etc.
      Releasing version 0.130.

-- 
Ben Hutchings
All extremists should be taken out and shot.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2017-04-26  1:16 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=1493169406.2474.8.camel@decadent.org.uk \
    --to=ben-/+tvbiectbitmtq+vha3yw@public.gmane.org \
    --cc=debian-kernel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=kernel-team-nLRlyDuq1AZFpShjVBNYrg@public.gmane.org \
    /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