A known bug in the current version (1.3.1) prevents the restoration of individual files or directories from an archive.
How often do people want to restore the whole archive vs. just a single file? Almost never. This is pretty typical of "backup" solutions and how people implement them, they test the backup but rarely test that you can restore from same.
A Complaint for Declaratory Judgment was filed in the United States District Court, District of Nevada in Reno, Nevada on November 6, 2003 by Orbital Development of Carson City, Nevada against the United States of America, demanding the U.S.A. acknowledge that Asteroid 433, Eros has been lawfully owned by Gregory W. Nemitz since March 3, 2000. Seems Nemitz sent NASA a $20 parking ticket for landing thair NEAR-Shoemaker spacecraft on his asteroid on February 12, 2001 - a real deal, since the fee would have covered a full century of landing rights. But in this era of bloated Federal expenditures, a decision was made that paying such a fee just wasn't in the current Federal budget. On August 15, 2003 Department of State officially responded, stating by its interpretation of the United Nations' Outer Space Treaty of 1967 that Nemitz's "claim is without legal basis."
Gregory W. Nemitz disagrees. And the first interplanetary legal battle has been joined.
As reported by Space Frontier, the Complaint alleges that Nemitz was denied his Fifth, Ninth and Tenth Amendment rights protected by the Constitution. Nemitz asserts in the Court filings that "no treaty has ever abrogated, overthrown, or amended constitutional law" The suit is seeking $1,107 in damages, rulings to overturn the NASA and Department of State conclusions, and a ruling that Nemitz's Claim to ownership of the asteroid is a Lawful and valid Claim. The central issue of the case submitted to the Court is "Treaty vs. the Natural, Inherent Rights of Man" to acquire and own property. The side issue of whether actual possession is required prior recognized ownership, is moot in this regard. US District Judge Howard D. McKibben has been assigned to the action.
Nevada, of course, has a long history of legal miner claims and this one is in some ways no different. Orbital Development of Carson City is behind the so-called "Eros Project" to ultimately mine the resources of that distant rock, a mining claim they claim is worth $10 trillion.
Nemitz expects a jury to hear his case. For those of you who can take a little jaunt to Hawaii on short notice, Nemitz will speak about Property Rights in Space and Space Property Law at the International Lunar Conference in Hawaii on November 21, 2003. His presentation is titled "Developing Property Claims and Asteroid Eros", and presumably he will unveil some of his planned legal strategy for pursuing this case. While the rest of us are waiting on CONUS for Court TV coverage, here's something else of related interest...
I'll take a bet that IBM settles the case out of court.
Yeah, with SCO paying an undisclosed sum of money to IBM for SCO Unix infringing on IBM's intellectual property. IBM has patents on operating system methods coming out of their ears and it is almost impossible for SCO not to infringe upon it.
The only saving grace might be if SCO already licenses this technology from IBM, but IBM can still withdraw that license and screw SCO six ways from Sunday.
Putting aside the fact that many people just gave out their password when asked directly, they probably didn't go on and say "You didn't tell me your password right away, but here's this shiny new pen - will you tell me now?"
Instead it was probably something rather simple like a website that they were directed at which had an "appreciation award" or something, and they had to supply their password in order to "confirm" that they were the right person collecting the "award".
That is similar to tons of fake porn sites which "accept" your credit card for age verification and/or a minimal charge. They don't actually verify your credit card or charge you $3.99 for unlimited porn, but instead use the card numbers to buy other stuff.
Anyhow, it seems to me a horrible idea to set this sort of prescident. What's next? Coke gives a few bucks to the football team and suddenly all students have to undergo a session about the crisp, refreshing taste of Coke, Diet Coke and Sprite?
You may suggest this as a joke, but it pretty much already happened. At the University of Calgary, the Student's Union signed an agreement with Pepsi that required only Pepsi to be sold at all SU retail facilities (they control a large number of the food court areas) and all vending machines on campus.
They also tried to force us to stop selling Coke at the EE snack store, but we told them to go F*** themselves. Coke and late night hacking are inseparable.
so what's the point of running ext3 in writeback if (as the faq says) it's exactly equivalent to ext2 "with a very fast fsck"? So is the _only_ gain the fsck time?
Well, ext3 with data=writeback is equivalent to
how reiserfs has always operated (i.e. if you crash you can lose data in files that were being written to). Using data=ordered is an extra benefit that doesn't have any noticable performance hit unless you are trashing the disk and RAM in a benchmark. FYI, there are now beta patches for reiserfs that implement data=ordered.
Only the fsck time can be a big deal if you have to wait 8 hours while your 1TB storage array is fscking (8 hours is a guess, I don't have that much disk...)
You only need a special motherboard for hotswap PCI/CPU/RAM if you want your system to keep running, and your components to work afterwards;-).
Seriously, though, yes you need special hardware on the motherboard side (HP has hot-swap PCI system(s), and IBM has hot-swap everything but not for ia32 or ia64 class hardware). AFAIK, the CPU/RAM/PCI card itself does not need to be special, just the motherboard.
As for hot-swap RAM, it is _very_ hard to do this without special hardware support. You would need something like RAID for RAM + special hardware that would let you remove/install DIMMs live.
Seems to be pure FUD, AFAICS. I'm on all of the PNG lists, and while there was a brief flurry of
discussion about this at the same time the whole W3C RAND licensing issue was a big deal, there has
not been anything since then (unless, of course I was unsubscribed from the PNG lists without my
knowledge, hard to tell when you get a few hundred
linux-kernel emails a day).
In any case, no threats from Apple ever about PNG, just speculation and pre-emptive prior art
gathering on the part of the PNG group.
If your ethernet driver supports multicast under Linux (see Documentation/networking/multicast.txt
for an incomplete list of supported hardware, or
look for MULTICAST in the output of "ifconfig")
then all you need is a simple ethernet HUB to connect the test systems. If you have an ethernet
SWITCH, it may or may not support multicast.
After that, it is "simply" a matter of writing code which does multicast. Note that if you have
multiple interfaces on a host, you will need to
specify a route for the multicast communication.
The biggest flaw in this whole document is that the 378 million Christian children are evenly distributed across the earth. Only what, 40% of Earth's surface is land, and only 10% of that is habitable. Even so, Santa has manipulated society so that as the population has grown it actually becomes more centrally located (i.e. cities). Also, his job is made easier by the fact that the Christian cities themselves are clumped together.
Therefore, Santa only has to go about 20m between each house in suburbia (less for apartments) in each millisecond. Luckily, with constant acceleration between major cities, this time is relatively short compared to the large number of short hops between each house.
One of the problems with flash memory is that it has a limited lifespan, in terms of the number of writes that it can do. The lifespan should be in the 100's of thousands of writes, but if they did something bad like have a regular filesystem on the flash, and update the size of a file a few hundred times while it was being uploaded to the RIO, you will quickly wear out one part of the flash (e.g. block 0).
One of the ways you can avoid having a problem like this is to use a log-structured filesystem, which simply writes the data in one long loop around the device, rather than always starting
at the beginning of the device. The exact details escape me, but the general idea is correct.
One of the new Linux filesystems, JFFS (journalling flash filesystem) does this, I believe. It was accidentally added to the 2.4 development kernel recently when one of the developers working on a flash driver submitted a patch to Linus, and forgot to remove the JFFS code from his patch... (Please, no flamewar about reiserfs here, there was enough on lkml already).
I think that the sourceforge code is also available. It has a web bug tracking feature, CVS, etc. However, I don't think there is any kind of integration between CVS and the bug repository (although that would be a good feature).
We have developed a filesystem OBDFS (based on ext2) which HAS snapshot capability, among other things. Its GPL, and available at http://www.lustre.org/ for download.
What we have done is split the ext2 filesystem into two layers:
the VFS interface, which knows about files and directories
the disk interface, which knows about files, blocks, and bitmaps
What this allows is for the on-disk data handling to be abstracted from what the mounted filesystem looks like, so we can do RAID/mirroring, snapshots, RPC (remote access like NFS), encryption, etc, just by stacking a small mid-level driver between the filesystem and the disk. Currently we have snapshots implemented, and RPC is in progress. The snapshots let you mount several "versions" of your filesystem, with all of the older copies being read-only filesystems.
It is definitely NOT for production yet, but OK to play with. A regular OBDFS filesystem can be mounted as ext2 and vice versa, but a snapshot filesystem cannot be mounted/fscked by the normal ext2 tools, unfortunately, although this may change in the future.
I looked at the jobs page for LinuxOpen, and it appears that they have copied the exact text for several positions from the jobs page at Red Hat. Obviously, they have no clue what they are doing, since they don't even know who to hire - they only know that "the other" Linux company wants this type of people, so they must want them too.
I have at least a couple of pieces of software that I was a major contributor to that Red Hat ships, namely libpng, the Linux/Unix support for POV-Ray 3 and PVMPOV (on Extreme Linux at least, not sure of normal dist). Am I to assume that I should have been sent an email about this, or what are the exact "qualifications" for being considered a developer? I've always thought that I would like to own Red Hat stock from years ago, but it was always privately held, and now that it goes public, I'm screwed.
If I had heard earlier that developers were in on the game, I would have made an effort to get on the list. I thought it had only been for certain Red Hat customers, and I haven't installed Linux on my home box since Slackware 2.x days (1995), so I don't think Red Hat was even a name back then.
I guess my instincts about going with Debian for my next installation were right...
Have a look at the ADSM home page for more info. The ADSM server needs to run on a non-Linux box (AIX, HP/UX, Solaris, NT), but it has a Linux client, as well as clients for most OSes, and also lots of database back-ends (DB/2, Oracle, Sybase, SQL Server, Notes, Exchange).
The quote from the article that really cracks me up is:
Wanke: Until Single IP, we were just like everyone else: we never had a 100 percent day. Never.
You mean to say that their much-beloved NT/IIS can't last a single day without crashing or otherwise failing in some way? This makes me think more and more that the Mindcraft benchmark should be run over several days or weeks, and we get to see how often NT dies.
How about these 3hr CHKDSKs on the 36GB disks? Isn't NTFS supposed to be a logging filesystem? If so, why does it take 3 hours to check the filesystem? Granted that ext2 would also do a long fsck on its filesystems, but at least it doesn't pretend to be something it isn't.
The failover is part of PVMPOV, and has nothing to do with the configuration of the systems. It was coded this way because it used to run on a room full of unreliable machines that ran at wildly different speeds that other people were using, and even if the machine didn't die, it was possible that a system was busy with other things at the time, so I didn't want to wait for renderings to finish when other CPUs were idle... Check out the PVMPOV Home Page for more info. Yes, 32s was impressive at one time (it used to be at the top of the list).
If you have any experience with AIX, you will know what a "mksysb" is. This is a system backup which stores as the first file in the backup the complete LOGICAL disk "partition" information. Since you can boot from tapes on RS/6000 machines, you can do a bare-metal restore from tape, and it creates all of the "partitions"/filesystems for you, and restores all of the files too. Of course, AIX uses a logical volume manager, so the concept of a "partition" isn't quite the same. However, an LVM implementation for Linux is available already (http://linux.msede.com/lvm/), so check it out too. My nascent idea is to make something like mksysb on Linux with LVM, so you can install straight from tape backup (with a boot floppy I guess) and have it set up partitions for you already, like AIX.
Slashdot Mirror
How often do people want to restore the whole archive vs. just a single file? Almost never. This is pretty typical of "backup" solutions and how people implement them, they test the backup but rarely test that you can restore from same.
A Complaint for Declaratory Judgment was filed in the United States District Court, District of Nevada in Reno, Nevada on November 6, 2003 by Orbital Development of Carson City, Nevada against the United States of America, demanding the U.S.A. acknowledge that Asteroid 433, Eros has been lawfully owned by Gregory W. Nemitz since March 3, 2000. Seems Nemitz sent NASA a $20 parking ticket for landing thair NEAR-Shoemaker spacecraft on his asteroid on February 12, 2001 - a real deal, since the fee would have covered a full century of landing rights. But in this era of bloated Federal expenditures, a decision was made that paying such a fee just wasn't in the current Federal budget. On August 15, 2003 Department of State officially responded, stating by its interpretation of the United Nations' Outer Space Treaty of 1967 that Nemitz's "claim is without legal basis."
Gregory W. Nemitz disagrees. And the first interplanetary legal battle has been joined.
As reported by Space Frontier, the Complaint alleges that Nemitz was denied his Fifth, Ninth and Tenth Amendment rights protected by the Constitution. Nemitz asserts in the Court filings that "no treaty has ever abrogated, overthrown, or amended constitutional law" The suit is seeking $1,107 in damages, rulings to overturn the NASA and Department of State conclusions, and a ruling that Nemitz's Claim to ownership of the asteroid is a Lawful and valid Claim. The central issue of the case submitted to the Court is "Treaty vs. the Natural, Inherent Rights of Man" to acquire and own property. The side issue of whether actual possession is required prior recognized ownership, is moot in this regard. US District Judge Howard D. McKibben has been assigned to the action.
Nevada, of course, has a long history of legal miner claims and this one is in some ways no different. Orbital Development of Carson City is behind the so-called "Eros Project" to ultimately mine the resources of that distant rock, a mining claim they claim is worth $10 trillion.
Nemitz expects a jury to hear his case. For those of you who can take a little jaunt to Hawaii on short notice, Nemitz will speak about Property Rights in Space and Space Property Law at the International Lunar Conference in Hawaii on November 21, 2003. His presentation is titled "Developing Property Claims and Asteroid Eros", and presumably he will unveil some of his planned legal strategy for pursuing this case. While the rest of us are waiting on CONUS for Court TV coverage, here's something else of related interest...
I find it highly ironic that slashdot is such a "pro-OSS" and "anti-patent" site, yet they use GIF instead of PNG images. Talk about hypocritical.
Yeah, with SCO paying an undisclosed sum of money to IBM for SCO Unix infringing on IBM's intellectual property. IBM has patents on operating system methods coming out of their ears and it is almost impossible for SCO not to infringe upon it.
The only saving grace might be if SCO already licenses this technology from IBM, but IBM can still withdraw that license and screw SCO six ways from Sunday.
Putting aside the fact that many people just gave out their password when asked directly, they probably didn't go on and say "You didn't tell me your password right away, but here's this shiny new pen - will you tell me now?"
Instead it was probably something rather simple like a website that they were directed at which had an "appreciation award" or something, and they had to supply their password in order to "confirm" that they were the right person collecting the "award".
That is similar to tons of fake porn sites which "accept" your credit card for age verification and/or a minimal charge. They don't actually verify your credit card or charge you $3.99 for unlimited porn, but instead use the card numbers to buy other stuff.
You may suggest this as a joke, but it pretty much already happened. At the University of Calgary, the Student's Union signed an agreement with Pepsi that required only Pepsi to be sold at all SU retail facilities (they control a large number of the food court areas) and all vending machines on campus.
They also tried to force us to stop selling Coke at the EE snack store, but we told them to go F*** themselves. Coke and late night hacking are inseparable.
Well, ext3 with data=writeback is equivalent to how reiserfs has always operated (i.e. if you crash you can lose data in files that were being written to). Using data=ordered is an extra benefit that doesn't have any noticable performance hit unless you are trashing the disk and RAM in a benchmark. FYI, there are now beta patches for reiserfs that implement data=ordered.
Only the fsck time can be a big deal if you have to wait 8 hours while your 1TB storage array is fscking (8 hours is a guess, I don't have that much disk...)
You only need a special motherboard for hotswap PCI/CPU/RAM if you want your system to keep running, and your components to work afterwards ;-).
Seriously, though, yes you need special hardware on the motherboard side (HP has hot-swap PCI system(s), and IBM has hot-swap everything but not for ia32 or ia64 class hardware). AFAIK, the CPU/RAM/PCI card itself does not need to be special, just the motherboard.
As for hot-swap RAM, it is _very_ hard to do this without special hardware support. You would need something like RAID for RAM + special hardware that would let you remove/install DIMMs live.
Seems to be pure FUD, AFAICS. I'm on all of the PNG lists, and while there was a brief flurry of
discussion about this at the same time the whole W3C RAND licensing issue was a big deal, there has
not been anything since then (unless, of course I was unsubscribed from the PNG lists without my
knowledge, hard to tell when you get a few hundred
linux-kernel emails a day).
In any case, no threats from Apple ever about PNG, just speculation and pre-emptive prior art
gathering on the part of the PNG group.
If your ethernet driver supports multicast under Linux (see Documentation/networking/multicast.txt
for an incomplete list of supported hardware, or
look for MULTICAST in the output of "ifconfig")
then all you need is a simple ethernet HUB to connect the test systems. If you have an ethernet
SWITCH, it may or may not support multicast.
After that, it is "simply" a matter of writing code which does multicast. Note that if you have
multiple interfaces on a host, you will need to
specify a route for the multicast communication.
The biggest flaw in this whole document is that the 378 million Christian children are evenly distributed across the earth. Only what, 40% of Earth's surface is land, and only 10% of that is habitable. Even so, Santa has manipulated society so that as the population has grown it actually becomes more centrally located (i.e. cities). Also, his job is made easier by the fact that the Christian cities themselves are clumped together. Therefore, Santa only has to go about 20m between each house in suburbia (less for apartments) in each millisecond. Luckily, with constant acceleration between major cities, this time is relatively short compared to the large number of short hops between each house.
One of the ways you can avoid having a problem like this is to use a log-structured filesystem, which simply writes the data in one long loop around the device, rather than always starting at the beginning of the device. The exact details escape me, but the general idea is correct.
One of the new Linux filesystems, JFFS (journalling flash filesystem) does this, I believe. It was accidentally added to the 2.4 development kernel recently when one of the developers working on a flash driver submitted a patch to Linus, and forgot to remove the JFFS code from his patch... (Please, no flamewar about reiserfs here, there was enough on lkml already).
I think that the sourceforge code is also available. It has a web bug tracking feature, CVS, etc. However, I don't think there is any kind of integration between CVS and the bug repository (although that would be a good feature).
What we have done is split the ext2 filesystem into two layers:
What this allows is for the on-disk data handling to be abstracted from what the mounted filesystem looks like, so we can do RAID/mirroring, snapshots, RPC (remote access like NFS), encryption, etc, just by stacking a small mid-level driver between the filesystem and the disk. Currently we have snapshots implemented, and RPC is in progress. The snapshots let you mount several "versions" of your filesystem, with all of the older copies being read-only filesystems.
It is definitely NOT for production yet, but OK to play with. A regular OBDFS filesystem can be mounted as ext2 and vice versa, but a snapshot filesystem cannot be mounted/fscked by the normal ext2 tools, unfortunately, although this may change in the future.
I looked at the jobs page for LinuxOpen, and it appears that they have copied the exact text for several positions from the jobs page at Red Hat. Obviously, they have no clue what they are doing, since they don't even know who to hire - they only know that "the other" Linux company wants this type of people, so they must want them too.
If I had heard earlier that developers were in on the game, I would have made an effort to get on the list. I thought it had only been for certain Red Hat customers, and I haven't installed Linux on my home box since Slackware 2.x days (1995), so I don't think Red Hat was even a name back then.
I guess my instincts about going with Debian for my next installation were right...
Have a look at the ADSM home page for more info. The ADSM server needs to run on a non-Linux box (AIX, HP/UX, Solaris, NT), but it has a Linux client, as well as clients for most OSes, and also lots of database back-ends (DB/2, Oracle, Sybase, SQL Server, Notes, Exchange).
The quote from the article that really cracks me up is:
Wanke: Until Single IP, we were just like everyone else: we never had a 100 percent day. Never.
You mean to say that their much-beloved NT/IIS can't last a single day without crashing or otherwise failing in some way? This makes me think more and more that the Mindcraft benchmark should be run over several days or weeks, and we get to see how often NT dies.
How about these 3hr CHKDSKs on the 36GB disks? Isn't NTFS supposed to be a logging filesystem? If so, why does it take 3 hours to check the filesystem? Granted that ext2 would also do a long fsck on its filesystems, but at least it doesn't pretend to be something it isn't.
The failover is part of PVMPOV, and has nothing to do with the configuration of the systems. It was coded this way because it used to run on a room full of unreliable machines that ran at wildly different speeds that other people were using, and even if the machine didn't die, it was possible that a system was busy with other things at the time, so I didn't want to wait for renderings to finish when other CPUs were idle... Check out the PVMPOV Home Page for more info. Yes, 32s was impressive at one time (it used to be at the top of the list).
If you have any experience with AIX, you will know what a "mksysb" is. This is a system backup which stores as the first file in the backup the complete LOGICAL disk "partition" information. Since you can boot from tapes on RS/6000 machines, you can do a bare-metal restore from tape, and it creates all of the "partitions"/filesystems for you, and restores all of the files too. Of course, AIX uses a logical volume manager, so the concept of a "partition" isn't quite the same. However, an LVM implementation for Linux is available already (http://linux.msede.com/lvm/), so check it out too. My nascent idea is to make something like mksysb on Linux with LVM, so you can install straight from tape backup (with a boot floppy I guess) and have it set up partitions for you already, like AIX.