aboutsummaryrefslogtreecommitdiff
path: root/release/i386/make-memstick.sh
Commit message (Collapse)AuthorAgeFilesLines
* Make i386 memstick images bootable.Ed Maste2020-05-241-9/+0
| | | | | | | | | | | | | | | | | | | | | | This reverts the i386 part of r342283, "Rework UEFI ESP generation", and the followup commit in r342690. r342283 added an ESP to the i386 memstick image, and as a side effect made the ESP the active partition, not the bootcode-containing UFS partition. As a result the i386 memstick images would not boot in either UEFI or legacy mode - UEFI failed because we do not support i386 UEFI booting, and legacy mode failed because the partition with legacy bootcode was not active. The bootcode-containing UFS partition is again the only, and active, partition. PR: 246494 Reported by: Jorge Maidana Differential Revision: The FreeBSD Foundation Notes: svn path=/head/; revision=361437
* Escape a new line following r342283.Glen Barber2019-01-021-1/+1
| | | | | | | Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=342690
* Rework UEFI ESP generationRebecca Cran2018-12-201-0/+9
| | | | | | | | | | | | | | | | Currently, the installer uses pre-created 800KB FAT12 filesystems that it dd's onto the ESP partition. This changeset improves that by having the installer generate a FAT32 filesystem directly onto the ESP using newfs_msdos and then copying loader.efi into /EFI/freebsd. For live installs it then runs efibootmgr to add a FreeBSD boot entry in the BIOS. Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D17947 Notes: svn path=/head/; revision=342283
* switch i386 memstick installer images to MBREd Maste2018-04-121-5/+3
| | | | | | | | | | | | | | | | | | | | | | | Some BIOSes have trouble booting from GPT in non-UEFI mode. This is commonly reported with Lenovo laptops, including my x220. As we do not currently support booting FreeBSD/i386 via UEFI there's no reason to prefer GPT. The "vestigial swap partition" was added in r265017 to work around an issue with loader's GPT support, so we should not need it when using MBR. We may want to make the same change to amd64, although the issue there is mitigated by such systems booting via UEFI in the common case. PR: 227422 Reviewed by: gjb MFC after: 3 weeks Relnotes: Yes Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=332446
* make-memstick.sh: put partition args on separate linesEd Maste2018-04-101-1/+6
| | | | | | | | | | | | This makes it easier to identify the individual partition types and facilitates comparisons across architectures. Reviewed by: gjb MFC after: 1 week Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=332390
* make-memstick.sh: use UFSv2Ed Maste2017-09-111-1/+1
| | | | | | | | | | | | | | | | | | There's not much practical difference as far as install media is concerned but newfs creates UFSv2 by default and it is sensible to use the contemporary UFS version. I also intend to change makefs to create UFSv2 by default (to match newfs) so we'll want make-memstick.sh to be explicit, rather than relying on the host tool's default. Reviewed by: andrew, gjb, jhibbits MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D12231 Notes: svn path=/head/; revision=323438
* revert unintentional changes from r323436Ed Maste2017-09-111-1/+1
| | | | Notes: svn path=/head/; revision=323437
* boot1: remove BOOT1_MAXSIZE default valueEd Maste2017-09-111-1/+1
| | | | | | | | | | | | This Makefile relies on Makefile.fat providing the correct value for BOOT1_MAXSIZE and BOOT1_OFFSET. Since BOOT1_OFFSET had no default value here the build would already fail if Makefile.fat did not provide correct values. Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=323436
* make-memstick.sh: use 'set -e' to abort if any step failsEd Maste2017-09-051-4/+2
| | | | | | | | | | | | | | | Also remove the now-redundant error handling that was only for makefs. This change applies arm64's r308171 to the other make-memstick.sh versions. Reviewed by: gjb MFC after: 1 week Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D12195 Notes: svn path=/head/; revision=323178
* Prevent memstick installation medium from attempting to mountGlen Barber2016-01-051-0/+2
| | | | | | | | | | | | | | the root filesystem read-write. This causes problems booting the memstick installation medium from write-protected USB flash drives. Submitted by: A.J. Kehoe IV [1], Oliver Jones [2] PR: 187161 [1], 205886 [2] MFC after: 1 week Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=293188
* Use mkimg(1) to create the i386 memstick images, similar toGlen Barber2015-05-231-10/+3
| | | | | | | | | | | how is done for amd64. The exception here is there is no EFI partition for i386. MFC after: 3 days Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=283307
* Fix indentation for diff reduction with commits to follow.Glen Barber2014-04-251-11/+11
| | | | | | | Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=264933
* Revert r264907 and r264908:Glen Barber2014-04-251-61/+16
| | | | | | | | | | | | | | | Restore make-memstick.sh back to its original state to unbreak booting for machines that do not support GPT. I have in-progress work to keep the MBR layout and add the EFI partition, but it is not yet ready, and does need at least one full release build to be certain it does not break. Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=264922
* Style cleanupGlen Barber2014-04-251-24/+24
| | | | | | | | | | | | | - Indent 1 full tab where needed - Use $() for shell exec - Insert a space between '$(( ))' parens MFC After: 1 week X-MFC-With: r264907 Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=264908
* Refactor make-memstick.sh to avoid creating the 'dangerouslyGlen Barber2014-04-251-6/+51
| | | | | | | | | | | | | | | | | | | | | | dedicated' partition scheme, reported to cause the memstick.img to fail to boot. Similar to how make-memstick.sh worked on stable/8, use makefs(8) to create the actual filesystem. Then calculate the size of the resulting image file, create the GPT partition scheme, then dd(1) the filesystem created with makefs(8) to the freebsd-ufs GPT partition. This was tested on a known-working machine[1] for regression, and a known-not-working machine[2] to ensure the boot issue has been resolved. Testers: myself [1], db [2] MFC After: 1 week Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=264907
* Use UFS labels and bsdlabels (like the 8.x memsticks) instead of GPT toNathan Whitehorn2011-10-091-35/+5
| | | | | | | | | fix problems with some BIOSes. MFC after: 3 days Notes: svn path=/head/; revision=226170
* Mount memsticks read-only by default to prevent them being filled byNathan Whitehorn2011-07-301-1/+1
| | | | | | | | | user modifications and subsequently preventing a functioning installation. Approved by: re (kib) Notes: svn path=/head/; revision=224504
* Use labels to find release media instead of hard-coded device paths. ThisNathan Whitehorn2011-03-221-14/+9
| | | | | | | | | | | makes booting more reliable (and working at all on USB sticks). While here, move responsibility for setting up fstab into the various platform mk-*.sh scripts. Suggested by: many Notes: svn path=/head/; revision=219856
* Add generation of memstick images to the bsdinstall release makefile forNathan Whitehorn2011-03-131-0/+83
i386 and amd64. This involved moving the memstick generation script to the arch directories from scripts/, in analogy to mkisoimages.sh. This script was never called from /usr/src/release/Makefile, so that hasn't been updated. Notes: svn path=/head/; revision=219584