| 26af0da4f7e0fd5cc9410011ca05ff6539bbf42d |
|
02-Mar-2015 |
Hung-Te Lin <hungte@chromium.org> |
make_dev_ssd: Allow smaller kernel partition.
Some Brillo devices may have smaller kernel partition and we need to reduce the
size limit.
BUG=none
BRANCH=none
TEST=make_dev_ssd.sh applied on a Brillo config with 8MB kernel partition.
Change-Id: I9ca37445a6cdb20138f13dbe975c207383a1474c
Reviewed-on: https://chromium-review.googlesource.com/255341
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Mao Huang <littlecvr@chromium.org>
Commit-Queue: Hung-Te Lin <hungte@chromium.org>
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| 42f02139d522cc787630ee95ecf654f4410175e5 |
|
01-Nov-2014 |
Hung-Te Lin <hungte@chromium.org> |
make_dev_ssd: support devices using /dev/dm-1 as root device.
Some devices may use rootdev=/dev/dm-1 as root device (the default one was
dm-0, according to build scripts). Running make_dev_ssd.sh
--remove_rootfs_verification on these devices will fail changing rootdev kernel
command line, and cause people not able to re-mount root device as writable.
To support running make_dev_ssd on these devices, we want to change the rootdev
pattern to dm[0-9].
BUG=chromium:428041.
TEST=make_dev_ssd.sh --remove_rootfs_verification
BRANCH=none
Change-Id: Idfd251c58e7d39b0b80ec1fc68989c2f49bdd1b2
Reviewed-on: https://chromium-review.googlesource.com/226782
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Bill Richardson <wfrichar@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| 8f15d74fd64e4a4d98471221948cc8f1fde127e2 |
|
10-Jul-2014 |
Hung-Te Lin <hungte@chromium.org> |
make_dev_ssd: Allow chromeos-install to run on a modified image.
chromeos-install always expects DM verity information from install source,
because even when --noenable_rootfs_verification is applied, the output image
will still include DM verity in kernel command line (just not enabled).
To support developers installing a modified image (by
--remove_rootfs_verification), we have to change the command line to keep DM
verity data, just like how --noenable_rootfs_verification is done.
BRANCH=none
BUG=none
TEST=make_dev_ssd.sh --noenable_rootfs_verification; reboot;
chromeos-install # success.
Change-Id: I3b2c8cbf1b89086ed91b5549c7147cd940fbda14
Reviewed-on: https://chromium-review.googlesource.com/207321
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Reviewed-by: Gaurav Shah <gauravsh@chromium.org>
Commit-Queue: Hung-Te Lin <hungte@chromium.org>
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| 798cc91de11d5a78e379c67731dcafaf2aae01e1 |
|
20-Aug-2013 |
Hung-Te Lin <hungte@chromium.org> |
Change flashrom target selection parameter.
The "-p internal:bus=*" is now deprecated by "-p {host,ec}" because we may have
EC on SPI bus.
BUG=none
TEST=manually executed dev_debug_vboot and see correct output.
BRANCH=none
Change-Id: I6363c09c2ebf57812bf35b7db220303a2786db20
Reviewed-on: https://gerrit.chromium.org/gerrit/66321
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Yung-Chieh Lo <yjlou@chromium.org>
Commit-Queue: Hung-Te Lin <hungte@chromium.org>
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| 8a42c2718fce6f34baaa52146f039a2acd1477be |
|
27-Nov-2012 |
Paul Taysom <taysom@chromium.org> |
remove verity regardless of dm device
Changed the pattern substitution to work with dm-[0-9]
BUG=chromium-os:25441
TEST=Turned off verity on stumpy both with and without bootcache
BRANCH=none
Change-Id: I519ad71879f2db847f450b869c8f7a67606f1e20
Reviewed-on: https://gerrit.chromium.org/gerrit/38691
Tested-by: Paul Taysom <taysom@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Paul Taysom <taysom@chromium.org>
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| 8dde1491e59a750a71c08c3d98f7f4f659b68a05 |
|
26-Jul-2012 |
Randall Spangler <rspangler@chromium.org> |
Fix make_dev_ssd.sh --remove_rootfs_verification
It was checking for /dev/dm-0, which isn't the case anymore. It now
always attempts to remove rootfs verification from the command line;
this is harmless (no-op) if it's already removed.
BUG=chromium-os:31558
TEST=manual
/usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification
reboot
touch /opt/google/chrome/chrome
Change-Id: I62dc138e8d1d09bdcb16be3faab74d32c5f7675a
Signed-off-by: Randall Spangler <rspangler@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/28506
Reviewed-by: David James <davidjames@chromium.org>
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| a7a879e0fbada0dd148781dfe325f4c7dc09c31b |
|
01-Jul-2011 |
Hung-Te Lin <hungte@chromium.org> |
make_dev_ssd: support new %U parameter
The %U is better since arm and x86 both supports it now.
BUG=chromium-os:15683
TEST=./make_dev_ssd.sh # need latest kernel patch
Change-Id: I94a6471788d3496cfa7ef263493e89877bb2b593
Reviewed-on: http://gerrit.chromium.org/gerrit/3551
Reviewed-by: Che-Liang Chiou <clchiou@chromium.org>
Tested-by: Hung-Te Lin <hungte@chromium.org>
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| c3b877d8cb2e413816d34ed685c6a35780e07bc8 |
|
27-Jun-2011 |
Hung-Te Lin <hungte@chromium.org> |
make_dev_ssd: fix ARM device names
BUG=chromium-os:15061
TEST=(on arm) ./make_dev_ssd.sh --remove_rootfs_verification # works
Change-Id: I0ed5e02cd566c89b2604a2e77b87413dc957471e
Reviewed-on: http://gerrit.chromium.org/gerrit/3375
Reviewed-by: Bill Richardson <wfrichar@chromium.org>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Tested-by: Hung-Te Lin <hungte@chromium.org>
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| c1d8dc8aa7f2e666324e476b10c7e5cfe9c58c04 |
|
26-Apr-2011 |
Hung-Te Lin <hungte@chromium.org> |
make_dev_ssd: more sanity checks
make_dev_ssd is a powerful command bug may confuse developers by its behavior.
Adding sanity checks can prevent developers throwing their system into
un-bootable ste.
BUG=chromium-os:14219
TEST=./make_dev_ssd.sh -i some_images; # no check, pass
./make_dev_ssd.sh # see alert for live partitions
(with non-developer firmware) ./make_dev_ssd.sh --partitions 2 # seeing firmware warning
(with developer firmware) ./make_dev_ssd.sh --partitions 2 # pass, no warning
(with dev-signed normal firmware) ./make_dev_ssd.sh --partitions 2 # pass, no warning
./make_dev_ssd.sh -f # seeing 5 second condown alert screen and then continue
Change-Id: I7ae134c03899b2dc4a6d95f6d9091c38e6f8cf65
R=rspangler@chromium.org
Review URL: http://codereview.chromium.org/6870026
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| 83728d0aef71945e54b8948107361b86a95118d9 |
|
15-Apr-2011 |
Hung-Te Lin <hungte@chromium.org> |
vboot_reference: check developer firmware before running make_dev_ssd
Developers may turn on developer switch, enter shell, and then try to run
make_dev_ssd without switching to developer firmware / dev root key.
And that would make the system showing "NO GOOD" or "INSERT" screen
after reboot.
For sanity check, we should check if firmware type is "developer" before running
make_dev_ssd.
BUG=none
TEST=(using normale firmware) make_dev_ssd # seeing the error messages
sudo chromeos-firmwareupdate --mode=todev; sudo reboot
(using developer firmware) make_dev_ssd # not seeing error
Change-Id: Id62959c91c39b0bbcca604c9e83fd087e3727b8b
R=rspangler@chromium.org
Review URL: http://codereview.chromium.org/6840047
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| b5633c6f65ac593769d615970a146717ee4d328c |
|
13-Apr-2011 |
Hung-Te Lin <hungte@chromium.org> |
make_dev_ssd.sh: support updating legacy boot partitions
Change the boot default option in partition 12 (ESP) when we want to disable
rootfs verification.
BUG=chromium-os:12424
TEST=./make_dev_ssd --remove_rootfs_verification --recovery_key -i USB_IMAGE
# the image is bootable by H2C and H2C BIOS(EFI).
# Not tried on non-EFI (syslinux) firmware, but it should work.
Change-Id: I7533bb73597041bbdc8cc57e4e8baaf6ca242309
R=wfrichar@chromium.org
Review URL: http://codereview.chromium.org/6813109
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| 7f37edcf006636c40409dea8be11e4a378440e72 |
|
07-Apr-2011 |
Hung-Te Lin <hungte@chromium.org> |
vboot_reference: allow using recovery_key in make_dev_ssd.
Adding --recovery_key enables make_dev_ssd to process recovery images (including
USB bootable images).
R=gauravsh@chromium.org
BUG=chromium-os:12424
TEST=./make_dev_ssd.sh --remove_rootfs_verification --recovery_key -i /dev/sdd
# then use the USB to boot on a H2C device - success.
Review URL: http://codereview.chromium.org/6799007
Change-Id: Ie983f08ff8eba9472800b2f4097915ce380a0c50
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| a41b7bae210f34cf012327f32f6fb1a6cf97c101 |
|
30-Mar-2011 |
Hung-Te Lin <hungte@chromium.org> |
vboot_reference: remove trailing newline/space for make_dev_ssd
To make the output of kernel_config from make_dev_ssd more close to the original
images, we should eliminate the trailing newline/space.
BUG=chromium-os:13516
TEST=make_dev_ssd.sh # succcess
Change-Id: I17f030f8815dea22b04058456d98db6911888ef6
R=rspangler@chromium.org,clchiou@chromium.org
Review URL: http://codereview.chromium.org/6735009
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| 605500b88cd99097d482ddcefee4ba04898781ae |
|
18-Jan-2011 |
Gaurav Shah <gauravsh@chromium.org> |
Split common.sh into bash-only and dash-only sections
Change-Id: I044331dc3558a4f7428b75fe43ef739498d65803
BUG=chromium-os:10836
TEST=scripts that use common.sh seem to work, would appreciate help in testing Chrome OS client scripts!
Review URL: http://codereview.chromium.org/6294002
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| e37ff5d5960c3a94809f54d7e412b387a7c396e5 |
|
05-Jan-2011 |
Randall Spangler <rspangler@chromium.org> |
Check in tofactory script.
Also refactor the other scripts to move more common functions (debug output, etc.) to common.sh.
BUG=chrome-os-partner:1903
TEST=manual; ran on a Chrome notebook, verified the right things got copied.
Review URL: http://codereview.chromium.org/5878005
Change-Id: Ib7131356ecb6f88eee3d529a518f23b94756d0c0
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| 51b9b8362259f44667117473c2d78f8c9e202286 |
|
11-Dec-2010 |
Bill Richardson <wfrichar@chromium.org> |
Accept list of kernels to re-sign, instead of assuming only 2 & 4.
Change-Id: Ice7b3a9323f003654d1062f721a21f37856f44d7
BUG=chromium-os:10246
TEST=manual
This should resign kernel partitions 2 & 4, as before:
make_dev_ssh.sh --save_config foo
make_dev_ssh.sh --set_config foo
This should only resign kernel 2:
make_dev_ssh.sh --save_config foo --partition '2'
make_dev_ssh.sh --set_config foo --partition '4'
This should attempt to resign 2, 4, and 6. It's okay if not all succeed.
make_dev_ssh.sh --save_config foo --partition '2 4 6'
make_dev_ssh.sh --set_config foo --partition '2 4 6'
Review URL: http://codereview.chromium.org/5736006
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| 1615bbff9a55f3d85e6b9d33fd4829afe8b41ad5 |
|
10-Dec-2010 |
Bill Richardson <wfrichar@chromium.org> |
make_dev_ssh.sh should handle image C as well
BUG=chromium-os:10213
TEST=manual
From a shell, run
cd /tmp
/usr/share/vboot/bin/make_dev_ssd.sh --save_config foo
You should see messages about kernel A, kernel B, and kernel C. It doesn't
matter what those messages are (well, it does, but testing that is way too
complicated and only useful for dev-mode hacking).
Change-Id: I32aaeae18fb9dd957ab17a452d1ea6d7cd8fe788
Review URL: http://codereview.chromium.org/5698004
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| 38ab919c086f5bcdb9feb49f0e2f8adac9972fda |
|
03-Dec-2010 |
Randall Spangler <rspangler@chromium.org> |
Add --save_config and --set_config options to make_dev_ssd.sh
Change-Id: I691e6e62f5d5d9b6671fd05f172829b84d503b77
BUG=9934
TEST=manual
1. From a root shell, on a device signed with developer keys:
make_dev_ssd.sh --save_config=foo
This should create a foo.2 file with a kernel command line. It'll be
similar to the one in /proc/cmdline. It may create a foo.4 file, if
kernel B is also valid.
2. Modify the command line in foo.2 (and foo.4, if it exists).
Suggest adding "blah2" to foo.2, and "blah4" to foo.4 if it
exists.
3. From a root shell:
make_dev_ssd.sh --set_config=foo
4. Reboot.
5. Check the kernel command line.
cat /proc/cmdline
If you booted from kernel A, you should see "blah2" in the command
line. If B, you should see "blah4".
Review URL: http://codereview.chromium.org/5567003
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| b5c991b3b821017746c24f7f7207e53f691c30b0 |
|
08-Nov-2010 |
Hung-Te Lin <hungte@chromium.org> |
make_dev_ssd: fix --remove_rootfs_verification
The remove_rootfs_verification was corrupted by several issues:
1. enable_rw_mount (ext2 RO bit hack) should be performed on every rootfs
and only after we successfully resigned the kernel.
2. for latest images, we must first resign again before changing
boot parameter, otherwise verification would fail.
Both fixed and verified.
BUG=chromium-os:8629
TEST=(1)built a ToT image, install by USB boot, then
./make_dev_ssd --remove_rootfs_verification; then reboot.
rootdev shows /dev/sda3 and is writable.
(2)install by factory setup and then wipe so that root = sda5
./make_dev_ssd --remove_rootfs_verification; then reboot.
rootdev shows /dev/sda5 and is writable.
Change-Id: I27d92964f3fbe160a207069a39516a879de64245
Review URL: http://codereview.chromium.org/4525002
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| f5529068ecbfc6770233ab76a04849d879067ee8 |
|
22-Oct-2010 |
Will Drewry <wad@chromium.org> |
make_dev_ssd: fix the offset for enable_rw_mount
The rootfs offset was not converted to bytes. This changes fixes that.
BUG=none
TEST=ran it on an image and it found the ext2 magic
Change-Id: I814c3b89bf5246e3ceab851f80c4a4d4d7e63919
Review URL: http://codereview.chromium.org/4071002
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| aaae959412acc95ba2f4a0b5af44d67186c7a3d2 |
|
22-Oct-2010 |
Will Drewry <wad@chromium.org> |
common.sh, ...: add support for ext2-ro/rw hack
Copies the helpers from crosutils.git/common.sh but uses
printf with octals for portability. This should update all
locations where we mount root rw and disable_rw_mounts just before
a final sign.
TEST= in progres; plz help :)
BUG=chromium-os:7972
Change-Id: Ibdd23cb30335942c36d537663aabea605a2f8704
Review URL: http://codereview.chromium.org/3987001
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|
| 20525b91644a786e966c9486ac9afdf3d7c5447f |
|
16-Oct-2010 |
Hung-Te Lin <hungte@chromium.org> |
make_dev_ssd: new script to change SSD image to dev key
The make_dev_ssd.sh is made for devinstall shim to
change SSD kernels to be signed by dev keys.
- Kernel A, B will be resigned with dev keys (ignore if A/B seems not bootable)
- Adding param --remove_rootfs_verification can even disable rootfs hash check
This CL also includes some shared refine/fix to make_dev_firmware.sh
BUG=chrome-os-partner:1276
TEST=sudo ./make_dev_ssd.sh; (seeing Kernel A is resigned and B is ignored)
then reboot without developer mode (OK),
rootdev shows /dev/dm-0, rootdev -s shows /dev/sda3
sudo ./make_dev_ssd.sh --remove_rootfs_verification;
then reboot without developer mode (OK), rootdev shows /dev/sda3
Change-Id: Ic20f734b2af42e50a43c19a565a166a39d57a7fd
Review URL: http://codereview.chromium.org/3772013
/external/vboot_reference/scripts/image_signing/make_dev_ssd.sh
|