The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Kind of off topic, but after an obscene amount of effort I found the majic words to make an Intel 7265 wifi work with current linux distros.

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mitigations=off pcie_port_pm=off"
 
Because dei means 2 different things effectively depending on where you are politically. On the right, it means choosing to promote some races, basically everything but white straight people, disregard any meritocracy.

For people on the left, they think dei is good because it just helps black people and gay people. So they think people that are against dei hate black people and gay people.
These are the same thing and this is a false dichotomy. And you can't "just" help black and gay people without it being at someone else's expense.

Which leads me to ask: Why the fuck do people use wayland? It seems to be nothing but bugs and issues. There has to be some reason everyone is forcing people to switch to it, right? What does it offer over x11?
Wayland has spotty HDR support, a boat load of security at the expense of convenience at the expense of security, the warm feeling you get by validating the hecking troonarinos, and corpo propaganda. What's not to love?

It tends to make things like multiple monitor set ups, easier. Especially if you have monitors with different refresh rates, and resolutions. It's something I have heard a lot of complaints about with xorg. It could be a skill issue from the people that complain about, but wayland makes it either automatic, or nearly automatic, like just adding a couple lines in the config of the window manager you are using. and you are done.
For the love of christ, please stop repeating this. It is materially false. I have multiple monitors on X11 (and now Xlibre) that work(ed) just fine with multiple resolutions and refresh rates. I only learned about this "issue" after I switched to linux with this setup so it's not even like I just happened to know about some workaround or something. Stop it.

And the security of xorg, isn't something the wayland people use as a reason xorg is bad.
They do this constantly, wtf are you talking about.

If you are implying something about tpm. I don't know. If anything Intel Management Engine is what I would worry about more, and amd psp.
Just how many layers of "fuck you" do all these corpos and govs need? CPU silicon, firmware, BIOS, OS, browser, not to mention the ISP. Genuinely, what the fuck.
I'm fully aware of the IME/PSP situation but however pozzed those are is irrelevant because the answer to Hal's question is "as many as possible". Secure boot will be the hardware control that the niggercattle can see and accept because it's "legal" or you can unlock it "just like my iphone" after provide a one year old proof of purchase and serial number to Asus. In reality this will be hard to impossible and without hardware attestation you won't be able to do anything useful but those are details for nerds.

They're already making this a requirement for battlefield 6 to "stop cheaters" (spoiler: it is not stoping the cheaters). This is to get people to enable secure boot so they get used to it. And so they can throw up scary messages if joe blow wants to turn it off. They will use this next to try and stop piracy. We already have widevine and HDCP just wait until niggerflix and the rangs of power require hardware attestation.

More reason to hate SecureBoot it seems, if what you are saying is correct then that vindicates all the people that hated it back when it came out. Feels like most Linux users nowadays have the consensus that this was just FOSS cultism and that enrolling your own keys is easy and works fine.
To be clear the brazilian gov't hasn't suggested that specifically yet but I suspect that is merely because they're technically illiterate. Sadly there's no prizes for being right about secure boot.
 
Waylands rigid design will consequentially position it on the one end of the security horseshoe. Once it inevitably grows to the same size as Xorg (this says nothing about feature completeness) it will resemble chinkshit tofu dreg, much the way the old pre-fork Xorg is painted. In addition, harder to solve one security hole without opening several others, ease of discovery varying.
 
Waylands rigid design will consequentially position it on the one end of the security horseshoe. Once it inevitably grows to the same size as Xorg (this says nothing about feature completeness) it will resemble chinkshit tofu dreg, much the way the old pre-fork Xorg is painted. In addition, harder to solve one security hole without opening several others, ease of discovery varying.
Wayland is destined to be an unmanageable mess even greater then they claim X11 is.
 
I've got one for you: Why does everyone in security agree that if your attacker has physical access that you're cooked but then turn around and spend all this effort trying to solve the "evil maid attack" by implementing secure boot/pluton/etc.?
It provides some limited degree of security for corporate laptops that are being taken on visits from the American empire, to less sophisticated but semi-free countries that might otherwise crack them for secrets, in that to get access to data would typically require them to be left powered up and unattended. That's the sole 'positive' goal. Anything else, is just security theatre to try and trick free people into thinking that these (crap) 'protections' will protect them, when they've all been backdoored by the NSA.
What exactly prevents Linux from having a sensible windowing system?
Failure to adopt the gospel of Plan 9 from Bell Labs, which correctly recognized that using networking to shunt windows around was Bad, but not because you should use some aborted travesty like Windows 1.01 or Wayland. Everything on your screen should be Files, as is Right and Normal.
 
Failure to adopt the gospel of Plan 9 from Bell Labs, which correctly recognized that using networking to shunt windows around was Bad, but not because you should use some aborted travesty like Windows 1.01 or Wayland. Everything on your screen should be Files, as is Right and Normal.
Now I'm interested. It runs as x86/x64 code so that I don't need to whip out QEMU, right? (As in: I can just use VirtualBox)
 
These are the same thing and this is a false dichotomy. And you can't "just" help black and gay people without it being at someone else's expense.
Explain that to them.
They do this constantly, wtf are you talking about.
I left the word "only" out on accident. it's not something, only wayland shills use. It should be pretty obvious what I meant from the sentence directly following that.

