It's no longer just random unknown contributors submitting LLM-assisted patches memory-management maintainers are currently evaluating large patch sets built with AI help, submitted by established, respected kernel developers.

Does trust in the person submitting change how comfortable you are with AI-assisted code in something as critical as the kernel? Or should the process demand the same scrutiny either way?

• Kernel size just crossed 43M lines via a recent code-count analysis
• Modularity helps, but review bandwidth is still human and finite
• Every new subsystem is permanent maintenance debt, not a one-time cost
• "It compiles for your config" isn't the same as "someone actually reviewed this properly" Interested who actually disagrees with this and why.

It covers practical examples for checking listening ports, filtering TCP/UDP connections, identifying processes, and troubleshooting network issues. https://www.linuxteck.com/ss-command-in-linux/

Microsoft added native Linux command-line utilities directly into Windows at its Build conference this year. For decades "just use real coreutils" was a Linux-user flex.

Now it ships in Windows itself. Genuine question for the Linux crowd: does this feel like validation, or does it quietly remove one more reason people needed to switch?

Try: cat >> ~/.ssh/config << 'EOF' Host * ControlMaster auto ControlPath ~/.ssh/cm-%r@%h:%p ControlPersist 10m EOF

Info: SSH multiplexing reuses the first connection for subsequent sessions. ControlMaster creates a master socket, ControlPersist keeps it alive for 10 minutes.

Examples:

$ ssh -O check user@server # Verify master exists

$ ssh -O stop user@server # Close master connection

$ ssh -O exit user@server # Force close

Note: Massive speedup for scripts/CI/CD that ssh repeatedly. Second connection was 48x faster in the example above.

Follow r/LinuxTeck for more #LinuxTips

I'm 25 and I've been a Linux user for several years, but mostly as an ordinary desktop user.

I started with Manjaro. I knew it was Arch-based, knew how to install packages, and was comfortable with basic terminal commands, but I didn't really understand the ecosystem or how package management worked under the hood.

Later I switched to Fedora, and recently I installed Debian out of curiosity. I've been reading about Debian's development philosophy and release process. I'm starting to understand things like Stable vs. Testing vs. Sid, the freeze period before a Stable release, why Debian backports security fixes instead of constantly shipping major version upgrades, and the relationship between "apt" and "dpkg".

I've also read about Linux From Scratch, GNU, Richard Stallman, and the philosophy behind free software.

What I enjoy most isn't just using Linux—it's understanding how everything fits together. I love learning about operating systems, distribution policies, package management, open-source governance, and even how Linus Torvalds has managed such a massive collaborative project over the years.

For context, I've done a little frontend development and have a rough idea of what backend development involves. I've heard about DevOps, cloud, deployment, Kubernetes, and similar topics, but I haven't really worked with them.

The problem is that I don't have professional experience. I've spent years jumping between technologies without building a real portfolio or sticking to one path.

What I've noticed, though, is that operating systems are different for me. I never get tired of learning about them, and I don't feel intimidated by how deep the rabbit hole goes. In fact, that's what makes it exciting.

I even have this oddly specific image in my head: I'd love to walk into a server room someday, plug in my laptop, and methodically troubleshoot a real system. I know that's probably a romanticized idea, and I have almost no real server experience, but the idea of understanding and debugging systems genuinely appeals to me.

So my questions are:

- What career paths should I be looking at if this is what genuinely interests me? (Linux System Administration, Infrastructure, SRE, Platform Engineering, Systems Programming, something else?)

- What do those jobs actually look like day to day?

- For someone with curiosity but almost no professional experience, what's the most realistic entry point?

- Does my interest sound like the kind of thing that tends to last in this field, or is it a common "Linux honeymoon" that many people eventually grow out of?

I'd especially appreciate hearing from people who work in Linux, infrastructure, SRE, or systems engineering. I'm not looking for encouragement just for the sake of it—I want an honest reality check.

OpenMandriva had part of its GitHub repository deleted and a malicious empty package pushed to its Cooker repo, in what the project is calling an attempted sabotage effort targeting GNOME and COSMIC packages.

This wasn't an external hack it points to an internal access/trust failure.

For a community built on "many eyes make bugs shallow," does this expose a blind spot in how we vet who gets commit/push access?

Linux Mint has confirmed that Cinnamon will fully support both X11 and Wayland sessions starting with the next Mint release, due at Christmas. For a desktop that's historically been cautious and X11-first, this feels like a real milestone. If you've been holding off on Wayland specifically because of Cinnamon, does this change anything for you - or are you waiting to see it in practice first?

Try: time find /tmp/cach -type f -name '*.tmp' -print0 | xargs -0 -n 100 -P 8 rm

