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, core79, updated. ec6b2ccbc0bdbc50d24cfa879ffd89ea9f81e0f4
Date: Mon, 23 Jun 2014 23:39:04 +0200	[thread overview]
Message-ID: <20140623213904.D730D21007@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2911 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, core79 has been updated
       via  ec6b2ccbc0bdbc50d24cfa879ffd89ea9f81e0f4 (commit)
      from  4c1e9ae0d9cff0191d5a7081d550695a9928b5f9 (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 ec6b2ccbc0bdbc50d24cfa879ffd89ea9f81e0f4
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sat Jun 21 19:04:33 2014 +0200

    syslinux: add serial console output.

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

Summary of changes:
 config/syslinux/syslinux.cfg | 53 ++++++++++++++++++++++++++++++++++++++++----
 1 file changed, 49 insertions(+), 4 deletions(-)

Difference in files:
diff --git a/config/syslinux/syslinux.cfg b/config/syslinux/syslinux.cfg
index 8832089..3c7ae87 100644
--- a/config/syslinux/syslinux.cfg
+++ b/config/syslinux/syslinux.cfg
@@ -1,3 +1,4 @@
+SERIAL 0 115200
 
 UI vesamenu.c32
 PROMPT 0
@@ -25,8 +26,7 @@ MENU TITLE Welcome!
 LABEL installer
 	MENU LABEL Install IPFire VERSION
 	TEXT HELP
-Install the version of IPFire that is
-on this disk.
+Install the version of IPFire that is on this disk.
 	ENDTEXT
 	KERNEL vmlinuz
 	INITRD instroot
@@ -80,12 +80,57 @@ Diagnose memory problems with memtest86+.
 	LABEL hdt
 		MENU LABEL Hardware Detection Tool
 		TEXT HELP
-Check your hardware with the Hardware Detection
-Tool!
+Check your hardware with the Hardware Detection Tool!
 		ENDTEXT
 		KERNEL hdt.c32
 MENU END
 
+MENU BEGIN serial
+	MENU TITLE Serial console options
+
+	LABEL serial.back
+		MENU LABEL Back
+		MENU EXIT
+
+	MENU SEPARATOR
+
+	LABEL ipfire-serial
+		MENU LABEL Install IPFire (serial)
+		TEXT HELP
+Run the installer with serial console.
+		ENDTEXT
+		KERNEL vmlinuz
+		INITRD instroot
+		APPEND console=ttyS0,115200 novga
+
+	LABEL unattended-serial
+		MENU LABEL Unattended installation (serial)
+		TEXT HELP
+Run an unattended installation wit serial console.
+		ENDTEXT
+		KERNEL vmlinuz
+		INITRD instroot
+		APPEND console=ttyS0,115200 novga unattended
+
+	MENU SEPARATOR
+
+	LABEL memtest-serial
+		MENU LABEL memtest86+ (serial)
+		TEXT HELP
+Diagnose memory problems with memtest86+ with serial console.
+		ENDTEXT
+		KERNEL memtest
+		APPEND console=ttyS0,115200
+
+	LABEL hdt-serial
+		MENU LABEL Hardware Detection Tool
+		TEXT HELP
+Check your hardware with the Hardware Detection Tool!
+		ENDTEXT
+		KERNEL hdt.c32
+
+MENU END
+
 MENU SEPARATOR
 
 LABEL netboot


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

                 reply	other threads:[~2014-06-23 21:39 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=20140623213904.D730D21007@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