All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Pool <mbp@samba.org>
To: linux-ia64@vger.kernel.org
Subject: Re: efibootmgr 0.4.2-test1
Date: Fri, 01 Aug 2003 01:54:10 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105970299504064@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105967815211635@msgid-missing>

On 31 Jul 2003, Matt_Domsch@Dell.com wrote:
> Announcing efibootmgr 0.4.2-test1.  If you have systems you can test
> this on, please do so.

It seems to work in brief tests on an rx2600 with Debian stable and
2.5.72.

Perhaps you could provide a bit more context in the introduction to
help people new to the platform?  Perhaps something like this:

cd ~/work/efibootmgr/efibootmgr-0.4.2-test1/src/man/man8/
diff -u -p /home/mbp/work/efibootmgr/efibootmgr-0.4.2-test1/src/man/man8/efibootmgr.8.docbook.orig /home/mbp/work/efibootmgr/efibootmgr-0.4.2-test1/src/man/man8/efibootmgr.8.docbook
--- /home/mbp/work/efibootmgr/efibootmgr-0.4.2-test1/src/man/man8/efibootmgr.8.docbook.orig	2002-04-06 13:46:54.000000000 +1000
+++ /home/mbp/work/efibootmgr/efibootmgr-0.4.2-test1/src/man/man8/efibootmgr.8.docbook	2003-08-01 11:52:21.000000000 +1000
@@ -92,11 +92,11 @@
     
     <note>
       <para>
-        &manpackage; requires that the kernel module efivars be loaded 
-        prior to use.  <command>'modprobe efivars'</command> should do the trick.
+        &manpackage; requires that the kernel support access to EFI
+        non-volatile variables (through <filename>/proc/efi/vars</filename>).
+        <command>'modprobe efivars'</command> should do the trick.
       </para>
     </note>
-
   </refsect1>
   <refsect1>
     <title>OPTIONS</title>

Diff finished at Fri Aug  1 11:53:10


Regards,
-- 
Martin 

  reply	other threads:[~2003-08-01  1:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31 19:02 efibootmgr 0.4.2-test1 Matt_Domsch
2003-08-01  1:54 ` Martin Pool [this message]
2003-08-01  2:09 ` Matt_Domsch

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-105970299504064@msgid-missing \
    --to=mbp@samba.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.