From: Stamatis Mitrofanis <ewstam@softhome.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug can configure XFree86
Date: Thu, 27 Dec 2001 23:00:28 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100949404228294@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100923910820843@msgid-missing>
David Brownell wrote:
>I certainly like the notion of the Linux distros having a better integration
>story in such areas, but I suspect there's a certain matter of installed base
>to worry about in terms of xf86config, kudzu, YaST, and so forth ...
>
The installation programs I've seen so far only provided a
once-and-for-all static configuration file. I'll be fully satisfied with
Linux hardware management when I can freely swap hard drives with any
computer and still see the system come up just as it used to.
The ugliest problem to solve is that of the X server not coming up when
the graphics adapter has changed. I couldn't find so far a better
solution than to integrate some autoconfiguration with the linux-hotplug
scripts.
I mentioned that there can be "hot" and "cold" XF86Config parts. The
installation programs can manage the "cold" parts which will contain
information that linux-hotplug can't (yet) retrieve. Eventually, the
"cold" part will become minimal.
_______________________________________________
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-27 23:00 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 [this message]
2001-12-28 1:10 ` Bill Nottingham
2001-12-28 4:51 ` David Brownell
2001-12-30 3:23 ` Stamatis Mitrofanis
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-100949404228294@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).