[SOLVED] /etc/X11/xorg.conf not available on reboot.

[kagashe]

Xorg 7.4 works without any xorg.conf file but in case I generate one it is not saved and hence not available for next boot. I copied the file to /home/tc and added this line to /opt/bootlocal.sh

cp /home/tc/xorg.conf /etc/X11/xorg.conf

kagashe

[curaga]

You can tweak what is saved to your backup in /opt/.filetool.lst - it's the list of what files/directories are saved on shutdown.

Edit: see the "backup" part of getting_started.html

[kagashe]

You can tweak what is saved to your backup in /opt/.filetool.lst - it's the list of what files/directories are saved on shutdown.

Edit: see the "backup" part of getting_started.html

I am using backup to save /home/tc and that is how a copy of xorg.conf is available on reboot. What I mean is Xorg started fresh on reboot without my xorg.conf and failed. I have added a line in /opt/bootlocal.sh to copy the file from /home/tc to /etc/X11 in addition to modprobe commands to load the modules which are not being added in my case (intel chip).

As you have written in your Xorg document that user should generate a file with "# Xorg -configure" please warn the user that any file generated as above and copied as /etc/X11/xorg.conf is not going to be available for next reboot, else, remedy the situation as I have done or by any other means.

kagashe

[^thehatsrule^]

You can also use the backup to restore those files upon next reboot, which is the standard method afaik.

[kagashe]

You can also use the backup to restore those files upon next reboot, which is the standard method afaik.

I have tried. /opt/.filetool.lst refuses to accept /etc/X11/xorg.conf file for back-up. I got errors on exit (shutdown canceled) and I had to remove the line:
/etc/X11/xorg.conf

from .filetool.lst

However, my method of keeping a copy of xorg.conf at /home/tc and putting cp command to copy it to /etc/X11 in bootlocal.sh works.

kagashe

[^thehatsrule^]

You probably made the mistake of placing the leading / in front, as the other entries should show I think.  Probably could be clearer on the getting started doc (if you were using that).

[kagashe]

You probably made the mistake of placing the leading / in front, as the other entries should show I think.  Probably could be clearer on the getting started doc (if you were using that).

I did it from GUI Tools/Add_to_filetool which places the leading / in front.

This time once again I used GUI to insert the line, then opened it on vi and removed the leading /.

Thank you.

kagashe

[^thehatsrule^]

This seems to be misleading.  I tried to reproduce your steps, but found that either having the leading / in front or not doesn't matter because tar will automatically remove it.

The suggestion I gave was just something I remembered, probably from another/older version.  I have no idea why it worked for you(?).

To others: please ignore my previous post in this thread.

[kagashe]

This seems to be misleading.  I tried to reproduce your steps, but found that either having the leading / in front or not doesn't matter because tar will automatically remove it.

The suggestion I gave was just something I remembered, probably from another/older version.  I have no idea why it worked for you(?).

To others: please ignore my previous post in this thread.

Yes., having a leading / does not matter but there is a problem when you reboot/shutdown with a check mark in Back up. You get following message:

Back up produced errors. Please see /tmp/backup_status. Shutdown aborted.

and the shutdown is actually aborted. File /tmp/backup_status reads:

tar: removing leading '/' from member names.

If that is supposed to mean that leading '/' gets removed from the file listed in /opt/.filetool.lst it is not REMOVED.

Finally you have to shutdown unchecking the Back up option and it is fine since in spite of leading '/' in .filetool.lst the file gets loaded on reboot.

kagashe

[^thehatsrule^]

Aha, I see what the problem is now.  Thanks for replying again.

I was backing up manually without shutting down, and overlooked different scenarios.  While keeping the idea that the fix is to remove the leading /, a quick interim fix would be to change the add2file program.  For example, if modifying the .cxx, you can change line 33 to

Code: [Select]

fout << chooser.value()+1 << endl;
This brings up some problems with some scripts related to this that will be looked at.

FYI, that error in backup_status is generally a "safe-to-ignore" warning from tar and it does not mean that it modifies your .filetool.lst at all.