[gentoo-user] how to recompile
Salut, made a mistake during portage-update (make.conf). And now i compiled my KDE with i686 and not i586. Is it enough to delete the succesfull in /var/tmp/portage//Temp ?? Next problem: while compling KDE I ran out of disc space, after cleaning up (had a 1,5 G Image to move) KDE compiling finished good. But I found in KDEEdu-3.1.2 ( where run out of disc space, while compiling) too much dirs and two files .compiled and .unpacked . Charlie -- [EMAIL PROTECTED] mailing list
[gentoo-user] initrd
Salut, run now a gentoo 1.4 startet with stage 3. Look up for the way to make it running with a initrd. Is there a script to build one ? Where ? amicalement Charlie -- [EMAIL PROTECTED] mailing list
[gentoo-user] initrd (comming again)
Salut, run now a gentoo 1.4 startet with stage 3. Look up for the way to make it running with a initrd. Is there a script to build one ? Where ? a Howdo ? amicalement Charlie -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] initrd (comming again)
Hi Charlie, Am Freitag, 27. Juni 2003 21:02 schrieb Charlie: run now a gentoo 1.4 startet with stage 3. Look up for the way to make it running with a initrd. Is there a script to build one ? Where ? there was a thread "mkinitrd" on Thu, 26 Jun 2003 13:29:26 -0400 started by "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> with the Message-ID: <[EMAIL PROTECTED]>. Please check your archive. -- PLEASE where is the archiv Kai -- [EMAIL PROTECTED] mailing list
[gentoo-user] emerge accident
Salut , during emerge kde after an emerge -f kde (unsing a modem) I found a froozen gentoo box when I came back. I had to restart . Now if I want to emerge , i'v get the attachet message. The hole systen dit not find any lib it seams. Can anbodey help me , or have I to start at untar stage3 ? amicalement Charlie python2.2: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge accident
--- The missing lib is part of GCC. `env-update` should fix things. Zack Gilburd All I started 'env-update', 'mc', 'wvdial'. All can't find there LIB But I found them all in /usr/lib/gcc-lib/i586-pc-linux-gnu/3.2.2 Any Idea Thanks Charlie -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge accident
Charlie schrieb: --- The missing lib is part of GCC. `env-update` should fix things. Zack Gilburd All I started 'env-update', 'mc', 'wvdial'. All can't find there LIB But I found them all in /usr/lib/gcc-lib/i586-pc-linux-gnu/3.2.2 Any Idea Thanks Charlie Salut, finaly, knowing that I have nomore to lose (to know it is a new installation, with no data to lose), I had two plans: 1. untar a state over it. 2. make a ldconfig, what is not usual on gentoo I think. I started with the ldconfig and dit a env-update after. And it worked. All progs refind there LIB-Files, and I coulde finish my emerge kde. I don't know why the maschine lost the path to the g++ libpath ? Even I don't know howe the accident arrived. I thing my motherboard has a problem if it gets to hot ( since yesterday summer has a break here in germany and we don't have the 30 °C like the last 4 weeks passed), because if the box ran for a while and I restart here, it hangs . I can't even enter to the cmos, without shut here down for some minutes. Charlie -- [EMAIL PROTECTED] mailing list
[gentoo-user] need some help for
Salut, after installing gentoo on my test-box .I started to change from SuSE to gentoo on my productiv-box. Haveing some troubles thas normal, wrong masked protage, cflags etc. Used till now -athlon-mp -03 -pipe But now with cflags I have a big trouble, perhapes not with cflags, but with my box. Let me tell you. Everything runs fine, but allways there were a drak shadow thrown by hanging maschine. So I redived into cpu-type and cflags. I found by typing cat /proc/cpuinfo the attached result, and it is strange for me. My motherboard is a Tyan S2462 Thunder K7 with two Cpu (Athlon MP I thought) The Output says not. ??? is it the Linux Hardware-detection or my dealer who failed ?? Till now with SuSE 7.2 the box ran fine. Thanks for all help Charlie processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 6 model name : AMD Athlon(tm) MP stepping: 1 cpu MHz : 1194.763 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow bogomips: 2378.95 processor : 1 vendor_id : AuthenticAMD cpu family : 6 model : 6 model name : AMD Athlon(tm) Processor stepping: 1 cpu MHz : 1194.763 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow bogomips: 2385.51 -- [EMAIL PROTECTED] mailing list
[gentoo-user] need some hlep for
Salut, after installing gentoo on my test-box .I started to change from SuSE 7.2 to gentoo on my productiv-box. Haveing some troubles thats normal, wrong masked protage, cflags etc. Used till now -athlon-mp -03 -pipe But now with cflags I have a big trouble, perhapes not with cflags, but with my box. Let me tell you. Everything runs fine, but allways there were a drak shadow thrown by hanging maschine. So I redived into cpu-type and cflags. I found by typing cat /proc/cpuinfo the attached result, and it is strange for me. My motherboard is a Tyan S2462 Thunder K7 with two Cpu (Athlon MP I thought) The Output says not. ??? is it the Linux Hardware-detection or my dealer who failed ?? Till now with SuSE 7.2 the box ran fine with a SMP-Kernel. Thanks for all help Charlie processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 6 model name : AMD Athlon(tm) MP stepping: 1 cpu MHz : 1194.763 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow bogomips: 2378.95 processor : 1 vendor_id : AuthenticAMD cpu family : 6 model : 6 model name : AMD Athlon(tm) Processor stepping: 1 cpu MHz : 1194.763 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow bogomips: 2385.51 -- [EMAIL PROTECTED] mailing list
[gentoo-user] Re :mozilla mail not working
Ever since I emerged mozilla 1.4 the mail component has stopped working. I cannot send or receive messages. I am sending this from my debian sarge. Are bothe users the same ID ? Dit it work before ? The debian mozilla package is version Mozilla Debian Package did this so that whichever OS is active I can see any email received. Prior to the 1.4 emerge everything worked as planned. Do I need to downgrade gentoo mozilla? And the real bonehead question: How would I downgrade? Tom Stoddard -- [EMAIL PROTECTED] mailing list
[gentoo-user] nothing to do with gentoo, but a problem for me
Salut, here you see my diskspace made with df -h , the problem is my /root it shows me only 18M available, but with 'du' it must be about 300 M, I made it the 'du' also for the other partitions and it is OK. Has anybody a hint for me. I logged in with a Knoppix and can't find nothing which explaint the lost 30M. df -h FilesystemSize Used Avail Use% Mounted on /dev/sda112.0G 2.0G 18M 100% / /dev/sda5 30M 8.3M 20M 29% /boot /dev/sda123.0G 2.0G 1.0G 64% /usr /dev/sda133.0G 1.1G 1.9G 35% /opt /dev/sda141.0G 505M 522M 50% /home /dev/sda15 10G 4.0G 6.0G 40% /vmware shmfs1006M 0 1006M 0% /dev/shm . in root making du -h -m -x -s 1705 cd /boot du -h -m -x -s 9 . cd /home du -h -m -x -s 489 . cd /opt du -h -m -x -s . cd /usr du -h -m -x -s 2154. Charlie -- [EMAIL PROTECTED] mailing list
[gentoo-user] hat nichts mit gentoo zu tun, aber ist ein Problem für mich
Salut, hier seht ihr meinen Plattenplatz (mit df -h), das problem ist die /root partition, sie zeigt nur 18 MB. Aber mit 'du' sind es 300 MB. Ich habe den 'du' auf die anderen Partitionen zum vergleich gefahren, und die scheinen OK. Hat jemand eine Idee ? Ich hab mir das auch schon mit Knoppix angeschaut, aber nichts gefunden was die fehlenden 280 MB erklären könnten. df -h FilesystemSize Used Avail Use% Mounted on /dev/sda112.0G 2.0G 18M 100% / /dev/sda5 30M 8.3M 20M 29% /boot /dev/sda123.0G 2.0G 1.0G 64% /usr /dev/sda133.0G 1.1G 1.9G 35% /opt /dev/sda141.0G 505M 522M 50% /home /dev/sda15 10G 4.0G 6.0G 40% /vmware shmfs1006M 0 1006M 0% /dev/shm . in root making du -h -m -x -s 1705 cd /boot du -h -m -x -s 9 . cd /home du -h -m -x -s 489 . cd /opt du -h -m -x -s . cd /usr du -h -m -x -s 2154. Charlie -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] nothing to do with gentoo, but a problem for me
On Mon, 22 Sep 2003 16:05:12 -0700 Anthony Floyd <[EMAIL PROTECTED]> wrote: On Mon, 22 Sep 2003 23:54:54 +0200 Charlie <[EMAIL PROTECTED]> wrote: > Salut, > > here you see my diskspace made with df -h , the problem is my /root > it shows me only 18M available, but with 'du' it must be about 300 > M, I made it the 'du' also for the other partitions and it is OK. > Has anybody a hint for me. From the ext3 FAQ (http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html): Q: 'df' command says partition is full, while 'du' reports free space Theodore Ts'o, the ext2 developer, said: The standard cause for this is some user process keeping a deleted file open. To find the process in question, heres a trick using "lsof" (do it as root ) /usr/sbin/lsof -n |grep delete - HTH, HAND //Spider Thanks for the lsof, but he ditn't find any big file. So some more details. FS is ReiserFs. I'v got a ' no more Diskspace ' while coping with a wrong destination That was at a time where the system wasn't mountet correcly. Had insert a new SCSI disk between scda and scdb, so scdb moved to scdc and after mounting all this I meant to copy from scdc5 to scdb5 and scda11 had no more diskspace, I could free 20 M from /tmp After no finding the big one , I shut down and had a look with Knoppix but could find anything. Charlie -- [EMAIL PROTECTED] mailing list
RE: [gentoo-user] Problem with 2004.3-r1 universal live cd image
Been there too :( Really, boot a memtest86 kernel and test your hw. #emerge memtest86 Don't remember if there is any memtest-option on the LiveCD...? Cheers! /C -Original Message- From: Kevin [mailto:[EMAIL PROTECTED] Sent: 9 januari 2005 17:10 To: [EMAIL PROTECTED] Subject: [gentoo-user] Problem with 2004.3-r1 universal live cd image Hi All- I'm having some installation problems that are associated with the subject CD image: install-x86-universal-2004.3-r1.iso I recently downloaded and burned this iso image to CD. I checked the gpg signature and md5sum before and after burning and they were both ok. On two very different hardware platforms, I've used this image to install Gentoo systems and either during or after installation (or both), I've seen these problems: Various "emerge -v X" commands have failed with segfaults and messages along the lines of, "...not reproducible so probably hardware or OS related...". In one case, even the tar -xvjpf stage3-... command segfaulted. I managed to get it to complete after several tries and by removing the "-v" flag (for some odd reason, the "-v" definitely has an impact on whether or not segfaults occur on both boxes with either tar or emerge). In this case (with the tar files), I md5sum'ed the stage3 bzipped tarfiles and they were ok, but bzip2 -vvt reported integrity problems (with the one I wanted and all the others on the CD also, except for one of them). Later, running bzip2 -vvt reported no integrity problems, so I went ahead with the tar -xjpf command without problem. Clearly, something is inherently unstable here because running the same command (bzip2 -vvt) on the same file stage3-whatever fails at one point in time and succeeds at another (no reboot in between). I've also seen kernel Oops and kernel panics. The two hardware platforms were: 1) An eMachines T2824 desktop computer. Specifications: -Intel Celeron D 325 Processor (2.53 GHz, 256k L2 Cache, 533 MHz FSB); -Intel 845GV Chipset -8-in-1 Digital Media Manager (USB 2.0, Secure Digital (SD), Smart Media, Compact Flash, Memory Stick, Memory Stick PRO, Micro Drive, Multimedia Card) -standard 256 MB DDR (PC 2100) RAM replaced with 1024 MB of same -http://www.emachines.com/support/support_info.html?prodName=T2824 for others if you're interested. I used the stage3-pentium4 tarfile for this. I'm really not sure if that's right or if I should be using one of the others (i686? pentium3? x86? With Celeron processors, how does one decide which CFLAGS and binaries to use?). I chose pentium4 because memtest86+ v1.11 reported the CPU as a pentium4 and I've seen some hints that some Celeron processors are "Pentium-4 flavors." 2) A very old Cyrix 6x86 with 132 MB RAM, using the stage3-x86 tarfile. I have run memtest86 and memtest86+ on both boxes (at least 10 passes each) and discovered no errors with the memory in either case. Interestingly (at least to me), memtest86+ v1.3 reports FSB at 133 MHz rather than 533 MHz. Could this be a clue as to the cause of the problems? Does anyone have any thoughts on what's causing this strange behavior? I installed first on the eMachines box and suspected hardware problems, but the segfaults were not so frequent that I could not proceed, so whenever I encountered one, I just ran the command again until it completed successfully and figured I could troubleshoot the hardware more later, after the base install. But now that I've seen the same sorts of problems on this Cyrix 6x86 CPU, I'm less inclined to think hardware problems and more inclined to think that there may be some problem with the software on the subject iso image. Has anyone else encountered this? Any ideas as to what else could be the problem if not the memory? As I said, the md5sum is fine on the cd image, the cd itself, and various tar files on the cd. Is there another hardware component that could be causing this (aside from the memory). TIA for any thoughts. -Kevin -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
RE: [gentoo-user] WiFi success story :|
Try: 'ACCEPT_KEYWORDS="~x86" emerge -Dv ipw2200' /©harlie On Wed, January 12, 2005 8:25, Schafer Frank said: > ipw2200 is masked by ~x86 keyword. How did you unmask it? I've tried to > put wpa_supplicant to package.unmask too and it remains masked. > > ... but anyway, thanks for the hint. > > Frank > > -Original Message- > From: Martin Büchler [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 11, 2005 4:46 PM > To: [EMAIL PROTECTED] > Subject: Re: [gentoo-user] WiFi success story :| > > unmask ipw2200, then there is no need for building the driver yourself. > > i've got it here on my laptop, and it works like a charm. (asus travelmate > 6002lmi, kernel 2.6.9) > > mfg martin > > On Tue, 11 Jan 2005 09:35:01 -0700 (MST), Ric Messier <[EMAIL PROTECTED]> > wrote: >> >> On Tue, 11 Jan 2005, Ric Messier wrote: >> >> > >> > On Tue, 11 Jan 2005, Schafer Frank wrote: >> > >> >> >> >> What will I have to do to change from simpleinit to sysv init? >> >> Would it be sufficiennt to emerge sysv? Will I have to unmerge >> >> simpleinit? I'd like to have my initscripts #!/bin/sh. >> >> >> > >> > Is that the only reason you want a SysV init? A bit odd, especially >> given: >> > >> >> Thinking about this further, I'm even less sure about the problem you >> are trying to solve. You might check to see whether sysvinit is >> already installed as I seem to recall it's part of the base system. I >> know it's installed on my system and I never asked for it explicitly. >> >> Ric >> >> -- >> gentoo-user@gentoo.org mailing list >> >> > > -- > gentoo-user@gentoo.org mailing list > > > > > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
RE: [gentoo-user] WiFi success story :|
I disagree, when dealing with a ~x86-package it might have deep-dependencies that is also in ~x86. I also disagree on package.keywords since it's better to test if emerge goes well and that module actually works before making any static changes regarding keywords or even USE- & FEATURES-flags for that matter. /©harlie On Wed, January 12, 2005 10:37, Eugene Rosenzweig said: > I dont like using ACCEPT_KEYWORDS, it makes emerge try and install all > sorts of packages > with -D option. Better way is to put > > net-wireless/ipw2200 ~x86 > > line into /etc/portage/package.keywords. > > See portage manpage for more info. > > Eugene. > >> -Original Message- >> From: Charlie Gehlin [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, 12 January 2005 7:58 PM >> To: [EMAIL PROTECTED] >> Subject: RE: [gentoo-user] WiFi success story :| >> >> Try: >> >> 'ACCEPT_KEYWORDS="~x86" emerge -Dv ipw2200' >> >> /©harlie >> >> On Wed, January 12, 2005 8:25, Schafer Frank said: >> > ipw2200 is masked by ~x86 keyword. How did you unmask it? I've tried >> to >> > put wpa_supplicant to package.unmask too and it remains masked. >> > >> > ... but anyway, thanks for the hint. >> > >> > Frank >> > >> > -Original Message- >> > From: Martin Büchler [mailto:[EMAIL PROTECTED] >> > Sent: Tuesday, January 11, 2005 4:46 PM >> > To: [EMAIL PROTECTED] >> > Subject: Re: [gentoo-user] WiFi success story :| >> > >> > unmask ipw2200, then there is no need for building the driver >> yourself. >> > >> > i've got it here on my laptop, and it works like a charm. (asus >> travelmate >> > 6002lmi, kernel 2.6.9) >> > >> > mfg martin >> > >> > On Tue, 11 Jan 2005 09:35:01 -0700 (MST), Ric Messier >> <[EMAIL PROTECTED]> >> > wrote: >> >> >> >> On Tue, 11 Jan 2005, Ric Messier wrote: >> >> >> >> > >> >> > On Tue, 11 Jan 2005, Schafer Frank wrote: >> >> > >> >> >> >> >> >> What will I have to do to change from simpleinit to sysv init? >> >> >> Would it be sufficiennt to emerge sysv? Will I have to unmerge >> >> >> simpleinit? I'd like to have my initscripts #!/bin/sh. >> >> >> >> >> > >> >> > Is that the only reason you want a SysV init? A bit odd, especially >> >> given: >> >> > >> >> >> >> Thinking about this further, I'm even less sure about the problem you >> >> are trying to solve. You might check to see whether sysvinit is >> >> already installed as I seem to recall it's part of the base system. I >> >> know it's installed on my system and I never asked for it explicitly. >> >> >> >> Ric >> >> >> >> -- >> >> gentoo-user@gentoo.org mailing list >> >> >> >> >> > >> > -- >> > gentoo-user@gentoo.org mailing list >> > >> > >> > >> > >> > -- >> > gentoo-user@gentoo.org mailing list >> > >> > >> >> >> >> -- >> gentoo-user@gentoo.org mailing list >> > > > > -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Small Gentoo
On Wed, January 12, 2005 11:40, Lode Vanstechelman said: > Hi, > > I wonder if there has already been a thread about this, but I would > like to build a very small (in disk-space terms) Gentoo Linux > distribution, to be used on 400 to 600 MB hard-disks. > > I would build the whole Gentoo system on another computer and leave it > there and then later on copy a 'subset' of that system to the small > computer. I would create the subset by copying the whole Gentoo system > and then deleting portage and distfiles and kernel sources etc. > > Said in another way: In a first stage I would build a whole new Gentoo > system on some big partition. In the second stage I would copy that > whole Gentoo system to another big partition. In that second Gentoo > system I would delete lots of stuff that I wouldn't need on the small > disks like gcc and stuff. Then in the final stage I would copy the > small linux to the small harddisk. > > I would keep the original version of the chroot Gentoo in case I need > to recompile something. Diskspace is not a problem on the big > partition. > > Now is my question: What would you guys advise me to delete to make > the system smaller? The system on the small disk would only have to > run iptables. > > Thanks, > > Lode > > -- > gentoo-user@gentoo.org mailing list > > I would do a stage1-install and set size-optimizations (see the GNU GCC-link in the Gentoo Handbook). Before doing 'emerge system', i would do emerge -Dpv system and with the help of that output remove some USE-flags and set them static in /etc/make.conf ( USE="-X -alsa -gtk etc etc" ). After 'emerge system' just do 'emerge -Dv iptables'. Then remove files in /usr/src/linux* , (*)/usr/portage/distfiles , (*)/usr/portage/packages/All and (*)/var/tmp/portage/* (*)=may vary depending on your settings in /etc/make.conf /©harlie -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel update
On Thu, January 13, 2005 7:26, Me said: > I currently have 2.6.9-r9, and recently did emerge -uD world. I got an > updated set of kernel headers (2.6.8-r2) and an updated set of development > sources (2.6.10-r4). In order to use the new kernel and save the 2.6.9 > (just in case), I think that I need to do: > make oldconfig I myself prefer the 'make menuconfig' config. > make modules_install > emerge alsa-driver (according to the alsa gentoo doc, it says that > whenever > you re-compile kernel sources, this should be done - hopefully, my > /etc/asound.state, make.conf and modules.d/alsa files will be left intact) This applies if you're using a 2.4-kernel. In 2.6, use the native ALSA-drivers (available under Sound). > cp bzImage /boot/kernel-2.6.10-r4 arch/i386/boot/bzImage, but I'm sure you'll find it anyway > cp System.map /boot/System.map-2.6.10-r4 > cp /usr/src/2.6.10/.config /boot/config-2.6.10-r4 > edit grub.conf to add the new kernel version > rm -f /usr/src/linux > ln -s /usr/src/linux-2.6.10-gentoo-r4 /usr/src/linux > > I don't think I've left anything out. any input is greatly appreciated. IF anything didn't go well, you can always boot back to the previuos kernel (if you kept it in grub.conf) > I'm > somewhat new at this and don't want to have to redo anything I don't have > to. > Don't worry, plenty of help out here :) > > > > > > -- > gentoo-user@gentoo.org mailing list > > /Charlie -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] WiFi success story :|
On Wed, January 12, 2005 21:50, Boyd Stephen Smith Jr. said:
> On Wednesday 12 January 2005 04:12 am, "Charlie Gehlin"
> <[EMAIL PROTECTED]> wrote:
>> I disagree, when dealing with a ~x86-package it might have
>> deep-dependencies that is also in ~x86.
>
> Better to be informed about what unstable packages are being installed
> than
> accept them automatically with any other (possibly stable) dependencies.
>
I don't do stable x86, I do ~x86 and ~sparc, so I don't really care if I
got unstable packages. Anyway, in this case when we're about to be
constructive regarding user help: wy are we even having this discussion in
this thread? Start a new one if you have general recommendations, this
thread is about getting a ipw2200 to work, right?
> So, use package.keywords.
>
> Also, environment variables from the command line are easily forgotten (or
> may be contradictory) so are not easily used with an emerge -uD --newuse
> world. Once you've used environement variables on the command line, this
> might downgrade packages or remove use flags in breaking ways. To keep
> the system maintained you have to edit the package.{use,keywords} files
> anyway.
>
> So, /use package.keywords/.
>
>> I also disagree on package.keywords since it's better to
>> test if emerge goes well and that module actually works
>> before making any static changes regarding keywords
>> or even USE- & FEATURES-flags for that matter.
>
> I disagree. When testing it is better to minimize the changes you make to
> the system. When using environment variables on the command-line, you
> change how portage looks at *every* package during the install. If you
> modify package.use or package.keywords your changes are limited to that
> package only.
>
> So, *use package.keywords*.
>
> I suppose environment variable on the command-line could be useful for a
> -p
> (--pretend) emerge, but not very since for any real emerge you'd want to
> use package.{use,keywords} and the results will be different.
>
> FEATURES is different, because it always affects all packages (unless
> they've added a package.features I don't know about) so it is safe to
> specify on the command line.
>
> In short, you should always use package.{use,keywords} instead of the
> corresponding environment variable on the command-line for 4 simple
> reasons:
> 1. Changes are minimized. [single package vs. all packages]
> 2. Changes are publicized. [you can easily view the files]
> 3. Changes are persisted. [emerge -uD --newuse world picks up on them]
> 4. Changes are verified. [As a corallary to (1) and (2), you will know
> what
> packages you've changed and how]
>
Let's make it up to the users to decide if they wan't unstable or stable
packages/package-dependencies.
> So, USE PACKAGE.KEYWORDS!
No need for capsing, We all sure can read you anyway.
>
> --
> Boyd Stephen Smith Jr.
> [EMAIL PROTECTED]
> ICQ: 514984 YM/AIM: DaTwinkDaddy
>
> --
> gentoo-user@gentoo.org mailing list
>
>
/Charlie
--
gentoo-user@gentoo.org mailing list
RE: [gentoo-user] kernel update
On Thu, January 13, 2005 7:59, Me said: > Charlie~ > Thanks very much for the sanity check. > > I looked at using make oldconfig, since I've made a few changes to the > existing kernel, and didn't want to have to 'rememeber' to make all of > those > changes again. If you'd like, you can run 'make menuconfig' after oldconfig to see if there's any new bleeding egde-super options that you might be interested to activate. > I didn't know that the emerge was only for 2.4 kernels. But, under 2.6, > for > some reason, I couldn't seem to get sound working at the commandline, and > by > removing the sound from the kernel and going through the steps in the alsa > gentoo guide, I was able to get it running (and through some additional > googling, set the asound.state file to keep it running on reboot). I've never had any problem with native 2.6-ALSA, but I've emerged theese packages (not needed to re-emerege after kernel-updates): alsa-lib alsa-utils alsa-tools > Yeah, I knew the arch/i386... path, I just didn't want to type it all out > ;) heh :p > Being able to boot back to the 2.6.9 kernel is what I'm trying to do with > as > a part of this exercise. I had a serious problem develop on my first > install, which got so out of hand, that I re-installed. I just don't want > that problem again. > > That's the one thing I really like about gentoo. This user-list and the > irc > channel seem to be the most helpful places in the world. As soon as I can, > I'm dumping my windows boxes entirely and staying with gentoo. > > Regards, > > -Original Message- > From: Charlie Gehlin [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 13, 2005 1:39 AM > To: [EMAIL PROTECTED] > Subject: Re: [gentoo-user] kernel update > > On Thu, January 13, 2005 7:26, Me said: >> I currently have 2.6.9-r9, and recently did emerge -uD world. I got an >> updated set of kernel headers (2.6.8-r2) and an updated set of >> development >> sources (2.6.10-r4). In order to use the new kernel and save the 2.6.9 >> (just in case), I think that I need to do: >> make oldconfig > > I myself prefer the 'make menuconfig' config. > >> make modules_install >> emerge alsa-driver (according to the alsa gentoo doc, it says that >> whenever >> you re-compile kernel sources, this should be done - hopefully, my >> /etc/asound.state, make.conf and modules.d/alsa files will be left >> intact) > > This applies if you're using a 2.4-kernel. In 2.6, use the native > ALSA-drivers (available under Sound). > >> cp bzImage /boot/kernel-2.6.10-r4 > > arch/i386/boot/bzImage, but I'm sure you'll find it anyway > >> cp System.map /boot/System.map-2.6.10-r4 >> cp /usr/src/2.6.10/.config /boot/config-2.6.10-r4 >> edit grub.conf to add the new kernel version >> rm -f /usr/src/linux >> ln -s /usr/src/linux-2.6.10-gentoo-r4 /usr/src/linux >> >> I don't think I've left anything out. any input is greatly appreciated. > > IF anything didn't go well, you can always boot back to the previuos > kernel (if you kept it in grub.conf) > >> I'm >> somewhat new at this and don't want to have to redo anything I don't >> have >> to. >> > > Don't worry, plenty of help out here :) > >> >> >> >> >> >> -- >> gentoo-user@gentoo.org mailing list >> >> > > /Charlie > > > -- > gentoo-user@gentoo.org mailing list > > > > > > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] system backup with quickpkg
I would include user(s) home-dirs, as many settings gets stored there.
Oh, and kernel-configs :)
Charlie
On Fri, January 14, 2005 14:40, Bastian Balthazar Bux said:
> The following oneline create binary packages for all installed ebuilds.
>
> # find /var/db/pkg/ -type d -mindepth 2 -exec quickpkg {} \;
>
> adding a backup of /etc is it enough to recreate the same
> system/installation ?
> there are drawback, known bugs?
>
> tnx
>
> --
> Francesco Riosa
>
>
> --
> gentoo-user@gentoo.org mailing list
>
>
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MegaRAID
On Thu, January 27, 2005 17:07, Daniel Corbe said: > Hello, Hi! > > I have been trying rather unsucessfully to find monitoring tools for > the MegaRAID-based RAID cards that will run on Gentoo. Does anyone > out there have one of these cards? If so, what are you using to > monitor the status of the array. I don't use it anymore (simply haven't changed RAID- layout for the last 3-4 re-installs or so), but here it is: http://linux.dell.com/storage.shtml under "Megaraid" and "Management Utility" I see thats it's quiet outdated, but I had it working on a RedHat 9 with no sweat getting it installed. I don't have a Dell-card either (card, HP NetRAID, was slaughtered from a HP LX-Pro?) but that didn't matter. > > I just want some basic information out of it: Whether or not the > drives are on line, rebuilding, failed, etc. As I recall it, the utility looks just like the BIOS-firmware that you enter at boot. > > Any help is appriciated. Hope it helps. > > Regards, > Daniel > Regards Charlie -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: Mouse Problems...
I would suspect that this might be a power-issue, especially as you said that HDD's gone offline. Observe your +12V and +5V voltages from PSU via lm_sensors or in BIOS to if your values are OK. Keyboards and mice are powered w. +5V (both PS/2 and USB) so that might be the voltage to focus on. Regarding the HDD: you might find a spin-up delay setting in SCSI-BIOS, to prevent all devices being powered-up all at the same time. /Charlie On Wed, February 9, 2005 13:58, Alex Lambert said: > I am being slowly driven insane by my mouse. When in X.org (GNUStep) I > am having problems with my mouse losing synchronisation and doing odd > stuff (randomly moving, selecting, clicking etc). Sometimes (and for > varying degrees fo time in both fixing and before it becomes > unfixable) I can fix this by removing the psmouse module and reloading > it (It is now a mosule to avoid me having to reboot every time it did > this). I have tried different mice and different kernels (in kernel > and module), but nothing seems to fix this. I have come to the > conclusion it's a hardware problem (unless anyone knows of any > problems with mice doing this in latest portage (~x86) x.org or > GNUStep). > > I have also noticed that sometimes, when I do have to reboot over this > issue, one of my SCSI harddrives is "Not Ready" (from the Advansys > "BIOS" screen) and I have to leave it for a while before rebooting > again. Could this be tied into the problem? If so, I need to remove it > from my LVM before I can take it out and was looking to see if anyone > had any other ideas before I bring the house down with my screaming. > > Alex -- gentoo-user@gentoo.org mailing list
