From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/livecd-tools:master commit in: /
Date: Sun, 1 May 2011 02:49:11 +0000 (UTC) [thread overview]
Message-ID: <3ca14c1c816e098e0ce8719ab962a01d51e8462a.williamH@gentoo> (raw)
commit: 3ca14c1c816e098e0ce8719ab962a01d51e8462a
Author: William Hubbs <williamh <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 13 19:22:31 2011 +0000
Commit: William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Sun May 1 02:46:14 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/livecd-tools.git;a=commit;h=3ca14c1c
start xdm from autoconfig
We need to start xdm ourselves instead of allowing it to start in the
default order. This allows us to not start it when X is not requested by
the user or when speakup or brltty is requested.
---
autoconfig | 6 +-----
1 files changed, 1 insertions(+), 5 deletions(-)
diff --git a/autoconfig b/autoconfig
index 3d3c71f..9eec5ce 100755
--- a/autoconfig
+++ b/autoconfig
@@ -278,6 +278,7 @@ list_services() {
svcs="${svcs} $(check_svc ${PASSWD} pwgen)"
svcs="${svcs} $(check_svc ${PCMCIA} pcmcia)"
svcs="${svcs} $(check_svc ${SSHD} sshd)"
+ svcs="${svcs} $(check_svc ${X11} xdm)"
### TODO: make this baselayout-2 compatible
### TODO: make these checks accurate using service dependencies
@@ -602,11 +603,6 @@ start() {
[ -n "${XDESC}" ] && einfo "VideoCard: ${HILITE}${XDESC}${NORMAL}"
- if ! yesno "${X11}"
- then
- touch /etc/.noxdm
- fi
-
killall hwsetup 2>/dev/null
echo "6" > /proc/sys/kernel/printk
}
next reply other threads:[~2011-05-01 2:51 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 2:49 William Hubbs [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-26 17:07 [gentoo-commits] proj/livecd-tools:master commit in: / Rick Farina
2017-03-07 15:35 Brian Evans
2017-02-25 0:54 Robin H. Johnson
2017-01-10 21:54 Brian Evans
2015-10-18 2:26 William Hubbs
2015-10-18 1:45 Jorge Manuel B. S. Vicetto
2015-02-22 22:35 William Hubbs
2015-01-14 18:33 William Hubbs
2015-01-14 2:55 Jorge Manuel B. S. Vicetto
2013-07-07 22:48 William Hubbs
2013-07-07 22:28 William Hubbs
2013-07-06 23:53 William Hubbs
2013-02-25 18:20 William Hubbs
2013-02-25 17:48 William Hubbs
2013-02-25 17:48 William Hubbs
2011-06-30 20:31 William Hubbs
2011-06-28 19:56 William Hubbs
2011-06-28 17:32 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-05-01 2:49 William Hubbs
2011-02-17 5:38 William Hubbs
2011-02-10 21:30 William Hubbs
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=3ca14c1c816e098e0ce8719ab962a01d51e8462a.williamH@gentoo \
--to=williamh@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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