Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/etc/etc.i386/Makefile.inc

41 lines
1.5 KiB
PHP
Raw Permalink Normal View History

x86: Release the ramdisks too. This way we will get cgdroot.fs (and zfsroot.fs too) in the release. PR misc/57534
2024-03-20 16:51:35 +03:00
# $NetBSD: Makefile.inc,v 1.70 2024/03/20 13:51:35 riastradh Exp $
add 'snapshot' target, including machine-dependent targets
1994-03-05 11:06:41 +03:00
#
# etc.i386/Makefile.inc -- i386-specific etc Makefile targets
#
restore snap_md target (sigh...)
1996-10-16 06:25:08 +04:00
Add a comment reminding to update the release notes if the list of kernels change.
2007-07-24 14:28:05 +04:00
# If you change the list of distributed kernels, don't forget
# to update the release documentation in distrib/notes/common/contents
Put the kernels one per line for easier commenting out
2006-11-19 00:04:40 +03:00
KERNEL_SETS= GENERIC
Build the "MONOLITHIC" kernel configuration by default and include in the release. Using the modularise "GENERIC" kernel on an existing NetBSD 5.0 system is difficult and error-prone. The "MONOLITHIC" kernel provides an easy way to test a new kernel or to upgrade an existing system.
2009-10-01 15:51:03 +04:00
KERNEL_SETS+= MONOLITHIC
remove vga@isa and pcdisplay@isa from i386 GENERIC, and create a new LEGACY kernel that includes them instead. now radeon@pci is able to properly claim wsdisplay0 on i386 systems, and radeondrmkms has a good chance of working. this "fixes" PR#49290.
2015-03-07 10:28:37 +03:00
KERNEL_SETS+= LEGACY
Add XEN3PAE_DOM0 to the list of kernels to build for a release.
2009-03-05 23:06:13 +03:00
KERNEL_SETS+= XEN3PAE_DOM0
build XEN3PAE kernels as part of release.
2008-01-23 22:52:24 +03:00
KERNEL_SETS+= XEN3PAE_DOMU
Disable GENERIC_USERMODE kernel auto-build to avoid problems with the current autobuild-system.
2012-07-04 17:54:20 +04:00
# KERNEL_SETS+= GENERIC_USERMODE
Stop building the INSTALL_SMALL, INSTALL_TINY, INSTALL_PS2, GENERIC_TINY and GENERIC_PS2TINY kernels. These kernels are for i386 (and small i486) systems that have almost all long since met their makers. Add ALL (to help avoid bitrot).
2006-11-19 14:21:19 +03:00
# KERNEL_SETS+= GENERIC_TINY
# KERNEL_SETS+= GENERIC_PS2TINY
Change the way kernel sets are specified, and make them more consistent. To quote the comment in etc/Makefile that describes how it's done: # This target builds the kernels specified by each port. A port may # specify the following kernels: # # KERNEL_SETS The list of kernels that will be # packaged into sets, named # kern-${kernel}.tgz. These kernels # are also placed in the binary/kernels # area of the release package as # netbsd-${kernel}.gz. # # EXTRA_KERNELS Additional kernels to place in the # binary/kernels area of the release # package as netbsd-${kernel}.gz, but # which are not placed into sets. This # allows a port to provide e.g. a netbootable # installation kernel containing a ramdisk. # # BUILD_KERNELS Additional kernels to build which are # not placed into sets nor into the # binary/kernels area of the release # package. These are typically kernels # that are built for inclusion only in # installation disk/CD-ROM/tape images. #
2001-11-30 01:45:53 +03:00
Reinstate INSTALL kernel for embedded ramdisk installs. Reasons being: - INSTALL is GENERIC with an embedded ramdisk, and as such, can benefit from features included within. - INSTALL_FLOPPY has its own config(5) file, and is tailored for "small" floppy images; it misses features/drivers that could be needed to boot in a decent environment for recent x86 machines (like ACPI) - makes it closer to floppies distrib available for amd64 While here, comment out INSTALL_FLOPPY and bootfloppy-big image build. NetBSD does not use the 3.6MiB image for El Torito cdroms anymore. Remove the FLOPPYMAX limit; i386 needs 4 floppies now. Modify boot.cfg and release/contents to reflect reality. See http://mail-index.netbsd.org/port-i386/2011/02/08/msg002307.html No comments, no objections.
2011-02-10 03:43:19 +03:00
BUILD_KERNELS+= INSTALL
build XEN3PAE kernels as part of release.
2008-01-23 22:52:24 +03:00
BUILD_KERNELS+= INSTALL_XEN3PAE_DOMU
Reinstate INSTALL kernel for embedded ramdisk installs. Reasons being: - INSTALL is GENERIC with an embedded ramdisk, and as such, can benefit from features included within. - INSTALL_FLOPPY has its own config(5) file, and is tailored for "small" floppy images; it misses features/drivers that could be needed to boot in a decent environment for recent x86 machines (like ACPI) - makes it closer to floppies distrib available for amd64 While here, comment out INSTALL_FLOPPY and bootfloppy-big image build. NetBSD does not use the 3.6MiB image for El Torito cdroms anymore. Remove the FLOPPYMAX limit; i386 needs 4 floppies now. Modify boot.cfg and release/contents to reflect reality. See http://mail-index.netbsd.org/port-i386/2011/02/08/msg002307.html No comments, no objections.
2011-02-10 03:43:19 +03:00
# BUILD_KERNELS+= INSTALL_FLOPPY
Stop building the INSTALL_SMALL, INSTALL_TINY, INSTALL_PS2, GENERIC_TINY and GENERIC_PS2TINY kernels. These kernels are for i386 (and small i486) systems that have almost all long since met their makers. Add ALL (to help avoid bitrot).
2006-11-19 14:21:19 +03:00
# BUILD_KERNELS+= INSTALL_SMALL
# BUILD_KERNELS+= INSTALL_TINY
# BUILD_KERNELS+= INSTALL_PS2
Provide some more automation in the "make release" process. Also build and install: o INSTALL and INSTALL_TINY kernels (for boot floppy images) o GENERIC_TINY kernel o Boot floppy images Ideas borrowed from etc/etc.sun3/ setup.
1999-11-09 03:22:39 +03:00
Put the kernels one per line for easier commenting out
2006-11-19 00:04:40 +03:00
INSTALLATION_DIRS+= installation/misc
INSTALLATION_DIRS+= installation/cdrom
INSTALLATION_DIRS+= installation/floppy
As part of make release copy the miniroot.kmod into installation/miniroot/ and create sums for it. This means all the pieces to do network installation are easily accessible following a release build (and will also come out of the build servers). netbsd-GENERIC is in binary/kernel/ pxeboot_ia32.bin is in installation/misc/ miniroot.kmod is in installation/miniroot/
2008-05-11 16:31:45 +04:00
INSTALLATION_DIRS+= installation/miniroot
x86: Release the ramdisks too. This way we will get cgdroot.fs (and zfsroot.fs too) in the release. PR misc/57534
2024-03-20 16:51:35 +03:00
INSTALLATION_DIRS+= installation/ramdisk
Provide some more automation in the "make release" process. Also build and install: o INSTALL and INSTALL_TINY kernels (for boot floppy images) o GENERIC_TINY kernel o Boot floppy images Ideas borrowed from etc/etc.sun3/ setup.
1999-11-09 03:22:39 +03:00
- add snap_post, which makes "clean depend all release" in ../distrib/ for all platforms. - remove now unnecessary replicated code in the various snap_md_post targets - remove snap_md_pre; nothing uses it any more - use ${NETBSDSRCDIR} and ${KERNSRCDIR} as appropriate
2002-12-02 16:18:03 +03:00
# i386 specific distrib stuff
Revert last two changes. As pointed out by enami tsugutomo, snap_md_post is the wrong place to do the splits, as the tar files are not yet made!
2000-03-30 03:47:53 +04:00
snap_md_post:
- add snap_post, which makes "clean depend all release" in ../distrib/ for all platforms. - remove now unnecessary replicated code in the various snap_md_post targets - remove snap_md_pre; nothing uses it any more - use ${NETBSDSRCDIR} and ${KERNSRCDIR} as appropriate
2002-12-02 16:18:03 +03:00
cd ${KERNSRCDIR}/arch/i386/stand/dosboot && ${MAKE} release
Install pxeboot_ia32.bin as part of a "make release" on i386 and amd64.
2007-02-27 21:17:28 +03:00
cd ${KERNSRCDIR}/arch/i386/stand/pxeboot && ${MAKE} release
- add snap_post, which makes "clean depend all release" in ../distrib/ for all platforms. - remove now unnecessary replicated code in the various snap_md_post targets - remove snap_md_pre; nothing uses it any more - use ${NETBSDSRCDIR} and ${KERNSRCDIR} as appropriate
2002-12-02 16:18:03 +03:00
cd ${KERNSRCDIR}/arch/i386/stand/misc && ${MAKE} release
Convert all the etc/etc.*/Makefile.inc to use RELEASEDIR/RELEASEMACHINEDIR just like etc/Makefile does.
2008-03-18 07:20:36 +03:00
${MAKESUMS} -t ${RELEASEDIR}/${RELEASEMACHINEDIR}/installation/cdrom '*.iso'
${MAKESUMS} -t ${RELEASEDIR}/${RELEASEMACHINEDIR}/installation/floppy '*.fs'
As part of make release copy the miniroot.kmod into installation/miniroot/ and create sums for it. This means all the pieces to do network installation are easily accessible following a release build (and will also come out of the build servers). netbsd-GENERIC is in binary/kernel/ pxeboot_ia32.bin is in installation/misc/ miniroot.kmod is in installation/miniroot/
2008-05-11 16:31:45 +04:00
${MAKESUMS} -t ${RELEASEDIR}/${RELEASEMACHINEDIR}/installation/miniroot '*.*'
Convert all the etc/etc.*/Makefile.inc to use RELEASEDIR/RELEASEMACHINEDIR just like etc/Makefile does.
2008-03-18 07:20:36 +03:00
${MAKESUMS} -t ${RELEASEDIR}/${RELEASEMACHINEDIR}/installation/misc '*.*'
x86: Release the ramdisks too. This way we will get cgdroot.fs (and zfsroot.fs too) in the release. PR misc/57534
2024-03-20 16:51:35 +03:00
${MAKESUMS} -t ${RELEASEDIR}/${RELEASEMACHINEDIR}/installation/ramdisk '*.*'