I already have those... Do I still have to pay Micros~1 some
sort of royalty? It seems that these are brand new innovations
by Microsoft and probably soon be patented.
by the way... I've bought various MS-DOS versions, Windows 3.1, 3.11 etc. etc. Finally I decided to stop buying/using Windows series products simply because of mathematical induction.
If this law comes into effect, in about 10 years US companies will start chasing export licences from European countries. I cannot believe how Americans (probably only the gov officials) are so keen to isolate the the country from the rest of the world.
I posted the following questions to SCO before buying a license. My credit card is ready. Will promptly rush and get my license once they answer me.
I intended to buy a license to protect me against any future legal problems but couldn't decide which license I should buy.
I have a few questions:
My operating system (I won't quote its name here now, because I don't have the license yet) reports two CPU's. I've got one of those hyper-threading CPU's. Should I buy two licenses? Do you carry fractional licenses?
I am a typical desktop user but I run proptfd, samba and postfix. Now, does this qualify my machine as a server?
What do you mean by the "name of the server"? Names can change as you very well know, for instance www.sco.com can grow to become www.thescogroup.com.
Do you also own proftpd, apache, samba, postfix? How will I know that you will not start asking for more money to cover licenses of programming in C, breathing etc.
By the way; do you also own stdio.h? Should I revise my old programs to get rid of them? On second thought, you might send me the list of IPs that you do not own. This might make life easier for both parties.
These are crooked figures. Don't take them seriously! The real marketshare of IIS is above 80 percent. The catch is, IIS boxes are declaring themselves as Apache servers to avoid attacks.
Note: This not an MS sponsored report (yet). Hopefully they will contact me and it will become one.:)
The report implies that 67 percent of servers are LINUX boxes, and 23 percent are win boxes. What about Solaris, AIX, HP-UX boxes? Either they are not attacked at all or they don't exist.
Just another laughable petty report (probably) financed my micros~1.
we maintain a database where we keep MAC addresses vs IP addresses and student IDs. The users get their IP addresses by signing in an automated service using their student account/passwd (so that we know who they really are) and declaring their MAC addresses to this automated service while they signup with the resnet.
An automated task grabs the ARP tables frequently (every 5 minutes) and reports any IP-MAC pairs that we do not have in our database to another program which in turn blocks the IP's Internet access. Since Internet access is the most valuable asset in a dorm room, the user immediately calls the support center to place a complaint or ask whats wrong. and you have a chance to talk directly to the owner of the computer causing the problem.
This technique lets us to be sure about who is using which IP address and this info is useful not only in reaching the owner of an infected machine but also in reaching massive p2p trafficers which is another BIG headache in residential networks.
This worked fine UNTIL "dear" micros~1 added a completely useless and potentially dangerous feature of altering the MAC address of a PC. Now some students sniff their LAN, find valid IP-MAC pairs and monitor the net and when a valid pair shuts down, they change their computer's seetings to these values and so on. The resnet users are warned that if a fraud is detected, the student will loose the resnet connection forever.
The scheme works at least for most of the students who wouldn't or couldn't sniff their LAN.
we maintain a database where we keep MAC addresses vs IP addresses and student IDs. The users get their IP addresses by signing in an automated service using their student account/passwd (so that we know who they really are) and declaring their MAC addresses to this automated service while they signup with the resnet.
An automated task grabs the ARP tables frequently and reports any IP-MAC pairs that we do not have in our database to another program which in turn blocks the IP's Internet access. Since Internet access is the most valuable asset in a dorm room, the user immediately calls the support center to place a complaint or ask whats wrong. and you have a chance to talk directly to the owner of the computer causing the problem.
This technyque lets us to be sure about who is using which IP address and this info is useful not only in reaching the owner of an infected machine but also in reaching massive p2p trafficers which is another BIG headache in residential networks.
This worked fine UNTIL dear micros~1 added a completely useless and potentially dangerous feature of altering the MAC address of a PC. Now some students sniff their LAN, find valid IP-MAC pairs and monitor the net and when a valid pair shuts down, they change their computer's seetings to these values and so on. The resnet users are warned that if a fraud is detected, the student will loose the resnet connection forever.
The scheme works at least for most of the students who wouldn't or couldn't sniff their LAN.
it is not only sco.com and caldera.com. sco.de and sco.it dont respond either. the urls resolve though... it seems that they're dropping incoming http requests
I am sure that someone has asked the same question when Mr. Bool first established the Boolean Arithmetic looong time ago. It is certain that your kids or grandkids will benefit from this. Just be patient...
Win4Lin is a beauty... BUT, it is quite slow on moderate machines and some win application (rare, but there are some) simply wont work!
and you're right about stability... the windows running under win4lin is more atable than a standalone win9x.
We are running about 500 PCs in labs, most of which are equipped with Windows application s/w.
The main problem being students messing up with the windows configurations and storing personal files created by the users, we came along with the following solution:
Keep user homes on powerful UNIX servers.
Install one Linux server in each lab hall (approx one Linux server for each 40-50 PC; a 300 MHz oldish PC with 64 M RAM and a few GB HDD perfectly does the job.
NFS Mount various home trees on the main server(s) to these lab servers.
Setup Lab servers to provide print spooling and print quota checks
Setup lab servers with Samba server; make them domain controllers
setup lab PCs to authenticate from lab servers. This is the worst part. NT, XP wont do this. Believe it or not, we have the best solution with Win95. Win98 also works, but any win beyond that simply doesnt work.
Configure lab PCs to have access only to printer(s) in the same lab
Use some incremental disk restoration program (PC-Rdist is a good one) so that when a student logs out, the Windows settings and any deleted files are restores; any new files added by teh user are cleaned up (except the home directories of course).
Keep a Windows system disk image on each lab server so in case a machine fails beyond the repair capability of incremental restorer, you can restore a full image over the LAN.
Everybody is happy with the above configuration.
The average up-time for PCs have increased to 98%. Access is limited to only students and staff (since a domain logon is enforced). Printer and disk quotas a re under control since these services are in fact provided by UNIX machines. Cookies and other personal information are removed from the pcs when somebody logs out.
As far as general security audits are concerned, the net admin will have a log of who used which pc, when and for how long.
The cost is just the cost of an extra PC to be configured as lab server and since you dont need a hell of a peformance on these, any old PC can be used.
Using thin clients in Win env is a dream. The only solution in the markets seems to be Citrix but is certainly is NOT designed for lab environments. They expect users to load one or two applications into the RAM in the morning and use only them till they leave their offices.
Slashdot Mirror
I already have those... Do I still have to pay Micros~1 some sort of royalty? It seems that these are brand new innovations by Microsoft and probably soon be patented. by the way... I've bought various MS-DOS versions, Windows 3.1, 3.11 etc. etc. Finally I decided to stop buying/using Windows series products simply because of mathematical induction.
If this law comes into effect, in about 10 years US companies will start chasing export licences from European countries. I cannot believe how Americans (probably only the gov officials) are so keen to isolate the the country from the rest of the world.
you mean "inventing from them"?
10**100 is a "googol", nor "google"
I intended to buy a license to protect me against any future legal problems but couldn't decide which license I should buy.
I have a few questions:
My operating system (I won't quote its name here now, because I don't have the license yet) reports two CPU's. I've got one of those hyper-threading CPU's. Should I buy two licenses? Do you carry fractional licenses?
I am a typical desktop user but I run proptfd, samba and postfix. Now, does this qualify my machine as a server?
What do you mean by the "name of the server"? Names can change as you very well know, for instance www.sco.com can grow to become www.thescogroup.com.
Do you also own proftpd, apache, samba, postfix? How will I know that you will not start asking for more money to cover licenses of programming in C, breathing etc.
By the way; do you also own stdio.h? Should I revise my old programs to get rid of them? On second thought, you might send me the list of IPs that you do not own. This might make life easier for both parties.
I shall appreciate a prompt answer.
both...
These are crooked figures. Don't take them seriously! The real marketshare of IIS is above 80 percent. The catch is, IIS boxes are declaring themselves as Apache servers to avoid attacks. Note: This not an MS sponsored report (yet). Hopefully they will contact me and it will become one. :)
The report implies that 67 percent of servers are LINUX boxes, and 23 percent are win boxes. What about Solaris, AIX, HP-UX boxes? Either they are not attacked at all or they don't exist. Just another laughable petty report (probably) financed my micros~1.
we maintain a database where we keep MAC addresses vs IP addresses and student IDs. The users get their IP addresses by signing in an automated service using their student account/passwd (so that we know who they really are) and declaring their MAC addresses to this automated service while they signup with the resnet.
An automated task grabs the ARP tables frequently (every 5 minutes) and reports any IP-MAC pairs that we do not have in our database to another program which in turn blocks the IP's Internet access. Since Internet access is the most valuable asset in a dorm room, the user immediately calls the support center to place a complaint or ask whats wrong. and you have a chance to talk directly to the owner of the computer causing the problem.
This technique lets us to be sure about who is using which IP address and this info is useful not only in reaching the owner of an infected machine but also in reaching massive p2p trafficers which is another BIG headache in residential networks.
This worked fine UNTIL "dear" micros~1 added a completely useless and potentially dangerous feature of altering the MAC address of a PC. Now some students sniff their LAN, find valid IP-MAC pairs and monitor the net and when a valid pair shuts down, they change their computer's seetings to these values and so on. The resnet users are warned that if a fraud is detected, the student will loose the resnet connection forever.
The scheme works at least for most of the students who wouldn't or couldn't sniff their LAN.
we maintain a database where we keep MAC addresses vs IP addresses and student IDs. The users get their IP addresses by signing in an automated service using their student account/passwd (so that we know who they really are) and declaring their MAC addresses to this automated service while they signup with the resnet. An automated task grabs the ARP tables frequently and reports any IP-MAC pairs that we do not have in our database to another program which in turn blocks the IP's Internet access. Since Internet access is the most valuable asset in a dorm room, the user immediately calls the support center to place a complaint or ask whats wrong. and you have a chance to talk directly to the owner of the computer causing the problem. This technyque lets us to be sure about who is using which IP address and this info is useful not only in reaching the owner of an infected machine but also in reaching massive p2p trafficers which is another BIG headache in residential networks. This worked fine UNTIL dear micros~1 added a completely useless and potentially dangerous feature of altering the MAC address of a PC. Now some students sniff their LAN, find valid IP-MAC pairs and monitor the net and when a valid pair shuts down, they change their computer's seetings to these values and so on. The resnet users are warned that if a fraud is detected, the student will loose the resnet connection forever. The scheme works at least for most of the students who wouldn't or couldn't sniff their LAN.
it is not only sco.com and caldera.com. sco.de and sco.it dont respond either. the urls resolve though... it seems that they're dropping incoming http requests
I am sure that someone has asked the same question when Mr. Bool first established the Boolean Arithmetic looong time ago. It is certain that your kids or grandkids will benefit from this. Just be patient...
Win4Lin is a beauty... BUT, it is quite slow on moderate machines and some win application (rare, but there are some) simply wont work! and you're right about stability... the windows running under win4lin is more atable than a standalone win9x.
The main problem being students messing up with the windows configurations and storing personal files created by the users, we came along with the following solution:
- Keep user homes on powerful UNIX servers.
- Install one Linux server in each lab hall (approx one Linux server for each 40-50 PC; a 300 MHz oldish PC with 64 M RAM and a few GB HDD perfectly does the job.
- NFS Mount various home trees on the main server(s) to these lab servers.
- Setup Lab servers to provide print spooling and print quota checks
- Setup lab servers with Samba server; make them domain controllers
- setup lab PCs to authenticate from lab servers. This is the worst part. NT, XP wont do this. Believe it or not, we have the best solution with Win95. Win98 also works, but any win beyond that simply doesnt work.
- Configure lab PCs to have access only to printer(s) in the same lab
- Use some incremental disk restoration program (PC-Rdist is a good one) so that when a student logs out, the Windows settings and any deleted files are restores; any new files added by teh user are cleaned up (except the home directories of course).
- Keep a Windows system disk image on each lab server so in case a machine fails beyond the repair capability of incremental restorer, you can restore a full image over the LAN.
Everybody is happy with the above configuration. The average up-time for PCs have increased to 98%. Access is limited to only students and staff (since a domain logon is enforced). Printer and disk quotas a re under control since these services are in fact provided by UNIX machines. Cookies and other personal information are removed from the pcs when somebody logs out.As far as general security audits are concerned, the net admin will have a log of who used which pc, when and for how long.
The cost is just the cost of an extra PC to be configured as lab server and since you dont need a hell of a peformance on these, any old PC can be used.
Using thin clients in Win env is a dream. The only solution in the markets seems to be Citrix but is certainly is NOT designed for lab environments. They expect users to load one or two applications into the RAM in the morning and use only them till they leave their offices.