Hello, My name is Terje J. Hanssen and I will welcome this new and interesting openSUSE server project. I'm not a very skillfull server sysadmin, and look forward to learn more from this project. As a user of openSUSE/SLES/OES2, and a tester of openSUSE, it might be of interest for me to test this openSUSE flavor as HO server, if possible. In my opinion, one of SUSE's/SLES's strengths also on the server side has always been the option to select between text and YaST gui interfaces. Of course pure text interface is important, but I would suggests to keep the option to select gui. Shouldn't finally WebYaST have a nice opportunity to be applied on this openSUSE server flavor? Is there any documentation over package content and the pre-configurations that has been made for the invis server? Beyond being free software, what will typically differ this openSUSE server flavor from the commercial Novell Open Workgroup Suite - Small Business Edition (NOWS-SBE) and i.e. from a competitor like the Ubuntu server? Terje J. Hanssen -- To unsubscribe, e-mail: opensuse-invis+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-invis+help@opensuse.org
Hello Am 29.10.2010 00:39, schrieb Terje J. Hanssen:
Hello,
My name is Terje J. Hanssen and I will welcome this new and interesting openSUSE server project. I'm not a very skillfull server sysadmin, and look forward to learn more from this project. As a user of openSUSE/SLES/OES2, and a tester of openSUSE, it might be of interest for me to test this openSUSE flavor as HO server, if possible. You're welcome ;-)
In my opinion, one of SUSE's/SLES's strengths also on the server side has always been the option to select between text and YaST gui interfaces. Of course pure text interface is important, but I would suggests to keep the option to select gui. Shouldn't finally WebYaST have a nice opportunity to be applied on this openSUSE server flavor? To have the option to select an installation with GUI is absolutely ok. I think that we need the option to install a gui for other reasons too. The list of packages i mentioned in my mail was just a draft proposal for our start.
But what i don't want is a desktop-discussion like at the openSUSE project a few month ago. A second point. In my opinion installing a GUI should not be the standard on a Linux-Server installation. Most servers i work with didn't have monitor, mouse and keyboard or KVM-console connected. Running a GUI by default is a waste of resources. WebYaST on the other hand is very interesting. Our own user- and administration-interface "invis portal" is web based.
Is there any documentation over package content and the pre-configurations that has been made for the invis server?
What we have is a documented setup-script and a collection of pre-configured configuration files. We have no written list of installed packages. I think, that i should work this out. Additional we install some third party software which is not packaged for openSUSE yet. The whole documentation of the project is a german wiki-page (http://wiki.invis-server.org).
Beyond being free software, what will typically differ this openSUSE server flavor from the commercial Novell Open Workgroup Suite - Small Business Edition (NOWS-SBE) and i.e. from a competitor like the Ubuntu server?
The main difference is that invis servers points to (very) small business companies without any IT-knowhow. This is a very big target group in germany and i think in other european countries as well. The other server products are mostly downscaled enterprise products which didn't fit the recommendations of small business companies. (It's difficult for me to explain this in english, i haven't enough practice... )
Terje J. Hanssen
Stefan Schaefer -- www.invis-server.org Stefan Schäfer Vogelsbergstr. 27 63679 Schotten -- To unsubscribe, e-mail: opensuse-invis+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-invis+help@opensuse.org
Den 29. okt. 2010 10:32, skrev Stefan Schäfer:
Hello
Am 29.10.2010 00:39, schrieb Terje J. Hanssen:
Hello,
My name is Terje J. Hanssen and I will welcome this new and interesting openSUSE server project. I'm not a very skillfull server sysadmin, and look forward to learn more from this project. As a user of openSUSE/SLES/OES2, and a tester of openSUSE, it might be of interest for me to test this openSUSE flavor as HO server, if possible. You're welcome ;-)
Thank you :)
In my opinion, one of SUSE's/SLES's strengths also on the server side has always been the option to select between text and YaST gui interfaces. Of course pure text interface is important, but I would suggests to keep the option to select gui. Shouldn't finally WebYaST have a nice opportunity to be applied on this openSUSE server flavor?
To have the option to select an installation with GUI is absolutely ok. I think that we need the option to install a gui for other reasons too. The list of packages i mentioned in my mail was just a draft proposal for our start.
But what i don't want is a desktop-discussion like at the openSUSE project a few month ago. A second point. In my opinion installing a GUI should not be the standard on a Linux-Server installation. Most servers i work with didn't have monitor, mouse and keyboard or KVM-console connected. Running a GUI by default is a waste of resources.
I fully or mostly agree here. Without going into details, what I also thought of is to have the neccessary peaces and software patterns available to apply it as a terminal server and/or application server use - on demand. A good reference article I like is this one that emphasize the native available options on demand to switch between run level 5 with gui and run level 3 multiuser without gui. http://www.novell.com/communities/node/6669/rdp-linux-managing-gui-displays-...
WebYaST on the other hand is very interesting. Our own user- and administration-interface "invis portal" is web based.
Yes, also my mentioned NOWS-SBE based on SLES supply a web based interface as shown here http://www.novell.com/documentation/nows/nows_admin_install/data/bb3fhcd.htm...
Is there any documentation over package content and the pre-configurations that has been made for the invis server?
What we have is a documented setup-script and a collection of pre-configured configuration files. We have no written list of installed packages. I think, that i should work this out. Additional we install some third party software which is not packaged for openSUSE yet.
The whole documentation of the project is a german wiki-page (http://wiki.invis-server.org).
One task will be to translate a wiki to English, as my German reading isn't good enough :)
Beyond being free software, what will typically differ this openSUSE server flavor from the commercial Novell Open Workgroup Suite - Small Business Edition (NOWS-SBE) and i.e. from a competitor like the Ubuntu server?
The main difference is that invis servers points to (very) small business companies without any IT-knowhow. This is a very big target group in germany and i think in other european countries as well. The other server products are mostly downscaled enterprise products which didn't fit the recommendations of small business companies. (It's difficult for me to explain this in english, i haven't enough practice... )
Good example and I fully agree. I think small scale thinking beside user friendly gui are important reasons why Windows servers has had success with growing from small business companies and upwards. I myself am working in a small office within civil engineering in Norway, just with less than 10 employees. Terje J. Hanssen -- To unsubscribe, e-mail: opensuse-invis+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-invis+help@opensuse.org
On Friday 29 October 2010 10:32:10 Stefan Schäfer wrote: Hi,
But what i don't want is a desktop-discussion like at the openSUSE project a few month ago. A second point. In my opinion installing a GUI should not be the standard on a Linux-Server installation. Most servers i work with didn't have monitor, mouse and keyboard or KVM-console connected. Running a GUI by default is a waste of resources. Agreed, no desktop discussion here.
WebYaST on the other hand is very interesting. Our own user- and administration-interface "invis portal" is web based.
Is there any documentation over package content and the pre-configurations that has been made for the invis server? What we have is a documented setup-script and a collection of pre-configured configuration files. We have no written list of installed packages. I think, that i should work this out. I digged a bit into that and read a bit in sine, the install script. Find attached a list packages that get explicitely installed, some
Maybe that could be merged in the very very long run ;-) patterns and from which repos. Later on in the installation process, more packages get installed depending on users choice. I did not investigate that yet. I think our first action should be to strip down the number of used repositories. For that, we should work towards moving most of the stuff to openSUSE:Factory. Only special packages should remain in an invis repo which need to be created. In best case we shouldn't need more repos. Stefan which packages did I miss? Do we really use all repos?
Additional we install some third party software which is not packaged for openSUSE yet. Which are these? Can somebody start over to work on packages?
regards, Klaas
Den 29. okt. 2010 18:13, skrev Klaas Freitag:
On Friday 29 October 2010 10:32:10 Stefan Schäfer wrote:
Hi,
But what i don't want is a desktop-discussion like at the openSUSE project a few month ago. A second point. In my opinion installing a GUI should not be the standard on a Linux-Server installation. Most servers i work with didn't have monitor, mouse and keyboard or KVM-console connected. Running a GUI by default is a waste of resources. Agreed, no desktop discussion here.
Even that 'standalone desktop discussion' of course is beyond the scope here, related client-server configurations are of more interest and importance. Servers are not isolated but has the purpose to supply useful services for users on networked clients. Sometimes specific configurations and setup on the client side are required to obtain this. And as already mentioned, small companies most often don't have such IT-knowledge, either it is Windows or Linux clients. A couple of client/server configuration examples from my own experience: Single logon: that is login on the dekstop client should automatic give transparent access to the network server. Using Samba shared file access, the user will usual (default) be asked for another logon/password. (The Novell client for OES2 is more streamlined and has more features, but is never available for the latest openSUSE release). Starting OpenVPN on the client side in a terminal requires root password. The practical and user friendly use of OpenVPN, is when it is setup to be startet from Network Manager. Terje J. Hanssen -- To unsubscribe, e-mail: opensuse-invis+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-invis+help@opensuse.org
participants (3)
-
Klaas Freitag -
Stefan Schäfer -
Terje J. Hanssen