"If you are more afraid of the "government" than you are of the possible accidental shooting of someone with your legally purchased firearm, then you aren't paying attention."
I trust myself a lot more than I trust the government. And I have a better track record.
And if guns had fingerprint scanners like your rose gold iPhone did, they would need to be charged regularly. Not very helpful to have a secured gun with a dead battery rendering it inoperable.
"The real issue is that a parent may have others depending on them."
The real issue here is irresponsible actions by the parent. The hypothetical offered ignores the reality that clear signs that something was wrong with the 'student' are almost always present.
"Jail the parent for indirect manslaughter and that charge could be applied to everyone involved with the student (teachers and counselors for example)."
No. Not everyone involved with the student made a gun available to the student. More importantly, however, if you start making those teachers and counselors responsible for reporting on 'concerning behavior' or whatever, is there any systems or processes to follow up and offer help? Sadly, no, in virtually every jurisdiction.
"Just throwing people in jail unneededly will almost always cause more issues down the line."
Most likely, it will also prevent more issues down the line. But we aren't interested in that.
"What if they are the only bread winner in the family? Single parent with more than that one murderer kid?"
What if they aren't. Still in jail.
I can easily come up with N + 1 situations where a simple "jail them all and let God sort them out" solutions fail in every regard.
How about coming up with realistic ones? The examples are available.
Ya' know? There are even family situations where the kid gets a gun from some other person (Gang member, friend, found on the street, etc.) and there are many cases where the parents are seriously scared of their kids, but they don't do something about it because that is the one protection they can give their kids, a clearer legal record. All sorts of situations.
I'm betting these kids showed warning signs before they became dangerous. Any action?
"Think of it like this. The moment when a person is able to think, "I want to kill that person" in the context that is not like a kid "playing" with a pet and accidentally killing it (I killed a goldfish like this), is when they are able to take murderous action and should be tried as an independent adult. At this point they also have the capacity to understand what laws are and understand the most simple of laws (like not killing people). It all rests on them and their choices."
Well, then we have a new standard for responsibility. What about diminished capacity? Parental abuse? N + 1 situations where children are really still children?
Excusing the parents doesn't work as well for me as it does for you.
Toddlers have no idea what they are doing. Even 5 year olds are questionably aware of the danger of a gun, but:
- If their parents (or whoever was the owner of the gun) cared to instruct them, they should reconsider the efficacy of such a discussion. Children that young barely understand such issues.
- And their parents (or whoever was the owner of the gun) should have secured it, preventing access. To not do so is criminal.
- The parents (or whoever was the owner of the gun) should go to jail.
I'm a Second Amendment advocate, previous gun owner, and when I do purchase a gun (soon) I must also purchase secure storage for it. I have 5- and 7-year old nieces visiting. It would be entirely unacceptable for them to even touch a gun of mine without my direct supervision and training. And these two nieces come from a family where both parents own and handle guns regularly. All secured. Never left out unattended. Never.
It's unacceptable. Gun owners are responsible.
Now, truth is, most of these sad incidents involve adults that are plainly irresponsible. No way to legislate that out of existence.
0. Where I work this has never been a problem or issue. Not in 10 years.
1. Such statements imply you have an antiquated and inadequate understanding of women. Please consider doing more research on this, outside your limited sphere of experience.
You in any industry that cannot be discussed by me in polite terms. But you know that, and I'm not ready quite yet to tell you to find respectable or honest work. It's mostly not illegal, and of not proven illegal then I will not further condemn you.
I don't doubt it's an unforgiving place. The price of failure is tangible.
Don't get me started on turning Mag Card I/O into terminals. The selectors and solenoids were fairly straightforward, and the transmit was sufficient for keyboard data.
The 5218, I think that's the model, was a Selectric Printer for the DisplayWriter. Letter quality, reliable, not too noisy. The 5219(?) Daisy printer could not be repurposed to print from PCs , but you could run MS-DOS 2.11 on the DisplayWriter. Just needed the 8" floppies.
Many Selectric models were controlled electrically, Composers and Executives, Mag Tape (MT/ST) and Mag Card (MC/ST), several system printers for old mini systems, and they used a variety of interfaces interfaces.
The Selectric selected the character on the by its tilt and rotate position. Capital and shifted characters were on reach hemisphere of the ball. Impression was accomplished by driving the entire element carrier on a pivot towards the paper and platen, lifting the ribbon in so that it was pressed against the paper. Correcting, when implemented, lifted an adhesive tape in place of the ribbon, lifting the not-yet fully adhered Robin material from the paper. Functions such as escapement (moving the carrier to the right {or left for Hebrew, Aramaic?, etc}), paper feed or indexing, carrier return, tabulation, etc. Were handled by dedicated mechanisms, and were v electrified to be actuated by solenoids. Reed switches etc would signal the state of the machine. Printing was driven by the operational shaft, a half turn per character.
Selectrics are indeed remarkable machines. Frustrating to service, but worth the effort.
The Electronic 50, 60, 75 are advanced Selectric IIIs also electrified. Faster and not as reliable, the electronics advanced features. Before that, the Memory 50 and 100 used a tape loop to store data, functioning much like MC/ST. After the Electronics, it was WheelWriters. Not nearly as mechanical. Soon after this, PCs and WordPerfect took over.
People are still repairing Selectrics, and still converting the electrified ones for various uses. Certainly a good substitute for an ASR/KSR-33, the original single-element printer. I can refer you to some Selectric groups.
0. Many old IDE drives failed when the stepper drivers got flaky and when hot would crash the heads. I put them on long cables, stuffed them in a freezer compartment, and they would usually live long enough to be backed up. Seagates did this some, but Maxtors were the worst.
1. When I was asked to install a 750MB drive in an old Novell 2.15c server, it took some thinking to figure out how many disk buffers would be needed to access the drive reliably. The customer asked me to leave the DCB attached, with both 20MB drives still spinning and serving data. Doing this without powering down the DCB and drives? Priceless.
2. Going back to the same server and replacing the thinnet NIC with a gig Ethernet NIC a year later. If you configure enough packet buffers, it works... We used a number Novell had never tried.
3. A few years after this, the DCB is still running, and they call me back to install a pair of 320GB drives. More buffers. Add-on zero slot SCSI RAID controller in RAID 1 mode. Linked the driver as required, the manufacturer did this hack and wrote the driver floppy for me, as NetWare 2.15c was EOL'd at least 10 years before this card was produced. They get credit for that hack. Keeping the DCB drive spinning so they don't stop and stick? Priceless. Figuring out the LBC-CHS mapping that allowed the server use all the space? Scary. It was non intuitive, but fixed thanks to a friend who does octal math in his head to 8 places. He's weird.
4. When GroupWise 4.x wasn't quite patched up, you had some Korean jerk reflecting Yahoo addresses off it as SMTP postmaster error replies to spam the world with Yahoo Mail addresses. The server I serviced could send 200-250 million in a weekend until the disk filled with the errors. Fix was to set the MX record for the customer to a server at their ISP, teach GroupWise it's SMTP gateway was that machine, and let it properly refuse the incoming mail. GW was patched a while later for this and the big security hold that this was not part of. That ran for about 8 years. Finally Exchange worked well enough for that customer to switch.
5. There was the Novell era where we did so many weird hacks to overcome corrupted volumes, funky network routing, and Novell's figuring out the IDE driver was causing the clock to lose time, forcing us to install NTP and eventually the whole NAMP stack. Apache on Novell was not my hack.
The Selectric stuff wouldn't interest anyone here.
If the Kernel team's goal is the best work they can do, is abusive behavior helping achieve that goal? If a locker-room mentality works, so be it, but you will narrow your pool of available talent. Will that get you the best work you can get?
If the Kernel team is not interested in doing the best work they can do, then it's up to their leader, Linus from the sounds of it, to decide if that's the way he wants it to be.
And again, it's Linus' world there. Play or not, yours and his choice. Results will prove out.
"Men need to learn to communicate _differently_ with different people and consider their differences . Unless they don't care, in which case they willingly suffer the consequences "
FTFY.
I work in a professional environment where we do not use vulgarity or obscenities, do not personally insult one another, nor threaten with violence, even emotional violence. I also volunteer, but do not for those organizations that permit such willful dysfunction.
Sarah is entirely in the right on this. Continued behavior like this may only cost the Kernel team a talented but replaceable team member, but making it a public issue may also cause them recruiting problems, and it should.
If you want to play in Linus' world, you know the price.
Amex starts with a 33 or 37. 6 is shared by a multitude of types, including Discover. Diners Club USA uses 54 and 55.
The first four are more useful than the first single digit.
Many issuers do use segments for product types, so the available account numbers for an issuer nay be less than the mathematical maximum, and since account numbers generally have to meet MOD 10 crc, the available combinations are less.
More true than you know. PII is a big deal. This should have become an internally reported event, since it disclosed purchase details, and risked significant exposure.
Slashdot Mirror
"If you are more afraid of the "government" than you are of the possible accidental shooting of someone with your legally purchased firearm, then you aren't paying attention."
I trust myself a lot more than I trust the government. And I have a better track record.
And if guns had fingerprint scanners like your rose gold iPhone did, they would need to be charged regularly. Not very helpful to have a secured gun with a dead battery rendering it inoperable.
Technology isn't always the answer.
"(Spare me any anecdotes about how every Southern boy goes to gun safety class for his hunting license.)"
Why? It seems on point to me.
"The real issue is that a parent may have others depending on them."
The real issue here is irresponsible actions by the parent. The hypothetical offered ignores the reality that clear signs that something was wrong with the 'student' are almost always present.
"Jail the parent for indirect manslaughter and that charge could be applied to everyone involved with the student (teachers and counselors for example)."
No. Not everyone involved with the student made a gun available to the student. More importantly, however, if you start making those teachers and counselors responsible for reporting on 'concerning behavior' or whatever, is there any systems or processes to follow up and offer help? Sadly, no, in virtually every jurisdiction.
"Just throwing people in jail unneededly will almost always cause more issues down the line."
Most likely, it will also prevent more issues down the line. But we aren't interested in that.
"What if they are the only bread winner in the family? Single parent with more than that one murderer kid?"
What if they aren't. Still in jail.
I can easily come up with N + 1 situations where a simple "jail them all and let God sort them out" solutions fail in every regard.
How about coming up with realistic ones? The examples are available.
Ya' know? There are even family situations where the kid gets a gun from some other person (Gang member, friend, found on the street, etc.) and there are many cases where the parents are seriously scared of their kids, but they don't do something about it because that is the one protection they can give their kids, a clearer legal record. All sorts of situations.
I'm betting these kids showed warning signs before they became dangerous. Any action?
"Think of it like this. The moment when a person is able to think, "I want to kill that person" in the context that is not like a kid "playing" with a pet and accidentally killing it (I killed a goldfish like this), is when they are able to take murderous action and should be tried as an independent adult. At this point they also have the capacity to understand what laws are and understand the most simple of laws (like not killing people). It all rests on them and their choices."
Well, then we have a new standard for responsibility. What about diminished capacity? Parental abuse? N + 1 situations where children are really still children?
Excusing the parents doesn't work as well for me as it does for you.
Idiot.
Toddlers have no idea what they are doing. Even 5 year olds are questionably aware of the danger of a gun, but:
- If their parents (or whoever was the owner of the gun) cared to instruct them, they should reconsider the efficacy of such a discussion. Children that young barely understand such issues.
- And their parents (or whoever was the owner of the gun) should have secured it, preventing access. To not do so is criminal.
- The parents (or whoever was the owner of the gun) should go to jail.
I'm a Second Amendment advocate, previous gun owner, and when I do purchase a gun (soon) I must also purchase secure storage for it. I have 5- and 7-year old nieces visiting. It would be entirely unacceptable for them to even touch a gun of mine without my direct supervision and training. And these two nieces come from a family where both parents own and handle guns regularly. All secured. Never left out unattended. Never.
It's unacceptable. Gun owners are responsible.
Now, truth is, most of these sad incidents involve adults that are plainly irresponsible. No way to legislate that out of existence.
Reinstituting G-S would be a huge fix. Does any politician have the balls? Carly? The Donald?
Ok, any politician that's electable? Carly? Cruz? No Democrat . And neither will Bernie.
How much closer they are to a Beowulf cluster of these...
0. Where I work this has never been a problem or issue. Not in 10 years.
1. Such statements imply you have an antiquated and inadequate understanding of women. Please consider doing more research on this, outside your limited sphere of experience.
You need to look up where I work.
Their name. It's the most favorite sound to a person.
Try reading first sentence as 'You work in an industry...'
This keyboard is almost as bad as m.slashdot..
You in any industry that cannot be discussed by me in polite terms. But you know that, and I'm not ready quite yet to tell you to find respectable or honest work. It's mostly not illegal, and of not proven illegal then I will not further condemn you.
I don't doubt it's an unforgiving place. The price of failure is tangible.
And hopefully Lollipop brings a reliable keyboard for my Nexus 7.2. Grrr.
Don't get me started on turning Mag Card I/O into terminals. The selectors and solenoids were fairly straightforward, and the transmit was sufficient for keyboard data.
The 5218, I think that's the model, was a Selectric Printer for the DisplayWriter. Letter quality, reliable, not too noisy. The 5219(?) Daisy printer could not be repurposed to print from PCs , but you could run MS-DOS 2.11 on the DisplayWriter. Just needed the 8" floppies.
Many Selectric models were controlled electrically, Composers and Executives, Mag Tape (MT/ST) and Mag Card (MC/ST), several system printers for old mini systems, and they used a variety of interfaces interfaces.
The Selectric selected the character on the by its tilt and rotate position. Capital and shifted characters were on reach hemisphere of the ball. Impression was accomplished by driving the entire element carrier on a pivot towards the paper and platen, lifting the ribbon in so that it was pressed against the paper. Correcting, when implemented, lifted an adhesive tape in place of the ribbon, lifting the not-yet fully adhered Robin material from the paper. Functions such as escapement (moving the carrier to the right {or left for Hebrew, Aramaic?, etc}), paper feed or indexing, carrier return, tabulation, etc. Were handled by dedicated mechanisms, and were v electrified to be actuated by solenoids. Reed switches etc would signal the state of the machine. Printing was driven by the operational shaft, a half turn per character.
Selectrics are indeed remarkable machines. Frustrating to service, but worth the effort.
The Electronic 50, 60, 75 are advanced Selectric IIIs also electrified. Faster and not as reliable, the electronics advanced features. Before that, the Memory 50 and 100 used a tape loop to store data, functioning much like MC/ST. After the Electronics, it was WheelWriters. Not nearly as mechanical. Soon after this, PCs and WordPerfect took over.
People are still repairing Selectrics, and still converting the electrified ones for various uses. Certainly a good substitute for an ASR/KSR-33, the original single-element printer. I can refer you to some Selectric groups.
If you can't crack open the Jam and fix the jack, you need to return your credentials and work as an auto detailer.
Actually, you failed Google. Since you asked, I'll answer.
That's nice. Imagine this with an Arduino and a servo shield.
0. Many old IDE drives failed when the stepper drivers got flaky and when hot would crash the heads. I put them on long cables, stuffed them in a freezer compartment, and they would usually live long enough to be backed up. Seagates did this some, but Maxtors were the worst.
1. When I was asked to install a 750MB drive in an old Novell 2.15c server, it took some thinking to figure out how many disk buffers would be needed to access the drive reliably. The customer asked me to leave the DCB attached, with both 20MB drives still spinning and serving data. Doing this without powering down the DCB and drives? Priceless.
2. Going back to the same server and replacing the thinnet NIC with a gig Ethernet NIC a year later. If you configure enough packet buffers, it works... We used a number Novell had never tried.
3. A few years after this, the DCB is still running, and they call me back to install a pair of 320GB drives. More buffers. Add-on zero slot SCSI RAID controller in RAID 1 mode. Linked the driver as required, the manufacturer did this hack and wrote the driver floppy for me, as NetWare 2.15c was EOL'd at least 10 years before this card was produced. They get credit for that hack. Keeping the DCB drive spinning so they don't stop and stick? Priceless. Figuring out the LBC-CHS mapping that allowed the server use all the space? Scary. It was non intuitive, but fixed thanks to a friend who does octal math in his head to 8 places. He's weird.
4. When GroupWise 4.x wasn't quite patched up, you had some Korean jerk reflecting Yahoo addresses off it as SMTP postmaster error replies to spam the world with Yahoo Mail addresses. The server I serviced could send 200-250 million in a weekend until the disk filled with the errors. Fix was to set the MX record for the customer to a server at their ISP, teach GroupWise it's SMTP gateway was that machine, and let it properly refuse the incoming mail. GW was patched a while later for this and the big security hold that this was not part of. That ran for about 8 years. Finally Exchange worked well enough for that customer to switch.
5. There was the Novell era where we did so many weird hacks to overcome corrupted volumes, funky network routing, and Novell's figuring out the IDE driver was causing the clock to lose time, forcing us to install NTP and eventually the whole NAMP stack. Apache on Novell was not my hack.
The Selectric stuff wouldn't interest anyone here.
"Men are blunt to each and will call you out on your bullshit to your face."
0. This need not be obscene or abusive.
"Women, on the other hand, will do it behind your back and will be far more vindictive about it."
0. Not where I work. YMMV.
Actually, cut to the chase.
If the Kernel team's goal is the best work they can do, is abusive behavior helping achieve that goal? If a locker-room mentality works, so be it, but you will narrow your pool of available talent. Will that get you the best work you can get?
If the Kernel team is not interested in doing the best work they can do, then it's up to their leader, Linus from the sounds of it, to decide if that's the way he wants it to be.
And again, it's Linus' world there. Play or not, yours and his choice. Results will prove out.
Professional behavior doesn't differ by gender. Even the words should be the same.
I never have to treat the women I work with differently because of their 'emotional state' or any gender issue.
"Men need to learn to communicate _differently_ with different people and consider their differences . Unless they don't care, in which case they willingly suffer the consequences "
FTFY.
I work in a professional environment where we do not use vulgarity or obscenities, do not personally insult one another, nor threaten with violence, even emotional violence. I also volunteer, but do not for those organizations that permit such willful dysfunction.
Sarah is entirely in the right on this. Continued behavior like this may only cost the Kernel team a talented but replaceable team member, but making it a public issue may also cause them recruiting problems, and it should.
If you want to play in Linus' world, you know the price.
Woops, Amex uses 34, not 3.
Amex starts with a 33 or 37. 6 is shared by a multitude of types, including Discover. Diners Club USA uses 54 and 55.
The first four are more useful than the first single digit.
Many issuers do use segments for product types, so the available account numbers for an issuer nay be less than the mathematical maximum, and since account numbers generally have to meet MOD 10 crc, the available combinations are less.
On the first report the bank should have recognized the disclosure and taken action to disable the phone service and contact the cardholder.
Yes, rank incompetence.
More true than you know. PII is a big deal. This should have become an internally reported event, since it disclosed purchase details, and risked significant exposure.