On Thu, Nov 3, 2011 at 9:10 PM, Carlos E. R. wrote:

What the yast package manager loads first are the updated indexes of the packages it can offer for you later. It doesn't install anything unless you tell it so.

And even if I accept all those packages (without I actually know what the packages do), it would have no harm...? My printer Samsung ML-1610, was not detected (still not getting detected) and I am not able to take the prints.. What should I do? When to Yast and tried for detection but that doesn't help.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, Nov 4, 2011 at 7:07 AM, Anton Aylward wrote:

Get your updates working and the necessary repositories set up. There's no point complaining abut what can't be done if you don't have the up to date software.

I have done this complete and still was the printer problem!

As for printers, you need to get CUPS working and you need the definition package for your printer.  You should have this in a CD that came with the printer; that was the case for my printers.

Neither touched (anything on CUPS) nor have the original CD to do that, if I were having, it would have been no more an issue! On Fri, Nov 4, 2011 at 7:09 AM, Johannes Meixner wrote:

Install both the OpenPrintingPPDs-ghostscript RPM and also the splix RPM, see the "Driver" section in http://en.opensuse.org/YaST_Printer ------------------------------------------------------------------- The Add New Printer Configuration Dialog ... Driver ... click the "Driver Packages" button to check whether or not you may have to install more printer driver software packages

Ah, it really worked, I just installed 'OpenPrintingPPDs-ghostscript' and 'splix' from Yast (after putting this in the search field) and it got installed and now the printer is working! Thanks that I didn't go the long way of CUPS since needed the printer only for one PC. On Fri, Nov 4, 2011 at 7:13 AM, Carlos E. R. wrote:

...

And even if I accept all those packages (without I actually know what the packages do), it would have no harm...?

Normally, no; specially if you restrict yourself to YOU.

I am sure even if I don't know about all those packages which the Yast (very clever) installs automatically, it would not do any harm since I read in a review, 'openSUSE is developed by much skilled persons'. On Fri, Nov 4, 2011 at 7:18 AM, Anton Aylward wrote:

...

Well, I guess the passwords of the superuser ('root') and this created 'user' (during installation) is same until I manually change the root password but the two users are, of course, different. I guess it is like this....? I just see how to change the root password.

You said it was security of Linux that impressed you?

I didn't say that this was the **particular** aspect I was impressed with but rather in review what I read is, "openSUSE is without a doubt, the overall best distribution currently available EXCEPT that for the novice, it takes way too much knowledge to make it work 'just like Windows'." Further why actually this could be an good OS is because it works on open-mindedness. It says, "The openSUSE project explicitly looks beyond the technical community to the broader non-technical community of computer users interested in Linux." This line only changed my mind for which I installed it. "Note that it is the bigger community which is non-technical and uses computers". On Fri, Nov 4, 2011 at 7:42 AM, Anton Aylward wrote:

And how do you change the root password?

su password: passwd Changing password for root. New Password: Reenter New Password: Password changed. On Fri, Nov 4, 2011 at 7:52 AM, Basil Chupin wrote:

I think, Linux Tyro, you should make up your mind which distro you are going to get used to to begin with.

It seems you are asking the same questions in Ubuntu mail list as well as here.

If you run after two hares you won't catch either.

Sure, I have made it now for sure that openSUSE is the way to go and because of aforesaid reason ("The openSUSE project explicitly looks beyond the technical community to the broader non-technical community of computer users interested in Linux"), I have already installed it and now the printer is working too! See more things when I get time.. -- THX -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. wrote:

...

