This is not a problem for the most important Linux systems which are not dual boot.
Most systems that are dual boot are workstations, not servers.
Meaning the person who uses the system every day is most likely using Linux.
I think the solution is for the Linux installer to create Windows icons and a Start menu item group with two things....
A "boot Linux" icon (for launching loadlin)
And a "fix grub" icon, for fixing grub, no matter what some dastardly windows program has done to it.
Nothing is supposed to be there except the user-installed system boot code, boot data, and hard drive parameters.
Third party software certainly has no business messing with Sector 0 or the boot blocks unless it gets explicit permission,
advises users of the risks in messing with the boot block, prompts the user to back anything up that's there right now,
and writes its bits only to the portion of the boot block that is provided for its required purpose.
It may detect bootloaders, and update their configuration, if the user accepts that, but bootloader configuration is generally stored on the boot volume not the boot block
I personally would love some backup protection against accidentally leaving a young child in the vehicle on a hot day
That sounds like a vehicle feature.
Use infrared-based detectors intersecting with each seat to monitor for living beings being present in the car.
If the temperature gauge is too high or too low, the vehicle is off, and nobody is in the driver's seat, then sound a dedicated alarm tone for 5 minutes, audible from outside and inside the vehicle.
Oh.. I said 'they can be used'... not that we have no recourse, or that it is legal.
The problem is they can do a lot of spread out harm in the mean time / interrim until someone reacts to try to fix this wrong.
Seems like a textbook case for a class-action suit though.
The problem is it needs to be proven in court that the X-rays harmed a lot of people, or legislative action, before anything gets done.
Which is hard when they are allowed to operate these things in secrecy,
and the harmful effects are so spread out, that nobody can prove The gov't X-ray is the one thing that caused cancer or sterility for them;
since there are so many other variables involved.
The problem with lead-based paints is they are illegal, are they not?
You could put the barrier behind the glass front window.
The only question is: How do these scanners work, and How can we make them unable to see into our vehicles and other private places ?
Is there a material we can apply to the walls in our house and the windows + frames of our vehicles to negate the utility of these scanners against our possessions?
Yes, one method shadow copy uses is COW.
Shadow copy is not NTFS.
It is a volume-level mechanism that lies under the NTFS file system.
There is an area for files, and there is a volume shadow copy region on each volume.
There are two methods shadow copy can be implemented, one involves re-directing writes to the reserved region. Copy on write is the other option.
It's worth mentioning that the latest version of Windows Server (2008 R2) is 64-bit only as well.
And ZFS has always had 64-bit as minimum system requirements for production systems, even on Solaris.
That is, 32-bit is considered okay for limited testing, unsuitable for production use, particularly for use with zpools larger than a few hundred GB in size or so.
If you have a 1TB or larger storage pool with ZFS, you need 2gb of RAM and a 64-bit CPU to have something acceptable and stable.
This is true whether you used Solaris or BSD.
I consider it a good thing that the person porting to Linux is actually enforcing the basic 64-bit requirement.
Maybe fewer people who don't read docs and 'system requirements' sheets will get burned that way,
by not noticing that "32-bit is not suitable for enterprise use",
and say ZFS on Linux 'sucks', because they screwed up basic configuration and deployment requirements ?
Because ZFS is not production quality on a 32-bit CPU or with less than at least additional 2GB of RAM available for ARC,
even on Solaris where ZFS is most mature. Bare minimum for ZFS: 1Gb RAM, 64bit proc.
If you have a 32-bit CPU or less than 2GB system RAM, use UFS or Ext3, forget about ZFS for such hardware configurations, unless you want to experience pain (system hangs, memory starvation, crashes / Panics due to 32-bit address space squeeze causing fragmentation and ultimately inability to allocate ARC efficiently).
That doesn't stop them from pursuing more claims against targets they perceive to be vulnerable.
If they think they can get a quick win or quick settlement with BSD folks (to stop distributing), they will do so, and then use it as leverage to attempt to reach a settlement with Oracle.
Probably requiring Oracle to get out of the storage business and stop making ZFS available to ISVs/partners to build NASes with, or as open source
The MPEG LA says it will continue to collect fees on AVC/H.264 video that consumers pay for. The video format is used on Blu-Ray discs and on most on-demand and paid video delivery services, such as iTunes. It will also continue to collect fees from software that ships with the coders and decoders required to play H.264 video — even software that’s distributed for free, such as web browsers.
I don't know if that's true. I know you probably can't redistribute the kernel with the CDDL bits
Just like you can't distribute a Linux distribution and include nVidia drivers?
Tell that to the distros.
But I think it may fall on death ears. Or you might hear back a reminder that mere aggregation on a storage medium is exempted in the GPL... as long as the non-free package is separated from the GPL'd package.
In fact, GLIBC has some nastier bugs than.NET, which lead to remotely exploitable vulnerabilities in network software and privilege escalation vulnerabilities caused by GLIBC.
Under the guise of "helping citizens to develop better detection and understanding of Weapons of Mass Destruction"
Surely weapons of mass destruction do less damage, if they're better understood, and more people know about what techniques are need to make them and how to get around pitfalls and difficulties in constructing WMDs, right?
You're prepared to tell me there are no bugs in the most recent version of GNU Libc, Win32 API or Java SDK? None? Zero? Nil?
It's software. It has bugs. In this case, bugs that pop up in critical places and can't be hammered into place without avoiding Glibc, Win32, or Java, for that feature entirely.
You can't get a 10-Gibabit USB 3.0 Ethernet adapter and download files at 1.2 gigabytes / second.
By the time we have devices and computers actually shipping using the USB 3.0 standard, 1 Gigabit Ethernet will be what 10 Megabit Ethernet is today... obsoleted, and slow as hell...
long since replaced by 100 Gbit.
Trading files with BitTorrent is illegal, and if you were caught, you could be prosecuted under the NET act and go to jail for 5 years, or have to pay a $250,000 fine.
Or (more likely) be sued by the MPAA for the statutory amount of civil damages.
Presumably if you watch the video on a for-pay site,
part of your payment goes to properly licensing the content.
Slashdot Mirror
This is not a problem for the most important Linux systems which are not dual boot.
Most systems that are dual boot are workstations, not servers. Meaning the person who uses the system every day is most likely using Linux.
I think the solution is for the Linux installer to create Windows icons and a Start menu item group with two things.... A "boot Linux" icon (for launching loadlin)
And a "fix grub" icon, for fixing grub, no matter what some dastardly windows program has done to it.
Nothing is supposed to be there except the user-installed system boot code, boot data, and hard drive parameters.
Third party software certainly has no business messing with Sector 0 or the boot blocks unless it gets explicit permission, advises users of the risks in messing with the boot block, prompts the user to back anything up that's there right now, and writes its bits only to the portion of the boot block that is provided for its required purpose.
It may detect bootloaders, and update their configuration, if the user accepts that, but bootloader configuration is generally stored on the boot volume not the boot block
There's an easier more elegant way than machining a new case to fix a battery cover, that's for sure.
I personally would love some backup protection against accidentally leaving a young child in the vehicle on a hot day
That sounds like a vehicle feature.
Use infrared-based detectors intersecting with each seat to monitor for living beings being present in the car.
If the temperature gauge is too high or too low, the vehicle is off, and nobody is in the driver's seat, then sound a dedicated alarm tone for 5 minutes, audible from outside and inside the vehicle.
Oh.. I said 'they can be used'... not that we have no recourse, or that it is legal. The problem is they can do a lot of spread out harm in the mean time / interrim until someone reacts to try to fix this wrong.
Seems like a textbook case for a class-action suit though.
The problem is it needs to be proven in court that the X-rays harmed a lot of people, or legislative action, before anything gets done. Which is hard when they are allowed to operate these things in secrecy, and the harmful effects are so spread out, that nobody can prove The gov't X-ray is the one thing that caused cancer or sterility for them; since there are so many other variables involved.
The problem with lead-based paints is they are illegal, are they not?
You could put the barrier behind the glass front window.
Neither. The use of these is already illegal
Aren't there electronic devices that can detect X-rays?
Perhaps they could be countered by emitting an EM burst or EMP in the direction X-rays were detected in.
The only question is: How do these scanners work, and How can we make them unable to see into our vehicles and other private places ?
Is there a material we can apply to the walls in our house and the windows + frames of our vehicles to negate the utility of these scanners against our possessions?
OpenSolaris ZFS Screencast: 100 Mirrored Filesystems in 5 minutes
OpenSolaris Screencast: ZFS Self Healing
Oracle Demo: ZFS Discovery Day
Presentation: (PDF) ZFS: The Last Word in File Systems (2008)
Presentation (VIDEO) ZFS: The Last Word in File Systems" (2008)
Nexenta 3.0 webinar (Slide 18, Deduplication)
Sun ZFS drive destruction Demo
You ready to try it on a live Oracle database server with a 10TB filesystem that averages at least say 5,000 DB transactions per second? :)
I/O is only frozen for 10 seconds. I'm sure Microsoft has an article about this
Yes, one method shadow copy uses is COW. Shadow copy is not NTFS.
It is a volume-level mechanism that lies under the NTFS file system. There is an area for files, and there is a volume shadow copy region on each volume.
There are two methods shadow copy can be implemented, one involves re-directing writes to the reserved region. Copy on write is the other option.
It's worth mentioning that the latest version of Windows Server (2008 R2) is 64-bit only as well.
And ZFS has always had 64-bit as minimum system requirements for production systems, even on Solaris.
That is, 32-bit is considered okay for limited testing, unsuitable for production use, particularly for use with zpools larger than a few hundred GB in size or so.
If you have a 1TB or larger storage pool with ZFS, you need 2gb of RAM and a 64-bit CPU to have something acceptable and stable. This is true whether you used Solaris or BSD.
I consider it a good thing that the person porting to Linux is actually enforcing the basic 64-bit requirement. Maybe fewer people who don't read docs and 'system requirements' sheets will get burned that way, by not noticing that "32-bit is not suitable for enterprise use", and say ZFS on Linux 'sucks', because they screwed up basic configuration and deployment requirements ?
ZFS is just about as "production ready" on the latest stable release of FreeBSD, as BtrFS is "Production Ready" on the latest Linux kernel release.
Because ZFS is not production quality on a 32-bit CPU or with less than at least additional 2GB of RAM available for ARC, even on Solaris where ZFS is most mature. Bare minimum for ZFS: 1Gb RAM, 64bit proc.
If you have a 32-bit CPU or less than 2GB system RAM, use UFS or Ext3, forget about ZFS for such hardware configurations, unless you want to experience pain (system hangs, memory starvation, crashes / Panics due to 32-bit address space squeeze causing fragmentation and ultimately inability to allocate ARC efficiently).
That doesn't stop them from pursuing more claims against targets they perceive to be vulnerable. If they think they can get a quick win or quick settlement with BSD folks (to stop distributing), they will do so, and then use it as leverage to attempt to reach a settlement with Oracle.
Probably requiring Oracle to get out of the storage business and stop making ZFS available to ISVs/partners to build NASes with, or as open source
I meant deaf ears, mainly because the distros. ignored whatever complaints they got and continued to include non-GPL-compatible drivers.
Free web browsers like Chrome and Firefox are still going to have to pay royalties.
From More detailed webmonkey.com article:
I don't know if that's true. I know you probably can't redistribute the kernel with the CDDL bits
Just like you can't distribute a Linux distribution and include nVidia drivers? Tell that to the distros.
But I think it may fall on death ears. Or you might hear back a reminder that mere aggregation on a storage medium is exempted in the GPL... as long as the non-free package is separated from the GPL'd package.
In fact, GLIBC has some nastier bugs than .NET, which lead to remotely exploitable vulnerabilities in network software and privilege escalation vulnerabilities caused by GLIBC.
Under the guise of "helping citizens to develop better detection and understanding of Weapons of Mass Destruction"
Surely weapons of mass destruction do less damage, if they're better understood, and more people know about what techniques are need to make them and how to get around pitfalls and difficulties in constructing WMDs, right?
You're prepared to tell me there are no bugs in the most recent version of GNU Libc, Win32 API or Java SDK? None? Zero? Nil?
It's software. It has bugs. In this case, bugs that pop up in critical places and can't be hammered into place without avoiding Glibc, Win32, or Java, for that feature entirely.
You mean Microsoft is moving away from .NET version 2.0.
This is like saying Oracle is moving away from Java, because version 1.4 or 1.5 was declared EOL.
You can't get a 10-Gibabit USB 3.0 Ethernet adapter and download files at 1.2 gigabytes / second.
By the time we have devices and computers actually shipping using the USB 3.0 standard, 1 Gigabit Ethernet will be what 10 Megabit Ethernet is today... obsoleted, and slow as hell... long since replaced by 100 Gbit.
The part that's better is it's actually legal.
Trading files with BitTorrent is illegal, and if you were caught, you could be prosecuted under the NET act and go to jail for 5 years, or have to pay a $250,000 fine.
Or (more likely) be sued by the MPAA for the statutory amount of civil damages.
Presumably if you watch the video on a for-pay site, part of your payment goes to properly licensing the content.