• 2 Posts
  • 127 Comments
Joined 3 years ago
cake
Cake day: October 4th, 2023

help-circle

  • I mean, you can do it from a technical standpoint, but some of them will have policies that conflict with that. IIRC, GitHub’s ToS only lets you use the non-enterprise service for open-source software, so if you’re just using it to store a ton of data as free personal cloud storage or filehosting, I imagine that at any moment, they might kick you and your data off.

    I just…don’t really see the point. I mean, for light use, most people have a reasonably peppy broadband connection today. There are various “free” — will presumably mine data, like who is using what — file-hosting services. For heavier stuff, you can get commercial Web hosting or a VPS or something like that that will let you push more data.

    EDIT: Yeah, Codeberg explicitly prohibits it too in their ToS:

    https://codeberg.org/Codeberg/org/src/branch/main/TermsOfUse.md

    (1) By using Codeberg, you agree to adhere to the following rules when posting content (like repository contents, wiki articles, issue comments, etc.):

    Public repository content shall be made available under a copyright licence which gives all natural and legal persons the following rights in the content:

    • the right to use the content for any purpose, including both commercial and non-commercial purposes;
    • the right to make unlimited copies of the content and redistribute those copies to others, with or without charge;
    • the right to examine the content and determine how it works and/or how it was made;
    • the right to make their own modifications to the content, to use the content with those modifications privately;
    • and the right to redistribute copies of the content which include their own modifications, with or without charge.

    Private repositories are only allowed for things required for FLOSS projects, like storing secrets, team-internal discussions or hiding projects from the public until they’re ready for usage and/or contribution. They are also allowed for really small & personal stuff like your journal, config files, ideas or notes, but explicitly not as a personal cloud or media storage.

    You might fly under their radar, but if they catch you, I assume that they’re gonna boot you off.


  • I mean, I am not, but if you feel strongly enough about making a stand on that particular issue and you’re willing to deal with a smaller userbase than Linux and all that comes with that, like more-limited developer time and hardware support, sure.

    If you don’t specifically want NetBSD, though, and are happy with FreeBSD, I’d probably use FreeBSD instead. Larger userbase than NetBSD.

    EDIT: I would point out, though, that there’s going to be a lot of packaged software in BSD distros where the upstream projects will have LLM-generated code in them, regardless of the specific position that the BSD distro takes, so either way, you’re going to be running LLM-generated code.


  • Yes, though usually it’s harder to make that tradeoff than it is to avoid disk I/O contention or network bandwidth.

    RAM-based caching of disk contents will have some minimal impact that way, though the main goal is reducing disk I/O; using something in RAM will use slightly less CPU time than pulling it off a disk, especially if you are using an encrypted filesystem or encrypted block device. Your system will already be using otherwise-unused RAM to cache content on disks.

    If application software is smart enough to have its own caching based on free memory or based on a number that the user uses, you can go twiddling that. IIRC, Bethesda’s engine (Skyrim, etc) has some setting that lets one keep a given number of cells loaded (though I don’t know whether all loaded cells are active or not, so it might be aimed more at limiting how many areas the computer is dealing with). But that’s at an application level, not a systemwide toggle.

    There isn’t really a great systemwide Linux feature that I’m aware of that gives you major CPU usage reduction by expending memory. The problem is, I think, that in general, if you want to avoid costly recomputation, it’s often preferable from an application standpoint to use a disk cache rather than a memory cache. If the cost is large enough, it’s preferable to just use a disk-based cache, which permits for persistent caching (I don’t wipe my cache every time I terminate, as a process) and usually permits for larger cache and still gets some of the benefits of RAM-based cache by letting the kernel handle sticking frequently-used disk contents into RAM. Plus, SSD storage has far lower latency (and somewhat-higher throughput) than rotational disk storage, so the cost of using a disk cache versus a memory cache is lower than it once was.

    Firefox is one program that I can think of that has both a disk-based cache and a memory-based cache, and looking at my current about:cache output on a new Linux laptop, it looks like these days, the default is to have the memory cache off by default, as I’ve got no entries in the memory cache.




  • Honestly, I didn’t even know that one could do a graphical environment on Termux (as XFCE and GIMP would entail) with it. The Termux I know on Android is an app in F-Droid that provides a terminal-only environment. So I don’t really know what-all is packaged for the environment you’re using. Just saying that traditional Linux distros will have those.

    EDIT: You might run a pkg update in Termux to update the index of currently-available packages, then try installing it.







  • did not pick up

    In what sense?

    Like, if you do something like:

    $ lsusb > not-in.txt
    

    Then plug it in (I’d have the SD card in, but I don’t think that it’d likely matter at the USB level) and do:

    $ lsusb > in.txt
    

    And then do:

    $ diff -u not-in.txt in.txt
    

    No differences show up?

    If the host can talk to the USB drive, then I’d expect it to show up there.

    EDIT: If it shows up there, then I’d think that the machine is talking to the device at a USB level. To see whether the host can see the block device corresponding to the SD card, I’d do the same with lsblk (for this one, the SD card probably has to be in the reader):

    $ lsblk > not-in-blk.txt
    

    Insert the USB reader into the machine.

    $ lsblk > in-blk.txt
    

    And then:

    $ diff -u not-in-blk.txt in-blk.txt
    

    If it can see that, then it can see the block device with the data on it, the card. The filesystem or something like that might be corrupt or something, but should still show up at that level.

    EDIT2: If the above works and you’re wanting KDE Plasma to pop up a window when you plug the thing or something and that’s not happening and that’s what’s you’re concerned about that…I don’t use KDE Plasma, so I’ve no idea what expected behavior is there. Maybe someone who uses it could tell you. I imagine that it has some kind of filesystem browser and it’s probably visible somewhere there, but…shrugs

    In a plain-Jane Linux sense, if you have a block device, you’ll probably have one block device, and maybe it’ll be partitioned and have smaller block devices for each partition. Maybe /dev/sdb for the main device or something and /dev/sdb1 for the partition. If you can see the block device for the partition (like, you can see it appear and disappear when running lsblk when you plug in and unplug the device), you can mount the block device in the traditional Linux way (with the correct block device where I’m using /dev/sdb1 below):

    $ sudo mkdir /mnt/sdcard
    $ sudo mount /dev/sdb1 /mnt/sdcard
    

    And then before you unplug it:

    $ sudo umount /mnt/sdcard
    

    That’ll be independent of any GUI filebrowser or whatever.


  • uranium…will be available forever

    I’m not trying to argue the broader point, but as to uranium…there’s a lot of uranium out there.

    First of all, you only go hunting for uranium when you need more. There’s probably quite a bit more than is in known reserves. But let’s even set that aside.

    There is a lot of uranium dissolved in seawater. We don’t currently extract it from seawater, because it’s cheaper to mine it. But we could. And the estimates I’ve seen are that if we did so, we could probably get the cost to about twice that of mining it. That’s an increase, but it’s not a big deal, because the fuel cost isn’t very significant when it comes to nuclear power.

    And there are tens of thousand years of uranium, at current electricity use levels, in seawater. As you extract it, the cost of extraction in the (now more dilute) seawater is going to rise, but I can’t imagine that it’d be any higher than a linear increase at most. So once we’ve extracted half of it, our costs maybe at most double. That’s a long ways down the road.

    With nuclear power, the constraint isn’t really availability of uranium. It’s the cost of constructing the plant (which, because nuclear plants last a long time, depends a lot on the finance cost, what interest rates a lender would currently demand to lend to someone at the moment).