Your Rogers connection is also capped, my friend... You cannot get Rogers business (i.e. uncapped) service at a zoned residential address. Not even if you're running a business from your home. I've tried, and both the signup lady and tech dude were sympathetic, but the system would not let them override the zoning information to allow a business service to be installed. My next attempt was going to be to order business service for a local business, get the modem and plug it into my home cable connection. I'm not sure if the head-end would pick up on that or not.
However, I had an app a while back that could 'build' Operator SMS messages and send them out to peoples phones, so yeah, unless the Operator takes serious steps to secure this system, it's gonna be hacked in no time. Once hacked, the concept will be useless, and the manufacturers will stop including the kill-system in the firmware...
I've been trying to do this for some time now. In North America, at least, it's damn near impossible to get a hold of your carrier's SMSC so you can send an SMS without going through the SMS-Email gateway (which mangles the message so you can't send things like "voicemail" messages).
Then there are SMS gateways online, but pretty much all of the ones I've found are quite pricey, both in setup and per-message costs.
Which software did you use? Was it carrier-agnostic?
Polycom phones are simply the best bang for the buck. They are professional, "feel" right (handset is weighted correctly), sound perfect (polycom's been in the speakerphone business from the start), they are *designed* to be provisioned properly, and they fit in any business or small office environment.
My complaints with them are few:
NO NORMAL RINGTONES!!! UGH!!! GIVE US A BASIC SET OF BUSINESS-FRIENDLY RINGERS!!!
Can't set VLAN ID via DHCP
430/501 can't use that beautiful screen, 601 can at least use XHTML
lack of backlight
shitty web interface (honestly, drop this and give us XHTML on 430/501!)
SSSSSSSLLLLLOOOOOWWWWWWW bootup time
some minor menuing issues (why do I have to be an admin to reboot the phone from the menu?!)
Idiotic lockdown of firmware (have to go through your vendor to get it, can't get it direct from Polycom's FTP site)
MWI warble is not tuneable or turn-offable
minor issues involving presence and directories
I've got several shops running these. It's a beautiful thing to just ssh in, alter the xml file, and send a reboot to the phone remotely to change *anything* on these phones. I'm VERY satisfied with them, aside from my quick shit-list above.
Which approach is better? It's hard to say, but FAST benefits everyone, while GOOD benefits only the elite.
Nonsense. Total, utter nonsense.
What good is fast if you put in "ooga" and get back "3*(~..!`" ? Or worse, what good is fast if you put in known good data and get back corrupted-but-still-appears-to-be-good data?
No, sir, FAST does not benefit anyone but the speed freaks that don't give a shit for data integrity, or who feel that taking the system down to restore from backup is a valid option to data corruption. I'll stick with throwing more hardware at it and staying in a far more comfortable position of knowing my database is not only enforcing the constraints I place on the data going in, but can also retrieve the information exactly as it went in. I don't trust any DB that takes artistic license with my data.
If you're working, you call in sick, go on leave if necessary, go back to work when you can and no harm done.
If I call in sick, I am either docked pay (if you're hourly), and have to catch up on my own time. If I have clients coming in, I need to have their appointments rescheduled if possible. How is this any different for college? You grab a friend's notes or talk to the prof or TA.
College students officially get no unscheduled days off, for any reason.
Uh, yeah. Stop going to the pub every night, get up for class, and DO YOUR FUCKING JOB. Honestly, you whine like you are ENTITLED to graduate. Do your job; if you have an illness/death you deal with it. There are procedures in place for this, and if you'd actually HAD one of these legitimate happenings you'd have known about them because you'd have gone to the administration office and enquired.
You pay your tuition, you are entitled to go to the classes and do your best to learn the course material, and you're entitled to write the exams and get a degree if you show that you've assimilated the information correctly. This professor is going above and beyond to produce a value-added service that is NOT in his job description to provide, and people like you piss and moan that it's not free. Unbelievable.
RAID-5 works but it only solves part of the problem, namely the failure of a single hard drive. However, what happens if the data on the drive gets wiped out by a virus or a malicious user? The RAID array will not solve this problem. Or if you have multiple hard drive failures. The RAID array will not protect against that either.
That's why you back up *to* RAID, not just use RAID for day-to-day. Drives are cheap, capacity's there, and you can do full incrementals and get back any file from any point in time. You still need to worry about multiple drive failure, but then you also need to worry about your DVD backup or DLT tape melting. An array of RAID backups would be cumbersome, so just do quarterly backups to DVDs or a single large hard drive and keep that in a separate location.
Funny, I use charting in Excel more than I use any other feature in the entire Office suite. I regularly import csv data to graph easily. Packet jitter. CPU/VM/IO load. Process variables read in over a serial port from some proprietary equipment. I haven't found something smaller and lighter that allows me to do this as quickly and easily as dumping to CSV and importing into Excel to graph. gnuplot is a contender, but it's just not as fast for me to use it yet.
(Microsoft Office file format bug explanation deleted, as Microsoft Office can't do this even between versions anyway)
What I see as the biggest OO flaw is the spreadsheet. Graphing *sucks*. Mightily so. It's extraordinarily limited, it's slower than molasses in January, it's impossible to print a chart on a page (honestly, I've tried and tried to select just the chart and say "print this, fit it to one page" -- is this just a glaring oversight, or am I just stupid?). It's got some strange UI modes but those are just strange because I'm used to the way selection and cursor movement in selections work with Word... but honestly... charting/graphing simply *blows* in Open Office. I feel that is the single biggest failing of the suite.
If you ever buy another palm, pick one that doesn't do much. No mp3, video playing and the like. Not only you'll save money but much more importantly, you'll have a crappy battery life if you pick the kitchen sink models.
Battery life really has come down a lot from the old Palm Vx days (actually I started out on the Palm Pro, but the Vx and then the 515 were my favourites, with the Vx still being a favourite), but I get about 3-4 days out of my T|X. I had the Treo 650 and really wanted to love it, but it just wasn't happening. The TX has wifi and bt and the bigger screen I wanted. It lacks the LED and the vibrate that the 515 had, but it's an alright trade-off. It does what I want, has the connectivity I need these days, and isn't as thick or unstable as the 650 was.
I never have to take my bt devices out from where they're at to access them. In that sense, BT has been good for me. Your "phone is a PDA" argument only works if the converged device actually works well. The Treo650 is a crappy PDA, a crappy phone AND a crappy media player/camera all in one. It's too big and bulky for a phone (I've had one since November), it's far too unstable for a phone, it's BT is very very poor, it's got no wifi, so there goes the well-connected PDA aspect, it hasn't got a regular 3.5mm audio jack so you're fucked for a media player... the camera is sub-par (naturally)... so no, the phone-is-a-PDA doesn't exist. The others are Windows Mobile platform which is a no-start for me, and none of them is small enough to be a day-to-day phone.
So no, your bigass list of suck for BT is a far cry from my huge-ass list of suck for converged devices (with particular focus on the Treo 650).
exactly that, but give me bluetooth. That's all I'm interested in. No fucking camera, no mp3, no colour, no MMS, no 500 contact directory; I want to dial the phone from my PDA, and talk on the headset. That's it. Convergence is just a quick way to lose everything at once.
No, crippled. There has been some work to get the Wifi card to work, and in fact by manipulating the HAL tables a little you can get the T|X network stack to work (bluetooth, wifi, PPP) -- at least in theory... this was crippled on purpose to keep the cell carriers happy.
To elaborate, BT slave devices can be set to either Active or Parked. Parked devices can't talk back to the phone, but the phone still needs to transmit a beacon packet every time the slaves reserved time slice comes up. Active mode devices can communicate based on one of several protocols. Handsfree requires Synchronous Connection-Oriented or SCO, which provides 64Kb CDR audio communication. It also requires that the physical link connnection remain in the Active state.
The phone shuts down the audio connection about 5 seconds after you stop playing with it. When you hit a button it wakes the device back up and re-establishes the audio path, so it certainly seems to be acting as your research has indicated it should.
Where my beef is is when it closes down the audio channel and keeps the connection in full-active. I don't think it's parking the connection, as the phone does not respond to any SDP or even HCI events outside of the headset that I've been able to tell... In other words, it does seem to shut down audio to conserve battery of both the phone and the headset, but it keeps the connection in full-out active mode. (it is probably closing down the SCO connection but nothing else).
Cell phones probably have very light BT stacks, including extremely limited buffers. That probably sets a hard limit on the number of devices that they can form active physical links with. To that end, the cell makers most likely set up handsfree systems to automatically park all other physical connections.
That's what I would have thought, too, but the way the phones seem to implement it makes it impossible to dial a phone using a PDA, and use the headset to talk. Your note about TDMA use with the master connections is interesting, but I found this to be intriguing:
It should be possible for your phone to be a SLAVE to your other devices while MASTER to the handsfree.
I'll have to play with this a little. The T|X bluetooth stack seems pretty buggered in and of itself, but I'll have to play with BlueZ to see if I can't get my laptop to open a connection to the phone as a master... Very interesting.
Lesson: there is more to this than you think. The core spec alone is 1300 pages of IEEE dribble.
Indeed. I've been doing a lot of DeviceNet work lately and that's a spec that's about as easy to work through as this is. It seems strange that this (using a PDA to dial a cell, and talk on the BT headset) would be so difficult, especially as this was an application Bluetooth was supposed to excel at.
I've used a Treo650 since November last year. It does not easily work. It's unstable, the bluetooth is shitty, the network connectivity lacks wifi (onboard doesn't bother me, but they crippled it so the sdio card won't work), the phone app itself sucks ass... It works, but barely.
Agreed. I am a longtime fan of Palm, but their smartphone line sucks hairy goat nad.
Weak bluetooth stack, no wifi capability (crippled, even), legendary instability, low memory, inability to properly use an SD/MMC card for memory, not just weak but positively craptastic phone app... all in a bulky-assed package. That's the Treo 600/650/700p.
I've moved to a Nokia 6265i with a T|X. It's still not perfect, because Palm's crippled the bluetooth dialing of their handhelds, but I can hack around that easily enough. However I cannot find a phone that doesn't lock out all bluetooth communications when a headset is connected.
Now allow me to elaborate a bit: Pair phone and headset. Pair phone and PDA. If the headset is active (audio is transferred) I can certainly understand the phone ignoring every other BT device out there; it takes a lot of horsepower to route audio. However the phone and headset are idle (no audio transfer but the connection active), the phone still ignores all other devices! You need to either shut the headset OFF or tell the phone to kill the connection. This means it's impossible to use the PDA to dial a number, and then talk on the headset without a lot of fucking around.
Unfortunately it's not just the Nokia; I've tried the RAZR and another phone whose model escapes me... What on earth is preventing the phone from allowing connections if the headset connection is not routing audio? How the blue fuck are you supposed to use your PDA to store all the numbers and just dial the phone, and use a bluetooth headset?
Back on topic: I got the 650 because it had the good screen and the Palm OS and the keyboard. The shitty phone app can be replaced with something like TAKephONE, and you can hack your way around the other intentional cripplings, but you get to a point where the instability, crappy BT and lack of Wifi just make you scream "enough!"
I'm not looking forward to this new phone; they'll just fuck it up like they always do. Palm is dead. PalmOne sucks balls.
Given the choice between either irradiating or phage-treating the stuff, or else risk giving their customers food poisoning, which should the packing companies choose?
Irradiating, clearly. Once the meat passes through the irradiating device, it is 'dead' -- there is nothing living in it, and it's not radioactive. We do this already with apples and potatoes, IIRC. Why not meat?
Windows Desktop Search does notice, and updates the index in real-time. With WDS, Outlook is fine. I just have one huge inbox, with the past 3 months in in - and auto-archive everything older than that so I don't outrun my Exchange quota.
I want a goddamned OSS autoarchiver -- index the stuff you go to archive, store it in an afio archive (so you don't have to untar the entire damn thing) and let me selectively search archive only, archive+current, or current only. DAMN I wish there was something like that that out there for kmail or even more generally, for Maildirs.
While I agree that tapes are an old, dying technology, there is no need to resort to hyperbole.
They'll appear to backup ok, but most will be bad after several uses. If you have a terabyte to back up, you're going to need about a dozen tapes a night, no matter how little has changed.
If you don't verify your backups (even on disk or network backup) then you deserve to lose your data. And since when does anyone do a full nightly backup of terabytes of data? You do quarterly full backups with monthly, weekly and daily incrementals. You take home one tape or drive, and with a proper rotation schedule you can pull up any change of any file within the last quarter.
In other words, once you get to fighting, or to running away, you aren't going to listen to reason until you've fought it out or have run far, far away.
Which book of his is this from? Which does he consider "cooling down" -- fighting it out (interally) or running away? To me cooling down's a third option which will let reason prevail again.
I only have two custom keyboard shortcuts: Alt-` to bring up a konsole shell prompt, and alt-k to bring up konqueror. The other few programs I use regularly find their way to the top of my K menu automatically.
I have to say that KDE ioslaves just rock. Being able to type smb://foo/data and get on a samba share, or even locate:ooga to find what I'm looking for is beyond fast and simple. Similar to Konqueror shortcuts, I find it faster to alt-k, then "gg:what I'm looking for" than it is to use the google search bar, which I have been turning off since it came out.:-) They text area for the location bar is already preselected.
Whatever happened to the 186? Why do you hear of 286, 386, 486, and 586, but never 186?
The 80186 was an 8088/86 hybrid with on-chip peripherals. It was intended for embedded applications. The old unisys ICONs used them.
(that was from memory, but Wikipedia backs me up on this. God I must be old to not only remember this stuff but also the NEC v20 and MOS 65xx histories...
Any word on something like that for Linux fileservers? I am envisioning (as a first pass thought) a cron job with find -ctime that replaced the file with a symlink to the online compressed storage, but you may need some kind of hook into Samba or a lower level hook into the FS itself that grabbed it out of "cold storage" so to speak.
Slashdot Mirror
Your Rogers connection is also capped, my friend... You cannot get Rogers business (i.e. uncapped) service at a zoned residential address. Not even if you're running a business from your home. I've tried, and both the signup lady and tech dude were sympathetic, but the system would not let them override the zoning information to allow a business service to be installed. My next attempt was going to be to order business service for a local business, get the modem and plug it into my home cable connection. I'm not sure if the head-end would pick up on that or not.
However, I had an app a while back that could 'build' Operator SMS messages and send them out to peoples phones, so yeah, unless the Operator takes serious steps to secure this system, it's gonna be hacked in no time. Once hacked, the concept will be useless, and the manufacturers will stop including the kill-system in the firmware...
I've been trying to do this for some time now. In North America, at least, it's damn near impossible to get a hold of your carrier's SMSC so you can send an SMS without going through the SMS-Email gateway (which mangles the message so you can't send things like "voicemail" messages).
Then there are SMS gateways online, but pretty much all of the ones I've found are quite pricey, both in setup and per-message costs.
Which software did you use? Was it carrier-agnostic?
Polycom phones are simply the best bang for the buck. They are professional, "feel" right (handset is weighted correctly), sound perfect (polycom's been in the speakerphone business from the start), they are *designed* to be provisioned properly, and they fit in any business or small office environment.
My complaints with them are few:
I've got several shops running these. It's a beautiful thing to just ssh in, alter the xml file, and send a reboot to the phone remotely to change *anything* on these phones. I'm VERY satisfied with them, aside from my quick shit-list above.
Which approach is better? It's hard to say, but FAST benefits everyone, while GOOD benefits only the elite.
Nonsense. Total, utter nonsense.
What good is fast if you put in "ooga" and get back "3*(~..!`" ? Or worse, what good is fast if you put in known good data and get back corrupted-but-still-appears-to-be-good data?
No, sir, FAST does not benefit anyone but the speed freaks that don't give a shit for data integrity, or who feel that taking the system down to restore from backup is a valid option to data corruption. I'll stick with throwing more hardware at it and staying in a far more comfortable position of knowing my database is not only enforcing the constraints I place on the data going in, but can also retrieve the information exactly as it went in. I don't trust any DB that takes artistic license with my data.
If you're working, you call in sick, go on leave if necessary, go back to work when you can and no harm done.
If I call in sick, I am either docked pay (if you're hourly), and have to catch up on my own time. If I have clients coming in, I need to have their appointments rescheduled if possible. How is this any different for college? You grab a friend's notes or talk to the prof or TA.
College students officially get no unscheduled days off, for any reason.
Uh, yeah. Stop going to the pub every night, get up for class, and DO YOUR FUCKING JOB. Honestly, you whine like you are ENTITLED to graduate. Do your job; if you have an illness/death you deal with it. There are procedures in place for this, and if you'd actually HAD one of these legitimate happenings you'd have known about them because you'd have gone to the administration office and enquired.
You pay your tuition, you are entitled to go to the classes and do your best to learn the course material, and you're entitled to write the exams and get a degree if you show that you've assimilated the information correctly. This professor is going above and beyond to produce a value-added service that is NOT in his job description to provide, and people like you piss and moan that it's not free. Unbelievable.
RAID-5 works but it only solves part of the problem, namely the failure of a single hard drive. However, what happens if the data on the drive gets wiped out by a virus or a malicious user? The RAID array will not solve this problem. Or if you have multiple hard drive failures. The RAID array will not protect against that either.
That's why you back up *to* RAID, not just use RAID for day-to-day. Drives are cheap, capacity's there, and you can do full incrementals and get back any file from any point in time. You still need to worry about multiple drive failure, but then you also need to worry about your DVD backup or DLT tape melting. An array of RAID backups would be cumbersome, so just do quarterly backups to DVDs or a single large hard drive and keep that in a separate location.
The answer is to buy a laser printer AND an inkjet. Always use the laser printer unless you really need color.
And discover that the ink cartridge is either dried up or the jets are crusted over from lack of use. Ink jets are cheap, but suck.
A chart in Excel does me and others little good.
Funny, I use charting in Excel more than I use any other feature in the entire Office suite. I regularly import csv data to graph easily. Packet jitter. CPU/VM/IO load. Process variables read in over a serial port from some proprietary equipment. I haven't found something smaller and lighter that allows me to do this as quickly and easily as dumping to CSV and importing into Excel to graph. gnuplot is a contender, but it's just not as fast for me to use it yet.
Open Office has another, more serious downfall.
(Microsoft Office file format bug explanation deleted, as Microsoft Office can't do this even between versions anyway)
What I see as the biggest OO flaw is the spreadsheet. Graphing *sucks*. Mightily so. It's extraordinarily limited, it's slower than molasses in January, it's impossible to print a chart on a page (honestly, I've tried and tried to select just the chart and say "print this, fit it to one page" -- is this just a glaring oversight, or am I just stupid?). It's got some strange UI modes but those are just strange because I'm used to the way selection and cursor movement in selections work with Word... but honestly... charting/graphing simply *blows* in Open Office. I feel that is the single biggest failing of the suite.
If you ever buy another palm, pick one that doesn't do much. No mp3, video playing and the like. Not only you'll save money but much more importantly, you'll have a crappy battery life if you pick the kitchen sink models.
Battery life really has come down a lot from the old Palm Vx days (actually I started out on the Palm Pro, but the Vx and then the 515 were my favourites, with the Vx still being a favourite), but I get about 3-4 days out of my T|X. I had the Treo 650 and really wanted to love it, but it just wasn't happening. The TX has wifi and bt and the bigger screen I wanted. It lacks the LED and the vibrate that the 515 had, but it's an alright trade-off. It does what I want, has the connectivity I need these days, and isn't as thick or unstable as the 650 was.
I never have to take my bt devices out from where they're at to access them. In that sense, BT has been good for me. Your "phone is a PDA" argument only works if the converged device actually works well. The Treo650 is a crappy PDA, a crappy phone AND a crappy media player/camera all in one. It's too big and bulky for a phone (I've had one since November), it's far too unstable for a phone, it's BT is very very poor, it's got no wifi, so there goes the well-connected PDA aspect, it hasn't got a regular 3.5mm audio jack so you're fucked for a media player... the camera is sub-par (naturally)... so no, the phone-is-a-PDA doesn't exist. The others are Windows Mobile platform which is a no-start for me, and none of them is small enough to be a day-to-day phone.
So no, your bigass list of suck for BT is a far cry from my huge-ass list of suck for converged devices (with particular focus on the Treo 650).
exactly that, but give me bluetooth. That's all I'm interested in. No fucking camera, no mp3, no colour, no MMS, no 500 contact directory; I want to dial the phone from my PDA, and talk on the headset. That's it. Convergence is just a quick way to lose everything at once.
No, crippled. There has been some work to get the Wifi card to work, and in fact by manipulating the HAL tables a little you can get the T|X network stack to work (bluetooth, wifi, PPP) -- at least in theory... this was crippled on purpose to keep the cell carriers happy.
To elaborate, BT slave devices can be set to either Active or Parked. Parked devices can't talk back to the phone, but the phone still needs to transmit a beacon packet every time the slaves reserved time slice comes up. Active mode devices can communicate based on one of several protocols. Handsfree requires Synchronous Connection-Oriented or SCO, which provides 64Kb CDR audio communication. It also requires that the physical link connnection remain in the Active state.
The phone shuts down the audio connection about 5 seconds after you stop playing with it. When you hit a button it wakes the device back up and re-establishes the audio path, so it certainly seems to be acting as your research has indicated it should.
Where my beef is is when it closes down the audio channel and keeps the connection in full-active. I don't think it's parking the connection, as the phone does not respond to any SDP or even HCI events outside of the headset that I've been able to tell... In other words, it does seem to shut down audio to conserve battery of both the phone and the headset, but it keeps the connection in full-out active mode. (it is probably closing down the SCO connection but nothing else).
Cell phones probably have very light BT stacks, including extremely limited buffers. That probably sets a hard limit on the number of devices that they can form active physical links with. To that end, the cell makers most likely set up handsfree systems to automatically park all other physical connections.
That's what I would have thought, too, but the way the phones seem to implement it makes it impossible to dial a phone using a PDA, and use the headset to talk. Your note about TDMA use with the master connections is interesting, but I found this to be intriguing:
It should be possible for your phone to be a SLAVE to your other devices while MASTER to the handsfree.
I'll have to play with this a little. The T|X bluetooth stack seems pretty buggered in and of itself, but I'll have to play with BlueZ to see if I can't get my laptop to open a connection to the phone as a master... Very interesting.
Lesson: there is more to this than you think. The core spec alone is 1300 pages of IEEE dribble.
Indeed. I've been doing a lot of DeviceNet work lately and that's a spec that's about as easy to work through as this is. It seems strange that this (using a PDA to dial a cell, and talk on the BT headset) would be so difficult, especially as this was an application Bluetooth was supposed to excel at.
I've used a Treo650 since November last year. It does not easily work. It's unstable, the bluetooth is shitty, the network connectivity lacks wifi (onboard doesn't bother me, but they crippled it so the sdio card won't work), the phone app itself sucks ass... It works, but barely.
Agreed. I am a longtime fan of Palm, but their smartphone line sucks hairy goat nad.
Weak bluetooth stack, no wifi capability (crippled, even), legendary instability, low memory, inability to properly use an SD/MMC card for memory, not just weak but positively craptastic phone app... all in a bulky-assed package. That's the Treo 600/650/700p.
I've moved to a Nokia 6265i with a T|X. It's still not perfect, because Palm's crippled the bluetooth dialing of their handhelds, but I can hack around that easily enough. However I cannot find a phone that doesn't lock out all bluetooth communications when a headset is connected.
Now allow me to elaborate a bit: Pair phone and headset. Pair phone and PDA. If the headset is active (audio is transferred) I can certainly understand the phone ignoring every other BT device out there; it takes a lot of horsepower to route audio. However the phone and headset are idle (no audio transfer but the connection active), the phone still ignores all other devices! You need to either shut the headset OFF or tell the phone to kill the connection. This means it's impossible to use the PDA to dial a number, and then talk on the headset without a lot of fucking around.
Unfortunately it's not just the Nokia; I've tried the RAZR and another phone whose model escapes me... What on earth is preventing the phone from allowing connections if the headset connection is not routing audio? How the blue fuck are you supposed to use your PDA to store all the numbers and just dial the phone, and use a bluetooth headset?
Back on topic: I got the 650 because it had the good screen and the Palm OS and the keyboard. The shitty phone app can be replaced with something like TAKephONE, and you can hack your way around the other intentional cripplings, but you get to a point where the instability, crappy BT and lack of Wifi just make you scream "enough!"
I'm not looking forward to this new phone; they'll just fuck it up like they always do. Palm is dead. PalmOne sucks balls.
It seems you simply don't understand what "memory" means in the technical sense. "Memory" is not required for learning, training, or routines.
Care to elaborate? How is memory not needed for learning?
Given the choice between either irradiating or phage-treating the stuff, or else risk giving their customers food poisoning, which should the packing companies choose?
Irradiating, clearly. Once the meat passes through the irradiating device, it is 'dead' -- there is nothing living in it, and it's not radioactive. We do this already with apples and potatoes, IIRC. Why not meat?
Windows Desktop Search does notice, and updates the index in real-time. With WDS, Outlook is fine. I just have one huge inbox, with the past 3 months in in - and auto-archive everything older than that so I don't outrun my Exchange quota.
I want a goddamned OSS autoarchiver -- index the stuff you go to archive, store it in an afio archive (so you don't have to untar the entire damn thing) and let me selectively search archive only, archive+current, or current only. DAMN I wish there was something like that that out there for kmail or even more generally, for Maildirs.
While I agree that tapes are an old, dying technology, there is no need to resort to hyperbole.
They'll appear to backup ok, but most will be bad after several uses. If you have a terabyte to back up, you're going to need about a dozen tapes a night, no matter how little has changed.
If you don't verify your backups (even on disk or network backup) then you deserve to lose your data. And since when does anyone do a full nightly backup of terabytes of data? You do quarterly full backups with monthly, weekly and daily incrementals. You take home one tape or drive, and with a proper rotation schedule you can pull up any change of any file within the last quarter.
In other words, once you get to fighting, or to running away, you aren't going to listen to reason until you've fought it out or have run far, far away.
Which book of his is this from? Which does he consider "cooling down" -- fighting it out (interally) or running away? To me cooling down's a third option which will let reason prevail again.
You linked to a 15W panel for US$179, or approximately $12/W. 120W would be $1440, all else being the same.
I only have two custom keyboard shortcuts: Alt-` to bring up a konsole shell prompt, and alt-k to bring up konqueror. The other few programs I use regularly find their way to the top of my K menu automatically.
I have to say that KDE ioslaves just rock. Being able to type smb://foo/data and get on a samba share, or even locate:ooga to find what I'm looking for is beyond fast and simple. Similar to Konqueror shortcuts, I find it faster to alt-k, then "gg:what I'm looking for" than it is to use the google search bar, which I have been turning off since it came out. :-) They text area for the location bar is already preselected.
Whatever happened to the 186? Why do you hear of 286, 386, 486, and 586, but never 186?
The 80186 was an 8088/86 hybrid with on-chip peripherals. It was intended for embedded applications. The old unisys ICONs used them.
(that was from memory, but Wikipedia backs me up on this. God I must be old to not only remember this stuff but also the NEC v20 and MOS 65xx histories...
Any word on something like that for Linux fileservers? I am envisioning (as a first pass thought) a cron job with find -ctime that replaced the file with a symlink to the online compressed storage, but you may need some kind of hook into Samba or a lower level hook into the FS itself that grabbed it out of "cold storage" so to speak.