A typical bike-riding leftist urbanite who also happens to be a hockey-crazy Western Canadian.

  • 0 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle



  • A really common issue with sway is that it doesn’t run as a login shell, so none of your .profile or other environment settings get sourced when you login. I think that might be the problem here.

    Try closing your sway session, then login to a tty and run sway. If the qt themes work properly then it’s definitely an environment issue.


  • Fellow Arch user here (btw). It’s exactly the same as building AUR packages. Clone a git repo containing a PKGBUILD, use makepkg to build it, and pacman to install it. The nice thing is you can host a repo of your built packages and install them on other systems really easily. The big downside is that dependency management is not automated, so it will take some time and annoyance to map out what packages you need to build and in what order, if you want a fully source-bootstrapped system.












  • The only difference between those two versions of linux is that the new one was built with a newer version of gcc. That doesn’t really narrow the problem down, though. As far as I’m aware, emergency mode is caused by either a kernel panic or a failure to mount a needed filesystem. I’m leaning towards a corrupted kernel, since it doesn’t sound like you changed your fstab or had any problem mounting /. I would run fsck -f on your boot partition, then try to re-download and reinstall the new package.

    If that doesn’t work, then you can add IgnorePkg = linux linux-headers to pacman.conf so you can update without installing the broken package, until you resolve the underlying issue. Or your can install a different kernel altogether.

    As for preventing problems in the future, there’s only so much you can do. Check archlinux.org before updating to see if anything requires manual intervention, and pay close attention while running pacman in case something goes wrong. You already seem to know the most important part, which is to keep a set of packages that are certain to work, so you can easily downgrade if a crash does happen.


  • I decided to switch when windows xp went end-of-life, because my pc was a mid-2000’s era relic that would surely catch fire if it was forced to handle the windows 7/10 bloat. Naturally, I installed Mint on bare metal without doing any research beforehand. Not the best idea, but sometimes it’s fun to jump headfirst into a completely foreign landscape. That said, Cinnamon (the desktop environment of Mint) shares much of its design language with windows, so it’s not really that foreign, as far as the graphical interface is concerned.

    What surprised me was just how different the underlying system was, how much more transparent and accessible it was, and how incredibly efficient and versatile the command line could be. Then there’s the broader OSS community, which I think is a fantastic thing to participate in even if you don’t use Linux, but using Linux is certainly a gateway.

    I’m not saying Linux is perfect, and it’s probably not for everyone, but it is nice to not be held captive by some monopolistic corporation, who continuously engages in ethically questionable anti-consumer behaviour, in the name of increasingly monetizing their user base. Linux gives power back to the end users, and that’s what makes it worthwhile and important.



  • It really just comes down to the differences in goals and philosophies between each distribution. Some distros have large curated repositories containing most of everything a normal user would want to use. That’s what people expect from those distros, and people use them because they want that experience. Likewise, people don’t use arch just because it has the AUR. They want a more DIY experience, and arch provides that, with the AUR being an essential part of how it works.

    You’re not going to get arch users to switch to ubuntu or whatever by duct-taping an AUR clone onto it. Furthermore, I believe trying to make one distro “to rule them all” that attempts to appeal to every niche would be not only a train wreck technically, but an abomination, antithetical to the principles of the OSS community as well.


  • I would highly recommend python. It’s fairly simple syntactically, which makes it less overwhelming someone who’s just looking at code for the first time. It doesn’t force you to learn about functions and classes right away, like other languages would, so you can focus on the real basics until you’re ready to tackle the more abstract stuff.

    The fact that it’s on the ‘simpler’ side doesn’t make it any less powerful, either. It’s one of the top languages used for neural net AI and data science. It’s also really great for throwing together a spur of the moment script when inspiration strikes, to automate a really boring task, for example. And yes, you can also make games with it.

    Plus, the fundamental concepts that you use to solve problems with python are mostly the same in every language, so once you get proficient in one language, you’ll be able to pick up other languages much easier.

    Whichever language you do end up choosing, good luck on your journey!