On Tue, Mar 12, 2013 at 7:34 AM, Basil Chupin
On 12/03/13 15:50, Felix Miata wrote:
Those init commands are aliases for systemd commands to perform the closest equivalent sysvinit function. It's the long-winded command strings and filenames used by systemd generally that make understanding and using it complicated and tough to learn. The aliases are welcome, but do nothing to solve systemd's wordy design.
If you look hard enough, you can find oddities everywhere. Systemd works so much better on modern hardware. I cannot imagine downgrading on anything I'm running Linux on. 12 extra letters (which you don't have to type anyway since the alias is there) is nothing in the bazillion keystrokes I seem to do every day - and the argument about remembering commands, all I can say is LOL. Linux is the god of obscure and cyptic commands. This is nothing new. :-P
A question: can grub boot into uefi setups which are now, or about to be, all the rage?
It can't handle any UEFI system I've got. I have to use Grub2. Grub is dead in the water if you're using current/new hardware (in any testing I've done). While yes, Grub2 was a pig to use initially, a lot has been done to make it seamless for install and use. Adding new entries (if you even really need to) is actually easier now with Grub2 (for me) than it ever was with Grub.
I don't see this here as I am using KDE 4.10.1, but perhaps I am not understanding what the problem described is all about - especially since nobody commented to your bug report back in April 2012.
This one was an issue in really old versions of KDE4. It hasn't been around for a long time on any system I use. If it still exists on any machine using current released of KDE4, I'd venture to say it's caused by some leftover cruft from using old releases of KDE. C. -- openSUSE 12.2 x86_64, KDE 4.10.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org