archweb VS QEMU

Arch is a popular Linux distribution(basically an os). Him saying that he uses arch is basically a joke that arch Linux users will always mention that they use the distro. (Also a penguin is also the Linux mascot)

Arch sends distribution news every week or so, usually in one or two paragraphs.

https://archlinux.org/

I've followed the gitlab migration and every package and distribution change that warranted community notification for more than a decade.

It's such an empowering feeling to have tracked all the changes to the distribution over a decade. The Arch maintainer culture has managed to provide consistent high quality communication and documentation.

Most of the news doesn't require action on my part regarding a subsystem or package I don't use. But they use the news channel sparingly and the distribution is minimal and clean. So news arrives only every other week or so and is succinctly written in one or two paragraphs.

It's a distribution for those who love precision and professionalism.

When searching for something just add Arch Linux to the and follow official archlinux.org and use duckduckgo.com for better results. You will get amazed how good arch wiki explained everything and how aur has very large apps.

I wonder how many people got frustrated with the solution posted on the front page of https://archlinux.org/, as it seems to not have been fixed for 5 days already.

when i visit the archlinux.org website i can't find the archlinux 2023.10.x update,

Since you want to use Linux in your job function, I would suggest you start with Arch Linux OS. https://archlinux.org/ Arch linux and arch based linux's like Manjaro, start you off in teaching you linux by making you install it and do everything from the command line. Nothing gets installed unless you want to install it. They have an extensive Arch Wiki that will walk you through anything you might need to learn.