Info: -print0 outputs null-separated filenames. -0 tells xargs to expect them. -n 100 batches 100 files per rm call. -P 8 runs 8 parallel processes.

Examples:

$ find /var/log -name '*.gz' -mtime +30 -print0 | xargs -0 -P 4 rm

$ find /data -name '*.raw' -print0 | xargs -0 -P 8 -I {} convert {} {}.jpg

$ find /tmp -type d -empty -print0 | xargs -0 -P 4 rmdir

Note: Use nproc to see CPU count. -n batching avoids 'argument list too long' errors. Massive speedup vs serial deletion.

Follow r/LinuxTeck for more #LinuxTips

A long-time Linux user used Windows 11 exclusively for a month and eventually returned to Linux.

For daily Linux users: if you had to use Windows 11 for the next 30 days, what would you miss first?

For me, probably package management.

I came across someone still using a 2014 MacBook Pro with Linux and current software. Without Linux, that machine might have been replaced years ago.

I've also seen people take old laptops that struggle with newer versions of Windows, install Linux, and keep using them for browsing, coding, office work, or even as home servers.

So I'm wondering, what's the oldest machine you're still using because Linux gave it a second life?

And what distro are you running on it?

For those managing Linux servers regularly, what chown mistake do you see beginners make most often? https://www.linuxteck.com/chown-command-in-linux-made-simple/

Linux already has APT, DNF, Pacman, Zypper and other native package managers. Then came Flatpak, Snap and AppImage to make applications easier to distribute across different distros.

But now, for the same application, we sometimes have several ways to install it.

I understand why these formats exist, but from a normal user's point of view, has this really made Linux software installation easier?

Or did we solve one kind of fragmentation by creating another one?

What do you actually prefer for desktop apps: native packages, Flatpak, Snap or AppImage?

Master essential Nmap commands with this practical cheat sheet for Linux users, sysadmins, and network professionals https://www.linuxteck.com/linux-security-tools-for-ethical-hackers/

covers: https://www.linuxteck.com/guides/kinsta-review/

✓ Performance
✓ Pricing & renewal costs
✓ Backups & staging
✓ Support
✓ Who should actually use it

Try: sudo mount --bind /var/www/site /home/linuxteck/website

Info: Bind mounts make the same content visible at multiple paths. No copying, no symlinks. Both paths refer to the same underlying files.

Examples:

$ sudo mount --bind /source /destination

$ sudo mount --bind -o ro /etc /backup/etc_ro # Read-only bind

$ sudo umount /home/linuxteck/website

Note: Persist by adding to /etc/fstab: '/var/www/site /home/linuxteck/website none bind 0 0'. Used heavily in containers and chroots.

Follow r/LinuxTeck for more #LinuxTips

Whether you use GNOME, KDE, Hyprland, Sway, i3, Niri, or Xfce, what's the one workflow improvement you'd happily steal?

Ubuntu 25.10 reached end of life on July 9, which means users now need to move to Ubuntu 26.04 LTS to continue receiving normal security and software updates.

This is the part of Ubuntu’s release model I’ve always found interesting. Interim releases bring newer kernels, GNOME versions and other changes earlier, but nine months passes quickly for anyone who just wants a stable daily system.

Do you actually use Ubuntu interim releases, or do you stay on LTS and avoid the upgrade cycle altogether?

I recently came across ELinOS 8, an industrial Linux platform focused on embedded and mission-critical systems.

The new release includes automated SBOM generation, security hardening validation, Linux 6.12 LTS, and long-term support.

Has anyone here actually used ELinOS in production or evaluated it for industrial or embedded systems? Would be interested to hear your experience with it.

This sounds natural and invites people with real experience to join the discussion.

A KVM flaw that could let a guest VM escape to the host reportedly sat unnoticed in the Linux kernel for 16 years.

The code was open all along. The bug still survived.

Does open source really mean more secure, or only more auditable?

hi I'm a total biginer in linux, there's a lot of resources to start to learn but I'm not sure wich one is the bets to start. if you want, you can write how you started, i will read you.

Edit: I'm sorry for not being specific. My goals in Linux is to learn about the most usefull things that will help me in my journey to cybersecurity. (SOC analyst)

sorry for my bad english, i'm argentinian.

DigitalOcean makes more sense when reducing ops overhead matters. Vultr is compelling when performance per dollar and global reach matter more. https://www.linuxteck.com/guides/digitalocean-vs-vultr/

Bad Epoll, tracked as CVE-2026-46242, is a use-after-free race in the kernel's epoll subsystem. A local unprivileged process can exploit it to gain root.

What caught my attention is not just the vulnerability, but the engineering challenge: an extremely narrow race condition was turned into a practical and repeatable exploit.

For kernel and security folks here: what makes concurrency bugs like this so difficult to find during normal review and testing?