• 1 Post
  • 5 Comments
Joined 1 year ago
cake
Cake day: February 18th, 2024

help-circle
  • A lot of the issues you mentioned get solved in season 2. I think there was a network shift and the camera work got better. Later on Amazon pumped a lot of money into the show as well. It’s really worth the watch and I’d love to hear back from you if you do.

    If you’re a gamer there’s a Telltale game that follows this account’s namesake. Camina Drummer.

    The writers did a fantastic job writing all the dialogue in the books. I would argue it’s on par or even better than the show. Which is hard, considering the writers for the books produced and even wrote the screenplays for the show.

    As someone who shares a line of work with Bobby Draper and many other characters, the military jargon and quips are also spot on. Never have I heard such accurate lingo and expression in sci-fi.



  • how are you booting windows from systemd?

    I’m not. I ran some Systemd-analyze, blame etc once Fedora started up and saw that most of my startup lag was caused by a specific drive on boot.

    systemd is not part of the bootloader.

    Yes, and so I used the systemd tools to figure out what was causing my issues on boot.

    As I explained in a reply in this thread it seems my issue is mostly resolved for now. The bootloader was stalling on initializing a pair of drives I have in RAID for system backups on the M$ side.

    This is turn, when running -analyze or other tools showed the drive that contained my Win10 machine stalling out and waiting 45+ seconds to initialise. Because /it/ was actually waiting for the RAID drives to sort it the hell out. So, it looked like there was a conflict between both boot disks when in reality the stall was a symptom of Linux not playing nice with RAID.

    I wrongly assumed it was a boot disk conflict similar to some Windows dual boots where the two disks may be fighting with each other for boot priority and causing a fight until one timed out.



  • Nope!

    Root, Boot, /EFI, /home

    After writing this post I took the nuclear option and disconnected all drives in the PC save for the one hosting Fedora. Then I incrementally connected them all until failure.

    It wasn’t the Win10 drive but the RAID pair I have as a system backup causing the problem. I guess Fedora was trying to mount those disks causing the hold up. Then that made it look like it was the Win10 disk causing the holdup because it was waiting to initialise.

    With the RAID drives disconnected everyone is speaking the same language now.