xorg.conf

In article <5rof8sF15lcgcU2@mid.individual.net>,
Derek Turner <frderek@cesmail.net> wrote:

> Meat Plow wrote:
> Do I need to
> >> start my file manager as root? I seem to remember other distros having a
> >> regular file manager and then one with root privileges. I wonder if that
> >> could be the difference.
> >>
> when you find it (see above) use sudo gedit xorg.conf in a terminal to
> launch the editor in root mode.
> >
Interesting thing is when I sudo gedit xorg.conf it opens it up and is
blank! If I just start gedit (sudo gedit) then go to file>open>xorg.conf
it opens as expected with all of the text. Strange.
 


In article <5rof8sF15lcgcU2@mid.individual.net>,
Derek Turner <frderek@cesmail.net> wrote:

> Meat Plow wrote:
> Do I need to
> >> start my file manager as root? I seem to remember other distros having a
> >> regular file manager and then one with root privileges. I wonder if that
> >> could be the difference.
> >>
> when you find it (see above) use sudo gedit xorg.conf in a terminal to
> launch the editor in root mode.
> >
Interesting thing is when I sudo gedit xorg.conf it opens it up and is
blank! If I just start gedit (sudo gedit) then go to file>open>xorg.conf
it opens as expected with all of the text. Strange.
 
brian wrote on Thu, 06 Dec 2007 13:20:21 -0500:

> Interesting thing is when I sudo gedit xorg.conf it opens it up and is
> blank!

Yeah, I suppose so if you really type sudo gedit xorg.conf (because then,
gedit searches for the file xorg.conf in the *current* directory).
It should open the correct file if you type sudo gedit /etc/X11/xorg.conf

> If I just start gedit (sudo gedit) then go to file>open>xorg.conf
> it opens as expected with all of the text. Strange.

Not really, see above.

--
Simon Gerber
simugerber@student.ethz.ch
 
brian wrote on Thu, 06 Dec 2007 13:20:21 -0500:

> Interesting thing is when I sudo gedit xorg.conf it opens it up and is
> blank!

Yeah, I suppose so if you really type sudo gedit xorg.conf (because then,
gedit searches for the file xorg.conf in the *current* directory).
It should open the correct file if you type sudo gedit /etc/X11/xorg.conf

> If I just start gedit (sudo gedit) then go to file>open>xorg.conf
> it opens as expected with all of the text. Strange.

Not really, see above.

--
Simon Gerber
simugerber@student.ethz.ch
 
brian wrote on Thu, 06 Dec 2007 13:20:21 -0500:

> Interesting thing is when I sudo gedit xorg.conf it opens it up and is
> blank!

Yeah, I suppose so if you really type sudo gedit xorg.conf (because then,
gedit searches for the file xorg.conf in the *current* directory).
It should open the correct file if you type sudo gedit /etc/X11/xorg.conf

> If I just start gedit (sudo gedit) then go to file>open>xorg.conf
> it opens as expected with all of the text. Strange.

Not really, see above.

--
Simon Gerber
simugerber@student.ethz.ch
 
