

You could try mine, SimpleK8s (kubeadm, containerd, systemd, buildroot), ~50Mb single file (kernel+initramfs). https://simplek8s.org/
The current footprint is lower than every alternatives commented on this article.


You could try mine, SimpleK8s (kubeadm, containerd, systemd, buildroot), ~50Mb single file (kernel+initramfs). https://simplek8s.org/
The current footprint is lower than every alternatives commented on this article.
VC == Venture Capital


Good information here about EXO, and ChromeOS:
Neal Gompa (ニール・ゴンパ) 1 week ago
Is Exo going to continue to exist as a Wayland compositor? I figured it was going to be retired as ChromeOS turned into an Android overlay…
Fangzhou Ge 1 week ago
Yes, becoming Android overlay removes Chrome from the OS so Exo is going to retire. We still have to maintain Exo experience until the all ChromeOS device reach AUE or be updated to Android. Latest device AUE date I see are in 2033.
If folks don’t want Exo be listed we’ll just have Chromium here. Edited 1 week ago by Fangzhou Ge
Neal Gompa (ニール・ゴンパ) 1 week ago
I’m fine either way, if the Aura Shell is going to be around for a while, then it makes sense to include it.
I don’t even knowed that Chrome OS is/will be replaced by Android as an overlay.
The first improvement (Media Foundation by FFMPEG) could be significant. Currently, VALVe generates large shaders to re-render those Media Foundation videos into other free codecs. These shaders can be several gigabytes in size for some games with lengthy videos. With FFMPEG, those videos could be played without being re-encoded as shaders.
TLDR:
Hi!
I made my own inmutable distro using buildroot (https://buildroot.org): https://simplek8s.org
This distro is just an AIO kernel image that will bootstrap everything in RAM. You can mount additional devices for data persistence (for example you can mount your storage in /var).
TLDR; from MIT to GPL.
For example, when someone ask for a command to list files, and another one reply with a command that removes everything.


TLDR; the reviewer is upset because the PSVR2-PC adapter doesn’t come with a Display Port cable, and his Bluetooth adapter is not compatible. So he can’t review the unit on time until he receive both items. 🤷
It’s illegal in Europe to have an opt-out checked by default, must be an opt-in unchecked by default. This is one of the reason that Microsoft has always troubles in Europe about privacy and opt-out services.


Buddy, this message was posted 6 month ago, when this issue was a thing. Does not applied nowdays. But thank you for your help.


When you create a filesystem, there is a parameter named as “block percent free”. This parameter should be “5%”, so a 5% of your partition size can only be written by the “root” user.
You can decrease this value or just free some space. You can try to create files or folders as root as well.
#!/usr/bin/env bash
A folder dotfiles as git repository and a dotfiles/install that soft links all configurations into their places.
Two files, ~/.zshrc (without secrets, could be shared) and another for secrets (sourced by .zshrc if exist secrets).




Maybe this functionality was replaced by the next thing?
Automatic root filesystem soft-reboot: systemctl automatically reboots into a new root filesystem located at /run/nextroot/.
I didn’t try yet: https://www.cmcrossroads.com/article/gnu-make-escaping-walk-wild-side
colon := :
$(colon) := :
url := https$(:)//something


syscall -> asm -> page_fault
This a native machine code execution that crashed in your system. Could be an instruction that your CPU doesn’t understand (because the instruction is newer than your CPU, example: AVX512), or because your hardware returns an error when this instruction is executed (RAM issues?). Too difficult for me to understand this ASM crash.
On the other hand:
aptCLI instead of the originally supported packages 🤬 (what the hell, Canonical!? Are you doing the same crap as Microsoft?).The server-side closed garden is the opposite of an open ecosystem and the open-source community. You can add custom repositories to APT or Flatpak. Every new snap interaction feels like another step toward forcing the user to use it, instead of offering cool features that convince users on their own merits.
The last change (installing snapped apps when you run
apt install) was horrendous. What’s next? Installing snapped apps when the user runsflatpak install?