I wanted to make my own home server. Can I use opensuse as my home server? If can, can I dual boot with the desktop version of opensuse. I’m using opensuse 13.2 32 bit.
If can, can I dual boot the opensuse?
Your question is “a bit broad” - what type of services do you want to host and for what purpose?
Well, run the services you want on your openSUSE system. There is not realy a difference between “servers” and “clients” as those terms are used in the Microsoft World (were they run different operating systems if I understand that strange world correct). Every Linux system can run server software (and most do, even if you are not aware of it). And of course, when the system is not headless, you can use it as a desktop at the same time.
The desktop I am typing this on (running Firefox in KDE) is at the same time an NSF server, a HTP server (Apache), a printer server (CUPS) for all the systems in the house.
Only thing is that I should not switch it off during the hourse that people use their systems in the house rotfl!.
Technicaly, these are the server ports on my “desktop/server”:
boven:~ # netstat -tulp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 *:nfs *:* LISTEN -
tcp 0 0 *:33441 *:* LISTEN 1351/rpc.statd
tcp 0 0 *:rsync *:* LISTEN 1260/xinetd
tcp 0 0 *:mysql *:* LISTEN 1637/mysqld
tcp 0 0 *:sunrpc *:* LISTEN 1/init
tcp 0 0 *:mountd *:* LISTEN 1346/rpc.mountd
tcp 0 0 *:ftp *:* LISTEN 1260/xinetd
tcp 0 0 *:ipp *:* LISTEN 1256/cupsd
tcp 0 0 localhost:smtp *:* LISTEN 1804/master
tcp 0 0 *:49465 *:* LISTEN -
tcp 0 0 *:nfs *:* LISTEN -
tcp 0 0 *:54755 *:* LISTEN 1351/rpc.statd
tcp 0 0 *:sunrpc *:* LISTEN 1/init
tcp 0 0 *:www-http *:* LISTEN 1277/httpd2-prefork
tcp 0 0 *:mountd *:* LISTEN 1346/rpc.mountd
tcp 0 0 *:ipp *:* LISTEN 1256/cupsd
tcp 0 0 localhost:smtp *:* LISTEN 1804/master
tcp 0 0 *:36063 *:* LISTEN -
udp 0 0 *:44490 *:* 1351/rpc.statd
udp 0 0 *:mountd *:* 1346/rpc.mountd
udp 0 0 *:ipp *:* 1256/cupsd
udp 0 0 *:doom *:* 490/rpcbind
udp 0 0 localhost:703 *:* 1351/rpc.statd
udp 0 0 *:nfs *:* -
udp 0 0 *:sunrpc *:* 1/init
udp 0 0 boven.henm.xs4all.n:ntp *:* 1343/ntpd
udp 0 0 localhost:ntp *:* 1343/ntpd
udp 0 0 *:ntp *:* 1343/ntpd
udp 0 0 *:53567 *:* -
udp 0 0 *:mountd *:* 1346/rpc.mountd
udp 0 0 *:doom *:* 490/rpcbind
udp 0 0 *:nfs *:* -
udp 0 0 *:42018 *:* -
udp 0 0 *:sunrpc *:* 1/init
udp 0 0 2001:980:91a0:1:99f:ntp *:* 1343/ntpd
udp 0 0 2001:980:91a0:1:21b:ntp *:* 1343/ntpd
udp 0 0 fe80::21b:fcff:fe7f:ntp *:* 1343/ntpd
udp 0 0 localhost:ntp *:* 1343/ntpd
udp 0 0 *:ntp *:* 1343/ntpd
udp 0 0 *:46416 *:* 1351/rpc.statd
boven:~ #
As you see FTP and Rsync and NTP are also available.
Can you show me how to do it? Because I’m still newbie here.
For client and server for my home.
To show what? What are you trying to achieve?
to set opensuse as home server beside as desktop
This is too vague.
My desktop (where I am typing this) is also my home server. And, what I mean by that is:
It is sharing some files with NFS for all home linux systems to access;
It is sharing the same file system with Samba, for Windows systems to access;
I have the mail server listening on the external port, so that other home system could use it for email (though none is using it that way at present);
It is running “sshd” as a kind of hub server so that other systems (linux and Windows) can login or copy (scp) files from there.
I am not currently running a DNS server there, though I have in the past. At present, I’m satisfied with the home router for providing a DNS forwarder and for DHCP services.
So now explain what you are wanting to achieve. It will be easier to give advice or make suggestions if we know what you want to achieve.
As said above. What do you nean by a home server? If you have a definition what a home server is, please share it with us.
In Unix/Linux and the internet you have server programs (and corresponding client programs). In general, when the main task of a computer is to run one or more of those server programs it may be called a “server”. But that does not say very much (may also be used as a “desktop” or not, may be located in a “server room” or “computer room” or not, etc.)
So please define each and every service you want to run (examples named by nrickert and me above in several posts) and we might be able to help you to set it up.
I would suggest your first step is to design your network, that would include who is going to belong to the network and what role you want each member to play in the network. Grab yourself a pencil and some paper and write down the information for each ‘member’, such as which operating system it uses, what it’s ‘name’ is, etc. Gather as much info as you can and document it. Document everything. Once you know the members you need to assign IP addresses and subnet masks to them. Whether you use DHCP to give them addresses or you give them static IP’s is a matter of choice (the exception is the router which is and should remain static). Next, whether you choose DHCP or static, you will need to select a proper ‘private’ IP address range. A quick search will tell you which IP addresses are ‘private’ and which are ‘public’. In my case, I only have 3 computers, all hardwired to the network so static assignment is suitable for me. They are assigned- Router: 192.168.10.1, comp1: 192.168.10.2, comp2: 192.168.10.3, comp3: 192.168.10.4 and all with a subnet of 255.255.255.0. Once the IP addresses are assigned (again, whether static or DHCP or combination) you should ‘ping’ each computer from each computer to make sure they see each other. You may have to enable ‘ping’ depending on the OS if so, enable it, run your tests and then disable it again. At this point, your network foundation has been laid. You still need to assign them all to the same ‘workgroup’ (windows) and or domain.
I will echo what has already been said. Unless you are running a Windows Server ( and honestly, even if you are), any ‘server’ functions you want to perform, let the Linux machine handle them. So much easier :-). Oh, and did I mention, Document Everything!
First, regarding “server” and “desktop” or “workstation”
It’s not just a Microsoft thing, to a certain degree you “tune” your install for different uses in openSUSE by selecting the appropriate kernel. On openSUSE, a Desktop/Workstation tuned kernel is installed by default. I haven’t looked at the kernel details recently, but I would expect like most other kernels(including Microsoft) would modify thread priority to favor non-background processes. But, on a SOHO (Small Office/Home Office) deployment, the desktop kernel is just fine.
As others have described, there are many types of SOHO “server” configurations, mainly defined by provided “network services” (various functionality remote machines can use). I’d expect you can find typical lists of network services by simply Googling so I won’t try to create a short list of typical services. You’ll find that any on such a list can be installed on openSUSE.
openSUSE currently doesn’t really have a “typical home server” setup(although I suppose it woudn’t be too difficult to create one). If you’re looking for a typical pre-designed setup, SUSE will sell you an easy to setup Server for very low cost
https://www.novell.com/products/openworkgroupsuite/smallbiz/
But, people who do something similar on openSUSE are typically the folks who don’t mind selecting, designing and building every component.
Lastly, if this is a <very> small home office, you may want to run your Server simultaneously with your Desktop. Instead of multi-booting which means that you can only run one OS at a time, you might consider virtualization so you can run both at the same time. Or, if you are willing to step into a bit of advanced leading edge technology, consider Docker for simultaneous running OS.
TSU
On Wed, 24 Dec 2014 10:46:01 +0000, mki wrote:
> I wanted to make my own home server. Can I use opensuse as my home
> server? If can, can I dual boot with the desktop version of opensuse.
> I’m using opensuse 13.2 32 bit.
Sure.
But “home server” is a broad definition. What do you want to be able to
“serve”? Files? Web services? FTP services? Print services? Share a
scanner? Hosting databases? Acting as a voice mail server/PBX?
Being a “server” can mean a lot of different things, as you can see from
the above far-from-complete list. 
And no need to dual boot - you can use server services with the desktop.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
1.web server
2.mail server
3.database server
4.ftp server
5.dns server
6.imap server
7.web site statistic
I have 1 computer with opensuse 13.2 connected via wire to router, 1 netbook with Windows 7 professional, and 1 notebook with Opensuse 13.2 connected wireless on router.
On Wed, 24 Dec 2014 21:56:02 +0000, mki wrote:
> 1.web server 2.mail server 3.database server 4.ftp server 5.dns server
> 6.imap server 7.web site statistic
Yes, that can be done. Start by installing the packages. Again, still
pretty generic - you haven’t stated what your goals are.
The default configurations are often sufficient for many needs, so start
with installing the packages, and then ask specific questions about
things you’re having problems with, each issue or group of related issues
in their own thread.
You’re not giving people a lot to go on, other than “walk me through how
to configure everything” - which doesn’t demonstrate having searched for
existing tutorials at all. I don’t like to use the phrase “Google is
your friend”, but in this case, Google is going to be an excellent place
to start. “site:opensuse.org” can also be a useful way of constraining
the search to openSUSE sites, including the wiki, documentation, forums,
and so on. There is a lot of information already out there that you will
find useful.
Jim
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Thank you for your advice
personally i recommend other distro ’ s like:
centos
ubuntu server
fedora server
although opensuse is suitable as a server too.
There are many pitfalls when seting up a server
like how to secure and hardening the server for example
an other issue is using it as a headless server or not.
i recommend , in your case, opensuse without kde, but with ssh access
some basic knowldge of if this is required
I think opensuse is enough for learning media to set up home server.
If you set up your Server services on openSUSE, you’ll have a easy to use tool for setting up the other distros listed don’t have… YAST.
Install the YAST applets and you’ll have those Server apps running very quickly.
TSU