this post was submitted on 17 Jun 2024
1000 points (99.0% liked)

linuxmemes

21222 readers
109 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 10 points 4 months ago (2 children)

    For me it was the reverse - ntfs-3g was constantly corrupting my windows drives because apparently NTFS is incredibly complicated and it can only handle a subset of that. But, the last time I used dual boot setup was more than 5 years ago. Has this gone any better nowadays?

    [–] [email protected] 9 points 4 months ago (1 children)

    It might be that the default for Windows is to sleep rather than do a full shutdown. Whenever Linux looks at a Windows partition it looks corrupted. When windows starts up again it's inconsistent as some of the data was in the sleep image.

    [–] [email protected] 6 points 4 months ago

    It already detects this and refuses to write to such a partition.