YAST SLOW.. and not all its cracked up to be..

fieldyweb · 03-02-2006, 11:25 PM

OK, i have just moved from Fedora C4 via Mandrake 10 to Suse10 and i must say, for all the HYPR i have read about this YAST, i think it is possibly one of the worst package managers i have come accross, and i thought YUM was bad...

Add Software repository....

Click on software package..

Wait (the userinterface is so poorly designed that there is no activity bar so i don't actually know if it is doing ANYTHING)

Wait

Wait

Out of 15 different repoitories i have tried 2 can actually work.. and both were for the KDE 3.5.1 update...

I'm sorry guys, but if this is the answer, someone should rewrite the question..

does this software need a special port open on the firewall? because if i actually use Firefox to navagate to the repositories it does so faster than light.. so its not the internet connection...

What am i missing? what am i doing wrong?

fieldyweb · 03-03-2006, 04:54 AM

Havbing spent all day using this with no effect, i diteched Suse for Ubbuntu, and had a similar isse with apt get.. and guess what..

/etc/resolv.conf

for some strange reason (which i have never had before)

if i put the DNS of the router in /etc/resolv.conf

nameserver <router DNS IP>

it works fine..

The DHCLIENT seemts to overwrite this at will.. so i put the line in with the existing

nameserver 192.168.1.1

And it all seems to be fine..

Why do i not have to do this on Mandrake or FC4?

comptiger5000 · 03-03-2006, 06:39 AM

you have to create it if it wasn't automatically. FC4 has the ability to edit/create that through the network config in X

fieldyweb · 03-03-2006, 08:36 AM

Quote:

you have to create it if it wasn't automatically

Sorry, what?

I'm using Ubuntu now, and the file /etc/resolv.conf exsists, and if i change it to reflect the routers dns, it overwrites the file and refers it back to NAMESERVER=192.168.1.1

How do i stop this?

mazinoz · 03-17-2006, 12:57 AM

What is the routers DNS? Do you have DHCP or static IP addresses?

fieldyweb · 03-17-2006, 03:10 AM

If i had setup the above file with the line

dns-nameservers 203.144.207.29

Because taht is how i solve the problem in Ubuntu...

basically the router was issuning 127.0.0.1 as a dns server, which it isn't... added this line uner the wireless settings (which i use as default) and the problem was resolved (excuse the pun)