From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/livecd-tools:master commit in: init.d/
Date: Wed, 3 Oct 2012 14:17:29 +0000 (UTC) [thread overview]
Message-ID: <1349273388.476fe7f59765f889d010c507f1142d48b724d60b.WilliamH@gentoo> (raw)
commit: 476fe7f59765f889d010c507f1142d48b724d60b
Author: William Hubbs <williamh <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 3 14:09:48 2012 +0000
Commit: William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Wed Oct 3 14:09:48 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/livecd-tools.git;a=commit;h=476fe7f5
gpm-pre: fix sourcing of hwsetup settings
Source the files only if they exist. Also, warn if a mouse was not
detected. The gpm init script already detects if a mouse isn't
configured and refuses to start, which is what we want.
X-Gentoo-Bug: 408533
X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=408533
---
init.d/gpm-pre | 10 ++++++----
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/init.d/gpm-pre b/init.d/gpm-pre
index f44e5c2..ef97e38 100755
--- a/init.d/gpm-pre
+++ b/init.d/gpm-pre
@@ -9,10 +9,12 @@ depend() {
}
start() {
- # FIXME: If MOUSE_DEVICE is empty, we actually do not want to do anything, not even start gpm.
- # created by hwsetup
- source /etc/sysconfig/gentoo
- source /etc/sysconfig/mouse
+ [ -f /etc/sysconfig/gentoo ] && source /etc/sysconfig/gentoo
+ [ -f /etc/sysconfig/mouse ] && source /etc/sysconfig/mouse
+ if [ -z "${MOUSE_DEVICE}" ]; then
+ ewarn "No mouse detected. GPM will not be started."
+ return 0
+ fi
einfo "Mouse is ${HILITE}${MOUSE_FULLNAME}${NORMAL} at ${HILITE}${MOUSE_DEVICE}${NORMAL} ..."
if [ $(grep "#MOUSE=${MOUSETYPE}" /etc/conf.d/gpm) ]; then
next reply other threads:[~2012-10-03 14:17 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 14:17 William Hubbs [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 16:57 [gentoo-commits] proj/livecd-tools:master commit in: init.d/ Ben Kohler
2021-07-29 4:05 Georgy Yakovlev
2021-02-25 23:12 Ben Kohler
2020-11-06 0:58 Matt Turner
2020-11-06 0:29 Matt Turner
2020-11-05 23:49 Matt Turner
2020-11-05 23:49 Matt Turner
2020-11-05 23:49 Matt Turner
2020-04-23 18:08 Rick Farina
2019-09-20 19:32 Matt Turner
2019-09-20 19:32 Matt Turner
2018-09-14 5:27 Matt Turner
2018-08-24 14:57 Richard Farina
2018-03-16 1:07 Richard Farina
2018-03-15 18:49 Richard Farina
2018-03-15 17:07 Richard Farina
2018-03-15 4:34 William Hubbs
2018-03-15 3:51 Richard Farina
2017-08-28 18:43 Richard Farina
2017-02-25 0:50 Robin H. Johnson
2016-07-09 4:27 William Hubbs
2015-12-11 17:53 William Hubbs
2015-12-11 17:53 William Hubbs
2015-11-01 20:44 Richard Farina
2014-05-22 16:30 Richard Farina
2013-07-05 21:55 William Hubbs
2013-07-05 21:46 William Hubbs
2013-01-03 18:20 William Hubbs
2011-10-25 2:37 William Hubbs
2011-09-19 1:41 Jorge Manuel B. S. Vicetto
2011-06-30 20:29 William Hubbs
2011-06-30 20:12 William Hubbs
2011-06-28 5:22 William Hubbs
2011-06-28 5:18 William Hubbs
2011-06-28 5:13 William Hubbs
2011-05-01 3: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
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=1349273388.476fe7f59765f889d010c507f1142d48b724d60b.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