keremet/mkimage-profiles
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
a860b1792e
mkimage-profiles/conf.d/server.mk

29 lines
1.1 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))
syslinux configuration revisited - incompatible change (to fix the rather broken early style): use/syslinux/ui-% is now use/syslinux/ui/%; - default timeout changed to 9 seconds (long enough and keeps the countdown in a single figure); - added totaltimeout of 300 seconds; - provided live kiosk images with almost-instant boot by default; ...and some other assorted tweaks here and there, sorry.
2012-03-30 23:41:19 +04:00
distro/.server-base: distro/.installer use/syslinux/ui/menu use/memtest
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
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
distro/server-nano: distro/.server-base \
server-nano += +power Essentially all the relevant server images got cpufreq setup and a power button handler; feel free to ask for revert if this causes any harm in any situation.
2012-07-28 14:26:27 +04:00
use/cleanup/x11-alterator use/bootloader/lilo +power
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)
kernel: introduced use/kernel/net target The various *8168 and friends among kernel modules have finally been pushed into a designated target so that RM doesn't have to care which particular additional ethernet modules are available in this particular branch and kernel. Tweak distros as appropriate. NB: *maybe* this is required by distro/.base either.
2013-02-21 13:49:32 +04:00
distro/server-mini: distro/.server-base use/server/mini use/kernel/net \
server.mk: add UEFI, move off el-smp UEFI support is pretty requisite by now; and el-smp hasn't seen updates for almost half a year by now so an actively maintained one is clearly preferred.
2013-01-02 22:03:29 +04:00
use/cleanup/x11-alterator use/efi
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
conf.d/server.mk: dropped wifi kernel modules There's no real reason to keep bcmwl and ndiswrapper around exclusively as the currently available support vastly takes over the early attempts at the task. (it's not about bare firmware though, and some day something like use/hardware/wireless should get in)
2012-04-10 22:00:30 +04:00
distro/server-ovz: distro/server-mini use/install2/net use/hdt use/rescue \
firmware: factored out cpu ucode Let's make CPU microcode an explicit target, it isn't required at every host where firmware-linux is. Adjusted its use accordingly.
2013-02-21 13:34:05 +04:00
use/firmware/server use/firmware/cpu use/power/acpi/button +wireless
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
@$(call set,STAGE1_KFLAVOUR,std-def)
@$(call set,KFLAVOURS,std-def ovz-el)
server.mk: pretty-printing kmodules Maybe it's worth moving to the kernel feature as well.
2013-02-21 13:56:00 +04:00
@$(call add,MAIN_KMODULES,ipset ipt-netflow opendpi pf_ring)
@$(call add,MAIN_KMODULES,xtables-addons) # t6/branch
introduced THE_{KMODULES,PACKAGES,LISTS,GROUPS} As too many things started duplicating between distros proper and (e.g. corresponding) LiveCDs, it became apparent that a class of entities which end up working for THE_USER (not a sysadmin, and not a developer, just a Linux user) is in need. So THE_KMODULES will power installed basesystem and live image, while THE_PACKAGES, THE_LISTS and THE_GROUPS will participate in building those.
2011-12-19 23:28:42 +04:00
@$(call add,MAIN_KMODULES,drbd83 kvm)
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
@$(call add,BASE_LISTS,ovz-server)
@$(call add,MAIN_GROUPS,dns-server http-server ftp-server kvm-server)
@$(call add,MAIN_GROUPS,ipmi mysql-server dhcp-server mail-server)
@$(call add,MAIN_GROUPS,monitoring diag-tools)
endif
Reference in New Issue Copy Permalink