Ontopic Random Computer-Electronics Thread

fly said:
Having a really odd issue. Picked up a couple WD 8TB drives. After running a full test on the drive, and taping the 3.3v pins, I added it to the server. Now when I attempt to boot, the BIOS hangs with a message in the lower corner saying B2.

wtf
Click to expand...
You somehow get the BIOS set back to legacy instead of UEFI?
 
fly said:
Nothing in the BIOS changed.

edit:
WHOA, I'll be damned. I needed to format it NTFS for the system to boot.
Click to expand...

i bet it had a fucked MBR/GPT due to being an external drive that made the bios confused. By formatting you rewrote the MBR and now the bios understands its not a boot disk
 
  • Gravy
Reactions: Jehannum
Today in Linux: UMN deliberately submitted buggy/vulnerable code to the linux kernel for "research purposes", seeing if it would get merged in, and sure enough some of it did.

Kernel maintainers are livid and UMN is banned from submitting kernel code for the near future.

fosspost.org

Researchers Secretly Tried To Add Vulnerabilities To Linux Kernel, Ended Up Getting Banned

Researchers from the University of Minnesota secretly tried to add security vulnerabilities to Linux kernel, but they were caught and banned.
fosspost.org fosspost.org
 
  • Haha
Reactions: wetwillie
gee said:
Today in Linux: UMN deliberately submitted buggy/vulnerable code to the linux kernel for "research purposes", seeing if it would get merged in, and sure enough some of it did.

Kernel maintainers are livid and UMN is banned from submitting kernel code for the near future.

fosspost.org

Researchers Secretly Tried To Add Vulnerabilities To Linux Kernel, Ended Up Getting Banned

Researchers from the University of Minnesota secretly tried to add security vulnerabilities to Linux kernel, but they were caught and banned.
fosspost.org fosspost.org
Click to expand...
eeeek. No matter which side you take, that's a HUGE shit sandwich.
 
fly said:
Does it? It's a fuckton of people trying to maintain millions of lines of code, for free. I think it's probably more likely that they're extremely busy and with extremely limited amounts of time.
Click to expand...
A lot of kernel maintainers are paid very well to do that job.

Whether the code is free or not is immaterial to the situation.
 
I've got code in the kernel somewhere submitted >10 years ago, in an ethernet device driver for a random ARM processor that wasn't properly resetting the PHY if someone unplugged and replugged the ethernet cable.

I don't expect the Linux maintainers to know exactly what I'm doing, read through the processor hardware manual and see what registers I was twiddling and say "yep, that looks right"... they took it, eyeballed it and said "yeah, seems OK", fixed the brackets/spacing/tabbing/whatever because I'm sure I fucked that part up, and submitted it to the kernel.
 
  • Love
  • Gravy
Reactions: Jehannum and fly
the open source community largely relies on good faith. If there were lots of people submitting intentionally "bad" shit, it wouldnt work.

Then again... somehow wikipedia manages to function despite being pretty much constantly under attack by liars.
 
Domon said:
the open source community largely relies on good faith. If there were lots of people submitting intentionally "bad" shit, it wouldnt work.

Then again... somehow wikipedia manages to function despite being pretty much constantly under attack by liars.
Click to expand...
That's obviously a terrible model. PHP nearly averted getting fucked similarly.
 
You must log in or register to reply here.
Top Bottom
Back