So, we've been on one trouble ticket system since 1992, On August 2 we switched over to a brand new system. I've been here all summer, and the new GUI based interface is 100 times slower than my old command line interface, but there's nothing I can do about it. Not to mention the other half of the student help who aren't here over the summer, and have no idea how to use this new software.
The university I work for has DSL for students, staff and faculty living off campus, but we have to go through Verizon, the cause of numerous headaches. When the students who are living off campus arive, they love hearing it'll be 3 to 6 weeks before DSL is installed and working. There are also students who live off campus, but through our housing department. Until last year, they didn't have any way of connecting other than through modem. Last year they got DSL through us. This year, they're going through Telerama. So all these incoming students looking for help to get their internet connection setup will first call me, then I'll have to look up Telerama's phone number and give that to them. I know I'll hear back from them when their connection doesn't work.
We also have implimented Wireless ethernet in the dorms over the summer in addition to wired ethernet. Our Service Level Agreement states that we support Win 95/98/ME/NT/2k/XP, Mac OS 7.6.1 through the most recent OS X. Technically we support Linux, but only our university's release, which is basically RedHat 6. Certain students and professors also have their own SUN, DEC ULTRIX, HPUX, SGI and whatnot other boxes which are also supported, but that luckily is not something I deal with often.
We also use special software that incorporates Kerberos authentication to send and recieve e-mail. Without that software, if people are using another ISP to read their e-mail, they can send e-mail to on campus recipients, but they can't send it off campus without changing the server they're using through a somewhat obscure preferences panel. And that software is bug-ridden to say the least.
In order to get connectivity, all users must register their MAC address, and wired users on campus must also register their outlet. With the exception of wireless and DSL, almost all the subnets assign static IPs, but we insist that users configure their computer for DHCP, for network abuse issues.
Now, you can imagine how much of a pain that can be, but for the next 3 weeks, my life is going to be a blur of alphanumeric userIDs, MAC and outlet addresses. But, lucky for me, we have beefed up our staff. Now, all the "experts" (programmers, administrators and the like) in Computing Services have scheduled a few hours every day to handle the approximately 1700 incoming freshmen and in total about 6000 returning students. In addition to the walkin/call center that is usually staffed from 9am-7pm, we'll be open until 8:30pm, we'll be closing our doors to the call center so that we can only take phone calls. We are also opening two outposts to handle walkins, and at certain hours, we will actually have people going to student's dorm rooms so that they can get on the network.
Fun, fun, fun, I already can't wait for next year.
You get MUCH better quality doing it yourself though. OEM motherboards are severly limited in settings, and dont support much. Cases are hard to upgrade, and for support you wait on hold forever.
nobody (statistically) really cares - for that matter, 99% of the population has no reason to care about code red anyway. SirCam should be getting the attention, but "Code Red" has a much more sensational name. Hence, the media blows it out of proportion
thats interesting. If they rewrote the article to handle generally screwed up cds, they could claim ignorance - how the f--- should we know that the cd was copy protected and not just dirty?
well, i thought it was pretty impressive to see the boost, whether or not that'll ever be realized in applications. that is some impressive performance
Slashdot Mirror
for the hibernation, if you hold shift, or control, or alt, (i really dont remember) on the shutdown dialog box, standby is replaced with hibernate
if there is a little pad under the heatsink, that should work in theory. if its bare metal, get paste
actually, the few seconds is without a heatsink. 6-8 seconds for a 1 gig on powerup, i believe
wow, a gig p3 for pr0n? what a waste of clock cycles :-p
slowing the clock lets you drop the voltage, which as a net result results in a MUCH cooler processor
That'd be the place.
The university I work for has DSL for students, staff and faculty living off campus, but we have to go through Verizon, the cause of numerous headaches. When the students who are living off campus arive, they love hearing it'll be 3 to 6 weeks before DSL is installed and working. There are also students who live off campus, but through our housing department. Until last year, they didn't have any way of connecting other than through modem. Last year they got DSL through us. This year, they're going through Telerama. So all these incoming students looking for help to get their internet connection setup will first call me, then I'll have to look up Telerama's phone number and give that to them. I know I'll hear back from them when their connection doesn't work.
We also have implimented Wireless ethernet in the dorms over the summer in addition to wired ethernet. Our Service Level Agreement states that we support Win 95/98/ME/NT/2k/XP, Mac OS 7.6.1 through the most recent OS X. Technically we support Linux, but only our university's release, which is basically RedHat 6. Certain students and professors also have their own SUN, DEC ULTRIX, HPUX, SGI and whatnot other boxes which are also supported, but that luckily is not something I deal with often.
We also use special software that incorporates Kerberos authentication to send and recieve e-mail. Without that software, if people are using another ISP to read their e-mail, they can send e-mail to on campus recipients, but they can't send it off campus without changing the server they're using through a somewhat obscure preferences panel. And that software is bug-ridden to say the least.
In order to get connectivity, all users must register their MAC address, and wired users on campus must also register their outlet. With the exception of wireless and DSL, almost all the subnets assign static IPs, but we insist that users configure their computer for DHCP, for network abuse issues.
Now, you can imagine how much of a pain that can be, but for the next 3 weeks, my life is going to be a blur of alphanumeric userIDs, MAC and outlet addresses. But, lucky for me, we have beefed up our staff. Now, all the "experts" (programmers, administrators and the like) in Computing Services have scheduled a few hours every day to handle the approximately 1700 incoming freshmen and in total about 6000 returning students. In addition to the walkin/call center that is usually staffed from 9am-7pm, we'll be open until 8:30pm, we'll be closing our doors to the call center so that we can only take phone calls. We are also opening two outposts to handle walkins, and at certain hours, we will actually have people going to student's dorm rooms so that they can get on the network.
Fun, fun, fun, I already can't wait for next year.
I'm assuming that a cyclotron is a particle accelerator?
You get MUCH better quality doing it yourself though. OEM motherboards are severly limited in settings, and dont support much. Cases are hard to upgrade, and for support you wait on hold forever.
nobody (statistically) really cares - for that matter, 99% of the population has no reason to care about code red anyway. SirCam should be getting the attention, but "Code Red" has a much more sensational name. Hence, the media blows it out of proportion
thats interesting. If they rewrote the article to handle generally screwed up cds, they could claim ignorance - how the f--- should we know that the cd was copy protected and not just dirty?
of course. they already execute the most people... now they can start working on instructions!!
I thought 7.1 fixed it... make bzImage worked fine on the test box I set up. 7.0 is the stupid one where you have to set gcc=kgcc
whats wrong with that? :D
actually, if you hit some limits, it gives you 14 days to clean up before old messages get killed
well, i thought it was pretty impressive to see the boost, whether or not that'll ever be realized in applications. that is some impressive performance