Re: [opensuse] Will making changes from command line 'confuse' the GUI?
- From: "Jeffrey L. Taylor" <abluz@xxxxxxxxxxxxxxxx>
- Date: Sat, 15 Dec 2007 10:19:08 -0600
Quoting Steve Jacobs <stevetjacobs@xxxxxxxxx>:
I have a laptop running OpenSUSE 10.3.
Powering up this morning, during the startup process that displays the
status as each component is loaded, I saw that the system timed out
searching for an NTP server. This makes sense, as there was no network
connection yet. I thought it would probably be a good idea to investigate
how to remove that from startup, and let it run after the system is booted
and online. Which lead to my question -
In the past, while learning my way about various linux systems, I've tended
to get into trouble when I make changes from the command-line, usually at
the recommendation of someone more knowlegeable than I am, and then make
other changes using the GUI. It seems that sometimes the GUI doesn't know
about the changes implemented at the command line, and this sometimes leads
to the entire system becoming hosed.
I realize there's only one actual filesystem, the config files are what they
are, and the GUI is only reading the same config files I'd be changing
manually at the command line anyway, but I didn't make up this scenario out
of thin air.For whatever reason, I have encountered problems that I think
are related to this. And at this point, even if my concerns may have been
valid 5 years ago and those issues no longer exist, I'm still uneasy about
making changes from both places.
SO, to those of you that actually know what you're doing, as opposed to me:
Is this a ridiculous concern, or should I avoid 'mixing & mtaching', and
pretty much stick to the CLI, or stick to the GUI, when making changes to
the system configuration?
It is best to stick with one or the other. Usually this can be done on a per
app/system basis. I usually use Yast to change the "run levels",
i.e. enable/disable various servers. However, my Postfix setup I manage by
editing the config files directly, Yast isn't up to the complexity of my
situation.
Or learn how the "SuSE/YaST" way and how to do that from the command line.
Look into "innserv" for changing run levels. Modify one service with Yast and
compare the old and new config files to verify that your understanding is
correct.
I have used various distributions over the years and have a tendency to "Just
Do It" from the command line and a text editor. I encountered some of the
same problems you are finding and have decided that it is better to learn the
GUI tools at least until I understand what they are doing. And stick to one
GUI tool, even where there are multiple ones. For example, just use one
package manager. Pick one and stick with it. Expect problems when changing
so don't change often.
HTH,
Jeffrey
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
- References:
- [opensuse] Will making changes from command line 'confuse' the GUI?
- From: Steve Jacobs
- [opensuse] Will making changes from command line 'confuse' the GUI?
- Prev by Date: Re: [opensuse] rsync - keys - no-password question
- Next by Date: Re: [opensuse] VitualBox OSE - kernel module missing friom update repo
- Previous by thread: Re: [opensuse] Will making changes from command line 'confuse' the GUI?
- Next by thread: Re: [opensuse] Will making changes from command line 'confuse' the GUI?
- Index(es):
Relevant Pages
|
