Die Video-AG des Engelsburg-Gymnasiums hatte der hessischen "Digitalministerin" Prof. Dr. Kristina Sinemus ein paar Fragen gestellt. Unter anderem stellten die Kinder die Frage: "Was ist Digitalisierung eigentlich?"
Das war ihre Antwort:
Digitalisierung ist eine Möglichkeit, um über Infrastruktur, also die
Anwendung sozusagen auf den Glasfasernetzen, neue Ideen in die Umsetzung zu
bringen. Digitalisierung heißt Anschlüsse und mathematische Algorithmen - die
Einsen und die Nullen.
Alternativ dazu die spontane Antwort einer 15-jährigen Schülerin auf dieselbe Frage:
Wenn man zum Beispiel tägliche Handlungen vereinfacht, indem man sie von
analog zu digital umwandelt.
Diese spontane Antwort der Schülerin entspricht ungefähr einer vereinfachten Definition auf digital-magazin.de:
Die einfachste Definition von Digitalisierung besagt, dass analoge Inhalte
oder Prozesse in eine digitale Form oder Arbeitsweise umgewandelt werden.
Die Erklärung von Frau Prof. Dr. Sinemus ist nicht nur leicht am Thema vorbei, sondern sogar falsch. Digitalisierung ist unabhängig von Netzen und erst recht sind Glasfasernetze keine Voraussetzung für Digitalisierung. Wenn jemand z.B. Anfang der 80er Jahre auf einem Apple II (=unvernetzt) ein Textdokument erstellt hat, das vorher nur handschriftlich vorlag, und das dann mehrfach ausgedruckt hat, dann stellte das bereits eine "Digitalisierung" dar. Ebenso werden nicht zwingend Algorithmen benötigt für Verarbeitung, Speicherung und Übertragung digitaler Daten. Und "Anschlüsse" sind ebenso irrelevant.
First enable tuxad repository:
rpm -i http://www.tuxad.com/repo/7/tuxad.rpm
We also need the EPEL repository. If you don't have it configured then follow the instructions on fedoraproject.org/wiki/EPEL.
Next required repo is nodesource. Enable it via tuxad meta package:
yum install nodesource-release-el7
Install jitsi-meet-install package which will by dependency also install other required packages:
yum install jitsi-meet-install
Add two entries to your DNS server to point to the server you are installing on:
After DNS is set up the final Jitsi Meet configuration can be done. The configuring script will call certbot to get certificates from Let's Encrypt.
It is important that (at least when running the configure script) no service is running on TCP port 80. If you have an http server running on this port then shut it down, run the configure script and then start it up again.
The configure script requires at least the IP address (IPv4) and the hostname. Example:
jitsi-meet-install.sh 1.2.3.4 jitsi.example.com
Run this script with your own settings. You are done!
I was curious if the widely used Crucial BX 500 did also "fail" as 480 GB model. And actually it shows the same picture as the 240 GB model: Fine consumption on standby, read values "ok" but high on write - with the same high bandwidth from approx. 1 Watts to 3.3 Watts.
Another two Patriot Burst 240 did also show the same results as the first Patriot Burst 240 measurement.
And the Kingston A400 960 was the first "1 TB class" SSD I measured. It did show the same great values like the 480 model did.
In addition to even more SSDs I made also the first measurement of an M.2 SSD (SATA, of course). Values were the same as for 2.5" SSD.
240 GB means actually 468862128 sectors.
480 GB means actually 937703088 sectors.
960 GB means actually 1875385008 sectors.
480 GB means actually 937703088 sectors.
SATA SSD | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
ADATA SU800 256 | 1.4 | 2.2 | ||
Apacer AS340 240 | 0.76 | 1.25 | 372 | 75 |
Corsair Force LE 120 | 0.58 | 0.58 | ||
Crucial BX500 240 | 0.6 | 1.7 | 372 | 99 |
Crucial BX500 480 | 0.86 | 1.66 | 373 | 81 |
Kingston A400 240 | 0.52 | 1.08 | 371 | 290 |
Kingston A400 480 | 0.5 | 0.5 | 371 | 328 |
0.49 | 0.49 | 408 | 345 | |
Patriot Burst 120 | 0.54 | 0.54 | 371 | 86 |
Patriot Burst 240 | 0.52 | 0.52 | 369 | 327 |
Patriot Burst 480 | 0.51 | 0.5 | 371 | 328 |
Samsung MZ7LN128 | 0.97 | 1.57 | 353 | 150 |
Sandisk Z410 120 | 0.7 | 1.5 | ||
Verbatim Vi500 S3 240 | 0.59 | 0.98 | 211 | 117 |
Verbatim Vi500 S3 480 | 0.84 | 1.13 | 359 | 129 |
WD Green 120 | 0.96 | 1.3 |
M.2 SATA | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
Kingston A400 480 | 0.5 | 0.5 | 372 | 329 |
2.5 HD | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
Seagate ST1000LM048 | 2.7 | 2.6 | ||
Toshiba MQ02ABD100H | 2.6 | 3.0 | ||
WD WD10SPZX | 1.62 | 2.47 | 256 |
3.5 HD | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
Seagate ST1000DM010 | 2.69 | 2.29 | ||
Toshiba DT01ACA100 | 2.86 | 2.94 |
Measuring environment is explained in power measuring ADATA SU800. The calculation of speed as logged in latest measurements was simply done by taking the time for reading and writing the whole SSD in relation to its size.
I ordered a Crucial BX250 because it was several times recommended by german magazine c't (Heise Verlag). It was also part of a recommendation for a DYI low power system "7-Watt-Mini" in c't 24/2019.
Unfortunately I can't understand this recommendation: The SSD has low write transfer rates and has a high power consumption on write. And even its (low) power consumption on read is higher than Corsair, Kingston and Patriot have.
240 GB means actually 468862128 sectors.
SATA SSD | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
ADATA SU800 256 | 1.4 | 2.2 | ||
Corsair Force LE 120 | 0.58 | 0.58 | ||
Crucial BX500 240 | 0.6 | 1.7 | 372 | 99 |
Kingston A400 480 | 0.5 | 0.5 | 371 | 328 |
Kingston A400 240 | 0.52 | 1.08 | 371 | 290 |
Patriot Burst 120 | 0.54 | 0.54 | 371 | 86 |
Patriot Burst 240 | 0.52 | 0.52 | 369 | 327 |
Patriot Burst 480 | 0.51 | 0.5 | 371 | 328 |
Samsung MZ7LN128 | 0.97 | 1.57 | 353 | 150 |
Sandisk Z410 120 | 0.7 | 1.5 | ||
Verbatim Vi500 S3 240 | 0.59 | 0.98 | 211 | 117 |
Verbatim Vi500 S3 480 | 0.84 | 1.13 | 359 | 129 |
WD Green 120 | 0.96 | 1.3 |
2.5 HD | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
Seagate ST1000LM048 | 2.7 | 2.6 | ||
Toshiba MQ02ABD100H | 2.6 | 3.0 | ||
WD WD10SPZX | 1.62 | 2.47 | 256 |
3.5 HD | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
Seagate ST1000DM010 | 2.69 | 2.29 | ||
Toshiba DT01ACA100 | 2.86 | 2.94 |
Measuring environment is explained in power measuring ADATA SU800. The calculation of speed as logged in latest measurements was simply done by taking the time for reading and writing the whole SSD in relation to its size.
In this session I measured a Kingston A400 480 which is much better than the smaller sizes. It's as great as the Patriot Burst 480: Very fast and very low power consumption. Additionally an old (used) Samsung 128 was measured.
480 GB means actually 937703088 sectors.
128 GB means actually 250069680 sectors.
SATA SSD | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
ADATA SU800 256 | 1.4 | 2.2 | ||
Corsair Force LE 120 | 0.58 | 0.58 | ||
Kingston A400 120 | 0.51 | 1.03 | 371 | |
Kingston A400 480 | 0.5 | 0.5 | 371 | 328 |
Kingston A400 240 | 0.52 | 1.08 | 371 | 290 |
Patriot Burst 120 | 0.54 | 0.54 | 371 | 86 |
Patriot Burst 240 | 0.52 | 0.52 | 369 | 327 |
Patriot Burst 480 | 0.51 | 0.5 | 371 | 328 |
Samsung MZ7LN128 | 0.97 | 1.57 | 353 | 150 |
Sandisk Z410 120 | 0.7 | 1.5 | ||
Verbatim Vi500 S3 240 | 0.59 | 0.98 | 211 | 117 |
Verbatim Vi500 S3 480 | 0.84 | 1.13 | 359 | 129 |
WD Green 120 | 0.96 | 1.3 |
2.5 HD | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
Seagate ST1000LM048 | 2.7 | 2.6 | ||
Toshiba MQ02ABD100H | 2.6 | 3.0 | ||
WD WD10SPZX | 1.62 | 2.47 | 256 |
3.5 HD | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
Seagate ST1000DM010 | 2.69 | 2.29 | ||
Toshiba DT01ACA100 | 2.86 | 2.94 |
Measuring environment is explained in power measuring ADATA SU800. The speed as logged and calculated in latest measurements was simply done by taking the time for reading and writing the whole SSD in relation to its size.
Finally the third Patriot Burst was tested. The results for the 480 are the same like for the 240: Lowest power consumption and highest speed. Additionally a 2.5 hard disk from WD was tested and two 3.5 disks to see the difference between 2.5 and 3.5.
480 GB means actually 937703088 sectors.
This is a 2.5 hard disk with 1953525168 sectors.
This is a 3.5 hard disk with 1 TB.
This is a 3.5 hard disk with 1 TB.
SATA SSD | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
ADATA SU800 256 | 1.4 | 2.2 | ||
Corsair Force LE 120 | 0.58 | 0.58 | ||
Kingston A400 120 | 0.51 | 1.03 | 371 | |
Kingston A400 240 | 0.52 | 1.08 | 371 | 290 |
Patriot Burst 120 | 0.54 | 0.54 | 371 | 86 |
Patriot Burst 240 | 0.52 | 0.52 | 369 | 327 |
Patriot Burst 480 | 0.51 | 0.5 | 371 | 328 |
Sandisk Z410 120 | 0.7 | 1.5 | ||
Verbatim Vi500 S3 240 | 0.59 | 0.98 | 211 | 117 |
Verbatim Vi500 S3 480 | 0.84 | 1.13 | 359 | 129 |
WD Green 120 | 0.96 | 1.3 |
2.5 HD | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
Seagate ST1000LM048 | 2.7 | 2.6 | ||
Toshiba MQ02ABD100H | 2.6 | 3.0 | ||
WD WD10SPZX | 1.62 | 2.47 | 256 |
3.5 HD | r pow (W) |
w pow (W) |
r spd (MB/s) |
w spd (MB/s) |
---|---|---|---|---|
Seagate ST1000DM010 | 2.69 | 2.29 | ||
Toshiba DT01ACA100 | 2.86 | 2.94 |
Measuring environment is explained in power measuring ADATA SU800. The speed as logged and calculated in latest measurements was simply done by taking the time for reading and writing the whole SSD in relation to its size.
This time three SSDs were measured. The Patriot Burst 240 is an exceptional SSD of all measured ones so far: It has the lowest power consumption combined with the highest speed - and it was also the cheapest one.
240 GB means actually 468862128 sectors.
480 GB means actually 937703088 sectors.
read | write | r speed | w speed | |
---|---|---|---|---|
Sandisk Z410 120 | 0.7 W | 1.5 W | ||
ADATA SU800 256 | 1.4 W | 2.2 W | ||
WD Green 120 | 0.96 W | 1.3 W | ||
Kingston A400 120 | 0.51 W | 1.03 W | 371 MB/s | |
Corsair Force LE 120 | 0.58 W | 0.58 W | ||
Patriot Burst 120 | 0.54 W | 0.54 W | 371 MB/s | 86 MB/s |
Kingston A400 240 | 0.52 W | 1.08 W | 371 MB/s | 290 MB/s |
Patriot Burst 240 | 0.52 W | 0.52 W | 369 MB/s | 327 MB/s |
Verbatim Vi500 S3 240 | 0.59 W | 0.98 W | 211 MB/s | 117 MB/s |
Verbatim Vi500 S3 480 | 0.84 W | 1.13 W | 359 MB/s | 129 MB/s |
Measuring environment is explained in power measuring ADATA SU800. The speed as logged and calculated in latest measurements was simply done by taking the time for reading and writing the whole SSD in relation to its size.
Hardkernel's ODROID GO handheld game kit is well known for his ability to emulate Gameboy and many more game consoles as also for ports of games like 3D Wolfenstein or Doom.
But with his versatile peripheral hardware like e.g. WiFi, Bluetooth and his expansion port with GPIO pins it allows a wide range of applications. Example applications with external hardware are a Weather Station and an Ultrasonic Distance Meter.
Programming is easy with the Arduino IDE even for novices. A lot of libraries are already available because ORDROID GO is based on the widely used ESP32 platform.
As first application I started developing of a "WiFi/network tool". Currently it can do some network tests and light configuration changes in our network. This is an example screenshot:
The Wifi connection works very well even through some walls. This Proof Of Concept is already very useful and I will continue to enhance it.
Some days ago my son told me that he had an issue on installing Unity via UnityHubSetup on Linux: Even with specifying TMPDIR and selecting home partition as installation target the installer did still show the (low) free disk space of the root partition.
There are several pages about this topic but apparently there's no easy solution for this issue. I told him that (assuming that you actually have enough free disk space) the disk space can be "faked" by pre-loading a shared library where the statfs() calls are wrapping the system calls and are "faking" the results.
As Proof-of-Concept and for educational purposes I wrote this fake library and a small shell script to control the Unity installer and the lib. A small issue is that the executable UnityHubSetup.AppImage is actually unpacking some kind of image and then starting the actual installer from this image. As a solution my script will launch UnityHubSetup.AppImage to get the image unpacked, then terminate UnityHubSetup.AppImage and finally start the real installer with the fake library preloaded. That causes the installer window flashing one time and then opening up finally.
Script and fake lib as archive: unityhubsetup-fake-diskspace.tar.gz
Content of the archive:
$ ls -1 unityhubsetup-fake-diskspace README launch-uhs-with-faked-increased-diskspace.sh wrap_statfs.c wrap_statfs.so
Some technical details: The actual free space is multiplied with a constant factor...
$ grep -B3 'resize_factor =' wrap_statfs.c /** * multiply free space with resize_factor */ static const int resize_factor = 16;
... and this is an implementation of a faked call:
$ fgrep -A9 'int statfs(' wrap_statfs.c int statfs(const char *path, struct statfs *buf) { int result; write(2, MESSAGE_STATFS, (sizeof MESSAGE_STATFS) - 1); actual_statfs = dlsym(RTLD_NEXT, "statfs"); result = actual_statfs(path, buf); if (result == 0) { SET(buf->f_blocks, buf->f_bfree, buf->f_bavail); } return result; }
Updated dovecot RPM package for RHEL / CentOS 5 is available in tuxad repository:
Please use yum update to update.
For RHEL 6 there's at least an SRPM package available: repo/6/SRPMS/dovecot-2.0.9-22.el6.1.src.rpm.
News history tuxad repository: