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

37 lines
1.4 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))
initial repo feature We've got some parts of it in build-distro feature, and some went to dev feature for no real reason. But a bare installer might go without package base, and LiveCDs other than live-builder might find local repository useful given aufs2 root overlay. Now the overall scheme is more straightforward: - a distro: + asks that a package repo be included + cares to further add the packages to it - a repo feature: + pulls in sub/main for it to happen + provides genbasedir script to create repo metadata + supplements live feature with repo configuration
2011-11-14 18:24:07 +04:00
distro/server-base: distro/installer use/repo/main \
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
use/syslinux/ui-menu use/memtest use/bootloader/grub
@$(call add,BASE_LISTS,server-base)
distro/server-mini: distro/server-base use/cleanup/x11-alterator
@$(call set,KFLAVOURS,el-smp)
@$(call add,KMODULES,e1000e igb)
@$(call add,BASE_LISTS,\
$(call tags,base && (server || network || security || pkg)))
@$(call add,BASE_LISTS,$(call tags,extra network))
initial systemd feature Thanks shaba@ for both the package and a wiki page, and dek@ for the inspiration to finally get to it.
2011-11-12 17:08:31 +04:00
distro/server-systemd: distro/server-mini use/systemd
server-ovz: rebase onto server-mini The culprit was missing dhcpcd, although the rest of niceties already in server-mini were welcome to server-ovz either.
2011-11-16 16:27:39 +04:00
distro/server-ovz: distro/server-mini \
use/hdt use/rescue use/firmware/server use/power/acpi/button
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-ovz: rebase onto server-mini The culprit was missing dhcpcd, although the rest of niceties already in server-mini were welcome to server-ovz either.
2011-11-16 16:27:39 +04:00
@$(call add,KMODULES,bcmwl ndiswrapper rtl8168 rtl8192)
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,KMODULES,ipset ipt-netflow opendpi pf_ring xtables-addons)
@$(call add,KMODULES,drbd83 kvm)
experimental server-ovz-netinst image It's now possible to: - make distro/server-ovz.iso; - make distro/server-ovz-netinst.iso; - publish the former image's contents on ftp.linux.kiev.ua; - boot the latter (~17M) image and enjoy the netinstall ;-) The catch is that the stage2 (altinst file) location has to be hardwired into syslinux config snippet for things to happen automatically -- even if it can be specified manually in case of failure. The other catch is that currently a netinstall image is somewhat tied to the particular image it installs since stage1 kernel and stage2 modules must correspond strictly (the typical symptoms of the glitch would be missing mouse driver and weird "permission denied" errors during an attempt to partition the hard drives). It might be desirable to provide multi-distro netinstall image...
2011-11-20 00:05:11 +04:00
@$(call add,INSTALL2_PACKAGES,curl) ### should become curl-mini
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_LISTS,kernel-wifi)
@$(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)
experimental server-ovz-netinst image It's now possible to: - make distro/server-ovz.iso; - make distro/server-ovz-netinst.iso; - publish the former image's contents on ftp.linux.kiev.ua; - boot the latter (~17M) image and enjoy the netinstall ;-) The catch is that the stage2 (altinst file) location has to be hardwired into syslinux config snippet for things to happen automatically -- even if it can be specified manually in case of failure. The other catch is that currently a netinstall image is somewhat tied to the particular image it installs since stage1 kernel and stage2 modules must correspond strictly (the typical symptoms of the glitch would be missing mouse driver and weird "permission denied" errors during an attempt to partition the hard drives). It might be desirable to provide multi-distro netinstall image...
2011-11-20 00:05:11 +04:00
# tiny network-only server-ovz installer (stage2 comes over net too)
distro/server-ovz-netinst: distro/.base sub/stage1 use/stage2 \
lib/distro.mk: don't do localboot by default distro/.base target used to pull in localboot syslinux config snippet which might be too early for some of the further distros; it's a quite fragile equilibrium which was shifted a bit by imz@ (see #26606). Feel free to reopen the discussion though, things might be tweaked so that localboot might be desirable on almost every image even if with lower priority...
2011-11-24 15:17:02 +04:00
use/syslinux/ui-menu use/syslinux/localboot.cfg use/memtest
experimental server-ovz-netinst image It's now possible to: - make distro/server-ovz.iso; - make distro/server-ovz-netinst.iso; - publish the former image's contents on ftp.linux.kiev.ua; - boot the latter (~17M) image and enjoy the netinstall ;-) The catch is that the stage2 (altinst file) location has to be hardwired into syslinux config snippet for things to happen automatically -- even if it can be specified manually in case of failure. The other catch is that currently a netinstall image is somewhat tied to the particular image it installs since stage1 kernel and stage2 modules must correspond strictly (the typical symptoms of the glitch would be missing mouse driver and weird "permission denied" errors during an attempt to partition the hard drives). It might be desirable to provide multi-distro netinstall image...
2011-11-20 00:05:11 +04:00
@$(call add,SYSLINUX_CFG,netinstall2)
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