Skip Navigation

User banner
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)T
Posts
0
Comments
26
Joined
2 yr. ago

  • It's just GRUB for boot on this PC, and that's how I'm selecting Windows or Linux - in the GRUB menu. This might break if I did a Windows version upgrade, but so far feature updates are not a problem.

    I don't think the placement of the partitions mattered much from a technical standpoint. I just liked the idea of a shared data partition at the end.

    But yeah, if you're thinking about just jumping from the current setup to the 1TB SSD it would be pretty easy to use dd to clone old to new by doing a live boot from USB and having the new drive in an external enclosure (the command would be something like dd if=/dev/sda of=/dev/sdb bs=64K status=progress - but double-check which drive id is used for each by comparing the names and sizes with lsblk first). That will copy the current disk contents to the first 256 GB of the new drive and leave the rest as free space. Swap in the new drive and test to be sure it boots to Windows. Then boot using Linux install media of your choice and install to the free space. If you're not sure about the distro yet, you might want to have a separate /home to make it easier to try other flavors without wiping out your user files.

    If anything goes south you'll have the original drive to swap in and get to Windows.

    Running MS Office in Linux will be a headache unless you have a very old full install version (not the current click-to-run tech). I would recommend giving Libre Office apps a try to replace Microsoft Office. I've found both Writer and Calc to have great compatibility with Microsoft features, and their UI is very intuitive. I only saw Excel workbooks have problems in Calc where very proprietary features were in use, like online stock quotes through the Microsoft back-end, and things like sparklines. Pretty complex formulas on a very large workbook were no problem. If either of you are using MS Office apps for work then definitely test compatibility before you make the jump. You can test that on Windows since Libre Office works on both Windows and Linux.

  • Agreed on other recommendations to test with a live environment via USB drive first.

    If you decide after that to proceed with a dual boot, I wouldn't worry as much about Windows breaking it these days. I have a Windows 11 dual boot on a Dell laptop. It has had Debian, Fedora and now openSUSE Tumbleweed as my main OS for some time. I have gone through around 3 years of Windows updates and there haven't been any problems with that.

    In my case I reinstalled Windows 11 first, reducing the size of the Windows system partition. I created a shared NTFS partition at the end of the drive and then installed Linux with / and /home partitions in the middle of the disk.

    You could check Disk Management in Windows to see how much you can shrink your system partition. If it gives you enough space that's worth a try as a first step.

  • To be fair it wasn't a random banana.

    It was this specific banana.

  • Just throwing out more ideas:

    Is there a CPU spike on the VPS?

    Anything weird about Wireguard on either end? Using kernel mode WG everywhere and not a user mode version, right?

    As a test I would be inclined to try a very small mtu to see if it makes a difference. 1280 is a failsafe that I use when on unknown networks and trying to wg out.

    Maybe try with a smaller packet size, like 1KB which I think is -l 1K

  • Are you specifying bandwidth (-b) on the iperf UDP test? It defaults to 1M if I recall correctly, which would explain the result.

    If not, try -b 10M or -b 0 for unlimited (the behavior used for TCP).

  • I'm doing this on a couple of machines. Only running NFS, Plex (looking at a Jellyfin migration soon), Home Assistant, LibreNMS and some really small other stuff. Not using VMs or LXC due to low-end hardware (pi and older tiny pc). Not using containers due to lack of experience with it and a little discomfort with the central daemon model of Docker, running containers built by people I don't know.

    The migration path I'm working on for myself is changing to Podman quadlets for rootless, more isolation between containers, and the benefits of management and updates via Systemd. So far my testing for that migration has been slow due to other projects. I'll probably get it rolling on Debian 13 soon.

  • Erika's Originals are EU made and great quality.

    Maybe not as colorful as you want.

  • Oh my!

  • Yeah, fair enough. Definitely not as strong flavored.

  • Yu choy is such an underappreciated vegetable in the US. It's usually very inexpensive, available at asian groceries all over, and stands in well for other greens. We use it as a 1/2 price (or cheaper) alternative to broccoli rabe in Italian dishes.

  • Yeah, this. I'm probably more aware of and familiar with world languages than the average American, but I have flipflopped between die and day pronunciations of Hyundai. I tried to figure out why that might be and I think it's probably related to the romanization differences among several east Asian languages. This seems most problematic with older romanization methods. Newer ones feel more intuitive.

    For example I'm meant to pronounce the 'ai' in Taipei, Saipan and zaibatsu as rhyming with "die", but the 'ai' in Hyundai and waifu as "rhyming with "day". So it's memorization and context. Which feels very appropriate as an English speaker when all of our shit is irregularities and exceptions!

  • Any car before electronic ignition became more popular. My first two cars (purchased already old) had them and I'm old but not ancient. If you had a mass production car built in the 1970s or earlier you probably had this in the distributor. The points eroded due to the high voltages and would get a pitted surface, causing problems with ignition timing and that could be bad. It's a wear item, so file them to dress them up a bit until you can't any more. Then replace them. But when you file or replace you've got to adjust the points and check the timing (edit:) dwell again.

    Both electronic ignition and later the ECU (plus developments in materials science) improved the lifespan of spark plugs too. This is why there were so many tune-up shops in the old days. You needed to regularly check the plugs, points, timing, oil and filters. Plus all the other things that didn't last or remain in adjustment as long back then as they do now.

  • Maybe the linked article changed since it was posted? That's the story I read yesterday, but the article I see posted says:

    It was handed over on Wednesday to the Argentinian judiciary by the daughter of the late Nazi financier Friedrich Kadgien, Patricia Kadgien, who has been under house arrest with her husband since Tuesday.

  • Just tried this on a recent Trixie amd64 install. locate isn't installed by default, but there is a locate/stable 4.10.0-3 package and it installs just fine for me.

     
        
    sudo apt update
    sudo apt install locate
    
      
  • What number am I thinking of?

  • I'm using Mikrotik and Ruckus. Would recommend both. I like that they are both at the level of reliability that I don't think about them at all for months at a time. I update quarterly or less and they require no other attention from me. They also work well with my centralized data collection and alerting via LibreNMS.

    OPNSense would be high on my list of alternatives when I reevaluate next time. And all Mikrotik would be a good option for me as well. Their Wi-Fi gear is not as strong as Ruckus or Ubiquiti, but they are super solid.

    The Unifi ecosystem is a bit too centralized for me. I don't want to create an account in order to use the hardware.

  • Matewan (1987) is a good movie covering aspects of this story. Great cast and an engaging story. The cinematography won an Oscar.

  • I've used a pretty cheap on (Duxtop or something like that) with a 6-8" heating coil. It worked fine on a well-conducting pan - 12" triple layer stainless-aluminum-stainless (like All-Clad, but a cheap version for restaurant use). It also did great with a 10" carbon steel pan. But I wasn't doing anything that required maximum heat across the width of the pan. I think that's a shortcoming for sure.

    There are also reports of poor performance with larger cast iron pans, which makes sense - they're not great heat conductors. So I think in part at least it depends on your cookware and what you're cooking. Boil/simmer/fry in a larger highly conductive pan will likely be fine. Sear in a larger less-conductive pan maybe not so much.