And have a list of serial numbers of stolen units...
And blacklist them from being able to install new versions of Apple software.
And make them automatically send phone-home messages to Apple and get bricked the next time a software update is attempted. With a message that says "Please bring to your nearest Apple store for service"
No.. PCI edge connectors have a minimum durability of 50 mating cycles....
Most of the ones in actual use will survive over 100, some over 500.
However, this number goes down considerably as the connectors age. Corrosion can significantly reduce the durability of the connector.
If your board is 5 years old, the connector may fail after 4 or 5 cycles.
The connector ratings apply primarily to hardware that is less than a year old.
If they have some factual information, they may have more. The defendant's legal team may wish to learn their identities, so the commentors can be subpoena'd for questioning as possible witnesses for trial.
Until one day when the CMOS battery dies, and after a power outage, the system no longer boots correctly (or no longer auto-recovers from power outage).
No I haven't... What are those fancy tablets called, where can I find one? I can think of some nice uses for an integrated device with a portable monitor+keyboard...
scary... OOB management should be standard minimal requirements on servers; no important server should ever be deployed without it, much like no really important server should be deployed without backups or with just 1 mechanical hard drive instead of a RAID array..
It also provides debugging output to the serial port eg
LinuxBIOS can report all errors and hardware failures over the serial console. A normal BIOS, even with serial console extensions, will initialize the serial port too late in the game for some failures to be detected, and it will usually fail if the CMOS is cleared.
They are completely correct, actually. Vista attempts to fix any problems that come up automagically.
What? No. That's completely wrong. Vista does not automatically try to fix all problems. Maybe you have a special build of Vista or something.
It tries to fix some problems, e.g. it reboots after a crash, but Vista would be unusable otherwise.
Some of the most common Windows problems are malware on the system, and Vista does nothing about this.
Vista doesn't even have documentation or well-published tutorials to help deal with many of the problems that can arise. The documentation of the Windows registry, and where you should go to clear or fix an app's settings for troubleshooting is basically non-existent.
Compare to Linux, where the file format and meaning of all the basic system configuration files are well documented. If you absolutely have to tweak settings by hand, you can find all the helpfiles and step-by-step tutorials you need.
Vista also does nothing about broken updates/software installers thet have corrupted important files, corrupt registry,
It is automatic though, and there sure as hell isn't anything automatic about fixing a problem in Linux.
Linux doesn't spontaneously develop problems like Windows does. If it doesn't break on its own, how the hell would you expect it to fix itself?
Unlike with Windows, the distribution vendors ship the third-party software apps, and in the case of major distros like Redhat, they actually qualify third-party software, and make sure it works.
With Windows, you download third-party software from third-party websites, it hasn't been even looked at by Microsoft, and it's a diceroll, whether it will be just fine, or whether it will 'break' your system, make subtle unexpected changes, or even modify well-hidden registry settings or drop files with poor permissions, creating massive security risks.
The vast majority of problems that develop on Linux systems are hardware failures.
Man pages are shit, by the way,
Man pages are quick 'help files', not the manual.
For the most part, they are only utilized by command-line users.
The manuals are info pages. Browsable using the info browser, on most enterprise distros, this is accessible from the Gnome or KDE desktop, using the menu.
And a RocketRaid controller whose drivers are open source but not included in the Linux kernel, and not available in compiled form from the OS vendor.
The RAID vendor ships source code and binaries, but binaries only for the original RHEL 5.0 and major release kernels, they don't roll a new driver for every kernel update.
Help people solve the problem the service created.
Now they just need to add a fee for it, and they may have a lucrative service.
For my part, I think the utility of the street view service is worth whatever minor embarrasment it causes for some people who got their picture taken when in public.
Google wasn't looking for them, they just happened to be there when Google was taking a picture of what was visible from the public street.
I don't see how Google can get to control the photo and "stop malicious use" once they've posted it; however.
First of all, they're basically driving down the road, continuously snapping automated pictures.
This in effect means that the photographs are merely factual, not selected based on creative value; merely automatically included, meaning they have no novelty or aesthetic value causing their inclusion, therefore, excluding them from copyright...
Second of all, the people "maliciously using" said pictures can always screen cap and post images without linking it to Google. Google's "banning" of their site has absolutely zero effect on the frozen images so displayed.
And mirror them as widely as possible... I don't see there being much Google can legally do, that is, unless Google's willing to engage in dirty behavior and use certain malicious strong-arm tactics themselves, which might be illegal in themselves....
Sure they do. When the driver is distributed sepately and not integrated in the kernel, it's a PAIN to keep the driver when 'yum updating' your kernel, you have to go grab kernel source again and recompile the driver.
It takes 6+ hours of extra work, just because you can't simply use the existing driver binary with the new kernel.
Moreover, most major hardware vendors aren't willing and don't want to distribute drivers as open source. For various reasons; mainly for support concerns, 3rd party licensed code, OEM'ed parts in the hardware, and proprietary hw details source would reveal.
Many of them deliver binary drivers that only work with specific kernels.
Or they deliver a driver, and you have to compile a special 'wrapper' kernel module to load the driver.
Again, you've got to spend the 3-6 hours of extra work every time you 'yum update' your kernel, you've got to manually go get the kernel sources, prepare a build environment, and compile the module against the new kernel, before it will even be willing to load the driver.
Btw, all this reflects extremely negatively on the Linux kernel
and strongly discourages hardware vendors from trying to support it.
Linux vs Windows is a fun debate that many nerds are interested in, due to Linux's special status, and many nerds have a passion for it, Slashdot is news for nerds, hence the article.
I'm sure most of the others are low-key debates like the merits of consumers buying Halo over Blizzard Starcraft, Epson over HP printers, Fujitsu VS TDK CD-Rs, or Mitsumi VS Samsung DVD-ROM drives, or VI vs Emacs are of little interest to most.
Those would be of interest to some, but probably not most slashdot readers.
But i'm sure if Intel put out some seriously negative propaganda about AMD CPUs, or nVidia put out some seriously nasty propaganda about ATI video cards, or HP put out some negative propaganda about Dells or Apples, massive numbers of slashdot readers would be concerned....
Much like they'd be if MS was involved. The bigger / more monopolistic the company, the more scandalous it is to put out negative propaganda about attempted competitors.
Because it's seen as a clearer abuse of monopoly power to quash attempts by weaker companies (or the community, in the case with Linux) to compete.
These remarks are easily proven false, by demonstrating the large volume of step-by-step tutorials and help documentation that are available.
http://i273.photobucket.com/albums/jj203/godofgrunts/Linux/Linux3.jpg
Makes a very non-subjective claim that Windows 7 is compatible with Many Printers and Scanners -- as in, a large number, and Linux is compatible with few -- as in a small number.
In fact, they display a bar graph for Windows and Linux compatibility; the graph for Windows is 100% full and the graph for Linux is 25% of full, indicating Linux is compatible with only 25% as many printers as Windows 7 is.
This is easily falsifiable by showing the large number of printers that Linux drivers are available for, the small number that drivers are unavailable for. And also showing the large number of printers Linux has drivers for that don't work in Windows 7 / Vista.
The same applies to Camera / mp3 player / iPod compatibility.
The claim Linux has no "Authorized support" available can also be shown to be false.
Telling lies is what's unethical, not promoting one product over another, that's fine, if done in a proper way.
Presumably, when best buy sells both Linux and Windows Netbooks, they would rather sell a Linux netbook than not make a sale, because the consumer thinks the Linux offering doesn't do what they want AND the Windows option is too expensive, they want to go elsewhere and shop around more.
They can lose the sale because of this.
Microsoft doesn't mind. They would rather the customer buys nothing from bestbuy than that they buy a Linux netbook.
They know if they can stop them from buying Linux long enough, they'll eventually buy some Windows from someone else; maybe they'll just wait 6 months until they can save up the extra money for that Windows netbook.
It's so bad, that at some point the kernel literally got a "MAGIC NUMBER" define where a constant is stored in every module,
And the kernel refuses to load any module whose "magic number" doesn't match the compiled kernel's version and certain compile options, like PAE support, SMP support, Xen.
This is irritating.
The kernel should be maintaining an ability to load drivers compiled against earlier kernel versions.
And provide a framework to be able to compile driver modules without kernel sources.
It makes sense for them, it doesn't make sense for some customers who will be spending more money. This hurts the customer, and may ultimately erode their trust, when their friends show them their Linux netbook and all it can do (that the best buy people said it couldn't).
It's dishonest if their employees tell their customers these things in order to discourage them from buying the cheaper unit.
No, when you click the "auto upgrade" button, WP prompts you to enter the hostname, FTP username, and FTP password, to apply the upgrades.
Now, this does pose a security risk if your site is compromised (unbeknownst to you), and the attacker manages to use SQL injection to redirect you to a 'fake upgrade page'
When you click the upgrade button, and provide your credentials... the attacker has co-opted the web-ui, and you're sending the FTP username and password directly to the kiddie, giving them the means to completely pwn the site....
Slashdot Mirror
And have a list of serial numbers of stolen units...
And blacklist them from being able to install new versions of Apple software.
And make them automatically send phone-home messages to Apple and get bricked the next time a software update is attempted. With a message that says "Please bring to your nearest Apple store for service"
Who says bad guys use the back of a stolen van?
In these days... I expect... One word: eBay.
The worm could be designed just to find as many wordpress installs as possible and attempt the exploit on all of them, regardless of version number.
Using searches for wordpress-specific files as search keywords to identify them.
No.. PCI edge connectors have a minimum durability of 50 mating cycles....
Most of the ones in actual use will survive over 100, some over 500.
However, this number goes down considerably as the connectors age. Corrosion can significantly reduce the durability of the connector.
If your board is 5 years old, the connector may fail after 4 or 5 cycles. The connector ratings apply primarily to hardware that is less than a year old.
The defense might want to suggest some sort of conspiracy theory planned by 300 internet users to frame the defendant.
If they have some factual information, they may have more. The defendant's legal team may wish to learn their identities, so the commentors can be subpoena'd for questioning as possible witnesses for trial.
The details are right, and it's not "fear mongering", it's just the unfortunate truth.
You don't configure the kernel for a serial console, you CONFIGURE THE BOOT LOADER for it:
Actually, you need to configure 3 (or 4) things for it:
Until one day when the CMOS battery dies, and after a power outage, the system no longer boots correctly (or no longer auto-recovers from power outage).
No I haven't... What are those fancy tablets called, where can I find one? I can think of some nice uses for an integrated device with a portable monitor+keyboard...
scary... OOB management should be standard minimal requirements on servers; no important server should ever be deployed without it, much like no really important server should be deployed without backups or with just 1 mechanical hard drive instead of a RAID array..
Use another server to PXE boot the former to a custom rescue image that has SSH enabled for you to remote login with.
Fix whatever you did that broke network access. Save changes, turn off netboot server, reboot.
It's drastic, but coreboot with a FILO payload and console on serial port.
May also have a USB EHCI Debug Port option
It also provides debugging output to the serial port eg
They are completely correct, actually. Vista attempts to fix any problems that come up automagically.
What? No. That's completely wrong. Vista does not automatically try to fix all problems. Maybe you have a special build of Vista or something. It tries to fix some problems, e.g. it reboots after a crash, but Vista would be unusable otherwise.
Some of the most common Windows problems are malware on the system, and Vista does nothing about this.
Vista doesn't even have documentation or well-published tutorials to help deal with many of the problems that can arise. The documentation of the Windows registry, and where you should go to clear or fix an app's settings for troubleshooting is basically non-existent.
Compare to Linux, where the file format and meaning of all the basic system configuration files are well documented. If you absolutely have to tweak settings by hand, you can find all the helpfiles and step-by-step tutorials you need.
Vista also does nothing about broken updates/software installers thet have corrupted important files, corrupt registry,
It is automatic though, and there sure as hell isn't anything automatic about fixing a problem in Linux.
Linux doesn't spontaneously develop problems like Windows does. If it doesn't break on its own, how the hell would you expect it to fix itself?
Unlike with Windows, the distribution vendors ship the third-party software apps, and in the case of major distros like Redhat, they actually qualify third-party software, and make sure it works.
With Windows, you download third-party software from third-party websites, it hasn't been even looked at by Microsoft, and it's a diceroll, whether it will be just fine, or whether it will 'break' your system, make subtle unexpected changes, or even modify well-hidden registry settings or drop files with poor permissions, creating massive security risks.
The vast majority of problems that develop on Linux systems are hardware failures.
Man pages are shit, by the way,
Man pages are quick 'help files', not the manual. For the most part, they are only utilized by command-line users.
The manuals are info pages. Browsable using the info browser, on most enterprise distros, this is accessible from the Gnome or KDE desktop, using the menu.
I'm using Redhat Enterprise Linux 5.4
And a RocketRaid controller whose drivers are open source but not included in the Linux kernel, and not available in compiled form from the OS vendor.
The RAID vendor ships source code and binaries, but binaries only for the original RHEL 5.0 and major release kernels, they don't roll a new driver for every kernel update.
Help people solve the problem the service created. Now they just need to add a fee for it, and they may have a lucrative service.
For my part, I think the utility of the street view service is worth whatever minor embarrasment it causes for some people who got their picture taken when in public.
Google wasn't looking for them, they just happened to be there when Google was taking a picture of what was visible from the public street.
I don't see how Google can get to control the photo and "stop malicious use" once they've posted it; however.
First of all, they're basically driving down the road, continuously snapping automated pictures. This in effect means that the photographs are merely factual, not selected based on creative value; merely automatically included, meaning they have no novelty or aesthetic value causing their inclusion, therefore, excluding them from copyright...
Second of all, the people "maliciously using" said pictures can always screen cap and post images without linking it to Google. Google's "banning" of their site has absolutely zero effect on the frozen images so displayed.
And mirror them as widely as possible... I don't see there being much Google can legally do, that is, unless Google's willing to engage in dirty behavior and use certain malicious strong-arm tactics themselves, which might be illegal in themselves....
"Open source drivers don't have this problem."
Sure they do. When the driver is distributed sepately and not integrated in the kernel, it's a PAIN to keep the driver when 'yum updating' your kernel, you have to go grab kernel source again and recompile the driver.
It takes 6+ hours of extra work, just because you can't simply use the existing driver binary with the new kernel.
Moreover, most major hardware vendors aren't willing and don't want to distribute drivers as open source. For various reasons; mainly for support concerns, 3rd party licensed code, OEM'ed parts in the hardware, and proprietary hw details source would reveal.
Many of them deliver binary drivers that only work with specific kernels.
Or they deliver a driver, and you have to compile a special 'wrapper' kernel module to load the driver.
Again, you've got to spend the 3-6 hours of extra work every time you 'yum update' your kernel, you've got to manually go get the kernel sources, prepare a build environment, and compile the module against the new kernel, before it will even be willing to load the driver.
Btw, all this reflects extremely negatively on the Linux kernel and strongly discourages hardware vendors from trying to support it.
Wolfenstein: Enemy Territory
Linux vs Windows is a fun debate that many nerds are interested in, due to Linux's special status, and many nerds have a passion for it, Slashdot is news for nerds, hence the article.
I'm sure most of the others are low-key debates like the merits of consumers buying Halo over Blizzard Starcraft, Epson over HP printers, Fujitsu VS TDK CD-Rs, or Mitsumi VS Samsung DVD-ROM drives, or VI vs Emacs are of little interest to most.
Those would be of interest to some, but probably not most slashdot readers.
But i'm sure if Intel put out some seriously negative propaganda about AMD CPUs, or nVidia put out some seriously nasty propaganda about ATI video cards, or HP put out some negative propaganda about Dells or Apples, massive numbers of slashdot readers would be concerned....
Much like they'd be if MS was involved. The bigger / more monopolistic the company, the more scandalous it is to put out negative propaganda about attempted competitors.
Because it's seen as a clearer abuse of monopoly power to quash attempts by weaker companies (or the community, in the case with Linux) to compete.
Taking in packages from outside the vetted repository is a security nightmare and can subject you to installing trojanned binaries.
But that's what .RPM and .DEB files are for... You can install manually, instead of from a repository.....
You can even use a tool called Alien to convert RPMs to DEBs and vice-versa
It's not puffery, they contain statements that are not subjective. For example:
http://i273.photobucket.com/albums/jj203/godofgrunts/Linux/Linux12.jpg
They say "Linux is a self help solution. There are no step-by-step tutorials provided, and help documentation is limited.
These remarks are easily proven false, by demonstrating the large volume of step-by-step tutorials and help documentation that are available.
http://i273.photobucket.com/albums/jj203/godofgrunts/Linux/Linux3.jpg
Makes a very non-subjective claim that Windows 7 is compatible with Many Printers and Scanners -- as in, a large number, and Linux is compatible with few -- as in a small number. In fact, they display a bar graph for Windows and Linux compatibility; the graph for Windows is 100% full and the graph for Linux is 25% of full, indicating Linux is compatible with only 25% as many printers as Windows 7 is.
This is easily falsifiable by showing the large number of printers that Linux drivers are available for, the small number that drivers are unavailable for. And also showing the large number of printers Linux has drivers for that don't work in Windows 7 / Vista.
The same applies to Camera / mp3 player / iPod compatibility.
The claim Linux has no "Authorized support" available can also be shown to be false.
Telling lies is what's unethical, not promoting one product over another, that's fine, if done in a proper way.
Presumably, when best buy sells both Linux and Windows Netbooks, they would rather sell a Linux netbook than not make a sale, because the consumer thinks the Linux offering doesn't do what they want AND the Windows option is too expensive, they want to go elsewhere and shop around more.
They can lose the sale because of this.
Microsoft doesn't mind. They would rather the customer buys nothing from bestbuy than that they buy a Linux netbook.
They know if they can stop them from buying Linux long enough, they'll eventually buy some Windows from someone else; maybe they'll just wait 6 months until they can save up the extra money for that Windows netbook.
In any case, it hurts the customer.
It's so bad, that at some point the kernel literally got a "MAGIC NUMBER" define where a constant is stored in every module,
And the kernel refuses to load any module whose "magic number" doesn't match the compiled kernel's version and certain compile options, like PAE support, SMP support, Xen.
This is irritating.
The kernel should be maintaining an ability to load drivers compiled against earlier kernel versions.
And provide a framework to be able to compile driver modules without kernel sources.
It makes sense for them, it doesn't make sense for some customers who will be spending more money. This hurts the customer, and may ultimately erode their trust, when their friends show them their Linux netbook and all it can do (that the best buy people said it couldn't).
It's dishonest if their employees tell their customers these things in order to discourage them from buying the cheaper unit.
Touch the track pad with two fingers and push the button.
That's how you right click.
No, when you click the "auto upgrade" button, WP prompts you to enter the hostname, FTP username, and FTP password, to apply the upgrades.
Now, this does pose a security risk if your site is compromised (unbeknownst to you), and the attacker manages to use SQL injection to redirect you to a 'fake upgrade page'
When you click the upgrade button, and provide your credentials... the attacker has co-opted the web-ui, and you're sending the FTP username and password directly to the kiddie, giving them the means to completely pwn the site....