public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core77, updated. a4da0b6e311ba28bcbc4f276c4030b6425fc4c4b
Date: Sun, 18 May 2014 20:22:08 +0200	[thread overview]
Message-ID: <20140518182208.3387621488@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3107 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, core77 has been updated
       via  a4da0b6e311ba28bcbc4f276c4030b6425fc4c4b (commit)
      from  a257ce6b8dab0186455692f847c4dc6517198062 (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 a4da0b6e311ba28bcbc4f276c4030b6425fc4c4b
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sun May 18 14:39:16 2014 +0200

    core77: drop xen kernel support.
    
    The legacy xen kernel is incompatible to grsecurity and new udev so we are forced to drop the support. We have anounced this step 8 month ago.
    http://planet.ipfire.org/post/dropping-support-for-xen-3-x-deprecation-warning

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/core/77/update.sh | 26 +++-----------------------
 1 file changed, 3 insertions(+), 23 deletions(-)

Difference in files:
diff --git a/config/rootfiles/core/77/update.sh b/config/rootfiles/core/77/update.sh
index e9cf770..9a4f781 100644
--- a/config/rootfiles/core/77/update.sh
+++ b/config/rootfiles/core/77/update.sh
@@ -44,20 +44,12 @@ done
 #
 # Do some sanity checks.
 case $(uname -r) in
-	*-ipfire-versatile )
+	*-ipfire-xen )
 		/usr/bin/logger -p syslog.emerg -t ipfire \
-			"core-update-${core}: ERROR cannot update. versatile support is dropped."
-		# Report no error to pakfire. So it does not try to install it again.
+			"core-update-${core}: ERROR cannot update. legacy-xen support was dropped."
+			echo "IPFire 2.13 (i586) - core 76 - xen-legacy (EOL) No support!" > /etc/system-release
 		exit 0
 		;;
-	*-ipfire-xen )
-		BOOTSIZE=`df /boot -Pk | sed "s| * | |g" | cut -d" " -f2 | tail -n 1`
-		if [ $BOOTSIZE -lt 28000 ]; then
-			/usr/bin/logger -p syslog.emerg -t ipfire \
-				"core-update-${core}: ERROR cannot update because not enough space on boot."
-			exit 2
-		fi
-		;;
 	*-ipfire* )
 		# Ok.
 		;;
@@ -475,18 +467,6 @@ if [ ! "$(grep "^flags.* pae " /proc/cpuinfo)" == "" ]; then
 	fi
 fi
 
-# Force reinstall xen kernel if it was installed
-if [ -e "/opt/pakfire/db/installed/meta-linux-xen" ]; then
-	echo "Name: linux-xen" > /opt/pakfire/db/installed/meta-linux-xen
-	echo "ProgVersion: 0" >> /opt/pakfire/db/installed/meta-linux-xen
-	echo "Release: 0"     >> /opt/pakfire/db/installed/meta-linux-xen
-	echo "Name: linux-xen" > /opt/pakfire/db/meta/meta-linux-xen
-	echo "ProgVersion: 0" >> /opt/pakfire/db/meta/meta-linux-xen
-	echo "Release: 0"     >> /opt/pakfire/db/meta/meta-linux-xen
-	# Add xvc0 to /etc/securetty
-	echo "xvc0" >> /etc/securetty
-fi
-
 #
 # After pakfire has ended run it again and update the lists and do upgrade
 #


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2014-05-18 18:22 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=20140518182208.3387621488@argus.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