From: Stamatis Mitrofanis <ewstam@softhome.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug can configure XFree86
Date: Sun, 30 Dec 2001 03:23:09 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100968255400378@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100923910820843@msgid-missing>
David Brownell wrote:
>...
>
>I'm making a fairly general point here, which I hope most
>folk will agree with: Linux desktop systems should do a
>lot more "automatic detection" of hardware ("hotplugging")
>than they've traditionally done, and demand a lot less user
>input on configuration changes. It's been getting better in
>the past few years ... and I hope it'll continue !! Likewise,
>I'll hope that the distros will converge on at least the tools
>in those areas, if not all the policies they use. That's harder.
>
Ok... Enough general theory.
The idea was that the hotplug scripts can autoconfigure XFree86. We
consider XFree86 to be similar to the kernel (drivers, modules,
devices...). The scripts _could_ map actual devices to more abstract
XFree86 devices.
I suggest that we do some cherry-picking from open-source installation
programs around to find good ways to complete the XFree86 configuration.
Then we can include things in hotplug. (right?)
_______________________________________________
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:[~2001-12-30 3:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-25 0:11 Hotplug can configure XFree86 Stamatis Mitrofanis
2001-12-27 20:32 ` David Brownell
2001-12-27 23:00 ` Stamatis Mitrofanis
2001-12-28 1:10 ` Bill Nottingham
2001-12-28 4:51 ` David Brownell
2001-12-30 3:23 ` Stamatis Mitrofanis [this message]
2001-12-30 3:56 ` Miles Lane
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-100968255400378@msgid-missing \
--to=ewstam@softhome.net \
--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.