If an ISP determines that subscriber usage of new service X in particular is changing their oversubscription model such that significant capital expenditure is necessary to maintain an expected quality of service across the board for all users, is it unfair to try to pass those costs off to service X and ultimately the users of X rather than all subscribers across the board?
Another thing is that you really had the sense that you were on the edge of something new back then. These were some of the first computers that were adopted by the public in significant numbers, and if you had one, you were really one of the few early computer owners. If you happened to be a teenager, more exciting and better yet
In those days using a computer was really a choice of love, because it was NOT CONSIDERED COOL. You had to pay some social stigma price to stick it out. We did. The younger folks never really faced it.
Agreed, if you read the reference guide you really had an understanding of the way it worked.
By the time the DOS architecture machines reached the point that a pointer was a pointer was a pointer, I gave up my grip on trying to fully understand the machine from outside to inside to focus on what I could accomplish within the framework of ANSI C. Things feel increasingly squishy each year with layers upon layers. There's too much for me to really grok in the same depth that I used to. The focus shifts to consistent understanding of a number of adjacent domains in an appropriate depth to get work done.
Linus seemed a little less extreme - later in the thread he wrote:
"No, we very much expose/proc/cmdline for a reason. System services are *supposed* to parse it, because it gives a unified way for people to pass in various flags. The kernel doesn't complain about flags it doesn't recognize, exactly because the kernel realizes that "hey, maybe this flag is for something else".
The classic example of this is things like "charset" markers, but also options to modules that modprobe parses etc etc.
And yes, that does include "quiet" and "debug". Parsing them and doing something sane with them is not a bug, it's a feature.
But the problem appears when system services seem to think that they *own* those flags, and nothing else matters, and they don't do something "sane" any more. "
I would seriously think that you could build something user-friendly around rsync - the guts are all about efficient file replication. I use it extensively to sync backups of data on the home network and sync music to a few devices and USB stick. You have to take responsibility for keeping a server up 24/7 or whenever you want to sync data, deal with bandwidth etc, some things that the service provides for you.
Indeed Prigogine had a key early view. I found the notion that systems organize to minimize the rate of entropy production to be fascinating, as well as the result that the fundamental transport equations can be derived from this thermodynamic basis. I had the pleasure of meeting him briefly before his death.
Truth be told, probably 80% of people who purchased PCs for their home since 1995 never really had a need or use for a full-fledged computer, and find it too complex to fully use. They bought a computer because that was the only way to access internet content and eventually participate in the heap of web 2.0 conversation to which people seem drawn. Having these people abandon PCs for simpler devices that "break" less easily, require little maintenance, and are considered disposable/replaceable is a natural evolution of behavior, PCs were overwrought for their needs. It will be interesting to see how much divergence and continuity happens between the arenas. I think Win8 demonstrates that there's not really a one answer suits all approach at this time. There's way too much spread of hardware projecting the O/S.
Ultima IV had a really broad world for the time, and was pretty open ended. You had to proceed through a lot of things before it was even apparent there was an endgame other than self-improvement.
Yeah I use rsync in cygwin to distribute from a Win7 desktop machine to both an external mybook sort of drive and a Linux machine with RAID array. When using the size/time/date matching method to a non-Windows machine it is important to use the --modify-window=1 flag recommended in the man page else the timestamps may fail to match resulting in more data transfer. I run it nightly from a scheduled task but it does not take very long to complete.
If an ISP determines that subscriber usage of new service X in particular is changing their oversubscription model such that significant capital expenditure is necessary to maintain an expected quality of service across the board for all users, is it unfair to try to pass those costs off to service X and ultimately the users of X rather than all subscribers across the board?
Another thing is that you really had the sense that you were on the edge of something new back then. These were some of the first computers that were adopted by the public in significant numbers, and if you had one, you were really one of the few early computer owners. If you happened to be a teenager, more exciting and better yet
In those days using a computer was really a choice of love, because it was NOT CONSIDERED COOL. You had to pay some social stigma price to stick it out. We did. The younger folks never really faced it.
Agreed, if you read the reference guide you really had an understanding of the way it worked.
By the time the DOS architecture machines reached the point that a pointer was a pointer was a pointer, I gave up my grip on trying to fully understand the machine from outside to inside to focus on what I could accomplish within the framework of ANSI C. Things feel increasingly squishy each year with layers upon layers. There's too much for me to really grok in the same depth that I used to. The focus shifts to consistent understanding of a number of adjacent domains in an appropriate depth to get work done.
Just LDA and JSR to $FFD2 :)
Linus seemed a little less extreme - later in the thread he wrote:
"No, we very much expose /proc/cmdline for a reason. System services
are *supposed* to parse it, because it gives a unified way for people
to pass in various flags. The kernel doesn't complain about flags it
doesn't recognize, exactly because the kernel realizes that "hey,
maybe this flag is for something else".
The classic example of this is things like "charset" markers, but also
options to modules that modprobe parses etc etc.
And yes, that does include "quiet" and "debug". Parsing them and doing
something sane with them is not a bug, it's a feature.
But the problem appears when system services seem to think that they
*own* those flags, and nothing else matters, and they don't do
something "sane" any more. "
I would seriously think that you could build something user-friendly around rsync - the guts are all about efficient file replication. I use it extensively to sync backups of data on the home network and sync music to a few devices and USB stick. You have to take responsibility for keeping a server up 24/7 or whenever you want to sync data, deal with bandwidth etc, some things that the service provides for you.
I have used Password Safe, Bruce Schneier's solution for a number of years. (pwsafe.org)
Linux version is in beta with Windows and Android versions available
I suppose it should be a required step in the initial configuration of the router.
It's nice to see somebody answer a question without being a dick :)
How much does using the heat trash your mileage when it's that cold?
Hmm maybe the plug/interface on the cable is failing with size contraction somehow?
Some of his work in the area was published as early as the 1950s IIRC
Indeed Prigogine had a key early view. I found the notion that systems organize to minimize the rate of entropy production to be fascinating, as well as the result that the fundamental transport equations can be derived from this thermodynamic basis. I had the pleasure of meeting him briefly before his death.
Truth be told, probably 80% of people who purchased PCs for their home since 1995 never really had a need or use for a full-fledged computer, and find it too complex to fully use. They bought a computer because that was the only way to access internet content and eventually participate in the heap of web 2.0 conversation to which people seem drawn. Having these people abandon PCs for simpler devices that "break" less easily, require little maintenance, and are considered disposable/replaceable is a natural evolution of behavior, PCs were overwrought for their needs. It will be interesting to see how much divergence and continuity happens between the arenas. I think Win8 demonstrates that there's not really a one answer suits all approach at this time. There's way too much spread of hardware projecting the O/S.
I recently found the schematic for my old Commodore 64 in 1982, made me smile.
I'm OK with anything that stop pretending we aren't broke.
After the first two story telling gave way to greater marketing interests.
I thought it was a NMI
Ultima IV had a really broad world for the time, and was pretty open ended. You had to proceed through a lot of things before it was even apparent there was an endgame other than self-improvement.
Fahrenheit 451 might be too long, but germane.
(Other than the initial run of course)
Yeah I use rsync in cygwin to distribute from a Win7 desktop machine to both an external mybook sort of drive and a Linux machine with RAID array. When using the size/time/date matching method to a non-Windows machine it is important to use the --modify-window=1 flag recommended in the man page else the timestamps may fail to match resulting in more data transfer. I run it nightly from a scheduled task but it does not take very long to complete.
Can we just move them all back to AOL? :)
Ditto for error strings emitted by software.
An amazingly prescient book...