Step one, don't buy more furniture than will comfortably fit in 475sqft apartment.
Seriously, if you've left yourself enough room to move around-in once the furniture is placed, then you should have enough room to assemble it. If all you have are 1' wide paths through the place then you have too much furniture.
On a full-featured PC I would agree, but on something with a small screen where every function takes up an inordinate amount of that screen (ie a smartphone that has a UI large enough that a human finger can use) it makes sense to use a model that lacks a dedicated button for the function.
Like everything it's a compromise. Google's gmail application on Android uses this kind of refresh and it wasn't exactly difficult to accidentally trigger the first time and then subsequently continue using when it became apparent.
So one of the problems that any car attempting to integrate technology could face is a poor user interface. There's a video on an older Maserati on Youtube where the reviewer comments about flaws in the interface, including issues where some features require use of both the physical button and the on-screen controls, and in a nutshell, too much time has to be taken off paying attention to the road in order to operate these features.
Personally I think that touchscreens are a horrible way to control a car. There's no tactile feedback on a touchscreen. One cannot tell for certain without taking one's eyes from the road what one is doing with the interface. Its bad enough for optional things like the radio and cell phone interaction, but it's a real problem for things that are mandatory when driving. The article summary's comment on the windshield wipers is a case in point, if most of the time I just need a light intermittent wiper setting I probably will leave my wipers set that way. If I drive into a thunderstorm on the highwayay I might immediately need fast-speed wipers. It's bad enough to not have an immediate way to turn up the speed without thinking, but if I have to hunt through menus to find the setting then that could be disastrous.
At times RMS has called any Linux distro that allowed for the easy installation of non-free software a non-free operating system. This includes Debian.
Now, from a practical point of view, Android is a lot closer to the BSD-model while theoretically still complying with the GPL, in that the developer has done as much as humanly possible to prevent the user from doing anything to the OS platform including installing software that the OS developer doesn't agree with. On the other hand, on a phone I'm not exactly going to get bent out of shape over it so long as the quality of what they do deliver is high. Sure, some more openness would be nice, but on the other hand I just need the damn thing to work every time I go to use it.
As for Linux subsystems for Windows, to play on the toybox analogies in the article summary, it isn't that Microsoft is going to take Shuttleworth's toys and go home, it's that Microsoft is going to take Shuttleworth's playmates and go home. From a corporate point of view, if the same software runs on a Linux environment or on a Windows environment, a decision-maker is going to opt for that Windows environment a lot when that decision-maker is himself more comfortable with Windows than with Linux.
With work I go to two or three smaller trade shows or conferences a year, usually held locally. There are a whole lot of vendors that are pushing products to supposedly get away from the command line when managing technology. Even Cisco is getting in on it, with a roadmap that essentially leaves behind the traditional IOS roots and heads off to a web-based central management system with zero-configuration management. A Microsoft approach to take Linux's functionality and integrate it into Windows will give decision-makers confidence that they too can migrate to Windows, even if the actual process to do it is difficult or if the software runs poorly that way.
...but the way Oracle runs it, probably getting to be most-hated and most-abandoned too. At some point most-abandoned will cross with most popular and it won't be most popular anymore.
An active cell-phone is no different in this regard from a person shouting, for example.
Sure it is. An active cell phone, idly waiting for an incoming call or to place one, is not detectable by human ears.
There's a legal concept calleed Plain View Doctrine. Previously this concept has been applied to curtilage, aka the private property surrounding a house that police may have to tread-upon in order to knock at the door. Officers are allowed to take actions if they, with their natural human senses, detect a crime, but they're not allowed to use tools and if they have a clear path to the door, they're not allowed to go around peeking into windows, they are supposed to stick with the path. Even using dogs when walking up to a house is not permitted.
It's no stretch to consider that your argument violates Plain View Doctrine since an officer cannot, with his natural senses, detect a cell phone nearby or identify a particular cell phone. He may be able to get a warrant to use a technology like stingray, or he may get a warrant to compel the carrier to provide him with data, but that's another matter.
To restate for the mentally impaired, by targeting 32 bit computing platforms as this infection did, it naturally filters-out nearly all home computers. That means that the majority of computers that get infected and phone-home are business computers, which is what they want to target.
A business is a place where people go to make money. Except your mom, she goes to the local street corner, which is how she got saddled with you.
If it's simply a hop-off point, all you need is one engineer who operates outside of his IT department whose specific software needs mandate he has local admin rights on his computer. He runs the tool he uses at home instead of calling IT, and suddenly his box is now the initial penetration point to access the company network.
You clearly overestimate the intelligence of management, supervisors, and service technicians.
We had a lead technician still trying to use Regclean a few years ago. On Windows 7 and Windows 8.1 computers. Same technician kept setting ethernet interfaces to 10Mbit Half Duplex because he somehow interpreted the time that 10/half was needed to push far beyond the 100m channel-length for a waaaaay overlength data drop as the Setting That We Should All Set.
My point is that a lot of myth and misunderstanding goes into IT, and often we get good results despite the stupidity, rather than because of it. I have no doubt that some technicians swore by CCleaner and used it in the corporate setting, and some IT departments even routinely used it in lieu of reimaging infected computers.
...for outlining why I thought specific 32 bit platforms, like those used by corporate computing because they tend to maintain their existing image over time even if they have 64 bit machines rather than migrating to a 64 bit OS. Home computers have been sold with essentially only 64 bit OSes preinstalled for several years. Only ancient home computers and business computers are still 32 bit. Natural filter, reduces the amount of unwanted communications to the Command and Control servers.
I'm more surprised with the venue that he chose in which to work, especially if he managed to get onto the company's wireless network and to reach sensitive stuff.
It's almost amateurish to actually sit there. He could have set up an old laptop with both an integrated Wifi controller and a PCMCIA Wifi device and used it as a wireless bridge into their network, set up shop somewhere that wasn't company premises, and then just formatted the old laptop once he was done, abandoning it in place. Hell, he could have even left it in the conference room sitting in a corner next to company equipment and probably no one would have paid it any mind, and may have even disposed of it for him ("what is this still doing here? I thought we got rid of these, must've missed one") and no ne would have been the wiser.
More to the point, just because it was used to reboot the PC, doesn't mean that it was necessary in order to trigger the OS to provide a login prompt.
Other than NT-based OSes, I don't know of any OSes that required doing that. Only reason I can think of to require it is that it may be difficult to script it, so a partially infected computer can't be brute-forced terribly easily, or one cannot easily build a second computer that attempts to control the keyboard connection to another computer to attempt to brute-force. I'm going to assume that there are other ways around that though, besides attempting to have a hardware key on the keyboard that cannot be emulated.
The archetypical story I've heard over the years was someone walking in on a manager banging his secretary on the conference table. [...] If you want to get away with something, try an IT storage closet.
And supervisors wonder why I leave the closets with the cutoff ends from terminating copper and fiber cable, plus an (un)healthy dose of crumbled ceiling tile and jagged-edged conduit sticking out.
I'm curious what security camera footage, if any, will reveal about the defendant's arrival and movements through the building.
If he took advantage of the bustle at the end of the workday to slip-in and then hid for a time where he would be unlikely to be stumbled upon then he's screwed.
Slashdot Mirror
Step one, don't buy more furniture than will comfortably fit in 475sqft apartment.
Seriously, if you've left yourself enough room to move around-in once the furniture is placed, then you should have enough room to assemble it. If all you have are 1' wide paths through the place then you have too much furniture.
So you can't shift gears?
On a full-featured PC I would agree, but on something with a small screen where every function takes up an inordinate amount of that screen (ie a smartphone that has a UI large enough that a human finger can use) it makes sense to use a model that lacks a dedicated button for the function.
Like everything it's a compromise. Google's gmail application on Android uses this kind of refresh and it wasn't exactly difficult to accidentally trigger the first time and then subsequently continue using when it became apparent.
So one of the problems that any car attempting to integrate technology could face is a poor user interface. There's a video on an older Maserati on Youtube where the reviewer comments about flaws in the interface, including issues where some features require use of both the physical button and the on-screen controls, and in a nutshell, too much time has to be taken off paying attention to the road in order to operate these features.
Personally I think that touchscreens are a horrible way to control a car. There's no tactile feedback on a touchscreen. One cannot tell for certain without taking one's eyes from the road what one is doing with the interface. Its bad enough for optional things like the radio and cell phone interaction, but it's a real problem for things that are mandatory when driving. The article summary's comment on the windshield wipers is a case in point, if most of the time I just need a light intermittent wiper setting I probably will leave my wipers set that way. If I drive into a thunderstorm on the highwayay I might immediately need fast-speed wipers. It's bad enough to not have an immediate way to turn up the speed without thinking, but if I have to hunt through menus to find the setting then that could be disastrous.
At times RMS has called any Linux distro that allowed for the easy installation of non-free software a non-free operating system. This includes Debian.
Now, from a practical point of view, Android is a lot closer to the BSD-model while theoretically still complying with the GPL, in that the developer has done as much as humanly possible to prevent the user from doing anything to the OS platform including installing software that the OS developer doesn't agree with. On the other hand, on a phone I'm not exactly going to get bent out of shape over it so long as the quality of what they do deliver is high. Sure, some more openness would be nice, but on the other hand I just need the damn thing to work every time I go to use it.
As for Linux subsystems for Windows, to play on the toybox analogies in the article summary, it isn't that Microsoft is going to take Shuttleworth's toys and go home, it's that Microsoft is going to take Shuttleworth's playmates and go home. From a corporate point of view, if the same software runs on a Linux environment or on a Windows environment, a decision-maker is going to opt for that Windows environment a lot when that decision-maker is himself more comfortable with Windows than with Linux.
With work I go to two or three smaller trade shows or conferences a year, usually held locally. There are a whole lot of vendors that are pushing products to supposedly get away from the command line when managing technology. Even Cisco is getting in on it, with a roadmap that essentially leaves behind the traditional IOS roots and heads off to a web-based central management system with zero-configuration management. A Microsoft approach to take Linux's functionality and integrate it into Windows will give decision-makers confidence that they too can migrate to Windows, even if the actual process to do it is difficult or if the software runs poorly that way.
So they caught mono?
You misread it. It isn't that corporations mainly run 32-bit OS, it's that one won't find 32-bit OS anywhere else besides corporations.
...but the way Oracle runs it, probably getting to be most-hated and most-abandoned too. At some point most-abandoned will cross with most popular and it won't be most popular anymore.
It's not even a honeypot. A honeypot requires intentional penetration of a system one knowingly is not welcome into.
This is arguably jamming and is an illegal use of spectrum that the device owner is not entitled to use.
An active cell-phone is no different in this regard from a person shouting, for example.
Sure it is. An active cell phone, idly waiting for an incoming call or to place one, is not detectable by human ears.
There's a legal concept calleed Plain View Doctrine. Previously this concept has been applied to curtilage, aka the private property surrounding a house that police may have to tread-upon in order to knock at the door. Officers are allowed to take actions if they, with their natural human senses, detect a crime, but they're not allowed to use tools and if they have a clear path to the door, they're not allowed to go around peeking into windows, they are supposed to stick with the path. Even using dogs when walking up to a house is not permitted.
It's no stretch to consider that your argument violates Plain View Doctrine since an officer cannot, with his natural senses, detect a cell phone nearby or identify a particular cell phone. He may be able to get a warrant to use a technology like stingray, or he may get a warrant to compel the carrier to provide him with data, but that's another matter.
2.0 Build 12571412 does not make it obvious that it has tab support. Does anyone else see tabs?
Why China? The companies targeted already manufacture most of their products in China, so China already has access to their technology.
To restate for the mentally impaired, by targeting 32 bit computing platforms as this infection did, it naturally filters-out nearly all home computers. That means that the majority of computers that get infected and phone-home are business computers, which is what they want to target.
A business is a place where people go to make money. Except your mom, she goes to the local street corner, which is how she got saddled with you.
If it's simply a hop-off point, all you need is one engineer who operates outside of his IT department whose specific software needs mandate he has local admin rights on his computer. He runs the tool he uses at home instead of calling IT, and suddenly his box is now the initial penetration point to access the company network.
You clearly overestimate the intelligence of management, supervisors, and service technicians.
We had a lead technician still trying to use Regclean a few years ago. On Windows 7 and Windows 8.1 computers. Same technician kept setting ethernet interfaces to 10Mbit Half Duplex because he somehow interpreted the time that 10/half was needed to push far beyond the 100m channel-length for a waaaaay overlength data drop as the Setting That We Should All Set.
My point is that a lot of myth and misunderstanding goes into IT, and often we get good results despite the stupidity, rather than because of it. I have no doubt that some technicians swore by CCleaner and used it in the corporate setting, and some IT departments even routinely used it in lieu of reimaging infected computers.
...for outlining why I thought specific 32 bit platforms, like those used by corporate computing because they tend to maintain their existing image over time even if they have 64 bit machines rather than migrating to a 64 bit OS. Home computers have been sold with essentially only 64 bit OSes preinstalled for several years. Only ancient home computers and business computers are still 32 bit. Natural filter, reduces the amount of unwanted communications to the Command and Control servers.
Salvage the bearings out for something else?
I'm more surprised with the venue that he chose in which to work, especially if he managed to get onto the company's wireless network and to reach sensitive stuff.
It's almost amateurish to actually sit there. He could have set up an old laptop with both an integrated Wifi controller and a PCMCIA Wifi device and used it as a wireless bridge into their network, set up shop somewhere that wasn't company premises, and then just formatted the old laptop once he was done, abandoning it in place. Hell, he could have even left it in the conference room sitting in a corner next to company equipment and probably no one would have paid it any mind, and may have even disposed of it for him ("what is this still doing here? I thought we got rid of these, must've missed one") and no ne would have been the wiser.
It was NT. Might be as far back as NT 3.x. Can't remember anymore.
Yet I can still remember how to install a Soundblaster 16 in the MCI control panel in Windows for Workgroups 3.11.
And I've got an Annie Key on my keyboard. When you press it the in-keyboard macro prints, "tomorrow, tomorrow, I love you, tomorrow..." on-screen.
More to the point, just because it was used to reboot the PC, doesn't mean that it was necessary in order to trigger the OS to provide a login prompt.
Other than NT-based OSes, I don't know of any OSes that required doing that. Only reason I can think of to require it is that it may be difficult to script it, so a partially infected computer can't be brute-forced terribly easily, or one cannot easily build a second computer that attempts to control the keyboard connection to another computer to attempt to brute-force. I'm going to assume that there are other ways around that though, besides attempting to have a hardware key on the keyboard that cannot be emulated.
Why would you pay for fidget spinners when you can go to a trade show and literally every single vendor is handing them out as swag?
Not in here mister, this is a Whole Foods.
The archetypical story I've heard over the years was someone walking in on a manager banging his secretary on the conference table. [...] If you want to get away with something, try an IT storage closet.
And supervisors wonder why I leave the closets with the cutoff ends from terminating copper and fiber cable, plus an (un)healthy dose of crumbled ceiling tile and jagged-edged conduit sticking out.
I'm curious what security camera footage, if any, will reveal about the defendant's arrival and movements through the building.
If he took advantage of the bustle at the end of the workday to slip-in and then hid for a time where he would be unlikely to be stumbled upon then he's screwed.