On 2015-11-14 17:22, Mike Burns wrote:
On 2015-11-14 16.27.30 +0100, bian wrote:
* mention that the "segmentation fault"-message when running the X
-configure is harmless and that the xorg.conf.new file was created as
it
should.
That's a bug, and while I likely can't fix it (will gladly look), we'll
need your dmesg and the backtrace from the coredump, in the least.
I will post this shortly in the bugs list on your suggestion.
* be sure that this info is obvious: "Your xorg.conf file is
/root/xorg.conf.new ". A new user typically logs in to his account, su
to
root, run X -configure, and start looking for the file in the current
directory. Well, it's not there.
Seems like something that should be updated in Xorg(1). Though, I must
say: typically a new user will not configure X at all,
true, but how can faq 11 help if he must (or want).
and won't use su(1) if they do.
Does this confusion appear when using doas(1)/sudo(1)?
Yes. Running sudo X -configure will create the file in /root as
expected. This way of working does not improve on the situation.
* clear up the links
http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/xenocara/distrib/notes/README.amd64
and
http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/xenocara/distrib/notes/README.i386
. The linked text refers to the page where the links are. This is not
very
helpful as the user never would have clicked the link if the info
already
was available. Furthermore, the linked text ends with the phrase
"problem_blurb" suggesting that it is unfinished.
Perhaps you have a patch that clarifies this?
No patch, but a short term improvement is to replace the text which the
above links point at with the text in /usr/X11R6/README included in the
5.8 release.
Generally about faq 11, there was a promising discussion on quality
issues in http://marc.info/?l=openbsd-www&m=139222057820465&w=2 but it
seems to have fizzled out unfortunately.