3. I created one user during installation and gave its password. Now, is this user [which has system administrative privileges (was written underneath the user when I created it)] having some sort of root powers ... or that is different? Since when I go to yast, it says me to enter the root password and I only enter the password of this created user (with which I log-in too) and yast works, so by default that is the password of root also? Or different (since I didn't set the root password and it is accepting that password..!). Or could root password be set separately..?

You normally will have a plain user and root, and typically both have the same password.

Typically? Well, they're only the same if you make them the same. -- Per Jessen, Zürich (11.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Linux Tyro said the following on 11/04/2011 06:11 AM:

Well, I guess the passwords of the superuser ('root') and this created 'user' (during installation) is same until I manually change the root password but the two users are, of course, different. I guess it is like this....? I just see how to change the root password.

You said it was security of Linux that impressed you? Well, only if you don't subvert it by doing silly/stupid things that are typical of Windows. Having and normally using a non-root user is an important part of that. Root is only for the admin tasks that require root. Preferably root login should be disables so that you have to log in as a regular user and then user 'sudo'. I've no doubt that people out of windows find this an inconvenient imposition, but then again, running with God-like power is one reason Windows has so many security problems. Yes, Vista tried to address this but managed to annoy. It *is* possible to delegate the various subsystems to higher-than-user but lower-than-root accounts with Suse, but its not worth the effort of setting it up unless you are in a serious and large IT shop where the administration of MANY machines is handled by many individuals with specific roles and responsibilities. -- Communism doesn't work because people like to own stuff. Frank Zappa -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 04/11/11 21:11, Linux Tyro wrote:

On Fri, Nov 4, 2011 at 5:02 AM, Per Jessen wrote:

...

...

...

3. I created one user during installation and gave its password. Now, is this user [which has system administrative privileges (was written underneath the user when I created it)] having some sort of root powers ... or that is different? Since when I go to yast, it says me to enter the root password and I only enter the password of this created user (with which I log-in too) and yast works, so by default that is the password of root also? Or different (since I didn't set the root password and it is accepting that password..!). Or could root password be set separately..? You normally will have a plain user and root, and typically both have the same password. Typically? Well, they're only the same if you make them the same. Well, I guess the passwords of the superuser ('root') and this created 'user' (during installation) is same until I manually change the root password but the two users are, of course, different. I guess it is like this....? I just see how to change the root password.

-- THX

I think, Linux Tyro, you should make up your mind which distro you are going to get used to to begin with. It seems you are asking the same questions in Ubuntu mail list as well as here. If you run after two hares you won't catch either. BC -- The truth is incontrovertible, malice may attack it, ignorance may deride it, but in the end, there it is. Sir Winston Churchill -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2011-11-04 10:02, Per Jessen wrote:

...

Carlos E. R. wrote:

...

...

You normally will have a plain user and root, and typically both have the same password.

Typically? Well, they're only the same if you make them the same.

The default in YaST nowdays is both the same password.

Really? I wasn't aware of that. I'm sure I did a Factory install just the other day and still had to enter two passwords. Well, if you're right, the openSUSE attitude towards security is deteriorating rapidly. -- Per Jessen, Zürich (12.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, Nov 4, 2011 at 11:50, Per Jessen wrote:

Carlos E. R. wrote:

...

On 2011-11-04 10:02, Per Jessen wrote:

...

Carlos E. R. wrote:

...

...

You normally will have a plain user and root, and typically both have the same password.

Typically?  Well, they're only the same if you make them the same.

The default in YaST nowdays is both the same password.

Really?  I wasn't aware of that.  I'm sure I did a Factory install just the other day and still had to enter two passwords.

Rapidly? It's been like that for a while now... at least early 2008... https://bugzilla.novell.com/show_bug.cgi?id=381420 Just for clarity on what this is about... on the Create New User screen of the installation wizard, there is a check-box that is checked by default: Use this password for system administrator C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, Nov 4, 2011 at 6:58 AM, Clayton wrote:

Just for clarity on what this is about... on the Create New User screen of the installation wizard, there is a check-box that is checked by default: Use this password for system administrator

Okay, I would change the root password (by command) but another thing is that I created an user (during installation) with some name, say, 'name1' and after getting desktop of 'name1', I changed it name to 'name_new' but this is okay, but now when see the contents of '/home' (from the desktop/terminal prompt of the user 'name_new'), the directory of 'linux~' is also there, which user is this one...? Okay one more directory is for 'name_new' but for 'linux~', I don't know, how did it come into existence...? -- THX -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hello,

On Fri, Nov 4, 2011 at 4:56 AM, Johannes Meixner wrote:

...

On my openSUSE 11.4 system I find those PPDs:

...

# lpinfo -m | grep -i samsung | grep -i 1610

This command gives no output in my case.

...

OpenPrintingPPDs/ghostscript/Samsung-ML-1610.gdi.ppd.gz  Samsung ML-1610 Foomatic/gdi

...

samsung/ml1610.ppd.gz Samsung ML-1610, SpliX V. 2.0.0

...

Therefore the Samsung ML-1610 should be supported by a Ghostscript driver via the first PPD from the OpenPrintingPPDs-ghostscript RPM and also by the SpliX driver in the splix RPM.

Install both the OpenPrintingPPDs-ghostscript RPM and also the splix RPM, see the "Driver" section in http://en.opensuse.org/YaST_Printer ------------------------------------------------------------------- The Add New Printer Configuration Dialog ... Driver ... click the "Driver Packages" button to check whether or not you may have to install more printer driver software packages -------------------------------------------------------------------

I downloaded from net (somwhere, on some website) this file 'ml1610unifiedlinuxdriverv2-00-90.gz' might be this is the driver it needs.

I am afraid I cannot help with third-party software because I have no knowledge at all regarding those software. In general when you use third-party software you can usually only ask where you got the third-party software for help and support.

What I tried:-

...

From yast -> hardware -> printing -> Add (new printer add wizard) -> samsung (ok it too) -> "No matching driver found. Change the search string or try 'Find More'."

Install the above mentioned packages and then I assume a matching driver can be found. If there is still no matching driver found, simplify the search string in YaST so that more drivers match e.g. to only "samsung" or "1610" and then select the right driver manually, see the "Driver" section in http://en.opensuse.org/YaST_Printer Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer

Hello, On Nov 4 19:30 Rodney Baker wrote (excerpt):

...

... printer Samsung ML-1610 ... ... I'm pretty sure its suppored by CUPS

No. CUPS neither provides printer drivers nor does CUPS provide software for the low-level communication with a printer device. The former is provided by Ghostscript usually together with printer driver software packages, see http://en.opensuse.org/Concepts_printing the latter is provided basically by the kernel and other low-level software, see http://en.opensuse.org/SDB:Installing_a_Printer Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, Nov 4, 2011 at 9:22 AM, David C. Rankin wrote:

 Since you are obviously new to linux and opensuse, let me give you a couple of tips that will make working with linux much easier and working with opensuse a breeze.

(1) For Multimedia (Music and DVD) playing and access, you must always enable the following 2 repositories that contain the players and various codecs needed to play multi-media files:

 Videolan Repository    - http://download.videolan.org/pub/videolan/vlc/SuSE/11.4/

 Packman Repository    - http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_11.4/

Well, I have added these two repositories.

(2) enable 'sudo' and 'su' access so you can run programs that require root permission from your *normal user* account by exercising root privileges *only* when you need it. The 2 tools you need are 'sudo' and 'su':

 sudo - 'Super User Do'

 example:  to install a rpm you have downloaded:

   sudo rpm -Uvh name-of-rpm-1.2.3.i686.rpm

 su - 'Become Super User' (or any user with 'su username')

 from konsole or xterm, simply type 'su' and you change from your normal user to root (or any other user if you supply a username). Then you can execute or access any files needing root access and then simply type 'exit' to change back to your user.

 We will configure all of this from the command line. Open an xterm or konsole window so you have a command line in front of you. (I presume you have some sort of GUI desktop in front of you - kde/gnome/fluxbox) 'alt+F2 xterm' will work. Make the window big enough that it is comfortable to you. Then become root by typing 'su' and entering the root password. (you did enter one right)

 First, make yourself a member of the 'wheel' group. Use the 'groupmod' command as follows:

   groupmod -A yourUserName wheel

 confirm you were added to the wheel group with the following:

   [07:50 alchemy:~] # grep wheel /etc/group    wheel:x:10:david               ^^^^^ (yourUserName)

 To set up sudo access for members of the wheel group (you), do the following:

 in the same xterm (as root): type 'visudo' (that puts you in the vim editor editing the /etc/sudoers file -- always use 'visudo' to alter sudo privilege, do not edit the sudoers file by hand). Since you probably don't know vi, just do the following to uncomment the line needed:

 Press:

   shift+g - to move to the bottom of the file    up arrow 4 times - to the line '#%wheel  ALL=(ALL) NOPASSWD: ALL'    home - to make sure you are at the beginning of the line over the '#'    del - to delete the '#' comment character

 it should now look like this:

# Same thing without a password %wheel  ALL=(ALL) NOPASSWD: ALL

 then just type

   :wq - to 'write' (save) the file and 'quit'

 Done with sudo! Now as your normal user, you can do 'sudo anyCommand' and run any command as root from your normal user account. (note - learn the vi editor over time, it will serve you well on ANY linux/unix system) A good cheat sheet for vim is: http://www.tuxfiles.org/linuxhelp/vimcheat.html

Yeah, now I need no password when I type, for example: sudo /sbin/reboot and it reboots.

 Finally set up su access without a password so you can become root from your normal user without a password as follows:

 sudo vi /etc/pam.d/su   (to open the file in the vi editor)

 Now add the following 2 lines to the file:

auth     sufficient     pam_wheel.so trust use_uid auth     required       pam_wheel.so use_uid

There was no 'trust' in the second line (for whatever reason...)

 (copy the lines by highlighting the 2 lines above and then alt+tab to the xterm with /etc/pam.d/su open in vi and press)

  i - puts vi in insert mode   'press the middle-mouse button down to paste the 2 lines into the file'   (or just retype the lines there - use arrow keys to navigate)   esc - takes vi out of input mode (and back into command mode)   :wq - write and quit

 Done! Now you can su without a password from your normal user. Try it! Open a new xterm and just type 'su' - you should become root immediately without a password.

For 'sudo' it worked but for 'su' I still need to enter the password. Another thing is that I created an user (during installation) with a name, say, 'name1' and after getting desktop of 'name1', I changed this name to 'name_new'. But now when see the contents of '/home', the directory of 'linux~' is also there, which user is this one...? One directory is for 'name_new', that's okay but for 'linux~', I don't know, how did it come into existence...? -- THX -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, Nov 4, 2011 at 11:21 AM, Carlos E. R. wrote:

"http://opensuse-guide.org/repo/11.4/"

It says: Forbidden You don't have permission to access /repo/11.4/ on this server. -- THX -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sat, Nov 5, 2011 at 8:32 PM, Carlos E. R. wrote:

...

...

"http://opensuse-guide.org/repo/11.4/"

It says:

Forbidden

You don't have permission to access /repo/11.4/ on this server.

Many repos are not browseable, but nevertheless they work.

Oh I see! -- THX -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, Nov 4, 2011 at 12:00 PM, David C. Rankin wrote:

AYE YIE YIE!  Please fix your e-mail client so it doesn't quote my (or anyone elses) full e-mail in your replies :)  Spammers harvest e-mail address from these lists and it just means more junk mail for people trying to help you. I don't know why the idiots that set up mail clients set this as default.

Ok it (gmail only) is doing that, but now I stop that, I really didn't know this.... I would just remove the address now..

Let us know what mail client you are using and we'll tell you how to fix it...

Definitely I would set up this, I would set-up whatever is the best and ask in case find problem(s) [probably yes].

The complete /etc/pam.d/su file should look like this:

10:34 alchemy:~> sudo cat /etc/pam.d/su #%PAM-1.0 auth     sufficient     pam_rootok.so auth     sufficient     pam_wheel.so trust use_uid auth     required       pam_wheel.so use_uid auth     include        common-auth account  sufficient     pam_rootok.so account  include        common-account password include        common-password session  include        common-session session  optional       pam_xauth.so

Here it is- linuxworld@linux-g34l:~> sudo cat /etc/pam.d/su #%PAM-1.0 auth sufficient pam_rootok.so auth include common-auth account sufficient pam_rootok.so account include common-account password include common-password session include common-session session optional pam_xauth.so auth sufficient pam_wheel.so trust use_uid auth required pam_wheel.so use_uid Here I have two lines which show, 'pam_rootok.so' - 1) auth 2) account, is there any change required (means should I...?)

...

Another thing is that I created an user (during installation) with a name, say, 'name1' and after getting desktop of 'name1', I changed this name to 'name_new'. But now when see the contents of '/home', the directory of 'linux~' is also there, which user is this one...? One directory is for 'name_new', that's okay but for 'linux~', I don't know, how did it come into existence...?

Dunno,

 My guess is that you created them somehow during the install. The easiest way to manage users on opensuse is with yast. So just do:

sudo yast

 This will open the text version of yast and then just navigate to:

Security and Users -> User and Group Management

 You can also just use the normal GUI interface for yast, but it is good to get familiar with the text interface in the event you ever need to manage your box remotely (over ssh, etc..). The text interface is very good and much easier to manage remotely.

 Once you get to User and Group Management, you will see the list of users installed on your box. Just add or delete or rename to your liking. But I wouldn't delete your own user.

 You can also do the same with the command line commands of: useradd userdel and usermod (and their group companions of groupadd groupdel and groupmod). You use the 'passwd' command to change the passwords from the command line. By default, if you su to root, you can change/reset any user password simply by issuing the command:

passwd theUserName

or just

passwd  (to change the current user/root's passwd)

 What yast User and Group Management does is manage the useradd/usermod/userdel, groupadd/groupmod/groupdel and passwd for you with its interface.

 Remember, working from the command line will give you the most flexibility, but Yast is pretty good for most uses. When you run into a command that you don't know the options for, in Linux you can usually just do:

Yeah sure, I did that all, but there was no extra user except the user 'linuxworld' (this was the changed name I gave to the original user 'trialbox'. But when I do 'ls /home' its the output - linuxworld@linux-g34l:~> ls /home linux~ linuxworld lost+found So is it safe to manually delete 'linux~'... (probably I think yes...?) since it is not a user created by me!

command --help

 or

man command

 That will give you the help file or manual page for nearly all commands. E.g.:

10:47 alchemy:~> useradd --help Usage: useradd ... useradd - create a new user

 -c comment     Set the GECOS field for the new account  --show-defaults Print default values  --save-defaults Save modified default values  -D binddn      Use dn "binddn" to bind to the LDAP directory  -d homedir     Home directory for the new user  -e expire      Date on which the new account will be disabled  -f inactive    Days after a password expires until account is disabled  -G group,...   List of supplementary groups  -g gid         Name/number of the users primary group  -k skeldir     Specify an alternative skel directory  -m             Create home directory for the new user  -o             Allow duplicate (non-unique) UID  -P path        Search passwd, shadow and group file in "path"  -p password    Encrypted password as returned by crypt(3)  -u uid         Force the new userid to be the given number  -U umask       Umask value used for creating home directory  -r, --system   Create a system account  -s shell       Name of the user's login shell  --service srv   Add account to nameservice 'srv'      --help     Give this help list      --usage    Give a short usage message  -v, --version  Print program version Valid services for --service are: files, ldap

 Revisit the su setup. It really is a time saver once you get it set up.  One more note -- and I hate this about the recent openSuSE installs -- you must tell the installer to set a traditional root account and password during setup or it just creates a 'Super User' out of the user account used during install. That may be the problem with your su setup.  I've never let the installer do that to me, so others will need to chime in on how to fix it.

Oh nice.

 You may prefer the newfangled 'Super User' created by the installer, but I for one always want a traditional 'root' account and root password and then I want to create my 'user' accounts.

But whether it is installer creating the 'Super User' or it is traditional 'root', they both have all the powers - what I know, so the only error it may is that in this installation, by default, the 'root' is taking the exactly same password which the user was taking (during installation) and I changed the root's password by the command ('su', 'passwd'). So apart from it, is/are there more difference(s)...?

 Also, don't freak out about the user directories that get created under /home. They are just individual directories that hold the personal files for the users that get created. E.g.:

10:57 nirvana:~> ls -al /home total 84 drwxr-xr-x 18 root       root        4096 Oct 10 23:08 . drwxr-xr-x 22 root       root        4096 Oct 30 23:28 .. drwxr-x---  4 david      david       4096 Dec 30  2010 admin drwxr-xr-x  2 alan       alan        4096 May  5  2011 alan drwxr-xr-x  2 anna       anna        4096 May  5  2011 anna drwxr-xr-x 10 david      david       4096 Oct  4 13:27 backup drwxr-x--- 48 david      http        4096 Nov  4 10:57 david drwxr-xr-x 20 deborah    dcr         4096 Aug  9 20:03 deborah drwxr-xr-x  2 dell       dell        4096 May  5  2011 dell drwxr-xr-x  2 drr        drr         4096 May  5  2011 drr drwxr-xr-x  4 david      david       4096 Oct 10 23:08 dv drwxr-xr-x  8 jordan     jordan      4096 Aug 10 17:04 jordan drwx------  2 root       root       16384 Jul 23 10:59 lost+found drwxr-xr-x 20 david      david       4096 Jul 22 07:40 samba drwxr-xr-x  9 sydney     sydney      4096 Aug 10 17:04 sydney drwxr-xr-x 14 zachry     zachry      4096 Oct 23 22:03 zachry

 If there are users created that you no longer want, then delete the user in Yast or with userdel. If you use 'userdel -r' then the directory under /home will be deleted as well. If yast doesn't do that, then you can manually delete the directory after you remove the user.

Ah well.

 Good luck and good choice of openSuSE for your first linux install.

In fact and frankly telling you, I have liked the openSUSE but because of different job, it seems a little bit typical (initially 'yes') but this is very good. If the policy of openSUSE, which is: "The openSUSE project explicitly looks beyond the technical community to the broader non-technical community of computer users interested in Linux." and as it is practically implemented too, I am glad to use it. On Fri, Nov 4, 2011 at 12:12 PM, David C. Rankin wrote:

Good, that probably means you are using kmail as the mail program. It mows the grass, but I prefer thunderbird... kmail on kde4 is still under heavy development. Just be glad you have kde 4.6.x or 4.7.x, as kde 4.0.x through 4.5.x were -- challenging -- to put it mildly...

Check the settings in kmail and find out where to turn off the quoting on the full e-mail in your replies -- see above..^^^ It should be under the options of what to quote in replies and forwards. I don't have kde4, so others will have to tell you exactly which setting controls this, but you are likely to draw a bit of ire from other users if you don't fix it :)

I am just using Firefox and in it 'gmail' but would see it.. If would set up the client, would go for Thunderbird.. Not last but a doubt is that when I type: linuxworld@linux-g34l:~> sudo yast sudo: yast: command not found it doesn't work, but when I do type the following: linuxworld@linux-g34l:~> sudo /sbin/yast it works, just wanted to know the basic difference, and the same when I used ' sudo reboot' (didn't work) but 'sudo /sbin/reboot' (worked). -- THX -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 11/04/2011 12:26 PM, Linux Tyro wrote:

On Fri, Nov 4, 2011 at 12:00 PM, David C. Rankin wrote: <snip> Ok it (gmail only) is doing that, but now I stop that, I really didn't know this.... I would just remove the address now..

Whew, thanks. (Sven, Will, All disregard my last post re: kmail) <snip>

...

The complete /etc/pam.d/su file should look like this:

...

10:34 alchemy:~> sudo cat /etc/pam.d/su #%PAM-1.0 auth sufficient pam_rootok.so auth sufficient pam_wheel.so trust use_uid auth required pam_wheel.so use_uid auth include common-auth account sufficient pam_rootok.so account include common-account password include common-password session include common-session session optional pam_xauth.so

Here it is-

linuxworld@linux-g34l:~> sudo cat /etc/pam.d/su #%PAM-1.0 auth sufficient pam_rootok.so auth include common-auth account sufficient pam_rootok.so account include common-account password include common-password session include common-session session optional pam_xauth.so auth sufficient pam_wheel.so trust use_uid auth required pam_wheel.so use_uid

Here I have two lines which show, 'pam_rootok.so' - 1) auth 2) account, is there any change required (means should I...?)

