• 2 Posts
  • 19 Comments
Joined 9 months ago
cake
Cake day: December 20th, 2023

help-circle
  • The current "space" we go into, tends to have a tinny amount of atmosphere. (1.322×10-11 Pa according to some random top result on Google)
    So if you want to keep inside conditions at around 1 atm for a human to stay, that's all the difference you need to keep, and a duct tape might work.

    But the void I refer to, is very different.
    Think:

    • Vaporising metals
    • Theoretical quantum bubble formation

    Normal spacecrafts made for "space", might even have their outer surface constantly being diffused in the void.


    Disclaimer: I'm not a space nerd. The above is just speculation



  • ulterno@lemmy.kde.socialtoProgrammer Humor@lemmy.mlCheckmate
    ·
    edit-2
    4 months ago

    1950s

    A: The transistor I made using your blueprint doesn't switch properly at 12V.
    Maker of Blueprint: The one I made, works at 12V.
    B: I'mma make standard transistors.

    why?

    Blueprint was made by a person in the tropics.
    A was in Europe













  • I'm not sure how funny this will be, but here's how I broke my system twice in a single case. Step by step:

    1. Migrated from Manjaro KDE to EndeavourOS KDE. Kept the previous home directory.
    2. After a few updates, there was a problem with Plasma. Applications were not starting from the panels or the .desktop files (they worked from the terminal. The terminal emulator was in startup and worked that way)
    3. After a few google searches, found out that downgrading glibc would do something, so downgraded... Worked for a while
    4. While using pacman -Syu, I always checked for warnings (foolishly thinking that the downgraded and ignored glibc would cause a pacman warning if it broke dependencies) and there were none. So, the updated OS stopped working due to unmatched glibc. BREAK 1
    5. To fix it, I opened one of my multiple boots (another EndeavourOS) and made a script using pacman -Ql and cp to copy new glibc related files into the broken system (because I was too lazy to learn how to do it the correct way with pacman and chroot didn't work because glibc is needed by bash).
    6. Turned out the script I made was wrong and I hadn't checked the intermediate output from pacman -Ql, which was telling cp to copy the whole /etc /usr and other directories. (just if I hadn't given the -r to cp) BREAK 2

    In the end, I just made a new installation, this time with a new home and hand-picked whatever settings I wanted from the previous home, Viva la multi-HDD







  • "I have no idea what I’m doing here" <- Happens in the beginning. How about you start by trying to know what exactly you are doing? Let me give you a fasttrack...

    1. The first command you get in the instructions is curl. It is generally used to download stuff from a networked server.

      1.1. To understand the -fsSLo in the command, I strongly advise you to check out the manual of curl using man curl in a terminal.

    2. The second command in the instructions is echo "something" | sudo tee some/file

      2.1 Here you see 3 commands echo , sudo and tee. 2.1.1 Again, you can use man command-name to check the manual pages for these commands 2.2 There is a | symbol over here. It is called the "pipe symbol", which is what you can use to search for it. It is usually difficult to search for the symbol itself and I haven't found a man page for it, but open man bash and look for "Pipelines" and you'll know what it is about. Use Link, Link and Link to help yourself understand this.

    3. The commands in "Install the package" use the apt program. This is a Package Manager. Its job is to read package information that package developers have made and try to not let the system become unusable.

      • e.g. If you have a program called Xorg from 5 years ago, and a program called mesa from 5 years ago and Xorg depends upon mesa to work. Here, if you replace your mesa with a new, recent mesa yourself, there is a good chance Xorg will not work. The Package Manager prevents that from happening.
    4. The gist of what the instructions are making you do is, telling the Package Manager that there is another place from where you want it to look for packages.

    To understand man pages better, check out this link.

    Don't think too badly of people dissing you in the comments. They are tired and fed up of help vampires. Hopefully, you can try not to become one.

    • Try and build your own process of understanding the commands you see on the internet before entering them into the terminal.
    • The comments telling you to just follow the instructions, are coming from the perspective that you don't have the patience and determination to understand them yourself, which, a lot of people don't. I will leave it upto you to determine which one you decide to be. It is, however, a bad idea to follow instructions on any website, just because it "seems legit". You can't really say you "trust" the site until you have the ability to find out for yourself whether you want to trust it.

    Check this out