On Wed 25 Mar 2015 23:59:43 NZDT +1300, Alexander Graf wrote:
> > And now I must be seeing things because it's working now, although I
> > tried several times before posting yesterday. Networking is working as
> > expected, even with a fixed MAC address (blast android). I saw the same
> > problem on an RPi with oS 13.2 and I could ping briefly after forcing
> > an address so it's not the cable.
>
> Oh, ok. All is well then I guess?
Well, *networking*, yes. Sorry about the noise there, I don't get it.
> Since Factory is supposed to be super-stable now, I think you'd be
> better of with it than 13.2 :).
All depends on if I want it to boot, I guess... ;-)
After a day of running it I'm not sure factory doesn't mean exactly what
it suggests: bleeding edge. Have the list:
No NTP (ok solved, but it's not "stable release").
Different packages install the same files, different content [1].
I wanted yast-x11, because yast-ncurses is, uhm, for emergencies. Disk
space is cheap:
zypper in yast2-x11 yast2-control-center-qt libyui-qt6 xauth
Result:
None of the text input fields in any of the yast modules accept
keyboard input. No reaction to such.
yast-ncurses now runs dooog-sloooowwww, just by installing (but not
running) yast-x11.
The ncurses and x11 versiosn don't behave the same. The x11 one shows
a long list of autoinstall packages. Irritating.
Thanks for all your help,
Volker
[1]
Checking for file conflicts: ...............................[error]
Detected 2 file conflicts:
File /usr/share/locale-bundle/ar/LC_MESSAGES/libpwquality.mo
from install of
bundle-lang-common-ar-13.2-7.2.noarch(openSUSE-Factory-repo-oss)
conflicts with file from install of
bundle-lang-gnome-ar-12.3-8.1.noarch(openSUSE-Factory-repo-oss)
File /usr/share/locale-bundle/ar/LC_MESSAGES/system-config-printer.mo
from install of
bundle-lang-common-ar-13.2-7.2.noarch(openSUSE-Factory-repo-oss)
conflicts with file from install of
bundle-lang-gnome-ar-12.3-8.1.noarch(openSUSE-Factory-repo-oss)
--
Volker Kuhlmann
http://volker.top.geek.nz/ Please do not CC list postings to me.
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
