Pipewire works well enough for sharing screen even though it isn’t well supported by shit software like Slack. Would this replace it?
Pipewire works well enough for sharing screen even though it isn’t well supported by shit software like Slack. Would this replace it?
Those are very basic mice that will have no issues in Linux if you don’t care about their software.
I am surprised there isn’t an automatic mechanism to handle this especially if it is such a frequent issue.
btrfs dynamically allocates inodes.
Are you sure that’s the case with btrfs? I know ext has that feature. My understanding is btrfs just has a global reserve that can be used for any data in an low space situation.
# sudo btrfs fi usage /mnt/disk3
Overall:
Device size: 12.73TiB
Device allocated: 12.73TiB
Device unallocated: 1.00MiB
Device missing: 0.00B
Device slack: 0.00B
Used: 12.29TiB
Free (estimated): 449.43GiB (min: 449.43GiB)
Free (statfs, df): 449.43GiB
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 512.00MiB (used: 0.00B)
Multiple profiles: no
Data,single: Size:12.70TiB, Used:12.26TiB (96.55%)
/dev/sdd1 12.70TiB
Metadata,DUP: Size:15.00GiB, Used:14.49GiB (96.58%)
/dev/sdd1 30.00GiB
System,DUP: Size:8.00MiB, Used:1.34MiB (16.80%)
/dev/sdd1 16.00MiB
Unallocated:
/dev/sdd1 1.00MiB
I realize that’s not exactly what you asked for but Pipewire had been incredibly stable for me. Difference between the absolute nightmare of using BT devices with alsa and super smooth experience in pipewire is night and day.
I used to work in the same industry. We transferred several PBs from West US to Australia using Aspera via thick AWS pipes. Awesome software.