• 5 Posts
  • 159 Comments
Joined 2 years ago
cake
Cake day: June 5th, 2023

help-circle

  • https://lwn.net/Articles/335415/

    The evince PDF reader ran into this issue back in 2005. It is now rare to find a distributor shipping a version of evince which implements copy restrictions. Xpdf implements copy restrictions unconditionally, but Debian patched that code out in 2002, and that patch has spread to other distributors as well. In general, as one would expect, free PDF readers tend not to implement this behavior. Okular is about the only exception that your editor can find; it’s interesting to note that the version of Okular shipped with Fedora Rawhide also implements copy restrictions by default. Perhaps this behavior is result of the relative newness of this application; as it accumulates more users, the pressure for more user-friendly behavior is likely to grow.


  • Another downside of flatpak is that I don’t trust upstream devs to have my best interests at heart, but I trust Debian developers far more. I’ve seen upstream do some annoying or stupid shit and the Debian maintainers not budging.

    I think it was poppler or evince that decided they were going to enforce the no-copy-and-paste bit you can set on pdfs. Debian patched it out. I’ve seen Mozilla decide they were going to enforce their trademarks. They carved out special exceptions for various distros but that still would have meant you would have to rename Firefox if you were to fork Debian. Debian had none of it. There were many dodgy copyright and licensing problems upstream devs gave no shit about. Debian not including these often eventually put pressure on them to fix this shit or for some replacement to get developed.






  • Oh yeah that’s where I was getting at, but I didn’t have time to write that out earlier. I agree that OP probably pulled out the usb stick before buffers were flushed. I imagine that direct I/O would mitigate this problem a lot because presumably whatever buffers still exist (there would some hardware buffers and I think Linux kernel I/O buffers) will be minimal compared to the potentially large amount of dirty pages one might accumulate using normal cached writes. So I imagine those buffers would be empty very shortly (less than one second maybe?) after dd finishes, whereas I’ve seen regular dd finish tens of seconds before my usb stick stopped blinking it’s LED. Still if you wait for that long the result will be the same.




  • I’m not sure the Trump offer of getting 50% of Ukraine’s mineral wealth was real. The idea didn’t originate from the Trump regime, but it was Ukraine who brought that up first. They’re throwing that back into Ukraine’s face. It seems like they ambushed Zelenski with this ridiculous deal, which was a brazen insult really, and which was immediately rejected (correctly). It might have been the intention to mock them and show them what the actual bill of the US’s Ukraine support would look like, and how Ukraine would never actually be able to pay this debt.

    Trump has called for elections, and that’s because they want to get rid of Zelenski. And I’m sure that will happen. They’re basically overthrowing Zelenski.








  • It’s about as unhinged as someone assembling their own bicycle really. Most people (well, in a reasonably bikeable place, i.e. not in the US) just use their bikes for commuting or whatever, and don’t want to assemble a bike (I sure don’t). Some people like tinkering with their bikes though. That’s totally fine.

    If you’re not prepared to get your hands dirty, don’t buy bike parts you have to assemble yourself. And don’t install Arch. You are correct in the assessment that Arch isn’t for you (or me).

    There are bicycle repair shops, but there are no Arch repair shops. You have to be able to fix it yourself. OP is correct: Don’t recommend Arch to people who can’t do that. Recommend something that doesn’t push bleeding edge untested updates on its users, because it will break and the user will have to fix it themself.

    tl;dr: Arch existing is fine, in the same way any tinker hobby is fine. What is not fine is telling people to use it that just want to get work done or won’t know how to fix it.


  • MEM% for each NetworkManager process is 0.4 % of 3.28 G ≈ 13.1 M. Additionally, almost certainly most of this will be shared between these processes, as well as other processes, so you cannot just add them together.

    The virtual size (315M) is the virtual memory. Quite clearly only 13.1 M of this are actually in use. The rest will only start getting backed by real physical memory if it is being written to.

    The way this works is that the process will get interrupted if it writes to a non-physical memory location (by the memory management unit (MMU); this is known as a page fault), and executions jumps to the kernel which will allocate physical memory and alter the virtual memory table, and then proceed with the execution of the write operation.

    Many programs or library functions like to get way larger virtual memory buffers than they will actually use in practice, because that way the kernel does all this in the background if more memory is needed, and the program doesn’t need to do anything. I.e. it simplifies the code.


  • gnuhaut@lemmy.mltoLinux@lemmy.mlResigning as Asahi Linux project lead
    link
    fedilink
    arrow-up
    15
    arrow-down
    1
    ·
    edit-2
    27 days ago

    I’m not just talking about the US police. I’ve never been to the US, and I assure you the police is shit here too. Ts’o is American, and that “thin blue line” saying seems especially American or Anglo. I’ve never heard that over here. So I’m not sure how that’s even relevant to the discussion.