The Linux Thread - The Autist's OS of Choice

Battlefield42 said:
reminds me of how people keep asking this from me on a website im janny on. i never forward these requests and i just ban them. is it bad? yes. do i care? no.
Click to expand...
You'll be the only one to blame for that site getting fucked up the ass by the fines that GDPR non-compliance incurs, then.
 
  • Agree
Reactions: std::string
Battlefield42 said:
reminds me of how people keep asking this from me on a website im janny on. i never forward these requests and i just ban them. is it bad? yes. do i care? no.
Click to expand...
I would assume that any private information on this site is not private information anymore

And just making sure, if I want to move a Debian 12 install from a larger SATA SSD to a smaller NVMe SSD I can just use clonezilla and disconnect the old drive until I change the UUID right?
 
Last edited:
  • Agree
Reactions: 419
clonezilla did NOT like cloning to the new drive, but I was able to use gparted to copy and paste the OS partition, create a new swap partition, and change the UUID and update fstab.

problem is that the server does not list the new drive as a bootable option, as it is not able to boot from a PCIe drive

So now I need to figure out how am I going to boot it. should I update GRUB on the old SSD to add the new drive (and run the risk of losing the ability to reboot if I reformat that drive), should I use a microusb drive permanently plugged in that has a bootloader on it, or should I see if there's a way to add the drive to my server's uefi enviroment
 
Ok, the server is up and running on the old drive while I figure this out.

The best thing to do is to use an old Cruiser Fit to make a drive that can autoboot the NVMe drive, but can also boot a couple recovery tools on the drive such as rescatux, rescuzilla, and netboot.xyz.
 
for those thinking im making a full distro.
im not, it was just for a little bit of fun and to learn the basic parts of every linux distro.
the bootloader, kernel and userspace.
i said I'd cristin it, not release it.
Slav Power said:
Linux From Scratch = goodbye sanity
Click to expand...
i learnt more about how the various parts of a linux work together by doing this then i learned from LFS.
if lfs really wants to teach people how this shit works, then yeet everything out except the absolute bare essentials for a bootable system.
i also forgot to include that im using fat as the file system so any kind of symbolic linking wont work here.
unfortunately due to this, a lot of apps dont seem to work correctly.
so many use symbolic links that finding one that'll work is a pain.
i tried two windowing systems and both refused to work, one gui one, and one cli one.
i suspect that I'm just missing a few things but i cant be bothered to figure it out since I'll bet at least one can't be a static binary.
maybe ill upload the sh script i wrote to make it so you boys can mess around with it.
 
TheDataHorder said:
for those thinking im making a full distro.
im not, it was just for a little bit of fun and to learn the basic parts of every linux distro.
the bootloader, kernel and userspace.
i said I'd cristin it, not release it.

i learnt more about how the various parts of a linux work together by doing this then i learned from LFS.
if lfs really wants to teach people how this shit works, then yeet everything out except the absolute bare essentials for a bootable system.
i also forgot to include that im using fat as the file system so any kind of symbolic linking wont work here.
unfortunately due to this, a lot of apps dont seem to work correctly.
so many use symbolic links that finding one that'll work is a pain.
i tried two windowing systems and both refused to work, one gui one, and one cli one.
i suspect that I'm just missing a few things but i cant be bothered to figure it out since I'll bet at least one can't be a static binary.
maybe ill upload the sh script i wrote to make it so you boys can mess around with it.
Click to expand...
May not be symbolic links, may be sockets. You could try /tmp and/or /run as ramdisks to see if that works.
Might also try umsdos as the fs type which adds some Unix magic on FAT if it's still supported.
 
  • Like
Reactions: TheDataHorder
It's a pain in the ass to get used to the KDE desktop after leaving XFCE 4 from Endeavor OS but I have done it. I am officially filled with Slack.
image.png
 
  • Winner
  • Like
Reactions: Blackhole, Belisarius Cawl, Kiwi2Shoes and 4 others
Boo, did a clean reinstall on the new drive and getting permissions issues and I don't know why
I own the files and have set permissions to 2775 and can access each mounted drive directly, but for some reason I cannot access the mergerfs pool unless I use sudo

edit: weirdly enough, disabling the pool then changing permissions on the mountpoint then reconnecting the pool worked

I am annoyed at how easy it was to configure dnsmasq just by following the official Debian guide, compared to the headache I had trying to get something working

jellyfin and bazarr refused to import my configurations so they had to be set up again, but everything else seems to be easy to get up and running
 
Last edited:
  • TMI
