Perhaps I have been trolled. But I'll elaborate, just in case I haven't.
The guards are not required to inform you of your rights. In fact, there are only a few narrow instances where you are required to be informed of your rights at all. As I said, I bet someone here has encountered a guard who didn't know. There are a lot of them, after all.
The guards are NOT supposed to hold onto your items for you. Items you leave with the guards are destroyed. If you read my post, it was the ticket counter that would hold onto the item for my friend. Even then they certainly were not obligated to, and might have opened themselves to some liability if it had been lost. So this was certainly lucky. Returning an item to your car, for instance, would be reliable.
To reiterate, if you get stopped for something, and if you tried to leave the line with it, and if they confiscated it anyway, then that would've been illegal. And even illegal things happen every day.
I'll mention one more exception: It's may be (and probably is) a violation of law to attempt to circumvent their security. I don't doubt that they could arrest you and/or confiscate your stuff if they believed you were purposefully trying to circumvent them. But if you'd run afoul of that, you would likely have been interrogated, not just relieved of some item.
You're seeing some reasonable trees, but you're missing the forest.
I don't disagree with the detail of your point - my parents late 70s (?) Oldsmobile Cutlass was rear ended at approximately 50 mph. Luckily it was parked and no one was inside. It was totalled, but essentially the correct size. Three smaller foreign cars in front of it were compacted tremendously. The momentum of the traveling vehicle is it's m1v1, while the end momentum of the system is going to be the same. So the velocity change of the stationary vehicle is m1v1/(m1+m2) Obviously, the ideal case is for your semitruck to get hit by a speck of dust. But assuming your car weighs 3x as much as mine and you hit me at 40 mph, the basic idea is we'd both end up going 30, you've undergone a 10mph collision, I've undergone a 30mph one.
But that's a false argument on many levels, especially regarding our current discussion. For ease of discussion here, lets compare hitting something of essentially infinite momentum, like a bridge. In this case the velocity change of your car is going to be to zero, and quickly. In this case I'd bet a well designed newer car with crumple zones and air bags would be much more survivable at, say, 40mph than an older one without them, because the mass doesn't matter. I'm not saying either is very survivable at 75mph, today. This applies pretty well to you hitting a semi, actually, too. Basically hitting a car is MUCH better...
Now, certainly, if I was going to hit something with a roughly similar mass, I'd rather be in the heavier car than the lighter one. Or if I was going to hit anything under a critical threshold where the collision wasn't going to be too great, like a signpost, a newer (breakaway) powerline... Car-car accidents involve a devilish number of details, too...
To wrapup, I frankly think being a proficient driver, being aware of your surroundings, having good tires and brakes, etc, are more important than 10% more crumple zone. And I certainly like a real side-impact frame, wear my seatbelt, etc. But that doesn't mean that the actually survivability of an accident hasn't gotten a lot better, and won't continue to get a lot better.
As a somewhat silly example, I was at a convention (ok, I'm a geek, it was GenCon) where they didn't allow you to bring in outside food & drink. They weren't subjecting you to close inspection. One person tried to bring in a 24 case of soda, obvious upon inspection.
The security guard told them they had to give them the soda. The poor security guard unfortunately had to deal with an energetic, geeky law student. IANAL, but as I understand it the guard could legally refuse entry but not confiscate, but wasn't trained very precisely for this. The student started ranting about how that was illegal search and seizure (which, I think, only applies to governments anyway) and just kept doing it until he was well inside. But I believe the student was technically correct that the guard couldn't actually seize the soda.
Nope, they don't confiscate stuff at the airport (generally)
The power to confiscate your stuff is much harder to establish than the power to deny you access. At airport security, you have the option of keeping your nailclippers and leaving the TSA line. Usually you'll "voluntarily surrender" your nailclippers instead of missing your flight.
Just after 9/11, a friend of mine left the line and convinced his airline ticket counter to hold onto his knife until he returned home a week later. But he had enough time to do this and go back through the security line.
They could confiscate things that are illegal to posess, like drugs explosives or concealed firearms. They can confiscate stuff, I think, AFTER you pass through security, if they determined you were trying to get it past.
Since this is/., I'll bother to point out that someone here definitely got stuff confiscate at the airport by a guard who didn't understand this or, at least, didn't bother to illuminate your options. But that doesn't mean you couldn't have legally refused. I'm also not claiming that having a camera in a defense establishment wouldn't get confiscated.
Any mac with smoothly netboot and it's easy to configure. That is not my impression of x86 nix. To be fair, it's not the OS - it's OpenFirmware vs. PC BIOS (both for variety and because it's often less powerful)
I think you underestimate technology. Further, I think you misperceive the driving principle behind what is actually adopted.
If you crash at high enough speeds, you die. But what changes routinely is what speed that is. When my father was growing up, cars didn't HAVE seatbelts. They're still fighting to get people to wear them.
For instance, racing cars are routinely surviveable at very high speeds. But they cost more when they crash (because they do a lot of normalizing by breaking themselves) and they depend upon you strapping yourself into a working saftey harness.
When people don't use seatbelts, why would you expect them to use a harness? The problem you have is that if you sold a car with a standard harness, no one would buy that car because it would be more annoying to get into and out of. How much more will you pay for your car to be safer?
I _do_ suspect that the ability to accelerate and generally control a car at a given speed will generally continue to outpace the ability to reliably survive a crash at that speed. At least for cars not designed to pay attention to speed limits.
Unless Fords suddenly run better than Toyotas, which seems unlikely, that would be false advertising:) It might possibly also be libel or slander (I forget which) if it led to the false belief that Toyotas were worse.
But, it's still not a trademark violation.
This is why car ads usually are very specific about what they mean by better, using non-arguable facts. Interior room as listed, hp, torque, particular features, third party awards...
I have an Atari 800 that I haven't used in a few years but expect to pull out again - Arkanoids. I'm using a wonderful Amdek monitor (RCA:) from an Apple][ as the monitor for hte PS1 that is my CD player.
My father still very occasionally mails Apple][s around the country (][e w/ the max memory expansion, 1 MB I think) for some project that was written in assembly for it.
A friend of mine's work bought something like a P2/200 or so with a single 16! MB DIMM, running DOS only, for backwards compatibility with something. It was named xxxxx386 I think indicating what it directly replaced.
My main laptop is a 233 Mhz Thinkpad. My primary desktop still has a full length ISA SB16 card - '94 it says. My fileserver/AIM box/secondary linux has one of those too - it's a PPro 200 and also has a '94 2 MB ATI video card. The guest workstation here is a PPro 180 (HP Vectra) with similar stuff. I was using a 1 MB video card as late as last year in one machine.
I'm using a Powermac 9500/120 as my primary SCSI machine (mainly, it runs my scanner) although it's been upped to a G3/300 (and it desperately needs more RAM, so if anybody has 95/96/85/86/72/7500 RAM they don't need, of any size...) I think they keyboard is probably from ~ '91.
I still use a Powerbook 3400 fairly regularly, and a Powerbook 170 very rarely. I'm also using a P100 as a firewall.
Soon I'll again be using an SGI Personal Iris (486) - as a table.
I just sold (!) a Mac Plus because someone wanted to use it, and wouldn't take it for free - along with an Imagewriter II.
My primary printer is an Apple Laserwriter Pro/630, which I think is '93ish (and really an HP)
In Windows 2000, at least, you must first enable hibernate. This all happens in Start->Settings-> Control Panels-> Power Options. With hibernate enabled, you can select separate idle times for: monitor off, disk off, standby, hibernate (separate for battery or AC, and also arrangeable in profiles) You can ALSO select what to do on a battery alarm (for which you set the battery left) a critical battery alarm (again configurable) and laptop close, power button, and sleep button.
So, in short, yes, you can make it do pretty much whatever you want. Mine, at least, will hibernate on critical battery alarm, even if it's already in standby.
MacOS X is by far the best desktop environment _I've_ ever used, and it's far better than XP. It does tend to be more expensive, of course.
It does almost everything you want it to, and it does it automatically, and they're constantly building new features in smooth ways.
It also has one of the largest available software bases around: It runs MacOSX software, MacOS7/8/9 software, linux/BSD software compiled for PPC (X11 isn't installed by default, but the OpenOffice.org installer smoothly includes it, for instance, and it's on the OSX CD) and has an available emulator (VPC) that allows you to run x86 in a window, including Windows or Linux.
Even they aren't perfect, but they're closer than anybody else. Oh, and "Mail" rocks, hard.
First of all, most people in this thread. are talking about suspend/standby, not hibernate. Hibernate is a no-power mode ('cept the clock) which writes all RAM data to disk, while standby is a low-power mode (no display, disk, etc.) that just basically waits. Hibernate is historically somewhat less reliable, although either will destroy open network connections. Both modes work quite well in Win2k+, although I'd certainly be scared in 95/98/ME.
On most laptops I've seen, you can set the bios to send standby, hibernate, or nothing to the OS when you close the case. Any effect can be used with the case open by selecting it from the Start-> Shutdown menu.
On my 233Mhz Thinkpad 600 (which is a wonderful if aged machine, but which isn't technically supported by Windows 2000 which is running it) I have case-close mapped to standby and the power-button mapped to hibernate. I also have autohibernate on low battery. So if I close it it goes to standby and from standby it'll shutdown if it gets in danger of running out of power to stay going. (Standby does _not_ last indefinitely on battery)
I've had Windows 2000 fail to recover on hibernate, but not very often and that machine had other issues. I've _thought_ standby was failing on this laptop because the response time to the wakeup button-press varies and isn't particularly fast. It's occasionally woken up without the mouse, but the mouse is finicky to start with (again, W2k doesn't properly support the onboard mouse) Sleeping and waking again has always fixed the problem, all applications still running.
All of that said, however, I certainly recommend saving everything important before sleeping, hibernating, changing power sources, or transporting the machine (even in case-closed but staying on mode) All of those things are somewhat more risky than doing nothing, but less risky than some applications.
RAID cache ram is supposed to persist during a power outage. Persistent cache RAM in a RAID array or SCSI controller allows your controller to respond to sync() commands without lying (which would be dangerous) or waiting for the disk to get to the part where you can write that data. So it makes small data writes instantaneous, and can't be replicated by more main memory like cached reads can be. These small writes would otherwise have large seek times to find the right disk areas (at least on non-journalling filesystems)
I don't know this product. I don't know when it's from. But start out thinking laptop RAM for the static requirements, which is more. It may furthermore be that there didn't exist a standard part that met their requirements for size, response time, bandwidth, etc, WHEN they were designing the unit, even if one came out immediately thereafter. So they might have done this to get you a better product.
IANAL, but you're quite wrong about that. In Illinois at least, and I believe most of the US, you are often responsible for things someone does when you loan them a car.
If some extremely unpredictable act happens your insurance will be liable before theirs, if your insurance covers that person driving (most do) In that way you're being fiscally responsible.
More importantly, if the plaintiff can show that you knew or should have known they were a poor driver, you then can be liable for having put a weapon into dangerous hands. I believe this has been used to achieve manslaughter charges in extreme cases.
I'm not a terribly liberal person, but I'm currently decisively anti-death penalty. Life without the option for parole COSTS less money for society. Apparently we spend so much money fighting appeals and paying both sides of them that housing and feeding for life is cheaper.
I believe the chance of someone escaping from our maximum security prison is essentially zero. (If they could escape, I imagine they could do it from death row, too, and likely would try faster) And the few occasions I know of where it has happened have had rapid successful manhunts. Perhaps I'm being too idealistic on this point, and I agree it's a prerequisite for my major point.
As I've heard it explained, the commandment said you shouldn't waste the lives of people, but "people" basically meant those people in your tribe. Everyone else was considered sortof a savage, since they were likely to come attack you. (and vice versa)
And furthermore that waste was pretty loosely interpreted. You could certainly argue that "everyone is our tribesman now..." but it certainly wouldn't be the original meaning.
Of course, not randomly killing people in your own tribe is a good way to keep your numbers up, as is making sure you only use sperm if you're breeding. So those factors do tend to make a strong tribe.
Of course, the thou, shalt, thy stuff is junk, because it wasn't even english. But I think it sounds better that way.
My first piece of advice is to let us know where you're located so you can get your/. networking going. I'm in Chicago, for instance. If you're good and that cheap, I might contract you occasionally.
I'm doing this right now. I'm a bit older than you and have more experience, but I also have more bills : )
My experiences: In a real business the systems are either totally unimportant or they "have to" work. So most things anyone will bother with are going to get fixed, and you're being compared to those competitors that you're undercutting.
In most consumer settings (and some small businesses that are more poorly managed) they're comparing the amount of money to "just living with it" and the price drops to the range where very few people can make a living at it. This is a great niche for you while you're young.
I set a standard rate and then discount often. I'll often negotiate a discount when I'm arranging an appointment. That allows you to get around the "cheap, must be worthless" idea without necessarily charging too much. Usually I ask people whether this problem is urgent. If it's not, I offer a discount for scheduling flexibilty, on the condition that I might have to cancel if an emergency situation comes up. Or make coupons. Have a high hourly rate but then offer to flat charge when you've seen the problem.
Be very attentive. Most computer support people pay very little attention to the actual desires of their clients.
Take checks. I don't care what people said above, just take them. Don't trust the money until it clears, and know your bank might charge you a fee if it bounces (up to $25!) but you need to look like you trust them.
Don't keep working for someone who's never paid you. Do generally keep working for someone who's already paid you on lots of previous deals, unless you think they're going to skip on this one. If someone asks to pay you later, DO negotiate for partial payment. It demonstrates they believed you were owed payment, and furthermore it gets you some money. Even a 1/2 payment still beats bagging groceries...
www.irs.gov You generally need to make quarterly tax payments. There's about 234324 other things.
You can always argue forever about why a certain policy happened. Certainly, I was not in Clinton's head. I believe the encryption was removed because it was already defeated, and the defeating devices were being distributed. That would have been illegal had the DMCA already been passed.
There was definitely a time when encryption was on when certain civilian devices were more accurate than the military ones. Perhaps simply a faster time-to-market on a later generation model. I was under the impression is was due to a more basic difference, but I couldn't swear by that. (Nor could I swear that all the military ones didn't have a secret button on the bottom that said "pretend to suck" for use whenever they were tested.)
The particular example I was referring to was actually GPS in use in interstate trucking. Apparently you can't tell from any maps available whether someone is (for instance) in the correct lane based on their in-truck GPS, because it's not accurate enough. But you can easily tell if you put reporting GPS transcievers in a lot of vehicles, because the results are very repeatable. So you can easily tell that one of them was not where the huge majority of them had gone.
Of course, this depends on the sometimes weak assumption that the majority of those vehicles were in the lane...
The dominant reason for mirroring is data availability. In linux, the OS is perfectly capable of doing this perfectly well. So we need a reason to have a _hardware_ raid card. There are three that I can think of:
1. Additional IDE channels. 2. No use of main CPU (although this apparently is NOT true of many of the listed cards, it would be a good reason) 3. Cache. A real raid controller caches the last 64MB at least of transactions, which especially avoids lots of seek-time waiting, hugely reducing disk thrashing. More is better. In linux, your main memory already does this for you, but it uses the main CPU to do it. 4. Battery backed cache. A real raid controller has a battery backup for the cache, solving the problem of worrying about your unsynced (to the drive) data in a crash without doing those unoptimized writes. This only matters for writes.
My ultimate mirroring controller is *drumroll* another linux box as a NAS. Put 1.5 GB of RAM in it, most of which will automatically be used as cache. Don't boot into X;) Share partitions over NFS, or network protocol dejour. Gigabit ethernet should exceed the throughput you were actually getting from those cards. (ATA 100 and 100mb ethernet are approximately the same speed...)
For added fun, install other file services, and make it really work as a NAS.
To optimize for cost, use whatever hardware you have laying around. Anything with PCI should work adequately. Machines with at least UDMA will be more responsive (generally PII +) and for bonus cheapness put 4 disks on it. (1 of each mirrorset on each chain) So the cost for many people is free.
For real performance use a MB that supports two channels of the ATA speed the disks really support. And buy an IDE controller (or a scsi controller) if you need more disks than your channels support well. Practically speaking, ATA66 is still almost enough for most common drives right now.
My mediocre answer to battery backed cache is a UPS.
The next complaint is usually about being able to mirror the boot drive if your mirror is in the NAS. My answer to this is to go ahead and softmirror the boot drive in the workstation. But try to have very little written to that drive that will be waited for, and very little read from after boot. Even better is to netboot from a CD or floppy you have many copies of.
That certainly wasn't true for a while, although I haven't been keeping up.
Originally, at least, the military used certain GPS frequencies, and the civilians others. The civilians were scrambled to reduce effectiveness, so the military ones were substantially better.
But this was preDMCA, so they unscrambled it. After a year or so, the high end civvie GPSs were actually MORE accurate than the military ones, because it turns out the frequency was actually slightly better.
That said, GPS is MUCH more repeatable than it is accurate, so the military might have some advantages there. (If you make a map USING GPS it's damn accurate at placing new GPS devices in the same spot - but it's not necessarily a geometrically true map to the actual dimensions of the space.) You can calibrate a GPS using either historical measurements nearby or a known differential GPS transciever. While both techniques are available to civilians, I'd guess hte military is more likely to spend money on them.
My mother definitely seemed to have had a harder time getting a job because she had a PhD. (In English, for a teaching job) The basic deal is either
1) A big company has to pay you more for a PhD because they have policies and don't have the leeway to say that a PhD took a Master's level job. Therefore sometimes relatively equivalent candidates will be decided in terms of who's lighter on the pocketbook.
2) A company with the leeway to offer you less money and benefits thinks you won't take it.
But I think it's worth it, because when you find a job it'll probably be a better one. My advice is to find a job, get a PhD, and then you have the leisure to look for a GREAT position.
In response to another comment: Even if 99.9% of/. is PhD free, 0.1% of/. is a helluva lotta people;)
Slashdot Mirror
Perhaps I have been trolled. But I'll elaborate, just in case I haven't.
The guards are not required to inform you of your rights. In fact, there are only a few narrow instances where you are required to be informed of your rights at all. As I said, I bet someone here has encountered a guard who didn't know. There are a lot of them, after all.
The guards are NOT supposed to hold onto your items for you. Items you leave with the guards are destroyed. If you read my post, it was the ticket counter that would hold onto the item for my friend. Even then they certainly were not obligated to, and might have opened themselves to some liability if it had been lost. So this was certainly lucky. Returning an item to your car, for instance, would be reliable.
To reiterate, if you get stopped for something, and if you tried to leave the line with it, and if they confiscated it anyway, then that would've been illegal. And even illegal things happen every day.
I'll mention one more exception: It's may be (and probably is) a violation of law to attempt to circumvent their security. I don't doubt that they could arrest you and/or confiscate your stuff if they believed you were purposefully trying to circumvent them. But if you'd run afoul of that, you would likely have been interrogated, not just relieved of some item.
You're seeing some reasonable trees, but you're missing the forest.
I don't disagree with the detail of your point - my parents late 70s (?) Oldsmobile Cutlass was rear ended at approximately 50 mph. Luckily it was parked and no one was inside. It was totalled, but essentially the correct size. Three smaller foreign cars in front of it were compacted tremendously. The momentum of the traveling vehicle is it's m1v1, while the end momentum of the system is going to be the same. So the velocity change of the stationary vehicle is m1v1/(m1+m2) Obviously, the ideal case is for your semitruck to get hit by a speck of dust. But assuming your car weighs 3x as much as mine and you hit me at 40 mph, the basic idea is we'd both end up going 30, you've undergone a 10mph collision, I've undergone a 30mph one.
But that's a false argument on many levels, especially regarding our current discussion. For ease of discussion here, lets compare hitting something of essentially infinite momentum, like a bridge. In this case the velocity change of your car is going to be to zero, and quickly. In this case I'd bet a well designed newer car with crumple zones and air bags would be much more survivable at, say, 40mph than an older one without them, because the mass doesn't matter. I'm not saying either is very survivable at 75mph, today. This applies pretty well to you hitting a semi, actually, too. Basically hitting a car is MUCH better...
Now, certainly, if I was going to hit something with a roughly similar mass, I'd rather be in the heavier car than the lighter one. Or if I was going to hit anything under a critical threshold where the collision wasn't going to be too great, like a signpost, a newer (breakaway) powerline...
Car-car accidents involve a devilish number of details, too...
To wrapup, I frankly think being a proficient driver, being aware of your surroundings, having good tires and brakes, etc, are more important than 10% more crumple zone. And I certainly like a real side-impact frame, wear my seatbelt, etc. But that doesn't mean that the actually survivability of an accident hasn't gotten a lot better, and won't continue to get a lot better.
yeah, so I posted twice. Shoot me.
As a somewhat silly example, I was at a convention (ok, I'm a geek, it was GenCon) where they didn't allow you to bring in outside food & drink. They weren't subjecting you to close inspection. One person tried to bring in a 24 case of soda, obvious upon inspection.
The security guard told them they had to give them the soda. The poor security guard unfortunately had to deal with an energetic, geeky law student. IANAL, but as I understand it the guard could legally refuse entry but not confiscate, but wasn't trained very precisely for this. The student started ranting about how that was illegal search and seizure (which, I think, only applies to governments anyway) and just kept doing it until he was well inside. But I believe the student was technically correct that the guard couldn't actually seize the soda.
The security guard relented.
Nope, they don't confiscate stuff at the airport (generally)
/., I'll bother to point out that someone here definitely got stuff confiscate at the airport by a guard who didn't understand this or, at least, didn't bother to illuminate your options. But that doesn't mean you couldn't have legally refused. I'm also not claiming that having a camera in a defense establishment wouldn't get confiscated.
The power to confiscate your stuff is much harder to establish than the power to deny you access. At airport security, you have the option of keeping your nailclippers and leaving the TSA line. Usually you'll "voluntarily surrender" your nailclippers instead of missing your flight.
Just after 9/11, a friend of mine left the line and convinced his airline ticket counter to hold onto his knife until he returned home a week later. But he had enough time to do this and go back through the security line.
They could confiscate things that are illegal to posess, like drugs explosives or concealed firearms. They can confiscate stuff, I think, AFTER you pass through security, if they determined you were trying to get it past.
Since this is
Any mac with smoothly netboot and it's easy to configure. That is not my impression of x86 nix. To be fair, it's not the OS - it's OpenFirmware vs. PC BIOS (both for variety and because it's often less powerful)
I think you underestimate technology. Further, I think you misperceive the driving principle behind what is actually adopted.
If you crash at high enough speeds, you die. But what changes routinely is what speed that is. When my father was growing up, cars didn't HAVE seatbelts. They're still fighting to get people to wear them.
For instance, racing cars are routinely surviveable at very high speeds. But they cost more when they crash (because they do a lot of normalizing by breaking themselves) and they depend upon you strapping yourself into a working saftey harness.
When people don't use seatbelts, why would you expect them to use a harness? The problem you have is that if you sold a car with a standard harness, no one would buy that car because it would be more annoying to get into and out of. How much more will you pay for your car to be safer?
I _do_ suspect that the ability to accelerate and generally control a car at a given speed will generally continue to outpace the ability to reliably survive a crash at that speed. At least for cars not designed to pay attention to speed limits.
Unless Fords suddenly run better than Toyotas, which seems unlikely, that would be false advertising :) It might possibly also be libel or slander (I forget which) if it led to the false belief that Toyotas were worse.
But, it's still not a trademark violation.
This is why car ads usually are very specific about what they mean by better, using non-arguable facts. Interior room as listed, hp, torque, particular features, third party awards...
you couldn't perhaps forward me that, could you? It sounds neat.
I have an Atari 800 that I haven't used in a few years but expect to pull out again - Arkanoids. I'm using a wonderful Amdek monitor (RCA:) from an Apple][ as the monitor for hte PS1 that is my CD player.
My father still very occasionally mails Apple][s around the country (][e w/ the max memory expansion, 1 MB I think) for some project that was written in assembly for it.
A friend of mine's work bought something like a P2/200 or so with a single 16! MB DIMM, running DOS only, for backwards compatibility with something. It was named xxxxx386 I think indicating what it directly replaced.
My main laptop is a 233 Mhz Thinkpad. My primary desktop still has a full length ISA SB16 card - '94 it says. My fileserver/AIM box/secondary linux has one of those too - it's a PPro 200 and also has a '94 2 MB ATI video card. The guest workstation here is a PPro 180 (HP Vectra) with similar stuff. I was using a 1 MB video card as late as last year in one machine.
I'm using a Powermac 9500/120 as my primary SCSI machine (mainly, it runs my scanner) although it's been upped to a G3/300 (and it desperately needs more RAM, so if anybody has 95/96/85/86/72/7500 RAM they don't need, of any size...) I think they keyboard is probably from ~ '91.
I still use a Powerbook 3400 fairly regularly, and a Powerbook 170 very rarely. I'm also using a P100 as a firewall.
Soon I'll again be using an SGI Personal Iris (486) - as a table.
I just sold (!) a Mac Plus because someone wanted to use it, and wouldn't take it for free - along with an Imagewriter II.
My primary printer is an Apple Laserwriter Pro/630, which I think is '93ish (and really an HP)
In Windows 2000, at least, you must first enable hibernate. This all happens in Start->Settings-> Control Panels-> Power Options. With hibernate enabled, you can select separate idle times for:
monitor off, disk off, standby, hibernate (separate for battery or AC, and also arrangeable in profiles) You can ALSO select what to do on a battery alarm (for which you set the battery left) a critical battery alarm (again configurable) and laptop close, power button, and sleep button.
So, in short, yes, you can make it do pretty much whatever you want. Mine, at least, will hibernate on critical battery alarm, even if it's already in standby.
MacOS X is by far the best desktop environment _I've_ ever used, and it's far better than XP. It does tend to be more expensive, of course.
It does almost everything you want it to, and it does it automatically, and they're constantly building new features in smooth ways.
It also has one of the largest available software bases around: It runs MacOSX software, MacOS7/8/9 software, linux/BSD software compiled for PPC (X11 isn't installed by default, but the OpenOffice.org installer smoothly includes it, for instance, and it's on the OSX CD) and has an available emulator (VPC) that allows you to run x86 in a window, including Windows or Linux.
Even they aren't perfect, but they're closer than anybody else. Oh, and "Mail" rocks, hard.
First of all, most people in this thread. are talking about suspend/standby, not hibernate. Hibernate is a no-power mode ('cept the clock) which writes all RAM data to disk, while standby is a low-power mode (no display, disk, etc.) that just basically waits. Hibernate is historically somewhat less reliable, although either will destroy open network connections. Both modes work quite well in Win2k+, although I'd certainly be scared in 95/98/ME.
On most laptops I've seen, you can set the bios to send standby, hibernate, or nothing to the OS when you close the case. Any effect can be used with the case open by selecting it from the Start-> Shutdown menu.
On my 233Mhz Thinkpad 600 (which is a wonderful if aged machine, but which isn't technically supported by Windows 2000 which is running it) I have case-close mapped to standby and the power-button mapped to hibernate. I also have autohibernate on low battery. So if I close it it goes to standby and from standby it'll shutdown if it gets in danger of running out of power to stay going. (Standby does _not_ last indefinitely on battery)
I've had Windows 2000 fail to recover on hibernate, but not very often and that machine had other issues. I've _thought_ standby was failing on this laptop because the response time to the wakeup button-press varies and isn't particularly fast. It's occasionally woken up without the mouse, but the mouse is finicky to start with (again, W2k doesn't properly support the onboard mouse) Sleeping and waking again has always fixed the problem, all applications still running.
All of that said, however, I certainly recommend saving everything important before sleeping, hibernating, changing power sources, or transporting the machine (even in case-closed but staying on mode) All of those things are somewhat more risky than doing nothing, but less risky than some applications.
RAID cache ram is supposed to persist during a power outage. Persistent cache RAM in a RAID array or SCSI controller allows your controller to respond to sync() commands without lying (which would be dangerous) or waiting for the disk to get to the part where you can write that data. So it makes small data writes instantaneous, and can't be replicated by more main memory like cached reads can be. These small writes would otherwise have large seek times to find the right disk areas (at least on non-journalling filesystems)
I don't know this product. I don't know when it's from. But start out thinking laptop RAM for the static requirements, which is more. It may furthermore be that there didn't exist a standard part that met their requirements for size, response time, bandwidth, etc, WHEN they were designing the unit, even if one came out immediately thereafter. So they might have done this to get you a better product.
those were always my favorite movies.
(well, it wasn't Roeper then)
Outlook Express has outstanding IMAP support. No, I'm not kidding and yes, I know this is /.
But I can't find another win mail client that works better for a large IMAP mailbox.
(Outlook horks, btw, only Express works)
IANAL, but you're quite wrong about that. In Illinois at least, and I believe most of the US, you are often responsible for things someone does when you loan them a car.
If some extremely unpredictable act happens your insurance will be liable before theirs, if your insurance covers that person driving (most do) In that way you're being fiscally responsible.
More importantly, if the plaintiff can show that you knew or should have known they were a poor driver, you then can be liable for having put a weapon into dangerous hands. I believe this has been used to achieve manslaughter charges in extreme cases.
I'm not a terribly liberal person, but I'm currently decisively anti-death penalty. Life without the option for parole COSTS less money for society. Apparently we spend so much money fighting appeals and paying both sides of them that housing and feeding for life is cheaper.
I believe the chance of someone escaping from our maximum security prison is essentially zero. (If they could escape, I imagine they could do it from death row, too, and likely would try faster) And the few occasions I know of where it has happened have had rapid successful manhunts. Perhaps I'm being too idealistic on this point, and I agree it's a prerequisite for my major point.
As I've heard it explained, the commandment said you shouldn't waste the lives of people, but "people" basically meant those people in your tribe. Everyone else was considered sortof a savage, since they were likely to come attack you. (and vice versa)
And furthermore that waste was pretty loosely interpreted. You could certainly argue that "everyone is our tribesman now..." but it certainly wouldn't be the original meaning.
Of course, not randomly killing people in your own tribe is a good way to keep your numbers up, as is making sure you only use sperm if you're breeding. So those factors do tend to make a strong tribe.
Of course, the thou, shalt, thy stuff is junk, because it wasn't even english. But I think it sounds better that way.
My first piece of advice is to let us know where you're located so you can get your /. networking going. I'm in Chicago, for instance. If you're good and that cheap, I might contract you occasionally.
I'm doing this right now. I'm a bit older than you and have more experience, but I also have more bills : )
My experiences:
In a real business the systems are either totally unimportant or they "have to" work. So most things anyone will bother with are going to get fixed, and you're being compared to those competitors that you're undercutting.
In most consumer settings (and some small businesses that are more poorly managed) they're comparing the amount of money to "just living with it" and the price drops to the range where very few people can make a living at it. This is a great niche for you while you're young.
I set a standard rate and then discount often. I'll often negotiate a discount when I'm arranging an appointment. That allows you to get around the "cheap, must be worthless" idea without necessarily charging too much. Usually I ask people whether this problem is urgent. If it's not, I offer a discount for scheduling flexibilty, on the condition that I might have to cancel if an emergency situation comes up. Or make coupons. Have a high hourly rate but then offer to flat charge when you've seen the problem.
Be very attentive. Most computer support people pay very little attention to the actual desires of their clients.
Take checks. I don't care what people said above, just take them. Don't trust the money until it clears, and know your bank might charge you a fee if it bounces (up to $25!) but you need to look like you trust them.
Don't keep working for someone who's never paid you. Do generally keep working for someone who's already paid you on lots of previous deals, unless you think they're going to skip on this one. If someone asks to pay you later, DO negotiate for partial payment. It demonstrates they believed you were owed payment, and furthermore it gets you some money. Even a 1/2 payment still beats bagging groceries...
www.irs.gov You generally need to make quarterly tax payments. There's about 234324 other things.
http://www.washingtonpost.com/wp-dyn/articles/A642 67-2003Aug29.html
They arrested him. 18 years old - Minnesota.
You can always argue forever about why a certain policy happened. Certainly, I was not in Clinton's head. I believe the encryption was removed because it was already defeated, and the defeating devices were being distributed. That would have been illegal had the DMCA already been passed.
There was definitely a time when encryption was on when certain civilian devices were more accurate than the military ones. Perhaps simply a faster time-to-market on a later generation model. I was under the impression is was due to a more basic difference, but I couldn't swear by that. (Nor could I swear that all the military ones didn't have a secret button on the bottom that said "pretend to suck" for use whenever they were tested.)
The particular example I was referring to was actually GPS in use in interstate trucking. Apparently you can't tell from any maps available whether someone is (for instance) in the correct lane based on their in-truck GPS, because it's not accurate enough. But you can easily tell if you put reporting GPS transcievers in a lot of vehicles, because the results are very repeatable. So you can easily tell that one of them was not where the huge majority of them had gone.
Of course, this depends on the sometimes weak assumption that the majority of those vehicles were in the lane...
The dominant reason for mirroring is data availability. In linux, the OS is perfectly capable of doing this perfectly well. So we need a reason to have a _hardware_ raid card. There are three that I can think of:
;) Share partitions over NFS, or network protocol dejour. Gigabit ethernet should exceed the throughput you were actually getting from those cards. (ATA 100 and 100mb ethernet are approximately the same speed...)
1. Additional IDE channels.
2. No use of main CPU (although this apparently is NOT true of many of the listed cards, it would be a good reason)
3. Cache. A real raid controller caches the last 64MB at least of transactions, which especially avoids lots of seek-time waiting, hugely reducing disk thrashing. More is better. In linux, your main memory already does this for you, but it uses the main CPU to do it.
4. Battery backed cache. A real raid controller has a battery backup for the cache, solving the problem of worrying about your unsynced (to the drive) data in a crash without doing those unoptimized writes. This only matters for writes.
My ultimate mirroring controller is *drumroll* another linux box as a NAS. Put 1.5 GB of RAM in it, most of which will automatically be used as cache. Don't boot into X
For added fun, install other file services, and make it really work as a NAS.
To optimize for cost, use whatever hardware you have laying around. Anything with PCI should work adequately. Machines with at least UDMA will be more responsive (generally PII +) and for bonus cheapness put 4 disks on it. (1 of each mirrorset on each chain) So the cost for many people is free.
For real performance use a MB that supports two channels of the ATA speed the disks really support. And buy an IDE controller (or a scsi controller) if you need more disks than your channels support well. Practically speaking, ATA66 is still almost enough for most common drives right now.
My mediocre answer to battery backed cache is a UPS.
The next complaint is usually about being able to mirror the boot drive if your mirror is in the NAS. My answer to this is to go ahead and softmirror the boot drive in the workstation. But try to have very little written to that drive that will be waited for, and very little read from after boot. Even better is to netboot from a CD or floppy you have many copies of.
That certainly wasn't true for a while, although I haven't been keeping up.
Originally, at least, the military used certain GPS frequencies, and the civilians others. The civilians were scrambled to reduce effectiveness, so the military ones were substantially better.
But this was preDMCA, so they unscrambled it. After a year or so, the high end civvie GPSs were actually MORE accurate than the military ones, because it turns out the frequency was actually slightly better.
That said, GPS is MUCH more repeatable than it is accurate, so the military might have some advantages there. (If you make a map USING GPS it's damn accurate at placing new GPS devices in the same spot - but it's not necessarily a geometrically true map to the actual dimensions of the space.) You can calibrate a GPS using either historical measurements nearby or a known differential GPS transciever. While both techniques are available to civilians, I'd guess hte military is more likely to spend money on them.
Outlook 2000, at least, has a dramatically inferior IMAP interface. Inferior to the point that it just didn't work with at least one server.
Outlook Express that came with Win2k on the other hand, worked fine. Same settings.
Possibly they fixed this in 2002.
My mother definitely seemed to have had a harder time getting a job because she had a PhD. (In English, for a teaching job) The basic deal is either
/. is PhD free, 0.1% of /. is a helluva lotta people ;)
1) A big company has to pay you more for a PhD because they have policies and don't have the leeway to say that a PhD took a Master's level job. Therefore sometimes relatively equivalent candidates will be decided in terms of who's lighter on the pocketbook.
2) A company with the leeway to offer you less money and benefits thinks you won't take it.
But I think it's worth it, because when you find a job it'll probably be a better one. My advice is to find a job, get a PhD, and then you have the leisure to look for a GREAT position.
In response to another comment: Even if 99.9% of