SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Currently I've openSuse 10.1 installed. As we all know it wasn't the best Suse edition released, but with some work you could get around the problems experienced.
However, now I'm wondering, how much better is 10.2 compared to 10.1? Is it really worth downloading and burning? Will I notice any major differences (performance, quality, etc.)?
After some troubles during my upgrade process, I'm pretty happy right now with my 10.2 system.
Caveat: I'm still exploring the changes right now (I just found that lineakd somehow has stopped working - dunno why yet). As a positive surprise, the YAST update mechanisms now work much smoother than in 10.1.
If your options are downloading and burning the 10.1-remastered CDs/DVD or downloading 10.2, I'd do 10.2. They've incorporated the Xgl and desktop features of the Commercial SuSE Novel product into 10.2.
Not sure if this is the relevant thread, but it seemed like a good place to start...
The biggest problem I'm having...I DIDN'T have with 10.1.
I have actually installed 10.2 on three different systems and EACH ONE has had the very same problem.
SAMBA DOESN'T WORK.
Any time I look at settings involving the Samba services, it says that the service 'is not configured' or any number of messages that indicate that the kernel doesn't have Samba (smbfs) support built in.
To be clear...I'm a little pissed off because I can't even remove it and reinstall it without Yast wanting to remove HALF of the goddamn operating system WITH it. (Especially where Gnome packages are concerned.) I tried downloading the newest (stable) source and recompiling...which it did successfully. NO EFFECT. Nothing changed.
If I use a URL such as "smb://Username@IP/share/folder" it actually allows me to browse the shares on my Windows server. However, in order to get MP3's to work in Amarok without having to transfer them to the HDD first, I have to mount the network share locally as an SMBFS mounted folder. (Amarok still sucks at streaming, apparently.) Upon trying to mount the remote share as a local folder using the SMBFS file type, it tells me that the kernel doesn't have built-in SMBFS support. I even downloaded and installed Samb4k to assist me in mounting the shares. It sees them, but it will only browse the share one folder deep before it gives me the usual error message.
I KNOW for a fact that Samba is installed. Since I started using Linux in 2000, I have ALWAYS checked any and all packages related to Samba.
It occurs to me that this isn't just a contained issue since I have installed 10.2 on three of my different machines and got the EXACT SAME RESULTS. I got perfect support for DVD and MP3's installed. I can play MP3's in Amarok. Just not when they're streamed. (It crashes Amarok when I try to play them directly from the share.)
It also occurs to me that Samba is related to MS's network sharing protocol...and MS got all bent out of shape during the development of 10.2...and Novell went and signed a contract with MS about this or that, "PLEASE DON'T SUE OUR USERS." etc.
Anyone else smell BS? I've NEVER had a problem with Samba until NOW. So it strikes me as a bit ODD.
A problem that a lot of people including myself are having right now is the printer driver installer hanging. This started to show up about December 18th and has not been resolved yet.
The manpage for mount has documentation on cifs. There is also a cifs.txt file in the kernel source documentation.
Quote:
This is the client VFS module for the Common Internet File System (CIFS) protocol which is the successor to the Server Message Block (SMB) protocol, the native file sharing mechanism for most early PC operating systems. CIFS is fully supported by current network file servers such as Windows 2000, Windows 2003 (including Windows XP) as well by Samba (which provides excellent CIFS server support for Linux and many other operating systems), so this network filesystem client can mount to a wide variety of servers. The smbfs module should be used instead of this cifs module for mounting to older SMB servers such as OS/2. The smbfs and cifs modules can coexist and do not conflict. The CIFS VFS filesystem module is designed to work well with servers that implement the newer versions (dialects) of the SMB/CIFS protocol such as Samba, the program written by Andrew Tridgell that turns any Unix host into a SMB/CIFS file server.
I agree that the samba setup in SuSE can be troublesome. If you install the samba-doc package, the Samba 3 Reference & Howto and the Samba 3 by Example books are supplied in pdf and html form in /usr/share/doc/packages/samba. Also, you can use samba swat to configure and monitor networking.
Two common problems are the firewall settings, and a service such as nmbd or winbind not running. ( The later is if you used WINS in your configuration.
Another problem is that the networking model that Win95 uses is different than the model that Win NT uses is different then what XP uses. Also, your home router may not supply NetBIOS name resolution, or you may be using static addresses. If that is the case, you need to enable NetBIOS over TCP/IP on the XP machines and make sure that "disable NetBIOS = yes" isn't in your smb.conf file ( The default is no.) Another problem is if each samba host is configured to be the master browser.
Also make sure that you don't have the Netware protocol installed on an older windows machine, or it will always win the elections, which may not be what you want.
so far opensuse 10.2 seems to be much better.
Just do not update cups yet - there are some serious issues with 1.2.7-3.2 and 1.2.7-3.3 on 3 systems I own. Others are experiencing many of the same problems. http://www.linuxquestions.org/questi...d.php?t=512656
Hopefully this sill be solved soon. Either way the cups that ships with 10.2 does work ( at least for me)
To the OP:
10.2 is superior to 10.1 in nearly every way and is well worth the upgrade. The speed increase alone made it worthwhile for all of my computers, some of which are pretty old. If you simply add the "opensuse current" directory on your favorite mirror to YaST or Smart or YumEX whatever and update all available packages you will automatically upgrade to 10.2 without having to download an iso or even reboot your computer (until after the upgrade is complete, anyway).
This kind of upset me:
Quote:
Originally Posted by cyryl_the_wolf
Not sure if this is the relevant thread, but it seemed like a good place to start...
The biggest problem I'm having...I DIDN'T have with 10.1.
I have actually installed 10.2 on three different systems and EACH ONE has had the very same problem.
SAMBA DOESN'T WORK.
*profane, irrelevant, infalmmatory, conspiracy-theorist, and only partially exlpanatory rant snipped*
Anyone else smell BS? I've NEVER had a problem with Samba until NOW. So it strikes me as a bit ODD.
Whatever. I just want to fix the problem.
samba is deprecated... COMPLETELY. This is not a legal issue and has nothing to do with MS, Gates, Windows, Nazis, or the price of rice in China. Distros that are still including samba support in the kernel are phasing it out more slowly than Novell. That's all. Follow these steps:
1. un-knot your panties.
2. open /etc/fstab in your favorite text editor (as root)
3. change your samba lines to use CIFS instead, like so:
Code:
OLD
//192.168.1.2/mp3 /mnt/mp3 smbfs auto,credentials=/root/.credentials,uid=1000 0 0
NEW
//192.168.1.2/mp3 /mnt/mp3 cifs auto,credentials=/root/.credentials,uid=1000 0 0
(notice the change in the FS option value?)
4. type "mount -a" at a command line (as root or sudo)
See? Wasn't that simple? CIFS is a newer network protocol that is backwards compatible with the formally deprecated samba. A quick search of this very forum would produce lots of threads (including one started by me) wherein people have run into this problem since 10.2's release and found the solution I just told you without having a hissy and pointing fingers at Bill Gates or Novell or whoever you feel the need to blame/flame.
//moderator removes content found in violation of the LQ Rules and general netiquette.
So the Samba project is no longer maintained, eh? I DID NOT KNOW THAT. Amazing. So... What's to replace it then? How are we going to maintain Windows sharing functionality then? Anyone know? (One could ASSUME CIFS. Personally, I have never heard of it. I will be researching it.)
I mean... I'm asking because I'm not a 'linux guru' just yet and I'm so VERY afraid that someone might try to EDUCATE me whilst also going out of their way to TRY and make me feel STUPID at the same time; all the while making sure that I am NOT allowed to feel or express frustration without consequence...
Last edited by unSpawn; 01-18-2007 at 03:44 AM.
Reason: //content removal
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.