It’s been a long time since I had a working OpenSuSE system. But if I can get wicd talking to my hidden wpa2-psk network via my usb wireless adaptor {the built-in wireless has never worked} Which is usualy detected as wlan1 Then I’m going to want as current an E17 as is possible using the repositories, And E16 {and maybe icewm} as backup gui environments {since e17 is still under development and is NOT quite stable} I do use a few kde applications such as yakuake, konsole, & kaffeine. But I would like to know how to unclutter my system from the rest of it. Will I need to simply remove kde completely (after installing e17 of course) And the selectively add the applicatyions like yakuake, konsole, & kaffeine back in and let them pull in what parts of kde they need???
And about E17 on opensuse… most of what I can find is OLD info except for a reference to
Well I finally got near my computer again… Actually I’m not sure all the questions below belong in this subforum. But if so just tell me where I should post them… thanks!
I need to replace “network manager” with wicd. Unfortunately according to zypper the default repos don’t include wicd. What repo do I need to add to get it???
I don’t remember how to add repos anymore. Is there a good easy to understand up to date how-to for doing so?? *(Preferably from the command line…) *I suppose I could try “man zypper” But I’ve never found it easy to understand “man” documents…
I’m not sure if this is the best repo for E17 either.
Is adding the:
I need to ditch most of kde. I don’t mind keeping whatever parts of it are needed for the few kde apps I intend to go on using. But it’s got way too much of my harddrive space for a user interface I can’t stand.
I’m thinking that I should get E17 running, then perhaps I need to remove kde. And then add back in the apps that I want along with whatever dependencies the package manager thinks I need.
Is that a reasonable plan? Could the removal of kde part of the above be as simple as:
zypper rm kde
Or is there perhaps a little more to it??
I don’t know if it’s a kde thing or just the way OpenSuSE works. But While I don’t mind basic screen blanking after a minimum of 1/2 hour of apperarnt inactivity, and/or passwork verification if I do something like close the lid on my laptop. I absolutely can NOT stand any kind of autosuspend or whatever it is that happens on the new OpenSuSE 12.2 install uppon a few minutes of inactivity. IE the screen suddenly goes dark. Once it does, neither touching the mouse nor keyboard can restore the screen for a while. It’s like it’s busy saving everything to the swap partition with a negative nice priority. Then after an extended time the power button goes dark though the front power-on indicator light stays on. At that point a light toch on the dark power buton will restore the system where it left off. But it takes as long as it does to boot kde in the first place… ARRRGHGH!
How do I totally disable “suspend” operations?
I’m not yet sure if it was a fluke, But I got so buggered by the above “suppending wiout warning” Thaat I rebooted using the “3” kernal option. Unfortunately when I tried to do an :
zypper se wicd;/CODE]
I got a lot of repeating garbage about not being able to resolve the url of some repo... I know the laptop was connected via an Ethernet cable to the same router the desktop I'm typing this on is connected to and the internet WAS working... Is the default network manager dependent on X somehow???
7) I do frequently work from the virtual consoles. But the current default console fonts are awful small.
With antiX Linux I could fix the with the debian command:
dpkg-reconfigure console-setup
But I can't find an equivalent command in OpenSuSE...
I can temporarily fix it for the currently in use console with:
setfont suse12x22
But how can I set it permanently for all 6 tty console screens??
8) According to the boot screen f1 help text, the kernel option splash=0 should prevent the splash from being used at all... I know the green openSuSE logo screen is cute and all. But I feel more comfortable when I can see the boot text messages. I want to know if one of them ended in
Thanks for the suggestion vatsers, But I’m not ready to give up on the OpenSuSE 12.2 I’ve already got installed just yet. Besides I’ve never used a “torrent”. I’m not sure how to configure my system to get it working? And would I need to reduce my routers firewall security settings?
But If I can figure out the torrent stuff, then I might try it the next time I bork one of my linux installations.
Speaking of the currently installed OpenSuSE 12.2:
I’ve been working on the concerns I asked about. Some of them I’ve found a solution or workaround for…
It looks like wicd needs a patch or some such for OpenSuSE 12.2 {no wonder I couldn’t find it in the repos} But I guess it wasn’t so much that I needed wicd, as that I needed to ditch “network manager”. And I found a solution in yast that allowed me to turn off “network manager” and use traditional “ifup” methods. It seems once NM is outa the way, yast is very able to use my usb wireless adapter…
I tripped over an example of how I did it with my last OpenSuSE installation in an old e-mail… It’s actually a lot easier than the description in “man zypper” make it seem…
Well it worked. Though for some reason it doesn’t appear able to create a personal application launcher. And it can’t convert *.jpg or *.png images to *.edj files for use as custom background images…
But that might be do to the inherently instabilities of using a DE/WM that’s still under development…
Actually it looks like OpenSuSE 12.2 installed less of kde than I thought… It looks like all I really need to ditch is pulseaudio…
Looks like all I needed to do was to remove the grub kernel option specifying where to resume from…
I figured out a hackish workaround… I put this in my /etc/profile:
if $DISPLAY ="" ]
then
setfont suse12x22
fi
Which fixes the font in whatever tty I login to… Though I’d welcome a cleaner solution.
I’m thinking my problem was that OpenSuSE’s grub menu, offered an “easy” kernel option input line for temporary cheat codes like the one on the live-cd’s boot menu… Once I edited the actual menu.lst entry to say: “splash=0” there, it worked…