Facebook is not banned from any KSU PCs that I've used.
$ telnet www.facebook.com 80 GET / HTTP/1.1 Host: www.facebook.com
returns the expected from machines in the Kent CS and Geography departments. Granted, Network Services does bandwidth capping and QoS for at least dorm connections. I believe they severely rate-limit packets believed to be from P2P networks (so much so as to make them unusable). I've never heard of them outright blocking any web resources though.
What is the "Technology Division"? I've been in CS since 2001 and I've never heard of it.
It seems like the "Collections" concept of the upcoming XMMS2 is designed to address your problem squarely.
Sébastien Cevey, one of the developers, wrote a manifesto on the subject, claiming that collections (hierarchical, unordered subsets) and playlists (flat, ordered subsets) of a larger library are the solution to media file management. It also happens to be a good review of how different media players handle the problem.
Slashdot Mirror
Wow. That was a big waste of time. All of this stuff is obvious and everyone knows it. Why did anyone write all of this?
Let's say you want to rename all *.jpeg files to *.jpg.
A little simpler:
for i in *.jpeg; do mv $i `basename $i`.jpg; done
Or (on a Red Hat distro):
rename '.jpeg' '.jpg' *.jpeg
Or (on a debian distro):
rename 's/\.jpeg$/.jpg/' *.jpeg
If you're not sure which your system uses, run: man rename
What is the "Technology Division"? I've been in CS since 2001 and I've never heard of it.
It seems like the "Collections" concept of the upcoming XMMS2 is designed to address your problem squarely. Sébastien Cevey, one of the developers, wrote a manifesto on the subject, claiming that collections (hierarchical, unordered subsets) and playlists (flat, ordered subsets) of a larger library are the solution to media file management. It also happens to be a good review of how different media players handle the problem.