aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLeah Rowe <info@minifree.org>2016-10-14 10:54:21 +0100
committerLeah Rowe <info@minifree.org>2016-10-14 10:54:21 +0100
commitc15fc86040beffcf0f9fdc02aea9085e73391b5c (patch)
treeba2458ba33a4f999c0fbea813759b72b76ff6367
parent675aea2e2bfcfbe0401dc6b4fef9b1bde5ab764a (diff)
downloadlibrebootfr-c15fc86040beffcf0f9fdc02aea9085e73391b5c.tar.gz
librebootfr-c15fc86040beffcf0f9fdc02aea9085e73391b5c.zip
docs/index: re-add information about finding the version (moved from FAQ)
-rw-r--r--docs/index.html54
1 files changed, 53 insertions, 1 deletions
diff --git a/docs/index.html b/docs/index.html
index d0946ecb..3798d288 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -196,9 +196,61 @@
<h1>How do I know what version I'm running?</h1>
<p>
- See <a href="https://libreboot.org/faq/#version">https://libreboot.org/faq/#version</a>
+ If you are at least 127 commits after release 20150518
+ (commit message <em>build/roms/helper: add version information to CBFS</em>)
+ (or you have any <strong>upstream</strong> stable release of libreboot after 20150518), then you can
+ press C at the GRUB console, and use this command to find out what version of libreboot you have:<br/>
+ <strong>cat (cbfsdisk)/lbversion</strong><br/>
+ This will also work on non-release images (the version string is automatically generated,
+ using <em>git describe --tags HEAD</em>), built from the git repository.
+ A file named <em>version</em> will also be included in the archives that you downloaded (if you are
+ using release archives).
</p>
+ <p>
+ If it exists, you can also extract this <em>lbversion</em> file by using the <i>cbfstool</i> utility
+ which libreboot includes, from a ROM image that you either dumped or haven't flashed yet.
+ In your distribution, run cbfstool on your ROM image (<em>libreboot.rom</em>, in this example):<br/>
+ $ <strong>./cbfstool libreboot.rom extract -n lbversion -f lbversion</strong><br/>
+ You will now have a file, named <em>lbversion</em>, which you can read in whatever program
+ it is that you use for reading/writing text files.
+ </p>
+
+ <p>
+ For git, it's easy. Just check the git log.
+ </p>
+
+ <p>
+ For releases on or below 20150518, or snapshots generated from the git repository below 127 commits
+ after 20150518, you can find a file named <em>commitid</em> inside the archives. If you are using
+ pre-built ROM images from the libreboot project, you can press C in GRUB for access to the terminal,
+ and then run this command:<br/>
+ <strong>lscoreboot</strong><br/>
+ You may find a date in here, detailing when that ROM image was built. For pre-built images distributed
+ by the libreboot project, this is a rough approximation of what version you have, because the version
+ numbers are dated, and the release archives are typically built on the same day as the release; you can
+ correlate that with the release information in <a href="release.html">release.html</a>.
+ </p>
+ <p>
+ For 20160818, note that the lbversion file was missing from CBFS on GRUB images. You can still find out
+ what libreboot version you have by comparing checksums of image dumps (with the descriptor blanked out with 00s,
+ and the same done to the ROMs from the release archive, if you are on a GM45 laptop).
+ </p>
+ <p>
+ There may also be a ChangeLog file included in your release archive, so that you can
+ look in there to figure out what version you have.
+ </p>
+
+ <p>
+ You can also check the documentation that came with your archives, and in <em>docs/release.html</em> will be
+ the information about the version of libreboot that you are using.
+ </p>
+
+ <p>
+ Generally speaking, it is advisable to use the latest version of libreboot.
+ </p>
+
+
</div>
<div class="section">