| 00:55.14 | *** join/#debianppc simonrvn (i=simon@unaffiliated/simonrvn) |
| 03:26.02 | *** join/#debianppc simonrvn (i=simon@unaffiliated/simonrvn) |
| 04:49.44 | *** join/#debianppc Vaidy (n=sv@59.92.196.51) |
| 06:25.38 | *** join/#debianppc Bryanstein (i=bryan@shellium/admin/bryanstein) |
| 09:10.23 | *** join/#debianppc Bryanstein (i=bryan@free.psybnc.and.eggdrop.at.shellium.org) |
| 09:28.57 | *** join/#debianppc lumis (n=jon@cpc1-leic7-0-0-cust236.lei3.cable.ntl.com) |
| 10:39.54 | *** join/#debianppc Vaidy (n=sv@122.248.163.1) |
| 11:20.52 | *** join/#debianppc mjt (n=mjt@isrv.corpit.ru) |
| 11:22.25 | mjt | Hello. Somewhat.. stupid question: Is an IBM p670 (power4, 64bit) a ppc machine? ;) |
| 11:23.26 | mjt | we've one of these (i know it's quite old but still powerful enough), it's running aix now, and I'm thinking about replacing aix with debian. |
| 11:27.46 | Bor_Ed | yup |
| 11:53.55 | *** join/#debianppc ctga-mg (n=weslei_c@200.243.11.180) |
| 11:54.25 | *** part/#debianppc ctga-mg (n=weslei_c@200.243.11.180) |
| 13:35.50 | *** join/#debianppc _Trinity_ (n=m0@pc-72-103-160-190.cm.vtr.net) |
| 14:29.28 | *** join/#debianppc Bryanstein (i=bryan@free.psybnc.and.eggdrop.at.shellium.org) |
| 15:32.24 | mjt | how does ppc machines boot over network? something like pxe with drivers? |
| 15:33.30 | Bor_Ed | tftpboot is possible from OF |
| 15:37.55 | mjt | oh |
| 15:38.20 | mjt | i'm trying to understand what to do with kvm (qemu) build for ppc |
| 15:38.52 | mjt | for x86 we're shipping pxe-*.bin ROMs |
| 15:40.09 | mjt | so it should be in the bios in qemu |
| 15:40.14 | Bor_Ed | http://ftp.nl.debian.org/debian/dists/lenny/main/installer-powerpc/current/images/ ready netboot images for ppc |
| 15:40.17 | mjt | (fsvo "bios") |
| 16:32.48 | *** join/#debianppc Vaidy (n=sv@59.92.137.172) |
| 17:34.36 | _Trinity_ | do I have to edit yaboot after installing a kernel from the repositorires? Or is it go to go next time I boot --choosable from the 2nd interactive interface? |
| 17:35.04 | Bor_Ed | it should be in the yaboot conf, check before reboot |
| 17:39.05 | _Trinity_ | will do, thanks |
| 18:57.35 | _Trinity_ | say,I'm reading here about pinning and wondering if a Jim's critique is correct on http://www.howtoforge.com/a-short-introduction-to-apt-pinning-p2 |
| 18:59.42 | _Trinity_ | he says stable shuold be 300, testing, 80 and unsatble 50 rather than 700, 650, 600 to prevent unwanted updaing of pinned programs. Can someone confirm his priority numbers |
| 18:59.43 | _Trinity_ | ? |
| 21:04.19 | *** join/#debianppc ctga-mg (n=weslei_c@200.243.11.180) |
| 21:04.37 | *** part/#debianppc ctga-mg (n=weslei_c@200.243.11.180) |
| 21:07.41 | simonrvn | um, the default is 50 for stuff like experimental, and local gets 100, so you want something higher than that.... |
| 21:28.20 | _Trinity_ | so the numbers suggested by the author are proably best |
| 21:29.48 | simonrvn | lemme see that first |
| 21:30.51 | _Trinity_ | http://www.howtoforge.com/a-short-introduction-to-apt-pinning-p2 |
| 21:33.07 | simonrvn | it's not the author but the comment ;). |
| 21:33.27 | simonrvn | and yeh, i'd go for that. i've set up something like that for my lenny box. |
| 21:34.01 | _Trinity_ | which look best? the commentartor's? |
| 21:34.36 | simonrvn | hm actually no, but that's a good idea nonetheless (comment) |
| 21:34.48 | simonrvn | you can always try it ;). |
| 21:35.02 | _Trinity_ | I sasume you liked the author's setup. And that's what i changed my settings ck to |
| 21:35.44 | simonrvn | the author's is the one i have - sorta. i use different numbers. |
| 21:36.12 | _Trinity_ | there's an interseting suggestion to have debian to try to fulfill deps with stable with apt-get install phpmyadmin/unstable. |
| 21:36.36 | _Trinity_ | and that is not at all what's popular, apt-get -t unstable install phpmyadmin |
| 21:36.39 | _Trinity_ | is |
| 21:36.40 | simonrvn | for instance, i have 998 or 999 for stuff like the various lenny-based repos, like backports and security |
| 21:37.20 | simonrvn | p-u (proposed-updates) gets 400 in mine |
| 21:37.53 | simonrvn | but, like the commentator said, you can get issues with versioning that way... |
| 21:38.42 | _Trinity_ | here let me psatbin whta I got |
| 21:39.40 | simonrvn | mine i set up years ago.. and i haven't really tweaked them properly since |
| 21:40.52 | _Trinity_ | http://debian.pastebin.com/d1b412ab1 |
| 21:42.07 | simonrvn | i'd lower testing and unstable below 500, and up backports to above 500 |
| 21:42.53 | simonrvn | stable is fine there |
| 21:43.39 | simonrvn | <PROTECTED> |
| 21:43.42 | simonrvn | <PROTECTED> |
| 21:44.10 | _Trinity_ | you're referring to the first set |
| 21:45.00 | simonrvn | see also te paragraph that starts with "In a typical situation,..." |
| 21:45.05 | simonrvn | the* |
| 21:48.32 | _Trinity_ | "in a typical" in http://www.howtoforge.com/a-short-introduction-to-apt-pinning-p2 ? |
| 21:49.06 | simonrvn | no, the manual |
| 21:49.11 | _Trinity_ | ll |
| 21:49.13 | _Trinity_ | lol |
| 21:59.16 | _Trinity_ | k ,I think I git something decent. I guess to respond to that commentator, one yuo got something working from Sid or even testing where things are changing all the time, you really shuld pin the actual program you want down after getting it working like you want |
| 22:00.03 | _Trinity_ | and thus avoid the type of problems he mentions |
| 22:02.13 | _Trinity_ | the thing that surprises me that most articles suggest the apt-get -t unstable install phpmyadmin format that dispells chances of trying to satisfy deps via stable and introduces and increases the likelyhood of breakage |
| 22:29.44 | simonrvn | no, that's not a practical solution. you should either tweak the numbers down or use hold |
| 22:29.55 | simonrvn | yes |
| 22:29.58 | simonrvn | !hold |
| 22:30.06 | simonrvn | !+hold |
| 22:30.08 | ravenbird | i guess hold is a status flag to tell apt not to automatically upgrade a package. apt will place packages on hold if they require packages that are not currently installable; you can 'apt-get install pkgname' to explicitly install the package. To put a package on hold, 'echo pkgname hold | dpkg --set-selections' or use the '=' key on the package in dselect, or 'echo pkgname install | dpkg --set-selections' to remove the hold |
| 23:44.43 | *** join/#debianppc tilmann_ (n=tilmann@p5B2F7764.dip.t-dialin.net) |