stepchenkoas/mkimage-profiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
59dc98c3d8
mkimage-profiles/conf.d/server.mk

32 lines
1.0 KiB
Makefile
Raw Normal View History

introduced conf.d/ for distro, ve config snippets This was asked for by Leo-sp50 and torabora, and seems quite reasonable: let's provide means to keep at least some distribution configurations a bit apart, so that these can be considered more standalone in terms of hard warranted functionality but at the same time enjoying the common infrastructure. Considering lib/distro.mk: it's now experimentally pulled apart so that parallel development of different distro families can go on without major merge hassles. *Please* don't abuse with massive copy-paste. And before you ask: this might get extended to allow for "private" out-of-tree configurations being included since apparently there are goals with no meaning outside of some very particular context... but otherwise I'd like to encourage getting reusable bits in-tree.
2011-10-31 14:40:02 +04:00
# server distributions
ifeq (distro,$(IMAGE_CLASS))
server.mk: minor refactoring There was no real reason to use/cleanup/x11-alterator downstream every time instead of promoting it upstream to the common point.
2013-05-24 14:42:48 +04:00
distro/.server-base: distro/.installer use/syslinux/ui/menu use/memtest \
use/cleanup/x11-alterator
factor out openssh packages There's no need to repeat the typical openssh-* triade all over the place; those who need server and client are better off pulling in "openssh" pkglist, and those needing a particular package should specify it.
2012-06-25 16:32:13 +04:00
@$(call add,BASE_LISTS,server-base openssh)
introduced conf.d/ for distro, ve config snippets This was asked for by Leo-sp50 and torabora, and seems quite reasonable: let's provide means to keep at least some distribution configurations a bit apart, so that these can be considered more standalone in terms of hard warranted functionality but at the same time enjoying the common infrastructure. Considering lib/distro.mk: it's now experimentally pulled apart so that parallel development of different distro families can go on without major merge hassles. *Please* don't abuse with massive copy-paste. And before you ask: this might get extended to allow for "private" out-of-tree configurations being included since apparently there are goals with no meaning outside of some very particular context... but otherwise I'd like to encourage getting reusable bits in-tree.
2011-10-31 14:40:02 +04:00
regular.mk, server.mk: do not use deprecated lilo
2023-08-14 15:24:27 +03:00
distro/server-nano: distro/.server-base +power \
install2: remove target use/install2/cleanup/crypto 1. alterator-browser-qt5 does not start now without libgnutls 2. Successful remount with luks requires cryptsetup 3. There is no conflict with the luks feature for a long time
2023-07-04 10:08:24 +03:00
use/install2/cleanup/vnc
conf.d/server.mk += server-nano A very basic server image with sshd onboard for testing and very basic installs; thanks legion@ for the query.
2012-04-01 21:50:38 +04:00
@$(call add,BASE_LISTS,$(call tags,server network))
@$(call add,BASE_PACKAGES,dhcpcd cpio)
Drop net-eth support
2021-04-12 19:05:25 +03:00
distro/server-mini: distro/.server-base \
server.mk: amend net-eth usage either +net-eth covers both stage2 and base installation parts while use/stage2/net-eth would result in an inobvious catch when udev-rule-generator-net would hit install2 but not the installed system, and interface bindings would be carried over from installer to the installation but would *not* be updated in case of changed network card(s) configuration.
2014-08-26 22:44:11 +04:00
use/server/mini use/kernel/net use/efi use/power/acpi/button
server: generalize server-ovz configuration bits OpenVZ related part is now a reusable use/server/ovz target, and service related groups which have been largely taken from rider@'s server-light project are now use/server/groups/base.
2014-02-26 15:37:05 +04:00
@$(call set,INSTALLER,altlinux-server)
server.mk: added mdadm, lvm support to server-mini Pretty natural but delayed somehow...
2012-12-06 05:12:51 +04:00
@$(call add,BASE_PACKAGES,make-initrd-mdadm make-initrd-lvm)
introduced conf.d/ for distro, ve config snippets This was asked for by Leo-sp50 and torabora, and seems quite reasonable: let's provide means to keep at least some distribution configurations a bit apart, so that these can be considered more standalone in terms of hard warranted functionality but at the same time enjoying the common infrastructure. Considering lib/distro.mk: it's now experimentally pulled apart so that parallel development of different distro families can go on without major merge hassles. *Please* don't abuse with massive copy-paste. And before you ask: this might get extended to allow for "private" out-of-tree configurations being included since apparently there are goals with no meaning outside of some very particular context... but otherwise I'd like to encourage getting reusable bits in-tree.
2011-10-31 14:40:02 +04:00
add distro/server-mini-systemd-networkd
2015-12-01 14:38:48 +03:00
distro/server-mini-systemd-networkd: distro/.server-base \
use/net/networkd +systemd \
use/server/mini use/efi use/firmware
@$(call set,INSTALLER,altlinux-server)
regular.mk, server, server.mk: mark openvz available for x86_64 only
2022-07-18 17:56:36 +03:00
ifneq (,$(filter-out x86_64 aarch64,$(ARCH)))
server: generalize server-ovz configuration bits OpenVZ related part is now a reusable use/server/ovz target, and service related groups which have been largely taken from rider@'s server-light project are now use/server/groups/base.
2014-02-26 15:37:05 +04:00
distro/server-ovz: distro/server-mini use/server/ovz use/server/groups/base \
server.mk: shift use/power/acpi/button to server-mini It used to be added in server-ovz but it really belongs to the underlying server-mini already as more images built upon that one should perform correct shutdown given ATX compatible case/mobo or a VM that can do ACPI.
2014-04-14 14:49:14 +04:00
use/install2/net use/hdt use/rescue \
server: generalize server-ovz configuration bits OpenVZ related part is now a reusable use/server/ovz target, and service related groups which have been largely taken from rider@'s server-light project are now use/server/groups/base.
2014-02-26 15:37:05 +04:00
use/firmware/server use/firmware/cpu +wireless; @:
regular.mk, server, server.mk: mark openvz available for x86_64 only
2022-07-18 17:56:36 +03:00
endif
introduced conf.d/ for distro, ve config snippets This was asked for by Leo-sp50 and torabora, and seems quite reasonable: let's provide means to keep at least some distribution configurations a bit apart, so that these can be considered more standalone in terms of hard warranted functionality but at the same time enjoying the common infrastructure. Considering lib/distro.mk: it's now experimentally pulled apart so that parallel development of different distro families can go on without major merge hassles. *Please* don't abuse with massive copy-paste. And before you ask: this might get extended to allow for "private" out-of-tree configurations being included since apparently there are goals with no meaning outside of some very particular context... but otherwise I'd like to encourage getting reusable bits in-tree.
2011-10-31 14:40:02 +04:00
server.mk, test.mk: added zabbix images server-zabbix.iso is ready for deployment, and live-zabbix.iso is zabbix agent + firefox (needs at least Server to be specified properly within zabbix_agentd.conf when booted).
2014-04-14 16:02:20 +04:00
distro/server-zabbix: distro/server-mini use/server/zabbix; @:
introduced conf.d/ for distro, ve config snippets This was asked for by Leo-sp50 and torabora, and seems quite reasonable: let's provide means to keep at least some distribution configurations a bit apart, so that these can be considered more standalone in terms of hard warranted functionality but at the same time enjoying the common infrastructure. Considering lib/distro.mk: it's now experimentally pulled apart so that parallel development of different distro families can go on without major merge hassles. *Please* don't abuse with massive copy-paste. And before you ask: this might get extended to allow for "private" out-of-tree configurations being included since apparently there are goals with no meaning outside of some very particular context... but otherwise I'd like to encourage getting reusable bits in-tree.
2011-10-31 14:40:02 +04:00
endif
Reference in New Issue Copy Permalink