PaX

joined 2 years ago
[–] [email protected] 7 points 7 months ago* (last edited 7 months ago)

The flash memory controller in your e-reader hasn't swapped out any of the blocks that store your copy of Capital due to overuse by multiple reads or writes? Interesting...

It says here that your e-reader's operating system has been up for 3 months, has 1 GB of free memory and yet your copy of Blackshirts and Reds isn't even cached... hmmm...

The access time recorded on your copy of Imperialism is the same as the creation time... very interesting

[–] [email protected] 32 points 7 months ago* (last edited 7 months ago) (2 children)

guess i won't be seeing this, even just to laugh at how dumb it is

pirate-jammincat-vibingpirate-jammin

[–] [email protected] 7 points 7 months ago* (last edited 7 months ago)

Genuinely really pretty photo

hex-moon

NOW

TAKING

APPLICATIONS

dafoe-horror

[–] [email protected] 1 points 7 months ago (4 children)
[–] [email protected] 4 points 7 months ago* (last edited 7 months ago)

I will award a class B network to anyone who can come up with a new internet protocol, simpler than IPv6 and it has to be called BEANS somehow

I will make it a class A if you can come up with a more readable addressing format than IPv6's 128-bit CAFEBABE nonsense

Don't do sleep deprivation or you will end up badposting like me

[–] [email protected] 9 points 7 months ago* (last edited 7 months ago) (2 children)

STOP DOING NAT

SYSTEMS PARTICIPATING IN THE INTERNET WERE NOT SUPPOSED TO BE UNREACHABLE OUTSIDE OF THEIR LOCAL SUBNET

Wanted to do it anyway, as a bit? We had a tool for that: it was called a "FIREWALL"

YEARS OF HEADER MANGLING yet NO REAL WORLD USE FOUND for going beyond variable length globally routable subnet masking

"Yes, you can reach my system at 134.84.167.99 but only through port 483. Oh, you want to play a game together? Let me forward a port (??) or we can use STUN to traverse my NAT (????)" - statements made up by the utterly deranged

LOOK at what network ""engineers"" have been demanding your "respect" for all this time, with all the routers & physical networking layers we built for them (These are REAL techniques, devised by REAL network engineers)

iptables -t mangle -A POSTROUTING -o eth0 -j TTL --ttl-set $(cat /proc/sys/net/ipv4/ip_default_ttl)

iptables -A NO_PROXY -t nat -d 0.0.0.0/8 -j ACCEPT

[–] [email protected] 11 points 7 months ago

nineteeneightyfourspeech-side-l-1There was no downtime. It was solely on your end.speech-side-l-2

1984

[–] [email protected] 12 points 7 months ago* (last edited 7 months ago)

Yeah, the safe path is to nuke the machine and consider all passwords compromised

What do you mean by "without switching from home network to mesh network"? What network was the system connected to? Also if you had a transfer running some FTP clients will open multiple connections to the server which could explain your "7 connections terminated" message. Can you check the FTP server logs to see what exactly happened?

[–] [email protected] 11 points 7 months ago

Sleep deprived and couldn't see the eclipse cuz I couldn't find anything strong enough to attenuate the light from the sun enough to stare at it

And Hexbear was down too

:(

[–] [email protected] 27 points 7 months ago* (last edited 7 months ago) (2 children)

yea, agony-deep even

Hard to think of any worse ways to die than rabies

We should bring back public criticism sessions for antivaxxers

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago) (1 children)

I don't have a fixed address due to my service on an SSN. I can't tell you my exact SSN for opsec reasons but I can say I'm on the last Shchuka-B nuclear attack submarine flying the Soviet naval ensign somewhere under the Atlantic ocean

51
submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]
 

capitalizing "GUN" as though it mattered looked rather like hoplophobia

Link: https://news.ycombinator.com/item?id=24749158

 

cross-posted from: https://hexbear.net/post/1747735

CPU-posting on main

MTI = MIPS Technologies (company that made MIPS (Microprocessor without Interlocked Pipeline Stages) processors, they make RISC-V processors now lmao)

