SAGF
  • Communities
  • Create Post
  • heart
    Support Lemmy
  • search
    Search
  • Login
  • Sign Up
0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · 8 days ago

Theoretical physicists: Actually...

sh.itjust.works

message-square
32
fedilink
343

Theoretical physicists: Actually...

sh.itjust.works

0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · 8 days ago
message-square
32
fedilink
alert-triangle
You must log in or register to comment.
  • Successful_Try543@feddit.org
    link
    fedilink
    arrow-up
    65
    ·
    edit-2
    8 days ago

    The query actually shows a lack of confidence. He should have googled “How to recover a file from /dev/null?” instead.

    • brbposting@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      35
      ·
      8 days ago

      Done

      • Kairos@lemmy.today
        link
        fedilink
        arrow-up
        1
        ·
        2 days ago

        Can you not just try it with a dummy folder??

    • wander1236@sh.itjust.works
      link
      fedilink
      arrow-up
      9
      ·
      edit-2
      8 days ago

      - Stack Overflow

      • sundray@lemmus.org
        link
        fedilink
        English
        arrow-up
        8
        ·
        8 days ago

        Top voted answer

        “Why would you want to?”

  • palordrolap@fedia.io
    link
    fedilink
    arrow-up
    57
    arrow-down
    1
    ·
    8 days ago

    “… you don’t. You recover it from /dev/random. Eventually.”

    • 0x4E4F@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      11
      ·
      edit-2
      8 days ago

      And if really want quality recovery, /dev/urandom. Might take a bit longer, but it’s worth the wait 👌.

  • qjkxbmwvz@startrek.website
    link
    fedilink
    arrow-up
    28
    arrow-down
    1
    ·
    8 days ago

    Duh, just read it back from /dev/random

    You will recover the data, you just need to wait long enough.

    • 0x4E4F@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      6
      ·
      8 days ago

      Patience is key.

  • BaroqueInMind@lemmy.one
    link
    fedilink
    arrow-up
    21
    arrow-down
    1
    ·
    8 days ago

    I mean, if the data was written to a HDD, then any forensic tool can read the magnetic residual patterns on the metal platters instead of looking for file headers?

    • 0x4E4F@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      16
      ·
      8 days ago

      That is true, though it would be pointless to look for it in /dev/null.

      • stoicmaverick@lemmy.world
        link
        fedilink
        arrow-up
        8
        ·
        8 days ago

        There is nothing in /dev/null, and no man needs nothing.

        • SmoothLiquidation@lemmy.world
          link
          fedilink
          English
          arrow-up
          9
          ·
          8 days ago

          A hole would be something, this is NOTHING!

          • 0x4E4F@sh.itjust.worksOP
            link
            fedilink
            English
            arrow-up
            8
            ·
            8 days ago

            /dev/void 🤔

  • stoicmaverick@lemmy.world
    link
    fedilink
    arrow-up
    17
    ·
    8 days ago

    That hack Torvalds keeps denying my pull request to implement /dev/aether which would immediately begin overwriting the entire disk and all other mounted storage with the repeating content of whatever is moved there.

    • 0x4E4F@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      6
      ·
      8 days ago

      That is… brilliant! I love it!

  • TimeSquirrel@kbin.melroy.org
    link
    fedilink
    arrow-up
    14
    ·
    8 days ago

    Programmatically, what does the kernel actually do with data sent to /dev/null? Put it in a temp buffer and just delete it?

    • m_f@midwest.social
      link
      fedilink
      arrow-up
      19
      ·
      8 days ago

      I was also curious, here’s a good answer:

      https://unix.stackexchange.com/questions/670199/how-is-dev-null-implemented

      The implementation is:

      static ssize_t write_null(struct file *file, const char __user *buf,
                    size_t count, loff_t *ppos)
      {
          return count;
      }
      
      • TimeSquirrel@kbin.melroy.org
        link
        fedilink
        arrow-up
        16
        ·
        8 days ago

        So it’s basically doing nothing and lying about it. 😆

        • TaldenNZ@lemmy.nz
          link
          fedilink
          English
          arrow-up
          15
          ·
          8 days ago

          “I accepted all of the bytes you gave me. I didn’t do anything with them, but I accept you gave them to me”.

          • 0x4E4F@sh.itjust.worksOP
            link
            fedilink
            English
            arrow-up
            4
            ·
            8 days ago

            Could’ve at least say thank you…

            • TaldenNZ@lemmy.nz
              link
              fedilink
              English
              arrow-up
              2
              ·
              7 days ago

              It’s open source. If manners are an important feature to you perhaps look into contributing… :)

              • 0x4E4F@sh.itjust.worksOP
                link
                fedilink
                English
                arrow-up
                2
                ·
                6 days ago

                Yeah, that could actually be fun to be honest, lol 😂. But I just know the PR would be rejected, lol 😂.

    • Flipper@feddit.org
      link
      fedilink
      arrow-up
      16
      ·
      8 days ago

      The syscall to write passes a buffer and length. If it is Dev null the call just returns without doing anything more.

    • Boxscape@lemmy.sdf.org
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      8 days ago

      Programmatically, what does the kernel actually do with data sent to /dev/null?

      I imagine it’s like getting nullified in that olde show ReBoot.

  • CO5MO ✨@midwest.social
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    8 days ago

    This is the worst meme template, ever

  • Possibly linux@lemmy.zip
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 days ago

    Why would you be trying to recover something from a virtual device?

    • 0x4E4F@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      8 days ago

      Because apparently, he moved it there… and doesn’t know what /dev/null is…

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        8 days ago

        It is still on the disk though

        Do people not understand how files work? Actually never mind that makes sense.

        • shyguyblue@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          8 days ago

          Do people not understand how files work?

          Oh honey, imagine trying to tech-support a family of rednecks. Threaten to charge them for services and they’ll stop pretty quick though…

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        8 days ago

        It is still on the disk though

        Do people not understand how files work? Actually never mind that makes sense.

        • 0x4E4F@sh.itjust.worksOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 days ago

          Yes.

linuxmemes@lemmy.world

linuxmemes@lemmy.world

Subscribe from Remote Instance

Create a post
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !linuxmemes@lemmy.world

Hint: :q!


Sister communities:
  • LemmyMemes: Memes
  • LemmyShitpost: Anything and everything goes.
  • RISA: Star Trek memes and shitposts

Community rules (click to expand)

1. Follow the site-wide rules
  • Instance-wide TOS: https://legal.lemmy.world/tos/
  • Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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!

Visibility: Public
globe

This community can be federated to other instances and be posted/commented in by their users.

  • 1.17K users / day
  • 3.39K users / week
  • 7.08K users / month
  • 18.5K users / 6 months
  • 1 local subscriber
  • 21.1K subscribers
  • 1.27K Posts
  • 64K Comments
  • Modlog
  • mods:
  • Kevin@lemmy.world
  • zephyr@lemmy.world
  • rtxn@lemmy.world
  • BE: 0.19.5
  • Modlog
  • Instances
  • Docs
  • Code
  • join-lemmy.org