From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: [ANNOUNCE] salinfo 1.1 is available
Date: Mon, 13 Feb 2006 17:34:33 +0000 [thread overview]
Message-ID: <200602131034.33693.bjorn.helgaas@hp.com> (raw)
Keith has put together salinfo 1.1, available here:
ftp://kernel.org/pub/linux/kernel/people/helgaas/salinfo-1.1.tar.bz2
The changelog is:
* mandir patch to Makefile, from SuSE.
* gcc 4 alias fixes, from SuSE.
* Remove spurious exports from /etc/sysconfig/salinfo_decode_all,
from SuSE.
* salinfo_decode_all has to catch signals so it can send them to its
children. SuSE's killproc sends three signals in quick succession,
STOP, TERM, CONT which can cause a timing race where only the last
one caught by salinfo_decode_all gets through to the children. Do
not catch SIGSTOP or SIGCONT, so killproc's SIGTERM gets through to
the children.
* Set some sensible defaults for MCA and INIT rate limiting.
* Remove SGI specific decoding of nasid, now done in SGI's
salinfo_decode_oem.
* Detect and drop duplicate records. This gives SAL the flexibility to
save some records that would normally be lost over a reboot, without
creating duplicate records in the filesystem.
* Fix pointer signedness warnings from gcc 4.1.
* Released as 1.1.
reply other threads:[~2006-02-13 17:34 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=200602131034.33693.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.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