as a sysadmin this so much.
-
-
@puppygirlhornypost2 Even complete novices. You don't have to understand the message. You just need to be able to type it into a search engine and see how other ppl solved it.
Sometimes I think this is WHY they removed the messages. Enshittifucation of (or just feeling out of control over) search and the threat of malicious hits leading users to download malware.
-
@MekahimeAkari @puppygirlhornypost2 It means "installing preloaded junkware".
-
@MisuseCase @puppygirlhornypost2 @bonaventuresoft Not if the message is not sent to a channel that belongs to the attacker (or someone other than the legitimate user). This kind of wrong thinking is endemic, that just because you're not supposed to output php or python errors in the http data stream, this also means you're not supposed to show error messages on the user's monitor.
-
@[email protected] @[email protected] @[email protected] damn we should tell the pfsense team they aren’t supposed to use printf debugging in regards to cryptographic secrets related to their plagiarized wireguard implementation that lost them write access to FreeBSD’s repository…
-
@[email protected] @[email protected] @[email protected] entire thing is insane to me so many levels of "how did this happen". It all started when the guy who made wireguard told pfsense he’d love to help and they hired two shady devs instead that plagiarized GPL code from the Linux implementation… god I laugh every fucking time what a genuine shitshow
-
@puppygirlhornypost2 i was so fucking mad when i first BSOD'd a windows 8 machine and saw what they'd done to the screen. Really, a fucking emoticon instead of actual useful fucking info?!
-
Jernej Simončič �replied to Wyatt (🏳️⚧️♀?) on last edited by
@wyatt8740 @puppygirlhornypost2 Ever seen a Windows NT 3.1 BSOD?
-
Rairii :win3_progman: :win3:replied to Jernej Simončič � on last edited by@jernej__s @wyatt8740 @puppygirlhornypost2 ah yes, NT 3.1, when x86 still had a register dump on bugcheck
they got rid of that pretty fast, probably because it wasn't really useful (other architectures kept the register dump though) -
@puppygirlhornypost2 Also, "something went wrong; contact your sysadmin" is quite infuriating when you're the sysadmin
-
Wyatt (🏳️⚧️♀?)replied to Jernej Simončič � on last edited by
@jernej__s @puppygirlhornypost2 no. But it's amazing.
Are all kernels debuggable over a serial port, or just NT 3.1?
-
Jernej Simončič �replied to Wyatt (🏳️⚧️♀?) on last edited by
@wyatt8740 @puppygirlhornypost2 They all are, though nowadays you have to set them up first.
-
NKTSecurityreplied to hellhound gayming on last edited by
@pup @puppygirlhornypost2 Windows S mode literally has "visit something else" and "restart your pc" as the entire compliment of "why won't my website work/load?" 'solutions'.
-
P [email protected] shared this topic on
-
@puppygirlhornypost2 I think we need a 3rd option where you get an error message and its like "damn shit is real fucked right now lmao".
-
P [email protected] shared this topic on
-
@[email protected] that’s my error messages
-
Just this week I had to diagnose a program that kept failing to perform a DNS lookup. At least that was the error message. What it wasn't telling me was the thread responsible for performing the network communication was throwing an exception before it ever got to the lookup.
-
@[email protected] @[email protected] yeah. ReactOS development is purely around serial console debugging
-
Amberreplied to Rairii :win3_progman: :win3: last edited by
@[email protected] @[email protected] @[email protected] yeah it’s not particularly useful because of how system memory can change between computers. The registers are typically specific to a machine (modern windbg will warn you about this)