No those are fine - both are present in mine above... <snip>

Yeah sure, I did that all, but there was no extra user except the user 'linuxworld' (this was the changed name I gave to the original user 'trialbox'. But when I do 'ls /home' its the output -

linuxworld@linux-g34l:~> ls /home linux~ linuxworld lost+found

So is it safe to manually delete 'linux~'... (probably I think yes...?) since it is not a user created by me!

My guess is that is the user the live CD created when you first ran the live CD and installed openSuSE. What I would do is use yast to create a username you want on your box. "tyro" sounds like a good one for you :) I always like to create a group that is the same as the user to use as the user's primary group. (this tightens security preventing files created by everyone being owned by group 'user' by default) Suppose you want to create your user 'tyro' with a primary group of 'tyro' as well, if you want to do it from the command line, just do: sudo groupadd tyro sudo useradd -c "Linux Tyro" -m -g tyro -G wheel,user tyro sudo passwd tyro ** see 'useradd --help' for explanation of the options. now just logout and log back in as tyro. Then you can use yast and delete the other user accounts from within yast. Then check home with ls -l /home Post if you are unsure what you can delete. Otherwise, if you only want to keep the user account for tyro, just delete all directories except 'tyro' and 'lost+found' from the /home directory. The quick way is: cd /home sudo rm -r $(ls /home | grep -v "tyro\|lost+found") That will simply delete everything in home EXCEPT tyro and lost+found. Good Luck!

