Hello SUSErs,
I have been piling up some old PC and wanted to put one to good use.
Thought I’d make a server and practise some cms website building, so naturally i went with openSUSE 12.3 x86.
Being a noob in serverland I started to read and configure one step at the time. Finally got a Joomla installation done and ran into problems with pure-ftp, file permissions, users, groups, ftp user adding. I successfully made a no-ip account with a free domain and made the server visible from the internet. No hosting fees right. I want to do it right so some bored hacker doesnt stumble upon my server and exploits it.
Then I wanted to search the forum and there is no specific home server tutorial, there are a few SUSE Studio appliances but when its all dumbed down for you how can you fix when something goes wrong.
So is someone willing to write a few steps to install and configure Apache, MariaDB, FTP and prepare htdocs for cms installation from a fresh 12.3 ssh enabled server installation?
The idea of calling a computer a “server” is IMHO pur MS lingo, where MS even has different operating systems from those that are called Personal Compters/desktops/laptops/…
In Unix/Linux client server means something complete different and is TCP/IP oriented. There are server functions that are programs/processes (in this context mostly called deamons) running on a system and listening on a TCP/IP port, ready to serve other programs/processes running on the same or on other systems. And all of those can be (and are) mixed on both systems.
Thus I have an HTTP server (Apache) running on the system that sits on my desktop and that I am using right now, typing this in a HTTP client program’s (Firefox) window using the HTTP service on forums.opensuse.org HTTP server. In fact almost all the openSUSE systems ar serving something. Often they are a CUPS server. Often rsync server, often SSH server, most of them run an X-server, etc.
Thus there is no real difference setting up a service on a computer room system (that is what MS oriented people call a “sever” IIRC) or on a desktop.laptop system. Thus when you want to set up e.g. LAMP server, you search for information and howtos on how to install and run a LAMP service., not for howtos on “a server”.
The only thing that sometimes is done (specialy with older/smaller systems) is starting from texst only installation. But as even YaST runs on such an installation through it’s ncurses interface, that does not realy make things different.
So is someone willing to write a few steps to install and configure Apache, MariaDB, FTP and prepare htdocs for cms installation from a fresh 12.3 ssh enabled server installation?
Thus there is no real difference setting up a service on a computer room system (that is what MS oriented people call a “sever” IIRC) or on a desktop.laptop system. Thus when you want to set up e.g. LAMP server, you search for information and howtos on how to install and run a LAMP service., not for howtos on “a server”.
So your answer would be you have it setup and dont like the way I express myself so you lecture me about it.
Thank you
I think you missed my point. My point is that it is of no use to search for (or ask for) howtos on Linuxx “server” systems in general, because they do not realy exist. You must look for (and eventual ask for) howtos on those service functions you like to implement.
IMHO this gives you a far better chance to reach your goal in a shorter time. And I guess that is what you are after.
Henk’s point is that in the linux world there’s no actual difference between a server and a desktop install. The stuff is all there. For example: my laptop could hardly be called a server. Yet I run a LAMP (Linux Apache MariaDB PHP) server on it, an NFS server plus whatever other server functionality I need.
Search the forums for “LAMP”. I’ve written a couple of posts on how to quickly setup a LAMP server, they should still be out there.
I get the point but setting up a cms on a “dedicated machine” seems to be all over the place, on top of that pure-ftp, MariaDB have there own quirks in 12.3. And my lack of permissions setup knowledge to write into htdocs from a joomla /administrator is proving to be quite a challenge.
I was just wondering how great would it be to have helpful articles like that. Planet and Lizards is great but it gets buried quickly. Docs are a good read but sometimes it gets quite technical for my understanding. Most of the time I read articles from other distros and the procedures aren’t the same, file structure a differ.
Eventually Ill get there but every so often I get tempted to try a different distro for the job. I we all here now thats unnecessary, right.
Knowledge of basic things like file permissions is of course needed. But that is needed on all systems. It is basic Unix/Linux knowledge. Nobody ever will catagorize that as specific to systems which have serving a their main task.
And there are many documents on Linux file permissions on the internet. No need even to look for openSUSE specific, not even for Linux specific. This is the same in Unix for already more then 40 years.
Thank you for your time gentleman, this LAMP is a weekend project, Im shure all of you remember your first encounter with such tasks. Just hope this doesn’t turn out to be a summer project for me.
On 2013-05-18 17:56, SLK021 wrote:
>
> hcvv;2557926 Wrote:
>> Knowledge of basic things like file permissions is of course needed. But
>> that is needed on all systems. It is basic Unix/Linux knowledge. Nobody
>> ever will categorize that as specific to systems which have serving a
>> their main task.
>>
>> And there are many documents on Linux file permissions on the internet.
>> No need even to look for openSUSE specific, not even for Linux specific.
>> This is the same in Unix for already more then 40 years.
> Thank you for your time gentleman, this LAMP is a weekend project, Im
> shure all of you remember your first encounter with such tasks. Just
> hope this doesn’t turn out to be a summer project for me.
It is a decade long project. >:-)
You can not attempt to create a LAMP server in Linux without learning
first how things like the permissions system in Linux works.
And no, you will not find a howto worth of the time spent on reading it
that teaches you how to set up a any server (service) on any Linux
without assuming that you already know how to set permissions, and many
other basic things that I will not even name.
Remember: Linux is not Windows.
Example: this is a desktop machine at my home, and it has an email
server (both smtp and imap, plus antispam/malware), an apache server, an
ftp server, an nfs server, a samba sever, a print server, a database
server, a domain name server… I’m sure I forget some.
Even my laptop is also a server.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
A long long time ago in a forum not to terribly far away I was linux_learner and wrote a Linux Security Overview. You can find it here; SE-02: Linux Security Overview - MandrivaUsers.org No one can tell you how to secure your system, but with some understanding, you can make wise choices. I give this to help the OP understand permissions (as this will be a big part of their project).
On 05/19/2013 12:46 AM, SLK021 wrote:
> Think i’m into deep with my project.
just takes some qualities not always displayed by all
people…things like patience, persistence, willingness to read,
attention to detail…etc…the same qualities that might lead to
become a (say) teaching Professor with a Doctorate in Astrophysics,
rather than a (say) McDonald’s French Fry Guru…
walk before you run…there is lots to learn.
–
dd
openSUSE®, the “German Engineered Automobile” of operating systems!
> The idea of calling a computer a “server” is IMHO pur MS lingo, where MS
> even has different operating systems from those that are called Personal
> Compters/desktops/laptops/…
Actually, like many other things, Microsoft “borrowed” the idea of a
dedicated server from another company. In this case, IIRC, it was Novell.
Novell pioneered the idea of PC-based networking (though their first
platform was the M68K platform) with NetWare. Prior to that, “servers”
had typically been mainframes with terminals connected to them - PC-based
networking came about in the late 80’s. NetWare, IBM PC Net, and Lantastic
are a few systems that predate Windows’ use as a dedicated server
(Lantastic arguably was more peer-to-peer, but usually was implemented
with a dedicated server regardless).
Computers as servers is not an MS invention, and it’s in fact common even
with Linux boxes.
That is different from client-server communications, though, which use a
service that listens on a TCP/UDP port (or once upon a time, an IPX/SPX
port).
Instead of re-inventing the wheel you should download an already working server from SUSE Studio and then figure out how to use and secure it for your needs. The search function on that site sucks so make sure you look by date and maybe soho or media. You can even make your own server there.
for me.