That is unless you remove EOS packages, repositories, keyrings, mirror list and then update. I did this for a laugh once and it's unsurprisingly easy to convert an EOS system back to Arch. I suppose it's an option if the script stops working and you don't want to do the manual install. I usually do the manual because I like to set up GUID partitions for the auto-generator that locates and mount said partitions without any explicit /etc/fstab entries. It's what I am used to now and you don't risk stuff happening to your entries messing your system up. IIRC no manual installer lets you set that up during partitioning, but I could be out of date on that.
I use the distro SystemRescue for this instead. It's intended to be used in this way and comes with a ton of tools for it, but PuppyLinux probably works just as well too. For fstab issues you don't really need either, you can append systemd.unit=emergency to boot parameters which boots you into emergency mode, the most minimal environment available on systemd. You then mount to write, and you can fix from there. I prefer to use SystemRescue still though, it's nice to have a XFCE environment to fix in.
I respect Puppy Linux a lot for what it is. It's not much of a "daily driver" for anyone passing through here but for someone who does basic stuff on their computer it's great and can extend the life of old hardware significantly. And as you say, you can keep it lying around as it's designed to live entirely on removable media if you want so if you want a portable OS with GUI that runs well, it's a good choice. I've never considered using it for recovery, though.
I've been waiting for a year or two for my Arch install to brick itself so I can go back to Gentoo
Why wait? If you really want to get back onto Gentoo I say just do it.I've been waiting for a year or two for my Arch install to brick itself so I can go back to Gentoo
That's like saying that you want to wait for your horse to die before getting a car. Just make the switch when it's convenient so it doesn't happen when you are in the middle of a bunch of important things like a vacation or a family crisis.I've been waiting for a year or two for my Arch install to brick itself so I can go back to Gentoo
I have a good arch setup now, everything works how I need it to, I just dont have enough time like I used to, to fuck around with distro hopping/swapping. Although I know it would take an hour or two max to get a workable setup on my machine.
It all stems from your fstab being fucked up, really. Both mount not working and Dolphin not seeing partitions. There's a section on the Install page of the Arch Wiki that talks about setting up your fstab file manually, that's what I'd do personally. Also, it's very useful to have a live system on a USB drive for times like this.
pacman -Scc) and checking which packages are orphaned (pacman -Qtdq). Run down that list and check their info (pacman -Qi). It's not really a solution, but more of a sanity check to see if the links between packages are still OK and you're not about to pull a Linus and nuke something very important. The command for removing orphaned packages is pacman -Rns $(pacman -Qtdq). Then try a full system upgrade with yay, force a refresh of the database to be safe - that is the double "y" in pacman -Syyu.Of course. My post has a link to the AUR package. Someone has probably packaged it for your distro as well, unless it's niche.
This may be a dumb question, but have you a) not rebooted your computer between the time since you've added the drives until you ran this big update and b) had been using the mount command or just waiting for the drives to show up after being plugged in, and never actually had a persistent mount for those drives in the first place?
I don't see why, when you use it properly it's very intuitive. Just edit it on nano, do the systemctl reload to load it into memory, then Sudo mount -a and you're done.
tbh gentoo is baby mode nowadays what with everyone having 32 GB of RAM and 8+ CPU cores
I just run genfstab to generate the fstab file from my mounted drives
That's usually what /mnt is used for. You don't have to. But it's usually just an empty directory you can mount drives on and it will be fairly safe to do it there.
"Babe, what the fuck is neofetch? I thought we were having movie night"
I used to use /data for a while but tbh it's easier to find all the drives if you just throw them all in /mnt. Heck I have all the docker config files and such in /mnt/docker so I know where they are and can move them to their own drive if needed
update: Definitely is. Writing is now just KB here and there but reading is MB here and there.
