Chips and Cheese
Condor’s Cuzco RISC-V Core at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
Condor’s Cuzco RISC-V Core at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
Chips and Cheese
Intel's Clearwater Forest E-Core Server Chip at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
Intel's Clearwater Forest E-Core Server Chip at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
Chips and Cheese
Google's Liquid Cooling at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
Google's Liquid Cooling at Hot Chips 2025
#ChipAndCheese
Telegraph | source
(author: Chester Lam)
Arch Linux: Recent news updates
Recent services outages
We want to provide an update on the recent service outages affecting our infrastructure. The Arch Linux Project is currently experiencing an ongoing denial of service attack that primarily impacts our main webpage, the Arch User Repository (AUR), and the Forums.
We are aware of the problems that this creates for our end users and will continue to actively work with our hosting provider to mitigate the attack. We are also evaluating DDoS protection providers while carefully considering factors including cost, security, and ethical standards.
To improve the communication around this issue we will provide regular updates on our service status page going forward.
As a volunteer-driven project, we appreciate the community's patience as our DevOps team works to resolve these issues. Please bear with us and thank you for all the support you have shown so far.
Workarounds during service disruption
● In the case of downtime for archlinux.org: ● Mirrors: The mirror list endpoint used in tools like
● In the case of downtime for aur.archlinux.org: ● Packages: We maintain a mirror of AUR packages on GitHub. You can retrieve a package using:
Additional remarks
● Our services may send an initial connection reset due to the TCP SYN authentication performed by our hosting provider, but subsequent requests should work as expected.
● We are keeping technical details about the attack, its origin and our mitigation tactics internal while the attack is still ongoing.
source
(author: Christian Heusel)
Recent services outages
We want to provide an update on the recent service outages affecting our infrastructure. The Arch Linux Project is currently experiencing an ongoing denial of service attack that primarily impacts our main webpage, the Arch User Repository (AUR), and the Forums.
We are aware of the problems that this creates for our end users and will continue to actively work with our hosting provider to mitigate the attack. We are also evaluating DDoS protection providers while carefully considering factors including cost, security, and ethical standards.
To improve the communication around this issue we will provide regular updates on our service status page going forward.
As a volunteer-driven project, we appreciate the community's patience as our DevOps team works to resolve these issues. Please bear with us and thank you for all the support you have shown so far.
Workarounds during service disruption
● In the case of downtime for archlinux.org: ● Mirrors: The mirror list endpoint used in tools like
reflector is hosted on this site. Please default to the mirrors listed in the pacman-mirrorlist package during an outage. ● ISO: Our installation image is available on a lot of the mirrors, for example the DevOps administered geomirrors. Please always verify its integrity as described on the wiki and confirm it is signed by 0x54449A5C (or other trusted keys that may be used in the future).● In the case of downtime for aur.archlinux.org: ● Packages: We maintain a mirror of AUR packages on GitHub. You can retrieve a package using:
$ git clone --branch <package_name> --single-branch https://github.com/archlinux/aur.git <package_name>Additional remarks
● Our services may send an initial connection reset due to the TCP SYN authentication performed by our hosting provider, but subsequent requests should work as expected.
● We are keeping technical details about the attack, its origin and our mitigation tactics internal while the attack is still ongoing.
source
(author: Christian Heusel)
I scored 14/21 on https://e-mail.wtf and all I got was this lousy text to share on social media.
e-mail.wtf
Email is Easy
Everyone knows what an email address is, right?
这个up好玩
#今日看了什么
GNU Compiler Collection AutoVectorization for RISC-V’s Vector Extension 1.0: A Comparative Study Against x86-64 AVX2
https://www.diva-portal.org/smash/get/diva2:1985723/FULLTEXT01.pdf
GNU Compiler Collection AutoVectorization for RISC-V’s Vector Extension 1.0: A Comparative Study Against x86-64 AVX2
https://www.diva-portal.org/smash/get/diva2:1985723/FULLTEXT01.pdf
Arch Linux: Recent news updates
zabbix >= 7.4.1-2 may require manual intervention
Starting with
● zabbix-server
● zabbix-proxy
● zabbix-agent (also used by the
● zabbix-web-service
This shared
The switch to the new user account is handled automatically for the corresponding main configuration files and
However, manual intervention may be required if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example:
●
● Custom scripts for metrics collections or report generations
●
● ...
Those should therefore be updated to refer to and / or be owned by the new
Once migrated, you may remove the obsolete user accounts from your system.
source
(author: Robin Candau)
zabbix >= 7.4.1-2 may require manual intervention
Starting with
7.4.1-2, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared zabbix user account (as originally intended by upstream and done by other distributions):● zabbix-server
● zabbix-proxy
● zabbix-agent (also used by the
zabbix-agent2 package)● zabbix-web-service
This shared
zabbix user account is provided by the newly introduced zabbix-common split package, which is now a dependency for all relevant zabbix-* packages.The switch to the new user account is handled automatically for the corresponding main configuration files and
systemd service units.However, manual intervention may be required if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example:
●
PSK files used for encrypted communication● Custom scripts for metrics collections or report generations
●
sudoers rules for metrics requiring elevated privileges to be collected● ...
Those should therefore be updated to refer to and / or be owned by the new
zabbix user account, otherwise some services or user parameters may fail to work properly, or not at all.Once migrated, you may remove the obsolete user accounts from your system.
source
(author: Robin Candau)
