Software dev, D&D DM, Dog Dad, Linux User, FOSS supporter, pc builder, cyclist, volleyball player, wannabe handyman, socialist, feminist, and ally.

Profile pic credit Backie and Banner pic credit System76

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

help-circle

  • I actually think Lemmy should take a page from Mastodon here. Instead of users creating groups (which sounds like a huge headache to implement smoothly), Lemmy should add hashtags or something similar. So I would sub to #photography and people posting would be restricted to a max number of hashtags (TBD). You can then choose to stay subbed to the hashtag and/or sub to the communities that crop up frequently on your feed and then unsub from the hashtag if you want.





  • Well as long as you take a snapshot of your data and move that snapshot to another drive, you’re free to tinker without real worry. Arch Linux wiki should have lots of examples of what you’re trying to fix or modify. There’s always a fresh install as well, which isn’t ideal most of the time but as long as the data is safe, then its an option. Best of luck, hope you’re able to resolve the issue.


  • Only thing I can think of is the subvolumes left over might be causing an issue. I don’t know how snapper performs a rollback and I’ve seen a couple ways to do it. Sometimes its modifying the default subvolume to the snapshot you want to rollback to. This is fine IF your kernel params are NOT specifying the subvol. That would look like this rootflags=subvol=subvolume_name.

    Usually I just rename the subvols and make sure the snapshot I’m renaming to replace the current root subvol is not set to read only.

    So rename current root to root.broken Then rename snapshot to root Then set readonly prop to false.