Microsoft Windows's "Network Neighborhood" feature, for example, is simply a way to swap files. Almost every software application that capitalizes on this central functionality is therefore a Kinko's of sorts, and decreeing all search-and-copy software to be illegal is simply too sweeping a move for a court to make.
Now of course, I'm not suggesting that y'all start firing up windows, but I find this point really intriguing - filesharing using the SMB protocol over port 139 a'la redmond. What (c|w)ould the RIAA do about that ?
1) serve up a page with a cookie and a redirect 2) attempt to read cookie when client follows redirect 3) refuse to serve any more pages to client if cookie is present 4) ??????? 5) PROFIT!!!!
ah - I see - compare the ip address on subsequent hits to the ip address of the originating hit.
OK - wouldn't that be a problem where the user is behind *multiple* proxies, so the ip address that the website sees could change from hit to hit ?
(I'm behind such a set of proxies right now..)
We've created a minimal distro based on 7.2, with nothing that's not essential. You can optionally install RH's high availability tool "Pirahna" (snaffled from advanced server), but that's it. No X. Just enough stuff to admin the box. Everything else get's installed from source. The distro is easy to maintain; updates are downloaded by a cron job. Product End-of-life is worrying tho....
stratjakt, don't mind me saying this, but you seem to be pretty authoritative on M$ policy and practice in this area - is there something you're not telling us ?;o)
AFAIK Microsoft can't and doesnt prevent anyone from contributing to open source, but the employee who does better be ready to prove that he didn't contribute any of the companies code, else he'd be fired and probably sued.
they'd be fired, or even worse, assigned to the IIS security team;o) seriously though, I don't think M$ would sue
- they'd have to release the source code in court to prove the case !
I've been told that Microsoft discourages employees from contributing to open-source projects, even in their spare time. But so many of the best hackers work on open-source projects now that the main effect of this policy may be to ensure that they won't be able to hire any first-rate programmers.
but should surely read:
the main effect of this policy may be to ensure that they still won't be able to hire any first-rate programmers.
Microsoft Windows's "Network Neighborhood" feature, for example, is simply a way to swap files. Almost every software application that capitalizes on this central functionality is therefore a Kinko's of sorts, and decreeing all search-and-copy software to be illegal is simply too sweeping a move for a court to make.
Now of course, I'm not suggesting that y'all start firing up windows, but I find this point really intriguing - filesharing using the SMB protocol over port 139 a'la redmond. What (c|w)ould the RIAA do about that ?
1) serve up a page with a cookie and a redirect
2) attempt to read cookie when client follows redirect
3) refuse to serve any more pages to client if cookie is present
4) ???????
5) PROFIT!!!!
ah - I see - compare the ip address on subsequent hits to the ip address of the originating hit.
OK - wouldn't that be a problem where the user is behind *multiple* proxies, so the ip address that the website sees could change from hit to hit ?
(I'm behind such a set of proxies right now..)
Will the choice of the user be remembered using a cookie?
,-}
..only if they chose "ja", otherwise it's illegal
A far better way is to tie the id to a specific ip.
Wouldn't this present a problem where the user is behind a proxy ?
1. start watching live broadcast
2. pause live broadcast
3. resume watching broadcast
4. fast forward to catch up with live
Copyright protection prevents recordings from being copied to the PC...
So are the recordings encrypted on the ext3 filesystem ? I've RTFA(s) - it's not clear from those (pun intended)...
If it teams up with the Rubber Ducks then we could be in trouble ,-}
it's just below the link to "Beaver Mountain"
heh heh heh heh
Stop writing shell scripts and bat files, no matter how simple. Install Python, and write your utilities etc in that.
Lesson one: "I am cool" in python:
while 1:
print 'I am cool'
that said, 3rd party applications like legato networker (backup system) support will dwindle past EOL :o(
We've created a minimal distro based on 7.2, with nothing that's not essential. You can optionally install RH's high availability tool "Pirahna" (snaffled from advanced server), but that's it. No X. Just enough stuff to admin the box. Everything else get's installed from source. The distro is easy to maintain; updates are downloaded by a cron job. Product End-of-life is worrying tho ....
Practical Extraction and Report Language
OR
Pathologically Electic Rubbish Lister
01100110 01110010 01100101 01100101 00100000 01110011 01110000 01100101 01100101 01100011 01101000
free speech
The article talks about IT in terms of HARDWARE - Moore's Law - i.e. the doubling of processor speed every two years.
A neat graph shows the typical lifecycle of any technology from 'irruption' (sic) through to 'maturity', closely followed by the 'next great surge'
LINUX - THE NEXT GREAT SURGE !
stratjakt, don't mind me saying this, but you seem to be pretty authoritative on M$ policy and practice in this area - is there something you're not telling us ? ;o)
AFAIK Microsoft can't and doesnt prevent anyone from contributing to open source, but the employee who does better be ready to prove that he didn't contribute any of the companies code, else he'd be fired and probably sued.
;o) seriously though, I don't think M$ would sue
- they'd have to release the source code in court to prove the case !
they'd be fired, or even worse, assigned to the IIS security team
'nuff said
footnote 2 states:
;o)
I've been told that Microsoft discourages employees from contributing to open-source projects, even in their spare time. But so many of the best hackers work on open-source projects now that the main effect of this policy may be to ensure that they won't be able to hire any first-rate programmers.
but should surely read:
the main effect of this policy may be to ensure that they still won't be able to hire any first-rate programmers.
Thank you for you interest
from http://www.ushomeguard.org/coming-soon.asp
I can see it now
+5: Suspicious
Yeah - let's just hope and GNU and Linux can get their act together sometime soon
</sarcasm>
The error is invalid page fault in shlwapi.dll
..although placing this in the middle of a page doesn't always work:
DLL Name: Shell Light-weight Utility
Library Description: Contains utility functions for handling paths, urls, strings, registry entries and color settings
Interesting that this dll can also 'handle' registry entries....
In fact, the 5 lines of html can be reduced down to one:
<input type>
<html>
<head>
<title>foo</title>
</head>
<body>
<h1>foo</h1>
<input type>
</body>
</html>
type seems to be the only attribute that has the desired effect
Quick, Mobilise ! There's a sled comi *THUD*
In Soviet Russia AMD64 releases RedHat