• 0 Posts
  • 95 Comments
Joined 1 year ago
cake
Cake day: April 13th, 2024

help-circle


  • Using G.657.A2 fiber you could get away with 7.5 mm bend radius, or 15 mm diameter, for the innermost layer of the spool. That’s around 5/8 inch for freedom units.

    But then again if you went that tight you’d need like 56’000 windings for 10 km. That sounds like a fuckton, and like we can’t ignore the outer diameter being larger.

    Approaching it from the other side: The fiber diameter with coating but without any mantle is 0.25 mm. If you want to put 10 km on a 100 mm long spool you could put in 400 layers lengthwise, and each layer would have to be a spiral of 25 m (of course you’d spool it outside in, not layer by layer, but should be mathematically similar enough). Using this spiral calculator and some random changing of the values it looks like an outer diameter of 91 mm (3 & 5/8 inch), and inner of 15 mm and a thinkness of 0.25 mm would work for a 25 m spiral.

    Or if we go for 125 mm drum length, so 500 layers, with 20 m each we get 82 mm (3 & 1/4 inch) outer diameter.

    Or if we go for 150 mm drum length, so 600 layers, with 16.7 m each we get 75 mm (3 inch) outer diameter.

    So yeah I think your estimate was pretty spot on, if the 10 km length is the right assumption.


  • Today’s wires aren’t actually wires, they are optical fibers. It must be G.652 or G.657 from telecom use, since that’s commercially available en masse. I think most likely would be G.657.A2 because that can be bent tighter. Here’s an example data sheet from a random google search. I wrote it in a different comment already, but the core has 9 micrometer, the cladding 125 micrometer and the coating 250 micrometer diameter. For telecom applications you’d add at least a mantle, or more likely use a cable with many fibers in little pastic tubes wrapped around a metal core for stability, 12 x 12 is fairly standard. Here of course it’s just a single fiber without mantle being spooled off.




  • Those news are already not so new any more. We’ve had reports of those two months ago.

    Since fiber optic wire guided missiles exist it’s not that much of a leap to think it should work with drones too, so long as the weight works out.

    Fiber is really really thin. 9 micrometer core diameter and 125 micrometer cladding diameter (incl core) and 250 micrometer coating diameter (incl core, cladding). The 10 km spools we use in our lab for network equipment testing are boxes of only like 20x20x10cm, and those aren’t optimized to be extra small with bend insensitive fiber. I can totally believe the 1.2-1.4 kg for 10 km in the article.

    Edit: leak -> leap



  • I wanted a mainstream option but not Ubuntu, and one that was preferably offered with KDE Plasma pre-packaged.

    So I ended up deciding between Debian and Fedora, and what tipped me to Fedora was thinking: Well SELinux sounds neat, quite close to what I learned about Mandatory Access Control in the lectures, and besides, maybe it will be useful in my work knowing one that is close to RHEL.

    Now I work in a network team that has been using Debian for 30 years, lol. Kind of ironic, but I don’t regret it, now I just know both.

    And fighting SELinux was kind of fun too. I modified my local policies so that systemd can run screen because I wanted to create a Minecraft service to which I could connect as admin, even if it was started by systemd.



    1. Ah that makes sense then. I was confused why you would wipe your ESP over and over when it was shared.

    I don’t know why it comes off as hostile, it wasn’t intended that way. Sorry for not expressing it better!

    If the last sentence came across badly, that was more meant to be incredulous that people accept all these workaround instead. There are other comments in here that go to ridiculous lengths to enforce separation, like using the UEFI boot menu to select a disk manually. To me even having two ESPs seems overly cautious, and against the design philosophy. Sharing one ESP is really not an issue (at least as long as you know you’re doing it, as you unfortunately found out the hard way).


  • First of all: You don’t have to reinstall Windows to get it’s bootmgr EFI and supporting files back into the ESP. Installing those from the CLI in from a booted install media is possible, I did it before. You can even install all of Windows manually if you ever need to, it’s just annoying to do with the windows command line tools.

    Secondly: I’m not familiar with all distro installers, but surely you can just not format the ESP? Worst case scenario you’d have to use manual disk formatting I guess, but it’s not that difficult.

    Thirdly: You said Grub doesn’t show the disk. If you mean the Grub command interface didn’t show the disk, then the issue is deeper, at a UEFI or hardware level. If you mean there are no boot entries for a Windows install to be selected, then it could be that they were not generated because the Windows bootmgr EFI was not found when Grub got installed. Sometimes just booting back into Linux and running os-prober again might be enough, if the Windows bootmgr EFI is still around. On my distro the os-proper is automatically run when I run grub-mkconfig -o /boot/grub/grub.cfg

    I’ve always used a shared ESP for my dual boot systems and I certainly don’t reinstall one OS as the result of a change with the other.








  • Option “q” for sure.

    When you populate all four slot it is harder to hit high speeds at low latencies in the first place, and with not-identical sticks it’s harder also. I don’t think you can hit even the lower of the values, so 3000 MT/s, with that mix installed.

    Even if you could, running only the two fast sticks at 3200 MT/s will help you more for the games. I don’t think you’ll find a situation where a game is not happy with 32 GB of RAM in the system, and could derive any benefit from the additional 16 GB on the older sticks.

    Also you neglected to mention any latencies, but they are important to hit too, not just high clock rate. The stick with the highest latencies will be the bottleneck for your memory controller.

    (For my comment I’m assuming you mean MT/s not MHz, because everyone keeps treating them as the same, even though they are different by a factor of two. If you actually mean your RAM ran at 3000 MHz so 6000 MT/s then I’m impressed you got that with non-identical sticks, and think it will be even more impossible to hit 6000 MT/s let alone 6400 MT/s with the new ones in the mix)