I mean no harm.

  • 0 Posts
  • 59 Comments
Joined 2 years ago
cake
Cake day: July 4th, 2023

help-circle
  • JATth@lemmy.worldtolinuxmemes@lemmy.worldI use Arch btw
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    9 days ago

    hardmode: I did a fresh install on a HDD that is on verge of being dead. Every-time this thing boots it’s a miracle. Somehow dd blanking the disk, plenty of smartctl offline disk surface scans and finally putting btrfs with data in DUP profile resurrected the HDD. I have run btrfs scrub daily or else the os install may bitrot and well… expire. :D

    Edit: Todays catch, I was too late and now I have fix 3 files:

    Error summary:    read=112
      Corrected:      109
      Uncorrectable:  3
      Unverified:     0
    


  • JATth@lemmy.worldtolinuxmemes@lemmy.worldwindows update
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 month ago

    The \EFI\BOOT\BOOTX64.EFI is the only file the UEFI standard says it is required automatically lookup from an EFI system partition. There can many EFI partitions but the UEFI is only required to find a single file per such a partition.

    efibootmgr -u can show all bios auto created boot entries (don’t touch those, the bios can/will reset them at whim) and the manually created entries that don’t launch a BOOTX64.EFI named file.





  • I’ll just comment about one thing that keeps popping up in the discussions: grid-level storage. There is no such thing yet really that would last a full day cycle, and the 100MW or so units we are building are mostly for frequency stabilization and for buying enough time to turn on a base-load plant when the renewables drop out. I’m not arguing against storage - it is absolutely needed.

    The problem is the scale, which people don’t seem to get. Largest amount of energy we can currently repeatedly store and release is with pumped hydro, and the locations where this is possible are few and far between. Once the batteries reach this level-of-capacity, then we have a possibility to use them as grid-level storage that lasts a few days instead of hours.



  • JATth@lemmy.worldtolinuxmemes@lemmy.worldWe are not the same
    link
    fedilink
    arrow-up
    10
    arrow-down
    8
    ·
    6 months ago

    Arch maintenance: 0. Install it once. (The proper way)

    1. Every 2 weeks minimum pacman -Syu
    2. Every 3 months merge/update configs in /etc.

    I don’t get what is with this so hard? Yes, configs can be undecipherable but 90% time the merge involves just deleting the .pacnew versions.





  • permanently attached USB SSDs are supposed to be mounted

    Just mount them somewhere under / device, so if a disk/mount fails the mounts depended on the path can´t also fail.

    I keep my permanent mounts at /media/ and I have a udev rule, that all auto mounted media goes there, so /mnt stays empty. A funny case is that my projects BTRFS sub-volume also is mounted this way, although it is technically on the same device.


  • For example, the new .config directory in the home directory.

    I hope slowly but surely no program will ever dump its config(s) as ~/.xyz.conf (or even worse in a program specific ~/.thisapp/; The ~/.config/ scheme works as long as the programs don’t repeat the bad way of dumping files as ~/.config/thisconfig.txt. (I’m looking at you kde folks…) A unique dir in .config directory should be mandatory.

    If I ever need to shed some cruft accumulated over the years in ~/.config/ this would make it a lot easier.


  • They could be very well using the earth’s orbit around the sun to get better resolution - two data points from opposite sides of the orbit. What I know is that the largest “virtual” radiotelescope is literally the size of earth. The data points are synced with atomic clocks (or better), and a container of harddrives gets shipped into a datacenter to be ingested. Thats hundreds of streams (one per antenna) of data to be just synced up, before the actual analysis even can begin. (I’m just guessing after this) At this point, you have those hundreds (basically .wav files) lined up at timepoints they were sampled (one sample, one timepoint column). So row by row, so you can begin to sort out signal phase differences between the source rows.

    I.e to put it shortly: an image is not taken, it is inferred and computed. Not that you even could in the first place, it’s a blackhole after all.


  • Jokes on merge… when a rebase editing goes wrong after +15 commits and six hours, and git hits you with a leadpipe: “do it. Do it again, or reassemble your branch from the reflog.” I.e. you commited a change very early, went over bunch of commits resolving/fixing/improving them and at middle way forget if you should commit --amend or rebase --continue to move forward. Choose wrong, and two large change-sets get irreversilbly squashed together (that absolutely shouldn’t), with no way to undo. Cheers. 👍



  • I tried Luks and BTRFS more than 6 times leading to a script error each and every time.

    This was actually my experience also, so I went back to a manual install to just get it done. I think the archinstall script won’t get any configuration of device-mapper/LVM right (including disk encryption with cryptsetup). The disk encrypt setup had even more hoops to go through than just LVM.



  • Why would learning be gatekeeping? I wish I could just teach my secrets… The manuals are only a shallow guide to knowledge. E.g. ls, has condensed for me to ls -laR mostly, and that ls<tab> usually gives tools that list something. ch<tab> gives tools to “change something”, like chmod. mk<tab> to “create something” mkdir etc.

    I may navigate in the terminal, but putting me at front of Blender etc. and I’m back to crawling speed of RTFM, and all I would see is a zoo of buttons.