• 2 Posts
  • 43 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • I have three ideas: First, you could switch the desktop environment to one of the ones that has a GUI settings tool to set passwordless automatic sign in. I think Gnome 3 on Ubuntu, and Mate Desktop on Linux Mint have that feature. There are probably others.

    Second, you could switch your display manager to “nodm”. The display manager is the thing that runs the X server or Wayland, and it starts the greeter (the greeter is the program that shows the login screen). nodm is a special display manager that doesn’t use a greeter or ask for a password. It immediately starts the session using the username and desktop environment specified in its configuration file.

    I use nodm for my HTPC and it works very well. The only downside is that you have to edit its configuration file, /etc/default/nodm , using a text editor. I’m not aware of any GUI configuration tool for it. However, it’s pretty easy to configure.

    Third, you could abandon all display managers, and start the session manually, either from a shell script, or over SSH. This is a little more complex. You will probably want to get comfortable with SSH before trying this (SSH is the command-line analog of remote desktop).





  • What do you expect them to say? That they’re proud of this guy? Even though he’s clearly a madman?

    I know IRL gun nuts, and none of them would identify with this person. Also, none of them subscribe to the fallacy/straw-man of a “good guy with a gun”. The ones who carry concealed would remind you that they are carrying for themselves, not for you. If you find an active shooter in a mall, you can count on them… to run away.

    Skillful gun nuts know that shooting defensively is never worth the legal hassle unless it saves your life (or a family member’s life).

    The shooter in this article is nothing like any of the gun nuts I’ve ever met. This shooter is another Kyle Rittenhouse, someone anxious for a chance to kill a person and get away with it under the excuse of defense.




  • Remember that voltage is measured across a pair of wires, so you can’t power the chime with only a single wire. That’s part of what makes this difficult – these doorbell systems only have the bare minimum of wiring in them. Powering the camera and the chime in series with each other is quite difficult. I think a lot of these things just accept the short circuit, and use a battery to power the camera while the button is being held.

    Here is what I was proposing, and I think what ch00f was also proposing. Replace “5VDC power supply” in this diagram with “a full bridge rectifier and a bunch of caps” in their description, and also note that your camera probably requires a well regulated 5VDC supply.


  • The easy way: take your existing wiring. Put an 18VAC to 5VDC power supply in parallel with the pushbutton. Then, the output of that power supply goes to the 5V USB input of your camera setup.

    The downside is that it will reboot the camera every time someone rings the doorbell, because you are shorting across the camera’s power supply.

    You can put a resistor in series with the button to fix this. You will need to find a resistance that’s low enough to still cause the chime to ring, but high enough not to disrupt the camera’s power supply. Maybe start around 20 ohms. If you can’t find a working resistor value, you can change the transformer to a 24V or 36V transformer, but make sure to keep that resistor high enough not to burn out the chime, and make sure your 5VDC power supply can handle the increase in input voltage.


  • This is false. X is not less secure than Wayland. It does have a different security model, which can become insecure if you misuse it. I don’t think people really care about situations where multiple user accounts access the same display.

    In my opinion, the benefits of xdotool far outweigh any benefits gained by Wayland’s security model. It’s impossible to make xdotool in Wayland, because of its security model.





  • Limonene@lemmy.worldtoMildly Infuriating@lemmy.worldMFA
    link
    fedilink
    English
    arrow-up
    74
    arrow-down
    14
    ·
    3 months ago

    I agree with this sentiment. Steam notably falls into the third category, while otherwise being pretty good.

    But I’m quite disgusted now seeing an image of a Yubikey for the first time. I’ve heard so many good things about them that it’s a major disappointment to see now that they use that awful noncomplaint shape of USB plug.

    There are two very important reasons for the metal shield around USB plugs: 1. For ESD protection, and 2. to hold the receptacle’s tongue in place and prevent it from bending away and losing contact. Every USB device I’ve owned that was a flat plug (like this Yubikey image in this post) has within a month deformed the USB receptacle it’s plugged into to the point that the device no longer works in that port. Compliant USB devices still work in that port’s deformed receptacle, because they have a correct metal shield that bends the tongue back into the correct position.


  • Haha. I sent them an opt-out notice by email, and it bounced!

    They are using Google email servers for discord .com and Google has apparently shadowbanned me. It gives an error message saying “The account [my email address] is disabled.” but I have never created a Google or Gmail account, and my email address is on a domain not associated with Google at all.

    So I’ve completed my obligation to opt-out. Discord will have no record of it, but I have the email server logs to prove I sent it.

    If, in the future, anyone needs to sue Discord and forgot to opt-out, feel free to use this same excuse.


  • I never got Proton working on my main distro (Debian), so I probably fall into this category. I did use Wine, but Wine is a lot harder to set up, and never ran games as well as Proton did.

    Here is my major gaming history, since I started on Linux in 2007. Yes, I really could focus on a single game for years back then.

    • 2007: Starcraft, in Wine
    • 2007: Nethack, native
    • 2011: Morrowind and Oblivion in Wine
    • 2012: Minecraft, native
    • 2014: sgt-puzzles, native
    • 2016: Steam, got hundreds of native Linux games.
    • 2017: Briefly got Steam and Path of Exile working inside a Wine instance.
    • 2022: Steam deck, with the specific purpose of being able to run Proton on it.
    • 2023: New Ubuntu installation, and Proton finally worked on my PC.

    Today, I still prefer native Linux games. I mostly only use Proton when peer pressure for a multiplayer game required it. But I never use Wine any more.




  • A couple months ago, I made a Palworld server box out of a spare motherboard assembly (mobo, processor, ram) from a computer I had recently upgraded.

    I didn’t have any spare drives lying around, so I plugged in 7 USB flash drives and made them into a RAID array. Not a true RAID array, but a BTRFS filesystem with volumes spread onto each flash drive, with the data redundancy set to raid1, and the metadata redundancy set to raid1c3.

    It worked… in the sense that I never lost any data. It certainly didn’t work in the sense of having good uptime.

    The first problem was getting it to boot right. The boot line in GRUB had “root=UUID=…” instead of a specific drive named. That is normal. However, in BTRFS multi-volume filesystems, all the volumes have the same UUID. So the initrd was only waiting for a single drive matching that UUID, then trying to mount it as the root filesystem. This failed, because the kernel had not yet set up the other 6 USB drives, and this BTRFS filesystem needs all 7 volumes present. Maybe 6, if you used the “degraded” mount option.

    The workaround was to wait for this boot process to fail, at which point you get dropped into an initrd shell. Then, you look at all the drives and make sure they’re all there. And then… I don’t exactly remember what happened next. I think it was some black magic that erases your mind in the process. I somehow got it booted from the initrd shell.

    Installing Steam and the Palworld server worked ok, and it even ran for a few hours before crashing overnight.

    The next morning, I tried rebooting it. Unfortunately, the USB drives weren’t all appearing. Turns out the motherboard had some bad USB ports, some sometimes-bad USB ports, and a maybe-bad PCIe bus, because the PCIe USB expansion card I plugged in had weird problem that it had never had before.

    I found the most reliable ports and plugged the drives in there. But you can’t just replug them in the initrd. It doesn’t have USB hotplug support. So each time it tried to boot with not all the drives there, I restarted it again until one time I finally had all the drives.

    I changed the GRUB boot line to “root=/dev/sdg1” . This made it wait for all the drives to load, in any order, and whichever one was last would be mounted as the root filesystem (but the kernel would automatically include all the others too, since they were successfully initialized).

    The bad USB ports kept bringing down the server every day or two. I bought a cheap NVMe drive and added it to the BTRFS filesystem, and then removed all the USB drives except the largest. That fixed the reliability. It’s been like that since.

    Now, to boot the server, all I have to do is change the GRUB boot line to “root=/dev/sdb1” . Since the NVMe drive is much faster than the USB drive, it always initializes first. If the initrd waits for sdb2, then it will always have both drives initialized when it tries to mount the root filesystem.

    I could add that to the grub.cfg, or come up with some other more permanent solution, but I’m not planning on rebooting this server ever again. My friends fell off Palworld, and I gave a shutdown date that’s about a week away. And the electricity is pretty reliable here.