4 Likes
#upgrade
OpenAI states it is starting a test this week, which will introduce "Memory" to a "small portion" of its free and Plus ChatGPT users.
Memory will let ChatGPT remember what users have talked about across their devices so they won't have to reiterate the same details.
OpenAI is also introducing several security and privacy settings to help users stay in control of what is saved.
More here: https://openai.com/blog/memory-and-new-controls-for-chatgpt
A practical upgrade that can be a good tool to have available. Useful when you ask within a topic over time. ChatGPT is a wonderful Q&A tool, I embrace it for that, its a superior search engine. But yeah, the memory thing might be an issue when people use it for private questions and personal "chat".
#AI #ChatGPT #Memory #Upgrade
OpenAI tests 'memory' for ChatGPT so you won't have to repeat yourself
4 Likes
4 Likes
1 Shares
The end of #Windows 10 support could turn 240 million PCs into e-waste
source: https://www.canalys.com/insights/end-of-windows-10-support-could-turn-240-million-pcs-into-e-waste
Canalys estimates that in the nearly two-year period until #Microsoft’s official end-of-support date for Windows 10 – 14 October 2025 – roughly a fifth of devices will become e-waste due to incompatibility with the Windows 11 OS. This equates to 240 million PCs. If these were all folded laptops, stacked one on top of another, they would make a pile 600km taller than the moon.
#pc #laptop #computer #update #upgrade #problem #waste #pollution #news #environment #software #OS
One person like that
5 Comments
3 Shares
4 Likes
#Yamaha #SY77 / #TG77 #NEW #Templates For #Novation SL #Mkll #Controllers - #silverlight2004db
https://www.youtube.com/watch?v=HPT3xpE8C98
I've finally got round to updating and improving my TG77 templates for #sysex #control from the Novation Zero SL Mkll. Check out the #video to see what's new! If you bought my original templates and would like to #upgrade to these ones, send me an email and i'll send these new ones to you. If you'd like to get for the first time, send USD10 to my paypal at silverlight2004@hotmail.com and ask for the new TG77 template set for the Novation SL Mkll.
2 Likes
2 Likes
One person like that
.. 🔴LIVESTREAM SIMULCAST: A BREAK IN THE CLOUDS WITH #PENNY_KELLY, Julie & Jean-Claude@BeyondMystic 1:44:40
Jean-Claude@BeyondMystic
#upgrade experience inter dimensional
Source: https://youtube.com/watch?v=lTjoO6RxsFQ
One person like that
Upgrade Ubuntu
So, #Ubuntu prompted me yesterday with a good news: "Ubuntu #22.04.1 is there, do you like to #upgrade?" Yes, of course I want, what could possibly go wrong?
#Installation went smoothly over all, except for the Firefox configurator that suddenly didn't responded anymore after I clicked "Next". Then, reboot and hey, what a surprise: stuck at the #boot loader... Yeah. I gonna have a happy evening... 🙄
The last upgrade two years ago from 18.04 to 20.04 went smoothly. I guess that's already too lucky for me.
#nota404mn #announcement #upgrade
Diaspora will be down for approximately 20 minutes as I upgrade the server and take a backup of binary and database. This outage will begin in 6 minutes (2PM UTC).
#Linux #Mint #Linux-Mint #upgrade #uma #vanessa #21 #mint21
Das Versions-Upgrade von Linux Mint 20.3 (uma) auf Mint 21.0 (vanessa) ist möglich.
https://www.ehlertronic.de/linux/tipps-tricks/versions-upgrade.html
2 Likes
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/
One person like that
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/
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”
- download here https://support.lenovo.com/de/de/downloads/ds029265-flash-bios-update-thinkcentre-edge-92-thinkcentre-m82-m92-and-m92p-thinkstation-e31
- check sha256sum: 107f79a8fca7cf60531370f5cf78fc71905462c6e2fed6e6fffccf7aa30085bc
- instructions are in the readme
- start setup 9sjy9cusa.exe
- make new shortcut on desktop “cmd”
- r-click -> run it as Administrator
- cd into the folder where 9sjy9cusa.exe installed
- run flash.cmd
[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/
Kingston's datacenter capable (24-7) NVMe SSDs only work with mainboard that have U.2 interface
IDE, SCSI, SATA, SAS now U.2 M.2…
that reminds of…
the list of interfaces grows by the year?
no U.2 is not:
1) the band U2
or (more likely)
2) “a form factor” “a size factor” 2U (2x rack unit heights)
NVMe upgrading old servers is a massive challenge, that not always goes as planned on any OS (see here)
the dilemma SysAdmins face that do not want to replace a long running reliable server, that has enough CPU and RAM but the RAID10 is still running on magnetic discs and could be faster…
Links:
https://www.isunshare.com/blog/u-2-sata-pci-express-sata-express-msata-m-2-sas-ssd-interface-best/
#linux #gnu #gnulinux #opensource #administration #sysops #storage #nvme #ssd #kingston #upgrade #hardware #upgrades #standards
Originally posted at: https://dwaves.de/2022/03/10/kingstons-datacenter-capable-24-7-nvme-ssds-only-work-with-mainboard-that-have-u-2-interface/
What happens if you try to UPGRADE a $5,000 Mac Studio?
Too long don't watch: You can't upgrade it.
watch: https://www.youtube.com/watch?v=xEwS_VGD2yY
#Apple #Mac #expensive #economy #upgrade #fail #MacStudio #proprietary #hardware #news #ssd
5 Likes
11 Comments
1 Shares