I’m a technical kinda guy, doing technical kinda stuff.

  • 0 Posts
  • 99 Comments
Joined 1 year ago
cake
Cake day: September 27th, 2023

help-circle

  • Mainly the issues are about providing ~600 kilowatts for 8 minutes to charge your typical size EV battery.

    A row of 5 chargers of that size soaks up 3MW if they’re all in use, and that’s not something that can be quickly or easily shoehorned into a suburban electricity grid.

    It’s about 500 houses worth of electricity usage, for comparison. For just 5 fast chargers.

    Not to say it’s impossible, but infrastructure doesn’t come cheap, and so it’ll cost quite a bit to cram that 80 percent charge into your car’s battery.






  • Blu-Ray USB drive and M-Discs is about the best you can get at present. Keep the drive unplugged when not in use, it’ll probably last 10-20 years in storage.

    Seeing as there hasn’t been much advance past Blu-ray, keep an eye out for something useful to replace it in the future, or at least get another drive when you notice them becoming scarce.




  • Dave.@aussie.zonetoLinux@lemmy.mlCompanies that use desktop Linux
    link
    fedilink
    arrow-up
    39
    arrow-down
    1
    ·
    2 months ago

    how the IT team tries to justify being locked into Microsoft, and then telling me I could potentially become a point of vulnerability

    Because they can manage and control all the windows PCs , pushing updates automatically, restricting what users can do locally and on the network, they have monitoring tools and whatever antivirus and antimalware tools they have, and are able to easily manage and deploy/remove software and associated group licensing and so on and so forth.

    Meanwhile you’re a single user of unknown (to them) capabilities that they now have to trust with the rest of their system, basically.

    The first rule of corporate IT is, “control what’s on your network”. Your PC is their concern still, but they have no effective control over it. That’s why they’re being a bit of a pain in the ass about it.





  • The US system is broken. I have a tax file number in Australia, which is the broad equivalent of a US SSN, and you know what someone can do with it if they also have my name and DOB? Fuck-all, except file my taxes for me, because you can’t use it as an identifier anywhere else than the Australian tax office.

    If I want a loan or a credit card or to open a bank account or any number of things , I need enough verifiable documents including photo ID to satisfy the other party that I am really them. Basically it’s a points system where any form of government photo ID gives you about 80 points and any other item of identifiable data gives you 10-20 points and usually you have to clear 100 points to be “identified”.

    So my passport plus my driver’s licence is enough. My driver’s licence plus my non photo ID government Medicare card or my official original copy of my birth certificate is enough. My driver’s licence and two bank or credit cards is enough. About 5 or 6 things like my birth certificate, electricity bills in my name or local government rates notices and bank cards is sometimes enough, although photo ID from somewhere is usually required, or you need a statutory declaration from someone in good standing saying that you are who you say you are.

    This kind of thing, while slightly more inconvenient, requires a number of physical items that can’t be easily stolen en-masse. I carry enough of them in my wallet that I can do anything I need to do, as my driver’s licence provides photo ID. People who don’t drive or have a passport can scrape together enough bits and pieces to usually get by.

    So it’s time for a change. But it doesn’t have to involve technology or a huge shift in the way of doing things. It just requires a points system similar to what I describe. Whether the US can effect that change now with the millions of systems that rely on a SSN for a trivial key in a database in some small retailer somewhere, I don’t know.




    1. Replace CMOS battery.
    2. Get small UPS.
    3. Discover that small UPS’s fail regularly, usually with cooked batteries.
    4. Add maintenance routine for UPS battery.
    5. Begin to wonder if this is really worth it when the rest of the house has no power during an outage.
    6. Get small generator.
    7. Discover that small generators also need maintenance and exercise.
    8. Decide to get a whole house battery backup a-la Tesla Powerwall topped off by solar and a dedicated generator.
    9. Spend 15 years paying this off while wondering if the payback was really worth it, because you can count on one hand the number of extended power outages in that time.
    10. In the end times a roving band of thugs comes around and kills you and strips your house of valuable technology, leaving your homelab setup behind and - sadly - without power. Your dream of unlimited availability has all been for nought.

    Conclusion: just replace the CMOS battery on a yearly basis during planned system downtime.


  • Have a look here at the ICMP source code in the Linux kernel at line 400. That is the ICMP reply code.

    At lines 433/434 you can see the collection of the source and destination MAC addresses from the incoming packet. The source is just lifted directly from the packet, the destination is done with a helper function that presumably looks at which interface it arrived on and returns the MAC address of that interface.

    Lines 441 onwards construct the reply packet and push it to the generic ICMP transmit function (which is a bit higher up in the source code), which then pushes it on to the network stack.

    Hope that gives you an idea of how it works internally! It’s really only a slightly more detailed version of the actual standard, there are a few checks to make sure that we are not exceeding network rate limits in the stack and etc, but it’s a quite simple bit of code.

    Added edit: it’s “simple” at this point because a lot of the work has already been done. The packet has arrived via the network stack, it has been determined to be an ICMP packet, and it was sent here to this function. There are already functions that send packets out via the network stack, so this chunk of code just builds an appropriate packet and hands it on to be sent.



  • Seriously, give me any supported argument why it would be beneficial to send humans to the moon (and Mars) instead of just robots.

    Robots, in particular mining equipment robots that everyone seems to be jazzed up about, they need maintenance. Earth bound mining equipment has minor service intervals of 250 hours of operation, major intervals every thousand hours, machine-stopping breakdowns occur on a bathtub curve but there would be a dozen or so before the first 4000 hours of operation.

    For reference, 4000 hours of operation is less than half a year of 24/7 work.

    Even with the addition of a few hundred million per machine in hardening and robustness, the environment they will work in is much, much worse than earth. Seals will need frequent replacement, the parts that do the digging need replacement, hoses will burst or leak, etc etc.

    On the moon you could (probably) laboriously tele-operate repair robots with the 2.5 second lag you’d have to Earth.

    Mars? Not possible.

    So I look at all these plans, where they’ll send ice mining equipment to mars to run for two years unattended to make fuel and what-not, and with my 30 years of experience in the mining industry on earth, I just say, “that must be some good crack they’re smoking”.

    Someone is going to have to go, just to repair and maintain all the machines.