If you do a web search with the terms linux timeline (especially if you narrow the search down to "Images" using Google search), you'll find tons of charts showing how Linux has evolved over the years and branched out into different distributions. Some of the charts are old; some are kept relatively up-to-date.
A site that appears to frequently publish an updated Linux timeline: http://futurist.se/gldt/
They provide links for .png and .svg images, as well as a tar.bz2 file. If you click on the .png image, for example, the timeline will open up in your browser, and you can click on it for a close-up view.
A Linux fan could spend a lot of time exploring the branches of one of these timelines! I check 'em out from time to time, but today is the first time I noticed the inclusion of some of the relatively new distros like SalineOS and Linux Mint Debian on the Debian branch, and PearOS (based on Ubuntu).
These timelines show that most current Linux distros descend from Debian, Red Hat, and Slackware, with quite a considerable number descended from Ubuntu on the Debian branch. And more than a few distros have died off, like the Lindows/Linspire line (Linspire was my first distro!), and the Corel/Xandros line (Xandros was another one I used early on in my Linux days).
Looking down the "2003" column, where Mepis (which I still use here) first appears, I notice an explosion of distros that year and in the following couple of years -- especially on the Knoppix line. This kinda shows the influence of the live CD (pioneered by -- but not begun with -- distros like Knoppix and Mepis, both of which came before Ubuntu).
There's been an incredible amount of branching, resulting in hundreds of Linux distros. I was somewhat surprised to see all of the distros coming from the Red Hat branch prior to 2003; lots of those are no longer alive.
Anyway, a must-see for anyone interested in Linux history!
Saturday, January 28, 2012
Thursday, January 26, 2012
a year with saline
Well, it's been a full year since I first installed SalineOS here. I like to spend some time with a distro and not jump to any conclusion about it after a few days or weeks; Saline has not disappointed.
For the most part, Saline is just Debian Squeeze with Xfce. A few things that set SalineOS 1.x apart from Squeeze:
- Quick, easy installation from a single live DVD
- A User Manual, located conveniently on the desktop (I later moved mine into my home directory) that includes installation instructions and other information
- Lines in /etc/apt/sources.list for Squeeze Backports, WINE, and Remastersys
- Chromium is the default web browser, instead of Iceweasel
- While Synaptic is available for adding software, there's an AutoUpdate script that uses aptitude for updates; they include an icon on the panel to start this script, and one kinda odd thing about it is that it opens up two terminal windows
From the SalineOS "About" page:
The primary goal of the SalineOS project is to deliver a fast, lightweight, clean, easy to use and well doccumented operating system based on Debian GNU/Linux. In keeping with these goals SalineOS includes many things added on top of Debian to make it easier to use and more complete out of the box. This includes a choice of sgfxi and magix-driver-installer for installing proprietary graphics drivers, Debian repositories that include software that does not conform to Debian's strict free software guidelines, WINE repositories, Remastersys backup utility, binary firmware for common wireless network cards, the Debian backports repository and a script to install potentially patent encumbered multimedia codecs with one command.
Saline's developer, Anthony Nordquist, released SalineOS 1.0 right after Debian Squeeze was "frozen" -- before Squeeze actually became Debian Stable. Looks like he plans to do the same kind of thing with 2.0, planning to release the early development builds with the Wheezy freeze (probably at least 6 months away, yet).
Among other things, he plans to go with the Midori web browser, and will not include the Synaptic package manager. Chromium in the Stable repos kinda lags behind (which is why I ended up installing Google Chrome in Saline, as well as in Debian Stable). And Synaptic is easy enough to install, if you want it (I do).
Nordquist also plans to set up his own repository -- as he posted in the forum, "...this is likely to include packages for the user manual, salineos_utils, game packages built from upstream's pre-compiled binaries and packages pulled from Debian backports (When they start for Wheezy)."
About the only thing about SalineOS that I can think of that might be considered a drawback is that it's a "one-man distro." I don't necessarily consider that to be a drawback; part of the beauty of Linux is that lone developers can do some things that really can't be done with distros run by large organizations. Also, Saline uses Debian repos, so in that sense it isn't completely a one-man distro.
Considering that a lot of people complain about Debian being kinda difficult to install, and that a lot of people are unhappy with the direction GNOME has taken, and prefer something like Xfce, it surprises me a bit that SalineOS hasn't caught on more than it has. But it's still in its infancy, really. I'll be interested to see how much more popular it becomes over the next few years. I certainly plan to keep it installed here!
Here's a link to the home web page: http://www.salineos.com/
And, one more screen shot of my SalineOS desktop:
For the most part, Saline is just Debian Squeeze with Xfce. A few things that set SalineOS 1.x apart from Squeeze:
- Quick, easy installation from a single live DVD
- A User Manual, located conveniently on the desktop (I later moved mine into my home directory) that includes installation instructions and other information
- Lines in /etc/apt/sources.list for Squeeze Backports, WINE, and Remastersys
- Chromium is the default web browser, instead of Iceweasel
- While Synaptic is available for adding software, there's an AutoUpdate script that uses aptitude for updates; they include an icon on the panel to start this script, and one kinda odd thing about it is that it opens up two terminal windows
From the SalineOS "About" page:
The primary goal of the SalineOS project is to deliver a fast, lightweight, clean, easy to use and well doccumented operating system based on Debian GNU/Linux. In keeping with these goals SalineOS includes many things added on top of Debian to make it easier to use and more complete out of the box. This includes a choice of sgfxi and magix-driver-installer for installing proprietary graphics drivers, Debian repositories that include software that does not conform to Debian's strict free software guidelines, WINE repositories, Remastersys backup utility, binary firmware for common wireless network cards, the Debian backports repository and a script to install potentially patent encumbered multimedia codecs with one command.
Saline's developer, Anthony Nordquist, released SalineOS 1.0 right after Debian Squeeze was "frozen" -- before Squeeze actually became Debian Stable. Looks like he plans to do the same kind of thing with 2.0, planning to release the early development builds with the Wheezy freeze (probably at least 6 months away, yet).
Among other things, he plans to go with the Midori web browser, and will not include the Synaptic package manager. Chromium in the Stable repos kinda lags behind (which is why I ended up installing Google Chrome in Saline, as well as in Debian Stable). And Synaptic is easy enough to install, if you want it (I do).
Nordquist also plans to set up his own repository -- as he posted in the forum, "...this is likely to include packages for the user manual, salineos_utils, game packages built from upstream's pre-compiled binaries and packages pulled from Debian backports (When they start for Wheezy)."
About the only thing about SalineOS that I can think of that might be considered a drawback is that it's a "one-man distro." I don't necessarily consider that to be a drawback; part of the beauty of Linux is that lone developers can do some things that really can't be done with distros run by large organizations. Also, Saline uses Debian repos, so in that sense it isn't completely a one-man distro.
Considering that a lot of people complain about Debian being kinda difficult to install, and that a lot of people are unhappy with the direction GNOME has taken, and prefer something like Xfce, it surprises me a bit that SalineOS hasn't caught on more than it has. But it's still in its infancy, really. I'll be interested to see how much more popular it becomes over the next few years. I certainly plan to keep it installed here!
Here's a link to the home web page: http://www.salineos.com/
And, one more screen shot of my SalineOS desktop:
Sunday, January 22, 2012
man pages in your browser
This worked for me in Ubuntu 10.04 and Debian Squeeze. Don't know yet if it will work in other distros. A "thank you" for this tip to Linux Mint forum member "Habitual."
For this to work, you will need to have groff installed. In Ubuntu 10.04, installing groff brought in these packages:
groff (1.20.1-7)
libnetpbm10 (2:10.0-12.1ubuntu1)
netpbm (2:10.0-12.1ubuntu1)
psutils (1.17-27)
In Squeeze, it brought in these:
groff (1.20.1-10)
psutils (1.17-27)
Next, add the following to ~/.bashrc:
export BROWSER=chromium-browser
alias manb="man -H"
If you don't use Chromium, replace "chromium-browser" with "firefox" or "google-chrome" or whatever.
Then ran the following command:
source ~/.bashrc
(As Mint forum member "Jesse654" explains: "The file .bashrc is being changed. The source command reloads .bashrc. If you logged out, then logged in again, .bashrc would be reloaded automatically.")
Then, the following command will open "man page" in your browser:
$ manb [man page]
For example:
$ manb date
When I tried this without having groff installed, I got something like this:
$ manb date
man: command exited with status 3: /usr/bin/zsoelim | /usr/lib/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | tbl | groff -mandoc -Thtml
So, you need groff.
I couldn't get this to work in PCLinuxOS. Here's what I saw:
$ source ~/.bashrc
bash: TMOUT: readonly variable
$ manb date
What manual page do you want?
For this to work, you will need to have groff installed. In Ubuntu 10.04, installing groff brought in these packages:
groff (1.20.1-7)
libnetpbm10 (2:10.0-12.1ubuntu1)
netpbm (2:10.0-12.1ubuntu1)
psutils (1.17-27)
In Squeeze, it brought in these:
groff (1.20.1-10)
psutils (1.17-27)
Next, add the following to ~/.bashrc:
export BROWSER=chromium-browser
alias manb="man -H"
If you don't use Chromium, replace "chromium-browser" with "firefox" or "google-chrome" or whatever.
Then ran the following command:
source ~/.bashrc
(As Mint forum member "Jesse654" explains: "The file .bashrc is being changed. The source command reloads .bashrc. If you logged out, then logged in again, .bashrc would be reloaded automatically.")
Then, the following command will open "man page" in your browser:
$ manb [man page]
For example:
$ manb date
When I tried this without having groff installed, I got something like this:
$ manb date
man: command exited with status 3: /usr/bin/zsoelim | /usr/lib/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | tbl | groff -mandoc -Thtml
So, you need groff.
I couldn't get this to work in PCLinuxOS. Here's what I saw:
$ source ~/.bashrc
bash: TMOUT: readonly variable
$ manb date
What manual page do you want?
Sunday, January 8, 2012
change
Seems that one of the main reasons I had little problem adapting to KDE4 and GNOME 3 had to do with something I read in a book some years ago -- one of Octavia Bulter's science fiction novels. One of her characters was saying something along the lines of how "Change" is gonna happen no matter what, and the thing is to prepare yourself and position yourself to take advantage of that.
A simple idea, but it struck me as profound at the time, and I kinda decided to try to have that sort of outlook in my life.
It was an idea that was in the back of my mind when I decided to learn to use Linux. And while using Linux, it's had a lot do with my deciding to spend time with different distros, DEs, and WMs, and to try to become comfortable with .rpm distros as well as the Debian distros that I started out with.
So I wasn't all that tied down to KDE 3 or GNOME 2, and I've adapted to KDE 4 and GNOME 3 quite easily.
I really feel that my being open to Change -- preparing for its eventuality, positioning myself for it, embracing it -- has really allowed me to be more accepting than a lot of other people of the directions that KDE and GNOME have taken. So many of the comments I saw about KDE 4, and that I'm seeing about GNOME 3, are along the lines of, "It isn't KDE 3," or "It isn't GNOME 2." "It isn't what I'm used to," "It isn't like what we've been using all along."
And folks feel that the changes were forced on them. But that's usually how Change happens. Change doesn't usually stop and ask, "You gonna be okay with this?" It just comes, and if you haven't prepared yourself for it, you're gonna get blindsided by it, and you're gonna find yourself longing for the way things used to be.
A simple idea, but it struck me as profound at the time, and I kinda decided to try to have that sort of outlook in my life.
It was an idea that was in the back of my mind when I decided to learn to use Linux. And while using Linux, it's had a lot do with my deciding to spend time with different distros, DEs, and WMs, and to try to become comfortable with .rpm distros as well as the Debian distros that I started out with.
So I wasn't all that tied down to KDE 3 or GNOME 2, and I've adapted to KDE 4 and GNOME 3 quite easily.
I really feel that my being open to Change -- preparing for its eventuality, positioning myself for it, embracing it -- has really allowed me to be more accepting than a lot of other people of the directions that KDE and GNOME have taken. So many of the comments I saw about KDE 4, and that I'm seeing about GNOME 3, are along the lines of, "It isn't KDE 3," or "It isn't GNOME 2." "It isn't what I'm used to," "It isn't like what we've been using all along."
And folks feel that the changes were forced on them. But that's usually how Change happens. Change doesn't usually stop and ask, "You gonna be okay with this?" It just comes, and if you haven't prepared yourself for it, you're gonna get blindsided by it, and you're gonna find yourself longing for the way things used to be.
Wednesday, December 21, 2011
Trying GS Extensions
So far, I'm not much of a fan of GNOME Shell extensions. For the most part, I prefer the default set-up, and I have no problem getting around the desktop and getting work done.
Up until today, I had the following extensions installed in Fedora 16:
Alternative Status Menu: I like this one because it gives a Power Off option, which is something that should have been included in GNOME Shell from the beginning. I installed it from the Fedora repos, but it conflicted with GNOME Shell at first, until some subsequent updates apparently fixed it.
Icon-Manager: Don't use it, have it turned off.
Workspace Indicator: This is a pretty good extension for showing which workspace you're currently on, and provides an alternative way to quickly switch between workspaces. I have it running, but I rarely use it for switching workspaces.
Dock Extension: Don't use it, have it turned off.
User Themes: I have it turned on, but I've played with it only a couple of times.
Applications Menu: It's turned on, but I rarely use it.
Today, I added a couple more extensions: Panel-Docklet and Area Screenshot. Until now, I've only used extensions installed from the Fedora repos, but I pulled these two from the GNOME Shell Extensions site.
I use Google Chrome (or Chromium, depending on the distro I'm using at the moment). But the GNOME Shell Extensions site doesn't work with Chrome or Chromium; if you go there with one of those browsers, you'll see a mesage saying, "You do not appear to have an up to date version of GNOME3. You won't be able to install extensions from here."
You'll see this message even if your GNOME 3 version actually IS up-to-date.
So, I went to the site using Firefox.
Once you find an extension you want to install, you click on it's name and you're taken to that extension's page. There you'll find an on-off switch next to the name of the extension. Turn it on, and after a few seconds you're given the option to install the extension. I did this for Panel-Docklet, it installed, and I was taken through a settings manager. I was notified that I could later access the settings by right-clicking on Panel-Docklet.
While Panel-Docklet can be turn on/off via Advanced Settings, I see no way uninstall it other than going back to the extension site with Firefox and uninstalling it there.
One problem I'm noticing is that the icons sit too high on the panel, cutting off the top part of the icon. This screen shot gives you an idea:
With the mouse hovering over Panel-Docklet, you get a drop down list showing all open windows on each workspace, separated nicely by workspace.
If you right-click on one of the icons, you get a menu with the following items: Close Window, Minimize, New Window, Application, and the name of the active window. Under Application, there are options to Quit Application and Remove from Favorites.
If you right-click on one of the workspace numbers, you get a menu with the following items: Settings; and a menu of the same Favorites that you have in Dash (the dock) -- only, in reverse order! Hopefully this will be fixed.
It seems a bit buggy yet. I've lost control of the mouse at various times, particularly after trying to take a screen shot with GNOME's default screen shot app. Also I've noticed some times when the wrong workspace number was being displayed. Further, I'm not sure that I like having it up there in the panel any better than simply using the hot spot in the upper left corner to get a view of apps running on various workspaces, although it does seem useful for going directly to a particular running app quickly.
Next, I added the Area Screenshot Extension. As noted in the extension's homepage:
By default, this extension does nothing; you have to assign a keyboard shortcut to it. To do this, you can run the following command[s]:
key='/apps/metacity/global_keybindings/run_command_10'
gconftool-2 -s --type string "$key" 'Print'
After running those commands, I tried it out. The extension's homepage notes:
When you hit + Print now, you can select an area on your screen with your mouse. After releasing your mouse, a new screenshot will be saved in your local "Pictures" directory with the current timestamp. You can also take a screenshot of a single window by simply clicking on it.
When taking an area screenshot, you can set a timer to be able to open context menus and such, which can't usually be captured. To set the timer, simply press the numbers 1 to 9 on your keyboard to define the countdown. The timer will appear in the bottom left of your screen. After making your selection, it will count down to zero. Pressing 0 on your keyboard will deactivate the timer.
Well, things worked okay, except the timer didn't work at all here. I pressed numbers on the keyboard to define the countdown, but no timer ever appeared on my screen. I was able to select areas of the screen with the mouse, but the extension didn't work at all, for example, when I right-clicked on an icon in the Panel-Docklet extension to open up the menu.
So, I'm not sold on most of the GNOME Shell extensions I've tried so far. For now, I think I'm better off staying close to the default GNOME Shell, as designed by the GNOME developers. That set-up works fine for me; we'll see how things turn out in the future.
Up until today, I had the following extensions installed in Fedora 16:
Alternative Status Menu: I like this one because it gives a Power Off option, which is something that should have been included in GNOME Shell from the beginning. I installed it from the Fedora repos, but it conflicted with GNOME Shell at first, until some subsequent updates apparently fixed it.
Icon-Manager: Don't use it, have it turned off.
Workspace Indicator: This is a pretty good extension for showing which workspace you're currently on, and provides an alternative way to quickly switch between workspaces. I have it running, but I rarely use it for switching workspaces.
Dock Extension: Don't use it, have it turned off.
User Themes: I have it turned on, but I've played with it only a couple of times.
Applications Menu: It's turned on, but I rarely use it.
Today, I added a couple more extensions: Panel-Docklet and Area Screenshot. Until now, I've only used extensions installed from the Fedora repos, but I pulled these two from the GNOME Shell Extensions site.
I use Google Chrome (or Chromium, depending on the distro I'm using at the moment). But the GNOME Shell Extensions site doesn't work with Chrome or Chromium; if you go there with one of those browsers, you'll see a mesage saying, "You do not appear to have an up to date version of GNOME3. You won't be able to install extensions from here."
You'll see this message even if your GNOME 3 version actually IS up-to-date.
So, I went to the site using Firefox.
Once you find an extension you want to install, you click on it's name and you're taken to that extension's page. There you'll find an on-off switch next to the name of the extension. Turn it on, and after a few seconds you're given the option to install the extension. I did this for Panel-Docklet, it installed, and I was taken through a settings manager. I was notified that I could later access the settings by right-clicking on Panel-Docklet.
While Panel-Docklet can be turn on/off via Advanced Settings, I see no way uninstall it other than going back to the extension site with Firefox and uninstalling it there.
One problem I'm noticing is that the icons sit too high on the panel, cutting off the top part of the icon. This screen shot gives you an idea:
With the mouse hovering over Panel-Docklet, you get a drop down list showing all open windows on each workspace, separated nicely by workspace.
If you right-click on one of the icons, you get a menu with the following items: Close Window, Minimize, New Window, Application, and the name of the active window. Under Application, there are options to Quit Application and Remove from Favorites.
If you right-click on one of the workspace numbers, you get a menu with the following items: Settings; and a menu of the same Favorites that you have in Dash (the dock) -- only, in reverse order! Hopefully this will be fixed.
It seems a bit buggy yet. I've lost control of the mouse at various times, particularly after trying to take a screen shot with GNOME's default screen shot app. Also I've noticed some times when the wrong workspace number was being displayed. Further, I'm not sure that I like having it up there in the panel any better than simply using the hot spot in the upper left corner to get a view of apps running on various workspaces, although it does seem useful for going directly to a particular running app quickly.
Next, I added the Area Screenshot Extension. As noted in the extension's homepage:
By default, this extension does nothing; you have to assign a keyboard shortcut to it. To do this, you can run the following command[s]:
key='/apps/metacity/global_keybindings/run_command_10'
gconftool-2 -s --type string "$key" '
After running those commands, I tried it out. The extension's homepage notes:
When you hit
When taking an area screenshot, you can set a timer to be able to open context menus and such, which can't usually be captured. To set the timer, simply press the numbers 1 to 9 on your keyboard to define the countdown. The timer will appear in the bottom left of your screen. After making your selection, it will count down to zero. Pressing 0 on your keyboard will deactivate the timer.
Well, things worked okay, except the timer didn't work at all here. I pressed numbers on the keyboard to define the countdown, but no timer ever appeared on my screen. I was able to select areas of the screen with the mouse, but the extension didn't work at all, for example, when I right-clicked on an icon in the Panel-Docklet extension to open up the menu.
So, I'm not sold on most of the GNOME Shell extensions I've tried so far. For now, I think I'm better off staying close to the default GNOME Shell, as designed by the GNOME developers. That set-up works fine for me; we'll see how things turn out in the future.
A few additional notes regarding the extensions from the GNOME Shell Extensions site (as opposed to the ones available in the Fedora repos):
- Right now, if you want to update extensions, you have to uninstall them manually and reinstall them. Gnome 3.4 is supposed to include features for automatic updates of these extensions.
- You can either go to the site to uninstall extensions, or you can remove the extension's directory which is stored in ~/.local/share/gnome-shell/extensions, then restart the session.
I think I'll wait few weeks, then try uninstalling and re-installing some of the extensions from that site, and see how things have progressed.
f16 wallpaper fun
I managed to get an automatic wallpaper changer working in Fedora 16 in GNOME Shell, thanks to Ubuntu forum member "mareser." It's a script run by a cron job. mareser provides the script and a command to set up the cron job in this thread; anyone interested can pick them up from there.
Since I was trying this in Fedora 16 (not in Ubuntu), I did a few things differently. I dropped some wallpapers into a directory called ~/wallpapers, extracted the script to my home directory, and within the script edited the following line to read:
wallpaper_dir="/home/steve/wallpapers/"
I edited his command for setting up the cron job, changing the time interval from "30" to "10," and replacing "$USER" with "steve" and "$HOME/edit/this/path/change_wallpaper_gnome3.sh" with "/home/steve/change_wallpaper_gnome3.sh." I used su - to get root access instead of sudo, so here's the command I used to set up the crontab:
# sh -c "echo \*/2 \* \* \* \* steve bash /home/steve/change_wallpaper_gnome3.sh >> /etc/crontab"
Well, it works, and it'll do for now until I find a really nice GUI automatic wallpaper changer for GNOME Shell that works in Fedora.
Since I was trying this in Fedora 16 (not in Ubuntu), I did a few things differently. I dropped some wallpapers into a directory called ~/wallpapers, extracted the script to my home directory, and within the script edited the following line to read:
wallpaper_dir="/home/steve/wallpapers/"
I edited his command for setting up the cron job, changing the time interval from "30" to "10," and replacing "$USER" with "steve" and "$HOME/edit/this/path/change_wallpaper_gnome3.sh" with "/home/steve/change_wallpaper_gnome3.sh." I used su - to get root access instead of sudo, so here's the command I used to set up the crontab:
# sh -c "echo \*/2 \* \* \* \* steve bash /home/steve/change_wallpaper_gnome3.sh >> /etc/crontab"
Well, it works, and it'll do for now until I find a really nice GUI automatic wallpaper changer for GNOME Shell that works in Fedora.
Tuesday, December 6, 2011
BCS :(
Boise State coach Chris Peterson made the point that when he's voting (in the USAToday coaches poll), "I'm trying to make the best case for Boise State to get in there ... I probably shouldn't be voting."
Which, of course, is what every coach would be doing.
And, how many coaches really know all that much about teams outside of their own conferences? These guys don't have time to watch many other teams play, other than their own upcoming opponents, or the teams they've played against, so what do they really know?
Why should the coaches poll carry so much weight, then?
As Peterson also said, the polls lack credibility when teams ranked in the top ten can't even get into a BCS bowl game. This year: Boise, Arkansas, Kansas State, and South Carolina, all ranked in the top ten in the AP poll, the USAToday, and the BCS standings, all left out of BCS bowl games. Instead: Michigan, Clemson, Virginia Tech, West Virgina -- none of them ranked in the top ten by anybody, all of them playing in BCS bowl games.
Maybe Peterson is gonna come across as a "whiner," but he makes some points that are pretty hard to argue with:
I think everybody is tired of the BCS ... Everybody's frustrated. Nobody really knows what to do anymore. It doesn't make sense to anybody. … I don't think anybody's happy anywhere.
...The whole thing needs to be changed, no question about it...
...Why are we voting at all if it doesn't really mean anything?...
...I haven't heard anyone saying, 'Hey, this is really good.' Nobody likes it. Nobody understands it. Everyone says it needs to be tweaked. Hopefully it will be.
http://www.usatoday.com/sports/college/football/story/2011-12-06/bcs-boise-state-petersen/51666700/1
Which, of course, is what every coach would be doing.
And, how many coaches really know all that much about teams outside of their own conferences? These guys don't have time to watch many other teams play, other than their own upcoming opponents, or the teams they've played against, so what do they really know?
Why should the coaches poll carry so much weight, then?
As Peterson also said, the polls lack credibility when teams ranked in the top ten can't even get into a BCS bowl game. This year: Boise, Arkansas, Kansas State, and South Carolina, all ranked in the top ten in the AP poll, the USAToday, and the BCS standings, all left out of BCS bowl games. Instead: Michigan, Clemson, Virginia Tech, West Virgina -- none of them ranked in the top ten by anybody, all of them playing in BCS bowl games.
Maybe Peterson is gonna come across as a "whiner," but he makes some points that are pretty hard to argue with:
I think everybody is tired of the BCS ... Everybody's frustrated. Nobody really knows what to do anymore. It doesn't make sense to anybody. … I don't think anybody's happy anywhere.
...The whole thing needs to be changed, no question about it...
...Why are we voting at all if it doesn't really mean anything?...
...I haven't heard anyone saying, 'Hey, this is really good.' Nobody likes it. Nobody understands it. Everyone says it needs to be tweaked. Hopefully it will be.
http://www.usatoday.com/sports/college/football/story/2011-12-06/bcs-boise-state-petersen/51666700/1
Subscribe to:
Posts (Atom)