But whether it is installer creating the 'Super User' or it is traditional 'root', they both have all the powers - what I know, so the only error it may is that in this installation, by default, the 'root' is taking the exactly same password which the user was taking (during installation) and I changed the root's password by the command ('su', 'passwd'). So apart from it, is/are there more difference(s)...?

Correct, but everyone in the Linux community can help you based on a traditional root account, if that account is something line 'linuxuser' it's just going to inject additional confusion into the mix... <snip>

...

If there are users created that you no longer want, then delete the user in Yast or with userdel. If you use 'userdel -r' then the directory under /home will be deleted as well. If yast doesn't do that, then you can manually delete the directory after you remove the user.

Ah well.

...

Good luck and good choice of openSuSE for your first linux install.

In fact and frankly telling you, I have liked the openSUSE but because of different job, it seems a little bit typical (initially 'yes') but this is very good. If the policy of openSUSE, which is:

"The openSUSE project explicitly looks beyond the technical community to the broader non-technical community of computer users interested in Linux."

and as it is practically implemented too, I am glad to use it.

I am just using Firefox and in it 'gmail' but would see it.. If would set up the client, would go for Thunderbird..

Not last but a doubt is that when I type:

linuxworld@linux-g34l:~> sudo yast sudo: yast: command not found

it doesn't work, but when I do type the following:

