The last 12 month have been a „golden“ time of the upcomming embedded linux devices, but the custom OS’s offers some problems, you should know for projects:
embedded PC’s like the ARM based pi2 / pi3 uses a own compiled OS
not every known debian package is available
not all compile scripts to rebuild are available on git
slow performance can let you run into unuseable problems (heat, load, I/O), correct written scripts run into freezes without any error made by you!
you should take time for a closer look at buying them
calc the costs of non-x86 systems, later you cant often upgrade, cause embedded systems are not made for
dealers take too much money for less performance!
embedded devices can’t be grown up for additional precs like compression based on chips!
embedded devices need less energy, but can hangup by load over 65%, cause no cooling
the are made for learning and small control jobs
for NAS / Server jobs take x86 m-atx / micro-atx, cause you can access easy full debian packages
not all python + libs packages are available to run projects (example: acd_cli amazon cloud nas backup)
current embedded pc livetime at multimedia usage may be 24month cause to much and faster changes
May be that the arm os package trees may grow up, then we can talk again, but current x86 is the cheapest way to build systems without stress! And you have always the reserve to buildin new things of hardware..
Today the Point of Security and encrypted Webserver Communication is rolling over every User who hosts own Websites on the Internet. Last decades HTTPS was only used by Online Login Pages like Shops and Banks to verify the Communication between a User PC and the Website. But after January 2015 the most Search Engines like google decides to force index of Websites with HTTPS Protocol. The Background is that a TLS encrypted Connection isn’t easy to track and to force „drive-by-load-Viruses“ to the Website Visitors.
But a lot of Webmasters of the Opensource Community were angry about this handling. Thats is not real problem if you won’t buy a SSL/TLS Certificate. Every Webmaster can create a self signed Certificate on his Webserver if he is able to login via ssh and to config the Webserver like Apache. Self signed Certificates are warned by the Webbrowsers at the only first view, but if the User wants to install the Certificate the Browser isn’t warning next visits!
The Search Engines like Google don’t check the trust of the Certificates by the robots and so your Site will be good placed on the Index like the last decades. The ONLY thing is that you MUST move all Files,Images, Internal Links and Bookmarks to „https://“ that the „LOCK“ of the Browser Dialog is „CLOSED“ and „GREEN“ like on the Picture .
Of course if you want, you can buy and install „Domain Name Trusted“ Certificates, but if you only host private Websites/Blogs you won’t really pay over 100$ per Year for the Certificates.
Secure Login to your Site/Blog
Encrypted Transfer of Data
Security for your Visitors
Less Content Stealing
You will remark next years that the internet will be moved to HTTPS!
To create a Certificate use „OPENSSL“ with this command,answere the Questions of the Script, later put the Certificates .crt and .key to /etc/ssl/.. and tell Apache to pull them there!
Problem: If you use IDE or SATA Disc Drives inside your Workstation or Server without a additional uninterruppted power supply after a power loss your Disc Drives can lose data, do not boot clean up agian or damage the drive headers and sectors.
Background: SATA or IDE Drives uses „Disc Cached Controllers“, the count of this disc cache reach from 8 to 64 megabytes. In case of data write to disc, the disc controllers do cache some data who are often used. A Raid 1 Disc Mirror is affected too by this problem. SCSI od SAS are not using Cache by default.
Install the software tool called hdparm to set the cache parameters to disabled, cause most of operating systems have enabled by default.
at Debian/ubuntu do : # sudo aptitude install hdparm
at Centos/Redhat do: #sudo yum install hdparm
now lets show discs which are installed:
at Debian/ubuntu do: # sudo fdisk -l
at Centos/Redhat do: #sudo /sbin/sfdisk -l
at FreeBSD do: # fdisk -l
yet lets take settings to disable the cache on every boot:
at all linux do: sudo nano /etc/rc.local
insert for every drive
hdarm -W 0 /dev/sdX
(X is for a to …)
at FreeBSD do : #vi /etc/loader.conf
insert once for all drives
If you have two drives with same physical size inside your PC config a mdadm Software Raid 1 additional on your System.
Set the PC Bios Settings to auto boot ofter power failure and plug off the power on you testing System, check the results. There should not be needed a check disk called fsck after the Test, but its better to do it.
Hardware Raid Controllers do often have RAM Cache too, size 128MB up to 2GB, at power loss these Data lost, this can only be surpressed by a addtition RAM Cache Backup Battery connected to the Hardware Raid Controller
If you use:
and run db configuration setprop access private
the Login Interfaces is public !!!
Please take newer version: