[opensuse] Network settings in openSuse
I would like to know how to change the settings in openSuse without causing damage. I looked at yast, but it declares these are managed by NetworkManager. I looked at a couple of the network manager applets, but did not see how to proceed. I wish to change my ports from DHCP to static. I need to be able to add name servers etc. when I do this. I would also like to be able to tell the system what the password for my Wi-Fi is so that it does not prompt me all of the time. I think NetworkManager needs to be shut down to make these changes. But how does one do that. I tried disabling it in services but that did not appear to work. I would also like to know how to modify user parameters, such as the default shell, without breaking the system. I used a command line tool (forgot which one:-( and nobody was able to log into the system. I assume the damn check sums were not updated correctly. It used to be so easy to just edit /etc/passwd, or /etc/networking to make these changes. Thanks, Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/02/2015 06:48 PM, don fisher wrote:
I would like to know how to change the settings in openSuse without causing damage. I looked at yast, but it declares these are managed by NetworkManager. I looked at a couple of the network manager applets, but did not see how to proceed.
I wish to change my ports from DHCP to static. I need to be able to add name servers etc. when I do this. I would also like to be able to tell the system what the password for my Wi-Fi is so that it does not prompt me all of the time. I think NetworkManager needs to be shut down to make these changes. But how does one do that. I tried disabling it in services but that did not appear to work.
If you're running KDE, you should have an icon on your task bar for network connection. Click on it and then "Manage Connection". You can then configure your connections as desired. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, For the shell use the chsh command to change the shell for the current user, or as root `chsh username` of the user for which the shell must be changed e.g. chsh user1 The command will prompt you for the default shell which must be set for user1. As for the network configuration (in 13.1 and earlier) there is a switch in yast network settings which determines how the network interfaces are managed. It's in the Global Options Tab in console mode, but must be at the same place in the GUI. By switching to Traditional Method with ifup you can manage the settings for the network interfaces via yast or the files under /etc/sysconfig/network/ Best Regards, I. Petrov On 03/03/2015 01:48 AM, don fisher wrote:
I would like to know how to change the settings in openSuse without causing damage. I looked at yast, but it declares these are managed by NetworkManager. I looked at a couple of the network manager applets, but did not see how to proceed.
I wish to change my ports from DHCP to static. I need to be able to add name servers etc. when I do this. I would also like to be able to tell the system what the password for my Wi-Fi is so that it does not prompt me all of the time. I think NetworkManager needs to be shut down to make these changes. But how does one do that. I tried disabling it in services but that did not appear to work.
I would also like to know how to modify user parameters, such as the default shell, without breaking the system. I used a command line tool (forgot which one:-( and nobody was able to log into the system. I assume the damn check sums were not updated correctly.
It used to be so easy to just edit /etc/passwd, or /etc/networking to make these changes.
Thanks, Don
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJU9QYiAAoJEH8sJoKRFRU5fkYP/iKul45M34LwiLgFM2fphriQ Q2vDXB8SbPIyjAd5zW55xzC2Ho/aTGpPXxmPMUvdnan1TuVYWVtvJDiX83vLHh6T EOvjiFAmzVlR88QHTJeNIcSRNa4kPLPF1RevfvoOifvTnS0B+3r19pT9CBrIsoZI jY2kp+6plF5fv5gFIsLQ+3FD/+LDbK0vE8OHnuRKcBrNgj8xdpwfnjAnbq1/Azl5 E/o47Ebl5gpfBda6IOaD28r1FHSKpr/iJeOb1GAScpGYN52TNzc2gyu/2OccxPH+ B16YTTs0kDbJVuyvDbt04i5oMLGkSNerKaCM9Mm9nDSRul+UFLcwd2zOnx0XVBsw OZwgFiZpJHPCuHKd42vQ8ykGZ/4yvxOj0Yyazif7WxQo4PO7KQplJNfNQCdv/Ppt Bi3Wr7wFUE1wISE55kNB9U3lyaveEbi08KvJQnH9VtD7uenKKLjAYV24tfclK+/O vbOO9QCqSV1gdI2ZwkkYlNV+iGAwJ9/b5ZIzrGT5iqxyFu+Ipvj8O4D5tZYTFEJY rKrHW6YuDO224sMCRuKxYDdt8NdsskfCWvMkDjS8TqM8TksYPj/hFCUa9VJiXigM G1vG/xpuf6cC22dfXuRkIDeGjiWb1RQe57J06GoPD6289TCRJokBTApoOkMwyL7L Y2BlLc0GWYtvpHbIHgDC =Z3Wn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/02/15 17:53, I.Petrov wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
For the shell use the chsh command to change the shell for the current user, or as root `chsh username` of the user for which the shell must be changed e.g.
chsh user1
The command will prompt you for the default shell which must be set for user1. As for the network configuration (in 13.1 and earlier) there is a switch in yast network settings which determines how the network interfaces are managed. It's in the Global Options Tab in console mode, but must be at the same place in the GUI. By switching to Traditional Method with ifup you can manage the settings for the network interfaces via yast or the files under /etc/sysconfig/network/
Best Regards, I. Petrov
I have tried the chsh command with some success. But when I changed root to tcsh I could no longer su into it, nor would yast accept the root passwd. When I changed the root shell back to bash, it all appeared to recover. Any ideas? Network next:-) Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 3 Mar 2015 18:09, don fisher <hdf3@...> wrote:
On 03/02/15 17:53, I.Petrov wrote:
Hello,
For the shell use the chsh command to change the shell for the current user, or as root `chsh username` of the user for which the shell must be changed e.g.
chsh user1
The command will prompt you for the default shell which must be set for user1. As for the network configuration (in 13.1 and earlier) there is a switch in yast network settings which determines how the network interfaces are managed. It's in the Global Options Tab in console mode, but must be at the same place in the GUI. By switching to Traditional Method with ifup you can manage the settings for the network interfaces via yast or the files under /etc/sysconfig/network/
Best Regards, I. Petrov
I have tried the chsh command with some success. But when I changed root to tcsh I could no longer su into it, nor would yast accept the root passwd. When I changed the root shell back to bash, it all appeared to recover. Any ideas?
Have you tried what happens in a 'bash' root shell, if you use a small group of commands: (presume tcsh is /usr/bin/tcsh) [code] export SHELL=/usr/bin/tcsh; exec /usr/bin/tcsh -l [/code] If this does not satify you, try ...tcsh -i If that works for you, edit your "~/.bash_profile" or "~/.bashrc" to end with this commands. Shrugs, Hack? Yes, but what else is new? - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/03/15 10:24, Michael Foerster wrote:
On Tue, 3 Mar 2015 18:09, don fisher <hdf3@...> wrote:
On 03/02/15 17:53, I.Petrov wrote:
Hello,
For the shell use the chsh command to change the shell for the current user, or as root `chsh username` of the user for which the shell must be changed e.g.
chsh user1
The command will prompt you for the default shell which must be set for user1. As for the network configuration (in 13.1 and earlier) there is a switch in yast network settings which determines how the network interfaces are managed. It's in the Global Options Tab in console mode, but must be at the same place in the GUI. By switching to Traditional Method with ifup you can manage the settings for the network interfaces via yast or the files under /etc/sysconfig/network/
Best Regards, I. Petrov
I have tried the chsh command with some success. But when I changed root to tcsh I could no longer su into it, nor would yast accept the root passwd. When I changed the root shell back to bash, it all appeared to recover. Any ideas?
Have you tried what happens in a 'bash' root shell, if you use a small group of commands: (presume tcsh is /usr/bin/tcsh) [code] export SHELL=/usr/bin/tcsh; exec /usr/bin/tcsh -l [/code]
If this does not satify you, try ...tcsh -i
If that works for you, edit your "~/.bash_profile" or "~/.bashrc" to end with this commands.
Shrugs, Hack? Yes, but what else is new?
- Yamaban.
Thanks, I had thought of a similar idea. But I was curious why root will not run under tcsh? I like to understand what is going on. Is this just a suse thing? And what is breaking? I have used tcsh for root in my previous life under Fedora, but don't care for that distribution anymore. Don -- ----------------------------------------------------------------- | Don Fisher hdf3@comcast.net | | 865 W. Cresta Loma Dr. VOICE: (520)888-7613 | | Tucson, AZ. 85704-3705 | ----------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 3 Mar 2015 18:33, don fisher <hdf3@...> wrote:
On 03/03/15 10:24, Michael Foerster wrote:
On Tue, 3 Mar 2015 18:09, don fisher <hdf3@...> wrote:
On 03/02/15 17:53, I.Petrov wrote: [snip]
I have tried the chsh command with some success. But when I changed root to tcsh I could no longer su into it, nor would yast accept the root passwd. When I changed the root shell back to bash, it all appeared to recover. Any ideas?
Have you tried what happens in a 'bash' root shell, if you use a small group of commands: (presume tcsh is /usr/bin/tcsh) [code] export SHELL=/usr/bin/tcsh; exec /usr/bin/tcsh -l [/code]
If this does not satify you, try ...tcsh -i
If that works for you, edit your "~/.bash_profile" or "~/.bashrc" to end with this commands.
Shrugs, Hack? Yes, but what else is new?
- Yamaban.
Thanks, I had thought of a similar idea. But I was curious why root will not run under tcsh? I like to understand what is going on. Is this just a suse thing? And what is breaking? I have used tcsh for root in my previous life under Fedora, but don't care for that distribution anymore.
AFAIK there are some deeply ingrained bashisms and some other specific shell dependencies that simply do not work with csh/tcsh/ksh/pdksh, ash/sash/dash/bash are working, bash the best. Some of this is historic in the depth of SUSE history, some of this is carelessness from the devs in younger times. For a long time there was no Senior SLE dev member that used something other than bash as root-shell, and such discrepancies have crept in undetected. I'm not pointing at people, just showing how this was possible without being detected long before. There are efforts to reduce bashism in simple shell scripts, but not all scriptlets are caught that way. In some areas this is more a tribulations bordering on exertion than a simple endevour. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/03/15 11:23, Yamaban wrote:
On Tue, 3 Mar 2015 18:33, don fisher <hdf3@...> wrote:
AFAIK there are some deeply ingrained bashisms and some other specific shell dependencies that simply do not work with csh/tcsh/ksh/pdksh, ash/sash/dash/bash are working, bash the best.
Some of this is historic in the depth of SUSE history, some of this is carelessness from the devs in younger times.
For a long time there was no Senior SLE dev member that used something other than bash as root-shell, and such discrepancies have crept in undetected.
I'm not pointing at people, just showing how this was possible without being detected long before.
There are efforts to reduce bashism in simple shell scripts, but not all scriptlets are caught that way. In some areas this is more a tribulations bordering on exertion than a simple endevour.
- Yamaban. I have another problem with tcsh. If I am in a shell under bash and issue the tcsh command, it works as expected. If I change the default shell in /etc/passwd using the chsh command suggested, the shell is changed as a listing of /etc/passwd shows. But when I try and execute anything it says it does not know anything about display:0. This is a fatal mistake, for emacs and many other commands. I tried both /bin/tcsh and /usr/bin/tcsh. I have not tried to examine them but I assume they are the same thing? Any ideas? Is this a bug?
Thanks Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 3 Mar 2015 22:57, don fisher <hdf3@...> wrote:
On Tue, 3 Mar 2015 18:33, don fisher <hdf3@...> wrote:
AFAIK there are some deeply ingrained bashisms and some other specific shell dependencies that simply do not work with csh/tcsh/ksh/pdksh, ash/sash/dash/bash are working, bash the best.
Some of this is historic in the depth of SUSE history, some of this is carelessness from the devs in younger times.
For a long time there was no Senior SLE dev member that used something other than bash as root-shell, and such discrepancies have crept in undetected.
I'm not pointing at people, just showing how this was possible without being detected long before.
There are efforts to reduce bashism in simple shell scripts, but not all scriptlets are caught that way. In some areas this is more a tribulations bordering on exertion than a simple endevour.
- Yamaban. I have another problem with tcsh. If I am in a shell under bash and issue the tcsh command, it works as expected. If I change the default shell in /etc/passwd using the chsh command suggested, the shell is changed as a
On 03/03/15 11:23, Yamaban wrote: listing of /etc/passwd shows. But when I try and execute anything it says it does not know anything about display:0. This is a fatal mistake, for emacs and many other commands. I tried both /bin/tcsh and /usr/bin/tcsh. I have not tried to examine them but I assume they are the same thing? Any ideas? Is this a bug?
Not a bug per se, but simply the fact that the DISPLAY variable is not set or exported automatically into tcsh from profile script. There is some "magic" in /etc/profile{,.d/*,.local} that is wonky for (t)csh. Sorry, the system I'm sitting on ATM has no csh/tcsh intalled, so I cannot do testing on that. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/03/15 15:22, Yamaban wrote:
On Tue, 3 Mar 2015 22:57, don fisher <hdf3@...> wrote:
On 03/03/15 11:23, Yamaban wrote:
On Tue, 3 Mar 2015 18:33, don fisher <hdf3@...> wrote:
AFAIK there are some deeply ingrained bashisms and some other specific shell dependencies that simply do not work with csh/tcsh/ksh/pdksh, ash/sash/dash/bash are working, bash the best.
Some of this is historic in the depth of SUSE history, some of this is carelessness from the devs in younger times.
For a long time there was no Senior SLE dev member that used something other than bash as root-shell, and such discrepancies have crept in undetected.
I'm not pointing at people, just showing how this was possible without being detected long before.
There are efforts to reduce bashism in simple shell scripts, but not all scriptlets are caught that way. In some areas this is more a tribulations bordering on exertion than a simple endevour.
- Yamaban. I have another problem with tcsh. If I am in a shell under bash and issue the tcsh command, it works as expected. If I change the default shell in /etc/passwd using the chsh command suggested, the shell is changed as a listing of /etc/passwd shows. But when I try and execute anything it says it does not know anything about display:0. This is a fatal mistake, for emacs and many other commands. I tried both /bin/tcsh and /usr/bin/tcsh. I have not tried to examine them but I assume they are the same thing? Any ideas? Is this a bug?
Not a bug per se, but simply the fact that the DISPLAY variable is not set or exported automatically into tcsh from profile script.--
| Don Fisher hdf3@comcast.net | | 865 W. Cresta Loma Dr. VOICE: (520)888-7613 | | Tucson, AZ. 85704-3705 | -----------------------------------------------------------------
There is some "magic" in /etc/profile{,.d/*,.local} that is wonky for (t)csh.
Sorry, the system I'm sitting on ATM has no csh/tcsh intalled, so I cannot do testing on that.
- Yamaban.
Found an error message: invalid MIT-magic-cookie-1 keyxterm Xt error can't open display: :0 I did not know2 I had Kerberos enabled, if I do. Any ideas on how to pursue this one? Don -- ----------------------------------------------------------------- | Don Fisher hdf3@comcast.net | | 865 W. Cresta Loma Dr. VOICE: (520)888-7613 | | Tucson, AZ. 85704-3705 | ----------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 4 Mar 2015 00:40, don fisher <hdf3@...> wrote:
On 03/03/15 15:22, Yamaban wrote:
On Tue, 3 Mar 2015 22:57, don fisher <hdf3@...> wrote:
On 03/03/15 11:23, Yamaban wrote:
On Tue, 3 Mar 2015 18:33, don fisher <hdf3@...> wrote: [snip]
There is some "magic" in /etc/profile{,.d/*,.local} that is wonky for (t)csh.
Sorry, the system I'm sitting on ATM has no csh/tcsh intalled, so I cannot do testing on that.
- Yamaban. Found an error message: invalid MIT-magic-cookie-1 keyxterm Xt error can't open display: :0
I did not know2 I had Kerberos enabled, if I do. Any ideas on how to pursue this one?
what is the output of the "xhost" command in a termial? For the main user that should give something like: [output] access control enabled, only authorized clients can connect LOCAL: [/output] The relevant part is the "LOCAL:" line if not either add the "local" part, [code] xhost +local [/code] or disable all control [code] xhost + [/code] all that as the User that started the X11 session. Or it could be an environment problem. Compare the output of "printenv" between root with bash and root with tcsh. read the manpage of "su" and try to use "-m" That is the end of my knowledge, sorry. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/03/2015 01:23 PM, Yamaban wrote:
AFAIK there are some deeply ingrained bashisms and some other specific shell dependencies that simply do not work with csh/tcsh/ksh/pdksh, ash/sash/dash/bash are working, bash the best.
IIRC, you can specify bash be used in the script. In fact, I always start my scripts with #! /bin/sh, which links to bash. That was something I learned a long time ago. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
don fisher -
I.Petrov -
James Knott -
Michael Foerster -
Yamaban