stepchenkoas/mkimage-profiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
sisyphus
mkimage-profiles/features.in/stage2/config.mk

55 lines
1.8 KiB
Makefile
Raw Permalink Normal View History

stage2 based live subprofiles, updated docs - introduced generic stage2 subprofile (non-standalone) - ported installer and rescue over to stage2/{install2,rescue} - initial stage2/live (needs more work for sure) - use make-initrd-propagator - updated and somewhat extended doc/ NB: mind #26133, #26134
2011-08-20 13:55:05 +04:00
# "1" is not a typo
stage2: use/initrd-bootchain instead use/initrd-propagator for sisyphus
2021-08-31 18:45:57 +03:00
use/stage2:: sub/stage1
introduced add_feature function The features might get copy-pasted (or even copied-and-pruned) when initialized; there's an unneccessary duplication of the function name in the line adding it to FEATURES list, thus prone to being forgotten and causing some havoc later on. It was wrong in the first place but tackling this with some double-colon rules ran into terminality issues, and further tortures were considered unneccessary. The current solution isn't perfect (no completely transparent function name registration upon corresponding target being called) but at least it is an improvement...
2011-11-16 19:58:42 +04:00
@$(call add_feature)
stage2: fix make-initrd environment on p8 This has manifested on e2k for me -- still using older make-initrd lacking R: file -- so let's get this kludge back for a while, or until any reasonable make-initrd around has *everything* it needs to create images listed in its runtime requirements. Fixes: 2b3455c29a713caf75cd9c176017b0c177ee43a0
2018-10-17 17:33:42 +03:00
@$(call add,STAGE1_PACKAGES,make-initrd file iproute2)
stage1, stage2: initial modlists support stage1's got prepare-modules target collecting modules file snippets all over stage1/modules.d/ subdirectories within individual features. stage2 now adds names of all the features going into a particular image as snippet file suffix list so that individual features don't have to register themselves twice (as a feature and as a propagator modules.d snippet carrier). This is going to allow both "uncommon" modules getting included with no problem (sin@ has wanted cifs ones for quite some time, for example, and some want e.g. infiniband modules) *and* to reduce the actual list below the common mark as well (which is the case with live-privacy image, for one). And stage1 memory consumption does matter in some cases as it's highly critical with no chance to use swap yet.
2015-02-23 23:17:12 +03:00
@$(call add,STAGE1_MODLISTS,$$(FEATURES))
stage2: fix cifs-related bits sin@ was kind enough to just stick mount.cifs into initrd regardless of its presence in the chroot in question; let's look first and only add what's found. This started as a stopgap fix after make-initrd 2.2.0 which happened to collide with cifs-related m-p commits in a somewhat unfortunate manner...
2018-09-19 10:16:46 +03:00
@$(call xport,STAGE1_PACKAGES)
stage2, efi: added kernel config test collector The newly-introduced STAGE1_KCONFIG variable serves to keep those kernel configuration options that are required to be present in the kernel to boot.
2014-05-07 15:00:07 +04:00
@$(call xport,STAGE1_KCONFIG)
stage2 based live subprofiles, updated docs - introduced generic stage2 subprofile (non-standalone) - ported installer and rescue over to stage2/{install2,rescue} - initial stage2/live (needs more work for sure) - use make-initrd-propagator - updated and somewhat extended doc/ NB: mind #26133, #26134
2011-08-20 13:55:05 +04:00
stage2: enable bootchain for p11, c11* branches
2024-02-26 12:49:32 +03:00
ifeq (,$(filter-out sisyphus p11 c11%,$(BRANCH)))
stage2: use/initrd-bootchain instead use/initrd-propagator for sisyphus
2021-08-31 18:45:57 +03:00
use/stage2:: use/initrd-bootchain; @:
else
use/stage2:: use/initrd-propagator; @:
endif
stage2: make use of finer-grained module lists This is sort of laying the ground for the future dismantling of 10-stage2 (which was sub.in/stage1/modules just recently); things look like tagged lists might become due some day, e.g. "net+usb" or "scsi+raid" -- time will tell.
2015-04-14 19:58:01 +03:00
# building blocks for propagator's module cove
use/stage2/ata use/stage2/drm use/stage2/fs use/stage2/hid use/stage2/md \
use/stage2/mmc use/stage2/net use/stage2/net-cifs use/stage2/net-nfs \
use/stage2/pcmcia use/stage2/rtc use/stage2/scsi use/stage2/usb \
stage2: Not added nvidia kernel modules into propagator
2020-11-18 10:09:42 +03:00
use/stage2/virtio: \
stage2: make use of finer-grained module lists This is sort of laying the ground for the future dismantling of 10-stage2 (which was sub.in/stage1/modules just recently); things look like tagged lists might become due some day, e.g. "net+usb" or "scsi+raid" -- time will tell.
2015-04-14 19:58:01 +03:00
use/stage2/%: use/stage2
@$(call add,STAGE1_MODLISTS,stage2-$*)
stage2: Added use/stage2/sbc This list kernel modules for loading on single board computers.
2020-02-06 17:59:59 +03:00
use/stage2/sbc: use/stage2
ifeq (,$(filter-out aarch64,$(ARCH)))
@$(call add,STAGE1_MODLISTS,stage2-sbc-aarch64)
endif
@:
drm, plymouth, stage2, x11: initial feature drm The drm feature solves the problem of creating a common entry point for adding kernel drm modules for different package lists. The need for allocation into a separate feature arose from one parties to the need to make a switch between free and proprietary NVIDIA driver, on the other, because of the need to add only drm modules kernels for purposes such as use/stage2/kms and use/plymouth. Also no more switch needed for RADEON, as only the free video driver remains.
2020-09-08 12:04:55 +03:00
use/stage2/kms: use/stage2/drm use/drm/stage2/full; @:
stage2: fix use/stage2/kms/nvidia All drm modules are added to the first and second stages, except for nouveau and nvidia. Nouveau is added to stage2. nvidia needs to be added to live and the base system separately. This is an auxiliary target. See also https://bugzilla.altlinux.org/31971
2023-04-10 18:04:15 +03:00
# initrd without nouveau; see ALT bug 31971
use/stage2/kms/nvidia: use/stage2/drm use/drm/stage2/nvidia; @:
added plymouth feature An initial draft of it was done half a year ago but several tricky thingies had kept the code from showing up as it was rather brittle and incomplete. This implementation involves quite a few changes all over the place but finally works good enough for live and installer images. Please pay attention to the versions of these packages: - installer-feature-setup-plymouth (0.3.2-alt1+) - branding-altlinux-sisyphus (20110706-alt2+ if used) - plymouth (0.8.3-alt20.git20110406+) See also: - http://www.altlinux.org/Branding - http://www.altlinux.org/Plymouth
2012-06-13 23:07:10 +04:00
stage1: add CIFS installation method
2014-01-11 20:48:49 +04:00
# install mount.cifs to stage1
stage2: mv use/stage2/cifs{-install,} This has no users in master but out-of-tree branches might need a trivial update. The rationale is that it's actually for *any* stage2 and not related to specifically "install" at all (otherwise it should have been moved to install2 feature altogether). Note that there's no reason to add nfs-utils similarly as make-initrd requires kinit-utils which includes its own nfsmount.
2015-11-16 15:24:49 +03:00
# NB: there's builtin nfsmount there, no reason for nfs-utils
use/stage2/cifs: use/stage2/net-cifs
stage1: add CIFS installation method
2014-01-11 20:48:49 +04:00
@$(call add,STAGE1_PACKAGES,cifs-utils)
stage2: add use/stage2/net-install Adds grub "Network installation" submenu and kernel modules to initrd needed for network booting.
2021-09-02 22:12:57 +03:00
# grub submenu 'Network installation'
use/stage2/net-install: use/stage2/net use/stage2/cifs \
use/stage2/net-nfs use/grub/netinstall.cfg; @:
stage2: add use/stage2/net-install-live Designed to be added to an image with use/live-install/pkg + use/live/rescue. Also see commit 41a881f61ceeaef1d4405505541cce559087343c
2024-02-09 15:29:24 +03:00
# grub submenu 'Network installation' with stagename live only
use/stage2/net-install-live: use/stage2/net use/stage2/cifs \
use/stage2/net-nfs use/grub/netinstall-live.cfg; @:
live, stage2: net-eth moved It would be better to put it into stage2 in the first place but this somehow went over my head; rescue made a reminder.
2013-03-04 00:37:27 +04:00
# eth0 instead of enp0s3
use/stage2/net-eth: use/stage2
@$(call add,STAGE1_PACKAGES,udev-rule-generator-net)
@$(call add,STAGE2_PACKAGES,udev-rule-generator-net livecd-net-eth)
stage2 based live subprofiles, updated docs - introduced generic stage2 subprofile (non-standalone) - ported installer and rescue over to stage2/{install2,rescue} - initial stage2/live (needs more work for sure) - use make-initrd-propagator - updated and somewhat extended doc/ NB: mind #26133, #26134
2011-08-20 13:55:05 +04:00
# NB: sub/stage2 isn't used standalone but rather
# as a base for various livecd modifications
# (currently install2, live, rescue)
Reference in New Issue Copy Permalink