My android friends don't believe that a smartphone can go longer than 2 days so I send them screenshots.
My Samsung Galaxy Nexus will go for 3 days with some wifi tethering and other non-intensive data use, in addition to making calls. And if I need to, I can always swap out the battery for a fresh one if I am away from a power point for longer, which you cannot do with an iPhone.
In other words, turn it into a dumbphone. A cheapie $25 Nokia candy-bar will fit that purpose, and probably give you better battery life while taking up less room in your pocket.
I have to do this with Telstra about once a week. The issue is more common now that I live in a rural area of Tasmania (in Perth WA the problem was quite rare), so I believe the problem is with the carrier rather than the hardware.
Guess that's one reason they all left Android.... Something about their phone being completely out of date and unsupported 3-6 months into a 24 month contract.
I made that mistake with my last phone (a Sony/Ericsson Xperia X10 Mini Pro), which I quite liked initially, but was abandoned by both the manufacturer and my telco. So I'm never buying a pone from them again. But I'm still happy with my Samsung Galaxy Nexus, which although apparently abandoned (already and again) by my telco (I'm looking at you, Telstra, you total cunts), is easily flashed with an up-to-date version of the OS.
What carrier are you using? I have noticed that some are vastly better than others.
Since I'm now living in (very) rural Tasmania, I'm using Telstra. Not because it's good, but because it's the best of a bad lot. I sometimes think it's like living in the third world here, except that in the third world you probably get better service.
Never assume malicious intent when incompetence is just as easily an alternative.
Since this seems to be a recurring pattern with the Chinese, it seems to me an instructive way of dealing with the problem might be to "reverse" the Great Firewall so no-one in China can make a connection to the outside world at all. And maybe consider letting them back in when they learn to behave.
Not sure who is more stupid. Your wife for clicking a dialog box telling Time Machine to nuke the drive without reading or you for defending her. The willful ignorance of Americans at work... Readin' and personal responsibility are for suckers!
1. Neither my wife nor I are American.
2. I mentioned in my post that I had warned my wife about possible caveats with Time Machine.
Unfortunately, it seems she listened to her academic peers (she has a PhD in history) extolling the virtues of Time Machine before listening to me. You will note that I mentioned that I did not tell her "I told you so". Nevertheless, I had told her so.;)
Fortunately, she didn't lose too much stuff of any importance, since I had taken a belt-and-braces backup of her entire machine a month earlier...
While I acknowledge that Gentoo has its uses, my own experience of rolling my own (LFS) turned out to be a quicker and less painful process.
That said, whenever I want to set up any kind of a server system quickly, my first and quickest choice is always Slackware. In fact, that was my only choice for my desktop machines for many years (a position currently held by Arch Linux, though I am presently reconsidering that).
The great thing about Slackware is that the zero dependency checking of the package system makes admin so simple. You just have a world to stand on while you ./configure -prefix=/usr/local && make && make install
which is all you really need to install the majority of programs,
It is safe by default and will not wipe out your data.
I wouldn't count on that. My wife, who has been using Macs for the last 10 years (having discovered that her only killer app, EndNote couldn't be supported on the Slackware boxes I set up for her) backed up quite a lot of data on her external hard drive that was later cheerfully erased by Apple's so-called Time Machine. I had mentioned some of the destructive uses of rsync, but I was obviously howling into the wind. Saying "I told you so" is not a way to promote domestic harmony.
I spent hours trying to get the thing to install, and hours more after people urged me to try a different distro. All in all I think I spent a complete workday just installing with zero result.
As a matter of interest, and bearing in mind that you're posting as AC, what issues did you encounter, and with which distro?
Even back in the '90s when many of us had to struggle with unsupported hardware, we could usually get some sort of usable Linux box up and running. Nowadays, I tend to find that pretty much everything "just works" with kernels supplied out of the box.
I consider that to be a good contribution to the community and on projects I've managed in the past I really appreciated users who gave good bug reports.
I'll second that. A well-considered bug report is often a lot more valuable than any kind of whine, since it will often lead the dev to the exact point where the problem lies, while for another programmer (without the benefit of familiarity) might take some time to find and fix the issue.
Well, for those of us who don't like the way distros are going these days, there's always Slackware. Apart from the installation media, the installer process hasn't changed much in 20 years. It's fast, simple and easy. Sure it's text-only, but since the whole process is so quick, who cares?
It's one that works, and is another part of the scientific method, albeit a step along from establishing reproducibility of an experiment. If prior research appears to set a hypothesis, then that should be tested - i.e. someone should make an attempt to knock it down by whatever means are available. You never really "prove" something to be the case, but if nothing can be done to disprove it, that's pretty nearly as good.
If no one ever noticed or cared that their cookies were getting lost on a kde restart then how can you expect it to get fixed?
Since I don't use konq, I never noticed this bug, but in any case I would call this a feature, since I actually use a script to routinely delete any cookies files. While I realise cookies might be delicious, I don't care to be tracked by friends of acquaintances, so (as far as is conveniently possible) I don't choose to let them.
Does anyone actually use konqueror? I can't imagine why, it's horrible. That said, I have no beef about the rest of KDE, though I really did hate it for many years when it was kluttered and kfucking kfugly, but now it is as elegant, feature-rich and usable as I could wish for...
...Unlike Gnome, of which I really was a big supporter since ~1997 but which since version 3.0 is (for good reason) about as popular as a dose of the clap.
I hope you are young enough to watch our country turn into a modern and civilized society.
Sir, I would like some of what you are smoking.
I am now over 50, and the primary reason why my wife and I have never had kids is because there is little to no hope of there ever being a sound world into which to bring them.
The submission didn't actually specify backups, but in this case I would agree. From my point of view, if you want something done properly, you should be prepared to do it yourself. You can never get a 100% guarantee that your data is safe and secure, but you can get close by taking the process into your own hands.
So-called "cloud" services, while convenient and trendy, are subject to too many conditions that are entirely out of your control (even if you run those services yourself), so in my paranoid opinion they are nearly worthless as a real backup. But bear in mind that I am an ancient programmer and sysadmin, and I have been accustomed over my 35+ years in the industry to offline storage of media in fireproof safes in off-site locations. Sure it costs money, but loss of data could cost the existence of the business.
Well, no reason why it should. Just about anyone should be able to write some form of pseudocode, however incomplete, for whatever task they want to accomplish with or without the assistance of a computer.
That said, when I first started working with computers back in the '70s, programmers mostly didn't have access to the actual computer hardware, so if the chunk of code was large, we simply wrote out our FORTRAN, Assembly or COBOL programs on a cellulose-fibre "paper" substance called a Coding Sheet with a graphite-filled wooden stick known as a pencil. These were then transcribed on to mag tape by a platoon of very pretty but otherwise non-human keypunch ops who were universally capable of typing at a rate of 6.02 x 10^23 words per minute. (If the program or patch happened to be small or trivial, we used one of those metal card-punch contraptions with an 029 keypad, thus allowing the office door to slam with nothing to restrain it.)
This leisurely approach led to a very different and IMHO more creative attitude to coding, and it was probably no coincidence that many programmers back then were pipe-smokers.
In my first programming job, several of my more thankless tasks were fixing up code where the source had been (for one reason or another) lost. Back in the 1970s, this was not uncommon. The upside of this was that patching binaries directly was (and, of course still is) a challenge, and a nice change from the tedium of COBOL.
Of course, in those days patches were usually submitted via cards punched on 029 door-stops, and version control was handled with a device generally known as a pencil. This lead to an approach where the fastest means to obtain a usable code was the best, and documentation didn't really come into it unless the programmer was not up to scratch.
Slashdot Mirror
My android friends don't believe that a smartphone can go longer than 2 days so I send them screenshots.
My Samsung Galaxy Nexus will go for 3 days with some wifi tethering and other non-intensive data use, in addition to making calls. And if I need to, I can always swap out the battery for a fresh one if I am away from a power point for longer, which you cannot do with an iPhone.
In other words, turn it into a dumbphone. A cheapie $25 Nokia candy-bar will fit that purpose, and probably give you better battery life while taking up less room in your pocket.
I have to do this with Telstra about once a week. The issue is more common now that I live in a rural area of Tasmania (in Perth WA the problem was quite rare), so I believe the problem is with the carrier rather than the hardware.
Guess that's one reason they all left Android.... Something about their phone being completely out of date and unsupported 3-6 months into a 24 month contract.
I made that mistake with my last phone (a Sony/Ericsson Xperia X10 Mini Pro), which I quite liked initially, but was abandoned by both the manufacturer and my telco. So I'm never buying a pone from them again. But I'm still happy with my Samsung Galaxy Nexus, which although apparently abandoned (already and again) by my telco (I'm looking at you, Telstra, you total cunts), is easily flashed with an up-to-date version of the OS.
What carrier are you using? I have noticed that some are vastly better than others.
Since I'm now living in (very) rural Tasmania, I'm using Telstra. Not because it's good, but because it's the best of a bad lot. I sometimes think it's like living in the third world here, except that in the third world you probably get better service.
Found overage wherever I want to go(...) We seem to do OK.
You don't get out much, do you? Unless you really *do* mean you're overage.
Never assume malicious intent when incompetence is just as easily an alternative.
Since this seems to be a recurring pattern with the Chinese, it seems to me an instructive way of dealing with the problem might be to "reverse" the Great Firewall so no-one in China can make a connection to the outside world at all. And maybe consider letting them back in when they learn to behave.
Exactly. I've got one for sale now - no need to bother with a Beta. :)
Not sure who is more stupid. Your wife for clicking a dialog box telling Time Machine to nuke the drive without reading or you for defending her. The willful ignorance of Americans at work... Readin' and personal responsibility are for suckers!
1. Neither my wife nor I are American.
;)
2. I mentioned in my post that I had warned my wife about possible caveats with Time Machine.
Unfortunately, it seems she listened to her academic peers (she has a PhD in history) extolling the virtues of Time Machine before listening to me. You will note that I mentioned that I did not tell her "I told you so". Nevertheless, I had told her so.
Fortunately, she didn't lose too much stuff of any importance, since I had taken a belt-and-braces backup of her entire machine a month earlier...
While I acknowledge that Gentoo has its uses, my own experience of rolling my own (LFS) turned out to be a quicker and less painful process.
./configure -prefix=/usr/local && make && make install
That said, whenever I want to set up any kind of a server system quickly, my first and quickest choice is always Slackware. In fact, that was my only choice for my desktop machines for many years (a position currently held by Arch Linux, though I am presently reconsidering that).
The great thing about Slackware is that the zero dependency checking of the package system makes admin so simple. You just have a world to stand on while you
which is all you really need to install the majority of programs,
It is safe by default and will not wipe out your data.
I wouldn't count on that. My wife, who has been using Macs for the last 10 years (having discovered that her only killer app, EndNote couldn't be supported on the Slackware boxes I set up for her) backed up quite a lot of data on her external hard drive that was later cheerfully erased by Apple's so-called Time Machine. I had mentioned some of the destructive uses of rsync, but I was obviously howling into the wind. Saying "I told you so" is not a way to promote domestic harmony.
Sorry, but I think you should consider washing your keyboard with carbolic soap. Windows is not a viable alternative. :D
I spent hours trying to get the thing to install, and hours more after people urged me to try a different distro. All in all I think I spent a complete workday just installing with zero result.
As a matter of interest, and bearing in mind that you're posting as AC, what issues did you encounter, and with which distro?
Even back in the '90s when many of us had to struggle with unsupported hardware, we could usually get some sort of usable Linux box up and running. Nowadays, I tend to find that pretty much everything "just works" with kernels supplied out of the box.
I consider that to be a good contribution to the community and on projects I've managed in the past I really appreciated users who gave good bug reports.
I'll second that. A well-considered bug report is often a lot more valuable than any kind of whine, since it will often lead the dev to the exact point where the problem lies, while for another programmer (without the benefit of familiarity) might take some time to find and fix the issue.
Well, for those of us who don't like the way distros are going these days, there's always Slackware. Apart from the installation media, the installer process hasn't changed much in 20 years. It's fast, simple and easy. Sure it's text-only, but since the whole process is so quick, who cares?
That doesn't sound like a very good system.
It's one that works, and is another part of the scientific method, albeit a step along from establishing reproducibility of an experiment. If prior research appears to set a hypothesis, then that should be tested - i.e. someone should make an attempt to knock it down by whatever means are available. You never really "prove" something to be the case, but if nothing can be done to disprove it, that's pretty nearly as good.
If no one ever noticed or cared that their cookies were getting lost on a kde restart then how can you expect it to get fixed?
Since I don't use konq, I never noticed this bug, but in any case I would call this a feature, since I actually use a script to routinely delete any cookies files. While I realise cookies might be delicious, I don't care to be tracked by friends of acquaintances, so (as far as is conveniently possible) I don't choose to let them.
Does anyone actually use konqueror? I can't imagine why, it's horrible. That said, I have no beef about the rest of KDE, though I really did hate it for many years when it was kluttered and kfucking kfugly, but now it is as elegant, feature-rich and usable as I could wish for...
...Unlike Gnome, of which I really was a big supporter since ~1997 but which since version 3.0 is (for good reason) about as popular as a dose of the clap.
I hope you are young enough to watch our country turn into a modern and civilized society.
Sir, I would like some of what you are smoking.
I am now over 50, and the primary reason why my wife and I have never had kids is because there is little to no hope of there ever being a sound world into which to bring them.
The submission didn't actually specify backups, but in this case I would agree. From my point of view, if you want something done properly, you should be prepared to do it yourself. You can never get a 100% guarantee that your data is safe and secure, but you can get close by taking the process into your own hands.
So-called "cloud" services, while convenient and trendy, are subject to too many conditions that are entirely out of your control (even if you run those services yourself), so in my paranoid opinion they are nearly worthless as a real backup. But bear in mind that I am an ancient programmer and sysadmin, and I have been accustomed over my 35+ years in the industry to offline storage of media in fireproof safes in off-site locations. Sure it costs money, but loss of data could cost the existence of the business.
Well, no reason why it should. Just about anyone should be able to write some form of pseudocode, however incomplete, for whatever task they want to accomplish with or without the assistance of a computer.
That said, when I first started working with computers back in the '70s, programmers mostly didn't have access to the actual computer hardware, so if the chunk of code was large, we simply wrote out our FORTRAN, Assembly or COBOL programs on a cellulose-fibre "paper" substance called a Coding Sheet with a graphite-filled wooden stick known as a pencil. These were then transcribed on to mag tape by a platoon of very pretty but otherwise non-human keypunch ops who were universally capable of typing at a rate of 6.02 x 10^23 words per minute. (If the program or patch happened to be small or trivial, we used one of those metal card-punch contraptions with an 029 keypad, thus allowing the office door to slam with nothing to restrain it.)
This leisurely approach led to a very different and IMHO more creative attitude to coding, and it was probably no coincidence that many programmers back then were pipe-smokers.
And how would Mick Jagger know, without growing up?
I now Master Yoda get to my identity mask.
In my first programming job, several of my more thankless tasks were fixing up code where the source had been (for one reason or another) lost. Back in the 1970s, this was not uncommon. The upside of this was that patching binaries directly was (and, of course still is) a challenge, and a nice change from the tedium of COBOL.
Of course, in those days patches were usually submitted via cards punched on 029 door-stops, and version control was handled with a device generally known as a pencil. This lead to an approach where the fastest means to obtain a usable code was the best, and documentation didn't really come into it unless the programmer was not up to scratch.
You need tools for the job.
Trouble is, we have too many "tools" doing the job.