You can block communities one at a time. Once you get “All” mostly under control, you only have to worry about new ones that pop up.
I remember starting on Lemmy going “Wow, that’s a lot of furry porn… block block block…”
You can block communities one at a time. Once you get “All” mostly under control, you only have to worry about new ones that pop up.
I remember starting on Lemmy going “Wow, that’s a lot of furry porn… block block block…”
Symlinks. It doesn’t matter which partition they’re on.
https://www.futurelearn.com/info/courses/linux-for-bioinformatics/0/steps/201767
Typicaly the way a KVM worls is you connect both computers to it, then a single monitor, keyboard and mouse.
Flipping the switch on the KVM moves the keyboard and mouse input, and video output, from machine #1 to Machine #2.
I guess I’m not understanding the question…
You have a laptop connected to a docking station.
You have linux PC connected to a monitor, keyboard, and mouse.
You want to use the same monitor, keyboard and mouse on both machines? Switching between the two?
The monitor is the easy part, lots of monitors have multiple inputs, so you put the Linux PC on one input and the laptop dock on the other. Switch video inputs using the buttons on the monitor.
The keyboard and mouse would be tricky without a KVM switch. In theory, with a wireless keyboard and mouse, you could connect it to both machines, but you’d run the risk of using one and sending garbage data to the other if both were turned on at the same time.
I’d just get a KVM, that’s what they’re there for.
Wait until she finds out about daemons.
Over what?
I second the Epson Ecotank, but the problem it has is that unless you use it regularly, it dries up and needs 1 to 3 cleaning cycles before it will print again.
So unless you want phone calls like “It’s printing blank pages again…”
So when it comes to kernel modifications, I’m old school…
“If it’s not broken, don’t fix it.” :)
https://www.redhat.com/en/blog/balancing-if-it-aint-broke-dont-fix-it-vs-release-early-and-often
Unless there’s some VERY specific need, some security hole that needs patching, some critical flaw that is failing, in general, DO NOT mess with the kernel.
That being said, there are tons of good guides you can find just by googling “linux kernel modifications”, but also specific guides for your installations. RedHat makes it dead simple to do stuff like this.
But before you do it:
Make sure you have a specific need you’re addressing.
Make sure you have all the necessary backups you require.
Have a roll back process in case something goes wrong.
Have a diagnostic testing plan.
You have to do what’s best for yourself and your situation.
I was a systems administrator for a decade or so and I reached a turning point… I had a bad experience, was burning out, and I had the opportunity to take a new sysadmin gig at a credit union, or take a step down to a support role, that paid more, with less responsibility, and had IPO shares…
My kid was getting ready for college, so option 1 positioned me well if I needed to load up student loans. Option 2 maybe made it so we wouldn’t need student loans.
I went with option 2. Less stress, less responsibility, more pay, paid for kids college in cash, now through a series of IPOs and acquisitions, I’m working for a VERY large tech company.
Does “not being an engineer” look right for you? Quite possibly.
I’m not going to address the Fedora/KDE specific questions because I’m more of a generalist.
Can I partition /home directory in a different drive and still fuction?
Transferring /home directory without reinstalling Linux?
Best way to partition my / and /home directories?
Take the time to learn how Symbolic Links or Symlinks work. Once you have that down, you can pretty much put whatever you want, wherever you want.
https://www.futurelearn.com/info/courses/linux-for-bioinformatics/0/steps/201767
https://www.liquidweb.com/kb/creating-and-removing-symbolic-links-symlinks/
The core is the same, the shells are each a little different. I remember juggling 3 different installs and having to keep a cheat sheet to keep them all straight. :)
I don’t know that you can learn “all of them”, there are new ones popping up all the time.
I started with Unix in 1988 because I wanted to play on the Internet and back then you either learned Unix or you didn’t go.
Unix is interesting because when Bell labs came up with it, they were told “Look, you can have a monopoly in the telecommunications industry, or you can have a monopoly in the computer industry, PICK ONE.”
So they picked the telecom industry, but at the same time they went “Hey, here’s this computer OS, see what you all can do with it!”
So you ended up with Unix System V, HP-UX, Irix, BSD Unix, and so on and so on. They were all Unix but all also a little bit different.
Roll forward to the early 90s and Linus Torvalds going “Hey! Imma make my own Unix!” and then THAT splintered into all the Linux variants we have today.
When the early days of Linux happened, my reaction was “Well, I already learned Unix, how hard could this be?” :)
The problem was, there was no easy way to collect everything you needed for an install, so I waited until someone put out a CD with all the files I needed, I think that was 1993? 1994? Something like that.
Anyway, my first was Slackware. Since then, I can’t tell you how many I’ve used. Different situations call for different things. I was a Redhat admin for awhile. I installed YellowDog on a PS3 for fun. MacOS X is not Linux, but it’s underpinnings are based on BSD Unix so it’s kind of a kissing cousin. Apple does a lot of goofy shit, but it’s not insurrmountable if you know Unix.
My certifications were done around 2000/2001 through a company called SAIR and I’m not even sure they exist anymore. They got absorbed into Thomson Learning in 2002.
It was a great experience though. Wouldn’t trade it for anything. I made some good money administering Avaya Definity and Intuity phone systems running Unix.
I’ve been using Linux for 30 years now, certified to teach it and everything… Here’s your problem:
“Stop telling people it’s ‘tech-y’”
Compared to Windows or MacOS, yes, it is very techy.
“offer to help them install.” - If they need your help to install it they absolutely have no business running Linux.
“They don’t understand the concept of distros” - If they have no understanding of distros, they have no business running Linux.
Think of it like this… if they can’t wrap their head around a distro, what’s going to happen when you try explaining a package manager?
I get the evangelism, but Linux simply is not for everyone, that’s why Apple invented iPads.
I’m in this one:
Exactly. There’s no way to even know what the previous permissions were for everything.
They were TRYING to recursively change permissions in a single directory, accidentally hit the whole system. :(
Not me, but one I saw… dude used chmod to lock down permissions across the board… including root… including the chmod command.
“What do I do?”
🤔
“Re-install?”
Bunch of stuff here, but it looks like the Apple Watch implementations may be limited:
https://github.com/topics/heart-rate
I should say too, the fingertip pulse oximeters they use in doctors offices and hospitals can be had on Amazon for like $20.
Why do they care what OS people use? Is it the anti-cheat software that needs Windows?