Hi, I am using Samba to share my computer over a windows network. I can access any computer(there are over 400 computers) on LAN but no one can access. They can't do it.. I am pasting the output of testparam for your reference..Any pointers will be helpful linux-fh4f:/etc/samba # testparm /etc/samba/smb.conf Load smb config files from /etc/samba/smb.conf Processing section "[homes]" Processing section "[shared]" Global parameter guest account found in service section! Loaded services file OK. WARNING: passdb expand explicit = yes is deprecated Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions [global] workgroup = MSHOME netbios name = PUNEIT server string = puneit_singh security = SHARE map to guest = Bad User server signing = auto printcap name = cups add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ logon path = \\%L\profiles\.msprofile logon drive = P: logon home = \\%L\%U\.9xprofile os level = 2 preferred master = No local master = No domain master = No ldap ssl = no usershare max shares = 100 hosts allow = 192.168.0.0/255.255.255.0 cups options = raw include = /etc/samba/dhcp.conf [homes] comment = Home Directories valid users = %S, %D%w%S read only = No inherit acls = Yes browseable = No [shared] path = /home/puneit/Shared/ username = prometheus read only = No guest only = Yes guest ok = Yes case sensitive = No msdfs proxy = no -- Puneit Singh 0091-9350832020
On Tuesday 12 September 2006 14:33, Puneit Singh wrote:
Hi, I am using Samba to share my computer over a windows network. I can access any computer(there are over 400 computers) on LAN but no one can access. They can't do it.. I am pasting the output of testparam for your reference..Any pointers will be helpful
Do you have the firewall running on your box, and if so, what settings do you have? Peter
On Tuesday 12 September 2006 14:33, Puneit Singh wrote:
Hi, I am using Samba to share my computer over a windows network. I can access any computer(there are over 400 computers) on LAN but no one can access. They can't do it.. I am pasting the output of testparam for your reference..Any pointers will be helpful
Do you have the firewall running on your box, and if so, what settings do you have?
Peter Yes, I have a firewall... You would need to tell me how do I give you the
On Wednesday 13 September 2006 00:07, Peter Bloomfield wrote: details of the firewall.. Where is the firewall settings stored.. I can then copy paste the contents.. -- Puneit Singh 0091-9350832020
On Tuesday 12 September 2006 14:39, Puneit Singh wrote:
On Wednesday 13 September 2006 00:07, Peter Bloomfield wrote:
On Tuesday 12 September 2006 14:33, Puneit Singh wrote:
Hi, I am using Samba to share my computer over a windows network. I can access any computer(there are over 400 computers) on LAN but no one can access. They can't do it.. I am pasting the output of testparam for your reference..Any pointers will be helpful
Do you have the firewall running on your box, and if so, what settings do you have?
Peter
Yes, I have a firewall... You would need to tell me how do I give you the details of the firewall.. Where is the firewall settings stored.. I can then copy paste the contents..
I may not be the best person to answer this, but I can give you some hints. I go through the 'Yast control Centre' and select 'Firewall' from the 'Security and User' tab. In the firwall window that 'pops up' look in the 'Allowed services' section. I have 'Samba Server' as an allowed service. Peter
On Wednesday 13 September 2006 00:18, Peter Bloomfield wrote:
On Tuesday 12 September 2006 14:39, Puneit Singh wrote:
On Wednesday 13 September 2006 00:07, Peter Bloomfield wrote:
On Tuesday 12 September 2006 14:33, Puneit Singh wrote:
Hi, I am using Samba to share my computer over a windows network. I can access any computer(there are over 400 computers) on LAN but no one can access. They can't do it.. I am pasting the output of testparam for your reference..Any pointers will be helpful
Do you have the firewall running on your box, and if so, what settings do you have?
Peter
Yes, I have a firewall... You would need to tell me how do I give you the details of the firewall.. Where is the firewall settings stored.. I can then copy paste the contents..
I may not be the best person to answer this, but I can give you some hints.
I go through the 'Yast control Centre' and select 'Firewall' from the 'Security and User' tab.
In the firwall window that 'pops up' look in the 'Allowed services' section. I have 'Samba Server' as an allowed service.
Peter
So do I. I have Samba Server as an allowed service too -- Puneit Singh 0091-9350832020
On Tuesday 12 September 2006 14:55, Puneit Singh wrote:
On Wednesday 13 September 2006 00:18, Peter Bloomfield wrote:
On Tuesday 12 September 2006 14:39, Puneit Singh wrote:
On Wednesday 13 September 2006 00:07, Peter Bloomfield wrote:
On Tuesday 12 September 2006 14:33, Puneit Singh wrote:
Hi, I am using Samba to share my computer over a windows network. I can access any computer(there are over 400 computers) on LAN but no one can access. They can't do it.. I am pasting the output of testparam for your reference..Any pointers will be helpful
Do you have the firewall running on your box, and if so, what settings do you have?
Peter
Yes, I have a firewall... You would need to tell me how do I give you the details of the firewall.. Where is the firewall settings stored.. I can then copy paste the contents..
I may not be the best person to answer this, but I can give you some hints.
I go through the 'Yast control Centre' and select 'Firewall' from the 'Security and User' tab.
In the firwall window that 'pops up' look in the 'Allowed services' section. I have 'Samba Server' as an allowed service.
Peter
So do I. I have Samba Server as an allowed service too
On the same page, selecting the 'advanced tab', do you have any additional ports allowed? This is where I am hitting the limits of my limited knowledge, sorry for my ignorance. Peter
On the same page, selecting the 'advanced tab', do you have any additional ports allowed? This is where I am hitting the limits of my limited knowledge, sorry for my ignorance.
Peter
Just the TCP ports have this entry netbios-dgm netbios-ns rest all are blank -- Puneit Singh 0091-9350832020
Puneit Singh wrote:
So do I. I have Samba Server as an allowed service too
May I suggest you turn off your firewall and make sure that samba is working correctly first? ..as root jrm:/ # rcSuSEfirewall2 stop or if you prefer jrm:/# /etc/init.d/SuSEfirewall2_setup stop Justin
On Wednesday 13 September 2006 19:22, Justin M wrote:
Puneit Singh wrote:
So do I. I have Samba Server as an allowed service too
May I suggest you turn off your firewall and make sure that samba is working correctly first?
..as root jrm:/ # rcSuSEfirewall2 stop or if you prefer jrm:/# /etc/init.d/SuSEfirewall2_setup stop
Justin I turned off the firewall and checked.. It still didn't work... How do I ensure Samba is working correctly -- Puneit Singh 0091-9350832020
Puneit Singh wrote:
On Wednesday 13 September 2006 19:22, Justin M wrote:
Puneit Singh wrote:
So do I. I have Samba Server as an allowed service too
May I suggest you turn off your firewall and make sure that samba is working correctly first?
..as root jrm:/ # rcSuSEfirewall2 stop or if you prefer jrm:/# /etc/init.d/SuSEfirewall2_setup stop
Justin
I turned off the firewall and checked.. It still didn't work... How do I ensure Samba is working correctly
Does the command below return anything? jrm@jrm:~> smbclient -L localhost --no-pass Is the server even started? jrm@jrm:~> rcsmb status jrm@jrm:~> rcnmb status
Does the command below return anything?
jrm@jrm:~> smbclient -L localhost --no-pass
Is the server even started? jrm@jrm:~> rcsmb status jrm@jrm:~> rcnmb status
puneit@linux-fh4f:~> smbclient -L localhost --no-pass Anonymous login successful Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.22-13.18-SUSE-CODE10] Sharename Type Comment --------- ---- ------- shared Disk IPC$ IPC IPC Service (puneit_singh) ADMIN$ IPC IPC Service (puneit_singh) Anonymous login successful Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.22-13.18-SUSE-CODE10] Server Comment --------- ------- ABCDSF xyz P-4 Neha PUNEIT puneit_singh TANISHA_MIB Workgroup Master --------- ------- MSHOME P-4 linux-fh4f:/home/puneit # rcsmb status Checking for Samba SMB daemon running linux-fh4f:/home/puneit # rcnmb status Checking for Samba NMB daemon running -- Puneit Singh 0091-9350832020
Puneit Singh wrote:
puneit@linux-fh4f:~> smbclient -L localhost --no-pass Anonymous login successful Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.22-13.18-SUSE-CODE10]
Sharename Type Comment --------- ---- ------- shared Disk IPC$ IPC IPC Service (puneit_singh) ADMIN$ IPC IPC Service (puneit_singh) Anonymous login successful Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.22-13.18-SUSE-CODE10]
Server Comment --------- ------- ABCDSF xyz P-4 Neha PUNEIT puneit_singh TANISHA_MIB
Workgroup Master --------- ------- MSHOME P-4
I am guessing all your hosts are on the 192.168.0.x network? This is a very simplistic smb.conf I have. [global] workgroup = JRM map to guest = Bad User printcap name = cups logon path = \\%L\profiles\.msprofile logon drive = P: logon home = \\%L\%U\.9xprofile local master = No cups options = raw [public] path = /localhome/jrm/public read only = No guest ok = Yes
I am guessing all your hosts are on the 192.168.0.x network?
This is a very simplistic smb.conf I have.
[global] workgroup = JRM map to guest = Bad User printcap name = cups logon path = \\%L\profiles\.msprofile logon drive = P: logon home = \\%L\%U\.9xprofile local master = No cups options = raw
[public] path = /localhome/jrm/public read only = No guest ok = Yes my smb.conf doesn't have a [public]
everyone is on 192.168.x.x not on e.g. majority of my peers are on 192.168.4.x or 192.168.5.x So, shall I change that? this is what my smb.conf shows # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2006/09/01 20:08:20 [global] workgroup = MSHOME netbios name = PUNEIT server string = puneit_singh map to guest = Bad User printcap name = cups add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ logon path = \\%L\profiles\.msprofile logon drive = P: logon home = \\%L\%U\.9xprofile os level = 2 preferred master = no local master = no domain master = no hosts allow = 192.168.0.0/255.255.255.0 cups options = raw include = /etc/samba/dhcp.conf usershare max shares = 100 security = domain restrict anonymous = no max protocol = NT ldap ssl = No server signing = Auto idmap gid = 10000-20000 idmap uid = 10000-20000 wins support = yes [homes] comment = Home Directories valid users = %S, %D%w%S read only = No inherit acls = Yes browseable = No [shared] path = /home/puneit/Shared/ guest ok = yes read only = no case sensitive = no msdfs proxy = no guest account = ftp guest only = yes username = prometheus -- Puneit Singh 0091-9350832020
Hi all, On a couple of our servers running SUSE Linux Enterprise Server 10 (x86_64), we have encountered some intermittent problems when users try to log on using ssh and failed: ssh user@machine Password: xxxxxx Permissions on the password database may be too restrictive. The machine has firewall enabled, but it appears that certain updates (quite likely from YOU) have been applied and the firewall has been reset. As a result no one can log on over the network using ssh. Restarting firewall (by invokine /etc/init.d/SuSEfirewall2_init and SuSEfirewall2_setup restart alone) will NOT reactivate the service. Access is only restored after flushing the firewall and restarting it. Has anyone come across the same problem? Any pointers here? Peter --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 13 November 2006 16:59, Chiu, PCM (Peter) wrote:
Hi all,
On a couple of our servers running SUSE Linux Enterprise Server 10 (x86_64), we have encountered some intermittent problems when users try to log on using ssh and failed:
ssh user@machine Password: xxxxxx Permissions on the password database may be too restrictive.
This error comes from PAM, and as far as I know it can mean one of two things: either the password or username was wrong, or PAM failed to contact the password source (for example failed to read /etc/shadow, or failed to contact the LDAP server for some reason) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thanks Anders, The system uses NIS, a client. I happened to have a session logged on at the time, and I could access the NIS servers. I did also restart ypbind, and it got started okay. As explained in my earlier post to Daniel Gomez, I ran a verify on pam, pam-32bit, pam-modules, pam-modules-32bit and yast2-pam, no specific differences reported apart from pam_pwcheck.conf. The latter has only 1 line, nothing obvious... Peter -----Original Message----- From: Anders Johansson [mailto:ajohansson@novell.com] Sent: 13 November 2006 19:31 To: opensuse@opensuse.org Subject: Re: [opensuse] SLES 10 x86_64 - Permissions on password database too restrictive On Monday 13 November 2006 16:59, Chiu, PCM (Peter) wrote:
Hi all,
On a couple of our servers running SUSE Linux Enterprise Server 10 (x86_64), we have encountered some intermittent problems when users try to log on using ssh and failed:
ssh user@machine Password: xxxxxx Permissions on the password database may be too restrictive.
This error comes from PAM, and as far as I know it can mean one of two things: either the password or username was wrong, or PAM failed to contact the password source (for example failed to read /etc/shadow, or failed to contact the LDAP server for some reason) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Well, NIS in itself is not an authentication scheme, it only distributes configurations. A NIS client can authenticate against LDAP or local shadow files, depending on the config files you're distributing Check the pam_unix2.conf in /lib/security to see what you are using for authentication On Tuesday 14 November 2006 11:59, Chiu, PCM (Peter) wrote:
Thanks Anders,
The system uses NIS, a client.
I happened to have a session logged on at the time, and I could access the NIS servers. I did also restart ypbind, and it got started okay.
As explained in my earlier post to Daniel Gomez, I ran a verify on pam, pam-32bit, pam-modules, pam-modules-32bit and yast2-pam, no specific differences reported apart from pam_pwcheck.conf. The latter has only 1 line, nothing obvious...
Peter
-----Original Message----- From: Anders Johansson [mailto:ajohansson@novell.com] Sent: 13 November 2006 19:31 To: opensuse@opensuse.org Subject: Re: [opensuse] SLES 10 x86_64 - Permissions on password database too restrictive
On Monday 13 November 2006 16:59, Chiu, PCM (Peter) wrote:
Hi all,
On a couple of our servers running SUSE Linux Enterprise Server 10 (x86_64), we have encountered some intermittent problems when users try to log on using ssh and failed:
ssh user@machine Password: xxxxxx Permissions on the password database may be too restrictive.
This error comes from PAM, and as far as I know it can mean one of two things: either the password or username was wrong, or PAM failed to contact the password source (for example failed to read /etc/shadow, or failed to contact the LDAP server for some reason) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Anders, I can only find pam_unix2.conf under /etc/security. In that, apart from comments, it contains the following four lines auth: account: password: session: none So presumably just using the defaults. Peter -----Original Message----- From: Anders Johansson [mailto:ajohansson@novell.com] Sent: 14 November 2006 12:08 To: Chiu, PCM (Peter) Cc: opensuse@opensuse.org Subject: Re: [opensuse] SLES 10 x86_64 - Permissions on password database too restrictive Well, NIS in itself is not an authentication scheme, it only distributes configurations. A NIS client can authenticate against LDAP or local shadow files, depending on the config files you're distributing Check the pam_unix2.conf in /lib/security to see what you are using for authentication On Tuesday 14 November 2006 11:59, Chiu, PCM (Peter) wrote:
Thanks Anders,
The system uses NIS, a client.
I happened to have a session logged on at the time, and I could access
the NIS servers. I did also restart ypbind, and it got started okay.
As explained in my earlier post to Daniel Gomez, I ran a verify on pam, pam-32bit, pam-modules, pam-modules-32bit and yast2-pam, no specific differences reported apart from pam_pwcheck.conf. The latter
has only 1 line, nothing obvious...
Peter
-----Original Message----- From: Anders Johansson [mailto:ajohansson@novell.com] Sent: 13 November 2006 19:31 To: opensuse@opensuse.org Subject: Re: [opensuse] SLES 10 x86_64 - Permissions on password database too restrictive
On Monday 13 November 2006 16:59, Chiu, PCM (Peter) wrote:
Hi all,
On a couple of our servers running SUSE Linux Enterprise Server 10 (x86_64), we have encountered some intermittent problems when users try to log on using ssh and failed:
ssh user@machine Password: xxxxxx Permissions on the password database may be too restrictive.
This error comes from PAM, and as far as I know it can mean one of two things: either the password or username was wrong, or PAM failed to contact the password source (for example failed to read /etc/shadow, or failed
to contact the LDAP server for some reason) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 14 November 2006 14:36, Chiu, PCM (Peter) wrote:
Hi Anders,
I can only find pam_unix2.conf under /etc/security. In that, apart from comments, it contains the following four lines
Sorry, yes, /lib/security has the plugins, /etc/security the config
auth: account: password: session: none
So presumably just using the defaults.
Yes, you are using /etc/shadow So, try to log in locally. Does that work? Is /etc/shadow readable by sshd at all? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Chiu, PCM (Peter) wrote:
Restarting firewall (by invokine /etc/init.d/SuSEfirewall2_init and SuSEfirewall2_setup restart alone) will NOT reactivate the service. Access is only restored after flushing the firewall and restarting it.
Has anyone come across the same problem?
Any pointers here?
Since you seem to indicate it IS a firewall issue, and not a PAM issue, I would suggest doing what many of us are doing (but which seems to be a bug), and that is SuSEfirewall2 stop, then SuSEfirewall2 start, which for me has always worked. For some reasons unknown to me (and since the fix was just as easy) this seems to flush the rules and works better than a restart. YMMV. HTH. -- Joe Morris Registered Linux user 231871 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thanks, Joe, Maybe a mix-up on terminalogy used. I did restart firewall by invoking /etc/init.d/SuSEfirewall2_init restart and /etc/init.d/SuSEfirewall2_setup restart I shall have to wait until the next time the problem strikes again to see if I have nailed the problem. Did try before with chkstat -set /etc/permissions but that didn't help - so thought it was a firewall issue triggered by YOU updates. Thanks a lot. Peter -----Original Message----- From: Joe Morris (NTM) [mailto:Joe_Morris@ntm.org] Sent: 14 November 2006 01:26 To: opensuse@opensuse.org Subject: Re: [opensuse] SLES 10 x86_64 - Permissions on password database too restrictive Chiu, PCM (Peter) wrote:
Restarting firewall (by invokine /etc/init.d/SuSEfirewall2_init and SuSEfirewall2_setup restart alone) will NOT reactivate the service. Access is only restored after flushing the firewall and restarting it.
Has anyone come across the same problem?
Any pointers here?
Since you seem to indicate it IS a firewall issue, and not a PAM issue, I would suggest doing what many of us are doing (but which seems to be a bug), and that is SuSEfirewall2 stop, then SuSEfirewall2 start, which for me has always worked. For some reasons unknown to me (and since the fix was just as easy) this seems to flush the rules and works better than a restart. YMMV. HTH. -- Joe Morris Registered Linux user 231871 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Chiu, PCM (Peter) wrote:
Thanks, Joe,
Maybe a mix-up on terminalogy used.
I did restart firewall by invoking
/etc/init.d/SuSEfirewall2_init restart
and
/etc/init.d/SuSEfirewall2_setup restart
-----Original Message----- From: Joe Morris (NTM) [mailto:Joe_Morris@ntm.org]
Since you seem to indicate it IS a firewall issue, and not a PAM issue, I would suggest doing what many of us are doing (but which seems to be a bug), and that is SuSEfirewall2 stop, then SuSEfirewall2 start, which for me has always worked. For some reasons unknown to me (and since the fix was just as easy) this seems to flush the rules and works better than a restart. YMMV. HTH.
Please do not top post, as it messes up the conversational style of email exchange. I think you misunderstood what I was saying. Since a long time ago (and recently mentioned on the security list), it was my experience that your commands above do not always work, while the ones I gave you (above) do. -- Joe Morris Registered Linux user 231871 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I can't be the only one who prefers top posting....I get so many e-mails on the lists I'm on, I tend to want to read the comments of the author of the e-mail sent....If I'm interested in reading any background or what the problem was/is with which he/she's trying to assist, I can then scroll down. I don't want to have to scroll down to read the comments of the e-mail I'm receiving. But, maybe that's just me... Rob Joe Morris (NTM) wrote:
Chiu, PCM (Peter) wrote:
Thanks, Joe,
Maybe a mix-up on terminalogy used.
I did restart firewall by invoking
/etc/init.d/SuSEfirewall2_init restart
and
/etc/init.d/SuSEfirewall2_setup restart
-----Original Message----- From: Joe Morris (NTM) [mailto:Joe_Morris@ntm.org]
Since you seem to indicate it IS a firewall issue, and not a PAM issue, I would suggest doing what many of us are doing (but which seems to be a bug), and that is SuSEfirewall2 stop, then SuSEfirewall2 start, which for me has always worked. For some reasons unknown to me (and since the fix was just as easy) this seems to flush the rules and works better than a restart. YMMV. HTH.
Please do not top post, as it messes up the conversational style of email exchange. I think you misunderstood what I was saying. Since a long time ago (and recently mentioned on the security list), it was my experience that your commands above do not always work, while the ones I gave you (above) do.
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 14 November 2006 22:15, RTF wrote:
I can't be the only one who prefers top posting.... Yes, its the convenient lazy way to post and all of us appreciate the tendency, but please don't do it.
For one, it breaks protocol ... you know, when in Rome... For another, its messes up the natural conversational style of threads... and, for what its worth, why deliberately push folks buttons... without a good reason... ? -- Kind regards, M Harris <>< --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Nov 14, 2006 at 11:15:32PM -0500, RTF wrote:
I can't be the only one who prefers top posting....I get so many e-mails on the lists I'm on, I tend to want to read the comments of the author of the e-mail sent....If I'm interested in reading any background or what the problem was/is with which he/she's trying to assist, I can then scroll down. I don't want to have to scroll down to read the comments of the e-mail I'm receiving.
But, maybe that's just me...
Irrelevant. This list has determined that topposting is not wanted. Neither is posting in HTML for that matter. See my sig for relevant information. houghi -- To have a nice mailinglist experience, follow the guidelines below:
Please do not toppost. Please turn off HTML Read http://en.opensuse.org/Opensuse_mailing_list_netiquette Read http://www.catb.org/~esr/faqs/smart-questions.html
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (10)
-
Anders Johansson -
Chiu, PCM (Peter) -
Darryl Gregorash -
houghi -
Joe Morris (NTM) -
Justin M -
M Harris -
Peter Bloomfield -
Puneit Singh -
RTF