Reactions: Yandex Captcha Solver
Betonhaus said:
protip: do not unzip a tarball of unorganized files to /
Click to expand...
I feel like file management in Linux would benefit with some form of aliasing paths to storage partitions as some sort of Windows-esque shorthand of A:/, B:/ C:/ and so on. Where is it that it normally mounts partitions? /media/sdb and such?

I feel like Linux's way of having every bit of your system as a path in the file system is a very bad idea from the home user standpoint. There should be toggleable abstractions for when you don't have to fuck around with the core Linux, so that / misuse, even accidental, won't lead to you fucking everything up. Have the terminal run in "simple mode" where you have letters for mount points, special paths like Config/ to access /etc and so on. Keep / away from the user whenever the user doesn't need to access it.
 
  • Disagree
  • Horrifying
  • Like
Reactions: Margo Martindale, Sperg Coalition, Marvin and 8 others
I did manage to fix it. I had changed ownership of / and /root to jellyfin and set /'s permissions to 750, and the OS did not like that one bit. Luckily the grub bootloader would boot me into my old drive where I was able to mount the new drive, figure out what was different, and fix it.

Bash: 
drwxr-x---   22 jellyfin adm   16384 Apr 22 08:10 newos
this is where the new drive was mounted to, and is the / for that drive. it should not look like that.

Now to leave the fucking thing alone as I started this around 2pm yesterday and I finally finish just before 9am. I just need to go to my partner's parents place to connect their roku to the new server as I can't walk them through it over the phone

all that's left is to install and configure some apps I barely use, and to shrink the old os partition to make a partition to download stuff to - but I don't have to do that until I do another bulk download of a whole show
 
Last edited:
  • Like
Reactions: Vesperus
Slav Power said:
I feel like Linux's way of having every bit of your system as a path in the file system is a very bad idea from the home user standpoint. There should be toggleable abstractions for when you don't have to fuck around with the core Linux, so that / misuse, even accidental, won't lead to you fucking everything up. Have the terminal run in "simple mode" where you have letters for mount points, special paths like Config/ to access /etc and so on. Keep / away from the user whenever the user doesn't need to access it.
Click to expand...
You're basically asking for an immutable /, which seems to be where every distro is slowly heading anyway. You can still accidentally clobber /etc on something like Fedora Silverblue but you can also just easily roll back your oops.
 
  • Like
Reactions: Kiwi2Shoes and The Ghost of Kviv
Slav Power said:
I feel like file management in Linux would benefit with some form of aliasing paths to storage partitions as some sort of Windows-esque shorthand of A:/, B:/ C:/ and so on. Where is it that it normally mounts partitions? /media/sdb and such?

I feel like Linux's way of having every bit of your system as a path in the file system is a very bad idea from the home user standpoint. There should be toggleable abstractions for when you don't have to fuck around with the core Linux, so that / misuse, even accidental, won't lead to you fucking everything up. Have the terminal run in "simple mode" where you have letters for mount points, special paths like Config/ to access /etc and so on. Keep / away from the user whenever the user doesn't need to access it.
Click to expand...
That's what snapshots are for, or cloned datasets for switching "/" on demand. Just embrace COW. Or don't run random crap as root.
 
  • Like
  • Agree
Reactions: The Ghost of Kviv, Kiwi2Shoes, Vecr and 1 other person
Most file browsers already do offer that. You click the drive in the side bar, it gets automatically mounted under /run/media/user/uuid or whatever your fstab or systemd config says, but the user never needs to worry about its actual path because it’s just accessible in the sidebar, just like in windows. That goes for drives you keep permanently attached, too, but which aren’t recognised by Linux as system partitions. For example your /home partition won’t appear in the list as a shortcut, but the flash drive you use for homework would, as would, say, the windows volume on your ZFS you use for your VM.
 
  • Like
Reactions: Vecr, Sperg Coalition, 419 and 2 others
Slav Power said:
I feel like file management in Linux would benefit with some form of aliasing paths to storage partitions as some sort of Windows-esque shorthand of A:/, B:/ C:/ and so on. Where is it that it normally mounts partitions? /media/sdb and such?

I feel like Linux's way of having every bit of your system as a path in the file system is a very bad idea from the home user standpoint. There should be toggleable abstractions for when you don't have to fuck around with the core Linux, so that / misuse, even accidental, won't lead to you fucking everything up. Have the terminal run in "simple mode" where you have letters for mount points, special paths like Config/ to access /etc and so on. Keep / away from the user whenever the user doesn't need to access it.
Click to expand...
The current filesystem setup is fine as we don't need to baby proof the os like ChromeOS does, but it would probably be more ideal if more guides that introduce people to Linux focus on ensuring that people work in the correct directory when performing operations. And maybe if tar had a warning like "this will extract 300 files totalling 8gb into '/', are you sure?"
 
You must log in or register to reply here.
Back