linuxworld@linux-g34l:~> sudo /sbin/yast

it works, just wanted to know the basic difference, and the same when I used ' sudo reboot' (didn't work) but 'sudo /sbin/reboot' (worked).

Oops, sorry, I include /sbin in my path so I don't have to type the /sbin part for programs in that directory. To do the same, just edit your /home/yourUser/.bashrc and add it to your path like this: export PATH=$PATH:/usr/local/bin:/usr/local/sbin:/sbin:/usr/sbin Just put it anywhere toward the top of the file. Also, I like increasing the size of my .bash-history file so if I ever forget a command, I can likely find it in the last 15,000 I've typed :). Just include the following below the path statement in .bashrc export HISTFILESIZE=15000 export HISTSIZE=15000 There are literally hundreds of things you can do with .bashrc that can make your life much easier in Linux. Explore as you have time. One thing you can do is customize your command line prompt to your liking. Try the following in .bashrc as your user prompt: export PS1="\[\e[0;37m\]\A\[\e[1;34m\] \[\e[1;34m\]\h:\w> \[\e[0m\]" and for root in root's .bashrc: export PS1="\[\e[1;34m\][\[\e[1;31m\]\A \[\e[1;34m\]\h\[\e[0;31m\]:\w\[\e[1;34m\]] # \[\e[0m\]" You will need to source .bashrc again to see the change or just enter the line without 'export ' at the command prompt. e.g.: PS1="\[\e[0;37m\]\A\[\e[1;34m\] \[\e[1;34m\]\h:\w> \[\e[0m\]" That will give you a prompt with the following format: 23:31 yourHostName:/home/admin/cnf> The real benefit becomes apparent when you need to transfer files via ssh, etc.. All you need do is copy the path from your prompt and then middle-mouse click to paste it into the command line. eg.: 23:31 yourHostName:/home/admin/cnf> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Good luck! -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Linux Tyro said the following on 11/05/2011 06:26 AM:

This means that, group 'user' has its files different from every one and only that 'tyro' (and the root, of course) could see (since it had been of group 'tyro'), is it like that...?

No. You seem confused., that wording is .... Users and groups are mapped to access. It's about access permissions. Users belong to groups; users can belong to more than one group. Groups don't "own" files; users own files. Files have access permissions - which user owns them. Groups are not a way of classifying or categorising files; we don't groups and associate files by group. The 'groups' is a sharing mechanism. Its about access control. I strongly suggest you read the relevant sections of the books and ebooks you've been referred to. That will go into matters in more depth and cross reference to other sections of the book about command for altering a files groups, permissions, a users groups and permission, and more. This forum is not meant to be a substitute for a text book about the fundamentals of Linux. Please download the e-books that have been mentioned and study them or get a book on Linux fundamentals from Amazon/Chapters/Barnes or your local library. -- Telling the future by looking at the past assumes that conditions remain constant. This is like driving a car by looking in the rear view mirror. - Herb Brody -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Linux Tyro said the following on 11/05/2011 06:26 AM:

Here, should there be or not (I don't know) any gap between comma and / or user) But it is saying an error:

linuxworld@linux-g34l:~/Music/old superhits> sudo groupadd tyro linuxworld@linux-g34l:~/Music/old superhits> > sudo useradd -c "LinuxTyro" -m -g tyro -G wheel,user tyro useradd: Unknown group `user'.

Please consult a textbook - you've been referred to many, about groups, or google for this. PLEASE take some initiative in finding out before asking here. We are not a substitute for a textbook. http://www.google.com/search?q=linux+groups will give you answers to all those questions. -- There is no greater mistake than the hasty conclusion that opinions are worthless because they are badly argued. Thomas H. Huxley -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Linux Tyro said the following on 11/05/2011 06:26 AM:

Oh, 'linuxworld' (or 'linuxuser', whatever) is not the root but has privileges of system administration, does it mean that?

NO! Root has uid=0. Other users don't. Other users may belong to a group which permits them, by one means or other, to have administration privileges granted to them. For example: (hypothetical to illustrate the point) There is a group 'lp' There are programs that are used to administer the printer system. These should not be run by ordinary users. So the will have access -rwxr-x--- root lp ..... However if you don't want to give out the root password to the guy who administers the printers, then you can add him to the 'lp' group. This technique was explained over two decades ago in a USENIX paper "Life Without Root". http://www.ussrback.com/docs/papers/unix/noroot.ps This approach is suited to larger systems where there will be delegation. It is too complex to implement for all possible forms of delegation in most sites! However it does illustrated well the point of group permissions. Now the example David gave is 'the-same-but-different'. The 'wheel' group is a historic tradition http://www.google.com?=linux+wheel+group that allows, via other methods, a group of users to be granted the ability to 'su' to root without the need for the root password. There are a number of mechanisms for this. The historic one was in 'sudo'. Later, PAM allowed for specific commands. Originally the mechanism prompted the user for his own password rather than the root password. (If you use the same password for both then this is a moot point.) If you googled, you would find specific instructions http://administratosphere.wordpress.com/2007/09/10/wheel-group-and-fedora-re... and explanations http://alien.slackbook.org/dokuwiki/doku.php?id=linux:admin http://foldoc.org/wheel+bit Of course you could have RTFM http://linux.die.net/man/8/pam_wheel Of course you could have found out all this by googling or by reading one of the books or e-books we've referred you to.

But even when I go to yast (GUI), I need to enter the root's password (which I changed after installation, since in the beginning it was the same as that of 'linuxworld' user) and it does only ROOT password not the linuxworld password, even though while installation, it declared the created user as having the system admin privileges.

-- Growth for the sake of growth is the ideology of the cancer cell. - Edward Abbey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Linux Tyro said the following on 11/05/2011 08:33 AM:

On Sat, Nov 5, 2011 at 8:28 AM, Anton Aylward wrote:

<snip>...

Yeah thanks. I would google.

It is a good habit to develop. -- The user's going to pick dancing pigs over security every time. -- Bruce Schneier -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sat, Nov 5, 2011 at 12:40 AM, David C. Rankin wrote: Please if you have time, step by step, let me know as like you said me previously, I was getting but confused here in the following:--

...

linuxworld@linux-g34l:~> sudo cat /etc/pam.d/su #%PAM-1.0 auth sufficient pam_rootok.so auth include common-auth account sufficient pam_rootok.so account include common-account password include common-password session include common-session session optional pam_xauth.so auth sufficient pam_wheel.so trust use_uid auth required pam_wheel.so use_uid

...

Here I have two lines which show, 'pam_rootok.so' - 1) auth 2) account, is there any change required (means should I...?)

No those are fine - both are present in mine above...

So what I do, I want that ease that typing 'su' changes the prompt to 'root' without all the times giving the password. Something still needs to be modified/changed/removed...? Since still it is asking for the password....

My guess is that is the user the live CD created when you first ran the live CD and installed openSuSE.

I have deleted completed this user ('linux~') and you are right since I had to delete also one file with name something like ...'livedesktop'...inside that. However, now it doesn't matter.

What I would do is use yast to create a username you want on your box. "tyro" sounds like a good one for you :) I always like to create a group that is the same as the user to use as the user's primary group.

Okay.

(this tightens security preventing files created by everyone being owned by group 'user' by default)

This means that, group 'user' has its files different from every one and only that 'tyro' (and the root, of course) could see (since it had been of group 'tyro'), is it like that...?

Suppose you want to create your user 'tyro' with a primary group of 'tyro' as well, if you want to do it from the command line, just do:

sudo groupadd tyro sudo useradd -c "Linux Tyro" -m -g tyro -G wheel,user tyro sudo passwd tyro

Here, should there be or not (I don't know) any gap between comma and / or user) But it is saying an error: linuxworld@linux-g34l:~/Music/old superhits> sudo groupadd tyro linuxworld@linux-g34l:~/Music/old superhits> > sudo useradd -c "LinuxTyro" -m -g tyro -G wheel,user tyro useradd: Unknown group `user'.

** see 'useradd --help' for explanation of the options.

now just logout and log back in as tyro. Then you can use yast and delete the other user accounts from within yast. Then check home with

So if the above user is created (after getting created, when I don't get the above error), this user 'linuxtyro' would have the same privileges like that of the user 'linuxworld' (created during the installation), is it like this....? Since it is also of the group 'wheel', the users of which have the power to run 'sudo' without being offered a root password and switching to su doesn't prompt password for them (after resolving that error too)...?

ls -l /home

Post if you are unsure what you can delete. Otherwise, if you only want to keep the user account for tyro, just delete all directories except 'tyro' and 'lost+found' from the /home directory. The quick way is:

cd /home sudo rm -r $(ls /home | grep -v "tyro\|lost+found")

That will simply delete everything in home EXCEPT tyro and lost+found.

But what this 'lost+found' is? It doesn't get deleted..?

Good Luck!

Thanks.

Correct, but everyone in the Linux community can help you based on a traditional root account, if that account is something line 'linuxuser' it's just going to inject additional confusion into the mix...

Oh, 'linuxworld' (or 'linuxuser', whatever) is not the root but has privileges of system administration, does it mean that? But even when I go to yast (GUI), I need to enter the root's password (which I changed after installation, since in the beginning it was the same as that of 'linuxworld' user) and it does only ROOT password not the linuxworld password, even though while installation, it declared the created user as having the system admin privileges.

It's a damn good distro. It's had its share of bumps over the years, but comparatively speaking, it is by far the best distro for all-around use you will find.

Sure and the most important part is the good community too where technical people can help anybody. I like SUSE.

...

it works, just wanted to know the basic difference, and the same when I used ' sudo reboot' (didn't work) but 'sudo /sbin/reboot' (worked).

Oops, sorry, I include /sbin in my path so I don't have to type the /sbin part for programs in that directory. To do the same, just edit your /home/yourUser/.bashrc and add it to your path like this:

export PATH=$PATH:/usr/local/bin:/usr/local/sbin:/sbin:/usr/sbin

Just put it anywhere toward the top of the file. Also, I like increasing the size of my .bash-history file so if I ever forget a command, I can likely find it in the last 15,000 I've typed :). Just include the following below the path statement in .bashrc

export HISTFILESIZE=15000 export HISTSIZE=15000

I have added 'export PATH=$PATH:/usr/local/bin:/usr/local/sbin:/sbin:/usr/sbin' line to the top of the file /home/linuxworld/.bashrc and yes now it doesn't need /sbin prefix! But I am sure it is only for this user since we have edited only the file (.bashrc) of this 'linuxworld' user.

There are literally hundreds of things you can do with .bashrc that can make your life much easier in Linux. Explore as you have time. One thing you can do is customize your command line prompt to your liking. Try the following in .bashrc as your user prompt:

export PS1="\[\e[0;37m\]\A\[\e[1;34m\] \[\e[1;34m\]\h:\w> \[\e[0m\]"

Just typed this (above) line at the command prompt without export, and the colour of the user 'linuxworld' (written) changed to violet, what does it mean? Is it becoming root or something like that?

and for root in root's .bashrc:

export PS1="\[\e[1;34m\][\[\e[1;31m\]\A \[\e[1;34m\]\h\[\e[0;31m\]:\w\[\e[1;34m\]] # \[\e[0m\]"

You will need to source .bashrc again to see the change or just enter the line without 'export ' at the command prompt. e.g.:

PS1="\[\e[0;37m\]\A\[\e[1;34m\] \[\e[1;34m\]\h:\w> \[\e[0m\]"

That will give you a prompt with the following format:

23:31 yourHostName:/home/admin/cnf>

The real benefit becomes apparent when you need to transfer files via ssh, etc.. All you need do is copy the path from your prompt and then middle-mouse click to paste it into the command line. eg.:

23:31 yourHostName:/home/admin/cnf> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Oh I see. On Fri, Nov 4, 2011 at 3:56 PM, Patrick Shanahan wrote:

this is really simple, when you type a command w/o it's path, your system searches it's path, $PATH, for the command. It cannot find the command because your $PATH does not contain /sbin which is a path normally reserved for "root user", ie: require root password.

you can display your path, $PATH echo $PATH

Oh, I see. -- THX -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sat, Nov 5, 2011 at 8:52 AM, Anton Aylward wrote:

Users are different; they have different uids.

Yeah, that is correct, but when I added the user to do that particular task only, then it should that thing only. Further, when switching to su, it still asks me the password, so how do I again edit those files... I understand this all will take much time and it is Linux. -- THX -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, Nov 4, 2011 at 9:22 AM, David C. Rankin wrote:

I presume you have some sort of GUI desktop in front of you

I am having KDE desktop and other details are architecture as x86_64 with openSUSE 11.4 (installed via Live CD). -- THX -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Am Freitag, 4. November 2011, 11:12:25 schrieb David C. Rankin:

Good, that probably means you are using kmail as the mail program. It mows the grass, but I prefer thunderbird... kmail on kde4 is still under heavy development. Just be glad you have kde 4.6.x or 4.7.x, as kde 4.0.x through 4.5.x were -- challenging -- to put it mildly...

Check the settings in kmail and find out where to turn off the quoting on the full e-mail in your replies -- see above..^^^ It should be under the options of what to quote in replies and forwards. I don't have kde4, so others will have to tell you exactly which setting controls this, but you are likely to draw a bit of ire from other users if you don't fix it :)

I am a kmail user for several years and never saw that behaviour (that the full mail address is quoted) by default. This mail is written with kmail2 and it also does not do that by default (though it adds the response with a line which is localized as you see at the top, same as the old kmail did by default). The template for a response can be edited in in the mail settings (editor settings, templates) which show me a %OFROMNAME not a %OFROMADDR for the response. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Am Freitag, 4. November 2011, 13:47:27 schrieb David C. Rankin:

...

The template for a response can be edited in in the mail settings (editor settings, templates) which show me a %OFROMNAME not a %OFROMADDR for the response.

Martin,

Thanks. I know in the past when I beta'ed kde4, I saw this behavior and I had to turn it off. Strange, I use it for at least 8 years (kde 3.x and all versions of 4.x which was real fun in a sarcastic sense), but I can remeber that some versions simply had no templates at all which I could use or threw away my existing ones and all such things. I can imagine that what you describe is of course possible. You are lucky that your templates seem to be a bit more sane. As I said I had all kinds of oddities over the years not only with templates, but luckily not the desribed one. I wonder if the OP's install from the live CD had anything to do with it? I know kdepim/kmail2 has been very fluid lately. The OP uses gmail so it is not kmail at all.

How to change that in kmail I tried to point to in my last mail, the editor settings and the templates there are directly accessible via the menu, but as the OP already told us that he/she had to change it in gmail not kmail. So I close now my off topic comment on that issue, I do not intend to hijack this thread. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Am Freitag, 4. November 2011, 12:31:23 schrieb Felix Miata:

I found SMplayer preferable to VLC some months ago, and NAICT don't need the Videolan repo any more.

You also do not need the videolan repo for vlc, since vlc is also shipped via packman (I use that vlc version from packman). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Am Freitag, 4. November 2011, 14:01:51 schrieb Linux Tyro:

On Fri, Nov 4, 2011 at 12:36 PM, Martin Helm wrote:

...

You also do not need the videolan repo for vlc, since vlc is also shipped via packman (I use that vlc version from packman).

I have added both the URLs, viz.,

Videolan Repository - http://download.videolan.org/pub/videolan/vlc/SuSE/11.4/

Packman Repository - http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_11.4/

And installed the VLC media player (after putting it in search field). Now music files of all format are working in it (like, .mp4, .flv, .mpg, .mpeg, .DAT, .mp3). But I really didn't know (but there must be some method) from which location was this VLC installed from Packman or the other one, but now I have removed the Videolan repository URL, and VLC is still working. Does this necessarily mean that VLC was installed from Packman repository?

No, when a repository is removed no package from it will be uninstalled and no package will swith its vendor. Simply open yast software management and search for vlc, in the versions tab you can see from which repository it is. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 11/4/2011 9:22 AM, David C. Rankin wrote:

sudo - 'Super User Do'

example: to install a rpm you have downloaded:

sudo rpm -Uvh name-of-rpm-1.2.3.i686.rpm

su - 'Become Super User' (or any user with 'su username')

I was about to say "No it means switch user!" But then: http://pthree.org/2009/12/31/the-meaning-of-su/ I guess I better not. ;) -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org