Relocating Fedora's RPM database

Posted Jan 13, 2022 11:36 UTC (Thu) by nim-nim (subscriber, #34454)
In reply to: Relocating Fedora's RPM database by nim-nim
Parent article: Relocating Fedora's RPM database

(For all its faults the FHS is the child of sysadmins that could not handwave away data loss)

Relocating Fedora's RPM database

Posted Jan 13, 2022 16:33 UTC (Thu) by smoogen (subscriber, #97) [Link] (2 responses)

Agreed. I got off the mailing lists and out of the argument because that is the fundamental gulf in understanding. There is computing which has clouds of failover data so that downtime can be limited due to 'unlimited VC money' and there is computing which is done on a typical shoestring budget which will take a long time to recover from if a 'reset' happens. Assuming /var should be wipeable and resetable at anytime works well in the 'we can just spin up more instances and keep cold copies or some other <fill in trend today> term' It doesn't work in 'real' systems administration where they are dealing with budgets set 20 years ago.

Relocating Fedora's RPM database

Posted Jan 13, 2022 17:07 UTC (Thu) by dbnichol (subscriber, #39622) [Link]

With my sysadmin hat on, I usually like to put application data (e.g., a website or repositories) in /srv whereas system program data (e.g., the package manager database) lives in /var. Some programs make this easier than others, but then it's straightforward for me to know where the data I actually care about is should it need to be backed up or migrated.

Relocating Fedora's RPM database

Posted Jan 13, 2022 19:45 UTC (Thu) by walters (subscriber, #7396) [Link]

No one is assuming /var is wipable at any time.

See https://lwn.net/Articles/881260/