Reduced number of config options in YaST command line?

Hi all,

I am using openSUSE 12.2 on a headless computer. Therefore, I am doing everything over ssh and in command line because I don’t have a graphical interface loaded.
When I call YaST using the command yast or yast2 (I didn’t notice any difference between the two?), I am presented with this:
http://i.imgur.com/3QIQw.png](http://imgur.com/3QIQw)

This seems to be lacking a lot of options (firewall config, most notably) over the graphical version of YaST.

Should I install something more to enable these missing options? Did I miss something?

Thanks for your help,

Hi
Have you got a local X server running, then ssh with the -X option…

Else install Nx, you can still have the server starting at runlevel 3,
but Nx will kick in a server for you to run a GUI desktop.


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.2 (x86_64) Kernel 3.4.6-2.10-desktop
up 5:36, 2 users, load average: 0.00, 0.06, 0.11
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

I do a lot through ssh, I’m seeing a lot more yast modules. Looks like you’re missing things. Maybe this output helps you


rpm -qa | grep yast2

yast2-sudo-2.22.0-2.1.2.noarch
yast2-trans-hu-2.22.0-8.7.1.noarch
yast2-pkg-bindings-2.22.2-2.1.3.x86_64
yast2-sysconfig-2.22.0-2.1.2.noarch
yast2-nfs-common-2.21.4-1.1.1.noarch
yast2-packager-2.22.6-2.1.2.x86_64
yast2-samba-client-2.22.2-2.1.2.noarch
yast2-users-2.22.4-2.1.3.x86_64
yast2-inetd-2.21.1-5.1.2.noarch
yast2-trans-en_US-2.22.0-8.7.1.noarch
yast2-dbus-client-2.22.0-2.1.3.x86_64
yast2-slp-2.22.0-2.1.3.x86_64
yast2-theme-openSUSE-Oxygen-2.21.18-5.1.1.noarch
yast2-tv-2.21.4-5.1.3.noarch
autoyast2-installation-2.22.6-1.4.1.noarch
yast2-tune-2.22.0-2.1.3.x86_64
yast2-libyui-2.21.4-2.1.2.x86_64
yast2-trans-ru-2.22.0-8.7.1.noarch
yast2-proxy-2.22.1-2.1.1.noarch
yast2-kerberos-client-2.22.2-2.1.2.noarch
yast2-add-on-2.22.0-2.1.1.noarch
yast2-trans-pl-2.22.0-8.7.1.noarch
yast2-ycp-ui-bindings-2.21.4-1.1.2.x86_64
yast2-storage-2.22.10-1.1.1.x86_64
yast2-qt-graph-2.19.0-10.1.2.x86_64
yast2-installation-2.22.10-1.1.4.noarch
yast2-update-2.22.3-1.1.1.x86_64
yast2-trans-en_GB-2.22.0-8.7.1.noarch
yast2-qt-2.22.6-2.1.2.x86_64
yast2-qt-pkg-2.21.26-1.1.2.x86_64
yast2-trans-nl-2.22.0-8.7.1.noarch
yast2-scanner-2.23.0-2.1.2.x86_64
yast2-security-2.22.5-2.1.2.noarch
yast2-gtk-2.22.5-2.2.3.x86_64
yast2-core-2.23.4-1.1.3.x86_64
yast2-restore-2.21.2-5.1.1.noarch
yast2-trans-cs-2.22.0-8.7.1.noarch
yast2-trans-zh_CN-2.22.0-8.7.1.noarch
yast2-transfer-2.22.0-2.1.3.x86_64
yast2-printer-2.23.1-2.1.3.x86_64
yast2-fingerprint-reader-2.22.3-2.1.3.x86_64
patterns-openSUSE-yast2_install_wf-12.2-5.5.1.x86_64
yast2-trans-ja-2.22.0-8.7.1.noarch
yast2-nfs-client-2.21.6-1.1.1.noarch
yast2-metapackage-handler-0.8.14-5.1.2.noarch
yast2-qt-branding-openSUSE-12.2-11.7.3.noarch
yast2-trans-fr-2.22.0-8.7.1.noarch
yast2-runlevel-2.21.3-5.1.2.noarch
yast2-perl-bindings-2.19.2-1.1.2.x86_64
yast2-nis-client-2.22.2-2.1.3.x86_64
yast2-backup-2.22.2-2.1.1.noarch
yast2-trans-sv-2.22.0-8.7.1.noarch
yast2-http-server-2.22.0-2.1.2.noarch
yast2-pam-2.22.1-2.1.1.noarch
yast2-sshd-2.22.0-2.1.1.noarch
yast2-control-center-2.22.2-2.1.2.x86_64
patterns-openSUSE-yast2_basis-12.2-5.5.1.x86_64
yast2-country-data-2.22.6-2.1.2.x86_64
yast2-trans-pt_BR-2.22.0-8.7.1.noarch
yast2-mouse-2.21.0-5.1.1.x86_64
yast2-iscsi-client-2.22.1-2.1.2.noarch
yast2-trans-es-2.22.0-8.7.1.noarch
yast2-hardware-detection-2.22.0-2.1.4.x86_64
yast2-control-center-gnome-2.21.3-2.1.3.x86_64
yast2-firewall-2.21.2-3.1.2.noarch
yast2-samba-server-2.22.3-2.1.1.noarch
yast2-trans-de-2.22.0-8.7.1.noarch
yast2-ntp-client-2.21.2-2.2.1.noarch
yast2-online-update-2.22.2-2.1.2.noarch
yast2-trans-pt-2.22.0-8.7.1.noarch
yast2-ldap-2.22.2-2.1.3.x86_64
yast2-ncurses-2.22.4-1.1.2.x86_64
yast2-country-2.22.6-2.1.2.x86_64
yast2-x11-2.22.1-2.1.2.x86_64
yast2-trans-it-2.22.0-8.7.1.noarch
yast2-vm-2.22.1-2.1.2.x86_64
yast2-control-center-qt-2.22.2-2.1.2.x86_64
yast2-ldap-client-2.22.8-2.1.2.noarch
yast2-mail-2.21.1-7.1.2.noarch
yast2-trans-da-2.22.0-8.7.1.noarch
yast2-trans-zh_TW-2.22.0-8.7.1.noarch
yast2-xml-2.16.1-69.1.3.x86_64
yast2-theme-openSUSE-2.21.18-5.1.1.noarch
yast2-sound-2.22.1-2.1.3.x86_64
yast2-network-2.24.3-1.1.1.x86_64
yast2-online-update-frontend-2.22.2-2.1.2.noarch
yast2-packager-webpin-2.22.6-2.1.2.x86_64
yast2-branding-openSUSE-2.18.0-17.1.1.noarch
yast2-trans-stats-2.19.0-10.1.2.noarch
yast2-ncurses-pkg-2.22.7-2.1.2.x86_64
yast2-2.23.3-1.2.1.x86_64
yast2-irda-2.22.0-2.1.1.noarch
yast2-bootloader-2.23.7-1.1.1.x86_64