-------------------------------------------- Hyprland Crash Report -------------------------------------------- I tried so hard, and got so far... Hyprland received signal 11 (Segmentation fault) Version: 0a78f6031c8fcc6773f136fccde3d560aaac239d Tag: v0.29.0 System info: System name: Linux Node name: nah Release: 6.4.12-arch1-1 Version: #1 SMP PREEMPT_DYNAMIC Thu, 24 Aug 2023 00:38:14 +0000 GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) os-release: NAME="Arch Linux" PRETTY_NAME="Arch Linux" ID=arch BUILD_ID=rolling ANSI_COLOR="38;2;23;147;209" HOME_URL="https://archlinux.org/" DOCUMENTATION_URL="https://wiki.archlinux.org/" SUPPORT_URL="https://bbs.archlinux.org/" BUG_REPORT_URL="https://bugs.archlinux.org/" PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/" LOGO=archlinux-logo Backtrace: #0 | Hyprland(_Z12getBacktracev+0x62) [0x55644d617522] ?? ??:0 #1 | Hyprland(_ZN13CrashReporter18createAndSaveCrashEi+0x42c) [0x55644d5f203c] ?? ??:0 #2 | Hyprland(_Z25handleUnrecoverableSignali+0x47) [0x55644d5893d7] ?? ??:0 #3 | /usr/lib/libc.so.6(+0x3e710) [0x7f350243e710] ?? ??:0 #4 | /usr/lib/libwlroots.so.12032(+0x516a2) [0x7f35030676a2] ?? ??:0 #5 | /usr/lib/libwlroots.so.12032(+0x4f659) [0x7f3503065659] ?? ??:0 #6 | /usr/lib/libwlroots.so.12032(+0x54d55) [0x7f350306ad55] ?? ??:0 #7 | /usr/lib/libwlroots.so.12032(+0x5689e) [0x7f350306c89e] ?? ??:0 #8 | /usr/lib/libwayland-server.so.0(wl_signal_emit_mutable+0x7e) [0x7f3502fcd01e] ?? ??:0 #9 | /usr/lib/libseat.so.1(+0x30ca) [0x7f3502a870ca] ?? ??:0 #10 | /usr/lib/libsystemd.so.0(+0x2a675) [0x7f350315c675] ?? ??:0 #11 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #12 | /usr/lib/libsystemd.so.0(+0x2a56d) [0x7f350315c56d] ?? ??:0 #13 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #14 | /usr/lib/libsystemd.so.0(+0x2a56d) [0x7f350315c56d] ?? ??:0 #15 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #16 | /usr/lib/libsystemd.so.0(+0x2a56d) [0x7f350315c56d] ?? ??:0 #17 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #18 | /usr/lib/libsystemd.so.0(+0x2a56d) [0x7f350315c56d] ?? ??:0 #19 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #20 | /usr/lib/libsystemd.so.0(+0x2a50b) [0x7f350315c50b] ?? ??:0 #21 | /usr/lib/libsystemd.so.0(+0x2a70f) [0x7f350315c70f] ?? ??:0 #22 | /usr/lib/libsystemd.so.0(+0x48268) [0x7f350317a268] ?? ??:0 #23 | /usr/lib/libsystemd.so.0(+0x4fce7) [0x7f3503181ce7] ?? ??:0 #24 | /usr/lib/libseat.so.1(+0x36de) [0x7f3502a876de] ?? ??:0 #25 | /usr/lib/libwlroots.so.12032(+0x4d127) [0x7f3503063127] ?? ??:0 #26 | /usr/lib/libwayland-server.so.0(wl_event_loop_dispatch+0xa2) [0x7f3502fceae2] ?? ??:0 #27 | /usr/lib/libwayland-server.so.0(wl_display_run+0x27) [0x7f3502fcf2d7] ?? ??:0 #28 | Hyprland(main+0x8d9) [0x55644d577dd9] ?? ??:0 #29 | /usr/lib/libc.so.6(+0x27cd0) [0x7f3502427cd0] ?? ??:0 #30 | /usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7f3502427d8a] ?? ??:0 #31 | Hyprland(_start+0x25) [0x55644d586735] ?? ??:0 Log tail: [LOG] Callback 5564501935d0 -> 5564501935c8, Keyboard removed. [LOG] Destroyed keyboard 5564501934d0 [LOG] Callback 55644fd2f938 -> 55644fd2f930, Keyboard removed. [LOG] Callback 55644fd2f800 -> 55644fd2f7f8, Keyboard removed. [LOG] Callback 55644fd2f868 -> 55644fd2f860, Keyboard removed. [LOG] Callback 55644fd2f8d0 -> 55644fd2f8c8, Keyboard removed. [LOG] Destroyed keyboard 55644fd2f7d0 [LOG] Callback 556450074a38 -> 556450074a30, Keyboard removed. [LOG] Callback 556450074900 -> 5564500748f8, Keyboard removed. [LOG] Callback 556450074968 -> 556450074960, Keyboard removed. [LOG] Callback 5564500749d0 -> 5564500749c8, Keyboard removed. [LOG] Destroyed keyboard 5564500748d0 [LOG] Callback 5564500874f8 -> 5564500874f0, Mouse removed. [LOG] Callback 5564501cc9d8 -> 5564501cc9d0, Keyboard removed. [LOG] Callback 5564501cc8a0 -> 5564501cc898, Keyboard removed. [LOG] Callback 5564501cc908 -> 5564501cc900, Keyboard removed. [LOG] Callback 5564501cc970 -> 5564501cc968, Keyboard removed. [LOG] Destroyed keyboard 5564501cc870 [LOG] Callback 55644fcf59e8 -> 55644fcf59e0, Mouse removed. [LOG] Callback 5564500bf3f8 -> 5564500bf3f0, Keyboard removed. [LOG] Callback 5564500bf2c0 -> 5564500bf2b8, Keyboard removed. [LOG] Callback 5564500bf328 -> 5564500bf320, Keyboard removed. [LOG] Callback 5564500bf390 -> 5564500bf388, Keyboard removed. [LOG] Destroyed keyboard 5564500bf290 [LOG] Callback 55644f3bc2b8 -> 55644f3bc2b0, Mouse removed. [LOG] Callback 55645003b3a8 -> 55645003b3a0, Keyboard removed. [LOG] Callback 55645003b270 -> 55645003b268, Keyboard removed. [LOG] Callback 55645003b2d8 -> 55645003b2d0, Keyboard removed. [LOG] Callback 55645003b340 -> 55645003b338, Keyboard removed. [LOG] Destroyed keyboard 55645003b240 [LOG] Callback 55644ff5f058 -> 55644ff5f050, Mouse removed. [LOG] Callback 5564500e9108 -> 5564500e9100, Keyboard removed. [LOG] Callback 5564500e8fd0 -> 5564500e8fc8, Keyboard removed. [LOG] Callback 5564500e9038 -> 5564500e9030, Keyboard removed. [LOG] Callback 5564500e90a0 -> 5564500e9098, Keyboard removed. [LOG] Destroyed keyboard 5564500e8fa0 [LOG] Callback 556450206068 -> 556450206060, Keyboard removed. [LOG] Callback 556450205f30 -> 556450205f28, Keyboard removed. [LOG] Callback 556450205f98 -> 556450205f90, Keyboard removed. [LOG] Callback 556450206000 -> 556450205ff8, Keyboard removed. [LOG] Destroyed keyboard 556450205f00 [LOG] Callback 556450067b70 -> 556450067b68, SwitchDevice removed. [LOG] Callback 556450067b08 -> 556450067b00, SwitchDevice removed. [LOG] Callback 55644fe495e8 -> 55644fe495e0, Tablet removed. [LOG] Callback 55644fe49580 -> 55644fe49578, Tablet removed. [LOG] Callback 55644fe49518 -> 55644fe49510, Tablet removed. [LOG] Callback 55644fe494b0 -> 55644fe494a8, Tablet removed. [LOG] Callback 55644fe49448 -> 55644fe49440, Tablet removed. [LOG] Removed a tablet [LOG] Session got activated!

