the ATF doesn't hire drunk smokers w/ unregistered firearm violations....... well yeah, because the ATF doesn't need to hire half the population of Michigan.
(c) CEASING COMMUNICATION. If a consumer notifies a debt collector in writing that the consumer refuses to pay a debt or that the consumer wishes the debt collector to cease further communication with the consumer, the debt collector shall not communicate further with the consumer with respect to such debt, except --
(1) to advise the consumer that the debt collector's further efforts are being terminated;
(2) to notify the consumer that the debt collector or creditor may invoke specified remedies which are ordinarily invoked by such debt collector or creditor; or
(3) where applicable, to notify the consumer that the debt collector or creditor intends to invoke a specified remedy.
If such notice from the consumer is made by mail, notification shall be complete upon receipt.
So, wait, if I win tier 1, can I elect the tier 2 prize? Who wants a segway anyways? I think a better incentive would have been Apple Cinema displays..
bug code 0x4e? Sounds like a memmory manager code; are you overclocking your light sabre? Try turning off APIC, ACPI and reinstalling.
Re:Gave up because the installer wouldn't let them
on
iPod Shuffle RAID
·
· Score: 1
That's wrong - there is such a standard, EDD - Enhanced Disk Drive services. It can indicate to the operating system that your harddrive is attached to ide, scsi, fibrechannel, firewire, or usb, which pci adapter hosts the drive, its location on the host adapter's bus, and the full geometry of the device. Pretty much every PC bios dating from the P3 era supports at least version 2.2, and many of the P4 machines I've seen support version 3.0.
To be honest, I agree. You're right. The connections exist. The difference between the two situations, however, is that your traffic is able to pass unhindered between your computer and a computer on the internet.
In the case of the nuclear plant, it was requisite for the virus to infect the host at the contractors site to leap frog to the plant. The nuclear power plant's computers were not routed to the internet.
As I said, I agree with you; the situation is inexcusable. I only reply to save face and clarify.
They weren't externally connected, however, they did have a leased line to a contractor. The contractor was externally connected and became infected, the virus spread across the leased line.
The system affected was a computer running a digital readout. It froze from resource starvation. Analog gauges and other safety systems continued to work fine.
The woeful inaccuracy of your post is really, really painful. Allow me to rebuke.
First of all, linux software raid has excellent autodetection. You need to set the partition identifier to 0xFD so that the autodetector can identify it. As many have mentioned, software raid has a huge advantage over hardware raid for recovery - you can disconnect the drives from one computer, hook them to another and the autodetect code will figure it out. I know this works because I've done it.
Second, for 8 drives and 2 controllers a card, you'd want four ATA133 adapters. Each adapter has, as you said, 2 controllers. You don't want to sue the slave channel, because that will definately kill performance.
Third, Don't install the OS on the raided partition. Don't keep anything fragile or irreplacable on the OS partition. If you want to backup the configuration, backup the configuration. There's no need to raid your boot drive, and if your boot drive fails you can trivially reinstall.
A cheap batch script is not an effective backup solution. What if files are locked or a file is backed up midway through a transaction? I readily agree that RAID is not a backup solution, but to putting any faith in a "cheap batch script" is profoundly naive.
RAID5 has the advantage that you only lose one drives worth of space to parity information. With eight 250 gig drives on a P3 500, its readily obvious that his goal is to inexpensively store a large amount of data with an effective mitigation against a single drive failure. Software RAID5 is an excellent solution for him.
Lastly, I'd recommend one of the intel gigabit cards, because although the drives will only read 50 or 60 megabytes/s, the whole point is moot if your network connection maxes out at around 10 megabytes a second. The client adapters, like the 1000MT is more than enough, and not that expensive.
This has, in large part, disappeared with the advent of UDMA. It was true that IDE was very cycle expensive a decade ago when the IDE really meant Internal Disk Eletronics. The IDE "interface" was just a set of tri-state latches and the CPU would be responsible for pushing and reading every single byte. If you ever look at the pinout for an IDE cable, it's no surprise that it very closely resembles the ISA bus. Another historical note, ATA means AT-Attachment because the first set of IDE drives that were really popular were designed to attach to the IBM PC AT (the successor of sorts to the IBM PC XT) bus.
Now, processors queue dma requests in and out of the drive and the "interface" really has grown up to be more of a "controller." They're not as complex as the SCSI adapters, of course, but then again, SCSI is a much more complex signaling system.
2. No Longer True.
What you're trying to describe is called as "bus disconnect." I'm not sure which side of the bus was responsible, however, the idea is that while a drive was processing a command, the bus was locked until the command finished.
Note, the first version of SCSI did not have Disconnect either. However, given many more devices sharing the bus, bus contention was more severe, especially using slow devices like tape drives and cdroms, that it became necessary rather than just a feature.
SCSI supports disconnection as well as Tagged Command Queueing. TCQ allows the host to issue multiple outstanding commands to the device. The device is allowed to complete these commands out of order. Many drives will reorder the requests to take advantage of the head movement.
Recent revisions of IDE include support for TCQ.
I will add, however, that it is still worthwhile to have only one device per channel. Compare this to putting more than two 15K drives on a U160 channel.
3. Not even remotely true. SCSI is a parralel bus, much like IDE, ISA, or half a dozen others. Its only possible for one device to drive the bus at one time. This is clearly evident since a few of the lines in the SCSI cable are used to indicate the Target of the bus transaction. There is only one set of these signals, therefore, there can only be one target.
Also, the electrical interface for Serial ATA is designed with hot-swap in mind.
While your first suggestion is accurate, disk i/o is very slow and SCSI equipment tends to be of better quality than IDE hardware. SCSI drives with higher spindle speeds have much lower latency, which can lend a dramatic difference to a similar computer with IDE drives. However, that difference is of no fault of IDE. I would encourage, you, in future to be more accurate with your information.
If you believe I have written inaccurately, I would recommend reading the draft documents from INCITS T13, the ATA technical comittee.
4) Audit logs. Record the entry and modification of every piece of information. Log time, username, and terminal.
4a) Remember that its not your job to review the audit log and you should not unless subpoenaed.
4b) Consider getting an old ibm/lexmark proprinter, one of the old, built-to-withstand-ww3 fan-fold printers to have a paper copy of the logfiles.
4c) An even better model is where you prohibit the removal of records. When information must be corrected, an update is added such that the old and new information is available.
5) IMHO, Web Based authentication is difficult to do reliably.
5a) It would be feasible to use a windows authentican mechanism and require NTLM to be passed over the SSL by IE. You could use Dallas iButtons if smartcards are too slow.
5b) You still should have some sort of PIN.
5c) Don't use fingerprint biometrics - it would require doctors and nurses to remove their gloves. I'm not sure what the regulations are in an emergency room, but given that its in an infectious area, you probably are required to wear gloves to use it.
This has to be the most effective solution suggested yet.
802.1x is more cross-platform than propietary VPN solutions, requires no instructor cooperation changing keys or announcing new keys, requires no hacking up of a DHCP server, etc.
A lot of posts seem to surround getting a large, professional server machine with redundant everything. Those are expensive and still have points of failure.
I would suggest buying a number of the inexpensive wal-mart PCs and clustering them redundantly. Keep spares around for emergencies - emergency switches, nics, drives, etc.
This is a more technically complicated environment, because you have to worry about data consistency between computers, but, these walmart PCs are disposable and can work independent of each other.
First of all, lets define an operating system (roughly, for the sake of argument): The operating system is software used to allow applications a standardized method for using system resources.
In DOS, applications would make calls to interrupt 0x21 to access system resources like files and memory.
If Windows 9X were a GUI that used DOS as it's operating system, then it would use interrupt 0x21 for all of its I/O.
Windows 9X, upon initialization, replaces the context of DOS with it's own. It switches the processor to 386 Protected mode and installs its own set of hardware, filesystem, network, and other drivers. It replaces the int 0x21 interface with its own. Applications use Windows 9X for access to system resources (ram, files, network, etc.) Also, this emulation is miserably slow.
Windows 9X does have code to allow Windows 9X to use DOS drivers (The 16bit drivers, if you will.) However, This is done by creating a virtual 8086 context, and making calls to int 0x21. This, however, is not recommended and is provided for backwards compatability. (Think of it as Windows 9X emulating DOS to allow the drivers to operate.)
Also, Windows 9X will return the computer to the DOS context that it replaced when it "quits". However, that context is not used (with the exception of the above paragraph) for the normal operation of the computer.
Windows 9X has its own kernel, its own drivers, and is very much a complete, functional operating system. Yes, it may be bug ridden and broken, however, it is a real operating system.
Honestly, a more accurate statement. would be that DOS is a bootloader for Windows 9X.
So? They're maximizing profit margins. It's a free market. They'll continue to do this until consumers stop patronizing the store. They offer lousy benefits but their employees are not bound to work at Walmart. If there are so many distributors that Walmart has such power, then its economics at work - too much supply.
It's also a free country; let your dissatisfaction be heard with your vote and wallet.
Honestly, that has very little to do with the the encoding standard and more to do with the quality of the handset. My GSM Nokia 8290 was horrible. A friend's ATT TDMA 8210 was a little better. My GSM Motorolla v60g sounds great, but is an obnoxious phone (miserable UI, otherwise, fabulous.) A friend's Qualcomm? Miserable. I'd encourage you to avoid making strong statements, because I dont think its a sound rule to follow.
I'm fairly certain that if Alpha or MIPS had the same amount of research dollars and money put behind it, those scores would be considerably higher. The x86 architecture is not the enabling factor that gets those high scores; rather, its preventing even higher scores.
I gotta just reinforce the fact that the new kbuild system makes compiling kernels outside of the build tree much easier.
First of all, there's now a symbolic link from/lib/modules/.../build to the kernel source, further with kbuild, it handles all the dependencies and symbols, etc.
Basically, compiling a module outside of the tree in the old 2.4.x was difficult and if you were using modversions, almost impossible - you need to have the kernel source and kernel configuration - its necessary anyways. Now, all I need to do is
I had a similar situation. My freshman year roommate and I were entirely dissimilar. I am your average geek. He was a 212 pound, born again christian, wrestling champ. He didn't drink, I did. He listened to christian rock, I listened to Wumpscut and other caustic german industrial. We both had obnoxiously massive stereos and large loud computers.
However, we arranged for some simple rules: no alcohol in the room, no sex in the room, and use headphones while both of us are in the room.
It worked out well, I would sleep during the day, he would sleep during the night, we arranged our room in an L, with desks at the foot of the beds, so that the monitor/lcd light would shine away from the person asleep. I had no problem sleeping while he did his homework; and he enjoyed the fact that my machine was a freaking wind tunnel with usb ports.
After living with a good friend the next year and watching things go down hill because we were too similar and too alike, I've learned to appreciate the healthy relationship I had with my first roommate.
Its something to note that while many chips can have 64 bit pointers, the chip does not necessarily support 64 address lines. For example, from the Athlon 64 FX Datasheet found here, we know that the Athlon 64 FX has 40 physical address lines, Granted, that's still a Terrabyte of physical address space, but, its nowhere near the numbers you quote.
Mind you, the originaly 68000 was like this, with only 24 physical address lines, as were the 80486SLC's with only 24 physical address lines, despite being 32bit internally. Oh, and I believe MIPS arches have 30 address lines because they do not support non word-aligned read/writes, but that may or may not be true.
Oh, another thing, the Athlon 64 does clock in 64 or 128 bits per read/write cycle, so even if it uses the physical address lines for the high bits (most likely) its still not the full 64 bit address space.
Slashdot Mirror
the ATF doesn't hire drunk smokers w/ unregistered firearm violations.... ... well yeah, because the ATF doesn't need to hire half the population of Michigan.
Oh, and there's the always exciting Internz list.
Where's Bill's statshot?
Pat White crew forever.
before anyone assumes this is bullshit, refer to the legislation referred:
(from http://www.ftc.gov/os/statutes/fdcpa/fdcpact.htm
)
(c) CEASING COMMUNICATION. If a consumer notifies a debt collector in writing that the consumer refuses to pay a debt or that the consumer wishes the debt collector to cease further communication with the consumer, the debt collector shall not communicate further with the consumer with respect to such debt, except --
(1) to advise the consumer that the debt collector's further efforts are being terminated;
(2) to notify the consumer that the debt collector or creditor may invoke specified remedies which are ordinarily invoked by such debt collector or creditor; or
(3) where applicable, to notify the consumer that the debt collector or creditor intends to invoke a specified remedy.
If such notice from the consumer is made by mail, notification shall be complete upon receipt.
So, wait, if I win tier 1, can I elect the tier 2 prize? Who wants a segway anyways? I think a better incentive would have been Apple Cinema displays..
bug code 0x4e? Sounds like a memmory manager code; are you overclocking your light sabre? Try turning off APIC, ACPI and reinstalling.
That's wrong - there is such a standard, EDD - Enhanced Disk Drive services. It can indicate to the operating system that your harddrive is attached to ide, scsi, fibrechannel, firewire, or usb, which pci adapter hosts the drive, its location on the host adapter's bus, and the full geometry of the device. Pretty much every PC bios dating from the P3 era supports at least version 2.2, and many of the P4 machines I've seen support version 3.0.
To be honest, I agree. You're right. The connections exist. The difference between the two situations, however, is that your traffic is able to pass unhindered between your computer and a computer on the internet.
In the case of the nuclear plant, it was requisite for the virus to infect the host at the contractors site to leap frog to the plant. The nuclear power plant's computers were not routed to the internet.
As I said, I agree with you; the situation is inexcusable. I only reply to save face and clarify.
They weren't externally connected, however, they did have a leased line to a contractor. The contractor was externally connected and became infected, the virus spread across the leased line.
The system affected was a computer running a digital readout. It froze from resource starvation. Analog gauges and other safety systems continued to work fine.
The missing step #2 is:
2. Cut product up into pieces and sell on ebay.
Now it all makes sense.
To be perfectly honest, the parent and parent's parent interaction is one of the chief reasons why I love Slashdot comments.
The woeful inaccuracy of your post is really, really painful. Allow me to rebuke.
First of all, linux software raid has excellent autodetection. You need to set the partition identifier to 0xFD so that the autodetector can identify it. As many have mentioned, software raid has a huge advantage over hardware raid for recovery - you can disconnect the drives from one computer, hook them to another and the autodetect code will figure it out. I know this works because I've done it.
Second, for 8 drives and 2 controllers a card, you'd want four ATA133 adapters. Each adapter has, as you said, 2 controllers. You don't want to sue the slave channel, because that will definately kill performance.
Third, Don't install the OS on the raided partition. Don't keep anything fragile or irreplacable on the OS partition. If you want to backup the configuration, backup the configuration. There's no need to raid your boot drive, and if your boot drive fails you can trivially reinstall.
A cheap batch script is not an effective backup solution. What if files are locked or a file is backed up midway through a transaction? I readily agree that RAID is not a backup solution, but to putting any faith in a "cheap batch script" is profoundly naive.
RAID5 has the advantage that you only lose one drives worth of space to parity information. With eight 250 gig drives on a P3 500, its readily obvious that his goal is to inexpensively store a large amount of data with an effective mitigation against a single drive failure. Software RAID5 is an excellent solution for him.
Lastly, I'd recommend one of the intel gigabit cards, because although the drives will only read 50 or 60 megabytes/s, the whole point is moot if your network connection maxes out at around 10 megabytes a second. The client adapters, like the 1000MT is more than enough, and not that expensive.
Not on this planet. Here, SCSI is an acronym for:
... next time, try google.
Small Computer System Interface
Check the ANSI document X3.131:1994[1999]
You may be thinking of some serial adaptations of SCSI, like SBP, Serial Bus Protocol, or SAS Serial Attached SCSI.
1. No Longer True.
This has, in large part, disappeared with the advent of UDMA. It was true that IDE was very cycle expensive a decade ago when the IDE really meant Internal Disk Eletronics. The IDE "interface" was just a set of tri-state latches and the CPU would be responsible for pushing and reading every single byte. If you ever look at the pinout for an IDE cable, it's no surprise that it very closely resembles the ISA bus. Another historical note, ATA means AT-Attachment because the first set of IDE drives that were really popular were designed to attach to the IBM PC AT (the successor of sorts to the IBM PC XT) bus.
Now, processors queue dma requests in and out of the drive and the "interface" really has grown up to be more of a "controller." They're not as complex as the SCSI adapters, of course, but then again, SCSI is a much more complex signaling system.
2. No Longer True.
What you're trying to describe is called as "bus disconnect." I'm not sure which side of the bus was responsible, however, the idea is that while a drive was processing a command, the bus was locked until the command finished.
Note, the first version of SCSI did not have Disconnect either. However, given many more devices sharing the bus, bus contention was more severe, especially using slow devices like tape drives and cdroms, that it became necessary rather than just a feature.
SCSI supports disconnection as well as Tagged Command Queueing. TCQ allows the host to issue multiple outstanding commands to the device. The device is allowed to complete these commands out of order. Many drives will reorder the requests to take advantage of the head movement.
Recent revisions of IDE include support for TCQ.
I will add, however, that it is still worthwhile to have only one device per channel. Compare this to putting more than two 15K drives on a U160 channel.
3. Not even remotely true. SCSI is a parralel bus, much like IDE, ISA, or half a dozen others. Its only possible for one device to drive the bus at one time. This is clearly evident since a few of the lines in the SCSI cable are used to indicate the Target of the bus transaction. There is only one set of these signals, therefore, there can only be one target.
Also, the electrical interface for Serial ATA is designed with hot-swap in mind.
While your first suggestion is accurate, disk i/o is very slow and SCSI equipment tends to be of better quality than IDE hardware. SCSI drives with higher spindle speeds have much lower latency, which can lend a dramatic difference to a similar computer with IDE drives. However, that difference is of no fault of IDE. I would encourage, you, in future to be more accurate with your information.
If you believe I have written inaccurately, I would recommend reading the draft documents from INCITS T13, the ATA technical comittee.
4) Audit logs. Record the entry and modification of every piece of information. Log time, username, and terminal.
4a) Remember that its not your job to review the audit log and you should not unless subpoenaed.
4b) Consider getting an old ibm/lexmark proprinter, one of the old, built-to-withstand-ww3 fan-fold printers to have a paper copy of the logfiles.
4c) An even better model is where you prohibit the removal of records. When information must be corrected, an update is added such that the old and new information is available.
5) IMHO, Web Based authentication is difficult to do reliably.
5a) It would be feasible to use a windows authentican mechanism and require NTLM to be passed over the SSL by IE. You could use Dallas iButtons if smartcards are too slow.
5b) You still should have some sort of PIN.
5c) Don't use fingerprint biometrics - it would require doctors and nurses to remove their gloves. I'm not sure what the regulations are in an emergency room, but given that its in an infectious area, you probably are required to wear gloves to use it.
This has to be the most effective solution suggested yet.
802.1x is more cross-platform than propietary VPN solutions, requires no instructor cooperation changing keys or announcing new keys, requires no hacking up of a DHCP server, etc.
This is actually a common trend. For example, Software WEP far outperforms hardware WEP. A modern processor will spend Jeff Mogul has a great paper describing how TCP Offloading is slower than software TCP:i ngs-new/mogul-offload-2003.pdf
http://bbcr.uwaterloo.ca/~brecht/courses/856/read
A lot of posts seem to surround getting a large, professional server machine with redundant everything. Those are expensive and still have points of failure.
I would suggest buying a number of the inexpensive wal-mart PCs and clustering them redundantly. Keep spares around for emergencies - emergency switches, nics, drives, etc.
This is a more technically complicated environment, because you have to worry about data consistency between computers, but, these walmart PCs are disposable and can work independent of each other.
This assertion is an untruthitude.
First of all, lets define an operating system (roughly, for the sake of argument): The operating system is software used to allow applications a standardized method for using system resources.
In DOS, applications would make calls to interrupt 0x21 to access system resources like files and memory.
If Windows 9X were a GUI that used DOS as it's operating system, then it would use interrupt 0x21 for all of its I/O.
Windows 9X, upon initialization, replaces the context of DOS with it's own. It switches the processor to 386 Protected mode and installs its own set of hardware, filesystem, network, and other drivers. It replaces the int 0x21 interface with its own. Applications use Windows 9X for access to system resources (ram, files, network, etc.) Also, this emulation is miserably slow.
Windows 9X does have code to allow Windows 9X to use DOS drivers (The 16bit drivers, if you will.) However, This is done by creating a virtual 8086 context, and making calls to int 0x21. This, however, is not recommended and is provided for backwards compatability. (Think of it as Windows 9X emulating DOS to allow the drivers to operate.)
Also, Windows 9X will return the computer to the DOS context that it replaced when it "quits". However, that context is not used (with the exception of the above paragraph) for the normal operation of the computer.
Windows 9X has its own kernel, its own drivers, and is very much a complete, functional operating system. Yes, it may be bug ridden and broken, however, it is a real operating system.
Honestly, a more accurate statement. would be that DOS is a bootloader for Windows 9X.
You mean, like this one? http://cgi.ebay.com/ebaymotors/ws/eBayISAPI.dll?Vi ewItem&rd=1&item=2474652269&category=6 419
So? They're maximizing profit margins. It's a free market. They'll continue to do this until consumers stop patronizing the store. They offer lousy benefits but their employees are not bound to work at Walmart. If there are so many distributors that Walmart has such power, then its economics at work - too much supply.
It's also a free country; let your dissatisfaction be heard with your vote and wallet.
Honestly, that has very little to do with the the encoding standard and more to do with the quality of the handset. My GSM Nokia 8290 was horrible. A friend's ATT TDMA 8210 was a little better. My GSM Motorolla v60g sounds great, but is an obnoxious phone (miserable UI, otherwise, fabulous.) A friend's Qualcomm? Miserable. I'd encourage you to avoid making strong statements, because I dont think its a sound rule to follow.
I'm fairly certain that if Alpha or MIPS had the same amount of research dollars and money put behind it, those scores would be considerably higher. The x86 architecture is not the enabling factor that gets those high scores; rather, its preventing even higher scores.
I gotta just reinforce the fact that the new kbuild system makes compiling kernels outside of the build tree much easier.
/lib/modules/.../build to the kernel source, further with kbuild, it handles all the dependencies and symbols, etc.
/usr/src/linux-2.6.2 SUBDIRS=$PWD modules
First of all, there's now a symbolic link from
Basically, compiling a module outside of the tree in the old 2.4.x was difficult and if you were using modversions, almost impossible - you need to have the kernel source and kernel configuration - its necessary anyways. Now, all I need to do is
make -C
and voila, kbuild handles everything for me.
I had a similar situation. My freshman year roommate and I were entirely dissimilar. I am your average geek. He was a 212 pound, born again christian, wrestling champ. He didn't drink, I did. He listened to christian rock, I listened to Wumpscut and other caustic german industrial. We both had obnoxiously massive stereos and large loud computers.
However, we arranged for some simple rules: no alcohol in the room, no sex in the room, and use headphones while both of us are in the room.
It worked out well, I would sleep during the day, he would sleep during the night, we arranged our room in an L, with desks at the foot of the beds, so that the monitor/lcd light would shine away from the person asleep. I had no problem sleeping while he did his homework; and he enjoyed the fact that my machine was a freaking wind tunnel with usb ports.
After living with a good friend the next year and watching things go down hill because we were too similar and too alike, I've learned to appreciate the healthy relationship I had with my first roommate.
Its something to note that while many chips can have 64 bit pointers, the chip does not necessarily support 64 address lines. For example, from the Athlon 64 FX Datasheet found here, we know that the Athlon 64 FX has 40 physical address lines, Granted, that's still a Terrabyte of physical address space, but, its nowhere near the numbers you quote.
Mind you, the originaly 68000 was like this, with only 24 physical address lines, as were the 80486SLC's with only 24 physical address lines, despite being 32bit internally. Oh, and I believe MIPS arches have 30 address lines because they do not support non word-aligned read/writes, but that may or may not be true.
Oh, another thing, the Athlon 64 does clock in 64 or 128 bits per read/write cycle, so even if it uses the physical address lines for the high bits (most likely) its still not the full 64 bit address space.