On 12/02/13 11:05, Hiroki Sato wrote: > So, if I understand it correctly, the ec2-scripts add > $firstboot_pkgs_enable and $firstboot_pkgs_list into /etc/rc.conf and then > send a signal to /etc/rc, and then the firstboot-pkg script runs.
s/and then/and at some point later/ The firstboot-pkgs script running isn't trigerred by the signal; it's just another rc.d script. And there's other things which could be configured by launch-time user-data, e.g., firstboot_freebsd_update_enable="NO" if someone didn't want their EC2 image to freebsd-update itself. > In this case, I think creating /etc/rc.conf.d/firstboot-pkg in ec2-scripts > is simpler. Sourcing /etc/rc.conf happens only once, but sourcing > /etc/rc.conf.d/<name> happens every time when "load_rc_config <name>" is > called. If firstboot-pkgs calls load_rc_config, it should work as expected > without sending a signal. That's a workaround, but I think it's less than ideal from a usability perspective -- FreeBSD users expect to edit /etc/rc.conf, and vanishingly few people even know that /etc/rc.conf.d/ exists. The idea here is to provide a general mechanism for creating and adding to configuration files with data provided at VM launch time, and trying to explain to people that editing /etc/rc.conf won't do what they expect seems like it would be difficult. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-rc To unsubscribe, send any mail to "[email protected]"
