#upgrades

bliter@diaspora-fr.org

#EXTREME #Amiga500 #Upgrades - #CrystalCase & #PiStorm #Updates - #DanWood

The Amiga 500 was the low-end, entry level machine back in the day but in 2022 I give it some EXTREME upgrades. Fitting a brand new Crystal Case and using a #RaspberryPi to boost the speed by over 1000x!

ā–¬ Contents of this video ā–¬

00:00 - Introduction & #Amiga500
01:50 - A1200.net Crystal Case
2:32 - #Unboxing #Crystal #Case
03:19 - Fitting #Amiga 500 Crystal Case
04:54 - #PiStorm Recap
05:57 - #Emu68 Introduction
06:53 - Squarespace Sponsor Slot
07:55 - Caffeine OS Introdution & Install
09:38 - #CaffeineOS Tour
11:40 - #Networking & #Internet
13:16 - Bundled #Utilities
14:38 - SysInfo #Benchmarks
15:04 - #Scene #Demos
15:25 - #Game #Performance
16:12 - Conclusion

https://www.youtube.com/watch?v=3s1_XCv-f1o
#retrocomputing #retrogames #retrogaming #amiga #raspberrypi

canoodle@nerdpol.ch

Rant: PHP & DokuWiki update upgrade problems - too much complexity: fixing one thing, while breaking another - why updates are hated

Nobody likes rantsā€¦ just as Updates are (sometimes) hated, but (sometimes) necessary.

This is how (probably) the slogan: ā€œnever touch a running/working systemā€ originated.

Once a system was fully tested (all used cases worked), an update came along a old functionality was not functioning anymore.

For security reasons: all machines/systems directly or indirectly exchanging messages with the wild west internet need to stay as up to date as possible.

the pros:

(+) First of DokuWiki is a nice software, itā€™s cool that it can do a lot of fancy stuff such as LDAP (?) if the user needs it.

(-) What is not cool, to have a lot of plugins installed per default, instead of starting with a bare minimum of software needed (software minimalism) and let the user add the software the user absolutely needs, because ā€œtoo much softwareā€ pre-installed tend to make systems fail.

This time it happened in a ā€œcomplex grown over years softwareā€ ā€œtrippleā€ upgrade situation:

  • php8 is out
  • DokuWiki ā€œupgrade pluginā€ needs updating
  • DokuWiki itself needs updating

ā€¦ things fell apart at the 1st step already, resulting in a still readable, but pretty ugly (missing CSS) version of what it was before.

culprit: with a stylesheed was not being properly generated:

url: http://localhost/projects/lib/exe/css.php?t=dokuwiki&tseed=djf83jhdfuz38odhfzho3z80ehilf

<br />
<b><span style="color: #ff9900;">Warning</span></b>: Undefined array key "speech" in <b>/path/to/dokuwiki/lib/exe/css.php</b> on line <b>83</b><br />
<br />
<b><span style="color: #ff0000;">Fatal error</span></b>: Array and string offset access syntax with curly braces is no longer supported in <b>/path/to/dokuwiki/vendor/marcusschwarz/lesserphp/lessc.inc.php</b> on line <b>761</b><br />

