1641
Some heroes don't wear capes
(lemmy.dbzer0.com)
Shoutout to screenshot tools
Way back in the olde tymes, I was having trouble with the NIC driver in my Linux install. I posted a question about it on USENET, and got a reply from the guy who wrote the drivers. He asked for some info about the card, then updated the driver to support it.
Damn... now that's a wholesome moment 🥹.
There used to be a lot of cards based on same or similar chips, but with small differences. That made little changes to drivers common. It's a bit like LCD modules or audio chipset quirks. One driver with tons of little differences depending on what each manufacturer decided to do differently.
Yeah, I know, that's why the kernel with the drivers is not more than 150MB. Otherwise, you'd have the Windows situation where driverpacks compressed with 7z (LZMA2, solid archive, 273 word dictionary size and 2GB decompression memory, which requires about 128GB of RAM to compress) take about 30GB.
You have to pack the driver from each manufacturer because of signatures, even though they might even be the same with other drivers in the pack... but, REV differs and oh well, the driver installer doesn't recognize that driver as a valid one for that device.
load more comments
(2 replies)
load more comments
(1 replies)
load more comments
(1 replies)
For all we know, he does wear a cape.
I wish capes were socially acceptable to wear again
And get stuck in turbines and shit?
Break away fasteners are a thing now. Line it with some Kevlar fibre and some good thermal insulation/fire resistance and you have an amazing utility device.
In public, it billows behind you, making you look dashing and heroic. When the shit hits the fan, instant bullet resistant cover for civilians. A way to shield them from the heat of a fire, or a small explosion. You could even use it offensively to tangle or deceive an opponent!
There is absolutely no way in hell a bullet-proof cape is billowing in the wind.
It won't stop a direct shot, but it would help against ricochet and shrapnel.
Back during the Napoleonic wars, silk underlayers were highly sought after. They could limit the damage a musket ball could do.
A spider silk based cape could definitely help projectile damage, while still being able to billow. The challenge would be making it fire and heat proof as well.
load more comments
(1 replies)
You should talk to that guy who made bulletproof Kimonos for Steven Seagal
load more comments
(6 replies)
lucky for me I don't often interact with things like that
load more comments
(1 replies)
I'd settle for a cloak. A nice leather, or heavy woollen cloak would be amazing for being outside on cold evenings.
Unfortunately, they are still seen as dark and 'edgy'. Moreso even than a trenchcoat. ☹️
Stop giving so many fucks about what other people think about your fashion. You do you, fam.
load more comments
(1 replies)
load more comments
(3 replies)
just wear them already
Be the change you want to see.
load more comments
(2 replies)
Shoutout to this guy for maintaining my mainboards temperature sensors and pwn fan headers: https://github.com/Fred78290/nct6687d
Without this and https://github.com/codifryed/coolercontrol my PC was either a jet engine from the sounds or a nuclear reactor from heat constipation.
Fred78290 is the man. Much better than Fred78920
Some dude wrote a driver for the temp sensors on my motherboard... Then quit maintining it because people were being shitty
https://github.com/a1wong/it87
DRIVER REMOVAL NOTICE ===================== I have been unable to meet support demands for this driver, resulting in unpleasant experience and frustration for everyone involved. Consequently, the driver will be removed from github, effective August 1, 2018. Interested parties are encouraged to clone the driver before that time and to start maintaining it on their own.
load more comments
(3 replies)
load more comments
(5 replies)
A lot of Linux drivers are like this - just one or two people maintaining them. They usually eventually mainline the driver rather than having a separate Git repo though.
It's mind boggling just thinking that things like this depend on the effort of one or two guys... while on the other hand, it's not so uncommon that a team of engineers and developers fails to deliver a working (mostly) bugfree product.
I think management is who is responsible for the shitty decisions, as always... and, in general, just holding the team back.
What's the deal with Nebraska? Are people from there like really polite and helpful?
There's nothing to do in Nebraska except drink and maintain Linux drivers
load more comments
(1 replies)
It's just a random location that was chosen for the joke, it's in the middle of nowhere
load more comments
(5 replies)
The thing with drivers is that the hardware they're written for doesn't really change. A particular network card is always going to behave the same way. Once the driver works well, it's pretty much complete, and the only changes that are needed are bug fixes, updates to handle new firmware, or adjustments if the kernel changes some implementation detail of how drivers are used. There could be months or years between updates to the driver.
Some manufacturers have great first-party Linux support. Intel is a good example - they contribute a lot of code to the kernel, and their drivers are maintained by employees.
load more comments
(5 replies)
There's such a lot of those heroes! I have some weird USB WiFi thing and there's someone maintaining a driver for it!
Yo I'm looking for something like that right now for Linux, what's the name of it??
load more comments
(1 replies)
Had some problems while trying to compile and install a WiFi driver for the first time. Managed to find the email of the driver's creator and sent them a message. They responded a few hours later with incredibly helpful guidance, walking me through the process and enabling me to get it working, all while gaining valuable insights....
This is the way
Its these kind of people that give me hope
To be honest, yes. In general, not just tech or Linux related stuff. You look at humanity and what it has come down to, and then you notice these people... and hope fills your heart again.
The vast majority of my open source projects, I'm the only user. I release it open source because back in the day, GitHub only allowed open source projects if you want to use it.
But another reason is the hope that someone will find it helpful. If not the project itself but maybe the code.
I have one project that has a significant following and honestly it's sometimes very scary because I might not want to keep it updated because of my own interests changing.
load more comments
(1 replies)
load more comments
(1 replies)
This is the link to the GitHub repository h̶t̶t̶p̶s̶:̶/̶/̶g̶i̶t̶h̶u̶b̶.̶c̶o̶m̶/̶m̶o̶r̶r̶o̶w̶n̶r̶/̶8̶8̶1̶2̶a̶u̶-̶2̶0̶2̶1̶0̶6̶2̶9̶ Give them a star.
(I also looked for a donation link, but couldn't find one.)
And shoutout for this one too: https://github.com/tomaspinho/rtl8821ce
Otherwise I wouldn't have a functional WiFi card either.
Send your thanks directly to the maintainer (preferably email/mastadon/twitter/etc, not a ticket)! Open source maintainers don't get a lot of positive direct feedback.
And if you have some coins to spare, don’t hesitate to donate 😊 it’s hard spending time for no money in this world right now.
load more comments
(1 replies)
One of the best parts about Linux. So much is open source which means your 20 year old hardware still likely has support.
Unfortunately, the RTL8812AU isn't 20 year old hardware (then it might get a pass) - it's current gen stuff
Shoutout to https://github.com/clnhub/rtl8192eu-linux for monitor mode and packet injection <3
load more comments
(2 replies)
Oh hey I have the same wifi card series (little usb dongle thingy). I use the aircrack drivers when i use it. https://github.com/aircrack-ng/rtl8812au
Shoutout to whoever maintained my wifi drivers before i switched to ethernet (i forgot who they are lol)
view more: next ›
this post was submitted on 28 Jan 2024
1641 points (99.1% liked)
linuxmemes
21281 readers
263 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
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 fork-bomb your computer.
founded 1 year ago
MODERATORS