mirror of https://gitlab.com/octtspacc/OcttKB
41 lines
1.9 KiB
Plaintext
41 lines
1.9 KiB
Plaintext
created: 20230111153758951
|
|
creator: Octt
|
|
icon: 🐧
|
|
modified: 20230725113527726
|
|
modifier: Octt
|
|
page-cover: https://images.unsplash.com/photo-1549605659-32d82da3a059?ixlib=rb-4.0.3&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D
|
|
tags: $:/i18n:en Unix
|
|
title: Linux
|
|
|
|
<<^wikipediaframe Linux en>>
|
|
|
|
!! ''Docs''
|
|
|
|
* [[The Linux Kernel documentation|https://docs.kernel.org/]]
|
|
* [[Embedded Linux Wiki|https://elinux.org/Main_Page]]
|
|
|
|
!!! ''Manpages''
|
|
|
|
* on [[linux die|https://linux.die.net/]]
|
|
* or, simplified: [[tldr pages|https://tldr.sh/]] --- <<#[ Git "https://github.com/tldr-pages">>
|
|
|
|
!!! ''Misc''
|
|
|
|
* LDP (obsolete?)
|
|
** [[The Network Administrators' Guide|https://tldp.org/LDP/nag/]]
|
|
|
|
* [[SquashFS|https://tldp.org/HOWTO/SquashFS-HOWTO/whatis.html]], [[DwarFS|https://github.com/mhx/dwarfs]]
|
|
* cannot access fuse mount as root or other users, [[Why does root get Permission denied when accessing FUSE directory?|https://unix.stackexchange.com/questions/17402/why-does-root-get-permission-denied-when-accessing-fuse-directory#17423]] --- To allow access to other users, add `user_allow_other` in `/etc/fuse.conf`, then mount fs with `-o allow_root` (only root) or `-o allow_other` (any user, including root).
|
|
|
|
* [[systemd-nspawn|https://wiki.archlinux.org/title/Systemd-nspawn]] --- //chroot on steroids// for systemd hosts and guests
|
|
|
|
* [[Running a script every time a new kernel is installed|https://unix.stackexchange.com/questions/30320/running-a-script-every-time-a-new-kernel-is-installed]] --- Just place a sh script in `/etc/kernel/postinst.d/`
|
|
|
|
!!! ''Benchmarks''
|
|
|
|
* [[Paul Raspberry Pi Benchmarks|https://willy-tech.de/raspberry-pi-benchmarks/]]
|
|
|
|
!!! ''Troubleshooting''
|
|
|
|
* [[cannot mount /dev/loop1 read-only|https://serverfault.com/questions/839898/cannot-mount-block-device-dev-loop-read-only]] --- Filesystem might have a dirty log, using `-o norecovery` can still mount it readonly.
|