mkimage-profiles/features.in/rescue/config.mk

use/rescue: use/stage2 sub/stage2@rescue use/syslinux/sdab.cfg \
	use/firmware/full +wireless
	@$(call add_feature)
	@$(call add,RESCUE_PACKAGES,interactivesystem sysvinit udev)
	@$(call add,RESCUE_PACKAGES,startup startup-rescue lilo)
	@$(call add,RESCUE_LISTS, openssh \
		$(call tags,(base || extra || server || misc) && \
			(rescue || network || security)))

# rw slice, see also use/live/rw (don't use simultaneously)
ifeq (,$(EFI_BOOTLOADER))
use/rescue/rw: use/rescue use/syslinux
	@$(call add,SYSLINUX_CFG,rescue_rw)
else
use/rescue/rw: use/rescue; @:
endif
rescue += firmware (server, wireless) There's no use of a rescue image when it has no firmware for the controller in the system being worked on... so added some. 2012-08-13 15:51:53 +04:00			`use/rescue: use/stage2 sub/stage2@rescue use/syslinux/sdab.cfg \`
rescue: extended firmware support As the firmware feature got more involved, this one has successfully dodged the change but is amended now. 2013-03-03 23:52:28 +04:00			`use/firmware/full +wireless`
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)`
rescue: tweaked pkglist and feature config Moved the packages which impeded pkglist reuse for live distros so that these stay within dedicated rescue images but don't neccessarily go into the more generic ones where things like fdisk are still quite useful. 2013-04-22 22:44:51 +04:00			`@$(call add,RESCUE_PACKAGES,interactivesystem sysvinit udev)`
			`@$(call add,RESCUE_PACKAGES,startup startup-rescue lilo)`
rescue += openssh Found myself pretty silly while sittin' at the rescue console and bein' unable to leave the cool server room for a way more comfortable armchair and a laptop's keyboard... (yes, it was that disk array needing GPT tools) 2012-08-08 20:27:59 +04:00			`@$(call add,RESCUE_LISTS, openssh \`
initial rescue+misc Things that weren't fit in the other rescue pkglists went here; more are sure to follow. 2013-03-04 01:16:00 +04:00			`$(call tags,(base \|\| extra \|\| server \|\| misc) && \`
rescue: add security related pkglists as well It's currently security+extra. 2013-03-04 01:22:10 +04:00			`(rescue \|\| network \|\| security)))`
added live_rw support There's a need for a separate boot target since persistent storage is way slower than tmpfs indeed; usbflash has a tendency for huge performance drops given simultaneous writes in addition to reads which are the bottleneck already. make-initrd-propagator 0.18 introduced ext4 rw slice, so the corresponding kernel module needs to be included into stage1; see also #28289. NB: not available on x86_64-efi (or hybrid GPT to be strict) due to fragility of the hack being made: parted(8) panics upon seeing that, and good ol' fdisk is unable to treat it. NB: use/live/rw use/rescue/rx use/syslinux/ui/gfxboot are unlikely to play very nice together due to the latter's magic l10n: "session" label is taken by live_rw config snippet and is translated in design-bootloader-source; OTOH "rescue_session" is not. 2013-03-20 00:01:43 +04:00
			`# rw slice, see also use/live/rw (don't use simultaneously)`
			`ifeq (,$(EFI_BOOTLOADER))`
			`use/rescue/rw: use/rescue use/syslinux`
			`@$(call add,SYSLINUX_CFG,rescue_rw)`
			`else`
			`use/rescue/rw: use/rescue; @:`
			`endif`