Hint: :q!
Community rules (click to expand)
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
So I only just got into linux this year. I gave some X11 distro's a go, but the screen tearing was awwwwfulll. So I've been running Wayalnd/Plasma for months now.
What exactly am I missing out on? Seems lots of users here still favor X11 over wayland but as I've never had any problems. It's still unclear to me why people are still sticking with X11.
If you have no issues with Wayland, keep using it. You aren't missing anything.
Linux is a vast space, and some people have use cases that aren't covered by Wayland, yet.
So they still use X.
Nothing, unless you really want to use a DE that's still lacking behind in its adoption. There are a few tools that still only offer early support for it (like RustDesk), but otherwise Wayland is a way better choice these days. However if you got an Nvidia GPU and need to use the proprietary driver you might be forced to still use X11. Their pile of garbage still routinely bugs on Wayland, and given their work on NVK I doubt that thing will ever get fully fixed.
Gather around kids, story time. It was 2002 and I had a desktop pc with two video cards, one Matrox with dual video output (they were pretty much the only consumer ones with that at the time) on AGP slot, and one "something" (probably ATI, it still had and RCA port) on PCI. So I installed gentoo (from stage1, as it was custom at the time) and fiddled around with xorg.conf to have two monitors output from the Matrox and a third (yes, I had 3 monitors) from the ATI.
That's when I understood the power of Linux (no way win2000 was able to do that).
I get the joke, but I'm getting tired of these very, very old memes being reposted ad-nauseam when they're so outdated. I did not have to open the xorg.conf file for at least a decade, probably more. It was a very annoying thing to do, yes, but hasn't been an issue for a lot of install in forever.
There's a resurgence of these "but it's very weird/difficult/annoying" outdated memes these last few weeks on a lot of websites, and at this point I'm wondering if it's just people discovering them or just some people bashing linux systems based on their experience from the last century.
It's people entering the Linux space and wanting to join the tribe by posting Linux memes they found on google.
I broke xorg.conf when i installed Linux Mint about a year ago, but i forgot what for. Ironically i never had issues with an Arch based distro.
Idk what I've traded to never have issues with that file, but I worry every day that the horror is ahead of me and not behind
This comic was posted in 2011 but still holds up today perfectly lol.
They still use X. You must never go there.
As an X user I support this message.
Wayland
Y'all have Desktop Environments?
I remember when loading a GUI in *NIX systems was frown upon and would get you judged by your peersβ¦
Y'all are still using xorg?
I am definitely going to need my morning coffee. I see the word "Y'all" and I'm somehow thinking "shouldn't it be Xall if we're taking about X11? Wait what's wrong with my brain"
A new Linux meme? I don't believe it
professional tip for those who decided to rock Debian on a laptop with two GPUβs.
Envycontrol will take the headache away from manually configuring your xorg & xrandr, trust me, compared to the Debian documentation this will save you hours of your life.
Can it force apps to use iGPU when dGPU is on? It's one of the things I miss from windows and couldn't figure out on linux
It has this hybrid option, thatβs about it from what I know.
Set graphics mode to hybrid and enable fine-grained power control:
sudo envycontrol -s hybrid --rtd3
Edit: the βrtd3 flag seems to have different levels of power management.
--rtd3 [VALUE] Setup PCI-Express Runtime D3 (RTD3) Power Management on Hybrid mode. Available choices: 0, 1, 2, 3. Default if specified: 2
...who... IN THE FUCK!!! Reads Debian docs?
Arch are the true Linux docs, maybe Gentoo docs, worst case Ubuntu forums.
Run a ton of Debian, only time I check their docs is when I'm trying to remember what the current stable release is called.
...who... IN THE FUCK!!! Reads Debian docs?
How else does one learn the distro they use without consulting the documentation?
Like I said, I use debian docs to install.
After that arch docs are INCREDIBLY thorough, they cover almost all of linux and are far more exhaustive than any other.
I do that. Why not? Best source on Debian specific stuff.
mandb -su | man man
Every config: get it to a place that works and create a .WORKING backup copy
Funny how vocal Wayland haters used to be until they tried Wayland.
Still won't handle popup menu correctly, still won't allow copy/paste with CLI programs without using an extra, implementation-specific, piece of software, still won't allow some window to correctly detect their position.
Wayland might be interesting, but between blind haters and blind supporters, it's really annoying. Forcing people to switch while some basic features are "mostly working" is not helping.
still wonβt allow copy/paste with CLI programs without using an extra, implementation-specific, piece of software
What are you referring to here? I haven't noticed anything out of place on KDE regarding copy/paste...
vim can't use the kde/wayland clipboard to copy/past properly, you have to script it through something. I've read it's related to non foreground app not being able to manipulate the clipboard or something close to that, which a CLI app will never be.
There are "solutions", mostly overriding vim behavior to write/read from that dedicated program, though. It's not a show stopper, but not every software allow this kind of flexibility.
Still gathering up my courage to make the switch. The better security / isolation between apps is a huge feature for me. But porting all of my shitty xorg-specific scripts and hacks will be a pain.
I mean, there was a point in time, quite some years back, when I had to do up modelines, but Xorg can generally handle things without an xorg.conf.
It has improved, but most developers working on Xorg have moved to Wayland. I'm not saying Xorg isn't still useful at times, like forwarding over SSH, but Wayland has more isolation & security considerations, which can be seen as both an advantage & limitation. However, Wayland compositors have implemented most controls & protocols now to fill in the gaps.
I still remember the old times before xorg.confs were modular. The truly hard times.
I was there, Gandalf, I was there when the modelines of xf86config failed...
I remember when /bin/sh was the default shell, when you had to build grep from source. LILO was our bootloader. Dmesg was our seer. We made fire from a friction drill. Knapped our own blades from flint.
Simpler times.
I dearly miss lilo, it was the best bootloader. But then everyone started using grub which I hated with a passion. So glad that there are so much better options nowadays.
Honestly, I'm still worried about getting pilloried for this. Systemd-boot on BTRFS with snapshotting is awesome. Bonus points if your system is entirely in initrd.
https://github.com/uszie/systemd-boot-snapshots
https://www.kernel.org/doc/html/latest/admin-guide/initrd.html
... I don't remember building grep, nor do I remember a time before bash.
Are... Are you God?
I was there when the dark magic was written. In the time before git. The shell had not yet been born again.
The great wizard Stahlman still held sway in the high court, his Gknights of Gnu were just building their kernel. Lo gaze upon their mighty works and see they lie in ruin.
Torvalds was the true vanguard, he lead us to build the mighty kernel, to reverse engineer the binary blobs, coax the meaning from machine code, a thin line from serial to stdout.
No heirarchy but those inherited from the libraries. User space was our land, ~ was our home, #! was our flag. No gods, no masters, only code.
Genuinely curious. When was your first time touching Linux/GNU?
'94 but I was on Usenet (actually probably not usenet but definitely one of the "readers") when I heard about it first. That would've been around '93. Me and a buddy were pretty nerdy and his dad worked at Bell Labs and they got a couple floppies. That was my start. It was just the kernel and Gnu Utilities. Literally Linux+Gnu. Shortly after that I grabbed SLS Linux, that became Slack. Then Debian, I was in the listserve when Ian would still answer questions and fix bugs. I hope he's found the peace now he was searching for in life.
I've contributed to quite a few open source projects over the years, nothing foundational. I didn't really know anybody from the old old days. Just a geeky kid lucky enough to have a computer and a modem at the time. I am very privileged to have grown up when I did and where I did.
I don't envy the kids coming up now. Completely abstracted away from their systems to the point where they actually think it's magic. I had a very junior engineer ask me how to print a pdf the other week at work. I can't imagine how modern education and tech have failed them. I hope I'm wrong but it feels like LLMs are talking away curiosity and hacking. I'm sure that's just me being a crusty old bastard though.
Speaking of I've been having fun playing around with this as of late.
You'd need to have access to the prompt tooling, or worse yet the RAG, otherwise you're just hoping that a user feeds your email into an LLM. The hidden ascii though, old tricks are new again.
I'm close, 93 also I think, slack on a 386.
Got stuck in vi, had to reboot.
Remember thinking how awesome 6 virtual consoles were. I think my tmux addiction came from there.
Lol! I thought vi was genuinely a new layer of the OS, like an embedded console. Ended up creating 10 files containing exit, or quit, or ^c, until I hit the escape key and the cursor changed....then I rebooted from frustration and actually read the man page. The controls are all from this dumb terminal keyboard that had useful decals on them. That's where navigation with kjhl came from and :q to quit.
https://pikuma.com/blog/origins-of-vim-text-editor
Rage quitting vi/vim really is a right of passage.
Remember ed?
Do you remember...
When someone first showed you tab completion?
Like absolute fucking wizardry man, like a Jedi Master appeared in front of you with the knowledge of the ancients.
Before that instant in your life you were typing out full pathnames, like some fucking schmuck.
And from then on, everything changed, forever.
Absolutely. Bash was such a game changer with history too, and ctrl+r
You mean I can search recent history and get a recently used command?!?!?!?!?!