For the love of christ, please stop repeating this. It is materially false
repeating that I've heard people complain about this? I have heard them complain about it.

Are you saying multiple monitors, with different refresh rates, and resolution were just set up for you automatically on x11? Or did you not actually read what I said, and assume I said it doesn't work at all?
 
Now I'm interested. It runs as x86/x64 code so that I don't need to whip out QEMU, right? (As in: I can just use VirtualBox)
It's been a while since I've played with it, but yes, amd64 or ARM (as long as it's Raspberry Pi) should be good to go. Don't let the 'notes' on the latest 'release' (on April 1) of 9front put you off.
1756969939908.webp
 
I've got one for you: Why does everyone in security agree that if your attacker has physical access that you're cooked but then turn around and spend all this effort trying to solve the "evil maid attack" by implementing secure boot/pluton/etc.?
Its the jews/corpos. Like how it is beneficial for you or I to practice defense in depth, it is to their benefit to practice corruption in depth. If you have ever been to any cybersecurity conference you will know very well that it is a corporate circle jerk where finance, military, oil and pharma grifters endlessly suck each other off about these "trusted computing" features. Its all cancer all the way down.

As for 'why Libreboot', because I simply do not trust anyone enough to leave it there. Closed source = backdoor is my assumption, and vPRO/IME absolutely can be accessed remotely, just because no one has exploited it remotely yet (as far as we know) does not mean it can't be done. Not that there are not other firmware-tier vectors of attack, mind you, but just cause you have a cracked window does not mean you should leave your front door ajar.
 
Are you saying multiple monitors, with different refresh rates, and resolution were just set up for you automatically on x11?
YES! I installed artix years ago and I had multiple monitors with different resolutions and refresh rates and it just worked.
 
Yo guys is there like even need for grub if you only use like 2 oses and have UEFI cuz i only see it that is really necessary in like legacy bios scenario
Maybe if you need to pass specific kernel parameters at boot (e.g. for booting into encrypted root)? I'm not sure if you can do it with pure UEFI, I know I set it in GRUB settings.

Also I have a question of my own, how do TTYs identify themselves as such? I'm thinking about building a small arduino-based terminal with a little screen and keyboard that I could use to access my server (I don't want to keep a bigass screen and keyboard for the few rare times I need root, not to mention it has no GPU..., also I think it could be an interesting project), but I'm not sure how I'd make the computer just send terminal stuff to the arduino at boot. I know that once I unlocked the rootfs I can just run stty, but that would not help in the above given scenario, for example. Maybe I will content myself with unlocking the rootfs 'blind', and gaining access after that point.
 
YES! I installed artix years ago and I had multiple monitors with different resolutions and refresh rates and it just worked.

I wonder why they spent all the effort to write this, for something that you don't need to do?

or this one.


and this.
and this

this guy should be ashamed of himself for spreading misinformation. How dare he act like he doesn't know how multiple monitors on x11 works.


or these people


I can't believe the lengths these wayland shills will go to, to spread their misinformation, pretending to be random people over years, that didn't know how to get multiple monitors properly working on x11.

Yo guys is there like even need for grub if you only use like 2 oses and have UEFI cuz i only see it that is really necessary in like legacy bios scenario
It does make it convenient. At least on some uefi's. Without it have to catch it between the very first scree, and when the grub menu starts to get to the boot menu from the uefi. Grub just alwasys shows the menu. So I can set the time out longer, or disable the timeout. So I don't have to sit there and watch, to catch it in time.

You technically don't need grub, but it's nice to have.
 
That sure is a lot of shit but at the end of the day this all boils down to "don't believe your lying eyes".

Looking through these links, some of them are ancient (decade+), some of them seem to be nvidia-specific troubles, the one from freedesktop can be thrown out due to wayland trannies, and finally from a few of your own links:

https://wiki.gentoo.org/wiki/Xorg/Multiple_monitors (literally the first thing on the page, at the top, in a highlighted information bubble):
"Important
Anything passing for a modern Xorg has autoconfiguration and RandR extension which means that it should just work"

https://unix.stackexchange.com/questions/712575/stackexchange-is-for-niggers (first line in the first and only answer)
"You don't usually need to manually play with xorg.conf anymore. Even an empty xorg.conf will often get it right"
 
Maybe if you need to pass specific kernel parameters at boot (e.g. for booting into encrypted root)?
You can do that with a unified kernel image. Really easy with dracut. Just needs something like this in /etc/dracut.conf.d/

Code:
uefi=yes
kernel_cmdline="cryptroot=UUID=...  "
 
You can do that with a unified kernel image. Really easy with dracut. Just needs something like this in /etc/dracut.conf.d/

Code:
uefi=yes
kernel_cmdline="cryptroot=UUID=...  "
yea i have excatly this but at the same time use systemd so its still niggerlicious
 
Man I'm getting fucking filtered HARD by Gentoo (:_(, second try installing it and at least I get to login, but root is mounted as read only for some reason. I guess my setup is probably fairly nonstandard, but I just know I'd have it installed in under an hour on arch. I think that instead of trying to set it all up at once, I'm gonna try to just get the bare minimum working, and then build the system up from there. At least I felt I understood more on this iteration. Third times the charm.
 
Back
Top Bottom