linux:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
linux:start [2026/04/26 22:11] – [Diagnostics] mhlinux:start [2026/10/31 22:34] (current) – [claude] align eGPU link label with page title (Core X) claude
Line 3: Line 3:
   -**[[linux:bash|Bash]]**   -**[[linux:bash|Bash]]**
   -**[[linux:git|Git basics]]**   -**[[linux:git|Git basics]]**
-  -**[[linux:eGPU|Razer Core eGPU]]**+  -**[[linux:eGPU|Razer Core X eGPU]]**
   -**[[linux:RBS|Razer Blade Stealth in Linux]]**   -**[[linux:RBS|Razer Blade Stealth in Linux]]**
  
Line 19: Line 19:
  
 <code bash> <code bash>
-tail -f /var/log/syslog+tail -f /var/log/syslog   # if rsyslog is installed 
 +journalctl -f             # systemd journal (Fedora, Debian 12+)
 </code> </code>
  
Line 37: Line 38:
 ===== System information ===== ===== System information =====
  
-=== General overview: ===+=== General overview ===
  
 <code bash> <code bash>
Line 43: Line 44:
 </code> </code>
  
-=== Distribution: ===+=== Distribution ===
  
 <code bash> <code bash>
Line 49: Line 50:
 </code> </code>
  
-=== Kernel: ===+=== Kernel ===
  
 <code bash> <code bash>
Line 59: Line 60:
   *''s'': kernel name   *''s'': kernel name
   *''n'': network node hostname   *''n'': network node hostname
-  *''r'': kernel relase number+  *''r'': kernel release number
   *''m'': machine hardware name   *''m'': machine hardware name
  
  
-=== CPU: ===+=== CPU ===
  
 <code bash> <code bash>
Line 70: Line 71:
 </code> </code>
  
-=== Memory: ===+=== Memory ===
  
 <code bash> <code bash>
Line 76: Line 77:
 </code> </code>
  
-=== Mounted filesystems: ===+=== Mounted filesystems ===
  
 <code bash> <code bash>
Line 82: Line 83:
 </code> </code>
  
-=== Kernel modules: ===+=== Kernel modules ===
  
 <code bash> <code bash>
Line 88: Line 89:
 </code> </code>
  
-=== Bash history: ===+=== Bash history ===
  
 <code bash> <code bash>
Line 102: Line 103:
 dmesg -T | tail     # recent kernel messages dmesg -T | tail     # recent kernel messages
 vmstat 1            # system performance vmstat 1            # system performance
-mpstat -P ALL 1     # CPU usage per core +mpstat -P ALL 1     # CPU usage per core (package: sysstat) 
-pidstat             # process statistics+pidstat             # process statistics (package: sysstat)
 free -h             # memory usage free -h             # memory usage
 </code> </code>
