Linux Learning Resources - Share Yours Too!

I'm not supposed to giggle, because I'm Admin, but I know what you mean. ;)
I kinna look at it this way....

Being a car guy, and Dad teaching me about cars....
I'll omit my passion for guitars, amps, and music, I drove my parents crazy with....

Lots of cars out there... It use to be most or half of em had an extra peddle called a clutch, and a gear shifter "stick". Those manuals still go just like the rest, you just gotta learn how to drive em.

Actually today with my pickup truck being an automatic, I still catch myself trying to grab the stick, gear shifter, even though it's not there! hehe... Or worse, unconsciously trying to push in the clutch that's not there, accidentally hitting the brakes. That's not good!! Or trying to click on the headlights brights with your foot. The button was, use to be, on the floor off to the left. Everything is on the steering columns these days. Although the old Mavericks, and others, had the shifter on the column. Anyway...Calling myself a dumbass each time! haha

Maybe a bad analogy?

Old stuff can be difficult to get use to, and new stuff can be difficult to get use to. It's all good stuff.

Just my outlook on it all.
 
Last edited by a moderator:


Bluetooth drove me nuts for a time. I hate when something runs on my system that I don't want to always run. Every so often I like to pair bluetooth with these cool speakers I have to pipe music to from my computer. When I'm not doing that I don't want bluetooth service constantly running.

This may not be a great way of dealing with it, but on my system bluetooth can be a pain.

I fixed it in a roundabout way....

Code:
Lets get rid of freaking bluetooth service always on....

sudo service bluetooth stop
sudo service bluetooth start
service bluetooth status
sudo systemctl disable bluetooth.service

Why is this so hard!!! Ugh....

sudo nano /etc/bluetooth/main.conf
Find and replace AutoEnable=true with AutoEnable=false
procedure may not always work ... Why?
**************************************
Bluetooth wants to run no matter what.
So... Lets put the creepo in jail...
**************************************

Ok... Doing this....
**************************************
systemctl stop bluetooth.service
sudo systemctl disable bluetooth.service
sudo systemctl mask bluetooth.service
**************************************
Turn back on....
sudo systemctl unmask bluetooth.service
sudo systemctl enable bluetooth.service
sudo systemctl start bluetooth.service
**************************************

Make sure it's in jail.. or set free...
**************************************
systemctl --type=service --state=running
**************************************
 
Last edited by a moderator:
A few things that helped me in the past. Most have probably already been listed here already.

linuxcommand.org - The Linux Command Line by William Shotts. The book helped demystify the Linux command when I was starting out.

https://explainshell.com - Breaks down commands and explains the individual pieces.

https://wiki.archlinux.org - I've found help and solutions to many problems on the Arch Linux Wiki regardless of what distro I was actually using.

https://www.protondb.com - Very helpful if you're playing Steam games for Windows on Linux.
 
Last edited:
I have something to add to this ancient thread...

There is command called sysctl (see man sysctl) which is used to configure kernel parameters at runtime and this website below will help you explore plenty of options to configure:

For instance, to enable IPv4 forwarding you'd click on net link, then ipv4 and then ip_forward and it should take you to https://sysctl-explorer.net/net/ipv4/ip_forward/

There it says variable: net.ipv4.ip_forward and 0 - disabled (default) not 0 - enabled below that, therefore to enable it you run:
Bash:
sudo sysctl --write net.ipv4.ip_forward=1
This is temporary and is lost upon reboot, for permanent config you'd run this instead
Bash:
echo "net.ipv4.ip_forward=1" | sudo tee /etc/sysctl.d/ipv4_forward.conf > /dev/null
Note that you want to set any variables in drop-in directory /etc/sysctl.d instead of modifying them directly in /etc/sysctl.conf.
When you do this you also need to load your config that was written into /etc/sysctl.d:
Bash:
sudo sysctl --load > /dev/null
sudo systemctl restart systemd-sysctl

If you prefer you can also enable kernel parameters on GRUB command line, here is another link with plenty of kernel options you can configure and learn about:

For permanent changes you edit /etc/default/grub file and add your desired parameters to the GRUB_CMDLINE_LINUX and then run:
Bash:
sudo update-grub
Or you can set them temporary during boot when GRUB shows up and pressing c on keyboard and appending your parameters with values to the command line.
 
Last edited:
AI has been teaching me Linux now lol!
 


Follow Linux.org

Staff online

Members online


Top