OpenSUSE reinstall Yast

opensusepackage-management

I just can't understand what just happend?

I installed an openSUSE system, the original plan was to use it as an internal DNS Server for easyer access to all of the internal network computers. However something wasn't right with the dns server package, so I decided to remove it and install it again.

But after the removal something happened and the yast, yast2 and webyast were also removed and I find myself now locked inside out! :S

The Package Manager from the desktop is also screwed it returns an Failed to execute command package-manager --install %F error message.

How can i reinstall the yast, I was googling but I couldn't find any info regarding this issue? All that I find is bunch of tutorials of how to use Yast.

EDIT
I just forgot to add that using sudo zypper install yast2-gtk is also out of the option since zypper has also been somehow mysteriously removed from my system :@

Best Answer

I found a way to fix my system without reinstaling it.

Using the original installation image and performing and upgrade install fixed my system and after that zypper was installed again.

After that all I had to do was to reinstall the yast manager and the webyast service.

This way the job was done in an hour or so. If I was reinstalling again I would have lost days of reconfiguring the whole system.

Just for clarification of some things:
System: OpenSUSE 12.1
Desktop: Xfce

Related Solutions

Router – OpenSUSE 11 server as a router

Maybe you just need to enable IPv4-forwarding (routing) like this:

echo 1 > /proc/sys/net/ipv4/ip_forward

(default value is 0 there. I setup debian as a firewall 2 days ago and this helped ;))

EDIT

This script saves and deletes all entries in your iptables and sets up a basic configuration for masquerading from the inner network.

#!/bin/bash
# saving old iptables-configuration
iptables-save > /home/xxusernamexx/iptables-saved.out

# delete all existing rules and chains
iptables -F
iptables -t nat -F
iptables -X
iptables -Z
iptables -t nat -Z

# setting up masquerade
iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE

# forwarding for answer-packages from the internet
iptables -A FORWARD -i eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A FORWARD -o eth1 -j ACCEPT
iptables -A FORWARD -j LOG --log-ip-options --log-prefix fwd-drop
iptables -A FORWARD -j DROP

# allowing loopback and internal connections
# uncommend the following line if you want to allow ping from external
iptables -A INPUT -s 0.0.0.0/0 -p tcp --dport 80 -j ACCEPT # for your webserver
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT # edited
iptables -A INPUT -p icmp --icmp-type 8 -i eth1 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT
iptables -A INPUT -i eth0 -j ACCEPT # for connections from lan-nic
iptables -A INPUT -s 192.168.0.0/24 -j ACCEPT
iptables -A INPUT -i lo -j ACCEPT
iptables -A INPUT -j LOG --log-ip-options --log-prefix io-drop
iptables -A INPUT -j DROP

iptables -A OUTPUT -j ACCEPT # edited
iptables -A OUTPUT -p icmp --icmp-type 0 -o eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT
iptables -A OUTPUT -j LOG --log-ip-options --log-prefix io-drop
iptables -A OUTPUT -j DROP

# just to make sure that routing is enabled
echo 1 > /proc/sys/net/ipv4/ip_forward

Try this script. I can't really test it, because my eth1-eth0 interfaces are used the other way, but I wrote this script based on my own configuration. To be save, this script exports your actual iptables-configuration to your home-folder. It can be recovered using iptables-restore < filename

EDIT: added iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT and deleted -m state --state RELATED,ESTABLISHED in OUTPUT's first rule in order to allow the server to make own connections in every net (i.e. for query a DNS-server)

EDIT2: The problem is solved. There were a few misconfigured things:

iptables: We had to change the script a little bit to get it fully working (edited it in my answer as well).

DHCP: dhcpd was configured to use '192.168.0.1' as DNS-server. But the server didn't run a DNS-Server. We configured it to ISP-DNS-servers.

Router: The server was plugged in at the WAN-Port of the router. That brought the router to drop several packets from the clients to the server (and back). Aurel plugged it into a LAN-Port and it worked.

Debian: How to use “apt-get install” without upgrading dependencies

You can try the --nodeps flag with apt-get or you can try the debian package utility, dpkg, with the option --ignore-depends.

Best Answer

Related Solutions

Router – OpenSUSE 11 server as a router

Debian: How to use “apt-get install” without upgrading dependencies

Related Topic