blob: a1d6a58919903ff6a2db2ef8ba23cb728839f1be (
plain)
1
2
3
4
5
6
7
8
9
10
|
<br>2011/5/22 Juergen Harms <span dir="ltr"><<a href="mailto:Juergen.Harms@unige.ch">Juergen.Harms@unige.ch</a>></span><br><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br></div>
Would it be worth the while to draft a short Mdva 2010.2-to-Mageia1 migration memo (enumerating known problems, listing hardware where an update-install is not recommended; from my experience: suggest that customized<br>
kde user-environments might be re-done using "mv .kde4 sv_kde4)?<br></blockquote><div><br></div><div>I think this is an good idea.</div><div>I think an other problem is the replacement of the proprietary drivers (I had a prob with nvidia96)</div>
<div><br></div><div>Another point the the automatic for setting the repos.</div><div><br></div><div>Normally I install first from dvd, reboot, add repos and the do the update.</div><div>This seems not good for the upgrade.</div>
<div>Because without updating during the upgrade there are no repos set (only cd-rom)</div><div><br></div><div>The repos should be set independent from update during installation.</div><div><br></div><div>What hapens with plf repos? (I think each normal system has them)</div>
<div><br></div><div>The routine for setting the repos should look for plf and then activate tainted.</div><div><br></div><div>Perhaps generate an automatic "urpmi -qa | mdv /plf)" to get a standard file for missing packages.</div>
<div>So everyone can send it to <a href="http://mageia.org">mageia.org</a>.</div><div><br></div><div>In the evening a will test an upgrage of an komplete 2010.2 (with plf, some muldimedia stuff, proprietary GeForce) on an KDE x86_64 system.</div>
<div>I think rather near by an enviroments of an simple user.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><br></div>
|