On 2012-09-25 20:56, ShaolinSatellite wrote:
>
> Hi all,
>
> I am using openSUSE 12.2 on a headless computer. Therefore, I am doing
> everything over ssh and in command line because I don’t have a graphical
> interface loaded.

You don’t need a graphical interface loaded in order to run yast, or any X program, over ssh on
another computer. It is the other computer which must have a graphical interface running.
Remember that X is a client-server implementation.

However, the server machine will need some graphical libraries.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

This machine can accomplish all it should only from command line thus I’d rather avoid having any graphical interface installed/running at all because I don’t need it and it will hog valuable resources.

On 2012-09-26 00:26, ShaolinSatellite wrote:

> This machine can accomplish all it should only from command line thus
> I’d rather avoid having any graphical interface installed/running at all
> because I don’t need it and it will hog valuable resources.

Wrong.

I repeat, you do not need to have any graphical interface in order to run a graphical tool from
another computer via ssh.

Learn Linux first.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

That is why I am here, I never said I was a Linux expert rotfl!

On 09/26/2012 03:16 AM, ShaolinSatellite wrote:
>
> That is why I am here, I never said I was a Linux expert rotfl!

-=WELCOME=- poster who has been here only 12 days!!

me neither (i’m not an expert–learn something EVERY day since i started
in Linux ~'98)]

you can also run yast in the non-graphical environment and use it to
INSTALL the missing modules (which will also run in the non-GUI
environment)…

Knurpth (kindly) supplied you with a list in an above post, which you
can also see (and install) in your non-GUI yast by using its Software
Management module,

well…maybe you don’t know how to navigate in non-GUI yast??
try:
yast will open as you showed in your referenced image, just press Tab
once and the focus will switch to the right and land on Software
Management!! then press Enter…

then the whole thing will change to the Software Management Module
where you can search on the term ‘yast’, which will produce a LONG list
and you can scroll down and find one that might mention Firewall (or
whatever else you miss)…

WAIT, i bet you are not missing the Firewall module, just have not
found how to access it yet!! (maybe)

when yast opens (and Software is highlighted on the left) just use the
down arrow key to get to “Security and Users” and then press Tab and you
will switch focus to the right pane where you select any of the modules
there (on mine there is a “Firewall” module, if you have one too just
Tab to it and press Enter–and do what you wanna do to your
firewall…note: the default is relatively secure.)

so short: navigate inside the non-GUI yast with Tab and Arrows,
initiate/execute your choices with Enter…if you get into trouble Tab
your way to somewhere else (like maybe to [Cancel] or [Back]) and start
over, or press F9 to close yast abruptly—highly recommend you NOT do
that if software download is in progress…

and DO NOT overlook the possibility to Tab to [Help] to learn a lot more…

is that helpful?

if not, ask more (after reading Help)


dd http://goo.gl/PUjnL
http://tinyurl.com/DD-Caveat

On 2012-09-26 03:16, ShaolinSatellite wrote:
>
> robin_listas;2490563 Wrote:
>> On 2012-09-26 00:26, ShaolinSatellite wrote:
>> Learn Linux first.
>
> That is why I am here, I never said I was a Linux expert rotfl!

Then please believe us when we say that you can run yast graphically because the graphical
environment is in the machine you sit at, using ssh. The server doesn’t need to have a
graphical environment running, not even installed.

You only need the libraries that yast (gtk or kde) needs. Not xorg.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Thank you that was very helpful.
The firewall module was indeed missing, I installed it now using the method you suggested.

On 09/26/2012 04:16 PM, ShaolinSatellite wrote:
> The firewall module was indeed missing

to me that sound very strange! is it a custom iso that you installed
from? or let me ask a different way:

A. if you downloaded an .iso from http://software.opensuse.org/ and
used it to install from then you either:

  1. elected during install to not have the firewall installed
    or
  2. installed from corrupt install media
    or
  3. had errors during install which you elected to ignore
    or
  4. somehow damaged your system after install (removing that yast module,
    which is auto-installed if the firewall is installed

so, i think you REALLY need to wonder if you have a solid system, or a
corrupt system, and you need to go back and check the validity of that
iso http://en.opensuse.org/SDB:Download_help#Checksums and
also boot from the install disk and run its self check by running “Check
Installation Media” like you see here
https://www.dropbox.com/s/j17hraoljbw72nr/01_bootsplash.jpg

B. if you didn’t download from http://software.opensuse.org/ then you
need to wonder who you got it from, and if you got a safe copy, or not.

bottom line is: i would not consider your system secure until you know
why that module was missing. [as far as i know it has been auto-included
on every SuSE/SUSE/openSUSE system i’ve had since 9.x]

others here may have had another experience, and i’ll let them tell you
how you can have a secure system without having that module installed by
default.


dd http://tinyurl.com/DD-Caveat