You mean high CPU utilization on a bunch of read/write requests? That's normal. We have the ability to stream reads and writes on a medium for quite some time now, both in win32 land, as well as others.
A judge ruled a while ago (don't have the link at the moment) that attempted rape is a real threat to your life, as you can catch a STD from that person. Therefore, you can use lethal force if you, or someone else, is being raped. I believe the case was a mother who killed the person who was raping her daughter. I think she killed him with a lamp.
With NTFS permissions, you can set group permissions to an object, as well as multiple user settings. For instance, Bob and Jill are both in group Secretaries:
This set of permissions cannot be done in Unix/Linux, without using another solution other than FS permissions. In addition, NTFS permissions are more detailed and complex than RWX, you have:
Change Owner/Permissions of Object
Execute and View Directory are Seperate permissions
and Read Permissions of Object
Which UNIX/Linux does not have natively. I believe you can achieve the same thing (except for the special permissions) using SELinux.
My uncle used to do the same thing, except he would ask the cashier if they accepted Legal Tender Notes, which is basically $. The cashier usually would just shrug, and my uncle would then rip out the $ and pay her. He did it to the cashier though, not the waitress.
It was in the 60s in Laurel, Montana this weekend. It is supposed to be anywhere from -20 to 20 degreeds F. I think our increase of 80 or so degrees is higher than your 20 degree hit.
(I'm the type that creates one big ass partition for/). The -l switch tells tar to stay on the same FS, as/backup is NFS mounted to a RAID array. Thus, I just backup the local machine, without having to specify which directories to backup, and which to skip.
Restoration, I do the lazy way:
mkdir test
cd test
tar -xvf/backup/whatever.tar
and then I grab the files (the RAID array usually has plenty of space).
Linux 2.6 has more drivers than XP. Compare the list of "out of the box" supported hardware, and you can easily see that Linux supports more devices w/o requiring a seperate driver from the manufacturer.
Forgot to mention what he used for output: an old VB II braille unit. Had a RS-232 port on it (hence the COM port trick). And make that &2> instead of &>.
I have a blind friend that used lynx, bash, etc on a Linux box. All the extra setup took was just a :
sh &>/dev/ttyS0
And he was up and running. I will admit though that he is a bit of a *NIX guy, and already owned a shell account (was new to Linux, but had used UNIX before). He's not a wizard granted, but he knew what he had to.
ipchains, iptables, kernel 2.2 and 2.4 are all on the installation medium. Despite popular belief, 2.4 is indeed in stable (2.4.18), and has been for quite some time.
Most RFID readers are not designed to operate in the presence of another reader that is also scanning for tags. To date, this has not been a significant problem, as RFID has been in limited deployment without much opportunity for readers to interfere with each other. As electronic tags become more common, however, readers will be deployed on a larger scale, effectively garbling the data for systems in proximity to each other. This problem will become particularly serious if many mobile hand-readers are in use within close range of each other. Standards will be needed to define a protocol to allow these systems to share the available bandwidth, perhaps based on a wireless CSMA (carrier sense multiple access) protocol. ISO is addressing these issues, but details are beyond the scope of this article.
Further, improvements can be made when interpreting the tag signals received at the reader, intelligently filtering out noise. Application of advanced data-coding techniques in the tag electronics may also improve noise immunity and allow some multitag signal collisions to be separated and interpreted correctly. This may require more costly signal processing in the reader, but the benefits of greater accuracy will eventually lead to acceptance by a larger market and will drive the cost back down again.
Product Packaging Independence
In contrast to RFID, bar codes can be printed on a label and still be readable independent of the contents of the product or packaging. RFID, on the other hand, can be disrupted by materials in the product itself. Because tags use tuned RF circuits to receive interrogation signals, it is possible to detune or attenuate the signals if placed next to certain types of packaging. Ferrous metals are some of the worst offenders--RFID and canned foods are not a good combination. This problem is a challenging one, as the most obvious solution is to change the packaging material, but clearly some products do not have economic alternatives to metal, or metallized packaging, particularly where robustness and airtight storage is required. It will be interesting to see if the popular use of RFID eventually has an effect on the materials used for industrial packaging, or if material science can provide a material to isolate the effect of a product on a tag.
Multiple Standards
As noted earlier, several frequencies and standards have been used for RFID tagging solutions--for example, the popular ISO 14443 standard that operates at 13.56 MHz, the EPCglobal (96-bit) 915-MHz standard, and several others. In an ideal world, industry would adopt one standard; however, there are cost trade-offs, national frequency use restrictions, and politics that keep several of these active in their own commercial domain. For example, while Wal-Mart is considering adoption of the EPCglobal standard, Nokia (the largest cellphone manufacturer in the world) is about to release a cellphone that incorporates an RFID reader based on the ISO 14443 standard. The combination allows callers to scan posters and stickers that contain an embedded tag and buy the depicted products with the charge appearing automatically on their next phone bill. A solution to this standardization problem is to build readers that can operate using multiple standards, perhaps automatically searching for tags across a number of frequency bands using a suite of protocols, and be programmable, allowing them to adjust to national frequency restrictions.
Data Formats
Although the data format returned by read-only tags is defined by standards, the writable tags provide flash memory that customers can use in a proprietary way. There are potential benefits to standardizing the way data is represented here, perhaps allowing information to be shared or passed among independent organizations as it moves through a supply chain. For example, a product might move from the factory by road, air, and then road again to a warehouse in a foreign country, and finally
Moving Forward EXTENDING RFID APPLICATIONS: SENSORS, SECURITY, AND MEMORY
RFID provides a data transport mechanism between a tag and a reader, which can be extended to provide greater utility than returning a simple identification number. The three important extensions of electronic tagging are: sensing the environment, security, and electronic memory.
Sensors
The addition of a physical sensor to a tag has been an important development, providing the capability for a storeowner to learn something about the conditions a product has experienced in the past, at the time its tag is interrogated. Consider a frozen chicken that is being transported to a store. If the refrigeration of the transporter truck fails on the road, the chicken may well begin to defrost and potentially be contaminated by bacterial growth. By incorporating a temperature-sensitive material into the tag, and electronics that can detect a change in its state (e.g., its electrical resistance might permanently increase), it is possible to determine which of the chickens could be contaminated. Not only is the customer protected in this situation, but some of the product might also be saved if the sensors show critical temperatures were not exceeded, perhaps in a more insulated part of the truck. In this case, it is also a win for the meat company and the retail stores. KSW-Microtec in Germany produces an RFID tag called TempSens that is based on these principles and is being trialed by a European pharmaceutical company.
Security
Packaging of modern products is frequently associated with tamper-protecting mechanisms to alert a customer if a product has been opened between the factory and time of purchase. In this way, consumers can be warned that something may have been removed from the package, or more seriously, that the product may have been deliberately contaminated. By combining RFID with a switch--perhaps a simple wire attached to the tag and the packaging that is broken when the product is opened--a tag can indicate the suspicious conditions when read at the time of purchase. If the same tagged product has been interrogated earlier by other readers, the read times can be used to determine roughly when the product was tampered with, perhaps leading to the apprehension of the perpetrator. The U.S. Food and Drug Administration has recommended that RFID be considered for the protection of pharmaceutical products.
Memory
Stable storage, in the form of a read/write memory based on EEPROM (electrically erasable programmable read-only memory), is a relatively straightforward addition to an electronic tag, without any need to modify its encapsulation. Sensor tags, by contrast, require additional components that are not easily integrated, and the encapsulation needs to be carefully redesigned to accommodate them. Adding user-programmable memory to a tag opens up many new possibilities for its use. It can be used to store information that remains associated with a tagged product without the need for factories, shipping companies, retail stores, and customers to share a common database to find information about its history. For example, if a car's VIN (vehicle identification number) were stored in an RFID tag, the name of each owner of the car could be stored alongside it, providing an ownership record over the lifetime of the car; it remains with the car and cannot easily be lost. Service information could be stored in a similar way, and independent garages would be able to find out about any prior service history to help guide their work. Read/write RFID tags are available from many companies including Philips, Texas Instruments TIRIS, and Gemplus; however, there are no standards in place that advise a customer how this memory should be used. ISSUES TO BE RESOLVED WITH RFID
Given everything you have read so far, you may have been led to believe that apart from cost, the remaining technical issues for RFID are all solved. A number of issues, however, still present a challenge: tag orientation, r
Slashdot Mirror
Why do you say it has to run on CE? Opera does have a port for Linux you know....
You mean high CPU utilization on a bunch of read/write requests? That's normal. We have the ability to stream reads and writes on a medium for quite some time now, both in win32 land, as well as others.
A judge ruled a while ago (don't have the link at the moment) that attempted rape is a real threat to your life, as you can catch a STD from that person. Therefore, you can use lethal force if you, or someone else, is being raped. I believe the case was a mother who killed the person who was raping her daughter. I think she killed him with a lamp.
With NTFS permissions, you can set group permissions to an object, as well as multiple user settings. For instance, Bob and Jill are both in group Secretaries:
Bob: rwx
Jill: -wx
Secretaries: r-x
Everybody: ---
This set of permissions cannot be done in Unix/Linux, without using another solution other than FS permissions. In addition, NTFS permissions are more detailed and complex than RWX, you have:
Change Owner/Permissions of Object
Execute and View Directory are Seperate permissions
and Read Permissions of Object
Which UNIX/Linux does not have natively. I believe you can achieve the same thing (except for the special permissions) using SELinux.
Guerilla warfare was what the Americans first used against the British.....
Yeah, mine have the same thing:
5 2:00:08 AM:1.0.501
7::ln 10:Out of memory::gcasDtServ:ScheduleScans:Update::1/21/200
About 50-60 of those in the file.
If I recall correctly, IE7 will only run on XP or Longhorn, correct? What about Windows 2000, which is still "fully supported"?
c:\Program Files\Microsoft AntiSpyware\errors.log
I think it is a problem specific to his PC, as mine was about 4 KB.
If you're running Exchange 2003, it comes with Outlook 2003.
That is a domain name, not a TLD. A Top Level Domain is .net, .org, etc.
My uncle used to do the same thing, except he would ask the cashier if they accepted Legal Tender Notes, which is basically $. The cashier usually would just shrug, and my uncle would then rip out the $ and pay her. He did it to the cashier though, not the waitress.
It was in the 60s in Laurel, Montana this weekend. It is supposed to be anywhere from -20 to 20 degreeds F. I think our increase of 80 or so degrees is higher than your 20 degree hit.
I was stating the rule, not the practice. Yes, I am fully aware that the only thing that will save this country is a full-out revolution.
Bullshit. You have 24 hours (maybe less, can't remember to be exact) before they have to let you go if they don't charge you with a crime.
tar -lcvf /backup/$HOSTNAME-$DATE.tar /
/). The -l switch tells tar to stay on the same FS, as /backup is NFS mounted to a RAID array. Thus, I just backup the local machine, without having to specify which directories to backup, and which to skip.
/backup/whatever.tar
(I'm the type that creates one big ass partition for
Restoration, I do the lazy way:
mkdir test
cd test
tar -xvf
and then I grab the files (the RAID array usually has plenty of space).
Linux 2.6 has more drivers than XP. Compare the list of "out of the box" supported hardware, and you can easily see that Linux supports more devices w/o requiring a seperate driver from the manufacturer.
Just use a packet sniffer. Who says that Uncle Sam already isn't doing this, to a lesser degree?
1.) It is cheap- under $500. This is rare. 2.) It runs Linux. Yes, believe it or not, this site does lean towards OSS and *NIX.
Forgot to mention what he used for output: an old VB II braille unit. Had a RS-232 port on it (hence the COM port trick). And make that &2> instead of &>.
I have a blind friend that used lynx, bash, etc on a Linux box. All the extra setup took was just a :
sh &>/dev/ttyS0
And he was up and running. I will admit though that he is a bit of a *NIX guy, and already owned a shell account (was new to Linux, but had used UNIX before). He's not a wizard granted, but he knew what he had to.
Nothing is hackpoof. Coders are humans, and humans make mistakes.
This has been around for quite some time....
ipchains, iptables, kernel 2.2 and 2.4 are all on the installation medium. Despite popular belief, 2.4 is indeed in stable (2.4.18), and has been for quite some time.
Issues
Reader Coordination and Signal Processing
Most RFID readers are not designed to operate in the presence of another reader that is also scanning for tags. To date, this has not been a significant problem, as RFID has been in limited deployment without much opportunity for readers to interfere with each other. As electronic tags become more common, however, readers will be deployed on a larger scale, effectively garbling the data for systems in proximity to each other. This problem will become particularly serious if many mobile hand-readers are in use within close range of each other. Standards will be needed to define a protocol to allow these systems to share the available bandwidth, perhaps based on a wireless CSMA (carrier sense multiple access) protocol. ISO is addressing these issues, but details are beyond the scope of this article.
Further, improvements can be made when interpreting the tag signals received at the reader, intelligently filtering out noise. Application of advanced data-coding techniques in the tag electronics may also improve noise immunity and allow some multitag signal collisions to be separated and interpreted correctly. This may require more costly signal processing in the reader, but the benefits of greater accuracy will eventually lead to acceptance by a larger market and will drive the cost back down again.
Product Packaging Independence
In contrast to RFID, bar codes can be printed on a label and still be readable independent of the contents of the product or packaging. RFID, on the other hand, can be disrupted by materials in the product itself. Because tags use tuned RF circuits to receive interrogation signals, it is possible to detune or attenuate the signals if placed next to certain types of packaging. Ferrous metals are some of the worst offenders--RFID and canned foods are not a good combination. This problem is a challenging one, as the most obvious solution is to change the packaging material, but clearly some products do not have economic alternatives to metal, or metallized packaging, particularly where robustness and airtight storage is required. It will be interesting to see if the popular use of RFID eventually has an effect on the materials used for industrial packaging, or if material science can provide a material to isolate the effect of a product on a tag.
Multiple Standards
As noted earlier, several frequencies and standards have been used for RFID tagging solutions--for example, the popular ISO 14443 standard that operates at 13.56 MHz, the EPCglobal (96-bit) 915-MHz standard, and several others. In an ideal world, industry would adopt one standard; however, there are cost trade-offs, national frequency use restrictions, and politics that keep several of these active in their own commercial domain. For example, while Wal-Mart is considering adoption of the EPCglobal standard, Nokia (the largest cellphone manufacturer in the world) is about to release a cellphone that incorporates an RFID reader based on the ISO 14443 standard. The combination allows callers to scan posters and stickers that contain an embedded tag and buy the depicted products with the charge appearing automatically on their next phone bill. A solution to this standardization problem is to build readers that can operate using multiple standards, perhaps automatically searching for tags across a number of frequency bands using a suite of protocols, and be programmable, allowing them to adjust to national frequency restrictions.
Data Formats
Although the data format returned by read-only tags is defined by standards, the writable tags provide flash memory that customers can use in a proprietary way. There are potential benefits to standardizing the way data is represented here, perhaps allowing information to be shared or passed among independent organizations as it moves through a supply chain. For example, a product might move from the factory by road, air, and then road again to a warehouse in a foreign country, and finally
Moving Forward
EXTENDING RFID APPLICATIONS: SENSORS, SECURITY, AND MEMORY
RFID provides a data transport mechanism between a tag and a reader, which can be extended to provide greater utility than returning a simple identification number. The three important extensions of electronic tagging are: sensing the environment, security, and electronic memory.
Sensors
The addition of a physical sensor to a tag has been an important development, providing the capability for a storeowner to learn something about the conditions a product has experienced in the past, at the time its tag is interrogated. Consider a frozen chicken that is being transported to a store. If the refrigeration of the transporter truck fails on the road, the chicken may well begin to defrost and potentially be contaminated by bacterial growth. By incorporating a temperature-sensitive material into the tag, and electronics that can detect a change in its state (e.g., its electrical resistance might permanently increase), it is possible to determine which of the chickens could be contaminated. Not only is the customer protected in this situation, but some of the product might also be saved if the sensors show critical temperatures were not exceeded, perhaps in a more insulated part of the truck. In this case, it is also a win for the meat company and the retail stores. KSW-Microtec in Germany produces an RFID tag called TempSens that is based on these principles and is being trialed by a European pharmaceutical company.
Security
Packaging of modern products is frequently associated with tamper-protecting mechanisms to alert a customer if a product has been opened between the factory and time of purchase. In this way, consumers can be warned that something may have been removed from the package, or more seriously, that the product may have been deliberately contaminated. By combining RFID with a switch--perhaps a simple wire attached to the tag and the packaging that is broken when the product is opened--a tag can indicate the suspicious conditions when read at the time of purchase. If the same tagged product has been interrogated earlier by other readers, the read times can be used to determine roughly when the product was tampered with, perhaps leading to the apprehension of the perpetrator. The U.S. Food and Drug Administration has recommended that RFID be considered for the protection of pharmaceutical products.
Memory
Stable storage, in the form of a read/write memory based on EEPROM (electrically erasable programmable read-only memory), is a relatively straightforward addition to an electronic tag, without any need to modify its encapsulation. Sensor tags, by contrast, require additional components that are not easily integrated, and the encapsulation needs to be carefully redesigned to accommodate them. Adding user-programmable memory to a tag opens up many new possibilities for its use. It can be used to store information that remains associated with a tagged product without the need for factories, shipping companies, retail stores, and customers to share a common database to find information about its history. For example, if a car's VIN (vehicle identification number) were stored in an RFID tag, the name of each owner of the car could be stored alongside it, providing an ownership record over the lifetime of the car; it remains with the car and cannot easily be lost. Service information could be stored in a similar way, and independent garages would be able to find out about any prior service history to help guide their work. Read/write RFID tags are available from many companies including Philips, Texas Instruments TIRIS, and Gemplus; however, there are no standards in place that advise a customer how this memory should be used.
ISSUES TO BE RESOLVED WITH RFID
Given everything you have read so far, you may have been led to believe that apart from cost, the remaining technical issues for RFID are all solved. A number of issues, however, still present a challenge: tag orientation, r