summaryrefslogtreecommitdiffstats
path: root/release/amd64
Commit message (Collapse)AuthorAgeFilesLines
* MFC r273093, r273096:gjb2014-10-162-8/+190
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r273093: Merge the following from ^/projects/release-vmimage: 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). r273096: Merge the following from ^/projects/release-vmimage: 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. Relnotes: yes Sponsored by: The FreeBSD Foundation
* MFC r272414:gjb2014-10-141-0/+188
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Merge the following revisions from ^/projects/release-vmimage: 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. Sponsored by: The FreeBSD Foundation
* Revert r272724:gjb2014-10-081-188/+0
| | | | | | | | | | | Features not yet available in stable/10 are needed in mkimg(1), and it is more dangerous to tweak these changes in stable/10 directly without explicitly testing certain failure cases. Re-addition of this change is imminent. Sponsored by: The FreeBSD Foundation
* MFC r272414:gjb2014-10-081-0/+188
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Merge the following revisions from ^/projects/release-vmimage: 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. Sponsored by: The FreeBSD Foundation
* MFC r264995 (nwhitehorn):emaste2014-09-121-0/+60
| | | | | | | | | | | | | | | | | | | Add script to setup bootable CD ISOs for both BIOS and EFI systems. Tested and working on QEMU. Actually using this script as the regular image generator, like with the memstick one, will require that the kernel support EFI too. In particular, the following two things are required: 1. vt(9) be the default console driver 2. vt_efifb and vt_vga be able to coexist usefully in the same kernel One other note here is that this requires newfs_msdos and mdconfig, which is really ugly. NetBSD's makefs at least seems to support FAT now. If that actually works, it should be imported and we can get rid of the mdconfig mess. Approved by: re Relnotes: Yes Sponsored by: The FreeBSD Foundation
* MFC UEFI memstick build scriptemaste2014-09-091-0/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r264935 (gjb): Add a separate script to build the memstick.img and the mini-memstick.img with UEFI support. As the comments in the file suggest, 1) there must be existing ${.OBJDIR}/usr/src/release/{release,bootonly}; 2) TARGET/TARGET_ARCH must be amd64; and 3) it must be a vt(4)-enabled kernel with vt_efifb (*not* vt_vga). This script is not hooked into release/Makefile in any way until further testing is complete. r264992 (nwhitehorn): Make a dual-boot BIOS/UEFI memstick image. Testing required before this gets renamed make-memstick.sh. r265017 (nwhitehorn): loader's GPT support on BIOS does not seem to like the root filesystem being the last filesystem on the disk for some reason when made by this script. Add a vestigial swap partition to allow this to boot with QEMU BIOS. Approved by: re Sponsored by: The FreeBSD Foundation
* MFC r264933:gjb2014-05-041-11/+11
| | | | | | Fix indentation in make-memstick.sh. Sponsored by: The FreeBSD Foundation
* MFC r260772:gjb2014-01-161-36/+0
| | | | | | | | | | | | | | | | | | Update the pkg-stage target to be more compatible with pkg-1.2: - 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 Sponsored by: The FreeBSD Foundation
* MFC r258305, r258307, r258308, r258309, r258310, r258314, r258317,gjb2013-11-211-0/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r258319, r258320: r258305: Use the IMAGES variable to determine which image files to remove as part of 'make -C /usr/src/release clean'. r258307: Add a script and configuration files to fetch pre-built packages from pkg.FreeBSD.org for inclusion on release medium (dvd1.iso). r258308: Unconditionally copy the build host /etc/resolv.conf into the chroot directory, since hostname resolution may be needed in the case of building a dvd image (with packages) and also setting 'NOPORTS=1'. r258309: Set the PKG_CACHEDIR directory to 'dvd/' instead of 'release/' in preparation of adding a 'dvd1.iso' target. r258310: Add the 'dvd1.iso' target. This mimics the 'release.iso' target, with the additional step of fetching packages for inclusion on the dvd image. The 'pkg-stage' target is used to run 'scripts/pkg-stage.sh' if the '${TARGET}/pkg-stage.conf' configuration file exists (currently only amd64 and i386). Allow dvd1.iso to be skipped if NODVD=1. r258314: Fix how ABI is evaluated so it matches more than a dot-zero case. r258317: Document the 'dvdrom' target. r258319: Remove WITHOUT_PROFILE=1 for the dvd1.iso medium. r258320: Simplify PKG_ABI for pkg-stage.sh. Approved by: re (hrs) 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-031-44/+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-18/+3
| | | | | | | | 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
* 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
* 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
* 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
* Keep each prog on its own line so that diffs between variousru2004-10-011-7/+23
| | | | *_crunch.conf files are easier to read.
* Take away unused libraries.ru2004-10-011-1/+1
|
* Add a publisher variable with the URL for the FreeBSD Project, and putmurray2004-07-151-1/+2
| | | | | | this into the ISO headers by specifying the -P option to mkisofs. Obtained from: share/examples/worm/makecdfs.sh
* Set BATCH=yes to avoid bumping into interactivity in the port builds.kris2004-07-121-1/+1
| | | | XXX /usr/ports is still hardcoded, should be ${PORTSDIR}
* mkisofs(8) is now installed by sysutils/cdrtools.marius2004-06-021-4/+4
| | | | This will be instantly MFC'ed.
* Clean up after revision 1.55.ru2004-01-281-1/+1
|
* amd64 will not provide floppies.ru2003-07-232-77/+0
|
* For amd64, delete the IA32 option for the boot kernel since it needspeter2003-06-261-0/+1
| | | | SYSV*, which is also removed.
* Enable the MUTEX_NOINLINE option for the BOOTMFS kernel for ia32, pc98, andscottl2003-05-181-0/+2
| | | | | | alpha. This shaves 36-50k off of the compressed kernel size. Submitted by: jhb
* disklabel(8) is spelled bsdlabel(8) or sunlabel(8) these days.ru2003-05-171-2/+3
| | | | | | | | Also make sure bsdlabel(8) (along with the disklabel(8) compat link) still appear on the fixit floppies of platforms that use it natively (alpha, i386, and pc98). Approved by: re (scottl)
* Revert rev 1.78 of dokern.sh. The ncv, stg, and nsp drivers aren'tscottl2003-05-051-3/+0
| | | | | specific to pc98, and it looks like space on the kernel floppy isn't as tight as it was.
* pc98 has it's own release subdir, so it's safe to remove the stg, ncv, andscottl2003-05-021-0/+3
| | | | | | nsp drivers from the i386 floppies. Suggested by: bmah
* Removed mount_devfs from progs since there is no "mount_devfs"ru2003-04-211-1/+1
| | | | | source directory (it's spelled mount_std nowadays), so it was a no-op anyway, and DEVFS is now the default.
* NO_COMPAT_FREEBSD4 is no more.jhay2003-04-171-1/+0
|
* Go for the auto-tuned `maxusers'. This at least fixesru2003-03-221-4/+0
| | | | | | the ``panic: timeout table full'' on Alphas. Tested by: wilko
* Push UFS_ACL back for i386. We have 11kbytes of free space on kern.flp.matusita2003-02-211-1/+0
| | | | | | | | | | | | If we have no UFS_ACL kernel, users who already uses UFS1/2 attributes get confused since no access control is performed for an update install. Still, pc98 and alpha doesn't have UFS_ACL since I don't know about them. Nyan-san, if kern.flp on tatsu has enough spaces (4k or more spaces), please back UFS_ACL for pc98 also. Data collected from: 5.0-CURRENT-20030221-JPSNAP on snapshots.jp.FreeBSD.org
* Pushing back aacp driver to kern.flp kernel. It can be removed iffmatusita2003-02-191-1/+0
| | | | | | | | aac is not compiled into a kernel. After this change, kgziped kernel got about 320 bytes; it still fits a floppy. Pointy hat to: matusita
* Yet another kernel diet: remove aacp and _KPOSIX_PRIORITY_SCHEDULING.matusita2003-02-181-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | aacp is a passthrough driver for aac, but it seems that aac kernel module has a feature provided by aacp; so it can be removed safely. _KPOSIX_PRIORITY_SCHEDULING provides P1003.1B realtime extension. However, in an installation phase, it seems that it helps a little for us, so we can remove this option from a kernel for floppy installation. I know _KPOSIX_PRIORITY_SCHEDULING option is defined in other architecture. However, I don't touch them at this time; I can't test it. Anyway here's result. Before diet: -rwxr-xr-x 1 matusita matusita 4849883 Feb 18 11:22 kernel -rwxr-xr-x 1 matusita matusita 1727143 Feb 18 11:47 kernel.kgz After diet: -rwxr-xr-x 1 matusita matusita 4840949 Feb 18 09:48 kernel -rwxr-xr-x 1 matusita matusita 1723911 Feb 18 11:47 kernel.kgz We've got extra 3232 bytes (using 5-current as of Feb/18/2003). In cooperation with: jwd (test ISO installation image) Boot tested on: several PCs around myself Installation tested on: VMware Workstation e.x.p build-4099
* tunefs now requires -lufs.ru2003-01-231-1/+1
|
OpenPOWER on IntegriCloud