From: Matt_Domsch@Dell.com
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] efibootmgr 0.4.0-test4
Date: Thu, 03 Jan 2002 18:20:33 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805738@msgid-missing> (raw)
I've made a newer efibootmgr. ChangeLog below. Most important change is
that write_variable() no longer has a hard-coded "victim" file in
/proc/efi/vars to open, it now searches the list of files to find one it's
not actively writing. This is necessary because the EFI 1.1 sample
implementation changed the name of the file we had been using as the
"victim". :-)
Posted to
http://domsch.com/linux/ia64/efibootmgr/efibootmgr-0.4.0-test4.tar.gz.
Feedback welcome.
* Thu Jan 3 2002 Matt Domsch <Matt_Domsch@dell.com>
- added back in read last sector IOCTL hack, but only after read() fails.
- released v0.4.0-test4
* Thu Jan 3 2002 Matt Domsch <Matt_Domsch@dell.com>
- more cleanups
- released v0.4.0-test3
* Wed Jan 2 2002 Matt Domsch <Matt_Domsch@dell.com>
- Changed PROC_DIR_EFI to PROC_DIR_EFI_VARS
- write_variable() now searches /proc/efi/vars for a variable that's not
the one being written. The EFI 1.1 sample implementation changed the
name of the "victim" being written to (was Efi-xxxxx, now EFI-xxxxx), so
previous versions of efibootmgr don't work with the new firmware. This
should fix that up.
- released v0.4.0-test2
* Fri Dec 7 2001 Matt Domsch <Matt_Domsch@dell.com>
- Removed read last sector ioctl hack, it's not needed anymore. The
kernel takes care of it for us with a new patch.
- Added test for valid PMBR, similar to parted and the kernel.
- Added test for returning size of block device as a u64.
- Added test for returning sector size as int, and use that.
- Changed GPT struct and member names to be more Linux-like.
- added -g option to force disk with invalid PMBR to be treated as GPT
anyhow.
- released v0.4.0-test1
--
Matt Domsch
Sr. Software Engineer
Dell Linux Solutions www.dell.com/linux
#1 US Linux Server provider with 24.5% (IDC Dec 2001)
#2 Worldwide Linux Server provider with 18.2% (IDC Dec 2001)
reply other threads:[~2002-01-03 18:20 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=marc-linux-ia64-105590698805738@msgid-missing \
--to=matt_domsch@dell.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