Line 109: Line 110:
  
 ====== Storage & Filesystems ====== ====== Storage & Filesystems ======
 +
 +===== Mounting =====
 +
 +=== List mounts ===
 +
 +<code bash>
 +findmnt
 +</code>
 +
 +=== List disks ===
 +
 +<code bash>
 +lsblk
 +</code>
 +
 +=== Mount ===
 +
 +<code bash>
 +sudo mkdir -p /media/DRIVE
 +sudo mount /dev/sdX# /media/DRIVE
 +</code>
 +
 +=== Unmount ===
 +
 +<code bash>
 +sudo umount /media/DRIVE
 +</code>
 +
 +----
 +
 +===== Samba =====
 +
 +==== Manage service ====
 +
 +<code bash>
 +sudo systemctl start smbd
 +sudo systemctl stop smbd
 +sudo systemctl restart smbd
 +</code>
 +
 +----
 +
 +==== List available shares ====
 +
 +<code bash>
 +smbclient -L //host -U username
 +</code>
 +
 +  * ''host'' → hostname or IP of the server
 +  * prompts for password
 +
 +----
 +
 +==== Access a share (temporary mount) ====
 +
 +Create mount point if needed:
 +
 +<code bash>
 +sudo mkdir -p /mnt/share
 +</code>
 +
 +Then mount:
 +
 +<code bash>
 +sudo mount -t cifs //host/share /mnt/share -o username=user
 +</code>
 +
 +----
 +
 +==== GUI mounts (file manager) ====
 +
 +When mounting via a file manager (Nautilus, Nemo, etc.), shares are typically mounted under:
 +
 +<code>
 +/run/user/UID/gvfs/
 +</code>
 +
 +----
 +
 +==== Notes ====
 +
 +<WRAP info>
 +**Notes:**
 +
 +  * ''smbclient -L'' is useful for discovery and debugging access issues
 +  * ''mount -t cifs'' provides a standard way to mount shares in scripts or system configs
 +  * SMB1 is deprecated and may be disabled on modern systems
 +</WRAP>
 +
 +----
 +
 +===== Mount/Repair NTFS =====
 +
 +If an NTFS volume mounts as read-only, it is usually due to an unclean shutdown or filesystem inconsistency.
 +
 +Attempt repair:
 +
 +<code bash>
 +sudo ntfsfix /dev/sdX#
 +</code>
 +
 +Create mount point if needed:
 +
 +<code bash>
 +sudo mkdir -p /mnt/ntfs
 +</code>
 +
 +Then remount:
 +
 +<code bash>
 +sudo mount -t ntfs3 /dev/sdX# /mnt/ntfs
 +</code>
 +
 +<WRAP info>
 +**Notes:**
 +
 +  * ''ntfsfix'' performs basic repairs and clears the "dirty" flag
 +  * Full repair should be done from Windows using ''chkdsk''
 +  * If the issue persists, ensure Windows Fast Startup is disabled
 +</WRAP>
 +
 +===== Repair FAT32 filesystem errors =====
 +
 +If a FAT32 filesystem mounts as read-only, it is often due to detected corruption.
 +
 +Check kernel logs:
 +
 +<code bash>
 +dmesg
 +</code>
 +
 +Typical errors:
 +
 +<code bash>
 +FAT-fs (sdb1): error, corrupted directory (invalid entries)
 +FAT-fs (sdb1): Filesystem has been set read-only
 +FAT-fs (sdb1): error, invalid access to FAT
 +</code>
 +
 +Repair the filesystem:
 +
 +<code bash>
 +sudo umount /dev/sdX#
 +sudo fsck.vfat -a -w /dev/sdX#
 +</code>
 +
 +  * ''-a'' automatically repair filesystem
 +  * ''-w'' write changes to disk
 +
 +Note: Ensure the correct device is targeted before running ''fsck''.
 +
 +
 +====== File & Data Operations ======
 +
 +===== Shell toolbox =====
 +
 +==== File operations ====
 +
 +=== Mass renaming ===
 +
 +__**Changing an extension:**__
 +
 +<code bash>
 +for i in *.JPG; do mv "$i" "${i/.JPG/.jpg}"; done
 +</code>
 +
 +__**Changing a prefix:**__
 +
 +<code bash>
 +for i in "prefix"*.png; do
 +  mv -n -- "$i" "${i/#prefix/another prefix}"
 +done
 +</code>
 +
 +  * ''"prefix"*.png'' targets only files beginning with the selected prefix, so unrelated files in the folder are ignored.
 +  * ''${i/#prefix/another prefix}'' replaces only the prefix at the beginning of the filename. If the same text appears later in the filename, it is left untouched.
 +  * In Bash parameter expansion, the ''#'' before ''prefix'' means “match only at the start of the variable value”. Without ''#'', Bash would replace the first matching occurrence anywhere in the filename.
 +  * ''mv -n'' prevents overwriting an existing file if the renamed target already exists.
 +  * ''--'' tells ''mv'' that everything after it is a filename, not an option. This protects against unusual filenames starting with ''-''.
 +  * ''"$i"'' keeps the original filename safely quoted, so spaces and special characters in filenames are preserved.
 +
 +__**Alternative (rename tool):**__
 +
 +<code bash>
 +rename 's/\.JPG$/.jpg/' *.JPG
 +</code>
 +
 +  * Use the ''for ... done'' + ''mv -n --'' loop for safe, explicit prefix renaming.
 +  * Use ''rename'' for concise regex-based changes, especially extension changes such as ''.JPG'' to ''.jpg''.
 +  * On Linux Mint / Ubuntu, ''rename 's/\.JPG$/.jpg/' *.JPG'' usually works because the available ''rename'' is the Perl-style tool.
 +  * On Ubuntu / Mint the Perl-style ''rename'' is a separate package and is not always preinstalled: ''sudo apt install rename''.
 +  * The ''rename'' command is not fully portable across all Linux distributions, because different systems may ship different versions with different syntax.
 +  * For safety, preview first with ''rename -n 's/\.JPG$/.jpg/' *.JPG''.
 +
 +----
 +
 +=== Empty a file ===
 +
 +<code bash>
 +: > /path/to/file
 +</code>
 +
 +----
 +
 +==== Text processing ====
 +
 +=== cut ===
 +
 +Extract part of a string:
 +
 +<code bash>
 +date | cut -c17-24
 +</code>
 +
 +----
 +
 +==== Archives ====
 +
 +=== tar ===
 +
 +<code bash>
 +# Extract
 +tar -xvf file.tar
 +tar -xvzf file.tar.gz
 +
 +# Create
 +tar -cvf file.tar /path/folder
 +tar -cvzf file.tar.gz /path/folder
 +</code>
 +
 +Flags:
 +
 +  * ''c'' create archive
 +  * ''x'' extract archive
 +  * ''v'' verbose (list files processed)
 +  * ''f'' specify archive file
 +  * ''z'' gzip compression
 +
 +----
 +
 +====== User Environment ======
 +
 ===== PATH ===== ===== PATH =====
 <WRAP round info> <WRAP round info>
Line 144: Line 387:
 </code> </code>
  
-[[http://refspecs.linuxfoundation.org/fhs.shtml|FHS Reference]]+[[https://refspecs.linuxfoundation.org/fhs.shtml|FHS Reference]]
  
 === Add to PATH === === Add to PATH ===
Line 246: Line 489:
 <code> <code>
 GRUB_BACKGROUND=/path/to/image.jpg GRUB_BACKGROUND=/path/to/image.jpg
 +</code>
 +
 +Apply the change:
 +
 +<code bash>
 +# Ubuntu / Mint
 +sudo update-grub
 +
 +# Fedora
 +sudo grub2-mkconfig -o /boot/grub2/grub.cfg
 </code> </code>
  
Line 278: Line 531:
  
 <code bash> <code bash>
-$ sudo fc-cache -f -v+fc-cache -f -v
 </code> </code>
  
Line 315: Line 568:
  
 It often reduces file size, especially with image-heavy PDFs, but this is not guaranteed. It often reduces file size, especially with image-heavy PDFs, but this is not guaranteed.
-</WRAP> 
- 
-===== Repair FAT32 filesystem errors ===== 
- 
-If a FAT32 filesystem mounts as read-only, it is often due to detected corruption. 
- 
-Check kernel logs: 
- 
-<code bash> 
-dmesg 
-</code> 
- 
-Typical errors: 
- 
-<code bash> 
-FAT-fs (sdb1): error, corrupted directory (invalid entries) 
-FAT-fs (sdb1): Filesystem has been set read-only 
-FAT-fs (sdb1): error, invalid access to FAT 
-</code> 
- 
-Repair the filesystem: 
- 
-<code bash> 
-sudo umount /dev/sdX# 
-sudo fsck.vfat -a -w /dev/sdX# 
-</code> 
- 
-  * ''-a'' automatically repair filesystem 
-  * ''-w'' write changes to disk 
- 
-Note: Ensure the correct device is targeted before running ''fsck''. 
- 
- 
-===== Data recovery ===== 
- 
-Use **TestDisk** / **PhotoRec** as a first recovery tool. 
- 
-  * **TestDisk** attempts partition repair and file undelete when filesystem metadata is still usable. 
-  * **PhotoRec** performs file carving by signature. It can recover files from damaged filesystems, but filenames and folder structure are usually lost. 
- 
-Do not write recovered files to the source disk. 
- 
-==== PhotoRec: recovered MOV files ==== 
- 
-For some recovered ''.mov'' files, PhotoRec may split the video into separate ''ftyp'' and ''mdat'' parts. 
- 
-In PhotoRec ''FileOpts'', enable: 
- 
-<code> 
-[X] mov/mdat Recover mdat atom as a separate file 
-</code> 
- 
-Sort recovered files by name, then try concatenating matching parts: 
- 
-<code bash> 
-cat f123_ftyp.mov f456_mdat.mov > recovered_1.mov 
-cat f456_mdat.mov f123_ftyp.mov > recovered_2.mov 
-</code> 
- 
-One order may produce a usable file. 
- 
-Sometimes the header/container part may be ''.mp4'' while the media data part is ''.mov'': 
- 
-<code bash> 
-cat f54114560.mp4 f51781632_mdat.mov > recovered.mov 
-</code> 
- 
-Note: This is a recovery attempt, not a guaranteed repair method. For valuable data, stop using the disk immediately and clone/image it before experimenting. 
- 
-===== Mount/Repair NTFS ===== 
- 
-If an NTFS volume mounts as read-only, it is usually due to an unclean shutdown or filesystem inconsistency. 
- 
-Attempt repair: 
- 
-<code bash> 
-sudo ntfsfix /dev/sdX# 
-</code> 
- 
-Then remount: 
- 
-<code bash> 
-sudo mount -t ntfs3 /dev/sdX# /mnt/ntfs 
-</code> 
- 
-Create mount point if needed: 
- 
-<code bash> 
-sudo mkdir -p /mnt/ntfs 
-</code> 
- 
-<WRAP info> 
-**Notes:** 
- 
-  * ''ntfsfix'' performs basic repairs and clears the "dirty" flag 
-  * Full repair should be done from Windows using ''chkdsk'' 
-  * If the issue persists, ensure Windows Fast Startup is disabled 
 </WRAP> </WRAP>
  
Line 464: Line 620:
 osdlevel=0 osdlevel=0
 </code> </code>
- 
-===== Using Apple USB SuperDrive ===== 
- 
-The Apple USB SuperDrive requires a vendor-specific command to activate on non-Apple systems. 
- 
-=== Required package === 
- 
-<code bash> 
-sudo apt install sg3-utils 
-</code> 
- 
-=== Identify device === 
- 
-Usually appears as ''/dev/sr0'': 
- 
-<code bash> 
-lsblk 
-</code> 
- 
-=== Send activation command === 
- 
-<code bash> 
-sudo sg_raw /dev/sr0 EA 00 00 00 00 00 01 
-</code> 
- 
-The drive should become usable immediately after. 
- 
-<WRAP info> 
-**Note:** This command must be reissued after reconnecting the drive. 
-</WRAP> 
- 
-===== QCAD (plugin location) ===== 
- 
-<WRAP center round alert 60%> 
-NOTE : MOVE TO BOTTOM 'MISC' SECTION AFTER REWRITE 
-</WRAP> 
- 
- 
-To locate the QCAD plugin directory: 
- 
-Go to: 
-  * Help > About > Plugins (Linux / Windows) 
-  * QCAD > About > Plugins (macOS) 
- 
-Click on any plugin name to reveal its file location. 
- 
-<WRAP info> 
-**Note:** Useful for locating and removing plugins related to trial limitations. 
-</WRAP> 
- 
-===== Screen recording ===== 
- 
-==== Recommended ==== 
- 
-  * **OBS Studio** → full-featured, actively maintained, works for both simple and advanced recording 
- 
-==== Lightweight alternatives ==== 
- 
-  * simplescreenrecorder → lightweight, reliable on X11 
-  * vokoscreenNG → simple GUI, good for quick recordings 
- 
-==== Notes ==== 
- 
-  * Older tools such as Kazam or gtk-recordmydesktop are largely unmaintained and may not work reliably on modern systems 
-  * Wayland sessions may require OBS or desktop-native recording tools 
- 
-===== Samba ===== 
- 
-==== List available shares ==== 
- 
-<code bash> 
-smbclient -L //host -U username 
-</code> 
- 
-  * ''host'' → hostname or IP of the server 
-  * prompts for password 
- 
----- 
- 
-==== Access a share (temporary mount) ==== 
- 
-<code bash> 
-sudo mount -t cifs //host/share /mnt/share -o username=user 
-</code> 
- 
-Create mount point if needed: 
- 
-<code bash> 
-sudo mkdir -p /mnt/share 
-</code> 
- 
----- 
- 
-==== GUI mounts (file manager) ==== 
- 
-When mounting via a file manager (Nautilus, Nemo, etc.), shares are typically mounted under: 
- 
-<code> 
-/run/user/UID/gvfs/ 
-</code> 
- 
----- 
- 
-==== Notes ==== 
- 
-<WRAP info> 
-**Notes:** 
- 
-  * ''smbclient -L'' is useful for discovery and debugging access issues 
-  * ''mount -t cifs'' provides a standard way to mount shares in scripts or system configs 
-  * SMB1 is deprecated and may be disabled on modern systems 
-</WRAP> 
  
 ===== Alias ===== ===== Alias =====
Line 623: Line 667:
 </code> </code>
  
-===== Mouse button mapping =====+===== Package management =====
  
-==== X11 method (xbindkeys) ====+==== Fix broken packages ====
  
-Install tools:+__**Ubuntu / Mint (apt):**__
  
 <code bash> <code bash>
-sudo apt install xbindkeys xvkbd+sudo dpkg --configure -a 
 +sudo apt --fix-broken install
 </code> </code>
  
-Identify button codes:+__**Fedora (dnf):**__
  
 <code bash> <code bash>
-xev | grep button+sudo dnf distro-sync 
 +sudo rpm --rebuilddb
 </code> </code>
  
-Create configuration:+  * ''dnf distro-sync'' realigns installed packages with the repositories and resolves inconsistent dependencies 
 +  * ''rpm --rebuilddb'' rebuilds the RPM database if it is damaged
  
-<code bash> 
-touch ~/.xbindkeysrc 
-</code> 
  
-Example:+====== Specialized & Recovery ====== 
 + 
 +===== Data recovery ===== 
 + 
 +Use **TestDisk** / **PhotoRec** as a first recovery tool. 
 + 
 +  * **TestDisk** attempts partition repair and file undelete when filesystem metadata is still usable. 
 +  * **PhotoRec** performs file carving by signature. It can recover files from damaged filesystems, but filenames and folder structure are usually lost. 
 + 
 +Do not write recovered files to the source disk. 
 + 
 +==== PhotoRec: recovered MOV files ==== 
 + 
 +For some recovered ''.mov'' files, PhotoRec may split the video into separate ''ftyp'' and ''mdat'' parts. 
 + 
 +In PhotoRec ''FileOpts'', enable:
  
 <code> <code>
-# Send Enter on mouse button 8 +[X] mov/mdat Recover mdat atom as a separate file
-"xvkbd -text '\r'" +
-b:8+
 </code> </code>
  
-Start xbindkeys:+Sort recovered files by name, then try concatenating matching parts:
  
 <code bash> <code bash>
-xbindkeys+cat f123_ftyp.mov f456_mdat.mov > recovered_1.mov 
 +cat f456_mdat.mov f123_ftyp.mov > recovered_2.mov
 </code> </code>
  
-----+One order may produce a usable file.
  
-<WRAP info> +Sometimes the header/container part may be ''.mp4'' while the media data part is ''.mov'':
-**Notes:**+
  
-  * Works on X11 sessions only +<code bash> 
-  * Wayland sessions generally do not support this method +cat f54114560.mp4 f51781632_mdat.mov > recovered.mov 
-  * ''xvkbd'' simulates keypresses; alternative tools may be preferred depending on use case +</code>
-</WRAP>+
  
-===== Shell toolbox =====+Note: This is a recovery attempt, not a guaranteed repair method. For valuable data, stop using the disk immediately and clone/image it before experimenting.
  
-==== File operations ==== 
  
-=== Mass renaming === 
  
-Uppercase .JPG to lowercase .jpg+===== Using Apple USB SuperDrive =====
  
-<code bash> +The Apple USB SuperDrive requires a vendor-specific command to activate on non-Apple systems.
-for i in *.JPG; do mv "$i" "${i/.JPG/.jpg}"; done +
-</code>+
  
-Alternative (rename tool):+=== Required package ===
  
 <code bash> <code bash>
-rename 's/\.JPG$/.jpg/' *.JPG+sudo apt install sg3-utils
 </code> </code>
  
-----+=== Identify device ===
  
-=== Empty a file ===+Usually appears as ''/dev/sr0'':
  
 <code bash> <code bash>
-: > /path/to/file+lsblk
 </code> </code>
  
-----+=== Send activation command ===
  
-==== Text processing ====+<code bash> 
 +sudo sg_raw /dev/sr0 EA 00 00 00 00 00 01 
 +</code>
  
-=== cut ===+The drive should become usable immediately after.
  
-Extract part of a string:+<WRAP info> 
 +**Note:** This command must be reissued after reconnecting the drive. 
 +</WRAP>
  
-<code bash> +===== Additional Resources =====
-date | cut -c17-24 +
-</code>+
  
-----+  * [[https://en.wikipedia.org/wiki/Magic_SysRq_key#Configuration|SysRq Keys]] -- Best combo is ''Alt + SysRq + R E I S U B'' 
 +  * [[https://wiki.networksecuritytoolkit.org/nstwiki/index.php?title=HowTo_Create_A_GPT_Disk_With_EFI_System_And_exFAT_Partitions_Using_Parted|Creating GPT/exFAT partitions using CLI]]
  
-==== Archives ==== 
  
-=== tar ===+====== Misc / Desktop ======
  
-<code bash> +===== Screen recording =====
-# Extract +
-tar -xvf file.tar +
-tar -xvzf file.tar.gz+
  
-# Create +==== Recommended ====
-tar -cvf file.tar /path/folder +
-tar -cvzf file.tar.gz /path/folder +
-</code>+
  
-Flags:+  * **OBS Studio** → full-featured, actively maintained, works for both simple and advanced recording
  
-  * ''c'' create archive +==== Lightweight alternatives ====
-  * ''x'' extract archive +
-  * ''v'' verbose (list files processed) +
-  * ''f'' specify archive file +
-  * ''z'' gzip compression+
  
-----+  * simplescreenrecorder → lightweight, reliable on X11 
 +  * vokoscreenNG → simple GUI, good for quick recordings 
 +  * Spectacle → on Fedora (KDE Plasma), the native screenshot tool can also record video; nothing to install
  
-==== Mounting ====+==== Notes ====
  
-=== List mounts: ===+  * Older tools such as Kazam or gtk-recordmydesktop are largely unmaintained and may not work reliably on modern systems 
 +  * Wayland sessions may require OBS or desktop-native recording tools
  
-<code bash> +===== Mouse button mapping =====
-findmnt +
-</code>+
  
-=== List disks: ===+==== X11 method (xbindkeys) ==== 
 + 
 +Install tools:
  
 <code bash> <code bash>
-lsblk+sudo apt install xbindkeys xvkbd
 </code> </code>
  
-=== Mount: ===+Identify button codes:
  
 <code bash> <code bash>
-sudo mkdir -p /media/DRIVE +xev | grep button
-sudo mount /dev/sdX# /media/DRIVE+
 </code> </code>
  
-=== Unmount: ===+Create configuration:
  
 <code bash> <code bash>
-sudo umount /media/DRIVE+touch ~/.xbindkeysrc
 </code> </code>
  
-----+Example:
  
-==== Samba ==== +<code> 
- +# Send Enter on mouse button 8 
-Manage service: +"xvkbd -text '\r'" 
- +b:8
-<code bash> +
-sudo systemctl start smbd +
-sudo systemctl stop smbd +
-sudo systemctl restart smbd+
 </code> </code>
  
----- +Start xbindkeys:
- +
-==== Package management ==== +
- +
-=== Fix broken packages ===+
  
 <code bash> <code bash>
-sudo dpkg --configure -a +xbindkeys
-sudo apt --fix-broken install+
 </code> </code>
  
 ---- ----
  
 +<WRAP info>
 +**Notes:**
  
 +  * Works on X11 sessions only
 +  * Wayland sessions generally do not support this method
 +  * ''xvkbd'' simulates keypresses; alternative tools may be preferred depending on use case
 +</WRAP>
  
-===== Additional Ressources =====+===== QCAD (plugin location) =====
  
-  ***[[https://en.wikipedia.org/wiki/Magic_SysRq_key#Configuration|SysRq Keys]]** -- Best combo is ''Alt + SysRq + R E I S U B''+To locate the QCAD plugin directory:
  
-  ***[[https://www.guruadvisor.net/en/software-saas/465-advanced-linux-troubleshooting-methods-and-tools-for-diagnostics-and-problem-identification|Advanced Linux Troubleshooting]]**+Go to: 
 +  * Help > About > Plugins (Linux / Windows) 
 +  * QCAD > About > Plugins (macOS)
  
-  ***[[https://wiki.networksecuritytoolkit.org/nstwiki/index.php?title=HowTo_Create_A_GPT_Disk_With_EFI_System_And_exFAT_Partitions_Using_Parted|Creating GPT/exFAT partitions using CLI]]**+Click on any plugin name to reveal its file location. 
 + 
 +<WRAP info> 
 +**Note:** Useful for locating and removing plugins related to trial limitations. 
 +</WRAP>
  • linux/start.1777234301.txt.gz
  • Last modified: 2026/04/26 22:11
  • by mh