If you told me you liked my monitor, and would pay me $10 for it, I would tell you it was worth more than $300.
Does this mean I offered to sell it to you, or just that I was informing you how much I paid to get it onto my desk (including freight etc)?
In all likelihood, I wouldn't want to sell my monitor - it works perfectly well, and I have gone to the trouble of installing it. I might be thinking of getting a new monitor - but unless you offered me a silly price for the one I have, I wouldn't see the point.
The one sticky point might be that he used "soft" - unless he goes by something like "Mike Rowe Software" somewhere else.
hmm, maybe I'll try registering "mikesoft.com" - my name _is_ Mike, and I write software (among other things)..... If I were to register a business name first (though Australian business name registrations are quite picky on trademarks) M$ would have no argument.
entire world (except US) forced to stop using windows because microsoft is a US company (argue out of that one Bill - we all know where it was written) I think SCO will have to fight damn hard to win that ruling.
Maybe the best thing OSS can do is let SCO lock M$ (and SCO) out of world markets, leaving only one alternative - anything written out side the US:-) That doesn't stop OSS being developed in the US - you you did say SELL... nothing about GIVING AWAY...
They could of course decide you can't give away software - but isn't that stopping you from donating to/volunteering for such things - but if you can't give away your productivity, you can't give to charity - and you can't help out those poor little countries that want to blow each other to bits (sorry, no more foreign aid - sure, we'll all stop helping Iraq won't we George?)
Basically you can't stop a group of people who want to get together and give things away to anyone who wants them, unless you can prove they don't own what they're giving away, or those things are desiged to cause direct damage to others (yea, you can't go handing out explosives to everyone - that's kinda acceptable - not that it stops government)
Of course you can show that ANY item can be used to cause damage - but just because I can use petrol to fire up my favourite politician, they aren't going to stop people selling it:-)
you could start with routing table lookups on the local host etc to check out any directly connected LANS. People would tend to use particular sub-sets of allocated space (for example 192.168.0.1 is always a good bet in a LAN, even though there are over 65000 ips to choose from). Similar things apply to 10.0.0.1. On the internet, scanning *.*.*.1, *.*.*.5 and *.*.*.10 would yield well. You can of course rule out pre-allocated space like 192.168.* and 10.* Once you have a hit on one of those addresses you can start looking deeper.
Extending these principals to IP6 would give a similar drop in target addresses - and once you have taken over one host on a network, you can get it to scan that range, rather than doing it from afar. IP6 will of course advertise other boxes on the LAN saving you a lot of trouble here.
You can narrow it down even further if you ask an appropriate whois server if a range is allocated.
Just like cracking encryption - all it takes is time, enough computing power, and a little planning. Software always has time, someone is bound to plan it, and as many winblows viruses have shown - you can always steal enough computing power!
Who said the drug dealer has to know... if they don't know what it is, they probably aren't using it - so they don't care if the feds are listening to it... and if they do know what it is, they can soon find themselves a geek - and how long will it be before they can just download some handy software that does it all for em anyway?
ok, hands up anyone who thinks anyone trying to actually have a private conversation is NOT going to encrypt it? but then what if they decided to just hold onto you without chpressign charges for a few years until they managed to decrypt enough conversation to find you guilty..... oh wait.... they do that already...
shame if you just wanted to discuss your business plans in private though....
forgot about that one - but it does require you to have root privs - limiting it to a single-user, definitly can't use in distribution solution. Although you can probably use an suid program, it's extra messy, not a good idea, and more hassle than win98
If it is in any way self-navigating, B&W = less data to process = less CPU power = less power/battery or more CPU to run other gadgets.
The points on bandwith for images to human CPUs also apply... as well as B&W cameras requiring less power.
The other point is the more time the nav cameras are available, the more time it can spend moving - so why not use a couple of cheap nav cameras, and keep the good stuff separate for the real pics?
Firstly, what's to stop them keeping a 98 box around to develop the quick and dirty version? If it's not online, who cares if it's virus proof?
Secondly, direct access to resources in a multi-user/multi-tasking system is probably asking for trouble - so you would want to develop the final driver on a better model anyway.
Thirdly, you take some sample code, and modify it - giving you a jump start on all the junk you have to go through to get access to the hardware.
Now that I sound like a windows zealot...
Linux is my platform of choice - I have run it as a small ISP, and these days as a small business/home network gateway, and more recently as my desktop (now that I use crossover office to run quickbooks for my accountant, I don't even use winblows)
The above strategies are just as valid for Linux as windows. (linux definitly requires you to write a driver to get direct hardware access).
As for someone's comment on RedHat's support for old releases - if I had to pay as much for RedHat as I do for Windows, I think they'd be employing people to support me a little longer, don't you? (I run Slackware, so I'm not pro-RedHat either)
Someone mentioned linux running on 8086's and 286's - WRONG - Linux was written at the time of the 386 _for_ the 386. It did not run on anything less untill it was ported to some strange architectures - One of the projects was to back-port/down-port it to processors with no memory management such as cisco routers, wireless lan access points and the like. Apparently there is an 8086 port for embedded systems, but I haven't seen anything specifically for the 286.
Slashdot Mirror
well what do ya know - I can't register mikesoft.com
It belongs to Mikesoft Computers - better watch out - it starts in M and ands in T - could confuse the customers!
If you told me you liked my monitor, and would pay me $10 for it, I would tell you it was worth more than $300.
Does this mean I offered to sell it to you, or just that I was informing you how much I paid to get it onto my desk (including freight etc)?
In all likelihood, I wouldn't want to sell my monitor - it works perfectly well, and I have gone to the trouble of installing it. I might be thinking of getting a new monitor - but unless you offered me a silly price for the one I have, I wouldn't see the point.
The one sticky point might be that he used "soft" - unless he goes by something like "Mike Rowe Software" somewhere else.
hmm, maybe I'll try registering "mikesoft.com" - my name _is_ Mike, and I write software (among other things)..... If I were to register a business name first (though Australian business name registrations are quite picky on trademarks) M$ would have no argument.
That could be interesting....
:-)
:-)
entire world (except US) forced to stop using windows because microsoft is a US company (argue out of that one Bill - we all know where it was written)
I think SCO will have to fight damn hard to win that ruling.
Maybe the best thing OSS can do is let SCO lock M$ (and SCO) out of world markets, leaving only one alternative - anything written out side the US
That doesn't stop OSS being developed in the US - you you did say SELL... nothing about GIVING AWAY...
They could of course decide you can't give away software - but isn't that stopping you from donating to/volunteering for such things - but if you can't give away your productivity, you can't give to charity - and you can't help out those poor little countries that want to blow each other to bits (sorry, no more foreign aid - sure, we'll all stop helping Iraq won't we George?)
Basically you can't stop a group of people who want to get together and give things away to anyone who wants them, unless you can prove they don't own what they're giving away, or those things are desiged to cause direct damage to others (yea, you can't go handing out explosives to everyone - that's kinda acceptable - not that it stops government)
Of course you can show that ANY item can be used to cause damage - but just because I can use petrol to fire up my favourite politician, they aren't going to stop people selling it
you could start with routing table lookups on the local host etc to check out any directly connected LANS.
People would tend to use particular sub-sets of allocated space (for example 192.168.0.1 is always a good bet in a LAN, even though there are over 65000 ips to choose from). Similar things apply to 10.0.0.1.
On the internet, scanning *.*.*.1, *.*.*.5 and *.*.*.10 would yield well. You can of course rule out pre-allocated space like 192.168.* and 10.*
Once you have a hit on one of those addresses you can start looking deeper.
Extending these principals to IP6 would give a similar drop in target addresses - and once you have taken over one host on a network, you can get it to scan that range, rather than doing it from afar. IP6 will of course advertise other boxes on the LAN saving you a lot of trouble here.
You can narrow it down even further if you ask an appropriate whois server if a range is allocated.
Just like cracking encryption - all it takes is time, enough computing power, and a little planning. Software always has time, someone is bound to plan it, and as many winblows viruses have shown - you can always steal enough computing power!
Code Red II - Toaster Edition.
Roams the IPv6 space outputting advertising on your breakfast.
Who said the drug dealer has to know... if they don't know what it is, they probably aren't using it - so they don't care if the feds are listening to it... and if they do know what it is, they can soon find themselves a geek - and how long will it be before they can just download some handy software that does it all for em anyway?
going round and round in smaller and smaller circles till you dissapear up your own butt could be here at last!
But seriously, it's one of those things that somebody is bound to do because it can be done, and who knows what we'll learn from it.
We didn't HAVE to have linux, but look were one man's experiment has taken us.
ok, hands up anyone who thinks anyone trying to actually have a private conversation is NOT going to encrypt it? but then what if they decided to just hold onto you without chpressign charges for a few years until they managed to decrypt enough conversation to find you guilty..... oh wait.... they do that already...
shame if you just wanted to discuss your business plans in private though....
forgot about that one - but it does require you to have root privs - limiting it to a single-user, definitly can't use in distribution solution.
Although you can probably use an suid program, it's extra messy, not a good idea, and more hassle than win98
If it is in any way self-navigating, B&W = less data to process = less CPU power = less power/battery or more CPU to run other gadgets.
The points on bandwith for images to human CPUs also apply... as well as B&W cameras requiring less power.
The other point is the more time the nav cameras are available, the more time it can spend moving - so why not use a couple of cheap nav cameras, and keep the good stuff separate for the real pics?
Firstly, what's to stop them keeping a 98 box around to develop the quick and dirty version? If it's not online, who cares if it's virus proof?
Secondly, direct access to resources in a multi-user/multi-tasking system is probably asking for trouble - so you would want to develop the final driver on a better model anyway.
Thirdly, you take some sample code, and modify it - giving you a jump start on all the junk you have to go through to get access to the hardware.
Now that I sound like a windows zealot...
Linux is my platform of choice - I have run it as a small ISP, and these days as a small business/home network gateway, and more recently as my desktop (now that I use crossover office to run quickbooks for my accountant, I don't even use winblows)
The above strategies are just as valid for Linux as windows. (linux definitly requires you to write a driver to get direct hardware access).
As for someone's comment on RedHat's support for old releases - if I had to pay as much for RedHat as I do for Windows, I think they'd be employing people to support me a little longer, don't you? (I run Slackware, so I'm not pro-RedHat either)
Someone mentioned linux running on 8086's and 286's - WRONG - Linux was written at the time of the 386 _for_ the 386. It did not run on anything less untill it was ported to some strange architectures - One of the projects was to back-port/down-port it to processors with no memory management such as cisco routers, wireless lan access points and the like. Apparently there is an 8086 port for embedded systems, but I haven't seen anything specifically for the 286.
just exercising my FUD-Zapper.....