Hello, for people needing to setup various production systems, multiple times for the same basic hardware but for different purposes, and mainly for people installing embedded systems, my collection of scripts/Makefiles named "deploy-tools" may be of interest. It makes use of standard FreeBSD make processes, but modified in a way that you can handle multiple rollouts in parallel, none touching the regular /usr/src /usr/obj trees. You can "menu" driven (by sbin/deploy-manager): - checkout source (svn+cvsup) and auto-apply local patches - build world/kernel - rollout installer-cd image of the customized system with auto-install-script - rollout "firmware" (RAM-root) images - flash card management for installing firmware images / packages The basic idea is to share platform config for various systems not related otherwise. And of course to manage/archive the configs/results. Therefor the configs are organized in projetcs, which basically is nothing more than a distinct directory tree. The deploy-manager can initialize such projects, taking care of all mandatory config files (provided as templates/examples). "deploy-tools" is the aggregation of several scripts/tools/Makefiles I've been using myself for several years. Only very view "make targets" are reachable by menu, but most of the not-reachable-ones are irrelevant for regular usage. Most important part is the "Embedded Systems" management. This emerged from a former project named FlashBSD. Aim was, to shrink a standard FreeBSD system to fit on a 64MB CF-Card, while still providing most of the admin's features like on regular systems (man pages etc). It makes use of standard processes as much as possible (unlike many other milli- micro- nano- projects) and ensures high robustnes for the target installation. Feedback of course is welcome. No man page available but you'll get infos/advices/descriptions during project initialization. ftp://ftp.omnilan.de/pub/FreeBSD/OmniLAN/deploy-tools-0.9.5.shar.gz Place it into usr/ports/inofficial gunzip and run the shell archive. Then you can install it like every other port. It's not feature complete yet, and may make assumptions not fitting for everybody, but if you're tired manually applying local patches, comparing/copying/merging configurations and doing over and over the same, it may be helpful. Especially if you want to setup any WRAP/NET devices! And also for VMWARE rollouts! You can have a ISO ready for auto-installtion with very view key strokes, idle brain and lots of spare time - depending on your building machine ;-) Only tested on FreeBSD 9, CD-imaging won't work on systems with makefs lacking cd9660 support! -Harry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20120906/92165e3e/signature.pgp
schrieb Harald Schmalzbauer am 06.09.2012 21:23 (localtime):> ... > > ftp://ftp.omnilan.de/pub/FreeBSD/OmniLAN/deploy-tools-0.9.5.shar.gz > Place it into usr/ports/inofficial gunzip and run the shell archive. > Then you can install it like every other port.ftp://ftp.omnilan.de/pub/FreeBSD/OmniLAN/deploy-tools-0.9.6.shar.gz Changelog: - Fixed several default-admin-account errors (wrong home, wrong shell) - Fixed wrong install-mode of reviewed passwd files - Fixed auto-restore-script (typo, perm-bits if /tmp is own fs, wrong order at size-calculation of /var) - Added minimum size check for size input in auto-restore-script - Some typos and descriptions - Added smbios/smbus/intpm to platform KERNEL_9 VMWARE template/example -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20120907/8d4ca1ec/signature.pgp
Bez?glich Harald Schmalzbauer's Nachricht vom 06.09.2012 21:23 (localtime): ?> for people needing to setup various production systems, multiple > times for the same basic hardware but for different purposes, and > mainly for people installing embedded systems, my collection of > scripts/Makefiles named "deploy-tools" may be of interest. It makes > use of standard FreeBSD make processes, but modified in a way that > you can handle multiple rollouts in parallel, none touching the > regular /usr/src /usr/obj trees. > > You can "menu" driven (by sbin/deploy-manager): - checkout source > (svn+cvsup) and auto-apply local patches - build world/kernel - > rollout installer-cd image of the customized system with > auto-install-script - rollout "firmware" (RAM-root) images - flash > card management for installing firmware images / packages > > The basic idea is to share platform config for various systems not > related otherwise. And of course to manage/archive the > configs/results. Therefor the configs are organized in projetcs, > which basically isPackage Building Menu" nothing more than a distinct > directory tree. The deploy-manager can initialize such projects, > taking care of all mandatory config files (provided as > templates/examples).? Long time no big update, but finally I added package handling on a custom-production-unit basis :-) Unfortunately, all the features are still undocumented, but the interactive deploy-manager script is self explaining in most places. Most important for package handling is "$UNIT-ports.lst", which resides in unit-config-subdir "ports" and lists all "root"-ports, the unit will have installed. In building-options-menu, you can selsect "Package Building Menu", and then "Batch building ports/packages". If you have a ports tree on the building host, it will mount that directory into it's building principle and create packages. After compilation finished, a package-resolver will check any dependent (pkg info for dependency is evaluated) package and make one if not existing. New is also the "package ISO" Option (in Rollout menu). Here you can find the port inofficial/deploy-tools: ftp://ftp.omnilan.de/pub/FreeBSD/OmniLAN/deploy-tools/ Have fun, -harry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20140707/aebb9ce9/attachment.sig>