But if do ping archlinux.org -6 or just ping archlinux.org, i only get PING archlinux.org(archlinux.org (2a01:4f9:c010:6b1f::1)) 56 data bytes

And just wait till you discover Arch Linux, Gentoo, Guix, or NixOS.

A better solution is just to write a plain ass shell script that tests if various C snippets compile.

https://github.com/oilshell/oil/blob/master/configure

https://github.com/oilshell/oil/blob/master/build/detect-pwe...

Not an unholy mix of m4, shell, and C, all in the same file.

---

These are the same style as a the configure scripts that Fabrice Bellard wrote for tcc and QEMU.

They are plain ass shell scripts, because he actually understands the code he writes.

https://github.com/qemu/qemu/blob/master/configure

https://github.com/TinyCC/tinycc/blob/mob/configure

OCaml’s configure script is also “normal”.

You don’t have to copy and paste thousands of lines of GNU stuff that you don’t understand.

(copy of lobste.rs comment)

Related:

A fast Pascal (Delphi) WebAssembly interpreter:

https://github.com/marat1961/wasm

WASM-4:

https://github.com/aduros/wasm4

Curated list of awesome things regarding WebAssembly (wasm) ecosystem:

https://github.com/mbasso/awesome-wasm

Also, it would be nice if there was a WASM (soft) CPU for QEMU, which (if it existed!) would go here:

https://github.com/qemu/qemu/tree/master/target

> architectural registers are always updated

In tiny code, the guest registers (global TCG variables) are stored in the host's registers until you either call an helper which can access the CPU state or you return (`git grep la_global_sync`). This is the reason why QEMU is not so terribly slow.

But after a check, this also happens when you access the guest memory address space! https://github.com/qemu/qemu/blob/master/include/tcg/tcg-opc... (TCG_OPF_SIDE_EFFECTS is what matters)

But still, in the end, it's the same problem. What QEMU does, can be done in LLVM too. You could probably be more efficient in LLVM by using the exception handling mechanism (invoke and friends) to only serialize back to memory when there's an actual exception, at the cost of higher register pressure. More or less what we do here: https://rev.ng/downloads/bar-2019-paper.pdf

Um, in case you don't know, UTM (based on QEMU) is out for quite a while.

Some of these tools include Oracle VM VirtualBox (that I've used since before the acquisition of Sun Microsystems by Oracle), VMWare Workstation Player, and QEMU, but last year, I found out about Multipass.

For C/C++ projects that use meson as the build system, there is an excellent way to manage dependencies:

https://mesonbuild.com/Wrapdb-projects.html

https://mesonbuild.com/Wrap-dependency-system-manual.html

meson will download and build the libraries automatically and give you a variable which you pass as a regular dependency into the built target:

https://github.com/qemu/qemu/tree/005ad32358f12fe9313a4a0191...

https://github.com/harfbuzz/harfbuzz/tree/main/subprojects

https://github.com/harfbuzz/harfbuzz/blob/37457412b3212463c5...

Or, if you're using proper operating systems, they're managed by the usual package manager, just like everything else.

For all the users of the Linux platform, QEMU is the VM that you should go for. This software comes without any price tag and works as an emulator of various machines with utmost ease and completion; the software uses dynamic translations to emulate hardware peripherals and enhances its overall performance. If you are using QEMU as a virtualizer, then it will function exactly like the host system (provided you have the right set of hardware).

In this tutorial, we set up macOS and Windows virtual machines on UTM, a macOS application that provides a GUI wrapper for QEMU, a powerful open-source emulator and virtualizer. UTM allows you to easily manage and run virtual machines without memorizing complex commands. It also has special handling for macOS, making it simpler to install compared to other virtual machine software.

I think you will need to build it yourself which you can do so by: Checkout the qemu repo and its submodules using the steps here: https://en.wikibooks.org/wiki/QEMU/Installing_QEMU in 'Building from Source' except for step 1 use the 'git clone https://github.com/qemu/qemu.git' Step 9 is where you enable the features, the build system does this by checking if you have the dev and or lib packages for the feature installed i.e. spice development packages will enable spice functionality, use the output from configure to help you with this then continue to step 10