[opensuse] Suse 12.2 battles and victories
OK, I gave up on Windows and assumed that I could get my laptop running with Suse. At first I had really big network trouble. I could get it connected, but every time I rebooted it wouldn't connect and wouldn't show me my wireless router until I deleted the connection and rebooted again. Then I tried Ubuntu; what a huge mistake. It worked great with the network, but it's an incredible PITA with loading software and security is a disaster; any user can su with their own password. I was looking for a solution where my girlfriend couldn't add things she didn't understand where harmful, and there is no good reason she should know. So, I went back to Suse and after getting the network up again, I went through the enormous online update. That fixed the network disconnection problem!!! Next I had used a Samba mount to save my M$ files to my desktop. I couldn't get Samba running from either Ubuntu or Suse as client, and NFS turned out to be a huge time investment. I remember the days when I just typed in the server and client information and it just worked. After quite a few hours I hit on the right combination and that is working just fine too. Now I just need a reliable way to kill the Synaptics touchpad; it doesn't stay off when switching users or timing out to a login screen. I wish there was an easy way to have it turn itself off when a USB mouse is plugged in. For now I'll just make a couple of scripts and put them into the screen menu so my g/f can remember how to turn it off. The webcam works right out of the box too, so life is now good. As long as I have one box, my desktop, that can dual boot M$, then I can update any hardware devices that are only supported by M$ applications. I'm a very happy camper. Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hey Jim, Not sure if Opensuse has synclient as I now use centos but this should work. synclient TouchpadOff=1 (disables the touchpad) Should be put in either the .bash_profile or in the .bashrc file. Phil On 10/23/2012 11:51 PM, Jim Sabatke wrote:
OK, I gave up on Windows and assumed that I could get my laptop running with Suse. At first I had really big network trouble. I could get it connected, but every time I rebooted it wouldn't connect and wouldn't show me my wireless router until I deleted the connection and rebooted again. Then I tried Ubuntu; what a huge mistake. It worked great with the network, but it's an incredible PITA with loading software and security is a disaster; any user can su with their own password. I was looking for a solution where my girlfriend couldn't add things she didn't understand where harmful, and there is no good reason she should know. So, I went back to Suse and after getting the network up again, I went through the enormous online update. That fixed the network disconnection problem!!!
Next I had used a Samba mount to save my M$ files to my desktop. I couldn't get Samba running from either Ubuntu or Suse as client, and NFS turned out to be a huge time investment. I remember the days when I just typed in the server and client information and it just worked. After quite a few hours I hit on the right combination and that is working just fine too.
Now I just need a reliable way to kill the Synaptics touchpad; it doesn't stay off when switching users or timing out to a login screen. I wish there was an easy way to have it turn itself off when a USB mouse is plugged in. For now I'll just make a couple of scripts and put them into the screen menu so my g/f can remember how to turn it off.
The webcam works right out of the box too, so life is now good.
As long as I have one box, my desktop, that can dual boot M$, then I can update any hardware devices that are only supported by M$ applications.
I'm a very happy camper.
Jim
-- Carpe Aptenodytes! (Seize the Penguins!) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
It would appear that on Oct 23, Jim Sabatke did say: -> Then I tried Ubuntu; what a huge mistake. It worked great with the network, -> but it's an incredible PITA with loading software and security is a disaster; -> any user can su with their own password. I was looking for a solution where -> my girlfriend couldn't add things she didn't understand where harmful, and -> there is no good reason she should know. Don't get me wrong Jim, you made the right decision when you picked OpenSuSE over Ubuntu... But the "any user can su with own password" issue is easily resolved by editing the /etc/sudoers config file (with visudo) you can stop the own password garbage by first creating a root password. (Which on Ubuntu is done: $ sudo passwd root Then editing the /etc/suduers to include the tag "targetpw" on the "defaults" line. After which you need to know the root passwd to do root stuff. -> Now I just need a reliable way to kill the Synaptics touchpad; it doesn't stay -> off when switching users or timing out to a login screen. I wish there was an -> easy way to have it turn itself off when a USB mouse is plugged in. For now -> I'll just make a couple of scripts and put them into the screen menu so my g/f -> can remember how to turn it off. It would appear that on Oct 24, Phil Savoie did say:
Hey Jim,
Not sure if Opensuse has synclient as I now use centos but this should work.
synclient TouchpadOff=1 (disables the touchpad)
Should be put in either the .bash_profile or in the .bashrc file.
Yes Phil it's in there, I use it every day. But putting it in those files only works if you use a display manager to login. If you log in on a virtual console (tty) in runlevel3 the command will fail (needs X) Since I use startx to start the GUI (when I'm ready for it) I get better results putting my synclient command in ~/.xinitrc instead... -- | --- ___ | <0> <-> | ^ JtWdyP | ~\___/~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-10-24 08:43, JtWdyP wrote:
It would appear that on Oct 23, Jim Sabatke did say:
over Ubuntu... But the "any user can su with own password" issue is easily resolved by editing the /etc/sudoers config file (with visudo) you can stop the own password garbage by first creating a root password. (Which on Ubuntu is done:
I think there is another method that the user has to belong to a certain group to be able to su to root. Wheel or root group, perhaps. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCH04oACgkQIvFNjefEBxqM7wCbBQrbrJkoLd4OTwg0eaTEjGTc kO0An0kDKpsT50r3Mtdn5YT4ZEGPbEdi =LC8P -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. said the following on 10/24/2012 07:39 AM:
I think there is another method that the user has to belong to a certain group to be able to su to root. Wheel or root group, perhaps.
Carlos has a point here. SU and SUDO are differnt. If the problem is with SU and not SUDO then the issue may be in how PAM is configured. see 'man pam wheel' and have a look at the contents of /etc/pam.d/su You should see lines like auth sufficient pam_rootok.so # Uncomment the following line to implicitly trust users in the "wheel" group. #auth sufficient pam_wheel.so trust use_uid # Uncomment the following line to require a user to be in the "wheel" group. #auth required pam_wheel.so use_uid The 'wheel group' is an old UNIX concept: http://unix.stackexchange.com/questions/1262/where-did-the-wheel-group-get-i... - -- In the fight between you and the world, back the world. Frank Zappa -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iOgEAQECAAYFAlCH7YkACgkQGa6akpZ3YCn6fgZeOZHp+AslfcyrpA6HcCG+9JJi 9OrH5mUDx4aD//9Sz3V0lLaKLGU3frnCEJKQjN619Uul0ry5O+6n0hyz+AWvrkGt To12Nvg2/Cy2EB5gc2VQ+lqzevSZYztBLrgHoUa220ALmt0HCXdiXSooy+5yNGE6 41aYztF2M4k9HZVVC9cVbFmSlKfBpc1pcKlHxxtmuKXSVtyUDBpUSkOevaQiGDyz HWtaXgMAg/gF7Yqt06EUqs/0SLDHG6dyghKFvRUIL9eckoAQIWkgSU5C =46yf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
It would appear that on Oct 24, Carlos E. R. did say:
On 2012-10-24 08:43, JtWdyP wrote:
over Ubuntu... But the "any user can su with own password" issue is easily resolved by editing the /etc/sudoers config file (with visudo) you can stop the own password garbage by first creating a root password. <snip> then adding targetpw flag to sudoers defaults.
I think there is another method that the user has to belong to a certain group to be able to su to root. Wheel or root group, perhaps.
Yes If you want to get into properly configuring sudo it's very possible to give permissions based on membership in any valid group, or even by specific username. # Uncomment to allow people in group wheel to run all commands %wheel ALL=(ALL) ALL # Same thing without a password # Never on MY system... #%wheel ALL=(ALL) NOPASSWD: ALL # If ctrl+alt+del can reboot then might as well %wheel ALL=NOPASSWD: /sbin/poweroff All of which I'd be inclined to do, even on a system Like OpenSuSE... But it was *buntu that forced me to learn how... But while *buntu is somewhat better than Microsoft, OpenSuSE is much better! -- JtWdyP -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
It would appear that on Oct 23, Jim Sabatke did say:
-> Then I tried Ubuntu; what a huge mistake. It worked great with the network, -> but it's an incredible PITA with loading software and security is a disaster; -> any user can su with their own password. I was looking for a solution where -> my girlfriend couldn't add things she didn't understand where harmful, and -> there is no good reason she should know.
Don't get me wrong Jim, you made the right decision when you picked OpenSuSE over Ubuntu... But the "any user can su with own password" issue is easily resolved by editing the /etc/sudoers config file (with visudo) you can stop the own password garbage by first creating a root password. (Which on Ubuntu is done:
$ sudo passwd root <snip> I actually spent quite a bit of time looking that issue up, and everything I read on Ubuntu support sites talked pretty loudly about how
On 10/24/2012 01:43 AM, JtWdyP wrote: they made a conscious decision to let everyone "sudo". I'm sure you have more accurate information, but with the other Ubuntu problems, including getting NFS to work, I just didn't want much more to do with it. They make it very easy to have a Windows like machine that is comfortable for the users, but I was not happy with the circles I had to run in to get software. It was probably just being a Suse user for over 20 years, but I have grown to know what to expect from Suse and I have a pretty good idea of how to get software and help. Thanks, Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I've been putting xinput disable 12 (the number for the touchpad service) into .xinitrc. That works fine, except when the screen times out and you type a password to get back, or when switching users and come back. Then I have to run it manually from a terminal. Is there a more appropriate place to put it? Sorry for top posting, but I respond in the OP's method (and I don't hate top posting on simple messages like most people here do, please don't flame me). Jim On 10/24/2012 12:38 AM, Phil Savoie wrote:
Hey Jim,
Not sure if Opensuse has synclient as I now use centos but this should work.
synclient TouchpadOff=1 (disables the touchpad)
Should be put in either the .bash_profile or in the .bashrc file.
Phil
On 10/23/2012 11:51 PM, Jim Sabatke wrote:
OK, I gave up on Windows and assumed that I could get my laptop running with Suse. At first I had really big network trouble. I could get it connected, but every time I rebooted it wouldn't connect and wouldn't show me my wireless router until I deleted the connection and rebooted again. Then I tried Ubuntu; what a huge mistake. It worked great with the network, but it's an incredible PITA with loading software and security is a disaster; any user can su with their own password. I was looking for a solution where my girlfriend couldn't add things she didn't understand where harmful, and there is no good reason she should know. So, I went back to Suse and after getting the network up again, I went through the enormous online update. That fixed the network disconnection problem!!!
Next I had used a Samba mount to save my M$ files to my desktop. I couldn't get Samba running from either Ubuntu or Suse as client, and NFS turned out to be a huge time investment. I remember the days when I just typed in the server and client information and it just worked. After quite a few hours I hit on the right combination and that is working just fine too.
Now I just need a reliable way to kill the Synaptics touchpad; it doesn't stay off when switching users or timing out to a login screen. I wish there was an easy way to have it turn itself off when a USB mouse is plugged in. For now I'll just make a couple of scripts and put them into the screen menu so my g/f can remember how to turn it off.
The webcam works right out of the box too, so life is now good.
As long as I have one box, my desktop, that can dual boot M$, then I can update any hardware devices that are only supported by M$ applications.
I'm a very happy camper.
Jim
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Sorry, I sent this to Phil. I noticed the mistake while sending. Yes, OpenSuse has synclient and I have used it along with xinput. Either way seems to work the same. Putting the commands in .x in .bashrc and .xinitrc works in some cases, but not all. For example, if I close the cover and open it, the touch pad is active again and I have to manually type in the command. Am I missing a place to put the command? I don't mind putting it multiple places, but I am running out of ideas. Is there a truly global place to place it? Thanks, Jim On 10/24/2012 12:38 AM, Phil Savoie wrote:
Hey Jim,
Not sure if Opensuse has synclient as I now use centos but this should work.
synclient TouchpadOff=1 (disables the touchpad)
Should be put in either the .bash_profile or in the .bashrc file.
Phil
On 10/23/2012 11:51 PM, Jim Sabatke wrote:
OK, I gave up on Windows and assumed that I could get my laptop running with Suse. At first I had really big network trouble. I could get it connected, but every time I rebooted it wouldn't connect and wouldn't show me my wireless router until I deleted the connection and rebooted again. Then I tried Ubuntu; what a huge mistake. It worked great with the network, but it's an incredible PITA with loading software and security is a disaster; any user can su with their own password. I was looking for a solution where my girlfriend couldn't add things she didn't understand where harmful, and there is no good reason she should know. So, I went back to Suse and after getting the network up again, I went through the enormous online update. That fixed the network disconnection problem!!!
Next I had used a Samba mount to save my M$ files to my desktop. I couldn't get Samba running from either Ubuntu or Suse as client, and NFS turned out to be a huge time investment. I remember the days when I just typed in the server and client information and it just worked. After quite a few hours I hit on the right combination and that is working just fine too.
Now I just need a reliable way to kill the Synaptics touchpad; it doesn't stay off when switching users or timing out to a login screen. I wish there was an easy way to have it turn itself off when a USB mouse is plugged in. For now I'll just make a couple of scripts and put them into the screen menu so my g/f can remember how to turn it off.
The webcam works right out of the box too, so life is now good.
As long as I have one box, my desktop, that can dual boot M$, then I can update any hardware devices that are only supported by M$ applications.
I'm a very happy camper.
Jim
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 2012-10-23 at 22:51 -0500, Jim Sabatke wrote:
OK, I gave up on Windows and assumed that I could get my laptop running with Suse.
It is openSUSE, not Suse. They are not the same thing.
know. So, I went back to Suse and after getting the network up again, I went through the enormous online update. That fixed the network disconnection problem!!!
This is common. Install, then update; always.
Next I had used a Samba mount to save my M$ files to my desktop. I couldn't get Samba running from either Ubuntu or Suse as client, and NFS turned out to be a huge time investment. I remember the days when I just typed in the server and client information and it just worked. After quite a few hours I hit on the right combination and that is working just fine too.
It does just work, what was specifically the issue? In nautilus I go to smb://username@hostname/sharename, and it 'just works'.
The webcam works right out of the box too, so life is now good.
You've got one up on me. My webcam doesn't do anything - although to be fair I've made no attempt at making it work. Running Cheese is the one way I can throw gnome-shell into a tail-spin. I don't even see a candidate device in lspci or lsusb.
I'm a very happy camper.
Same here. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/24/2012 07:36 AM, Adam Tauno Williams wrote:
On Tue, 2012-10-23 at 22:51 -0500, Jim Sabatke wrote:
OK, I gave up on Windows and assumed that I could get my laptop running with Suse. It is openSUSE, not Suse. They are not the same thing.
Yes, you are right.
know. So, I went back to Suse and after getting the network up again, I went through the enormous online update. That fixed the network disconnection problem!!! This is common. Install, then update; always.
Next I had used a Samba mount to save my M$ files to my desktop. I couldn't get Samba running from either Ubuntu or Suse as client, and NFS turned out to be a huge time investment. I remember the days when I just typed in the server and client information and it just worked. After quite a few hours I hit on the right combination and that is working just fine too. It does just work, what was specifically the issue? In nautilus I go to smb://username@hostname/sharename, and it 'just works'. It was a matter of picking NFS4 on both machines, setting up hostnames instead of using IP addresses and: I was trying to recover saved Samba mount info saved from the former Windows laptop; I wanted to export each user's home directory. That didn't work at all, I kept getting /var/log/messages and command line errors about the directories not existing. Finally I just export /home on the server and it connected to
Lesson learned. I have had trouble with past distros; long past; where performing the online updates would put a lot of programs and libraries out of synch and I would have to reload the system from scratch because it wouldn't run. I'm glad this is no longer happening and will make sure to do this from now on. the mount point right away. Probably a permissions problem. The main thing was that I was confused by needing hostnames instead of IPs and NFS4 instead of NFS3 (I tried both). I never had these sorts of issues in the past, but it has been a while since I have used NFS at home.
The webcam works right out of the box too, so life is now good. You've got one up on me. My webcam doesn't do anything - although to be fair I've made no attempt at making it work. Running Cheese is the one way I can throw gnome-shell into a tail-spin. I don't even see a candidate device in lspci or lsusb.
I'm a very happy camper. Same here.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Adam Tauno Williams -
Anton Aylward -
Carlos E. R. -
Jim Sabatke -
JtWdyP -
Phil Savoie