Ah, the old Sunk Costs Fallacy. My brother in law had a similar issue on his Windows laptop. I determined the cause to the the crap antivirus he was running (either Nortons/Symantec or McAfee). Told him that it was causing the problem and I was going to uninstall it. He wouldn't let me because he'd just renewed the subscription for it, so still had 10 months to go.
In hindsight, it was one of the best decisions he made, as from that point forwards I had a valid reason to refuse any computer support whatsoever.
Current versions of OS X use Menlo as the monospaced font in Terminal, it's better better than Monaco.
The OS X Terminal.app is one of the best, and simplest, terminals I've ever used. With telnet and ssh built in to the OS, and picocom available through MacPorts (and a number of other avenues) it pretty much has everything I need from a terminal.
So many terminals don't re-wrap the text on window resize (I can't believe this has only just come to CMD.EXE and Powershell in Windows 10) and the OS X terminal does this really well. There are plenty of theming options, including a reasonable approximation of the default Solaris terminal colours (Profiles > Man Page). And, if you want a transparent red cursor, it's easy to configure it that way...
No, go the other way as high res as possible. Scaling in OS X on a Retina class screen is quite good. The default is to display @2x - 2x2 physical pixels is 1 "pixel" but you can scale up or down and it looks OK. On my 13" laptop, I run it at a resolution similar to a 15" and everything looks good. On a 27" desktop, you could happily run it at a lower resolution and everything will scale. Things like fonts etc are generally drawn at the native resolution, so they're sharp and crisp. If the app is retina-aware, UI elements are drawn properly, otherwise if not, they're scaled - but with a high-res display, the scaling isn't as much as an issue as if you're doing it at 72-100 dpi.
Just like the vast majority of malware gets downloaded and run - phishing and drive-by downloads.
The most recent ones I've seen were from the Australian Federal Police warning you about a traffic infringement - please open the attachment to see the photo.
With ransomware, like Cryptolocker, it doesn't generate the key and then send it to the C&C servers - the machine doing the encrypting (i.e. what was your machine before it got owned) never has the private key in it's possession. When it's ready to start encrypting, it contacts the C&C server. The C&C server generates a new private/public keypair and sends the public key to the owned machine. The owned machine then starts encrypting everything with the public key, and only the private key (that resides on the C&C server and nowhere else) is able to decrypt the files.
This means that even if you were monitoring all network traffic and you scour the memory and the disk, you will never see a copy of the private key needed to decrypt the files.
Anyway, I'm going off on a tangent here, this doesn't have much to do with TFA...
but in terms of raw storage, a stack of 38 9.5mm tall 2.5" 2TB drives would only be 361mm
You think Microsoft is using "2.5" notebook hard drives" in its storage cloud?
A lot of enterprise storage actually uses small form factor (aka 2.5") hard drives because you can fit more drives in a chassis. Even in a lot of high-speed (10k and 15k rpm) 3.5" drives, the platters are not the full 3.5" size, they're more like a 2.5" platter in a 3.5" case.
Yep, this. If they can handle just a screen then an iPad is pretty hard to break (software-wise). If they need a full computer, get a Mac with AppleCare and One to One. Have the Mac set up with Parental Controls to lock down some of the more confusing aspects of the machine (i.e., make sure the icons you need to stay in the Dock are absolutely going be in the Dock).
What happened was that iFixit broke the NDA by posting the pics before the device was released. Apple then cancelled their developer account, which as they also used that developer account for their App, had the knock-on effect of pulling their app from the App Store
I'm wondering how these apps made it through in the first place.
From what I've read - it was a trojaned version of Xcode that some developers have used and this has inserted malware into their otherwise apps. Apple's scanning has now discovered it, although I don't know why it has taken them so long to pick it up.
Printers, otherwise known in the industry as Toner Dispensers. Manufacturers, especially Xerox, internally (and only half-jokingly) refer to printers as Toner Dispensers. It's where they make a massive amount of their revenue from.
Sure, when they're selling a printer for a price in the 10's of $k, they're not exactly making a loss, or only just breaking even on the hardware, there's still a decent amount of margin on this - but the ongoing revenue stream (and the reason they try to get everyone onto managed print services) is in selling toner, and lots of it.
Over the life of a printer (or copier, which is just a big printer with a scanner built into it) the cost of consumables will be far greater than the initial purchase price of the machine. Generally, toner is cheaper on bigger and more expensive printers (which in itself is strange as it's the same toner) - this is why if you're printing a large volume, you're better off getting a more expensive printer with cheaper toner.
AC has far lower transmission losses over long distances, however with the advent of rooftop solar now people can generate DC closer to where they're using it. Converting AC to DC and DC to AC will always incur losses, and as AC is far more efficient for transmission, we've historically used AC everywhere (well, except inside just about everything you plug into an electrical outlet, where DC is generally used)
I'll have to watch that docco - After using BBC micros and BBC Model B in primary school, and the Acorn Archimedes in high school, I've followed Arm with a bit of interest. Their rise and fall and then stratospheric rise again from the ashes is an incredible story. By sheer volume, there are probably more ARM cores on the planet than any other architecture - ARM was originally the Acorn RISC Machine and was an incredible processor architecture in it's day (and, through licensing to other fabs, still is pretty impressive for it's performance per watt)
One is to look for alternative remote desktop software that does work. I've had success with TeamViewer - YMMV.
Two is to put in a lan-to-lan VPN at each site and configure your routing appropriately - either go with something like DD-WRT or get something that will do it out of the box like a Ubiquity EdgeRouter Lite ($100 and it has 3x gigabit ports and enough horsepower to route at an appreciable fraction of that rate)
I know it's not infinite. Defects, bit rot, failure of moving parts - there's a lot to go wrong in a hard drive, that's why I had "infinite" in inverted commas...
The question is not whether certs are worth the time and money (I tend to believe that they're not) but if you're putting them on your resume, who is actually going to check...
Another answer for are they worth the time and money - most definitely for the certification centres.
Yep. I'll happily take 10x the number of IOPS and limited writes (that are in most cases many years of regular service) over "infinite" writes and moving parts. I wouldn't want to keep spinning rust in service more than 3-5 years tops, and if all the SSDs I've used will survive this long, why should I use the slower solution?
Yes, that makes perfect sense - because nothing good was ever accomplished in anything other than 1000 lines of easy-to-read C (an oxymoron if ever I've heard it)
Because someone has already done the hard work for you. Time to do what you want to do = 2-4 hours or more. Time to dump an image to a CF card and boot it - 2 minutes. Plus, if it's based on m0n0, it'll run out of the box on embedded systems like Alix and Soekris boxes, which are amazingly reliable embedded x86 systems with no moving parts. I've got Alix-based m0n0 firewalls out there that haven't been rebooted in years and they just keep going. It's also designed to run from flash media, so writes (for logs etc) are kept to a minimum.
Ah, the old Sunk Costs Fallacy.
My brother in law had a similar issue on his Windows laptop. I determined the cause to the the crap antivirus he was running (either Nortons/Symantec or McAfee).
Told him that it was causing the problem and I was going to uninstall it.
He wouldn't let me because he'd just renewed the subscription for it, so still had 10 months to go.
In hindsight, it was one of the best decisions he made, as from that point forwards I had a valid reason to refuse any computer support whatsoever.
Yep, but it'll be 128 integer cores with 64 floating-point cores, and someone will take them to court over it... because... butthurt.
Current versions of OS X use Menlo as the monospaced font in Terminal, it's better better than Monaco.
The OS X Terminal.app is one of the best, and simplest, terminals I've ever used. With telnet and ssh built in to the OS, and picocom available through MacPorts (and a number of other avenues) it pretty much has everything I need from a terminal.
So many terminals don't re-wrap the text on window resize (I can't believe this has only just come to CMD.EXE and Powershell in Windows 10) and the OS X terminal does this really well. There are plenty of theming options, including a reasonable approximation of the default Solaris terminal colours (Profiles > Man Page). And, if you want a transparent red cursor, it's easy to configure it that way...
No, go the other way as high res as possible. Scaling in OS X on a Retina class screen is quite good. The default is to display @2x - 2x2 physical pixels is 1 "pixel" but you can scale up or down and it looks OK. On my 13" laptop, I run it at a resolution similar to a 15" and everything looks good. On a 27" desktop, you could happily run it at a lower resolution and everything will scale. Things like fonts etc are generally drawn at the native resolution, so they're sharp and crisp. If the app is retina-aware, UI elements are drawn properly, otherwise if not, they're scaled - but with a high-res display, the scaling isn't as much as an issue as if you're doing it at 72-100 dpi.
I'm curious - what do you mean by the cores were parked, and you had to unpark every other core?
Just like the vast majority of malware gets downloaded and run - phishing and drive-by downloads.
The most recent ones I've seen were from the Australian Federal Police warning you about a traffic infringement - please open the attachment to see the photo.
With ransomware, like Cryptolocker, it doesn't generate the key and then send it to the C&C servers - the machine doing the encrypting (i.e. what was your machine before it got owned) never has the private key in it's possession. When it's ready to start encrypting, it contacts the C&C server. The C&C server generates a new private/public keypair and sends the public key to the owned machine. The owned machine then starts encrypting everything with the public key, and only the private key (that resides on the C&C server and nowhere else) is able to decrypt the files.
This means that even if you were monitoring all network traffic and you scour the memory and the disk, you will never see a copy of the private key needed to decrypt the files.
Anyway, I'm going off on a tangent here, this doesn't have much to do with TFA...
but in terms of raw storage, a stack of 38 9.5mm tall 2.5" 2TB drives would only be 361mm
You think Microsoft is using "2.5" notebook hard drives" in its storage cloud?
A lot of enterprise storage actually uses small form factor (aka 2.5") hard drives because you can fit more drives in a chassis. Even in a lot of high-speed (10k and 15k rpm) 3.5" drives, the platters are not the full 3.5" size, they're more like a 2.5" platter in a 3.5" case.
Yep, this. If they can handle just a screen then an iPad is pretty hard to break (software-wise).
If they need a full computer, get a Mac with AppleCare and One to One.
Have the Mac set up with Parental Controls to lock down some of the more confusing aspects of the machine (i.e., make sure the icons you need to stay in the Dock are absolutely going be in the Dock).
Getting a new computer every year won't transfer any of their data over, or help them with problems when they inevitably happen.
Office 2016 requires Yosemite, it will not install on 10.9 or earlier.
What happened was that iFixit broke the NDA by posting the pics before the device was released. Apple then cancelled their developer account, which as they also used that developer account for their App, had the knock-on effect of pulling their app from the App Store
http://ifixit.org/blog/7401/if...
From what I've read - it was a trojaned version of Xcode that some developers have used and this has inserted malware into their otherwise apps.
Apple's scanning has now discovered it, although I don't know why it has taken them so long to pick it up.
Printers, otherwise known in the industry as Toner Dispensers.
Manufacturers, especially Xerox, internally (and only half-jokingly) refer to printers as Toner Dispensers. It's where they make a massive amount of their revenue from.
Sure, when they're selling a printer for a price in the 10's of $k, they're not exactly making a loss, or only just breaking even on the hardware, there's still a decent amount of margin on this - but the ongoing revenue stream (and the reason they try to get everyone onto managed print services) is in selling toner, and lots of it.
Over the life of a printer (or copier, which is just a big printer with a scanner built into it) the cost of consumables will be far greater than the initial purchase price of the machine. Generally, toner is cheaper on bigger and more expensive printers (which in itself is strange as it's the same toner) - this is why if you're printing a large volume, you're better off getting a more expensive printer with cheaper toner.
AC has far lower transmission losses over long distances, however with the advent of rooftop solar now people can generate DC closer to where they're using it.
Converting AC to DC and DC to AC will always incur losses, and as AC is far more efficient for transmission, we've historically used AC everywhere (well, except inside just about everything you plug into an electrical outlet, where DC is generally used)
I'll have to watch that docco - After using BBC micros and BBC Model B in primary school, and the Acorn Archimedes in high school, I've followed Arm with a bit of interest. Their rise and fall and then stratospheric rise again from the ashes is an incredible story. By sheer volume, there are probably more ARM cores on the planet than any other architecture - ARM was originally the Acorn RISC Machine and was an incredible processor architecture in it's day (and, through licensing to other fabs, still is pretty impressive for it's performance per watt)
There are two ways of doing this.
One is to look for alternative remote desktop software that does work. I've had success with TeamViewer - YMMV.
Two is to put in a lan-to-lan VPN at each site and configure your routing appropriately - either go with something like DD-WRT or get something that will do it out of the box like a Ubiquity EdgeRouter Lite ($100 and it has 3x gigabit ports and enough horsepower to route at an appreciable fraction of that rate)
https://www.ubnt.com/edgemax/e...
I know it's not infinite. Defects, bit rot, failure of moving parts - there's a lot to go wrong in a hard drive, that's why I had "infinite" in inverted commas...
Yep, nothing at all wrong with doing that. Massive increase in IPOS by using SSD and dump data to the platters for long term and redundant storage.
The question is not whether certs are worth the time and money (I tend to believe that they're not) but if you're putting them on your resume, who is actually going to check...
Another answer for are they worth the time and money - most definitely for the certification centres.
Yep. I'll happily take 10x the number of IOPS and limited writes (that are in most cases many years of regular service) over "infinite" writes and moving parts. I wouldn't want to keep spinning rust in service more than 3-5 years tops, and if all the SSDs I've used will survive this long, why should I use the slower solution?
John, is that you?
Yes, that makes perfect sense - because nothing good was ever accomplished in anything other than 1000 lines of easy-to-read C (an oxymoron if ever I've heard it)
Hey, you forgot to write your own web-based interface so that even a complete nufty can edit firewall rules nat port mappings etc ;-)
Because someone has already done the hard work for you.
Time to do what you want to do = 2-4 hours or more.
Time to dump an image to a CF card and boot it - 2 minutes.
Plus, if it's based on m0n0, it'll run out of the box on embedded systems like Alix and Soekris boxes, which are amazingly reliable embedded x86 systems with no moving parts. I've got Alix-based m0n0 firewalls out there that haven't been rebooted in years and they just keep going. It's also designed to run from flash media, so writes (for logs etc) are kept to a minimum.