She/They

  • 1 Post
  • 83 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle

  • That was the best day ever when it went down a few years ago while I was doing an install of an Amazon site. They have some “test” software that we have to run to validate the system and it was completely down. Still got some things done that day, but it was utterly hilarious to watch all of the Amazon personnel run around in a panic for a few hours. Fucking Prime trucks stuck on the side of the road with no instructions on what to do next. Utterly precious.


  • I think this view is a little short sighted. I am glad that you don’t seem picky about your peripherals, but they are very important to others. As someone with a disability, if my mouse didn’t work on Linux, I wouldn’t even bother trying. I have spent a lot of money on peripherals and them working in Mac and Windows, but not Linux would be utterly rage inducing. It is irritating enough that I can’t adjust the dpi in Linux, but it is at least usable. I am still salty that every single pair of headphones I own use proprietary codecs that are not supported.

    I absolutely do not blame anyone for not using Linux if their peripherals do not work. I get that it is the “fault” of proprietary drivers. Unfortunately, some devices are not popular enough or too difficult for someone in the Linux community to want to work on it. I don’t blame the community either. However, telling someone they can’t use their mouse or keyboard the way it was intended isn’t going to convince anyone to use Linux.

    My point is, hardware costs money, is a physical device that you touch for hours at a time, and is configured to make your life easier. Tactile and ergonomic comfort is important. Macros, lights, and dpi settings are important to some people. For me, it is just dpi and smooth scrolling. Not everyone is happy with a cheap mouse and keyboard or wants to throw perfectly functional electronics in the bin.


  • UL certification can mean different things, depending on the product and type of mark. It also isn’t that expensive to get UL listed as it isn’t like every single item you produce is tested. Each product you design is tested, but not each item you produce.

    There are 3/4 types. UL listed, UL recognized, and UL classified. Certified is newer and more stringent.

    • Recognized is mostly for machinery and components within machinery. It isn’t terribly difficult to get, but annoying. I have dealt with this type as we design and build electrical panels. Usually you hand the design to a panel builder and they will get it certified before delivery.
    • Listed is for products and appliances, and is fully tested for safety. This applies to most consumer electronics.
    • Certified Enhanced is also for products, and you can read up on it here: https://www.ul.com/news/qa-uls-enhanced-certification-mark
    • Classified is for products and is half ass tested. All it means is that some requirements for UL were tested and passed, but not all.

    If a product is Classified by UL, this can mean its testing meets the particular requirements for a single test with a published result, but has nothing to do with all the other tests that may form part of a Standard (i.e., UL 181).

    As for pricing for UL listed, it can be just a few grand for a single product. Not much when you are selling thousands. I am sure Classified is even cheaper. I wonder how many of these cheap ass lamps say Classified.





  • We had a student run server for piracy at my University to get copied textbooks from, but even then we had to sometimes look elsewhere. I often couldn’t afford books and not all professors allowed the cheaper used previous editions.

    Science textbooks were the worst with their stupid fucking online code bullshit so we could do homework. They even made it where you could buy just the code, which was something like $70. Still better than 300+, but JFC. Having to spend over $1000 for books that you are only going to use for 10 weeks was nuts.

    The last saving grace we had is all textbooks were required to have at least one copy in the library that could not be checked out/removed. You could photocopy the homework pages that way. If your classmates were nice, they would let you borrow theirs to copy any pages too. You could also buy your textbook, copy what you needed, and return it within the return window.







  • Sorry, didn’t make it home until today and not sure if you get notifications on edits. You will need a monitor and keyboard hooked up to your server as you will not have ssh access until the network config is “fixed”. I would do the below with the GPU removed, so you know 100% that your networking config is correct before mucking about further.

    Step 1 - Create 99-default.link file

    Add a /etc/systemd/network/99-default.link with the below contents.

    # SPDX-License-Identifier: MIT-0
     #
     # This config file is installed as part of systemd.
     # It may be freely copied and edited (following the MIT No Attribution license).
     #
     # To make local modifications, one of the following methods may be used:
     # 1. add a drop-in file that extends this file by creating the
     #    /etc/systemd/network/99-default.link.d/ directory and creating a
     #    new .conf file there.
     # 2. copy this file into /etc/systemd/network or one of the other paths checked
     #    by systemd-udevd and edit it there.
     # This file should not be edited in place, because it'll be overwritten on upgrades.
    
     [Match]
     OriginalName=*
    
     [Link]
     NamePolicy=mac
     MACAddressPolicy=persistent
    

    Step 2 - Reboot and find new name of NIC that will be based on MAC

    I forget if you have to reboot, but I am going to assume so. At this point, you can get the new name of your nic card and fix your network config.

    1. ip link should list all of your nic devices, both real and virtual. Here is how mine looks like for reference, with the MAC obfuscated:
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: enxAABBCCDDEEFF: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
        link/ether AA:BB:CC:DD:EE:FF brd ff:ff:ff:ff:ff:ff
    3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
        link/ether AA:BB:CC:DD:EE:FF brd ff:ff:ff:ff:ff:ff
    

    Step 3 - Fix your network config and restart network manager

    You will need to edit your /etc/network/interfaces file so the correct card is used.

    1. Make a copy of /etc/network/interfaces, just in case you mess something up.
    2. sudo vim /etc/network/interfaces (or whatever text editor makes you happy) It will need to look something like below. I have to have DHCP turned on for mine, so your config likely uses static. Really all you need to do is change wherever it says enp yada yada to the enxAABBCCDDEEFF you identified above.
     source /etc/network/interfaces.d/*
    
     auto lo
     iface lo inet loopback
    
     iface enxAABBCCDDEEFF inet manual
    
     auto vmbr0
     iface vmbr0 inet dhcp
     #iface vmbr0 inet static
     #address 192.168.5.100/20
     #gateway 192.168.0.1
         bridge-ports enxAABBCCDDEEFF
         bridge-stp off
         bridge-fd 0
    
    1. Restart your networking service. You shouldn’t need to reboot. sudo systemctl restart networking.service

    Step 4 - Profit?

    Hopefully at this point you have nework access again. Check the below, do some ping tests, and if it doesn’t work, double check that you edited the interfaces file correctly.

    1. sudo systemctl status networking.service will show you if anything went wrong and hopefully show that everything is working correctly
    2. ip -br addr show should show that the interface is up now.
    lo               UNKNOWN        127.0.0.1/8 ::1/128
    enxAABBCCDDEEFF  UP
    vmbr0            UP             192.168.5.100/20 
    

    At this point, if all is well, I would reboot anyways, just to make sure. If you add any GPUs, sata drives, other PCI device, disable/enable wifi/bt in the BIOS, or anything else that changes the PCI numbering, you don’t have to worry about your NIC changing.




  • See, when I was in school, they didn’t teach fail fast and if anything they told you not to. Nowadays, we have moved past that nonsense. I gave it a shot about a year ago, and it has made me a better programmer. I am not going to sit there and count braces, but things are a lot easier when you get the error cases over with and out of the way.

    There are always going to be exceptions, but I have personally found a lot of value in using ‘fail fast’, and making more smaller methods that say what they do. I am not always great at that second part, but it is a process. As someone with severe ADHD, it has made it a lot easier to work through problems. Sure, you can end up with more lines of code, but who cares. Compiler should be optimizing most of that shit out anyway.