• 1 Post
  • 42 Comments
Joined 2 年前
cake
Cake day: 2023年6月10日

help-circle

  • Part of the issue is most keyboards in America don’t have keys to add accent marks. macOS has Option keys, iOS has the long-press popups, and Linux has dead keys, but on Windows (the vast majority of the market), you still have to bang open Character Map or memorize numeric codes to get accented letters. Sure, you can get an international keyboard for your desktop, but most people won’t, and if you have a laptop, swapping the keyboard is significantly harder.

    I wanted to correct someone’s last name in our system, changing Munoz to Muñoz. It took me a good minute to get that ñ in there. Not that most of my coworkers know how to pronounce that, mind you.

    I studied Spanish in high school. That has relatively few accent marks and diacritics compared to the Eastern European languages, which was not an option at all in high school and still something I barely know.

    Now, enough ranting. Are there any quick videos or tutorials for learning how to pronounce some of these letters in the various languages?


  • Agreed. It’s not exciting watching a bunch of people work together to build a windmill. Nobody will spend millions of dollars to hire actors and release it on Netflix.

    The only way it could be is if they’re also working together to, I dunno, resist murderous aliens or armed human capitalists at the same time. (“Oh no, the capitalists have come to destroy our peaceful and productive commune!”) But then we’re getting back to some kind of “us versus them.”





  • This is a compile-time option that will tell the compiler to optimize for the CPU in your computer, rather than any CPU.

    By default, the x86_64 kernel will build itself so that it can boot and run on any 64-bit Intel or AMD processor. This means it may have to ignore or check for newer instruction sets like (let’s say, totally at random) AVX512:

    if (CPU supports AVX512)
        do_efficient_avx512_thing (a, b, c)
    else
        a = something()
        b = some_nonavx512_prep_work()
        c = some_other_old_way_of_doing_things()
        do_nonavx512_thing (a, b, c)
    

    So, if you have an AVX512-capable CPU, it still has to check before using that instruction. Plus, your compiled kernel will be slightly larger because it needs to contain both ways of doing the thing.

    Using this option tells the compiler to compile code optimized for your current processor:

    do_efficient_avx512_thing (a, b, c)
    

    This is a gross oversimplication. The compiler will also take things into consideration such as instruction sets, scheduling, core and thread counts, big and small cores, and more.

    But the tl;dr is that optimized code is smaller, faster, and maybe a teensy bit more power efficient.

    The downside? If you try to boot this optimized code on an older CPU (or rarely, a newer CPU), it will eventually say “illegal instruction” and crash.











  • Could you send ePub files over ham radio? Let’s forget about TCP-IP mesh networking like AREDN for now. That’s too easy. Let’s look at radio protocols. D-Star can run at 128 Kbps on the 23 cm band. That’s not too common. Drop down to HF and you’re looking at 9 Kbps via PACTOR-IV.

    In comparison, landline dial-up modems topped out at around 56 Kbps.

    Now, I’ve seen ePub files around 1-2 MB, but that’s with cover art, images, embedded fonts, and all that fun stuff. With enough patience, that can work. But, strip out all that, leaving behind plain text and XML, and you’ve got something much more manageable that can be sent relatively quickly.

    I can’t speak for Spain, but in the U.S., the FCC recently removed most symbol rate restrictions, so we might be able to squeeze out a little more speed.



  • This is literally what dd does and what I would have recommended, if this person hadn’t beaten me to it.

    However, if you’re cloning to another disk or partition that will be plugged in at the same time as your existing installation, you’ll wind up with two partitions with the same identifier — a recipe for eventual disaster. In that case, I would run through setup (with your current disk unplugged) and then rsync over the new root partition.