I was aware that their portable devices were using ARM in their SoCs, but not their desktop/laptop machines.
MacIntosh using ARM? So, they are designing their own chips now... The M1 and more? Hmm...
OS/software wise I guess it's not a jump for them since they have the experience of using Android with ARM, which is Unix after all. And since their desk/laptops are Unix based, it actually makes sense for them. less platforms to maintain.
Which means they have now become much more vertically integrated. Good luck figuring out how it works now.
Who knows? We might go back to buying Macs as low cost alternatives to single board computers for prototyping RTOS.
Last edited:
Apple was using Intel CPUs a few generations ago.
Then they shifted to ARM.
They all have their pros and cons.
Unix had its origins in the software used by AT&T to control the traffic and routing on their long distance network, a call from NY to LA could go via Chicago, or Atlanta or Dallas, depending on congestion.
Then they shifted to ARM.
They all have their pros and cons.
Unix had its origins in the software used by AT&T to control the traffic and routing on their long distance network, a call from NY to LA could go via Chicago, or Atlanta or Dallas, depending on congestion.
Last edited:
I don't think UNIX was ever meant for phone traffic control. I think it was always a multi-user O/S(Successor to Multics) By mainly Kernighan, Ritche(RIP), & Thompson. Originally run on PDP's I believe. I used UNIX in 77 or 78 at university on a "big" PDP 11/70. I've used it almost exclusively (or a variant) ever since. Also used their "Software Tools" book in one college course. A brilliant group of 3 that are very underrated. Where would the world be without C, UNIX, ... I would have delighted having lunch with any of them.
They had a control center in the near mid west, basically west of NY, but East of Chicago, big screens, saw ads in American magazines when I was in school.
The 'pipeline', as used in UNIX, used to to divert traffic from one node to another without disturbing the rest of the circuit, comes from that, IIRC.
I may be wrong on that...
The 'pipeline', as used in UNIX, used to to divert traffic from one node to another without disturbing the rest of the circuit, comes from that, IIRC.
I may be wrong on that...
K&R and Thompson are NOT underrated... they are the "root" in my work. I have their books on C and Unix.
You are right. They developed Unix to run on PDPs. Then they need a programming language... ergo, C. After that they figured they needed a means to communicate and send data to each other, the team expanded, people jumped on the bandwagon... so they came up with RFCs and slowly, IP, UDP, TCP, etc.... I'm not quite sure about the history of the data link proper, there were many until the late 90s when everyone sort of settled on ATM for metro and intermetro and Ethernet for LANs.
The World was awesome until some bastards wrote the first spam. (*)
+++
I used RSTS-11 and later RSTS-E in my first forays into the PDP-11/70. Remember the DecWriter terminals?
Then you you got Internetworking with TCP/IP by Douglas E. Commer...
..and my much doggeared and abused copy of Advanced Programming in the UNIX environment by Richard Stevens..
...let's not forget Interconnections by Radia Perlman.
Or A Discipline of Programming by Edsger W. Dijkstra.
Do you recall the data in the PDP11 was left shifted when transferred to a VAX? I mean, WTF were they thinking?
Anyhow, those were the seminal books. I don't consider Stroupstrup's book on C++ as important -even if I have the first edition. Or Lipmman's otherwise very fine C++ Primer.
The only book that I've bought since the mid 90s that was truly important is Computer Architecture: A Quantitative Approach by John Hennessy and David Patterson. A book, that when you ready to understand why computers work, from an engineering perspective (**), is incredibly satisfying. If you can reach from CE to Dikjstra then you got a complete background in the field.
Yeah, when I hear people say "learn to code" it just shows they fundamental understanding of the art and science of computer and software engineering.
Oh well.
As my T-Shirt says: "I am root, fear me"... it's my favorite T-shirt to wear when I deal with IT.
Jeez... often time I wish I had been born a few years earlier... can you imagine being at Bell Labs with those guys? It's so sad that our current MBAs have killed the Research Centers.
(*) I had my own domain name and mail server by the mid 90s. So, at work, I set up my mail client to also load my personal email from my mail server. Things went fine until one morning at work in late 2000 when I loaded my email (not downloaded) and a porno spam suddenly filled my 20" Sony display! Sh!!t!!!
(**) As opposed to a theoretical mathematician's Turing Machine sort of look.
Last edited:
You are wrong. Unix was NOT developed for voice traffic control.
In 2006 I bought a new hard drive and needed to install Windows.
So plugged in new hard drive.
Installed Windows and it was easy and went fine.
Then tried to copy back up hard disc to new Windows disc.
In its wisdom Windows had decided to format both drives !
FFS !
I managed to dig out some DVD's with stuff on it but some of it wasn't on DVD so lost forever.
So now if I reinstall Windows I always disconnect back up drive.
So plugged in new hard drive.
Installed Windows and it was easy and went fine.
Then tried to copy back up hard disc to new Windows disc.
In its wisdom Windows had decided to format both drives !
FFS !
I managed to dig out some DVD's with stuff on it but some of it wasn't on DVD so lost forever.
So now if I reinstall Windows I always disconnect back up drive.
I used to physically disconnect every drive except the one I wanted to install to because it bit me like that once, too.
These days, it's a little more well behaved.
These days, it's a little more well behaved.
Oh man, to have been at Bell during those years. Yeah, I hear you. Purdue EE(78-ish) was one of the earlier sites for the UNIX/PDP's and I do remember the DECwriters. We mainly had LEAR terminals I think it was. DECwriters used paper, $$$'s. I'd taken some CS classes on the CDC the CS dept used and had been exposed to about a dozen languages by the time I saw C. I fell for it completely. Simple, close to the metal, and yet powerful. I mean how many people really understand the ++/-- shorthands are there because the PDP hardware had instructions for it. And you forgot LaTex, did my thesis using it. I still use C even for most my own projects as well as my product. As to spam, filters, multiple filters. I have so many methods of rejecting spam it gets confusing even to me and I wrote it. Mainly I reject based on IP address/domain name of sender. Works fairly well. Unfortunately, several large domains have issues with their DNS configs which causes even more tweaks. My CC company actually had A's IP address point to B and B's pointed to A. They fixed it after I pointed it out to them.
that AMD 5900X is serious device.
My 11700k shows only 60% CPU mark(CPU only) performance compares to your 5900X.
Attachments
I didn't forget LaTeX... is was big up until the 90s, I've only seen it since in one specific research center where the people are, well, researchers. In fact, in the last two years I had to write some design docs using LaTeX.... turns out there's a plug in for Eclipse ( the lab is too cheap to buy Word ).
But there are so many things, that if I were to post even a significant part of it, we'd reach the limits of post size quickly. So many tools... to think of the time that I spent mastering so many things that today are obsolete and only interesting from a historical perspective.
My many page resume is curated by yours truly so it won't look like a museum: " Look, what year was that tool used? Hey, let's look at Tony's resume!"
I have my domain hosted and they provide a mail server, so I have some home made filters (nothing from Microsoft) plus I've got good at it. And I must say that the main Telcos are doing a good job of filtering porno nowadays.
Story time.
In the mid 90s I was working at a very well known research center. One day, one of the researchers quit. It turns out he had a grant to study Internet traffic and stumbled into the idea of using a porno picture server to create traffic. The thing is he realized he could make money off it, so he got a T1 to his home where he hosted the front end, installed connections to the bank, and then used the lab's extensive Internet connectivity to serve the pictures from the servers in his office.
He got "caught" (more on that anon) when they were updating the LAN to 100baseT. One of the network admins saw some interesting traffic, tooks a snapshot and decoded the jpeg. Ooops!
Now, get this... at the time is was not against the law to do that, he was truly ahead of the curve, he was doing the research he was funded for.
But, when they realized he was making money off "using" the Lab's network (mind you, the servers were paid off his grant money) he was caught in an ethical conundrum, they wouldn't fire him but he had to shut down the schema.
He quit instead, opting for the "porno money".
I spoke with is office mate about it... he told me: "yeah, around 3PM every day his machines started to make a lot of disc noise..."
Solaris, naturally.
Last edited:
It seems new motherboards have a MAC address, so that is one way the people at Microsoft, and others can verify your software license, for example when you swap hard disks or CPUs.
Been there since Socket 775 days in HP and Lenovo, for example, you can see it in the BIOS, not alterable.
Been there since Socket 775 days in HP and Lenovo, for example, you can see it in the BIOS, not alterable.
MAC Address: Media Access Control Address.
The "motherboard" per se has NO MAC addresses of any kind. Network interface controllers (NIC) have one MAC address each -it is unique to the NIC. If the NIC is built into the motherboard then, it would seem like the motherboard has it, but in reality the NIC is the peripheral that carries the MAC address.
It has been like that since, oh.... the first time they put an ethernet adaptor on a motherboard. Today it is ubiquitous to have more than one: ethernet plus 802.11 wireless.
It could be used an a unique set of identifiers for the motherboard, yes, since it is highly unlikely that the motherboard would operate with failed peripherals.
The MAC Address is designed to be used by the data link layer to identify the hardware, just as the IP address is used to identify the IP connection. The MAC address identifies the manufacturer and additional information.
Back in the early 90s I worked on a test device that could be programmed with different MAC addresses... we called it hte "Turbo Basher" as it was meant to do all kinds of stress and mischief on our own routers -we were a router company then.
Stuff like bootp and DHCP can use the MAC address for access control and network configuration. Switches and routers -when managing network access- can also use it for network management.
Microsoft could use the core ID as a key, except that since cores are meant to be plugged, you could swap cores on a motherboard. Although, you'd think that doing so would require a new OS installation, huh?
The "motherboard" per se has NO MAC addresses of any kind. Network interface controllers (NIC) have one MAC address each -it is unique to the NIC. If the NIC is built into the motherboard then, it would seem like the motherboard has it, but in reality the NIC is the peripheral that carries the MAC address.
It has been like that since, oh.... the first time they put an ethernet adaptor on a motherboard. Today it is ubiquitous to have more than one: ethernet plus 802.11 wireless.
It could be used an a unique set of identifiers for the motherboard, yes, since it is highly unlikely that the motherboard would operate with failed peripherals.
The MAC Address is designed to be used by the data link layer to identify the hardware, just as the IP address is used to identify the IP connection. The MAC address identifies the manufacturer and additional information.
Back in the early 90s I worked on a test device that could be programmed with different MAC addresses... we called it hte "Turbo Basher" as it was meant to do all kinds of stress and mischief on our own routers -we were a router company then.
Stuff like bootp and DHCP can use the MAC address for access control and network configuration. Switches and routers -when managing network access- can also use it for network management.
Microsoft could use the core ID as a key, except that since cores are meant to be plugged, you could swap cores on a motherboard. Although, you'd think that doing so would require a new OS installation, huh?
Last edited:
iPhones, Android phones and now windows supports using random mac addresses that change periodically with the local mac address pool bit set, to avoid mac tracking.... It's the default setting in phones now.
Microsoft runs an "algorithm" on your hardware during a Windows 8 or higher installation. This generates a 32 digit hexadecimal number that is "unique" to your hardware build. You can see this number by going to Settings -> System -> About and looking at the Device ID. As I recently discovered, swapping out the CPU chip changed the Device ID, but did not trigger a need to reauthorize W10. Swapping RAM modules, video cards, or hard drives did not change the hardware ID. MS will also assign a "Name" to each device, but you can change it to whatever you want. Some of the non MS software that you have on your PC may need reauthorization if either the Device ID or machine name changes.
Clicking Settings -> home -> Accounts -> Manage my Microsoft Account should show you every Windows device associated with your MS account. I was surprised to find 16 "devices," so I set out to find them all. It took a while, that 12 year old Toshiba laptop that had been sleeping in a closet for a few years was one of the 16. I plugged it in, booted W10 and it took a whole day to "update" it to W22H2. It scored in the bottom 2% of all PC's on "your PC vs the world" with a total Passmark score of 169. One of my grandkids will likely get to destroy it.
Three "devices" turned out to be older motherboards with CPU's and boot SSD's that were in their boxes on a shelf waiting for a project.
One was a forgotten Intel NUC that had been replaced by the Lenovo Nano that I scored cheap on Ebay a couple years ago for use in a portable "music construction device." When I have time to build a bigger case for the "music destruction device" the Nano will be replaced with the Asrock Desk Mini with a better Focusrite USB sound module that I also got on Ebay. Some of the other devices are complete PC's used for dedicated tasks. The i7-4790K machine now runs the "synth lab" mostly for writing and debugging code for Teensy boards and working with hardware synthesizers.
The last W7 machine in my lab just got upgraded to W10, stuffed into a 2RU case, and had its old M-Audio internal PCI sound card replaced with a USB Focusrite Solo for an improved noise floor. Its sole use if for test and measurement on audio amps and maybe some synth modules. Swapping W7 for W10 added one more "device" to my MS account. Now there are 17.
My collection spans 95% of the performance levels of all the PCs ever tested and user reported by Passmark. The core i5-2500K, two from the bottom used to be my OTA DVR, now it's just a music player with a 4 TB hard drive.
Clicking Settings -> home -> Accounts -> Manage my Microsoft Account should show you every Windows device associated with your MS account. I was surprised to find 16 "devices," so I set out to find them all. It took a while, that 12 year old Toshiba laptop that had been sleeping in a closet for a few years was one of the 16. I plugged it in, booted W10 and it took a whole day to "update" it to W22H2. It scored in the bottom 2% of all PC's on "your PC vs the world" with a total Passmark score of 169. One of my grandkids will likely get to destroy it.
Three "devices" turned out to be older motherboards with CPU's and boot SSD's that were in their boxes on a shelf waiting for a project.
One was a forgotten Intel NUC that had been replaced by the Lenovo Nano that I scored cheap on Ebay a couple years ago for use in a portable "music construction device." When I have time to build a bigger case for the "music destruction device" the Nano will be replaced with the Asrock Desk Mini with a better Focusrite USB sound module that I also got on Ebay. Some of the other devices are complete PC's used for dedicated tasks. The i7-4790K machine now runs the "synth lab" mostly for writing and debugging code for Teensy boards and working with hardware synthesizers.
The last W7 machine in my lab just got upgraded to W10, stuffed into a 2RU case, and had its old M-Audio internal PCI sound card replaced with a USB Focusrite Solo for an improved noise floor. Its sole use if for test and measurement on audio amps and maybe some synth modules. Swapping W7 for W10 added one more "device" to my MS account. Now there are 17.
My collection spans 95% of the performance levels of all the PCs ever tested and user reported by Passmark. The core i5-2500K, two from the bottom used to be my OTA DVR, now it's just a music player with a 4 TB hard drive.
True, that's called MAC Address Spoofing.
It was done because the NSA was tracking mobile phones with their MAC ADDR.
I'm not quite sure it's done with non mobile devices. Also, I'm not quite sure if the MAC ADDRs are still unique to the device.
In any event, mobile, roaming networks are quite different from wired networks in this respect, in the way the device publishes itself over an open RF medium. This doesn't happen in wired networks. Also, nowadays wired networks using NAT and segments, etc... so the initial idea of a unique MAC ADDR for NIC is a bit archaic. It's highly unlikely that two devices with the same NIC would ever appear in the same LAN. But still, the number is big, so....