Op 20-11-12 17:20, Patrick Shanahan schreef:
* Oddball <monkey9@iae.nl> [11-20-12 10:58]: ... well, headaches are not nice...
Indeed, but luckily for me i do not suffer often from them..
You say i should read manuals, and not come here, no-one has offered that. Reading the manuals is *part* of it, and coming here is *part* of it, but *only* coming here is "not it"!
Yes, read the manual, i will read more manuals, more..
but at the same time you argue about things beside the point. Hard not to following your discorse :^)
But where is agrument not to the point?
Well, keep on pushing the manual through my throat does not help my digestion..;-)
The reason for wanting to know the answer quicker was that i wanted to capture output, which was there, and i do not know how to reproduce. Next thing i want to know is how to reproduce the output... because i had to reboot due to very sluggish system.. and the output doesn't start by itself.. probably an easy command which i do not know yet... There were things about the firewall, and about wifi that i wanted to know, because there are issues with it. Doing it *all* an one time makes for confusion.
This is absolutely true...
Accomplish one task at a time and move to the next.
That would be nice, that there would be one thing at the time...( i sometimes secretly wish for that..)
Which also entails "following directions".
Yes. But sometimes many people give directions at the same time...
I ask things that i want to know to add some maybe, relevant output, to be able to investigate where the issue comes from, or something else that can be known through it. 122 is different from all predecessors. and 123 even more. as are *every* other distro and version, and that is how "it will be" in the future.
Yes, progress is not bad, only a lot of work, especially with too few people...
It might be helpfull to track some things 'before' they happen. We all know 123, or factory is a mess due to the changes to get systemd controlling things instead of sysv, iirc. no, not a *mess* but certainly different and a "learning experience".
Well, before things are sorted out, it is a mess..
I just heard suspend is broken on factory due to systemd, and networkmanager is not yet adapted fully, so it is still messy, but seems to start happening on my 122. Maybe it has nothing to do with it, maybe it has.
My autosuspend does not connect wifi on wake, manual sleep and wake works fine.
Again with the "grasping straws"... Doesn't help. Pointed arguments, statements, facts, experiences, ....
Yes, once i will get it... i promise myself this, and than i do..get it..
hyperbole
piechart. -- Have a nice day, Oddball. OS: Linux 3.7.0-rc6-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.9.3 "release 520" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org