I agree - you have a point there - dunno how I missed the obvious - should've taken a detailed log on the events and put some feedback as in a bug report back to debian.org. I guess I still had some fever...or maybe it was a spontaneous act on my behalf ?
The Xorg is a very welcome feature indeed. Will you allow me to test this sarge -> etch on another machine and keep a log on what I do and what happens ? This way I could come up with a usable bug report, should the problem come up again. I'd like to see a fresh etch install and another case upgrading from existing sarge to etch.
When it comes to bug reporting, apparently I didn't have a clue;)
As I was recovering from a spring flu, I was bored enough and decided to upgrade from sarge to etch on my trusty old 600Mhz 256MB Compaq Deskpro. For the most part it went smooth and nice, but what amazes me is why the X stuff is still somewhat awkward. Hardware is certainly not bleeding edge. Maybe I'm just without a clue after a decade of professional multiplatform unix administration, but it sure beats me why X stuff still needs to be this clumsy - we're in year 2007, aren't we - ? Recently I installed two Dell 2900's at work and with Fedora FC6 it was surely as smooth as ever could be. Now someone jumps in and tells that 'Debian is not intended to be easy'. OK, but how is this intended to boost anyone's productivity to battle with stuff that was perhaps ok back in the early 90's ? Debian is such a stable (pun intended) and rock-solid platform to run servers on, I sure like it, but I'd like to see some minor refinements in getting wheels to roll.
Used to run sarge at work, used to set up sarge systems for friends small businesses and home use, but have since then moved on to Fedora due to these unnecessary issues. Beat the living daylight out of me but I just don't feel like attacking the xorg.conf or XF....conf with vi anymore "cool" these days. Especially on very common hardware.
Other than that, thanks for the debian folks for the release !
Slashdot Mirror
I agree - you have a point there - dunno how I missed the obvious - should've taken a detailed log on the events and put some feedback as in a bug report back to debian.org. I guess I still had some fever...or maybe it was a spontaneous act on my behalf ? The Xorg is a very welcome feature indeed. Will you allow me to test this sarge -> etch on another machine and keep a log on what I do and what happens ? This way I could come up with a usable bug report, should the problem come up again. I'd like to see a fresh etch install and another case upgrading from existing sarge to etch. When it comes to bug reporting, apparently I didn't have a clue ;)
As I was recovering from a spring flu, I was bored enough and decided to upgrade from sarge to etch on my trusty old 600Mhz 256MB Compaq Deskpro. For the most part it went smooth and nice, but what amazes me is why the X stuff is still somewhat awkward. Hardware is certainly not bleeding edge. Maybe I'm just without a clue after a decade of professional multiplatform unix administration, but it sure beats me why X stuff still needs to be this clumsy - we're in year 2007, aren't we - ? Recently I installed two Dell 2900's at work and with Fedora FC6 it was surely as smooth as ever could be. Now someone jumps in and tells that 'Debian is not intended to be easy'. OK, but how is this intended to boost anyone's productivity to battle with stuff that was perhaps ok back in the early 90's ? Debian is such a stable (pun intended) and rock-solid platform to run servers on, I sure like it, but I'd like to see some minor refinements in getting wheels to roll. Used to run sarge at work, used to set up sarge systems for friends small businesses and home use, but have since then moved on to Fedora due to these unnecessary issues. Beat the living daylight out of me but I just don't feel like attacking the xorg.conf or XF....conf with vi anymore "cool" these days. Especially on very common hardware. Other than that, thanks for the debian folks for the release !