Things have changed for the better for Windows I am quite sure, but back in the days when I was a UNIX sysadmin for a living you needed 10x as many Windows admins as UNIX admins for the same number of machines / user seats, so a simple salary ratio would be misleading!
I've seen at least one attack per minute since I took my ISP on-line on the NSF-managed Internet ~1993 (in those days Chile and.vz were the main source IIRC) whenever I've looked. And I still get upwards of ~10,000 SPAM attempts on my mail accounts per day, at least when I could last be bothered to waste the CPU cycles and Flash write cycles to count them. Attacks across the Net are not new. I was the only UK ISP even attempting to protect my own systems with an firewall (which I wrote and we nominally made available http://www.exnet.com/ExFilter/ though I don't think we sold any) for quite some time...
Never mind the fact that at least some of the participants of either sex many not be being exploited any more than the would if flipping burgers for minimum wage while their PhD is being reviewed.
I just took a huge pay cut last year (and gave the money away instead) to avoid a particularly grating tax change here (UK) that I think is rather dangerous to general child welfare (and the place the money that money went instead should benefit that same child welfare for many years to come). And in effect I'm doing more of the same this year.
And guess what, I found that we're doing perfectly well on the reduced income.
I don't begrudge taxes in general, but this is one that I feel is ill-conceived and will end up hurting the children of those lacking in confidence tackling more bureaucracy, as well as breaking some important principles about separate taxation and tax-payer privacy.
So there you go, I'm one example; I turned income away to protest a socially-damaging tax.
With the exception of one recent and unusual project, I typically print out at most a few sheets of paper per year for work and this has been true for years, with the added bonus of never having to understand how my clients' printers "work".
I'm still working through (ie recycling) a sheaf of old printouts from yesteryear for my small hand-written to-do lists. Even including that I can't imagine that I use even (say) 100 sheets of A4 per year.
Doesn't stop other people printing stuff out and giving it to me unsolicited, eg meeting minutes and agendas, but I push for less of that, and instant recycling afterwards.
Completing one's toilet was originally getting dressed and washed and a toilet (or lavatory) was the place to do that, etc, but then the word got hijacked, in a long and glorious tradition of being unable to call a spade a shovelling device...
Yes, I dislike this usually-literally-incorrect US euphemism.
I have a bath in my bathroom, and I take a dump etc in the WC in the *separate* room next to it. More hygienic for a start.
I can't quite see why the word 'toilet' (although another euphemism I'll grant you) was so offensive that the often-wrong 'bathroom' seemed better. How many public 'bathrooms' in the US sense actually contain a bath?
In general breach of contract by one party DOES free the other party from all its obligations but not rights under that contract under English contract law.
Note:
1) Non-disclosure may have been signed as a separate deed, etc.
Find a tentacle close to you and say that you have to pay rent so sadly you're going to have to sue said tentacle. Take an an onion and maybe a friendly, competent, but not-massively-expensive lawyer.
In the UK, any invoice not paid for 21 days beyond the agreed date renders the non-payer liable to liquidation. Liquidating clients is not great (though you should have acted on your credit control rather sooner) but I once had to threaten a major banking client with it and at the end of a memorable Friday I got my very very overdue money and my client got itself a new head of accounts, and I found that I had a few powerful friends inside the company amongst those pleased with my work for them.
6 months is technically known as "taking the piss".
Stop doing any further work until you get some sort of staged payment started, or start legal action. If you're entitled to the money and you take it slowly and gently and without grandstanding, you may well get it, and may even keep the client.
Start credit control earlier in future: that's your responsibility to limit damage.
Since (full) GPL software imposes conditions on stuff that just *links* to it without modifying it, never mind deriving from GPL-licensed types in (say) an OO language, and that turned out to be so toxic that the LGPL came to be, my point stands that a reasonable default view is that many other forms of usage that don't involve modification may be impacted unless shown otherwise.
Software running on such GPL hardware might be ensnared, and I wouldn't want to be the person dragged into court because I'd misunderstood.
(This is not theoretical: I had to unpick and redo a great deal of someone else's work because they hadn't noticed that one small library was GPL rather than LGPL, probably by accident; leaving it might have exposed trade secrets.)
But I've had some of my code used in places where the user could not have deployed GPL code and where there was a pressing need but not necessarily much money. Those few lines redeployed made the world a slightly better place IMHO.
I *want* corporates to be able to use my code *as well as* for it to be used in FOSS. My agenda is more important than RMS's for my code, sorry.
Anyhow, this disagreement is not a new one, but I'm just pointing out that your horror about GPLed h/w excluding legitimate non-GPL s/w is to me not really distinguishable from GPLed code refusing to co-exist with non-GPLed code in common instances.
Regardless of licensing/philosophy disagreements, it looks like a fantastic project!
Hmm, one problem I have with the full GPL is that it *is* by design rather intent on spreading itself virally and to the exclusion of other legitimate models, and thus a restriction on what software the hardware would be allowed to run would be unfortunately in keeping with the GPL.
I agree that that would be excessive, but then I think that the full GPL is generally excessive.
You may guess that I prefer to license my stuff under BSD licences to allow fully commercial uses. B^>
My DNS is often colocated with my Web sites and other services that it supports: forcing me to separate them would add nothing to end-user security in reaching me, and would likely lower reliability and increase costs.
Specialised and high-volume sites will also want to do things such as geo- and load- sensitive DNS and constraining innovation in that area by constraining DNS providers is unlikely to be helpful for the end user (ie would result in slower and less reliable service).
Entire IP addresses can be blackholed (blocked) if they are misbehaving, and delegation to misbehaving DNS servers can be stopped, though because of cacheing (etc) the latter may be slow to take effect.
Are you saying people like me that have always hosted their own DNS, since the Internet became available to us (~1992 here), should now have to stop doing so?
-x Normally, the time is slewed if the offset is less than the step
threshold, which is 128 ms by default, and stepped if above the
threshold. This option sets the threshold to 600 s...
which would still avoid this problem with an insane upstream, but would allow more leeway for a drifting clock to be brought back into sync, but 600s would take 14 days to slew back, so I'd still manually force it with ntpdate in that case almost certainly, since make and so on would be unhappy for most of that fortnight otherwise.
The last versions of NTP that I contributed to, and paid close attention to when I was providing stratum-1 service, had a flag something like --syncRTC to force the OS to update the underlying battery-backed clock to the 'right' time from its software clock, and thus it would stay close enough during a reboot that (x)ntpd would be happy to pick up again.
My view remains that if a real-time clock is WAY off then it should be manually investigated and manually corrected, eg when I found some remote and local machines at BigMultimationalCo being set to the right local time but completely the wrong timezones, so in reality many many hours out. The fix partly included user education in that case, rather than much technology.
Views differ: I'm sure your systems work fine. I'm just telling you how I have run NTP as a public time source and for hundreds of boxes on clients' networks.
Now that I'm not providing low-stratum time I'm a bit more relaxed about it, but my diversity of input sources seems to have saved me this time (I have 6 upstream sources for my primary NTP server).
Slashdot Mirror
Turns out it's unlucky to be superstitious!
Rgds
Damon
I don't think that "concurrent" means what you think it does.
Rgds
Damon
Nostalgia isn't what it used to be...
Glad that's not just me.
I wish they'd trash all calls for much more of the route; what do you think we'd have to club together for that service?
Rgds
Damon
Things have changed for the better for Windows I am quite sure, but back in the days when I was a UNIX sysadmin for a living you needed 10x as many Windows admins as UNIX admins for the same number of machines / user seats, so a simple salary ratio would be misleading!
Rgds
Damon
I've seen at least one attack per minute since I took my ISP on-line on the NSF-managed Internet ~1993 (in those days Chile and .vz were the main source IIRC) whenever I've looked. And I still get upwards of ~10,000 SPAM attempts on my mail accounts per day, at least when I could last be bothered to waste the CPU cycles and Flash write cycles to count them. Attacks across the Net are not new. I was the only UK ISP even attempting to protect my own systems with an firewall (which I wrote and we nominally made available http://www.exnet.com/ExFilter/ though I don't think we sold any) for quite some time...
Rgds
Damon
No, not "exponentially". A fixed constant factor higher in fact.
Let's not use up the art terms until we mean them. Adding a port-knocking *sequence* before access could get you into exponential territory.
Rgds
Damon
Never mind the fact that at least some of the participants of either sex many not be being exploited any more than the would if flipping burgers for minimum wage while their PhD is being reviewed.
Rgds
Damon
Maybe leave your personal homophobia / projection out of this?
I just took a huge pay cut last year (and gave the money away instead) to avoid a particularly grating tax change here (UK) that I think is rather dangerous to general child welfare (and the place the money that money went instead should benefit that same child welfare for many years to come). And in effect I'm doing more of the same this year.
And guess what, I found that we're doing perfectly well on the reduced income.
I don't begrudge taxes in general, but this is one that I feel is ill-conceived and will end up hurting the children of those lacking in confidence tackling more bureaucracy, as well as breaking some important principles about separate taxation and tax-payer privacy.
So there you go, I'm one example; I turned income away to protest a socially-damaging tax.
Rgds
Damon
With the exception of one recent and unusual project, I typically print out at most a few sheets of paper per year for work and this has been true for years, with the added bonus of never having to understand how my clients' printers "work".
I'm still working through (ie recycling) a sheaf of old printouts from yesteryear for my small hand-written to-do lists. Even including that I can't imagine that I use even (say) 100 sheets of A4 per year.
Doesn't stop other people printing stuff out and giving it to me unsolicited, eg meeting minutes and agendas, but I push for less of that, and instant recycling afterwards.
Rgds
Damon
This is finally the moment for Linux on the ... uh ... UI. We get to officially name the room "/dev/null"?
Rgds
Damon
Completing one's toilet was originally getting dressed and washed and a toilet (or lavatory) was the place to do that, etc, but then the word got hijacked, in a long and glorious tradition of being unable to call a spade a shovelling device...
http://aj.hd.org/TFTC/E.html#euphemisms
Rgds
Damon
Yes, I dislike this usually-literally-incorrect US euphemism.
I have a bath in my bathroom, and I take a dump etc in the WC in the *separate* room next to it. More hygienic for a start.
I can't quite see why the word 'toilet' (although another euphemism I'll grant you) was so offensive that the often-wrong 'bathroom' seemed better. How many public 'bathrooms' in the US sense actually contain a bath?
Rgds
Damon
In general breach of contract by one party DOES free the other party from all its obligations but not rights under that contract under English contract law.
Note:
1) Non-disclosure may have been signed as a separate deed, etc.
2) IANAL
Find a tentacle close to you and say that you have to pay rent so sadly you're going to have to sue said tentacle. Take an an onion and maybe a friendly, competent, but not-massively-expensive lawyer.
In the UK, any invoice not paid for 21 days beyond the agreed date renders the non-payer liable to liquidation. Liquidating clients is not great (though you should have acted on your credit control rather sooner) but I once had to threaten a major banking client with it and at the end of a memorable Friday I got my very very overdue money and my client got itself a new head of accounts, and I found that I had a few powerful friends inside the company amongst those pleased with my work for them.
6 months is technically known as "taking the piss".
Stop doing any further work until you get some sort of staged payment started, or start legal action. If you're entitled to the money and you take it slowly and gently and without grandstanding, you may well get it, and may even keep the client.
Start credit control earlier in future: that's your responsibility to limit damage.
Rgds
Damon
Gee, thanks for your calm consideration.
Since (full) GPL software imposes conditions on stuff that just *links* to it without modifying it, never mind deriving from GPL-licensed types in (say) an OO language, and that turned out to be so toxic that the LGPL came to be, my point stands that a reasonable default view is that many other forms of usage that don't involve modification may be impacted unless shown otherwise.
Software running on such GPL hardware might be ensnared, and I wouldn't want to be the person dragged into court because I'd misunderstood.
(This is not theoretical: I had to unpick and redo a great deal of someone else's work because they hadn't noticed that one small library was GPL rather than LGPL, probably by accident; leaving it might have exposed trade secrets.)
Rgds
Damon
I wish! B^>
Rgds
Damon
But I've had some of my code used in places where the user could not have deployed GPL code and where there was a pressing need but not necessarily much money. Those few lines redeployed made the world a slightly better place IMHO.
I *want* corporates to be able to use my code *as well as* for it to be used in FOSS. My agenda is more important than RMS's for my code, sorry.
Anyhow, this disagreement is not a new one, but I'm just pointing out that your horror about GPLed h/w excluding legitimate non-GPL s/w is to me not really distinguishable from GPLed code refusing to co-exist with non-GPLed code in common instances.
Regardless of licensing/philosophy disagreements, it looks like a fantastic project!
Rgds
Damon
Hmm, one problem I have with the full GPL is that it *is* by design rather intent on spreading itself virally and to the exclusion of other legitimate models, and thus a restriction on what software the hardware would be allowed to run would be unfortunately in keeping with the GPL.
I agree that that would be excessive, but then I think that the full GPL is generally excessive.
You may guess that I prefer to license my stuff under BSD licences to allow fully commercial uses. B^>
Rgds
Damon
My DNS is often colocated with my Web sites and other services that it supports: forcing me to separate them would add nothing to end-user security in reaching me, and would likely lower reliability and increase costs.
Specialised and high-volume sites will also want to do things such as geo- and load- sensitive DNS and constraining innovation in that area by constraining DNS providers is unlikely to be helpful for the end user (ie would result in slower and less reliable service).
Entire IP addresses can be blackholed (blocked) if they are misbehaving, and delegation to misbehaving DNS servers can be stopped, though because of cacheing (etc) the latter may be slow to take effect.
Rgds
Damon
Are you saying people like me that have always hosted their own DNS, since the Internet became available to us (~1992 here), should now have to stop doing so?
Rgds
Damon
And along with all other admin/config that a sysadmin forces on that new machine at that point, forcing the clock to be correct is easy.
Rgds
Damon
I note an option on ntpd on my Ubuntu 9 box:
-x Normally, the time is slewed if the offset is less than the step ...
threshold, which is 128 ms by default, and stepped if above the
threshold. This option sets the threshold to 600 s
which would still avoid this problem with an insane upstream, but would allow more leeway for a drifting clock to be brought back into sync, but 600s would take 14 days to slew back, so I'd still manually force it with ntpdate in that case almost certainly, since make and so on would be unhappy for most of that fortnight otherwise.
Rgds
Damon
Hi,
The last versions of NTP that I contributed to, and paid close attention to when I was providing stratum-1 service, had a flag something like --syncRTC to force the OS to update the underlying battery-backed clock to the 'right' time from its software clock, and thus it would stay close enough during a reboot that (x)ntpd would be happy to pick up again.
My view remains that if a real-time clock is WAY off then it should be manually investigated and manually corrected, eg when I found some remote and local machines at BigMultimationalCo being set to the right local time but completely the wrong timezones, so in reality many many hours out. The fix partly included user education in that case, rather than much technology.
Views differ: I'm sure your systems work fine. I'm just telling you how I have run NTP as a public time source and for hundreds of boxes on clients' networks.
Now that I'm not providing low-stratum time I'm a bit more relaxed about it, but my diversity of input sources seems to have saved me this time (I have 6 upstream sources for my primary NTP server).
Rgds
Damon