in 26935 20071205 201621 clay <clay@mation.com> wrote:
>Meat Plow wrote:
>> On Wed, 05 Dec 2007 14:46:55 -0500, brian wrote:
>>
>>> In article <fj6tju$f7a$1@cb.generation-online.de>,
>>> Simon Gerber <simugerber@student.ethz.ch> wrote:
>>>
>>>> brian wrote on Wed, 05 Dec 2007 14:09:14 -0500:
>>>>
>>>> > okay, I've hit google and a couple of linux (ubuntu) sites and for the
>>>> > life of me I cannot find xorg.conf file. It should be in the ~/etc/X11/
>>>> > folder but it's not (I did a search for it also). I need to edit it to
>>>> > use the Gsynaptics touchpad program. I'm using Ubuntu 7.10 with gnome
>>>> > (haven't change anything from a clean install from the livecd. Does
>>>> > anyone know where I might find it?
>>>> >
>>>> > tia
>>>>
>>>> If you mistyped and meant /etc/X11 instead of *~*/etc/X11 then I cannot
>>>> see where your xorg.conf might be.
>>>>
>>>> However if you didn't mistype peek into /etc/X11 where you'll probably
>>>> find your xorg.conf.
>>>>
>>>> HTH
>>>
>>> Whoops. I thought "~" meant that it is the root directory not the
>>> user's. Sorry.
>>> I did, however, look into /etc/X11/ and couldn't see it. Do I need to
>>> start my file manager as root? I seem to remember other distros having a
>>> regular file manager and then one with root privileges. I wonder if that
>>> could be the difference.
>>>
>>
>> Just open a terminal and type slocate xorg.conf.
>
>crap... as long as we're going to all the trouble to open a terminal,
>why not just:
>cd /etc/X11/
>ls xorg*
>*g*

That assumes you already know where it is.
This thread is about locating it
 
On Wed, 5 Dec 2007, in the Usenet newsgroup alt.os.linux.ubuntu, in article
<1f3k5r.9k4.19.7@news.alt.net>, Meat Plow wrote:

>Mark South wrote:

>> find /etc -iname xorg.conf
>
>~$ slocate xorg.conf works too

slocate (and the original 'locate') consult a database of files usually
created as a nightly cron-job. If your system isn't running at the
scheduled time, and you are not running a part-time cron daemon like
anacron or fcron, then the database won't be up to date. Thus it will
report about files you have deleted, and won't know about files that
have been created or moved since that database update. The 'find'
command looks to see what is "there" now, and tends to be much slower
than reading a pre-existing database (that was created by running
find as part of that cron-job).

Find can be made to run faster by (as here) limiting the area of the
filesystem that is searched. This implies that you are somewhat familiar
with the way files are located. See http://tldp.org/guides.html and
look through the 'Linux Filesystem Hierarchy' guide, which is a more
user-friendly translation of the 'Filesystem Hierarchy Standard' which
is available from http://www.pathname.com/fhs/.

Old guy
 
On Wed, 5 Dec 2007, in the Usenet newsgroup alt.os.linux.ubuntu, in article
<1f3k5r.9k4.19.7@news.alt.net>, Meat Plow wrote:

>Mark South wrote:

>> find /etc -iname xorg.conf
>
>~$ slocate xorg.conf works too

slocate (and the original 'locate') consult a database of files usually
created as a nightly cron-job. If your system isn't running at the
scheduled time, and you are not running a part-time cron daemon like
anacron or fcron, then the database won't be up to date. Thus it will
report about files you have deleted, and won't know about files that
have been created or moved since that database update. The 'find'
command looks to see what is "there" now, and tends to be much slower
than reading a pre-existing database (that was created by running
find as part of that cron-job).

Find can be made to run faster by (as here) limiting the area of the
filesystem that is searched. This implies that you are somewhat familiar
with the way files are located. See http://tldp.org/guides.html and
look through the 'Linux Filesystem Hierarchy' guide, which is a more
user-friendly translation of the 'Filesystem Hierarchy Standard' which
is available from http://www.pathname.com/fhs/.

Old guy
 
On Wed, 5 Dec 2007, in the Usenet newsgroup alt.os.linux.ubuntu, in article
<1f3k5r.9k4.19.7@news.alt.net>, Meat Plow wrote:

>Mark South wrote:

>> find /etc -iname xorg.conf
>
>~$ slocate xorg.conf works too

slocate (and the original 'locate') consult a database of files usually
created as a nightly cron-job. If your system isn't running at the
scheduled time, and you are not running a part-time cron daemon like
anacron or fcron, then the database won't be up to date. Thus it will
report about files you have deleted, and won't know about files that
have been created or moved since that database update. The 'find'
command looks to see what is "there" now, and tends to be much slower
than reading a pre-existing database (that was created by running
find as part of that cron-job).

Find can be made to run faster by (as here) limiting the area of the
filesystem that is searched. This implies that you are somewhat familiar
with the way files are located. See http://tldp.org/guides.html and
look through the 'Linux Filesystem Hierarchy' guide, which is a more
user-friendly translation of the 'Filesystem Hierarchy Standard' which
is available from http://www.pathname.com/fhs/.

Old guy
 
On Thu, 06 Dec 2007 14:00:14 -0600, Moe Trin wrote:

> On Wed, 5 Dec 2007, in the Usenet newsgroup alt.os.linux.ubuntu, in article
> <1f3k5r.9k4.19.7@news.alt.net>, Meat Plow wrote:
>
>>Mark South wrote:
>
>>> find /etc -iname xorg.conf
>>
>>~$ slocate xorg.conf works too
>
> slocate (and the original 'locate') consult a database of files usually
> created as a nightly cron-job. If your system isn't running at the
> scheduled time, and you are not running a part-time cron daemon like
> anacron or fcron, then the database won't be up to date. Thus it will
> report about files you have deleted, and won't know about files that
> have been created or moved since that database update. The 'find'
> command looks to see what is "there" now, and tends to be much slower
> than reading a pre-existing database (that was created by running
> find as part of that cron-job).
>
> Find can be made to run faster by (as here) limiting the area of the
> filesystem that is searched. This implies that you are somewhat familiar
> with the way files are located. See http://tldp.org/guides.html and
> look through the 'Linux Filesystem Hierarchy' guide, which is a more
> user-friendly translation of the 'Filesystem Hierarchy Standard' which
> is available from http://www.pathname.com/fhs/.
>
> Old guy

That's fine and dandy if all your assumptions are correct.
 

Back
Top