I mean no harm.

  • 0 Posts
  • 52 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle
  • I have “tight jaws” problems so a trip to dentist generally is a pain for me, even without surgery. There are hygienists and surgeon dentistry. You only want to have regular business with the first. So brush brush mouth wash.

    I learned the hard way that after root canal there is a chance you loose your tooth if you don’t get it cared over fully promptly. (if a temp cap has any problems it’s an emergency.) I think numbing the tooth is the worst part because for a root canal they have to (and you want this) kind of over do it. After this, no problem. Always tell beforehand if you have fears of the operation, so they can adjust how they work.


  • JATth@lemmy.worldtoAsklemmy@lemmy.mlFavorite horror movie?
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    28 days ago

    100% Nope: A episode from supernatural, where ghouls half way succeed to eat Sam. (I consider it as the most gruesome horror I have ever seen, and I don’t think I have the stomach to see it ever again. The blood draining is a … no.)

    Yellow brick road on otherhand hits the weird places spot of SCP, which I can’t get enough. (not horror really, but still)






  • 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.




  • 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.


  • The time you took to answer the archinstall questions and what would take to do them manually is (nearly) the same. The manual way is that you are forced learn the system (which does take time), and it’s thus more exact of what you want. Once you successfully boot a manual install on a bare hardware, you’ll get all the swag. ;)

    (I was lazy last time I had to do a full install, and I prepared the system almost entirely in a VM, for which I used the physical disk I would finally boot it from. The final step was to chroot’d into the nearly complete system and make it boot outside of the VM…)


  • JATth@lemmy.worldtolinuxmemes@lemmy.worldfree license key included
    link
    fedilink
    arrow-up
    7
    arrow-down
    5
    ·
    edit-2
    3 months ago

    I actually don’t get the fuzz/meme about Arch Linux. Yes, the installer drops you into a shell where you need to fix the keyboard layout for starters and the next thing is preparing enough disk resources for the OS which is somehow ungodly hard. My point is that if you can’t then you are not qualified to maintain the installation, or actually RTFM and start to fr think what you do.




  • I have learnt coffee oxidizes quite fast giving that horrible burnt taste, which even milk won’t hide. The longer it has been in a open-to-air-pot, the worse the taste gets. Storing in an air-tight container (thermos) it stays “ok” for days. So actually, I think all such servings from the coffee shops are thus inherently worse than brewing your own coffee.

    (There are no starbucks in my country, but I think McDonald’s coffee really is somehow heated past 100*C and it’s the first sip away to burn your mouth, so you wouldn’t taste it anyway.)