563
To be honest, it is quite complicated now as well with all of the proprietary software (sh.itjust.works)
submitted 5 months ago by 0x4E4F@sh.itjust.works to c/linuxmemes@lemmy.world
151 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[-] 0x4E4F@sh.itjust.works 13 points 5 months ago* (last edited 5 months ago)

Always remember, C:\ProgramData is the eqivalent of /etc in Linux. If they don't know where to put/hide shit, but needs admin priviliges to edit and users can only read, you put it in C:\ProgramData.

[-] Hawke@lemmy.world 13 points 5 months ago* (last edited 5 months ago)

I think programdata is closer to /usr/lib or maybe /var/lib.

You almost never see config files in programdata.

[-] 0x4E4F@sh.itjust.works 1 points 5 months ago* (last edited 5 months ago)

Config files that are meant to be used as sane defaults for new user accounts, yes. Config files that are meant to be manually edited, no.

Besides, there are a lot of examples of configs that are saved in ProgramData, like, let's say, registration info for proprietery programs (of course, this info needs to be shared amongst users, so your safest bet is ProgramData). Hidden by default, makes it perfect for storing everything the program is trying to hide from the user.

this post was submitted on 20 Apr 2024
563 points (90.9% liked)

linuxmemes

20707 readers
2328 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
poopsmith@lemmy.world
zephyr@lemmy.world