Generally, schools will recommend just one or two models of computers to students, and will have minimum requirements other than that. The fewer models, the less need for diversity of support. At the moment, compliance will probably target almost exclusively Windows machines, because they have been the most vulnerable platforms in the last few years, or at least the most exploited. The IT Department at my school also likes students running linux boxes or personal mail or web servers to talk to them first (though they don't publicize that,) basically just to vet the people and make sure that they know what they're doing.
It is a little more complicated than that, in that (certainly at small colleges) there is a relationship between the student body and the administration that makes the interaction at least slightly more give-and-take than you make it sound. The Administration wants the students to be able to use the network, but they also want to keep the network secure. Similarly, it's not just the students- they also want the Faculty to be able to use the network. So we come down to politics driving the usability side of the old security-v-usability dilemma.
Does this mean that they also limit the number of internet devices you're allowed to connect directly to their system? I mean, I suppose you could just hook a router up, but that still seems a little odd.
But it's not just a question of the people knowing how to do it. While it's unlikely, at least for a while, from a security-point of view having a MAC-address change get someone back on the network is still sketchy at best. Theoretically, a virus could change it as well. Not likely, I'll grant, but possible.
Williams College has also spent millions on this over the past few years. It's taken a few years, but class registration is now moving off of the VMS box.
Adaptation is the best way to deal with new technology. Lawsuits are just a way for companies to try to cover their behind until they either understand or are ready for the need to adapt.
On the package selection side, it would be nice to see some change. tasksel is decent enough for a very basic user, but for individual packet selection I find aptitude *a lot* more intuitive and, well, generally shiny, than I suspect dselect will ever be.
But it let in those really cool observations at the council of elrond - what was it - "He might take it, if all the free peoples of the world begged him, but he would not see the need."
Of course! Sorry, clarification: It's the really huge rabbits we have to worry about, and the really fast rabbits. Small rabbits that are not fast at attacking armored men and killing them, merely present the same troubles as tribbles.
This is massively disturbing; I was about to ask the same question. There is no way that, in a sane world, two people should have the human/rabbit embryo lead naturally to "night of the lepus."
Of course, a little rabbit never hurt anybody. It's the really huge rabbits we have to worry about.
Of course, this also brings up an interesting corollary to the Patriot Act. With Librarians destroying logs of what people checked out immediately after those books are returned to keep the government from scanning those logs without people's knowledge, how long is it until logrotated has its cycles tweaked to delete traffic information early? Or maybe just file-sharing traffic? Even a compliant ISP can't give the RIAA data it doesn't have.
Slashdot Mirror
Generally, schools will recommend just one or two models of computers to students, and will have minimum requirements other than that. The fewer models, the less need for diversity of support. At the moment, compliance will probably target almost exclusively Windows machines, because they have been the most vulnerable platforms in the last few years, or at least the most exploited. The IT Department at my school also likes students running linux boxes or personal mail or web servers to talk to them first (though they don't publicize that,) basically just to vet the people and make sure that they know what they're doing.
It is a little more complicated than that, in that (certainly at small colleges) there is a relationship between the student body and the administration that makes the interaction at least slightly more give-and-take than you make it sound. The Administration wants the students to be able to use the network, but they also want to keep the network secure. Similarly, it's not just the students- they also want the Faculty to be able to use the network. So we come down to politics driving the usability side of the old security-v-usability dilemma.
Does this mean that they also limit the number of internet devices you're allowed to connect directly to their system? I mean, I suppose you could just hook a router up, but that still seems a little odd.
But it's not just a question of the people knowing how to do it. While it's unlikely, at least for a while, from a security-point of view having a MAC-address change get someone back on the network is still sketchy at best. Theoretically, a virus could change it as well. Not likely, I'll grant, but possible.
Williams College has also spent millions on this over the past few years. It's taken a few years, but class registration is now moving off of the VMS box.
Anybody have hop count & RTT statistics?
Adaptation is the best way to deal with new technology. Lawsuits are just a way for companies to try to cover their behind until they either understand or are ready for the need to adapt.
On the package selection side, it would be nice to see some change. tasksel is decent enough for a very basic user, but for individual packet selection I find aptitude *a lot* more intuitive and, well, generally shiny, than I suspect dselect will ever be.
But it let in those really cool observations at the council of elrond - what was it - "He might take it, if all the free peoples of the world begged him, but he would not see the need."
Of course! Sorry, clarification: It's the really huge rabbits we have to worry about, and the really fast rabbits. Small rabbits that are not fast at attacking armored men and killing them, merely present the same troubles as tribbles.
Of course, a little rabbit never hurt anybody. It's the really huge rabbits we have to worry about.
Remember to put the junk mail in front of the robot chute so that you get the babel fish, though.
Of course, this also brings up an interesting corollary to the Patriot Act. With Librarians destroying logs of what people checked out immediately after those books are returned to keep the government from scanning those logs without people's knowledge, how long is it until logrotated has its cycles tweaked to delete traffic information early? Or maybe just file-sharing traffic? Even a compliant ISP can't give the RIAA data it doesn't have.