On 9/29/21 05:59, Nate Bargmann wrote:
Earlier this year I purchased a nice Lenovo Carbon X1 with an NVME SSD
with Win 10 Pro installed. Ordinarily I would reformat the drive
without a second thought but in this case I really do have occasional
need to use Win 10 (Kenwood radio programming mostly) and since swapping
the NVME is not trivial, I've opted to install Bullseye to a USB flash
drive.
A test run with KDE Plasma shows that performance is acceptable even
with EXT4 as the file system. I now have some SanDisk Ultra Fit flash
drives arriving in 128GB capacity (overkill, oh well). I am now
considering what file system would be proper to use in this case. I
understand that the journal can be disabled when using EXT4 to save
writes which is probably fine (this system will be non-critical). I've
also seen that F2FS has been available in the kernel since 3.8, but I'm
unsure whether the installer from a Debian live CD will offer it as a
choice.
The Arch Wiki notes some issues with its fsck and the Debian Wiki is
rather short on details. I found this page[1] that was from 2013 and
updated early last year. The process is not trivial which hints that
F2FS is not included in the Buster installer, at least.
As this is a non-typical installation for a dual-boot configuration that
intends to use UEFI to choose the OS to run, are there tips and
suggestions for this? I have already solved the bug where MS places its
boot image in a directory in the ESP that prevents an EFI enabled
removable media from booting[2] (second paragraph).
TIA
- Nate
[1] https://howtos.davidsebek.com/debian-f2fs.html
[2]
https://wiki.debian.org/UEFI#Force_grub-efi_installation_to_the_removable_media_path
I have several SanDisk UltraFit USB 3.0 Flash Drive 16 GB, and have
installed Debian onto them using btrfs and ext4. Both filesystems work.
btrfs requires periodic re-balancing, which is time consuming.
David
