- Joined
- Jul 24, 2021
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
If the gaming ecosystem wasn't like it is, Maybe my opinion would be different.So would you consider puzzle games, like a Zachtronics game for example, to be a vice? Theres a lot of value in keeping your brain sharp, especially as you get older.
how about simulators, like DCS, or Assetto Corsa? are those vices? even if they're "realistic", they're still games, and they're a fun way to learn skills like flying or racing, albeit niche.
If a game can get you working together and chatting with friends, like playing an ArmA 3 Operation, is there no value in that?
If a game can get you legitimately thinking about the world around you, the same way a well written book or movie might, is it still a vice?
I think theres an argument to be made that theres a lot of mindless slop out there made for people interested in low-quality pleasures, thats part of why I frankly dont game much anymore, but I think its a bit reactionary to say all of this is like that. or perhaps I misunderstand what you're getting at here.
Im pretty sure GOG can be run off lutris as well, but I've mostly stuck to steam so far.
And you can learn actual skills and do "actual things" in video games. Not all of them. I agree that Gaming, as it was originally formulated, is a fundamental vice. But not all video games are Gaming. Gaming is gambling, and you should absolutely kick the shit out of anyone who plays or even likes any incarnation of video game gambling, gachaslop and lootboxes included. They're addicts and they are consumed by vice. But outside that, condemning all of video games as immoral and a waste of time is the exact same as condemning all movies, books, radio and entertainment as a whole while taking slow sips out of a fresh bottle of Soylent™.What I see. With gaming, and just like anything. this isn't everyone that plays a video game.
C:\Users\[USER]\AppData\LocalLow\[THE GAME]
/home/[USER]/.local/share/Steam/steamapps/compatdata/[GAME ID]/pfx/drive_c/users/steamuser/AppData/LocalLow/[THE GAME]
Therapy is for pussies who want to be told they never did anything wrong. k8s will never pander to your delusions. It may confuse you, abuse you, or render you infertile and unfuckable, but it will never lie to you.
Sounds weird. I have no idea about Kitty. Do you have it starting up with a session already starting a sudo'd shell or something maybe?The only thing that turned into a wrinkle was my Kitty terminal launching slow as shit, I did a strace on it to see what's up and found that python tries to bytecode cache into the system folder which it does not have permissions to do. This led to it asking like hundreds of times before giving up after 3 seconds. I ended up just redirecting it to a cache in the home directory instead of messing about with permissions but maybe giving permissions is a better solution? I am new so I am not sure.
Your first login user will be setup as a member of the group if you don't set a root password. Otherwise it sticks to the way it has always been.That was the only legit issue, but there was also having to add yourself to sudoers which Debian insists on not doing during install. I say legit, because I genuinely don't know if not doing this is a security measure or if the minimal installer is just broken.
I did check but no, I also checked if the shell (or really anything) was running as root and for privileges, but it doesn't appear so unless I am mistaken. Pointing it to cache in home instead seems to have fixed the problem, though.Sounds weird. I have no idea about Kitty. Do you have it starting up with a session already starting a sudo'd shell or something maybe?
That's most likely it.Your first login user will be setup as a member of the group if you don't set a root password. Otherwise it sticks to the way it has always been.
you can do the same thing on linux.Today's "It's easier with Linux".
My main desktop as I mentioned the other day I added some stuff to, the other thing I added was a new, larger NVMe, but due to the boot fun I decided not to move everything over just yet. I decided today was the day.
The problem is I had LVM for / and /home and wanted to be rid of them, so usually I'd dd the partitions to the new drive. This time it was a bit more fun.
1. Make new partitions on new drive.
2. mkfs.fat(EFI) mkfs.ext4 and mkswap as appropriate.
3. Mount new root and rsync / and /home to it.
4. Reboot into live USB
5. mount new / and /boot/efi into temp dir.
6. Do one last rsync, including the EFI directory this time
7. Edit new /etc/fstab with proper UUIDs
8. Chroot into new root and run update-initramfs
9. Run update-grub. Which fails.
10. Bind mount /dev /sys and /proc into chroot.
11. Chroot back in and run update-grub
12. Check /boot/efi/EFI/debian/grub.cfg and notice it's still looking for LVM, fix the UUIDs there.
13. Check /boot/grub/grub.cfg and see it is correct.
14. Reboot
15. System doesn't boot
16. Boot back into live USB. Mount all the filesystems including /dev /sys and /proc
17. Run update-initramfs again and see the normal errors.
18. Reboot
19. Profit
20. Wipe old EFI partition to make sure the system doesn't try and boot the old drive.
21. Once all is confirmed, wipe now second drive and mount it somewhere for scratch space.
Windows, of course, would have been two steps:
1. Reinstall Windows on new drive.
2. Copy over any important files.
You can also image a Windows install to a different computer with a new drive, I have done it before.Windows, of course, would have been two steps:
1. Reinstall Windows on new drive.
2. Copy over any important files.
Couldn’t you have just made a backup of /home/, partitioned the drive with a copy of gparted on the Live USB and done a full reinstall with the GUI installer like a normal person?Today's "It's easier with Linux".
My main desktop as I mentioned the other day I added some stuff to, the other thing I added was a new, larger NVMe, but due to the boot fun I decided not to move everything over just yet. I decided today was the day.
The problem is I had LVM for / and /home and wanted to be rid of them, so usually I'd dd the partitions to the new drive. This time it was a bit more fun.
1. Make new partitions on new drive.
2. mkfs.fat(EFI) mkfs.ext4 and mkswap as appropriate.
3. Mount new root and rsync / and /home to it.
4. Reboot into live USB
5. mount new / and /boot/efi into temp dir.
6. Do one last rsync, including the EFI directory this time
7. Edit new /etc/fstab with proper UUIDs
8. Chroot into new root and run update-initramfs
9. Run update-grub. Which fails.
10. Bind mount /dev /sys and /proc into chroot.
11. Chroot back in and run update-grub
12. Check /boot/efi/EFI/debian/grub.cfg and notice it's still looking for LVM, fix the UUIDs there.
13. Check /boot/grub/grub.cfg and see it is correct.
14. Reboot
15. System doesn't boot
16. Boot back into live USB. Mount all the filesystems including /dev /sys and /proc
17. Run update-initramfs again and see the normal errors.
18. Reboot
19. Profit
20. Wipe old EFI partition to make sure the system doesn't try and boot the old drive.
21. Once all is confirmed, wipe now second drive and mount it somewhere for scratch space.
Windows, of course, would have been two steps:
1. Reinstall Windows on new drive.
2. Copy over any important files.
Sure, would have taken significantly longer as that would pull packages from the network. I'd have to make a package list to make sure everything gets installed and go find all the other non /home customizations. I think it was just network and Munin setup, but I'd probably forget a bunch of other stuff.Couldn’t you have just made a backup of /home/, partitioned the drive with a copy of gparted on the Live USB and done a full reinstall with the GUI installer like a normal person?
I've got about a 20% success rate of doing that and Windows not blowing up. Most of the time I have to go in and run the startup fixes either in the GUI or command line. And then about 20% of the time that all fails too and I end up blowing it all away anyway.You can also image a Windows install to a different computer with a new drive, I have done it before.
It can get fucky if you do it with a new machine with totally new hardware, but modern Windows is surprisingly resilient to hardware changes, and outside of something as drastic as going from Intel to AMD and vice versa can at least get you into the OS to the point where you can get new drivers. You can always install some drivers manually to ensure it starts up on different hardware.
Canonical are swapping out sudo with a Rust version.
Kek.
sudo
in favour of doas. This was back in November 2015 with the release of OpenBSD 5.8. Biggest reason why they did so was because of perceived vulnerabilities with sudo
, and to simplify the absolute mess that was /etc/sudoers
. I love how Canonical Ltd is taking it upon themselves to reinvent sudo (but in Rustsudo
immolates itself upon first being distributed. Fucking Shuttleworth and his insistence on arbitrary, meaningless design choices for the sake of marketplace differentiation.Learn crossdev: https://wiki.gentoo.org/wiki/Crossdev#Build_packages_with_crossdevDoes anyone here have any experience with "copying" a Gentoo installation from one machine to another, including to and from x86 and ARM architectures? Right now I have one "main" installation with all the packages I reasonably need, and I was thinking of compiling my own binaries to just port and install to my other computers, including a Pi 5 & Radxa Rock B+. AFAIK Gentoo does support ARM stuff, though I am not exactly sure if x86 packages will function on ARM.
They're the Microshit of open source.I've heard Canonical is one of the worst open source companies to apply at for a job.