#debian - Fri 18 May 2007 between 06:56 and 07:04

NY Lost Funds



foowols: http://forums.viaarena.com/messageview.aspx?catid=60&threadid=73739&enterthread=y - if you can, read that last thread there. I think I'm on to something
wolscydork: http://www.mini-itx.com/store/?c=32
peterSowh: well, at minimum we _should_ have been able to manage "aptitude install aptitude" then "aptitude dist-upgrade". (i.e., upgrade aptitude first, then upgrade everything else with the new aptitude. it should be possible to work around any deficiencies in old tools that way. however, since we didn't notice the problems in time, we couldn't "fix" aptitude.)
owhpeterS: I would have advocated a process that stopped the upgrade dead in its tracks by doing some funky package.gz munching with a pre-inst scripted warning. That can still be implemented today. Too late for me, not for the next punter running a stable system.
cydorkwols: oooh that will be costly..
foowols: "
wols: "I think it is up to ECS to solve this issue. For you I can only say : try to use linux with avoid_D3 option. In my case it works for ECS P4M800PRO-M motherboard. "
wols: Hm, I found that in the forum. How the heck can I "use linux with avoid_D3" option... hmm, ok.
owhpeterS: All I can say is that this has severely dented my confidence in the process. An apt-get dist-upgrade should *always* work. If it is known that it won't then it should stop there. IMHO anyway :)
cydorkfoo: check modinfo via-rhaine ;)
foocydork: ah, ok
peterSowh: you misspelled 'aptitude dist-upgrade'. apt-get is no longer considered state of the art for this sort of thing
foocydork: oh, nice.
cydork: Hmmm
wolsfoo: either a patch or a driver parameter
however: this only happens with sleep modes and PXE it seems
foowols / cydork: parm: avoid_D3:Avoid power state D3 (work-around for broken BIOSes) (bool) ... nice, looks like it is already in there
Dianoraok
peterSfoo: since it's a driver parameter, that means you say "via-rhine avoid_D3=1" in /etc/modules
wolsnothing that applies to you, does it?
peterSfoo: or if you're loading the module manually: modprobe via-rhine avoid_D3=1
owhpeterS: I understand wols sentiment about shooting myself in the foot. It's a fair comment. I must confess that I have not been following debian processes for a while now. This machine had been running stable for a long time and all the sysadmin wanted to do is update their version of PHP4. The rest was just a disaster waiting to happen.
wolsowh: the problem all stems from the small word "stable" in sources.list
peterSowh: yeah I'm not the one to say nyah nyah you didn't rtfm you deserve a broken system. it's unfortunate that we couldn't provide a smooth upgrade using the usual 'aptitude dist-upgrade' path. best we can do now is document it, which we did ... but that doesn't make me feel good about the sarge->etch upgrade we provided
foopeterS: hmm, but, modinfo via-rhine|grep -i avoi returns parm: avoid_D3:Avoid power state D3 (work-around for broken BIOSes) (bool) ... so, it must have already been applied, right?
wolsbut there are tradeoffs either way, if you put in "stable" or "branch version name"
owhpeterS: Well if apt-get is not considered "state of the art", then it should do the same as "nslookup" did/does, write a notice: "This tool is depreciated."
peterSowh: wols is right, to avoid surprise upgrades in the future, you want to hardcode the branch name 'sarge' or 'etch' in sources.list, rather than 'stable'.
cydorkfoo: that's a module parameter you have to use what peterS said to enable it.
wolspeterS: there were worse upgrade in debian's history than this one :)=
owhwols: Yes, the word stable did it. Of course that was the default install :)
foocydork: ohhh, I see.
peterSwols: yeah but we've had better ones too. I was disappointed, but of course I also didn't do the upgrade testing that would have found this problem early enough to do something about it, so it's my fault as much as anyone's
foocydork / peterS : thanks, hopefully this does it. Going to try that
owhpeterS: I have changed all references from stable to etch, before I rebooted.
wolsowh: if one had put "sarge" in ther by default, it could break in a sligthyl different way, when one year from now, tons of people have an outdated, exploitable system since they never ugpraded to etch
peterSowh: right
wols: still, I think that's better than doing a routine upgrade (for security uploads or whatever) and suddenly getting etch
whether or not it's seamless (:
owhpeterS: That is *exactly* my point.

Page: 4 11 18 25 32 39 46 53 60 67 74 81 88 95 102 109 116 

IrcArchive

NY Lost Funds