cifs?

[flymail]

I see that System Services (Runlevel) [package yast2-runlevel] has been dropped from the default YaST in openSUSE 13.1.
Since cifs is not enabled by default and the only way to activate it through YaST is via System Services (Runlevel), I
wonder whether this reflects an intent of cifs to become deprecated and subsequently obsoleted. I hope not.

[john_hudson]

My guess would be that this is more to do with the maturity of SAMBA, CIFS being an integral part of SAMBA.

You can enable CIFS with mount or in /etc/fstab anyway.

See this thread also: http://forums.opensuse.org/english/get-technical-help-here/network-internet/492372-opensuse-13-1-cifs-fstab-trouble.html

[eng-int]

@flymail

I see that System Services (Runlevel) [package yast2-runlevel] has been dropped from the default YaST in openSUSE 13.1.

That depends on how you installed 13.1. You can use YaST to install the package yast2-runlevel.

[jdmcdaniel3]

@flymail

I see that System Services (Runlevel) [package yast2-runlevel] has been dropped from the default YaST in openSUSE 13.1.
Since cifs is not enabled by default and the only way to activate it through YaST is via System Services (Runlevel), I
wonder whether this reflects an intent of cifs to become deprecated and subsequently obsoleted. I hope not.

For help in setting up Samba, see my blog complete with bash script to setup, configure and diagnose problems with Samba up to version 4.1 and openSUSE 13.1:

S.A.C.T. - Samba Automated Configuration Tool - Version 1.06 - Blogs - openSUSE Forums

Thank You,

[nrickert]

@flymail

I see that System Services (Runlevel) [package yast2-runlevel] has been dropped from the default YaST in openSUSE 13.1.
Since cifs is not enabled by default and the only way to activate it through YaST is via System Services (Runlevel), I
wonder whether this reflects an intent of cifs to become deprecated and subsequently obsoleted. I hope not.

There’s a Yast “Services Manager” which seems to allow setting up services.

I setup a Samba server (via Yast Network Services), and that part was taken care of automatically. However, it didn’t work. It seems that AppArmor is blocking Samba. For the time being, I have turned of AppArmor, till I work out how to configure it to allow an SMB server.