The first point is one of the reasons why iPods were not given to everyone at Duke--if it's a flop, the investment is a small cost. Everyone is confident it will be a success, though, so if the program is continued, eventually everyone will get an iPod by way of matriculating (iPod propagation, if you will).
...I don't think I'd be able to resist the temptation to say "By the way, I'm a hardcore Windows fan" right as he went under anesthesia. Then tell him the truth when he came back around.
Yup. OpenAFS. I tried Arla way back in the day as well...both have caused me kernel panic issues and general slowness. And while its not a HUGE issue, I cringe at the idea of needing to change my local UID to match my ACPUB UID....I can't see Apple supporting that.
what about a general user who just wants to be able to check email or read news without having to wait five minutes to log in on the new OS X.blah boxes?
Indeed that's the problem, and I've always somewhat advocated getting more "dumber" (sic) machines on campus in certain areas...any NetID would log you in, but without a home directory, it wouldn't be limited by AFS...it wouldn't record any web cache, history, etc...thatd be nice, IMO. That "5 minutes" you speak of is a little exaggerated, but the AFS client for Mac OS X does suck some significant donkey balls, and that's the cause of the delay (as if we didn't know...).
Sadly, I have. It's so slow I can hardly believe it at times. Both the Windows and Mac OS X clients are very young and not very refined...they are a beast to setup on one's personal machine, and can cause kernel issues. The fact that ResNet is so inundated with P2P traffic makes me cringe about using any network drive, let alone one as slow as AFS to begin with.
When I go to the labs, I have my files either on my personal machine (vanity name!), or sftp them to ACPUB space first...then at least I only have to deal with AFS on one end.
Just to clear one thing up though...Mac OS X is a UNIX box (essentially), and when one logs in to a Mac on campus, the home directory is your ACPUB space as well. The whole AFSDocs folder is a myth--just one folder--the entire space is networked. The Windows machines don't have networked home directories in the same way. Try the Macs.
I dunno where the whole CVS is broken thing comes in....its always worked fine for me. It's more complicated than most people would like, but c'est la vie.
I think that they made this decision based on several factors, including the "ooh, pretty!" factor.
Now that that's out of your system, let me assure you that while many were attracted to the iPod's pop-culture cult status as a part of this project, the academic and educational uses were the primary discussion. The "ooh, pretty!" factor, as you call it, was taken into consideration so the students would actually want to use the device given to them. Imagine Duke giving every student a Palm Zire...which most students would promptly toss in their desk after a month of occasional use if their classes didn't require it--most still won't, btw. But an iPod...the students will love those and use them!
I don't know who your friend is--I have some ideas--but if the "wow" factor is his explanation, he fell asleep at a few of the briefings, methinks. Take my word for it.
As for NACHOS....I didn't like it any more than you did, but many factors prevent 110 and 210 from switching to other options...I'd rather not rock the boat in the CS Dept right now.
Actually, Apple's OS Up-to-Date programs have always been similar. If you buy the old version on or after the date the new product is announced, you get to use the up-to-date program...if you buy the old version before the new one was announced, they don't feel sorry for you. It was this way with Jaguar and Panther, and may be the same for Tiger, then.
The issue is that this "trojan" is not really an AppleScript doing the heavy lifting--it's an AppleScript wrapper for a UNIX shell command such as "rm -rf ~/*" (or similar). If Apple put in such a system alert for the command line, it would seriously piss off a lot of *nix geeks who have expectations that they not encounter such alerts...when would you have those alerts? Just for certain folders? It'd be tough to properly script things when you don't know the expected behavior...
That aside, even if you did overload (er, recode) rm to have that bizarre behavior for certain files, the -f flag should suppress that and force the delete anyway. Tie that in with the AppleScript shell bridge and you have the makings of the same issue.
Wrong wrong wrong. That's the whole point of sudo (execute a command as another user). The default is to execute as root but it can be any user....
To that end, typing "sudo -s" will get you a root shell without ever activating the root user. In my experiences with OS X (which is extensive), the only reason I've ever had to activate root was to log in to the machine as root, which was more of a convenience than a necessity.
...what's the chance of Apple porting any libraries to Linux, and allowing anyone to run anything without buying a new Mac, every subsequent OS version, etc?
Don't let this get too publicized or all those office morons (the ones of tech support legend: CD Tray==Cupholder, etc) might start pouring their morning tea on the computer after a crash.
This could only prompt me to ask them: One Lump or Two? [WHACK WHACK]
Slashdot Mirror
Wow. Mod this parent up....wish I hadn't used up my mod points before this story.
http://www.duke.edu/ipod/
The first point is one of the reasons why iPods were not given to everyone at Duke--if it's a flop, the investment is a small cost. Everyone is confident it will be a success, though, so if the program is continued, eventually everyone will get an iPod by way of matriculating (iPod propagation, if you will).
Primary Reason: Because Belkin donated the Voice Recorders to Duke for nothing.
Without a doubt, the worst movie I have ever seen.
Fairly tough to make a sturdy car that is also lightweight enough to be driven by low-power solar generation...
the rocket, whose parachute malfunctioned, would have to be rebuilt
Usually one DOES have to rebuild after it EXPLODES!
Too many sites do this, and then face the fury of /.
Unfortunately some of the images are quite large (none more than 250KB)
All kidding aside, I'm more than glad he's going to be okay. He's done more for the computer industry than most.
...I don't think I'd be able to resist the temptation to say "By the way, I'm a hardcore Windows fan" right as he went under anesthesia. Then tell him the truth when he came back around.
Actually, it would look like this
Yup. OpenAFS. I tried Arla way back in the day as well...both have caused me kernel panic issues and general slowness. And while its not a HUGE issue, I cringe at the idea of needing to change my local UID to match my ACPUB UID....I can't see Apple supporting that.
It's like putting your parents in an old-folks home as a golden wedding anniversary present. Oh well....worse things have happened.
Indeed that's the problem, and I've always somewhat advocated getting more "dumber" (sic) machines on campus in certain areas...any NetID would log you in, but without a home directory, it wouldn't be limited by AFS...it wouldn't record any web cache, history, etc...thatd be nice, IMO. That "5 minutes" you speak of is a little exaggerated, but the AFS client for Mac OS X does suck some significant donkey balls, and that's the cause of the delay (as if we didn't know...).
When I go to the labs, I have my files either on my personal machine (vanity name!), or sftp them to ACPUB space first...then at least I only have to deal with AFS on one end.
Just to clear one thing up though...Mac OS X is a UNIX box (essentially), and when one logs in to a Mac on campus, the home directory is your ACPUB space as well. The whole AFSDocs folder is a myth--just one folder--the entire space is networked. The Windows machines don't have networked home directories in the same way. Try the Macs.
I dunno where the whole CVS is broken thing comes in....its always worked fine for me. It's more complicated than most people would like, but c'est la vie.
Now that that's out of your system, let me assure you that while many were attracted to the iPod's pop-culture cult status as a part of this project, the academic and educational uses were the primary discussion. The "ooh, pretty!" factor, as you call it, was taken into consideration so the students would actually want to use the device given to them. Imagine Duke giving every student a Palm Zire...which most students would promptly toss in their desk after a month of occasional use if their classes didn't require it--most still won't, btw. But an iPod...the students will love those and use them!
I don't know who your friend is--I have some ideas--but if the "wow" factor is his explanation, he fell asleep at a few of the briefings, methinks. Take my word for it.
As for NACHOS....I didn't like it any more than you did, but many factors prevent 110 and 210 from switching to other options...I'd rather not rock the boat in the CS Dept right now.
(X+Y)*(X-Y) = X*(X-Y)
I think you misfactored here. XY-Y^2 = Y*(X-Y), no?
My last techie girlfriend owned a Wallstreet model Powerbook *shudder*
/.ers can go a decade without 2 girlfriends.
Which should be perfectly fine, since one can assume that probably WAS around 1998...I know that some
Unless you've got something against the PowerBook...
Actually, Apple's OS Up-to-Date programs have always been similar. If you buy the old version on or after the date the new product is announced, you get to use the up-to-date program...if you buy the old version before the new one was announced, they don't feel sorry for you. It was this way with Jaguar and Panther, and may be the same for Tiger, then.
The issue is that this "trojan" is not really an AppleScript doing the heavy lifting--it's an AppleScript wrapper for a UNIX shell command such as "rm -rf ~/*" (or similar). If Apple put in such a system alert for the command line, it would seriously piss off a lot of *nix geeks who have expectations that they not encounter such alerts...when would you have those alerts? Just for certain folders? It'd be tough to properly script things when you don't know the expected behavior...
That aside, even if you did overload (er, recode) rm to have that bizarre behavior for certain files, the -f flag should suppress that and force the delete anyway. Tie that in with the AppleScript shell bridge and you have the makings of the same issue.
Wrong wrong wrong. That's the whole point of sudo (execute a command as another user). The default is to execute as root but it can be any user....
To that end, typing "sudo -s" will get you a root shell without ever activating the root user. In my experiences with OS X (which is extensive), the only reason I've ever had to activate root was to log in to the machine as root, which was more of a convenience than a necessity.
They won't even port Quicktime!
my job security is guaranteed
Lemme guess: You use and recommend Windows products to those users for the same job security reason?
Spray
This could only prompt me to ask them: One Lump or Two? [WHACK WHACK]