From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 0ed9b77099321c4addd0b91121194d90322242ed
Date: Wed, 15 Aug 2018 10:12:57 +0100 [thread overview]
Message-ID: <20180815091258.009A01081BD3@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2534 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 0ed9b77099321c4addd0b91121194d90322242ed (commit)
via 647ca912a2addac9ac32d6f91ceeb00c7c184897 (commit)
from 1e1806adce3e82b500e6ed6aed6508f0c63358d5 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 0ed9b77099321c4addd0b91121194d90322242ed
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Aug 15 10:11:08 2018 +0100
aws: Install all available updates first
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit 647ca912a2addac9ac32d6f91ceeb00c7c184897
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Aug 15 10:10:13 2018 +0100
aws: Setup DNS during init phase
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/helper/aws-setup | 14 ++++++++++++++
1 file changed, 14 insertions(+)
Difference in files:
diff --git a/src/initscripts/helper/aws-setup b/src/initscripts/helper/aws-setup
index 955583c02..792a7d5a5 100644
--- a/src/initscripts/helper/aws-setup
+++ b/src/initscripts/helper/aws-setup
@@ -111,6 +111,9 @@ import_aws_configuration() {
# Download the user-data script only on the first boot
if [ ! -e "/var/ipfire/main/firstsetup_ok" ]; then
+ # Install all available updates
+ pakfire update && pakfire upgrade -y
+
# Download user-data
local user_data="$(get user-data)"
@@ -289,11 +292,22 @@ case "${reason}" in
# Add the default route
ip route add default via "${new_routers}"
+ # Setup DNS
+ for domain_name_server in ${new_domain_name_servers}; do
+ echo "nameserver ${domain_name_server}"
+ done > /etc/resolv.conf
+
+ # The system is online now
+ touch /var/ipfire/red/active
+
# Import AWS configuration
import_aws_configuration
;;
EXPIRE|FAIL|RELEASE|STOP)
+ # The system is no longer online
+ rm -f /var/ipfire/red/active
+
# Remove all IP addresses
ip addr flush dev "${interface}"
;;
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-08-15 9:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180815091258.009A01081BD3@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox