summaryrefslogtreecommitdiffstats
path: root/release/i386
Commit message (Collapse)AuthorAgeFilesLines
* Merge the following from ^/projects/release-vmimage:gjb2014-10-141-0/+173
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r273076, r273077, r273079, r273095: r273076: Add a separate make(1) target to release/Makefile to build FreeBSD virtual machine disk images for use on the Microsoft Azure service. For now, this target is not directly connected to the build, however can be manually invoked. The 'vm-azure' target invokes {amd64,i386}/mk-azure.sh, which does the heavy lifting to produce proper VHDs. mk-azure.sh uses a configuration file, defaulting to tools/azure.conf if otherwise unset. r273077: Clear VM_RC_LIST. r273079: Fix signal list to trigger umount(8). r273095: Output an informational message when mkimg(1) runs, so it does not appear that the process has stopped while waiting for a 'y/n' response when waagent is deprovisioned. Tested on: releng/10.1@r272876 MFC after: 3 days X-MFC-10.1: yes Sponsored by: The FreeBSD Foundation
| * Add a separate make(1) target to release/Makefile togjb2014-10-141-0/+171
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | build FreeBSD virtual machine disk images for use on the Microsoft Azure service. For now, this target is not directly connected to the build, however can be manually invoked. The 'vm-azure' target invokes {amd64,i386}/mk-azure.sh, which does the heavy lifting to produce proper VHDs. mk-azure.sh uses a configuration file, defaulting to tools/azure.conf if otherwise unset. Sponsored by: The FreeBSD Foundation
| * Revert r272793, r272794, r272795:gjb2014-10-141-40/+0
| | | | | | | | | | | | | | | | | | | | Remove implementation of vm_prebuild_setup(), vm_setup(), and vm_postbuild_setup(). It does not scale well, and I am not happy with their implementation. Sponsored by: The FreeBSD Foundation
| * Reference vm_prebuild_setup(), vm_setup(), andgjb2014-10-091-0/+9
| | | | | | | | | | | | vm_postbuild_setup() functions. Sponsored by: The FreeBSD Foundation
| * Allow mk-vmimage.sh to accept a configuration file asgjb2014-10-091-0/+19
| | | | | | | | | | | | an argument to '-c'. Sponsored by: The FreeBSD Foundation
| * Add prototypes for build-specific tuning:gjb2014-10-091-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - vm_prebuild_setup(): Steps to run prior to creating the file-backed disk image. - vm_setup(): Steps to run while the file-backed disk image is mounted. - vm_postbuild_setup(): Steps to run after the file-backed disk image is dismounted. The intention is to override as necessary via build configuration files, as needed. Sponsored by: The FreeBSD Foundation
| * Add /usr/local/bin and /usr/local/sbin to PATH, neededgjb2014-10-091-1/+1
| | | | | | | | | | | | | | | | if third-party software needs to use utilities outside of the base system during post-install stages (indexinfo is one culprit). Sponsored by: The FreeBSD Foundation
| * If the vm-base target fails, prevent the vm-image targetgjb2014-10-021-0/+11
| | | | | | | | | | | | from being run since it cannot possibly succeed. Sponsored by: The FreeBSD Foundation
| * Remove the first argument to panic(), which was initiallygjb2014-10-021-7/+5
| | | | | | | | | | | | | | | | | | intended to be the exit code, however when a non-zero exit code was returned to release/Makefile, this would prevent any remaining (and possibly successful) stages from being attempted. Sponsored by: The FreeBSD Foundation
| * Avoid using env(1) to set values passed to mk-vmimage.sh,gjb2014-10-011-6/+47
| | | | | | | | | | | | | | | | | | and instead pass the values as arguments to the script, making it easier to run this by hand, without 'make release'. Add usage_vm_base() and usage_vm_image() usage helpers. Sponsored by: The FreeBSD Foundation
* | Merge the following from ^/projects/release-vmimage:gjb2014-10-141-8/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r272436, r272437, r272792: r272436: Remove the first argument to panic(), which was initially intended to be the exit code, however when a non-zero exit code was returned to release/Makefile, this would prevent any remaining (and possibly successful) stages from being attempted. r272437: If the vm-base target fails, prevent the vm-image target from being run since it cannot possibly succeed. r272792: Add /usr/local/bin and /usr/local/sbin to PATH, needed if third-party software needs to use utilities outside of the base system during post-install stages (indexinfo is one culprit). MFC after: 3 days X-MFC-10.1: yes Sponsored by: The FreeBSD Foundation
* | Merge the following revisions from ^/projects/release-vmimage:gjb2014-10-021-0/+188
|\ \ | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r272234, r272236, r272262, r272264, r272269, r272271, r272272, r272277, r272279, r272376, r272380, r272381, r272392, r272234, r272412: r272234: Initial commit to include virtual machine images as part of the FreeBSD release builds. This adds a make(1) environment variable requirement, WITH_VMIMAGES, which triggers the virtual machine image targets when not defined to an empty value. Relevant user-driven variables include: o VMFORMATS: The virtual machine image formats to create. Valid formats are provided by running 'mkimg --formats' o VMSIZE: The size of the resulting virtual machine image. Typical compression is roughly 140Mb, regardless of the target size (10GB, 15GB, 20GB, 40GB sizes have been tested with the same result). o VMBASE: The prefix of the virtual machine disk images. The VMBASE make(1) environment variable is suffixed with each format in VMFORMATS for each individual disk image, as well as '.img' for the source UFS filesystem passed to mkimg(1). This also includes a new script, mk-vmimage.sh, based on how the VM images for 10.0-RELEASE, 9.3-RELEASE, and 10.1-RELEASE were created (mk-vmimage.sh in ^/user/gjb/thermite/). With the order in which the stages need to occur, as well as sanity-checking error cases, it makes much more sense to execute a shell script called from make(1), using env(1) to set specific parameters for the target image than it does to do this in make(1) directly. r272236: Use VMBASE in place of a hard-coded filename in the CLEANFILES list. r272262: Remove a 'set -x' that snuck in during testing. r272264: release/Makefile: Connect the virtual machine image build to the release target if WITH_VMIMAGES is set to a non-empty value. release/release.sh: Add WITH_VMIMAGES to RELEASE_RMAKEFLAGS. release/release.conf.sample: Add commented entries for tuning the release build if the WITH_VMIMAGES make(1) environment variable is set to a non-empty value. r272269: release/Makefile: Include .OBJDIR in DESTDIR in the vm-base target. release/release.sh: Provide the full path to mddev. r272271: Fix UFS label for the root filesystem. r272272: Remove comments left in accidentally while testing, so the VM /etc/fstab is actually created. r272277: Remove the UFS label from the root filesystem since it is added by mkimg(1) as a gpt label, consistent with the fstab(5) entry. r272279: Comment cleanup in panic() message when mkimg(1) does not support the requested disk image format. r272376: Separate release/scripts/mk-vmimage.sh to machine-specific scripts, making it possible to mimic the functionality for non-x86 targets. Move echo output if MAKEFLAGS is empty outside of usage(). Remove TARGET/TARGET_ARCH evaluation. r272380: Avoid using env(1) to set values passed to mk-vmimage.sh, and instead pass the values as arguments to the script, making it easier to run this by hand, without 'make release'. Add usage_vm_base() and usage_vm_image() usage helpers. r272381: After evaluating WITH_VMIMAGES is non-empty, ensure the mk-vmimage.sh script exists before running it. r272392: Add WITH_COMPRESSED_VMIMAGES variable, which when set enables xz(1) compression of the virtual machine images. This is intentionally separate to allow more fine-grained tuning over which images are compressed, especially in cases where compressing 20GB sparse images can take hours. r272412: Document the new 'vm-image' target, and associated release.conf variables. r272413: Remove two stray comments added during the initial iterations of testing, no longer needed. MFC after: 5 days X-MFC-10.1: yes Tested on: r272269, r272272, r272279, r272380, r272392 Sponsored by: The FreeBSD Foundation
| * Separate release/scripts/mk-vmimage.sh to machine-specificgjb2014-10-011-0/+147
|/ | | | | | | | | | | scripts, making it possible to mimic the functionality for non-x86 targets. Move echo output if MAKEFLAGS is empty outside of usage(). Remove TARGET/TARGET_ARCH evaluation. Sponsored by: The FreeBSD Foundation
* Fix indentation for diff reduction with commits to follow.gjb2014-04-251-11/+11
| | | | Sponsored by: The FreeBSD Foundation
* Revert r264907 and r264908:gjb2014-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
* Style cleanupgjb2014-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
* Refactor make-memstick.sh to avoid creating the 'dangerouslygjb2014-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
* Update the pkg-stage target to be more compatible with pkg-1.2:gjb2014-01-161-36/+0
| | | | | | | | | | | | | | | | | | - Add a release-dvd.conf pkg(8) configuration file to override the default FreeBSD.conf configuration. - Remove architecture-specific pkg-stage.conf files, consolidate, and move their contents to scripts/pkg-stage.sh. - Use 'pkg -vv' to determine the ABI, which is used as the cache directory. Prior to these changes, it would be possible for pkg-stage to fetch conflicting binary packages from multiple repositories. Tested against: head@r260522, stable/10@r260522 MFC after: 3 days X-Insta-MFC: possibly Sponsored by: The FreeBSD Foundation
* Simplify PKG_ABI for pkg-stage.sh.gjb2013-11-181-1/+1
| | | | | | | Submitted by: hrs MFC after: 3 days X-MFC-With: r258310 Sponsored by: The FreeBSD Foundation
* Fix how ABI is evaluated so it matches more than a dot-zerogjb2013-11-181-1/+1
| | | | | | | | case. MFC after: 3 days X-MFC-With: r258310 Sponsored by: The FreeBSD Foundation
* Set the PKG_CACHEDIR directory to 'dvd/' instead of 'release/'gjb2013-11-181-1/+1
| | | | | | | | in preparation of adding a 'dvd1.iso' target. MFC after: 3 days X-MFC-With: r258305, r258307, r258308 Sponsored by: The FreeBSD Foundation
* Add a script and configuration files to fetch pre-built packagesgjb2013-11-181-0/+36
| | | | | | | | | | | | | | | | | | | | | | | from pkg.FreeBSD.org for inclusion on release medium (dvd1.iso). The script sources ${.CURDIR}/${TARGET}/pkg-stage.conf, which sets several environment variables, such as the pkg(8) ABI, PACKAGESITE, PKG_DBDIR, and PKG_CACHEDIR. PKG_CACHEDIR is set to the directory on the release medium used by bsdconfig(8) (/packages/${ABI}). ABI is determined by output of 'make -C /usr/src/release -V REVISION'. See pkg.conf(5) for descripton on other variables set here. The list of packages to include are set within the configuration file. The script and configuration files are intended to be run by the 'make dvd' target within the release directory, and assume the release is built within a chroot environment (such as by using release.sh). Relevant updates to release/Makefile will follow. Sponsored by: The FreeBSD Foundation
* - Add CHECKSUM.* support in Makefile[1].hrs2013-02-031-1/+2
| | | | | | | | | | | | - Use ln -fs to create a symlink. - Remove pkgadd for docports. - Use WITHOUT_JADETEX=yes instead of WITH_JADETEX=no. - Add {WORLD,KERNEL}_FLAGS to [BTWK]MAKE. - Use makefs(8) and gpart(8) for sparc64 ISO image[2]. - Add publisher option to makefs(8)[2]. Based on work by: gjb[1] Discussed with: marius, nwhitehorn[2]
* ISO 9660 specification allows only "d-characters" and "a-characters" in thehrs2013-01-081-2/+2
| | | | | | Volume Descriptor (section 7.4). In short, upper-case alphanumeric + some symbols only. While the makefs utility automatically converts the characters, $LABEL should be consistent in the scripts.
* Use UFS labels and bsdlabels (like the 8.x memsticks) instead of GPT tonwhitehorn2011-10-091-35/+5
| | | | | | fix problems with some BIOSes. MFC after: 3 days
* Farewall, sysinstall! You served us well for many years, but 10.0 is onenwhitehorn2011-10-032-93/+0
| | | | | | | | digit beyond your time. Various sysinstall dependencies (e.g. libftpio, libdisk, libodialog, etc.) will be cleaned up in coming days. Some will take longer than others due to a few other consumers (tzsetup and sade).
* Mount memsticks read-only by default to prevent them being filled bynwhitehorn2011-07-301-1/+1
| | | | | | user modifications and subsequently preventing a functioning installation. Approved by: re (kib)
* Garbage collect some unused variables and stray debug code.nwhitehorn2011-05-051-1/+0
| | | | Submitted by: marius
* Repair release CD generation on PC98 and sun4v after release buildingnwhitehorn2011-05-041-23/+5
| | | | | | | | changes, and backport the new logic (ISO images are TARGET dependant, not TARGET_CPUARCH dependant) to Makefile.sysinstall. While modifying ISO image scripts, change several archs to use makefs (from base) instead of mkisofs (from ports) which makes release CD generation both faster and self-hosting.
* Use labels to find release media instead of hard-coded device paths. Thisnwhitehorn2011-03-222-14/+12
| | | | | | | | 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
* Add generation of memstick images to the bsdinstall release makefile fornwhitehorn2011-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.
* Fix making a release. The old libdialog was renamed to libodialog.nyan2011-01-141-1/+1
|
* Reorder to have -lcrypto after -larchive. Our linker doesn't seem to likedelphij2010-05-261-2/+2
| | | | the current ordering :(
* libarchive now needs libcrypto and liblzma.delphij2010-05-251-2/+2
|
* Remove slattach from the install mfsroot since it doesn't exist anymorejhb2010-01-261-1/+0
| | | | | | to quiet a warning from crunchgen. MFC after: 1 week
* Remove libulog from the bootstrap again.ed2010-01-211-1/+1
| | | | | | libulog now only provides functions that are used by various packages from the ports tree, namely the libutempter ones. There is no reason to link it into the crunch/fixit binaries anymore.
* Don't forget to link the fixits against -lulog.ed2009-12-061-1/+1
| | | | | | reboot(8) now depends on it. Reported by: nyan
* Add libjail to the boot_crunch binaries (for ifconfig).jamie2009-06-291-1/+1
| | | | | | PR: 136071 Submitted by: Scot Hetzel Approved by: re (kensmith), bz (mentor)
* Install libusb20.so.1 as libusb.so.1, there will be a followup commit to thethompsa2009-03-091-1/+1
| | | | | | | | | ports tree so that programs use libusb from the base by default. Thanks to Stanislav Sedov for sorting out the ports build. Bump __FreeBSD_version to 800069 Help and testing by: stas
* Catch up with USB2 change.nyan2009-03-031-2/+2
| | | | | | | Remove the usbdevs and add the usbconfig. Spotted by: hrs Tested on: i386
* - Add libbsdxml and libsbuf required by bsdlabel.nyan2008-09-251-1/+1
| | | | | - Remove the mknod from pc98 fixit and also the ftp from pc98 small fixit to avoid disk full.
* Recent work on the gnu cpio seems to have introduced some bugs, itkensmith2008-08-201-4/+2
| | | | | | | | | | | | complains about "Malformed numbers" while unpacking the dists and what winds up on the disk isn't correct. Use this as an opportunity to switch over to bsdcpio since at this point we don't even build and install the gnu cpio by default. Note sysinstall needed to be tweaked a bit (dropping tape block size setting) because it seems bsdcpio doesn't do anything with block sizes, at least as far as reading from archives goes. That wasn't really a problem since installations from tape have been broken for a while and the rest of sysinstall's tape support code will be removed shortly.
* libbsdxml is now required by ifconfig(8).thompsa2008-04-221-0/+1
| | | | Submitted by: Florian Smeets
* In 'fixit mode' running "fsck /dev/ad0s1a" typically complains that itkensmith2008-01-221-0/+2
| | | | | | | | | | | | | | | | can't find fsck_4.2bsd because there was no fstab file saying what filesystem type it is looking at so it got the filesystem type from the disk's label. When that fails admins who haven't been in this situation before are most likely to try "fsck -t ufs /dev/ad0s1a" because ufs is the type used in fstab files on working systems but that also fails complaining it can't find fsck_ufs. This just sets it up so /stand in the MFS image (/sbin is a symlink to /stand) includes hard links pointing fsck_4.2bsd and fsck_ufs to fsck_ffs which is what is present in /sbin on installed systems. Prodded by: obrien MFC after: 1 day
* ed(1) no longer relies on crypto library when built for the fixit media.kensmith2007-07-021-1/+1
| | | | Approved by: re (hrs)
* The i386 "fixit" floppy began overflowing, most likely due to the newkensmith2007-06-151-4/+2
| | | | | gcc. Replace vi(1) with ed(1) as the editor to make the contents fit on a floppy again.
* Make a bootable CD on pc98.nyan2006-05-161-1/+4
|
* Revamp base system packaging of kernels to enable up/smp selectionsam2006-03-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | at runtime and to support distributing additional kernels: o remove kernel from the base tarball o add new kernel tarballs o build + package both SMP and GENERIC kernels when an <arch>/conf/SMP config file is present o add sysinstall support for multiple kernels o update sysinstall to probe for the number of cpus on a system and auto-select smp/up kernel accordingly o add a post-kernels install hook to fixup /boot/kernel o add -ldevinfo to boot crunch for sysinstall's cpu probing logic Notes: 1. On HEAD this code is not currently used because GENERIC kernels include SMP. This work is mainly intended for RELENG_6 where the GENERIC kernel is UP. If HEAD changes to match then just enable WITH_SMP in sysinstall/Makefile. 2. The cpu probing support is done with acpi and MPTable; this means some systems will require work for auto-detection to work. 3. The handling of /boot/kernel may need to be revisited; for now we rename one kernel at the last moment (SMP if installed, otherwise GENERIC). There are other, possibly better, approaches. Lots of help from ru, emaste, scottl, and jhb.
* Remove usbd(8) and all references to it. It is no longer necessaryiedowse2005-12-151-1/+0
| | | | | | since devd(8) now provides the same functionality. Submitted by: Anish Mistry
* The current version of mkisofs is warning us that the -P option willkensmith2005-01-301-1/+1
| | | | | | | | be changing with the next version, and we should be using -publisher instead. Also warned by: trhodes MFC after: 1 week
OpenPOWER on IntegriCloud