Re: [gentoo-user] Now Know Why Portage Is So Slow
On Fri, 2006-05-26 at 20:23 +0100, Neil Bothwick wrote: On Fri, 26 May 2006 10:02:25 -0700, Lord Sauron wrote: you should try the ~x86 version of portage which has many improvements: $ echo sys-apps/portage ~x86 /etc/portage/package.use $ emerge portage Just a question, but there's got to be a reason why it's still in ~x86. Yes, it's less than 30 days old. ~arch does not mean unstable, it means still-in-testing. In fact, since portage is on a continuous update-and-improvement move, it will _always_ have a version in ~x86. I run completely ~x86, and even unmask some hard-masked packages (like gnome-2.14 used to be) manually, and I haven't had any major issues. The secret is to update regularly. If you run ~x86 and update monthly or less frequently, you run the risk of multiple problems snowballing on you. Nevertheless, if you have any reason to keep your system stable, standard disclaimer applies: stay away from ~x86. Just cause it works for me, doesn't mean it always will. cya, -- Iain Buchanan iaindb at netspace dot net dot au Whip me. Beat me. Make me maintain AIX. -- Stephan Zielinski -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
Forgive my ignorance, but what is RSYNC? http://en.wikipedia.org/wiki/Rsync basically, portage use rsync to update the information on packages (ebuilds) in /usr/portage (with emerge --sync) If anything, this is a indicator that I need to try and contribute to the portage project... at least contribute as much as I'm able. you should try the ~x86 version of portage which has many improvements: $ echo sys-apps/portage ~x86 /etc/portage/package.use $ emerge portage you should also know that there is an alternative package manager which will maybe replace portage in the future: paludis. It is still in early development so use it at your own risk. http://paludis.berlios.de/ you can find more info on portage on the new gentoo development guide: http://devmanual.gentoo.org/ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
oops there was a little typo: $ echo sys-apps/portage ~x86 /etc/portage/package.use should be: $ echo sys-apps/portage ~x86 /etc/portage/package.keywords -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
On 5/25/06, Daniel da Veiga [EMAIL PROTECTED] wrote: On 5/25/06, Iain Buchanan [EMAIL PROTECTED] wrote: On Thu, 2006-05-25 at 18:20 -0300, Daniel da Veiga wrote: Anyway, the OP is using genkernel (wether it likes/knows it or not)... This doesn't look like genkernel: It doesn't have to look, he used the Gentoo installer, and so, it IS GENKERNEL. It's not genkernel. I don't use genkernel. I do *not* like genkernel. I loaded the configuration file from my old kernel and then just make make install to use genkernel, you have to call genkernel. If he's typing make make install, then he's just using the plain old kernel makefile. That if you do a manual install, the installer use it, or better, if you choose it will use the same kernel as the livecd, that is, voilá, genkernel. Try it, its pretty cool. Most settings from the original install are gone because I'm pretty nuts about customizing things. -- == GCv3.12 == GCS d-(++) s+: a? C++ UL+ P+ L++ E--- W+(+++) N++ o? K? w--- O? M+ V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+ DI+++ D+ G e* h- !r !y = END GCv3.12 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
On 5/26/06, leszek [EMAIL PROTECTED] wrote: Forgive my ignorance, but what is RSYNC? http://en.wikipedia.org/wiki/Rsync basically, portage use rsync to update the information on packages (ebuilds) in /usr/portage (with emerge --sync) If anything, this is a indicator that I need to try and contribute to the portage project... at least contribute as much as I'm able. you should try the ~x86 version of portage which has many improvements: $ echo sys-apps/portage ~x86 /etc/portage/package.use $ emerge portage Just a question, but there's got to be a reason why it's still in ~x86. -- == GCv3.12 == GCS d-(++) s+: a? C++ UL+ P+ L++ E--- W+(+++) N++ o? K? w--- O? M+ V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+ DI+++ D+ G e* h- !r !y = END GCv3.12 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
On Fri, 26 May 2006 10:02:25 -0700, Lord Sauron wrote: you should try the ~x86 version of portage which has many improvements: $ echo sys-apps/portage ~x86 /etc/portage/package.use $ emerge portage Just a question, but there's got to be a reason why it's still in ~x86. Yes, it's less than 30 days old. ~arch does not mean unstable, it means still-in-testing. -- Neil Bothwick WinErr 014: Keyboard locked - Try anything you can think of. signature.asc Description: PGP signature
Re: [gentoo-user] Now Know Why Portage Is So Slow
On 5/25/06, Lord Sauron [EMAIL PROTECTED] wrote: I think I may have made a break through here! I've always noticed that everything portage is very slow. It's like it's having to un-tar and un-bzip everything all the time... lo and behold, it is. No, it is not. I've found (after much exploration) that there is a archive: /portage-20060123.tar.bz2 Simply a portage snapshot, maybe the one you used to install Gentoo in the first place? Take a look at the date and tell me I'm wrong. This has - to the best of my knowledge - all the ebuild headers or whatever for everything. I know I can un-tar this and all, however, I want portage to use it in its uncompressed state, just to speed things up. I'm not burning for hard drive space, so a little more speed would be great. Of course, it is a portage snapshot, it has a whole compressed portage tree, used to install, or update portage when using alternative methods for those (like me) that lack the capacity to use remote RSYNC. However, I have no idea where to start to try and configure portage to reflect a change like this. I've read the man pages for ebuild and emerge several times over without finding any hints, so I was thinking someone on this list would know. There's no change and there's no such feature. If you take a look at /usr/portage, you'll notice that is has all portage related stuff there, a snapshot is decompressed there when you install (correct me if I'm wrong, but you installed using the Gentoo Installer, didn't you? if you had a complete experience of Gentoo install, you would know that by now, that's why I strongly advice new users to AVOID THE INSTALLER). If you sync once in a while, it is updated. Portage is not kept compressed. I also think that there's another file, /metadata.tar.bz2, which I think is portage-related. If possible I'd like to uncompress that as well. Oh, this one was a good choice, metadata is used by portage, but if you take a look at /usr/portage/metadata, it is uncompressed there too, and that is what portage uses. I think this is the cause of a slow portage because everything takes a long time to start going, then it's just fine. It takes about as long to start going as it does to open the archive /portage-20060123.tar.bz2 - conincidence? I think not! But it is. That's because of caching, not because it uncompress everything every time and compress it again later, that would be stupid (forgive my language). I also get the bonehead award: there was a new kernel sitting on my hard drive and just yesterday I found and installed it. It was remarkably easy to install! I loaded the configuration file from my old kernel and then just make make install and it worked! I didn't even have to edit /boot/grub/menu.lst! Dang... I got done and said that was easy. I think I'm really getting the hang of all this! You have run an emerge -u world and it got the kernel sources, you have no special needs and so the default configuration fit your need, compiling kernels is EASY, making them work, that's a hard one. You sincerely must be booting from your old kernel and your /usr/src/linux link must be pointing at your old sources, else you would have some problems and probably would have to recompile, reconfigure some stuff, because after make and all, you should copy the image to /boot and, if necessary, change the grub.conf (menu.lst) to point at the right file. See the Kernel upgrade guide at Gentoo.org for more info. -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
On 5/25/06, Steven Susbauer [EMAIL PROTECTED] wrote: On Thu, 25 May 2006, Daniel da Veiga wrote: I also get the bonehead award: there was a new kernel sitting on my hard drive and just yesterday I found and installed it. It was remarkably easy to install! I loaded the configuration file from my old kernel and then just make make install and it worked! I didn't even have to edit /boot/grub/menu.lst! Dang... I got done and said that was easy. I think I'm really getting the hang of all this! You have run an emerge -u world and it got the kernel sources, you have no special needs and so the default configuration fit your need, compiling kernels is EASY, making them work, that's a hard one. You sincerely must be booting from your old kernel and your /usr/src/linux link must be pointing at your old sources, else you would have some problems and probably would have to recompile, reconfigure some stuff, because after make and all, you should copy the image to /boot and, if necessary, change the grub.conf (menu.lst) to point at the right file. See the Kernel upgrade guide at Gentoo.org for more info. I don't know what the default grub.conf is for the Gentoo installer, but It points at a kernel named as Genkernel does. if it points to /boot/vmlinuz then make install is sufficient to install That's why I know it isn't pointing at vmlinuz, because the installer (and thus, the OP) uses genkernel. the new, working kernel... it rewrites symlinks to the new kernel. BTW, Only if you specifically do a USE=symlink emerge gentoo-sources he copied the config from his old kernel, it is not using the default options and thus *should* work just fine. Yeah, I missed that line. You're right. But he didn't installed the new kernel, and alsa-driver, ndiswrapper, nvidia drivers and a lot of other stuff claim a new compile after a kernel upgrade, I doubt it would be as clean as the OP stated. But yeah, it may happen. -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
On Thu, 25 May 2006 17:33:47 -0300, Daniel da Veiga wrote: the new, working kernel... it rewrites symlinks to the new kernel. BTW, Only if you specifically do a USE=symlink emerge gentoo-sources No, that controls the /usr/src/linux symlink to the sources. The /boot/vmlinuz symlink is created when you make install the kernel. -- Neil Bothwick COBOL: (n.) an old computer language, designed to be read and not run. Unfortunately, it is often run anyway. signature.asc Description: PGP signature
Re: [gentoo-user] Now Know Why Portage Is So Slow
On 5/25/06, Neil Bothwick [EMAIL PROTECTED] wrote: On Thu, 25 May 2006 17:33:47 -0300, Daniel da Veiga wrote: the new, working kernel... it rewrites symlinks to the new kernel. BTW, Only if you specifically do a USE=symlink emerge gentoo-sources No, that controls the /usr/src/linux symlink to the sources. The /boot/vmlinuz symlink is created when you make install the kernel. Hmm, I see. Thanks for the info. Anyway, the OP is using genkernel (wether it likes/knows it or not)... -- Neil Bothwick COBOL: (n.) an old computer language, designed to be read and not run. Unfortunately, it is often run anyway. *lol* Gotta send that out to my friends that are COBOL lovers... -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
On Thu, 2006-05-25 at 18:20 -0300, Daniel da Veiga wrote: Anyway, the OP is using genkernel (wether it likes/knows it or not)... This doesn't look like genkernel: I loaded the configuration file from my old kernel and then just make make install to use genkernel, you have to call genkernel. If he's typing make make install, then he's just using the plain old kernel makefile. -- Iain Buchanan iaindb at netspace dot net dot au There is not much to choose between a woman who deceives us for another, and a woman who deceives another for ourselves. -- Augier -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
he copied the config from his old kernel, it is not using the default options and thus *should* work just fine. Yeah, I missed that line. You're right. But he didn't installed the new kernel, and alsa-driver, ndiswrapper, nvidia drivers and a lot of other stuff claim a new compile after a kernel upgrade, I doubt it would be as clean as the OP stated. But yeah, it may happen. alsa could easily be built into the kernel, I know when I install a new kernel it is as easy as running make and make install, and re-emerging the nvidia-kernel if I'm using it. AFAIK this person didn't say anything about alsa, nvidia, ndiswrapper, etc. etc. A kernel compile compile and install is precisely as easy as the OP stated. make make install (make modules_install) is all it takes, if you're pointing at /boot/vmlinuz. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
On 5/25/06, Iain Buchanan [EMAIL PROTECTED] wrote: On Thu, 2006-05-25 at 18:20 -0300, Daniel da Veiga wrote: Anyway, the OP is using genkernel (wether it likes/knows it or not)... This doesn't look like genkernel: It doesn't have to look, he used the Gentoo installer, and so, it IS GENKERNEL. I loaded the configuration file from my old kernel and then just make make install to use genkernel, you have to call genkernel. If he's typing make make install, then he's just using the plain old kernel makefile. That if you do a manual install, the installer use it, or better, if you choose it will use the same kernel as the livecd, that is, voilá, genkernel. Try it, its pretty cool. -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
On 5/25/06, Steven Susbauer [EMAIL PROTECTED] wrote: he copied the config from his old kernel, it is not using the default options and thus *should* work just fine. Yeah, I missed that line. You're right. But he didn't installed the new kernel, and alsa-driver, ndiswrapper, nvidia drivers and a lot of other stuff claim a new compile after a kernel upgrade, I doubt it would be as clean as the OP stated. But yeah, it may happen. alsa could easily be built into the kernel, I know when I install a new kernel it is as easy as running make and make install, and re-emerging the nvidia-kernel if I'm using it. AFAIK this person didn't say anything about alsa, nvidia, ndiswrapper, etc. etc. A kernel compile compile and install is precisely as easy as the OP stated. make make install (make modules_install) is all it takes, if you're pointing at /boot/vmlinuz. But he isn't because he used the installer and thus use genkernel, hmm, its like the third time I'll say that, so, I'll stop and report you all to read the complete thread. -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
On 5/25/06, Daniel da Veiga [EMAIL PROTECTED] wrote: But he isn't because he used the installer and thus use genkernel, hmm, its like the third time I'll say that, so, I'll stop and report you all to read the complete thread. It doesn't really matter how many times you say it, the OP did *not* use genkernel to install his _new_ kernel. He quite explicitly said make make install. He *may* have unwittingly used genkernel when he first installed his system, but he definitely didn't upgrade with it. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
On Thu, 2006-05-25 at 23:50 -0300, Daniel da Veiga wrote: On 5/25/06, Iain Buchanan [EMAIL PROTECTED] wrote: On Thu, 2006-05-25 at 18:20 -0300, Daniel da Veiga wrote: Anyway, the OP is using genkernel (wether it likes/knows it or not)... This doesn't look like genkernel: It doesn't have to look, he used the Gentoo installer, and so, it IS GENKERNEL. I loaded the configuration file from my old kernel and then just make make install to use genkernel, you have to call genkernel. If he's typing make make install, then he's just using the plain old kernel makefile. That if you do a manual install, the installer use it, or better, if you choose it will use the same kernel as the livecd, that is, voilá, genkernel. Try it, its pretty cool. Yes, the initial install seems to be from the installer, which would have used genkernel to build a kernel. BUT he then typed make make install himself, rebooted, and voila, he is not using genkernel any more. -- Iain Buchanan iaindb at netspace dot net dot au The first condition of immortality is death. -Stanislaw Lec -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Now Know Why Portage Is So Slow
On 5/25/06, Daniel da Veiga [EMAIL PROTECTED] wrote: On 5/25/06, Lord Sauron [EMAIL PROTECTED] wrote: I've found (after much exploration) that there is a archive: /portage-20060123.tar.bz2 Simply a portage snapshot, maybe the one you used to install Gentoo in the first place? Take a look at the date and tell me I'm wrong. Okay, the date is when I installed Gentoo. You're right. This has - to the best of my knowledge - all the ebuild headers or whatever for everything. I know I can un-tar this and all, however, I want portage to use it in its uncompressed state, just to speed things up. I'm not burning for hard drive space, so a little more speed would be great. Of course, it is a portage snapshot, it has a whole compressed portage tree, used to install, or update portage when using alternative methods for those (like me) that lack the capacity to use remote RSYNC. Forgive my ignorance, but what is RSYNC? However, I have no idea where to start to try and configure portage to reflect a change like this. I've read the man pages for ebuild and emerge several times over without finding any hints, so I was thinking someone on this list would know. There's no change and there's no such feature. If you take a look at /usr/portage, you'll notice that is has all portage related stuff there, a snapshot is decompressed there when you install (correct me if I'm wrong, but you installed using the Gentoo Installer, didn't you? if you had a complete experience of Gentoo install, you would know that by now, that's why I strongly advice new users to AVOID THE INSTALLER). If you sync once in a while, it is updated. Portage is not kept compressed. Yeah, well this new Gentoo user wouldn't have gotten past partitioning my hard drive without the installer. I know it does let less experience people - like myself - into the community of vastly more experienced Gentoo users, however, I also think it's been a great tool for learning more about Linux. I also think that there's another file, /metadata.tar.bz2, which I think is portage-related. If possible I'd like to uncompress that as well. Oh, this one was a good choice, metadata is used by portage, but if you take a look at /usr/portage/metadata, it is uncompressed there too, and that is what portage uses. So any portage slowness now is just because... yeah, I really should look into this, because I see no reason why portage should be running as slow as it is. I think this is the cause of a slow portage because everything takes a long time to start going, then it's just fine. It takes about as long to start going as it does to open the archive /portage-20060123.tar.bz2 - conincidence? I think not! But it is. That's because of caching, not because it uncompress everything every time and compress it again later, that would be stupid (forgive my language). I also get the bonehead award: there was a new kernel sitting on my hard drive and just yesterday I found and installed it. It was remarkably easy to install! I loaded the configuration file from my old kernel and then just make make install and it worked! I didn't even have to edit /boot/grub/menu.lst! Dang... I got done and said that was easy. I think I'm really getting the hang of all this! You have run an emerge -u world and it got the kernel sources, you have no special needs and so the default configuration fit your need, compiling kernels is EASY, making them work, that's a hard one. It booted, so I'm perfectly happy. It's spitting out coldplug errors right now, so I'm going to be hammering out some more settings, but it still boots and runs just fine, so I can't complain. You sincerely must be booting from your old kernel and your /usr/src/linux link must be pointing at your old sources, else you would have some problems and probably would have to recompile, reconfigure some stuff, because after make and all, you should copy the image to /boot and, if necessary, change the grub.conf (menu.lst) to point at the right file. I ran make make install. I'm absolutely positive I'm running the new kernel because I've looked in /boot and it's there, and I've looked to check which kernel is actually running and it's the new one. The symlink in /usr/src is still pointing to the old kernel because I haven't bothered to change that yet, but I'll do it very soon. Especially since I gave in and unmasked YaKuake. I love Yakuake! See the Kernel upgrade guide at Gentoo.org for more info. I think I got it right the first time, which is ample reason for celebration as far as I'm concerned. -- == GCv3.12 == GCS d-(++) s+: a? C++ UL+ P+ L++ E--- W+(+++) N++ o? K? w--- O? M+ V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+ DI+++ D+ G e* h- !r !y = END GCv3.12 -- gentoo-user@gentoo.org mailing list
