That’s when Unix (Mach kernel and FreeBSD) based OSX launched. It included command line and OOP development tools that really were a huge improvement over the previous OS 7-9.
I bought my first Mac a few years later 2003 because I needed a reliable laptop, there was no competition (anyone remember the Sony Viao?) in good laptops, unless you liked thinkpads with one nipple. Plus as a design student, I needed macromedia and Adobe products, and worked in my college’s computer lab managing Mac’s anyway.
I’ve done a 1PB sync between a pair of 8-node SAN clusters as one was being physically moved since it’d be faster to seed the data and start a delta sync rather than try to do it all over a 10Gb pipe. M
I think 16 terabytes? Might have been twelve. I was consolidating a bunch of old drives and data into a nas for a friend. He just didn’t have the time, between working and school and brought me all the hardware and said “go” lol.
As a disclaimer: I really like Wayland and use it as my daily driver for months now with KDE/Proton.
Now my answer, based on my best knowledge:
Because there is no real Wayland to implement, the base Wayland protocols are extremely bare bone and most of the heavy lifting is done by all the different wayland compositors like hyprland, proton, Mutter, weston, wlroots, gamescope so as a developer you don’t have one target to program against (X11) but lots of different wayland implementations and those are not always doing things the same way or providing the identical interfaces/API or have the same level of features.
On my system is at least one wayland only program that works absolutely fine when started in a wlroots environment but crashes (reproduceable on different systems) with a segmentation fault in Mutter or Proton.
I once abused an SMTP relay (my own) by emailing Novell a 400+ MB memory dump. Their FTP site kept timing out.
After all that, and them swearing they had to have it, the OS team said “Nope, we’re not going to look at it”. Guess how I feel about Novell after that?
Manually transferred about 7TBs to my new Rpi4 powered NAS. It took a couple of days because I was lazy and transferred 15 GBs at a time which slowed down the speed for some reason. It could handle small sub 1 GB files in half a minute otherwise.
Could the slowdown be down to HDDs that cache on a section of - I think it’s single layer? - and slowly rewrite that cache onto the denser (compound layer?) storage?
I synced to the BSV shitcoin which is 11+ terabytes. So large I had to turn on throwing away the rest of what I downloaded because it wouldn’t fit on all of the storage media I own. I feel sorry for the people running an archive node.
No wonder. That file is super slow to transfer for some reason. but wait till you get to /dev/urandom. That file hat TBs to transfer at whatever pipe you can throw at it…
/dev/random and other “files” in /dev are not really files, they are interfaces which van be used to interact with virtual or hardware devices. /dev/random spits out cryptographically secure random data. Another example is /dev/zero, which spits out only zero bytes.
Both are infinite.
Not all “files” in /dev are infinite, for example hard drives can (depending on which technology they use) be accessed under /dev/sda /dev/sdb and so on.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.