Hi.
Doing some research into how devs are using their dev systems in terms
of the actual layout/partition of the drives. I've seen plenty of
articles, figured I'd ask here as well.
If you have an interested, I'd appreciate your thoughts.
no dev here, but ...
1) How is your drive/system laid out regarding your paritions?
Fedora drive is a btrfs pool with subvolumes for /, /home, /home/<main
user>/DATA
~10 % of the disksize is for overprovisioning and not (!) in the pool
2) Do you have multiple drives (SSD/Sata)?
2 ssd's (one
F34, second win 8.1)
1 external rotating HD (Backup)
3) Is OS on one drive, apps/data on the other?
see 1)
/home/<main user>/DATA was grown as separat, esp. for new installs without need to
shovel big data around (just unmount/unplug, (re-)install OS, remount)
4) Do you switch between OS(es)?
umh, no, I start Win 8.1 via
vbox without special reboot into it. I just staying in Fedora
- boot files generated with:
VBoxManage internalcommands createrawvmdk -filename ./Win_RAW.vmdk -rawdisk /dev/sdX
-partitions 1,2 -relative
- then vbox pointing to that files/disk
5) What's your "backup" process/strategy?
-
weekly rsync to an external rotating HD of /boot, /etc, /home, /lib/modules, /root,
/var/www, /var/lib/radical
6) What's your "update" strategy(ies)?
I'm
not clear what you mean here, but I mostly follow what Fedora/Kernel people "throw
into internet"
I'm looking to get a new system
AMD/ryzen -8core 16G 256G SSD - 1TBSata
get a 500 GB SSD:
- often higher TBW
- often faster then 256
- to get ~10 % of the unused disk size for "overprovisioning" into your account
> I realize that I haven't changed in >10 years, so now is probably a
> good time get up to date on a number of things!
>
> thanks for your insights