Changes

From SME Server
Jump to navigationJump to search
6 bytes removed ,  05:19, 9 February 2016
WIP
Line 12: Line 12:  
Ricks1950 - [https://forums.contribs.org/index.php/topic,52189.msg267676.html#msg267676 Source]
 
Ricks1950 - [https://forums.contribs.org/index.php/topic,52189.msg267676.html#msg267676 Source]
 
</blockquote>
 
</blockquote>
 +
      Line 18: Line 19:  
<br<br>
 
<br<br>
 
I am quiet capable ( now) of building any system from scratch but more often that not I throw in an e-smith server
 
I am quiet capable ( now) of building any system from scratch but more often that not I throw in an e-smith server
   
<br<br>
 
<br<br>
 
The reason for this is being demonstrated on this list right now. Careful consideration at development level allows ordinary, and lazy, users to throw in an e-smith and be confident that it will work just like it says on the tin.
 
The reason for this is being demonstrated on this list right now. Careful consideration at development level allows ordinary, and lazy, users to throw in an e-smith and be confident that it will work just like it says on the tin.
 
<br><br>
 
<br><br>
 
That is no mean feat and something that has been happening for a long time here. It takes huge effort to maintain that level of quality and consistency.  
 
That is no mean feat and something that has been happening for a long time here. It takes huge effort to maintain that level of quality and consistency.  
   
<br><br>
 
<br><br>
 
SME server release cycles make Redhat look like wild mad things. This can be seen as a problem. It can also be seen as a virtue. In over 15 years of e-smithery I have not once had a production system fail due to software error or hacked due to lax security. Isn't that cool?
 
SME server release cycles make Redhat look like wild mad things. This can be seen as a problem. It can also be seen as a virtue. In over 15 years of e-smithery I have not once had a production system fail due to software error or hacked due to lax security. Isn't that cool?
   
<br><br>
 
<br><br>
 
The server manager is old. It not accurately reflect how much has happened under the hood. It is clunky and ugly but it has one redeeming feature.
 
The server manager is old. It not accurately reflect how much has happened under the hood. It is clunky and ugly but it has one redeeming feature.
  −
   
<br><br>
 
<br><br>
 
It removes almost all technical verbiage from the user interface. Add a user, Add a group, Add an ibay. It just works and the user knows nothing about passwd, shadow and shells. No mention of DHCP, DNS and PPTP. Just "remote access"  
 
It removes almost all technical verbiage from the user interface. Add a user, Add a group, Add an ibay. It just works and the user knows nothing about passwd, shadow and shells. No mention of DHCP, DNS and PPTP. Just "remote access"  
 
<br><br>
 
<br><br>
 
Running setprop from the command line enable me to accurately and quietly set-up a major change on the server and then not activate it until it is all done. This is hugely advantageous in a production environment.
 
Running setprop from the command line enable me to accurately and quietly set-up a major change on the server and then not activate it until it is all done. This is hugely advantageous in a production environment.
   
<br><br>
 
<br><br>
 
From e-smith 4.04 onwards it has kicked bottom.  
 
From e-smith 4.04 onwards it has kicked bottom.  
   
<br><br>
 
<br><br>
 
Will get back on bug tracker.  
 
Will get back on bug tracker.  

Navigation menu