• 504 Posts
  • 7K Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle




  • Other comments are just giving you solutions without explaining the actual underlying question you’re asking, so let me break it down a bit:

    Linux is the underlying system that runs everything, and the desktop you’re seeing is just a Desktop Environment (aka: DE) running on top of that. Mint has its own DE called Cinnamon. The other big DE’s are Gnome and KDE.

    The user experience of how each DE handles mounting other drives varies, sometimes depending on how they are specifically setting defaults for each distro. For instance, Gnome and KDE will proactively mount other drives which you can access in their respective file explorers by default, while Cinnamon does not AFAIK. For things like removable storage, all of them should work as Windows does and be automatic.

    If you really like Cinnamon and want to stick with Mint, look into a search like “cinnamon automount windows volume” or similar. There’s tons of instructions out there, and some responses here have links as well.

    Otherwise, maybe try a LiveUSB of Fedora for a solid Gnome desktop, or KDE Neon for a KDE desktop and see if either of those appeals to you.



  • Another startup claiming a breakthrough on old tech. This isn’t anything new, and barely an improvement on elctrolyzers from the 50’s.

    The same problem exists with this as any other seawater extraction process: there will be byproducts that need to be disposed of. Desalinization creates a toxic brine, and this process will create a solution of seawater minus character components. This process takes seawater and removes Magnesium Chloride, keeps it in a molten state, then removes the magnesium. So you’re left with Magnesium, Magnesium Oxide as the useful byproducts, BUT…also Mercury, Lead, Sulphurous waste…etc.

    While they say they intend to run “net-zero emissions”, I believe they are strictly speaking about the energy needed to run the machines, NOT the toxic byproducts that are left behind. Desalinization projects all over the world have cause ecological disasters in their attempts to manage and deal with the waste products leftover, and this will be no different unless they also plan to process every seawater component down to its component form and use or sequester that…somehow.















  • I guess, but not simply. Probably easier to look it up, but I’ll take a stab at it:

    The CPU is informed how much memory is available to use, and the address spaces across the memory provisioned when it is assigned work, so it “decides” what it’s supposed to work with by using its own logic gates.

    The memory controller has a logic system of its own that decides how read/write work happens when it’s assigned work.

    Between the two there are no gates that measure how much traffic is flowing between them. This is just a bus that passes signals back and forth (caching gets more complex so I’ll skip that).

    So the signals passed back and forth between these two pieces of hardware doesn’t have a place where it can measure exactly what is passed back and forth, it just exists to provide a pathway to allow the signals.

    ECC memory passes parity bits with its payload, sort of like a TCP conversation, so it’s controller knows what is passed to it and if the expected payload is intact. Because this exists on the memory controller, you can read those values and find out what is passing through it to measure what OP is sort of asking about (though it’s so fast it wouldn’t make sense without sanitizing the data into a normalized measure somehow).


  • Non-ECC memory controllers don’t really track the flow of information in and out, the same way your CPU can’t track that as well until it hits a register. CPU and Memory use clock speed regulated by voltage to pass data back and forth with no gates between, so there isn’t a way to directly monitor and get feedback about the flow of information until it hits a destination that does report back or gatekeep for whatever it is (performance registers for example).

    You can view the frequency of your running memory, which should give you an idea of the speed at which things will pass in/out, but that’s about all you’re going to get unless you find a utility that pulls a bunch of information from /proc and consolidates it all, but even then I believe you’d only be seeing an approximation and not live feedback about what’s passing through memory.




















OSZAR »