DokuWiki authors added the work of this author (https://www.maswaba.de/lesserphpdocs/) for whatever reason and { curly brackets } (now deprecated) were not updated in time to [ square brackets ].

As simple as that.

In the beginning: all the user wants is an easy editable file based wiki (itā€™s even there in the Dokuwiki slogan ā€œitā€™s better when it is simpleā€)

Why exactly is this CSS compiler needed/active per default in the first place?

Has DokuWiki grown into unnecessary complex ā€œbloatwareā€ of over 5000 files?

<span style="color: #00ffff;">wget https://download.dokuwiki.org/out/dokuwiki-8186df5bcf8bba07ff8638254a75b094.tgz
tar fxvz dokuwiki-8186df5bcf8bba07ff8638254a75b094.tgz</span>
<span style="color: #00ffff;">find ./dokuwiki |wc -l</span>
<span style="color: #ff6600;">5579 files</span>

(much less than some PHP frameworksā€¦ but still a lot of filesā€¦ with a lot of moving partsā€¦ all potential points of failureā€¦)

violating UNIX K.I.S.S and leading to software failures

More complexity = more errors = less maintainability.

DokuWiki has gained functionalities of questionable qualities, such as the very faulty and thus pretty useless and annoying SPAM detection mechanism.

(every Wiki should be login & .htaccess protected, how to activate the DokuWiki (per default disabled) login screen, is the #1 most visited page of this blog X-D, already enough SPAM protectionā€¦ so completely unnecessary to add such faulty functionality)

Even worse: @the-official-DokuWiki-forum, the forum software triggers admins (that are unable to read and blindly trust this faulty SPAM detection mechanism, that basically detects EVERY URL as spam) to block the userā€™s (maybe useful) contributions aka ā€œoverblockingā€.

Be Brave New Web World.

Only solution: write your own tools that respect UNIX K.I.S.S principle and are therefore easy to fix and maintain and actually work, fast šŸ™‚ (using minimal resources)

DokuWiki updates-upgrades: how it is supposed to look and work like:

how to fix this mess:

==== howto fix ====
<b>Warning</b>: Undefined array key "speech" in <b>/path/to/dokuwiki/lib/exe/css.php</b> on line <b>83</b>
(usually php-warnings are disabled, but if warnings are enabled, it will mess up the css's format)

=== in file: /lib/exe/css.php

== in line: 82 to 87

= change, from:
        // load user styles
        if(is_array($config_cascade['userstyle'][$mediatype])) {
            foreach($config_cascade['userstyle'][$mediatype] as $userstyle) {
                $files[$userstyle] = DOKU_BASE;
            }
        }
= change, to:
        // load user styles
        if(array_key_exists($mediatype, $config_cascade['userstyle']))
        {
            if(is_array($config_cascade['userstyle'][$mediatype])) {
                foreach($config_cascade['userstyle'][$mediatype] as $userstyle) {
                    $files[$userstyle] = DOKU_BASE;
                }
            }
        }

==== howto fix ====

<b>Fatal error</b>: Array and string offset access syntax with curly braces is no longer supported in <b>/path/to/dokuwiki/vendor/marcusschwarz/lesserphp/lessc.inc.php</b> on line <b>761</b>

=== in file:
/vendor/marcusschwarz/lesserphp/lessc.inc.php

== line: 761
= change, from:
   $subProp[1]{0} != $this->vPrefix)
= change, to:
   $subProp[1][0] != $this->vPrefix)

== line: 2762
= change, from:
   if (!is_string($tag) || $tag{0} != $this->lessc->mPrefix)
= change, to:
   if (!is_string($tag) || $tag[0] != $this->lessc->mPrefix)

== line: 2816
= change, from:
   if ($tag{0} == $this->lessc->vPrefix)
= change, to:
   if ($tag[0] == $this->lessc->vPrefix)

#linux #gnu #gnulinux #opensource #administration #sysops #dokuwiki #when #upgrades #fail #upgrade #complexity #unix #kiss

Originally posted at: https://dwaves.de/2022/06/30/rant-php-dokuwiki-update-upgrade-problems-too-much-complexity-fixing-one-thing-while-breaking-another-why-updates-are-hated/

canoodle@nerdpol.ch

PHP & DokuWiki update upgrade problems - too much complexity: fixing one thing, while breaking another - why updates are hated

Updates are hated, but sometimes necessary.

This is how (probably) the slogan: ā€œnever touch a running/working systemā€ originated.

Once a system was fully tested (all used cases worked), an update came along a old functionality was not functioning anymore.

For security reasons: all machines/systems directly or indirectly exchanging messages with the wild west internet need to stay as up to date as possible.

the pros:

(+) First of DokuWiki is a nice software, itā€™s cool that it can do a lot of fancy stuff such as LDAP (?) if the user needs it.

(-) What is not cool, to have a lot of plugins installed per default, instead of starting with a bare minimum of software needed (software minimalism) and let the user add the software the user absolutely needs, because ā€œtoo much softwareā€ pre-installed tend to make systems fail.

This time it happened in a ā€œcomplex grown over years softwareā€ ā€œtrippleā€ upgrade situation:

  • php8 is out
  • DokuWiki ā€œupgrade pluginā€ needs updating
  • DokuWiki itself needs updating

ā€¦ things fell apart at the 1st step already, resulting in a still readable, but pretty ugly (missing CSS) version of what it was before.

culprit: with a stylesheed was not being properly generated:

url: http://localhost/projects/lib/exe/css.php?t=dokuwiki&tseed=djf83jhdfuz38odhfzho3z80ehilf

<br />
<b><span style="color: #ff9900;">Warning</span></b>: Undefined array key "speech" in <b>/path/to/dokuwiki/lib/exe/css.php</b> on line <b>83</b><br />
<br />
<b><span style="color: #ff0000;">Fatal error</span></b>: Array and string offset access syntax with curly braces is no longer supported in <b>/path/to/dokuwiki/vendor/marcusschwarz/lesserphp/lessc.inc.php</b> on line <b>761</b><br />

DokuWiki authors added the work of this author (https://www.maswaba.de/lesserphpdocs/) for whatever reason and { curly brackets } (now deprecated) were not updated in time to [ square brackets ].

As simple as that.

In the beginning: all the user wants is an easy editable file based wiki (itā€™s even there in the Dokuwiki slogan ā€œitā€™s better when it is simpleā€)

Why exactly is this CSS compiler needed/active per default in the first place?

Has DokuWiki grown into unnecessary complex ā€œbloatwareā€ of over 5000 files?

<span style="color: #00ffff;">wget https://download.dokuwiki.org/out/dokuwiki-8186df5bcf8bba07ff8638254a75b094.tgz
tar fxvz dokuwiki-8186df5bcf8bba07ff8638254a75b094.tgz</span>
<span style="color: #00ffff;">find ./dokuwiki |wc -l</span>
<span style="color: #ff6600;">5579 files</span>

(much less than some PHP frameworksā€¦ but still a lot of filesā€¦ with a lot of moving partsā€¦ all potential points of failureā€¦)

violating UNIX K.I.S.S and leading to software failures

More complexity = more errors = less maintainability.

DokuWiki has gained functionalities of questionable qualities, such as the very faulty and thus SPAM detection mechanism.

(every Wiki should be login & .htaccess protected, how to activate the DokuWiki (per default disabled) login screen, is the #1 most visited page of this blog X-D, already enough SPAM protectionā€¦ so completely unnecessary to add such faulty functionality)

Even worse: @the-official-DokuWiki-forum, the forum software triggers admins (that are unable to read and blindly trust this faulty SPAM detection mechanism, that basically detects EVERY URL as spam) to block the userā€™s (maybe useful) contributions aka ā€œoverblockingā€.

Be Brave New Web World.

Only solution: write your own tools that respect UNIX K.I.S.S principle and are therefore easy to fix and maintain and actually work, fast šŸ™‚ (using minimal resources)

how to fix this mess:

==== howto fix ====
<b>Warning</b>: Undefined array key "speech" in <b>/path/to/dokuwiki/lib/exe/css.php</b> on line <b>83</b>
(usually php-warnings are disabled, but if warnings are enabled, it will mess up the css's format)

=== in file: /lib/exe/css.php

== in line: 82 to 87

= change, from:
        // load user styles
        if(is_array($config_cascade['userstyle'][$mediatype])) {
            foreach($config_cascade['userstyle'][$mediatype] as $userstyle) {
                $files[$userstyle] = DOKU_BASE;
            }
        }
= change, to:
        // load user styles
        if(array_key_exists($mediatype, $config_cascade['userstyle']))
        {
            if(is_array($config_cascade['userstyle'][$mediatype])) {
                foreach($config_cascade['userstyle'][$mediatype] as $userstyle) {
                    $files[$userstyle] = DOKU_BASE;
                }
            }
        }

==== howto fix ====

<b>Fatal error</b>: Array and string offset access syntax with curly braces is no longer supported in <b>/path/to/dokuwiki/vendor/marcusschwarz/lesserphp/lessc.inc.php</b> on line <b>761</b>

=== in file:
/vendor/marcusschwarz/lesserphp/lessc.inc.php

== line: 761
= change, from:
   $subProp[1]{0} != $this->vPrefix)
= change, to:
   $subProp[1][0] != $this->vPrefix)

== line: 2762
= change, from:
   if (!is_string($tag) || $tag{0} != $this->lessc->mPrefix)
= change, to:
   if (!is_string($tag) || $tag[0] != $this->lessc->mPrefix)

== line: 2816
= change, from:
   if ($tag{0} == $this->lessc->vPrefix)
= change, to:
   if ($tag[0] == $this->lessc->vPrefix)

#linux #gnu #gnulinux #opensource #administration #sysops #dokuwiki #when #upgrades #fail #upgrade #complexity #unix #kiss

Originally posted at: https://dwaves.de/2022/06/30/php-dokuwiki-update-upgrade-problems-too-much-complexity-fixing-one-thing-while-breaking-another-why-updates-are-hated/

canoodle@nerdpol.ch

How to disassemble Harddisk Upgrade - Inside a Lenovo ThinkCentre M92p - 1962 error : No operation system found fixed by 2018 bios update

they are fast, they are small, they use very little energy (less than 30W), the Lenovo ThinkCentre M92p despite being also pretty old (2012) it still rocks, the naming ainā€™t sexy, but they work very well.

now letā€™s look inside:

it meassures:

  • width: 18cm
  • ā€œdepthā€: 18.5cm
  • height: 3.5cm

extremely compact.

this opening procedure was done to upgrade the ssd harddisk.

what is special about the M92p: it still has a tiny tiny speaker inside šŸ™‚

for all those beep code symphonies

How to disassemble Harddisk Upgrade ā€“ Inside a Lenovo ThinkCentre M92p ā€“ 1962 error : No operation system found

this happens, when trying to install Proxmox like in this how to article.

in order to fix this

windows 10 (yes argh) needs to be installed & BIOS update applied:

Intel ME almost no BIOS without itā€¦ with t440 it was able to ā€œdisable it permanentlyā€

[video width=ā€502ā€³ height=ā€492ā€³ mp4=ā€https://dwaves.de/wp-content/uploads/2022/05/Lenovo-ThinkCentre-M92p-1962-error-No-operation-system-found-update-bios-to-version-2018-flash-process.mp4ā€³\]\[/video\]

  • let it sit for a whileā€¦ when the blinking cursor comes upā€¦ let it blink for a whileā€¦
  • remove all usb drivesā€¦
  • Ctrl+Alt+Delā€¦
  • it should reboot fine
  • re-apply all bios settings

so updated from BIOS 2012 to 2018 version and now proxmox boots up fine.

#linux #gnu #gnulinux #opensource #administration #sysops #lenovo #hardware #bios #upgrades #upgrade #proxmox

Originally posted at: https://dwaves.de/2022/05/25/how-to-disassemble-harddisk-upgrade-inside-a-lenovo-thinkcentre-m92p-1962-error-no-operation-system-found-fixed-by-2018-bios-update/

canoodle@nerdpol.ch
danie10@squeet.me

Apple responds to iOS 15.4 battery drain on iPhones ā€” hereā€™s the advice that probably applies to any OS

Bild/Foto
Appleā€™s response to the issues raised was: ā€œThanks for reaching out! Weā€™ll be happy to help. Itā€™s normal for your apps and features to need to adjust up to 48 hours after an updateā€.

That is quite true, and also sometimes an OS needs even a second reboot for all updates to apply. Usually this will sort out any oddities after an OS upgrade.

See https://www.tomsguide.com/news/apple-responds-to-ios-154-battery-drain-on-iphones-heres-the-advice

#technology #apple #upgrades #updates #batterylife
#Blog, ##apple, ##batterylife, ##technology, ##updates, ##upgrades

canoodle@nerdpol.ch

ATTO Disk Benchmark Result Samsung 980 Pro PCIe 4.0 NVMe SSD 500GB MZ-V8P500BW on older ASUS Mainboard (i5)

because Win 10 compared to Win 7 is incredibly slow, a way to upgrade an older ASUS Mainboard was found

  • RAM was increased from 8 GB to 32 GB
  • it actually had an M.2 slot for the MZ-V8P500BW NVMe SSD (it is a NVMe but not directly PCIe attached but speaks to mainboard via SATA (SSD))

while not close to the theoreticall possible speeds of:

Read: 6,900 MB/s

Write: 5,000 MB/s

(src: do they mean Bits or Bytes here?)

imho those are impressive harddisk speeds, well done Samsung šŸ™‚

the user can try finding that NVMe SSD on ebay

when it comes to harddisk benchmarks, ATTO is probably ā€œbetterā€ than CrystalDiskMark as Crystal seems to actually meassure RAM-cached-harddisk-speeds?

#linux #gnu #gnulinux #opensource #administration #sysops #nvme #ssd #benchmark #samsung #harddisk #bench #upgrades #upgrade

Originally posted at: https://dwaves.de/2022/01/08/atto-disk-benchmark-result-samsung-980-pro-pcie-4-0-nvme-ssd-500gb-mz-v8p500bw-on-older-asus-mainboard-i5/