From: 520047054719-0001@t-online.de (Oliver Neukum)
To: linux-hotplug@vger.kernel.org
Subject: Re: User-level Tasks in Hotplug Scripts?
Date: Sat, 02 Feb 2002 22:52:32 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101269042825395@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101256895903801@msgid-missing>
> > Is there anything wrong with the simplistic approach of having a demon
> > listening on a socket? If you want it generic, you have to use generic
> > means of communication.
>
> You don't want to pass out permission to access your X server to anyone
> who happens to ask for it (if you do, you've compromized everything,
> or go down into compartmentalized workstation hell, someplace where we
> went 10 years ago and found fundamentally painful).
> So the issue is fundamentally one of authenticating
> the configuration GUI's process to the X server to allow connection.
There's no reason the listening demon has to be part of X, or is there ?
An interrested user would start a task listening upon login.
Regards
Oliver
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2002-02-02 22:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 13:09 User-level Tasks in Hotplug Scripts? Ryan Shaw
2002-02-01 23:58 ` David Brownell
2002-02-02 20:55 ` Jim Gettys
2002-02-02 22:02 ` Oliver Neukum
2002-02-02 22:12 ` Jim Gettys
2002-02-02 22:52 ` Oliver Neukum [this message]
2002-02-02 23:02 ` David Brownell
2002-02-03 0:58 ` Scott Cuyle Fritzinger
2002-02-03 8:36 ` Greg KH
2002-02-04 6:02 ` Dmitry Yu. Bolkhovityanov
2002-02-04 15:10 ` Jim Gettys
2002-02-04 19:28 ` Jim Carter
2002-02-05 3:32 ` David Brownell
2002-02-05 15:05 ` Ryan Shaw
2002-02-06 14:30 ` Marcus Harnisch
2002-02-06 14:54 ` Jim Gettys
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=marc-linux-hotplug-101269042825395@msgid-missing \
--to=520047054719-0001@t-online.de \
--cc=linux-hotplug@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.