a67aab7083
To add a string to your cmos.layout, you need to specify type 's': #start len type unused name 416 512 s 0 boot_devices With this patch you can do $ nvramtool -w boot_devices="(hd0,0);(hd2,1);(hd3)" And FILO will attempt to load a menu.lst from any of these devices in that order. The patch is not exactly pretty, but a cleaner solution might have resulted in a complete rewrite of the tool, which I did not want. Signed-off-by: Stefan Reinauer <stepan@coresystems.de> Acked-by: Joseph Smith <joe@settoplinux.org> git-svn-id: svn://svn.coreboot.org/coreboot/trunk@3613 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
49 lines
1.1 KiB
RPMSpec
49 lines
1.1 KiB
RPMSpec
##
|
|
|
|
Name: nvramtool
|
|
Version: 2.1
|
|
Release: 0
|
|
|
|
Summary: coreboot utility program
|
|
Group: System Environment/Base
|
|
License: GPL
|
|
Provides: nvramtool
|
|
|
|
BuildRoot: %{_tmppath}/%{name}-%{version}
|
|
|
|
Source0: %{name}-%{version}.tgz
|
|
|
|
%description
|
|
nvramtool is a utility for reading/writing coreboot parameters and displaying
|
|
information from the coreboot table.
|
|
|
|
At boot time, coreboot places a table (known as the coreboot table) in low
|
|
physical memory. The contents of this table are preserved even after
|
|
coreboot transfers control to the kernel and the kernel initializes itself.
|
|
The coreboot table contains various system information such as the type of
|
|
mainboard in use. It also specifies locations in the CMOS (nonvolatile RAM)
|
|
where the coreboot parameters are stored.
|
|
|
|
%prep
|
|
%setup -n %{name}-%{version}
|
|
|
|
%build
|
|
make
|
|
|
|
%install
|
|
rm -rf "$RPM_BUILD_ROOT"
|
|
mkdir -p "$RPM_BUILD_ROOT/usr/bin"
|
|
mkdir -p "$RPM_BUILD_ROOT/usr/man/man1"
|
|
cp nvramtool "$RPM_BUILD_ROOT/usr/bin"
|
|
cp nvramtool.1.gz $RPM_BUILD_ROOT/usr/man/man1
|
|
|
|
%clean
|
|
rm -rf "$RPM_BUILD_ROOT"
|
|
|
|
%files
|
|
%defattr(-,root,root,0755)
|
|
%doc ChangeLog README
|
|
%doc README
|
|
/usr/bin/nvramtool
|
|
/usr/man/man1/nvramtool.1.gz
|