pega.life my_wiki https://wiki.ho.stna.me/index.php/Main_Page MediaWiki 1.36.2 first-letter Media Special Talk User User talk Pega.life Pega.life talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk 0 1 466 439 2025-04-01T08:54:35Z 172.17.0.1 /* Formatting */ 466 wikitext text/x-wiki == Movies == * Joy Luck Club * Motherless Brooklyn * Dune * The Big Short * Andre The Giant 2018 * Joker * <s>Spider-Man</s> * <s>The Social Dilemma</s> * <s>King Richard (Will Smith)👍🏽</s> * <s>Shang-Chi</s> * <s>Venom</s> <pre>javascript:window.location=document.querySelector('#player iframe').src;</pre> <pre>javascript:window.location=document.querySelector('#player video').src;</pre> == Shows == * Marvelous Mrs Mazel * Watchmen (TV series) * Picard * <s>Cocaine Cowboys Miami</s> == Food == * Carnaval Brazilian BBQ * Feast * Across The Board * [https://www.tripadvisor.ca/Restaurant_Review-g2648278-d3171065-Reviews-Oma_s_Schnitzel_Stube-St_Pierre_Jolys_Manitoba.html German buffet in St. Malo] Closed/New (bad) management? * <s>smash burger</s> * <s>Turkey Tacos</s> * <s>[https://bluehazebbq.ca BBQ Beausejour]</s> * <s>tallest Poppy chicken</s> * Korean BBQ * home made chicken shawarma * https://www.winnipegrestaurantdeals.com/restaurants == Travel == * Pembina Valley * Banff * West Edmonton Mall * bunns creek trail (on way to half moon) * Bryce Canyon Utah == [[Disney World]]== {{:Disney World}} == [[Costa Rica]]== {{:Costa Rica}} == [[UNIX]]== {{:UNIX}} == Games == * X68000: Puzzle: [https://www.youtube.com/watch?v=T3l-6aQ28Ds Deflektor] * SNES: Puzzle: Bust-A-Move, The Lost Vikings * SNES: VS: Super Bomberman, Tetris Attack * SNES: Co-Op: Contra III, Wild Guns * SNES: Action RPG: Front Mission Gun Hazard * MAME: puzzle: Money Puzzle Exchanger * NEOGEO: Co-Op: Alpha Mission 2, Mslug, robo army, Shock Troopers * NEOGEO: VS: League Bowling, WindJammer, The Last Blade, Garou == emus == https://www.youtube.com/watch?app=desktop&v=UGtU5wRWuhc * OpenEmu: https://www.youtube.com/watch?v=RxhbhM8BA68&t=0s * PSP (PPSSPP ARM): https://www.youtube.com/watch?v=WYfnSCgRBdA&t=0s * GC/Wii (Dolphin ARM): https://www.youtube.com/watch?v=lwYKk-_HoPg&t=0s * PS2 (PCSX2): https://www.youtube.com/watch?v=veWRt0f7avk&t=0s * Dreamcast (Redream): https://www.youtube.com/watch?v=6x_vLg2m7T4&t=0s * 3DS (Citra ARM): https://www.youtube.com/watch?v=VpbDl0v_WCs&t=0s * PSX (DuckStation): hhttps://www.youtube.com/watch?v=MNofg_jkRnA&t=0s * Xbox (Xemu): https://www.youtube.com/watch?v=PCvQ_9M1nlI&t=0s * Mac Gaming: https://www.applegamingwiki.com/wiki/PlayStation_2 ==== mega thread ==== * roms: https://www.reddit.com/r/Roms/comments/gar3bc/roms_megathread_30_ybin_edition/ * emu files: https://emulation.gametechwiki.com/index.php/Emulator_files#PlayStation_2 ==Bike== * tighten seat * buy helmet == To Do == * <s>Red pocket</s> * <s>Plumber</s> == Self Hosting== === Fossil === https://dev.to/schollz/self-hosting-with-fossil-an-alternative-to-git-33bk === certbot === Add new cert: <pre># sudo certbot certonly -d wiki.ho.stna.me Saving debug log to /var/log/letsencrypt/letsencrypt.log How would you like to authenticate with the ACME CA? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1: Nginx Web Server plugin (nginx) 2: Spin up a temporary webserver (standalone) 3: Place files in webroot directory (webroot) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Select the appropriate number [1-3] then [enter] (press 'c' to cancel): 1 Plugins selected: Authenticator nginx, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for wiki.ho.stna.me Using default addresses 80 and [::]:80 ipv6only=on for authentication. Waiting for verification... Cleaning up challenges IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at:</pre> === nginx === == Linux == === Archiver / PeaZip === ==== File Manager Integration (Context Menus) ==== https://peazip.github.io/peazip-linux.html https://wiki.archlinux.org/title/GNOME/Files#Custom_scripts https://github.com/peazip/PeaZip/releases/download/9.5.0/peazip_portable-9.5.0.LINUX.GTK2.x86_64.tar.gz From the portable download, find scripts in the folder: res/share/batch/freedesktop_integration/ <b>Custom scripts</b> Scripts placed in ~/.local/share/nautilus/scripts can be run from the right click context menu of a file. The context menu can also be organized into subfolders, e.g. ~/.local/share/nautilus/scripts/images and ~/.local/share/nautilus/scripts/music. == SmartOS == === Upgrade === <pre> SmartOS (build: 20250220T074131Z) [root@cloud ~]# piadm avail 20250306T000316Z [root@cloud ~]# piadm -v install 20250306T000316Z [root@cloud ~]# piadm list PI STAMP BOOTABLE FILESYSTEM BOOT IMAGE NOW NEXT 20250220T074131Z zones/boot next yes yes 20250306T000316Z zones/boot available no no [root@cloud ~]# piadm -v activate 20250306T000316Z [root@cloud ~]# piadm list PI STAMP BOOTABLE FILESYSTEM BOOT IMAGE NOW NEXT 20250220T074131Z zones/boot available yes no 20250306T000316Z zones/boot next no yes [root@cloud ~]# </pre> === Migrating === https://docs.smartos.org/managing-instances-with-vmamd/#migrate-an-instance-to-a-different-compute-node == FreeBSD == === CUDA === https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=Rocky&target_version=9&target_type=rpm_local <pre> pkg install nvidia-driver kldload nvidia kldload nvidia-modeset # sysrc kld_list+=nvidia-modeset kldload linux64 pkg install linux_base-rl9 pkg install linux-rl9-libxml2 pkg install gcc #gcc13 fetch https://developer.download.nvidia.com/compute/cuda/12.5.1/local_installers/cuda_12.5.1_555.42.06_linux.run ./cuda_12.5.1_555.42.06_linux.run fetch https://developer.download.nvidia.com/compute/cuda/12.5.1/local_installers/cuda-repo-rhel9-12-5-local-12.5.1_555.42.06-1.x86_64.rpm rpm2cpio cuda-repo-rhel9-12-5-local-12.5.1_555.42.06-1.x86_64.rpm > cuda.cpio cpio -idmv < cuda.cpio var/cuda-repo-rhel9-12-5-local# rpm2cpio nvidia-driver-cuda-libs-555.42.06-1.el9.x86_64.rpm > nvidia-driver-cuda-libs-555.42.06-1.el9.x86_64.cpio cpio -idmv < nvidia-driver-cuda-libs-555.42.06-1.el9.x86_64.cpio brandelf -t Linux <path_to_CUDA_installer> ./cuda_<version>_linux.run LD_LIBRARY_PATH=/usr/lib64 ffmpeg -i TheBear-S03E01.ts -c:v h264_nvenc -preset slow -b:v 5000k -maxrate 5000k -bufsize 10000k -pix_fmt yuv420p -c:a aac output.mp4 </pre> === Containers === containerd / runj https://productionwithscissors.run/2022/09/04/containerd-linux-on-freebsd/ <pre> https://catalog.ngc.nvidia.com/orgs/nvidia/containers/cuda/tags nvcr.io/nvidia/cuda:12.5.1-cudnn-devel-ubuntu20.04 https://github.com/canonical/microk8s/issues/1239 #ctr run --rm --gpus 0 docker.io/nvidia/cuda:9.0-base nvidia-smi nvidia-smi ctr image pull --platform=linux nvcr.io/nvidia/cuda:12.5.1-cudnn-devel-ubuntu20.04 </pre> === VMs === ==== qemu / quickemu ==== https://github.com/quickemu-project/quickemu?tab=readme-ov-file <pre> pkg install qemu-nox11 coreutils socat usbutils swtpm zsync samba416 qemu-nox11 edk2-qemu-x64 git clone https://github.com/quickemu-project/quickemu cd quickemu ./quickget alpine v3.11 </pre> <pre>cat freebsd.patch</pre> <pre> diff --git a/quickemu b/quickemu index f2bd9df..2ad1933 100755 --- a/quickemu +++ b/quickemu @@ -652,6 +652,8 @@ function configure_bios() { if command -v brew &>/dev/null; then SHARE_PATH="$(brew --prefix qemu)/share" fi + elif [ "${OS_KERNEL}" == "FreeBSD" ]; then + SHARE_PATH=/usr/local/share fi # https://bugzilla.redhat.com/show_bug.cgi?id=1929357#c5 @@ -675,7 +677,9 @@ function configure_bios() { "${SHARE_PATH}/edk2-ovmf/OVMF_CODE.fd","${SHARE_PATH}/edk2-ovmf/OVMF_VARS.fd" \ "${SHARE_PATH}/qemu/ovmf-x86_64-4m-code.bin","${SHARE_PATH}/qemu/ovmf-x86_64-4m-vars.bin" \ "${SHARE_PATH}/qemu/edk2-x86_64-code.fd","${SHARE_PATH}/qemu/edk2-x86_64-code.fd" \ - "${SHARE_PATH}/edk2-ovmf/x64/OVMF_CODE.fd","${SHARE_PATH}/edk2-ovmf/x64/OVMF_VARS.fd" + "${SHARE_PATH}/edk2-ovmf/x64/OVMF_CODE.fd","${SHARE_PATH}/edk2-ov mf/x64/OVMF_VARS.fd" \ + "${SHARE_PATH}/edk2-qemu/QEMU_UEFI_CODE-x86_64.fd","${SHARE_PATH} /edk2-qemu/QEMU_UEFI_VARS-x86_64.fd" + );; esac # Attempt each EFI_CODE file one by one, selecting the corresponding code and vars </pre> === Linuxulator === Yes, I’m familiar with both '''SmartOS LX zones''' and '''FreeBSD’s Linuxulator'''. These are two different approaches to providing Linux binary compatibility on non-Linux systems, and their differing abilities to run '''systemd''' highlight some key technical distinctions. Let’s break this down and address what’s missing in FreeBSD’s Linuxulator to support systemd, as well as how you might approach enabling it by leveraging SmartOS/Illumos source code. ===== SmartOS LX Zones and FreeBSD Linuxulator ===== * '''SmartOS LX Zones''': LX zones are a feature of Illumos-based systems (like SmartOS) that allow running Linux binaries in a lightweight containerized environment called a "branded zone." These zones provide a near-native Linux kernel ABI (Application Binary Interface) by translating Linux system calls into Illumos equivalents. LX zones were originally developed by Joyent to support running Linux applications, including Docker, on SmartOS. Over time, they’ve been extended to support more complex Linux-specific features, including systemd, which is the default init system for many modern Linux distributions. * '''FreeBSD Linuxulator''': The Linuxulator is FreeBSD’s Linux binary compatibility layer. It allows FreeBSD to run unmodified Linux ELF binaries by translating Linux system calls to FreeBSD equivalents. Unlike LX zones, it’s not a containerization technology but a kernel-level compatibility layer that operates alongside native FreeBSD processes. It currently supports a subset of Linux kernel functionality, with compatibility levels pegged at Linux 3.2.0 in FreeBSD 12-STABLE and Linux 5.15.0 in FreeBSD 14-STABLE (as of recent documentation). However, it lacks support for several Linux-specific features required by systemd. ==== Why Systemd Works in LX Zones but Not Linuxulator ==== Systemd is a complex init system that relies heavily on Linux-specific kernel features, such as: * '''cgroups (Control Groups)''': Used for resource management and process grouping. * '''Namespaces''': Particularly PID, mount, and user namespaces, which provide isolation and scoping for processes. * '''Fanotify''': A file system notification system used by systemd for monitoring file events. * '''Specific System Calls''': Systemd depends on calls like <code>pidfd_open()</code>, <code>clone3()</code>, and others introduced in newer Linux kernels. * '''udev Integration''': Systemd integrates tightly with udev, which relies on Linux-specific device management mechanisms. '''SmartOS LX Zones''' have evolved to support these features. The Illumos kernel, with contributions from Joyent and the SmartOS community, has implemented enough of the Linux kernel ABI—including cgroups, namespaces, and additional system calls—to allow systemd to function within an LX-branded zone. This was driven by the need to support Docker and other modern Linux workloads, which often assume systemd is present. '''FreeBSD Linuxulator''', on the other hand, does not yet support these features fully. While it can run many Linux binaries (e.g., statically linked programs or those with simpler dependencies), its compatibility layer is incomplete for systemd’s requirements. The Linuxulator’s development has historically focused on supporting popular applications (like Steam or proprietary tools) rather than replicating the full Linux kernel feature set, and systemd support has not been a priority. ==== What’s Missing in FreeBSD Linuxulator? ==== To run systemd in FreeBSD’s Linuxulator, the following gaps need to be addressed: ===== 1. cgroups Support ===== * '''Current State''': FreeBSD has no native cgroups implementation. It uses its own resource control mechanisms (e.g., <code>rctl</code> for resource limits and jails for isolation), which are philosophically and technically different from Linux’s cgroups. * '''Requirement''': Systemd expects cgroups v1 or v2 for process grouping, resource limiting, and service management. Without this, systemd cannot initialize properly. ===== 2. Namespaces ===== * '''Current State''': FreeBSD supports some namespace-like features via jails and VNET (virtual networking), but these are not equivalent to Linux’s PID, mount, or user namespaces. The Linuxulator does not translate Linux namespace-related system calls (e.g., <code>unshare()</code>, <code>clone()</code> with namespace flags) into FreeBSD equivalents. * '''Requirement''': Systemd uses namespaces for service isolation and scoping, particularly PID namespaces to manage process trees. ===== 3. System Call Gaps ===== * '''Current State''': The Linuxulator implements a subset of Linux system calls (see <code>sys/compat/linux/linux_sysent.c</code> in the FreeBSD source). Missing calls include newer ones like <code>pidfd_open()</code> (Linux 5.3+), <code>clone3()</code> (Linux 5.3+), and others that systemd may use. * '''Requirement''': Full compatibility with the system calls systemd depends on, which may require extending the Linuxulator’s syscall table. ===== 4. Fanotify and File System Events ===== * '''Current State''': FreeBSD has <code>kqueue</code> for event notification, but it’s not compatible with Linux’s <code>fanotify</code> API, which systemd uses for file system monitoring. * '''Requirement''': An emulation layer to map <code>fanotify</code> calls to <code>kqueue</code> or a custom implementation. ===== 5. udev and Device Management ===== * '''Current State''': FreeBSD uses <code>devd</code> for device management, which differs significantly from Linux’s <code>udev</code>. The Linuxulator does not fully emulate <code>udev</code>’s behavior or its integration with the kernel. * '''Requirement''': Systemd expects <code>udev</code> to manage device events, so a compatibility layer or partial <code>udev</code> emulation is needed. ===== 6. Kernel ABI Stability and Versioning ===== * '''Current State''': The Linuxulator mimics a specific Linux kernel version (e.g., 5.15.0 in FreeBSD 14-STABLE), but systemd may expect features from newer kernels or specific behaviors not yet emulated. * '''Requirement''': Ensuring the emulated ABI matches a Linux kernel version that systemd supports (e.g., at least 4.4 or later for modern versions). ==== Where to Start: Leveraging SmartOS/Illumos Source ==== Since both SmartOS (Illumos) and FreeBSD are open source, you can study the LX zone implementation to guide enhancements to the Linuxulator. Here’s a step-by-step approach: ===== 1. Study Illumos LX Zone Source Code ===== * '''Location''': The relevant code is in the Illumos gate repository, specifically under <code>usr/src/uts/common/brand/lx/</code> and related directories. Key files include: ** <code>lx_syscalls.c</code>: Handles Linux system call emulation. ** <code>lx_cgroups.c</code>: Implements cgroups support. ** <code>lx_namespace.c</code>: Manages Linux namespace emulation. ** <code>lx_fanotify.c</code>: Provides fanotify support. * '''Key Insight''': Illumos has extended its kernel to natively support these features for LX zones, rather than just translating them to existing Solaris/Illumos mechanisms. This suggests FreeBSD may need a hybrid approach—either adding native support or building a more comprehensive translation layer. ===== 2. Map Illumos Features to FreeBSD ===== * '''cgroups''': Start by reviewing <code>lx_cgroups.c</code>. You could either: ** Implement a minimal cgroups shim in the Linuxulator that maps to FreeBSD’s <code>rctl</code> or a new subsystem. ** Port Illumos’s cgroups implementation directly, adapting it to FreeBSD’s kernel architecture. * '''Namespaces''': Look at <code>lx_namespace.c</code>. FreeBSD jails and VNET provide a foundation, but you’d need to extend the Linuxulator to handle <code>clone()</code> and <code>unshare()</code> with namespace flags, possibly by mapping them to jail-like constructs. * '''System Calls''': Compare Illumos’s <code>lx_syscalls.c</code> with FreeBSD’s <code>sys/compat/linux/linux_sysent.c</code>. Add missing syscalls (e.g., <code>pidfd_open()</code>, <code>clone3()</code>) by adapting Illumos’s implementations or writing new ones based on Linux kernel source (e.g., from kernel.org). * '''Fanotify''': Use <code>lx_fanotify.c</code> as a model to build a translation layer from <code>fanotify</code> to <code>kqueue</code>. ===== 3. Modify FreeBSD Linuxulator ===== * '''Source Location''': FreeBSD’s Linuxulator code is in <code>sys/compat/linux/</code> in the FreeBSD source tree (e.g., <code>/usr/src/sys/compat/linux/</code> if you’ve cloned the repo). * '''Steps''': # Extend the syscall table (<code>linux_sysent.c</code>) with missing calls, using Illumos as a reference. # Add new kernel modules or hooks for cgroups and namespaces, potentially under <code>sys/compat/linux/</code>. # Implement fanotify emulation by integrating with <code>kqueue</code>. # Test with a minimal systemd binary (e.g., from a lightweight distro like Alpine) in a chroot environment. ==== 4. Test and Iterate ===== * '''Setup''': Use a FreeBSD jail with Linuxulator enabled (e.g., via <code>sysctl compat.linux.emulation=1</code> and a Linux base system in <code>/compat/linux</code> or <code>/compat/ubuntu</code>). * '''Test Case''': Try running <code>systemd --version</code> or a simple <code>systemd</code> init process. Debug failures using <code>ktrace</code> or <code>truss</code> to identify missing syscalls or features. * '''Reference''': Illumos’s LX zone testing scripts (e.g., in <code>usr/src/test/</code>) can inspire a test suite. ===== 5. Community and Documentation ===== * '''FreeBSD Resources''': Check the FreeBSD Wiki’s Linuxulator page and the <code>linux(4)</code> man page for current capabilities and known gaps. * '''Illumos Resources''': The Illumos wiki and SmartOS documentation provide insights into LX zone internals. * '''Collaboration''': Engage with the FreeBSD and Illumos communities (e.g., via mailing lists like <code>freebsd-hackers@</code> or the Illumos IRC) to validate your approach and get feedback. ==== Challenges and Considerations ==== * '''Philosophical Differences''': FreeBSD avoids adopting Linux-specific features natively (e.g., cgroups) to maintain its distinct identity. You may need to argue for a compatibility-only approach rather than kernel bloat. * '''Performance''': Emulating complex features like cgroups and namespaces could introduce overhead, unlike Illumos’s native integration. * '''Upstream Acceptance''': Contributions to FreeBSD must align with project goals. Systemd support might face resistance unless justified by broad use cases (e.g., Docker compatibility). ==== Starting Point ==== Clone the FreeBSD source (<code>git clone https://git.freebsd.org/src.git</code>) and Illumos gate (<code>git clone https://github.com/illumos/illumos-gate.git</code>). Begin by prototyping cgroups support—perhaps a minimal shim in <code>sys/compat/linux/</code>—and test it with a systemd binary. Use Illumos’s <code>lx_cgroups.c</code> as a blueprint, adapting it to FreeBSD’s kernel structure (e.g., replacing Illumos’s <code>zone_t</code> with FreeBSD’s <code>struct prison</code> for jail integration). This is a significant undertaking, but with both projects being open source, you have the raw materials to bridge the gap. Good luck, and feel free to ask if you need more specific guidance as you dive in! == [[Podman]] == {{:Podman}} == [[WikiJS]] == {{:WikiJS}} == [[TrueNAS]] == {{:TrueNAS}} == [[XigmaNAS]] == {{:XigmaNAS}} == 3d printer == {{:3d printer}} == Formatting == * https://www.mediawiki.org/wiki/Help:Formatting == Extension Setup == old MediaWiki needs old PreToClip version <pre> # cd # git clone https://gerrit.wikimedia.org/r/mediawiki/extensions/PreToClip # cd PreToClip PreToClip# git checkout 924a129 # cd ; mv PreToClip /var/www/html/extensions/ # tail -n2 /var/www/html/LocalSettings.php wfLoadExtension( 'PreToClip' ); <pre> == Getting started == * [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki] hyd3anz9hhu03mdueysadhobjgoe8wm