Linked by Thom Holwerda on Mon 18th Aug 2008 23:33 UTC, submitted by Charles Wilson
Thread beginning with comment 327352
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Much ado about nothing
by jack_perry on Tue 19th Aug 2008 20:49
in reply to "RE[4]: Much ado about nothing"
If you want to tweak the settings of apache to start with a specified flag or what have you...
Well, I might have to tweak the settings of Xorg.conf too. That's way more advanced, but if I've bought a new computer with an as-yet unsupported monitor there's fun I'll have to have regardless.
I might have to tweak /etc/fstab.
See any one of a large number of experts offering advice to non-experts online. Lots of settings have to be tweaked from time to time.
RE[6]: Much ado about nothing
by leos on Wed 20th Aug 2008 18:53
in reply to "RE[5]: Much ado about nothing"
Well, I might have to tweak the settings of Xorg.conf too. That's way more advanced, but if I've bought a new computer with an as-yet unsupported monitor there's fun I'll have to have regardless.
The fundamental problem here is that you have to modify your xorg.conf. The problem is not that you can't find it, the problem is that you have to edit it in the first place. Xorg is moving towards the correct solution to this problem (better autodetection (xrandr) and bulletproof X).
I might have to tweak /etc/fstab.
Again, something that a regular user should never have to do. If they do, then the autodetection is broken and should be fixed. Renaming /etc/fstab to "/System Settings/mount points.config" or similar is not going to solve anything.
See any one of a large number of experts offering advice to non-experts online. Lots of settings have to be tweaked from time to time.
And they shouldn't have to be. But until those things get fixed, the file and folder names are certainly not the problem. If an expert is posting instructions for how to make a change to fstab, they will say something like "Open /etc/fstab and change line 4 to ..." which bypasses the whole problem since someone is telling you where to find that file. The non-expert doesn't have to find it themselves so whether it is etc or settings makes no difference.




Member since:
2005-09-21
Someone else already mentioned ~/.fonts
You shouldn't have to mess with the startup scripts. If you want a program starting in the GUI, use the GUI tools in Gnome or KDE to start it after boot. If you want to configure a system service to start (already extremely unlikely for any average user), use any startup script GUI tool to do it.
If you want to tweak the settings of apache to start with a specified flag or what have you, you're way advanced and finding init.d is a trivial and insignificant part of the task.