At the time when the MIPS R10000, known as the "T5" while in development, was being designed, MTI had made a name for themselves as designers of high-performance computer microprocessors along the lines of the then-new philosophy of reduced instruction set computing (RISC). Actually, their R2000 design was the first commercially-available RISC microprocessor. By the time the T5 was being designed, they were no longer alone in the RISC microprocessor market. Several companies, including IBM and Motorola (joined together in the AIM alliance which produced PowerPC), DEC (who designed the Alpha line of RISC microprocessors after MTI owned them in the 80s when their radically simpler chips were performing better than VAXen), and Sun Microsystems (who were making the SPARC line of microprocessors) were now marketing RISC microprocessors. Not just even marketing but beating MTI in the market they had created. After trying and failing to develop their own complete computer systems alongside their chips, they were having financial difficulties until Silicon Graphics acquired MTI to secure availability of MIPS microprocessors for their famous ("it's a Unix system, I know this!") MIPS-based workstations and servers. Although their new (in 1993) R4000 and R4400 designs performed well compared to their contemporaries, they were quickly being made obsolete by MTI's competitor's new offerings and they were left with a problem:

The MIPS R4000 and the R4400, which is essentially an R4000 with bigger on-die caches, were more or less just an architectural evolution from the R2000. The R4000 made its performance in much the same way as the R2000 did, the classic RISC design process mantra: "let's make it simpler" and thus be able to run it faster. In particular, what this means for the R4000, and what is a key difference from its predecessors and its contemporaries, is a technique called superpipelining. In an instruction pipeline, the maximum speed at which your processor can issue instructions is set by the pipeline stage which takes the longest to complete. Superpipelining is one way of addressing this problem: you can subdivide each pipeline stage into 2 simpler pipeline stages that individually complete faster and thus be able to clock your chip faster without problems. However, this has its limits. Eventually, it becomes impossible to further "deepen" the pipeline like this or clock the processor faster in general without other problems. This is why MTI's competitors opted for the analogous superscalar approach: you can duplicate functional units of your processor and have multiple instructions "in flight" at the same time and usually this also involves multiple pipelines. At the time MTI thought this approach would result in more consistently higher performance (not to mention save die space) but were quickly proven wrong when their competitor's superscalar (and often with other architectural tricks) chips were outperforming the R4000 in spite of MTI's fabrication partners constantly improving their process and releasing chips that ran at higher and higher speeds.

Enter the MIPS R8000 (die not pictured here) in 1994, a weird and expensive 6-chip 4-way superscalar design meant for the high-end microprocessor market while the next-generation T5 (which would become the MIPS R10000, as mentioned earlier) was under development. It didn't sell well because of its high price and the fact that its integer performance, important for general-purpose computing applications, was lacking compared to the 200-MHz R4400 that was being sold by then. It did, however, have impressive floating-point performance, which landed many R8000-based systems in the TOP500 supercomputer list for a time. But this design could never be the high-performance and general-purpose processor MTI needed to compete with their competitor's offerings...

Introduced in 1996, the MIPS R10000 (die IS pictured here) was a significant departure from the architecture of the R4000 (which more or less was directly derived from the first research done at Stanford University where MIPS was initially created over a decade earlier). Dropping the superpipeline approach, the R10000 is a 4-way superscalar processor even capable of executing instructions out of order! Another big change is that it has a branch predictor and speculatively executes instructions after a branch as opposed to the R4000, which used the classic MIPS "branch delay slot" technique to schedule one more instruction in the pipeline after a branch and then stall lol (they should have added even more delay slots, caring about binary compatibility is liberalism). It's hard to find benchmarks for something this old but this design performed at least several times faster than an R4400 at about the same clock speed!

If you like my CPU posting and want me to post more in the future let me know

Also ask me any questions if you want too and I'll try to answer

 

CPU-posting on main

MTI = MIPS Technologies (company that made MIPS (Microprocessor without Interlocked Pipeline Stages) processors, they make RISC-V processors now lmao)

At the time when the MIPS R10000, known as the "T5" while in development, was being designed, MTI had made a name for themselves as designers of high-performance computer microprocessors along the lines of the then-new philosophy of reduced instruction set computing (RISC). Actually, their R2000 design was the first commercially-available RISC microprocessor. By the time the T5 was being designed, they were no longer alone in the RISC microprocessor market. Several companies, including IBM and Motorola (joined together in the AIM alliance which produced PowerPC), DEC (who designed the Alpha line of RISC microprocessors after MTI owned them in the 80s when their radically simpler chips were performing better than VAXen), and Sun Microsystems (who were making the SPARC line of microprocessors) were now marketing RISC microprocessors. Not just even marketing but beating MTI in the market they had created. After trying and failing to develop their own complete computer systems alongside their chips, they were having financial difficulties until Silicon Graphics acquired MTI to secure availability of MIPS microprocessors for their famous ("it's a Unix system, I know this!") MIPS-based workstations and servers. Although their new (in 1993) R4000 and R4400 designs performed well compared to their contemporaries, they were quickly being made obsolete by MTI's competitor's new offerings and they were left with a problem:

The MIPS R4000 and the R4400, which is essentially an R4000 with bigger on-die caches, were more or less just an architectural evolution from the R2000. The R4000 made its performance in much the same way as the R2000 did, the classic RISC design process mantra: "let's make it simpler" and thus be able to run it faster. In particular, what this means for the R4000, and what is a key difference from its predecessors and its contemporaries, is a technique called superpipelining. In an instruction pipeline, the maximum speed at which your processor can issue instructions is set by the pipeline stage which takes the longest to complete. Superpipelining is one way of addressing this problem: you can subdivide each pipeline stage into 2 simpler pipeline stages that individually complete faster and thus be able to clock your chip faster without problems. However, this has its limits. Eventually, it becomes impossible to further "deepen" the pipeline like this or clock the processor faster in general without other problems. This is why MTI's competitors opted for the analogous superscalar approach: you can duplicate functional units of your processor and have multiple instructions "in flight" at the same time and usually this also involves multiple pipelines. At the time MTI thought this approach would result in more consistently higher performance (not to mention save die space) but were quickly proven wrong when their competitor's superscalar (and often with other architectural tricks) chips were outperforming the R4000 in spite of MTI's fabrication partners constantly improving their process and releasing chips that ran at higher and higher speeds.

Enter the MIPS R8000 (die not pictured here) in 1994, a weird and expensive 6-chip 4-way superscalar design meant for the high-end microprocessor market while the next-generation T5 (which would become the MIPS R10000, as mentioned earlier) was under development. It didn't sell well because of its high price and the fact that its integer performance, important for general-purpose computing applications, was lacking compared to the 200-MHz R4400 that was being sold by then. It did, however, have impressive floating-point performance, which landed many R8000-based systems in the TOP500 supercomputer list for a time. But this design could never be the high-performance and general-purpose processor MTI needed to compete with their competitor's offerings...

Introduced in 1996, the MIPS R10000 (die IS pictured here) was a significant departure from the architecture of the R4000 (which more or less was directly derived from the first research done at Stanford University where MIPS was initially created over a decade earlier). Dropping the superpipeline approach, the R10000 is a 4-way superscalar processor even capable of executing instructions out of order! Another big change is that it has a branch predictor and speculatively executes instructions after a branch as opposed to the R4000, which used the classic MIPS "branch delay slot" technique to schedule one more instruction in the pipeline after a branch and then stall lol (they should have added even more delay slots, caring about binary compatibility is liberalism). It's hard to find benchmarks for something this old but this design performed at least several times faster than an R4400 at about the same clock speed!

If you like my CPU posting and want me to post more in the future let me know

Also ask me any questions if you want too and I'll try to answer

 

Spent like an hour trying to degrade the quality just right for that perfect haunted look lol

If you can do better than me please upload your take

 

No, that was just a bit

Gosha is too powerful of a being to suffer from scurvy

11
submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]
 

Is it actually possible to make any good money doing that or am I better off doing surveys or some shit for money on the side lol

 

Trying not to cry about the fish :(

Fish are so cool tbh

 

I don't mean to but I lost one of my best friends partially this way :(

It's hard to control sometimes

If I ever find someone who cares about communism/Unix/Plan 9/computer architecture (I see all these as deeply interconnected) as much as I do our power will be unstoppable

Edit: Thanks everyone for your replies and for sharing your experiences, it means a lot to me. I want to reply to everyone I just don't know what to say lol

1
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

It just works. No need to sift through dozens of config files and options and issue a hundred verbose commands just to get the system in a somewhat working state. All my laptop's buttons work correctly out of the box. And it didn't even come at the cost of sprawling complexity maintained by a patchwork of corpo patrons, underpaid code monkeys, and forum users. The system just fits together very well. The documentation is amazing too.

Easily my favorite Unix. If Linux was too complicated or barebones for you, give OpenBSD a try!

1
Based Yugopnik (hexbear.net)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

Communism is the movement to abolish ALL oppressive systems, including systems that oppress animals and nature itself.

view more: ‹ prev next ›