Re: [gentoo-user] Can't login from terminal?
On Thu, 12 Feb 2009 12:41:17 +0800 Chuanwen Wu wcw8...@gmail.com wrote: My gentoo worked very well in the past two years. But today I found that I can't login it from the terminal, but ssh login is OK. If you have pam on your system, then it broken '/etc/pam.d/system-local-login' might be the cause, as well as user-specific files there. And if that's not the case, try commenting out pam modules like mod_access, which can add additional access restrictions. Also, you can probably tell if pam is the cause of a problem by commenting out all the required modules from whole authentication chain (usually, commenting out everything in system-auth will do) - it should allow any access w/o password, and it's probably not pam if it doesn't... can't really think what else it might be, though. -- Mike Kazantsev // fraggod.net
Re: [gentoo-user] Can't login from terminal?
Hi, thanks! If you have pam on your system, then it broken '/etc/pam.d/system-local-login' might be the cause, as well as user-specific files there. And if that's not the case, try commenting out pam modules like mod_access, which can add additional access restrictions. which file has mod_access ? # grep mod_access /etc/* -R grep: /etc/ssl/certs/cacert.org.pem: No such file or directory grep: /etc/ssl/certs/5ed36f99.0: No such file or directory Also, you can probably tell if pam is the cause of a problem by commenting out all the required modules from whole authentication chain (usually, commenting out everything in system-auth will do) - it should allow any access w/o password, and it's probably not pam if it doesn't... can't really think what else it might be, though. I have commented out everything in system-auth, and still can't login, although the result is diff: /*/ This is Gentoo-Server.unknown_domain (Linux i686 2.6.26-gentoo-r1) 12:22:39 Gentoo-Server login: root Last login: Thu Feb 12:09:24 CST 2009 from node07 on pts/0 This is Gentoo-Server.unknown_domain (Linux i686 2.6.26-gentoo-r1) 12:28:36 Gentoo-Server login: /*/ Now it don't prompt the Password: -- wcw
Re: [gentoo-user] Can't login from terminal?
On Thu, 12 Feb 2009 16:28:35 +0800 Chuanwen Wu wcw8...@gmail.com wrote: which file has mod_access ? I have it in '/etc/pam.d/system-login', which is included for both local and remote connections, but I could've added it myself. Now it don't prompt the Password: Looks like the system is unable to launch a shell for some reason, prehaps you can change it to something default, like /bin/sh, or just something else if it's bash already. Also, I'd double-check the logs - if something fails, there shoud be a message about it. Make sure you have syslog daemon running and not dropping any debug messages. -- Mike Kazantsev // fraggod.net
Re: [gentoo-user] python-2.5.2-r7 build problems
On Wed, 11 Feb 2009 20:22:32 -0800, Mark Knecht wrote: CFLAGS? The machine that fails: CFLAGS=-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe CFLAGS=-O2 -march=i686 -fomit-frame-pointer -pipe You have more aggressive flags on the failing machine, have you tried using the more conservative (less ricey) flags? -- Neil Bothwick USENET: Uniting Spammers, Erotomaniacs, Newbies, Extroverts and Trolls signature.asc Description: PGP signature
Re: [gentoo-user] Can't login from terminal?
On Thu, 12 Feb 2009 13:42:03 +0500, Mike Kazantsev wrote: Looks like the system is unable to launch a shell for some reason, prehaps you can change it to something default, like /bin/sh, or just something else if it's bash already. Could it also be something in the bash profile causing the shell to exit? -- Neil Bothwick From the moment I picked your book up until I laid it down I was convulsed with laughter. Someday I intend reading it. signature.asc Description: PGP signature
[gentoo-user] strange error during boot
Hi. I just upgraded a gentoo system from about August 2008 to current -- including updating baselayout and openrt and now when I boot I get a series of messages quite early in the boot modprobe: fatal /sys is not mounted. Eventually it does boot and all seems to work with the exception of the script for my hsfmodem, but I am curious as to what those message mean and if there is a way to fix them. Any assistance would be appreciated. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] strange error during boot
On Thu, February 12, 2009 10:52 am, John covici wrote: Hi. I just upgraded a gentoo system from about August 2008 to current -- including updating baselayout and openrt and now when I boot I get a series of messages quite early in the boot modprobe: fatal /sys is not mounted. Eventually it does boot and all seems to work with the exception of the script for my hsfmodem, but I am curious as to what those message mean and if there is a way to fix them. Any assistance would be appreciated. Did you include sysfs support to your kernel and do you have a directory '/sys'? (SYSFS) This can be found in: File systems / Pseudo filesystems in the kernel configuration. The '/sys' filesystem is as important as '/proc' these days. -- Joost Roeleveld
[gentoo-user] Re: Digest of gentoo-user@lists.gentoo.org issue 1710 (90678-90727)
hi, after trying many time, i am again trying to install the gentoo on my macbook pro 4.1 . after pessing 2 days with it, still i have some problem: 1. sound not working (tried most of the solutions that available online 2. wifi not working 3. touchpad not working ok (two fingurs scroll working, but not the second click and not moving ok) anybody here using gentoo on macbook pro I run Gentoo on a (white) MacBook v2, and with some exceptions (video card, backlighted keyboard, network card, number of fans, something I forgot?), the hardware is mostly the same to my knowledge. In general, I have made good documentation for how do install Gentoo on a MacBook, and it will be online in a couple months. I'm not actually that good with Gentoo, so there may be easier or better ways to do the things I do, but I am able to use all the MacBook hardware in Gentoo, so I'll tell you what I've done. (This is to say that respondants should be nice to me, because I'm not claiming this is gospel!) For the sound I did not have to do anything special for the MacBook, so I'll just give a run down of the things you should do in general (which I also did and found to work). Make sure you've gotten alsa-utils and alsa-oss from portage. Then make sure to run alsaconf, and that the daemon alsasound is started and in your default rc. If you update the kernel, you'd need to re-run alsaconf. For my 2.6.26 kernel, I have these ALSA configurations:CONFIG_SND=m;CONFIG_SND_TIMER=m;CONFIG_SND_PCM=m;CONFIG_SND_SEQUENCER=m;CONFIG_SND_OSSEMUL=y;CONFIG_SND_MIXER_OSS=m;CONFIG_SND_PCM_OSS=m;CONFIG_SND_PCM_OSS_PLUGINS=y;CONFIG_SND_SEQUENCER_OSS=y;CONFIG_SND_RTCTIMER=m;CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y;CONFIG_SND_SUPPORT_OLD_API=y;CONFIG_SND_VMASTER=y For wifi I found that madwifi-ng in portage does not make wifi on my MacBook work; probably it's user error, but maybe not. But it's really easy to do it manually, though. Just get the drivers with subversion and install them, as follows: $ cd /usr/src # svn checkout http://svn.madwifi-project.org/madwifi/trunk madwifi $ cd madwifi # make # make install # ln -s /usr/src/madwifi /usr/include/madwifi Now, for updates in the source code, we need only: # cd /usr/src/madwifi svn update Whenever you install a new kernel, you need to go to /usr/src/madwifi and make make install again. If your touchpad is working and you can two-finger scroll then I'm guessing you got synaptics working, and now it's just an issue to set up specific details. xorg.conf configuration for synaptics is now deprecated, but a lot of the documentation for Gentoo on MacBooks is outdated and suggests you to do this. I've been a bit lazy about the switch to doing things through HAL's fdi policy, so some of my configurations, which I ported straight from xorg.conf, might be deprecated or unsupported. But in any event, my touchpad works, including things like two-finger click, scrolling, and so on. You can see it here: http://en.gentoo-wiki.com/wiki/Synaptics_Touchpad/Configuration In general, feel free to send me personal emails about MacBook questions. ~daid
[gentoo-user] DebugFS
I see that DebugFS is getting mounted very early on in the boot sequence. I want to keep it enabled in the kernel, but not automatically mounted. What mounts it? How can I stop it? Thanks, Mark pgpZOmF3N5lI3.pgp Description: PGP signature
Re: [gentoo-user] DebugFS
On Thu, Feb 12, 2009 at 11:29:43AM +, Mark Somerville wrote: I see that DebugFS is getting mounted very early on in the boot sequence. I want to keep it enabled in the kernel, but not automatically mounted. What mounts it? How can I stop it? In typical style, I solved it almost immediately after asking! /etc/init.d/sysfs mounts it. Mark pgpJzzY7PhUIy.pgp Description: PGP signature
[gentoo-user] AMD Turion64x2 CFLAGS
Hi list, my laptop's cpu is AMD Turion64x2, I've installed both 32bits Debian testing and Gentoo on it, from Debian there is no SSE3 in /proc/cpuinfo, and I used CFLAGS=-O2 -march=athlon-xp -fomit-frame-pointer -pipe on gentoo, and I can not see SSE3 in cpuinfo also, I emerged x86info, and SSE3 is in its output: #x86info x86info v1.21. Dave Jones 2001-2007 Feedback to da...@redhat.com. Found 2 CPUs -- CPU #1 Family: 15 Model: 72 Stepping: 2 CPU Model : Turion 64 X2 (BH-F2) Processor name string: AMD Turion(tm) 64 X2 Mobile Technology TL-52 Feature flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflsh mmx fxsr sse sse2 ht sse3 cmpxchg16b Extended feature flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 nx mmxext mmx fxsr ffxsr rdtscp lm 3dnowext 3dnow lahf/sahf CmpLegacy svm ExtApicSpace LockMovCr0 SVM: revision 1, 64 ASIDs Address Size: 48 bits virtual, 40 bits physical The physical package has 2 of 2 possible cores implemented. ... ... my question is: I can not see SSE3 in cpuinfo because I did not use -msse3 in CFLAGS ?
Re: [gentoo-user] AMD Turion64x2 CFLAGS
On Thu, February 12, 2009 12:52 pm, Zhang Jun wrote: Hi list, my laptop's cpu is AMD Turion64x2, I've installed both 32bits Debian testing and Gentoo on it, from Debian there is no SSE3 in /proc/cpuinfo, and I used CFLAGS=-O2 -march=athlon-xp -fomit-frame-pointer -pipe on gentoo, and I can not see SSE3 in cpuinfo also, I emerged x86info, and SSE3 is in its output: #x86info x86info v1.21. Dave Jones 2001-2007 Feedback to da...@redhat.com. Found 2 CPUs -- snipped output my question is: I can not see SSE3 in cpuinfo because I did not use -msse3 in CFLAGS ? Hi, I would suspect that for your CPU using -march=athlon-fx would be more beneficial as your CPU has the x86_64 instruction set as well? -- Joost
Re: [gentoo-user] AMD Turion64x2 CFLAGS
thanks! I'm new to gentoo, I get the CFLAGS from gentoo-wiki( http://en.gentoo-wiki.com/wiki/Safe_Cflags/AMD#Turion64_.2F_X2_.2F_Ultra ) and I am using 32bit linux. 2009/2/12 Joost Roeleveld jo...@antarean.org: On Thu, February 12, 2009 12:52 pm, Zhang Jun wrote: Hi list, my laptop's cpu is AMD Turion64x2, I've installed both 32bits Debian testing and Gentoo on it, from Debian there is no SSE3 in /proc/cpuinfo, and I used CFLAGS=-O2 -march=athlon-xp -fomit-frame-pointer -pipe on gentoo, and I can not see SSE3 in cpuinfo also, I emerged x86info, and SSE3 is in its output: #x86info x86info v1.21. Dave Jones 2001-2007 Feedback to da...@redhat.com. Found 2 CPUs -- snipped output my question is: I can not see SSE3 in cpuinfo because I did not use -msse3 in CFLAGS ? Hi, I would suspect that for your CPU using -march=athlon-fx would be more beneficial as your CPU has the x86_64 instruction set as well? -- Joost
Re: [gentoo-user] AMD Turion64x2 CFLAGS
On Thu, February 12, 2009 1:34 pm, Zhang Jun wrote: thanks! I'm new to gentoo, I get the CFLAGS from gentoo-wiki( http://en.gentoo-wiki.com/wiki/Safe_Cflags/AMD#Turion64_.2F_X2_.2F_Ultra ) and I am using 32bit linux. 2009/2/12 Joost Roeleveld jo...@antarean.org: On Thu, February 12, 2009 12:52 pm, Zhang Jun wrote: Hi list, my laptop's cpu is AMD Turion64x2, I've installed both 32bits Debian testing and Gentoo on it, from Debian there is no SSE3 in /proc/cpuinfo, and I used CFLAGS=-O2 -march=athlon-xp -fomit-frame-pointer -pipe on gentoo, and I can not see SSE3 in cpuinfo also, I emerged x86info, and SSE3 is in its output: #x86info x86info v1.21. Dave Jones 2001-2007 Feedback to da...@redhat.com. Found 2 CPUs -- snipped output my question is: I can not see SSE3 in cpuinfo because I did not use -msse3 in CFLAGS ? Hi, I would suspect that for your CPU using -march=athlon-fx would be more beneficial as your CPU has the x86_64 instruction set as well? -- Joost Thank you for that link, I wasn't aware of it. Please, for future reference, try to avoid top-posting, it makes following conversations difficult. Try to keep your replies at the bottom of the email. According to that list, you need to add -msse3 to your CFLAGS. Which makes sense as -march=athlon-xp is actually for an older CPU which didn't have sse3 support yet. -- Joost
Re: [gentoo-user] strange error during boot
on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 10:52 am, John covici wrote: Hi. I just upgraded a gentoo system from about August 2008 to current -- including updating baselayout and openrt and now when I boot I get a series of messages quite early in the boot modprobe: fatal /sys is not mounted. Eventually it does boot and all seems to work with the exception of the script for my hsfmodem, but I am curious as to what those message mean and if there is a way to fix them. Any assistance would be appreciated. Did you include sysfs support to your kernel and do you have a directory '/sys'? (SYSFS) This can be found in: File systems / Pseudo filesystems in the kernel configuration. The '/sys' filesystem is as important as '/proc' these days. The plot thickens -- by the time I log in after booting, /sys is mounted with the correct file system. Still very strange. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] strange error during boot
On Thu, February 12, 2009 2:05 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 10:52 am, John covici wrote: Hi. I just upgraded a gentoo system from about August 2008 to current -- including updating baselayout and openrt and now when I boot I get a series of messages quite early in the boot modprobe: fatal /sys is not mounted. Eventually it does boot and all seems to work with the exception of the script for my hsfmodem, but I am curious as to what those message mean and if there is a way to fix them. Any assistance would be appreciated. Did you include sysfs support to your kernel and do you have a directory '/sys'? (SYSFS) This can be found in: File systems / Pseudo filesystems in the kernel configuration. The '/sys' filesystem is as important as '/proc' these days. The plot thickens -- by the time I log in after booting, /sys is mounted with the correct file system. Still very strange. Hmm... so, something does solve the problem you are seeing at the beginning later on. Did you update all the configuration files (including the ones in /etc/init.d/.. )? It could be that something there is not set correctly. For now, I am assuming the issue is in the boot-sequence/runlevel. Can you check which services are in your boot-runlevel? I have: bootmisc, checkfs, checkroot, clock, consolefone, hostname, keymaps, localmount, modules, net.lo rmnologin and urandom. Think these are the default ones. Do you use an initrd? If yes, did you update this as well? -- Joost
Re: [gentoo-user] AMD Turion64x2 CFLAGS
On Donnerstag 12 Februar 2009, Zhang Jun wrote: Hi list, my laptop's cpu is AMD Turion64x2, I've installed both 32bits Debian testing and Gentoo on it, from Debian there is no SSE3 in /proc/cpuinfo, I am sure there is. But it is called 'pni' - its original name. and I used CFLAGS=-O2 -march=athlon-xp -fomit-frame-pointer -pipe on gentoo, and I can not see SSE3 in cpuinfo also, I emerged x86info, and SSE3 is in its output: #x86info x86info v1.21. Dave Jones 2001-2007 Feedback to da...@redhat.com. Found 2 CPUs -- CPU #1 Family: 15 Model: 72 Stepping: 2 CPU Model : Turion 64 X2 (BH-F2) Processor name string: AMD Turion(tm) 64 X2 Mobile Technology TL-52 Feature flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflsh mmx fxsr sse sse2 ht sse3 cmpxchg16b Extended feature flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 nx mmxext mmx fxsr ffxsr rdtscp lm 3dnowext 3dnow lahf/sahf CmpLegacy svm ExtApicSpace LockMovCr0 SVM: revision 1, 64 ASIDs Address Size: 48 bits virtual, 40 bits physical The physical package has 2 of 2 possible cores implemented. ... ... my question is: I can not see SSE3 in cpuinfo because I did not use -msse3 in CFLAGS ? no. Because it is called 'pni'. How about this cflags: march=k8-sse3 -O2 -msse3 (in case march gets filtered) -pipe ? on amd64 fomit-frame-pointer isn't needed anymore.
Re: [gentoo-user] strange error during boot
on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 2:05 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 10:52 am, John covici wrote: Hi. I just upgraded a gentoo system from about August 2008 to current -- including updating baselayout and openrt and now when I boot I get a series of messages quite early in the boot modprobe: fatal /sys is not mounted. Eventually it does boot and all seems to work with the exception of the script for my hsfmodem, but I am curious as to what those message mean and if there is a way to fix them. Any assistance would be appreciated. Did you include sysfs support to your kernel and do you have a directory '/sys'? (SYSFS) This can be found in: File systems / Pseudo filesystems in the kernel configuration. The '/sys' filesystem is as important as '/proc' these days. The plot thickens -- by the time I log in after booting, /sys is mounted with the correct file system. Still very strange. Hmm... so, something does solve the problem you are seeing at the beginning later on. Did you update all the configuration files (including the ones in /etc/init.d/.. )? It could be that something there is not set correctly. For now, I am assuming the issue is in the boot-sequence/runlevel. Can you check which services are in your boot-runlevel? I have: bootmisc, checkfs, checkroot, clock, consolefone, hostname, keymaps, localmount, modules, net.lo rmnologin and urandom. Think these are the default ones. Do you use an initrd? If yes, did you update this as well? I regenerated the initrd, but I am still using 2.6.20 kernel which I will update soon, but I wonder if this is the problem -- something wrong with the initrd, but regenerating did not fix it. In my boot level I have bootmisc@ consolefont@ device-mapper@ fsck@ hibernate-cleanup@ hostname@ hwclock@ keymaps@ localmount@ modules@ mtab@ net.lo@ procfs@ root@ swap@ sysctl@ termencoding@ urandom@ in my sysinit I have devfs@ dmesg@ udev@ -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] syslog-ng +bash history
2009/2/5 Willie Wong ww...@princeton.edu On Thu, Feb 05, 2009 at 09:31:07AM +0100, Penguin Lover Marcin Niskiewicz squawked: It works fine (it writes history to history.log) but still it writes it to those 3 files (debug , syslog, messages) as well ... so now everything I type is written to 4 files (debug , syslog, messages and history.log) and I'd like it to be written only to 1 file. If you have a filter rule that matches for history, why don't you just append and not [insert rule here] to the filter rule for syslog, messages, and debug? W -- This is just for cultural purposes, so don't panic. ~DeathMech, S. Sondhi. P-town PHY 205 Sortir en Pantoufles: up 790 days, 13:07 Hello thanks for helping me as it seems the solution was easy - i had to put flags(final); parameter and change a little order in config file and put: log { source(src); filter(f_history); destination(history); flags(final); }; in the highest line in log section and it works! (the solution from syslog-ng group) thanks again regards nichu
Re: [gentoo-user] strange error during boot
On Thu, February 12, 2009 2:26 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 2:05 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 10:52 am, John covici wrote: Hi. I just upgraded a gentoo system from about August 2008 to current -- including updating baselayout and openrt and now when I boot I get a series of messages quite early in the boot modprobe: fatal /sys is not mounted. Eventually it does boot and all seems to work with the exception of the script for my hsfmodem, but I am curious as to what those message mean and if there is a way to fix them. Any assistance would be appreciated. Did you include sysfs support to your kernel and do you have a directory '/sys'? (SYSFS) This can be found in: File systems / Pseudo filesystems in the kernel configuration. The '/sys' filesystem is as important as '/proc' these days. The plot thickens -- by the time I log in after booting, /sys is mounted with the correct file system. Still very strange. Hmm... so, something does solve the problem you are seeing at the beginning later on. Did you update all the configuration files (including the ones in /etc/init.d/.. )? It could be that something there is not set correctly. For now, I am assuming the issue is in the boot-sequence/runlevel. Can you check which services are in your boot-runlevel? I have: bootmisc, checkfs, checkroot, clock, consolefone, hostname, keymaps, localmount, modules, net.lo rmnologin and urandom. Think these are the default ones. Do you use an initrd? If yes, did you update this as well? I regenerated the initrd, but I am still using 2.6.20 kernel which I will update soon, but I wonder if this is the problem -- something wrong with the initrd, but regenerating did not fix it. In my boot level I have bootmisc@ consolefont@ device-mapper@ fsck@ hibernate-cleanup@ hostname@ hwclock@ keymaps@ localmount@ modules@ mtab@ net.lo@ procfs@ root@ swap@ sysctl@ termencoding@ urandom@ in my sysinit I have devfs@ dmesg@ udev@ Do you have device-mapper in your boot-level? In that case, you might want to check which init-script mounts the '/sys' filesystem as this script requires the /sys filesystem to be mounted. May I ask why you have this added as I don't use it with my LVM drives. -- Joost
Re: [gentoo-user] python-2.5.2-r7 build problems
On Thu, Feb 12, 2009 at 12:58 AM, Neil Bothwick n...@digimed.co.uk wrote: On Wed, 11 Feb 2009 20:22:32 -0800, Mark Knecht wrote: CFLAGS? The machine that fails: CFLAGS=-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe CFLAGS=-O2 -march=i686 -fomit-frame-pointer -pipe You have more aggressive flags on the failing machine, have you tried using the more conservative (less ricey) flags? -- Neil Bothwick I have not and intend to do that today. The flags have been set like this since 2003 so I'm surprised that it might be something like this but it's clearly possible. I'm unqualified to say what part of the differences is making this set more aggressive. Line by line what's your opinion? -O3 vs -O2 ? -march=athlon-xp vs -march=i686 -funroll-loops -fprefetch-loop-arrays not using -fomit-frame-pointer I would think that I should be able to also make the flags more aggressive on a passing machine and see the same failure, assuming this is the root cause. Strange taht after 6-years this would come up but stranger thing happen. Thanks, Mark
Re: [gentoo-user] strange error during boot
On Thu, Feb 12, 2009 at 02:44:15PM +0100, Joost Roeleveld wrote: On Thu, February 12, 2009 2:26 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 2:05 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 10:52 am, John covici wrote: Hi. I just upgraded a gentoo system from about August 2008 to current -- including updating baselayout and openrt and now when I boot I get a series of messages quite early in the boot modprobe: fatal /sys is not mounted. Eventually it does boot and all seems to work with the exception of the script for my hsfmodem, but I am curious as to what those message mean and if there is a way to fix them. Any assistance would be appreciated. Did you include sysfs support to your kernel and do you have a directory '/sys'? (SYSFS) This can be found in: File systems / Pseudo filesystems in the kernel configuration. The '/sys' filesystem is as important as '/proc' these days. The plot thickens -- by the time I log in after booting, /sys is mounted with the correct file system. Still very strange. Hmm... so, something does solve the problem you are seeing at the beginning later on. Did you update all the configuration files (including the ones in /etc/init.d/.. )? It could be that something there is not set correctly. For now, I am assuming the issue is in the boot-sequence/runlevel. Can you check which services are in your boot-runlevel? I have: bootmisc, checkfs, checkroot, clock, consolefone, hostname, keymaps, localmount, modules, net.lo rmnologin and urandom. Think these are the default ones. Do you use an initrd? If yes, did you update this as well? I regenerated the initrd, but I am still using 2.6.20 kernel which I will update soon, but I wonder if this is the problem -- something wrong with the initrd, but regenerating did not fix it. In my boot level I have bootmisc@ consolefont@ device-mapper@ fsck@ hibernate-cleanup@ hostname@ hwclock@ keymaps@ localmount@ modules@ mtab@ net.lo@ procfs@ root@ swap@ sysctl@ termencoding@ urandom@ in my sysinit I have devfs@ dmesg@ udev@ Do you have device-mapper in your boot-level? In that case, you might want to check which init-script mounts the '/sys' filesystem as this script requires the /sys filesystem to be mounted. May I ask why you have this added as I don't use it with my LVM drives. -- Joost http://bugs.gentoo.org/show_bug.cgi?id=258442 === TopperH === pgpKGXTGmCFbs.pgp Description: PGP signature
Re: [gentoo-user] strange error during boot
On Thu, February 12, 2009 3:21 pm, Momesso Andrea wrote: On Thu, Feb 12, 2009 at 02:44:15PM +0100, Joost Roeleveld wrote: On Thu, February 12, 2009 2:26 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 2:05 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 10:52 am, John covici wrote: Hi. I just upgraded a gentoo system from about August 2008 to current -- including updating baselayout and openrt and now when I boot I get a series of messages quite early in the boot modprobe: fatal /sys is not mounted. Eventually it does boot and all seems to work with the exception of the script for my hsfmodem, but I am curious as to what those message mean and if there is a way to fix them. Any assistance would be appreciated. Did you include sysfs support to your kernel and do you have a directory '/sys'? (SYSFS) This can be found in: File systems / Pseudo filesystems in the kernel configuration. The '/sys' filesystem is as important as '/proc' these days. The plot thickens -- by the time I log in after booting, /sys is mounted with the correct file system. Still very strange. Hmm... so, something does solve the problem you are seeing at the beginning later on. Did you update all the configuration files (including the ones in /etc/init.d/.. )? It could be that something there is not set correctly. For now, I am assuming the issue is in the boot-sequence/runlevel. Can you check which services are in your boot-runlevel? I have: bootmisc, checkfs, checkroot, clock, consolefone, hostname, keymaps, localmount, modules, net.lo rmnologin and urandom. Think these are the default ones. Do you use an initrd? If yes, did you update this as well? I regenerated the initrd, but I am still using 2.6.20 kernel which I will update soon, but I wonder if this is the problem -- something wrong with the initrd, but regenerating did not fix it. In my boot level I have bootmisc@ consolefont@ device-mapper@ fsck@ hibernate-cleanup@ hostname@ hwclock@ keymaps@ localmount@ modules@ mtab@ net.lo@ procfs@ root@ swap@ sysctl@ termencoding@ urandom@ in my sysinit I have devfs@ dmesg@ udev@ Do you have device-mapper in your boot-level? In that case, you might want to check which init-script mounts the '/sys' filesystem as this script requires the /sys filesystem to be mounted. May I ask why you have this added as I don't use it with my LVM drives. http://bugs.gentoo.org/show_bug.cgi?id=258442 Helpful, but only if OP is using module-init-tools 3.6, which is currently in unstable for all archs. John, can you please confirm which 'module-init-tools' version you are using? -- Joost
Re: [gentoo-user] python-2.5.2-r7 build problems
On Thu, Feb 12, 2009 at 6:20 AM, Mark Knecht markkne...@gmail.com wrote: SNIP -O3 vs -O2 ? -march=athlon-xp vs -march=i686 -funroll-loops -fprefetch-loop-arrays not using -fomit-frame-pointer SNIP I started by removing -funroll-loops -fprefetch-loop-arrays and it emerged fine. Thanks, Mark
Re: [gentoo-user] The Linux Ecosystem (with funny references to Gentoo vs Canonical)
On Tue, February 10, 2009 11:12 pm, Joshua D Doll wrote: Roy Wright wrote: Mick wrote: On Tuesday 10 February 2009, Joshua D Doll wrote: Saphirus Sage wrote: Nikos Chantziaras wrote: http://video.linuxfoundation.org/video/1069 I found it quite interesting that even Gentoo beat Canonical in the amount of patches contributed upstream... Good find, I actually didn't know about E-Trade using Gentoo servers. I don't think it should be too surprising that Gentoo would contribute more patches than Conical, as until today, I'd only actually heard of one of them. This video brought up an interesting question by my friend (an ubuntu user). How would one go about getting Canonical or the ubuntu community to change their practice of not contributing fixes back upstream? Without having to change distributions. Gentoo involves you more with what goes bad under the bonnet and the average Gentoo user is more interested in the workings of their OS to attempt troubleshooting it and filing bugs. Your average Ubuntu user is less likely to get their hands dirty, unless they are a dev. So, essentially we are talking about different user profiles here. To answer your friend's hypothetical question - he would either have to change your average Ubuntu's user technical aptitude, or change the user. Either attempt may mean the end of Ubuntu as we know it. The ubuntus are targeted at disgruntled windows users while gentoo is targeted at unix users. The former are used to complaining and getting no response while the later know it's their responsibility to help make it better... Have fun, Roy I think you may be right with your assessment there Roy. The only solution I could up with was to change distributions he didn't like that suggestion, not sure why, because changing distros is like changing underwear. Maybe he has some strange fascination with Ubunutu's pretty color scheme? Wouldn't the following solve that though? # echo x11-themes/gtk-engines-ubuntulooks ~* # emerge gtk-engines-ubuntulooks It's currently at version 0.9.12-r2. I have not used this, so I have no clue how well this works. -- Joost
[gentoo-user] qt-xxx-4.5.0_rc1 conflicts
Being on ~amd64 after syncing, 'emerge -pvDuN world' command shows plenty similar errors (for each qt-related package), one of last ones is shown below. How to resolve the issue? x11-libs/qt-core:4 ('ebuild', '/', 'x11-libs/qt-core-4.5.0_rc1', 'merge') pulled in by ~x11-libs/qt-core-4.5.0_rc1[qt3support,-debug] required by ('ebuild', '/', 'x11-libs/qt- sql-4.5.0_rc1', 'merge') ~x11-libs/qt-core-4.5.0_rc1[-debug] required by ('ebuild', '/', 'x11-libs/qt-script-4.5.0_rc1', 'merge') ~x11-libs/qt-core-4.5.0_rc1[-debug] required by ('ebuild', '/', 'x11-libs/qt-test-4.5.0_rc1', 'merge') (and 250 more)
Re: [gentoo-user] qt-xxx-4.5.0_rc1 conflicts
On Thu, 12 Feb 2009 18:20:06 +0300, Andrew Gaydenko wrote: x11-libs/qt-core:4 ('ebuild', '/', 'x11-libs/qt-core-4.5.0_rc1', 'merge') pulled in by ~x11-libs/qt-core-4.5.0_rc1[qt3support,-debug] required by ('ebuild', '/', 'x11-libs/qt- sql-4.5.0_rc1', 'merge') ~x11-libs/qt-core-4.5.0_rc1[-debug] required by ('ebuild', '/', 'x11-libs/qt-script-4.5.0_rc1', 'merge') ~x11-libs/qt-core-4.5.0_rc1[-debug] required by ('ebuild', '/', 'x11-libs/qt-test-4.5.0_rc1', 'merge') (and 250 more) It's the more that shows the problem. The lines here show packages that are pulling in the latest version, you need to look for what is pulling in the conflicting version. My ~amd64 box just updated to qt-*-4.5.0_rc1 with no problem. There was a problem with a missing patch file, but it appears unrelated and was fixed by syncing. -- Neil Bothwick Mmmm, trouble with grammer have I, yes? - Yoda signature.asc Description: PGP signature
Re: [gentoo-user] qt-xxx-4.5.0_rc1 conflicts
On Donnerstag 12 Februar 2009, Andrew Gaydenko wrote: Being on ~amd64 after syncing, 'emerge -pvDuN world' command shows plenty similar errors (for each qt-related package), one of last ones is shown below. How to resolve the issue? x11-libs/qt-core:4 ('ebuild', '/', 'x11-libs/qt-core-4.5.0_rc1', 'merge') pulled in by ~x11-libs/qt-core-4.5.0_rc1[qt3support,-debug] required by ('ebuild', '/', 'x11-libs/qt- sql-4.5.0_rc1', 'merge') ~x11-libs/qt-core-4.5.0_rc1[-debug] required by ('ebuild', '/', 'x11-libs/qt-script-4.5.0_rc1', 'merge') ~x11-libs/qt-core-4.5.0_rc1[-debug] required by ('ebuild', '/', 'x11-libs/qt-test-4.5.0_rc1', 'merge') (and 250 more) mask all the qt 4.5 stuff. All of it. It will violently break everything.
Re: [gentoo-user] qt-xxx-4.5.0_rc1 conflicts
On Thu, Feb 12, 2009 at 04:25:49PM +0100, Volker Armin Hemmann wrote: On Donnerstag 12 Februar 2009, Andrew Gaydenko wrote: Being on ~amd64 after syncing, 'emerge -pvDuN world' command shows plenty similar errors (for each qt-related package), one of last ones is shown below. How to resolve the issue? x11-libs/qt-core:4 ('ebuild', '/', 'x11-libs/qt-core-4.5.0_rc1', 'merge') pulled in by ~x11-libs/qt-core-4.5.0_rc1[qt3support,-debug] required by ('ebuild', '/', 'x11-libs/qt- sql-4.5.0_rc1', 'merge') ~x11-libs/qt-core-4.5.0_rc1[-debug] required by ('ebuild', '/', 'x11-libs/qt-script-4.5.0_rc1', 'merge') ~x11-libs/qt-core-4.5.0_rc1[-debug] required by ('ebuild', '/', 'x11-libs/qt-test-4.5.0_rc1', 'merge') (and 250 more) mask all the qt 4.5 stuff. All of it. It will violently break everything. It didn't on my system... BTW, for the OP, just need to enable USE=qt3support on qt-core. === TopperH === pgp1jaIGETBa1.pgp Description: PGP signature
Re: [gentoo-user] qt-xxx-4.5.0_rc1 conflicts
On Donnerstag 12 Februar 2009, Momesso Andrea wrote: On Thu, Feb 12, 2009 at 04:25:49PM +0100, Volker Armin Hemmann wrote: On Donnerstag 12 Februar 2009, Andrew Gaydenko wrote: Being on ~amd64 after syncing, 'emerge -pvDuN world' command shows plenty similar errors (for each qt-related package), one of last ones is shown below. How to resolve the issue? x11-libs/qt-core:4 ('ebuild', '/', 'x11-libs/qt-core-4.5.0_rc1', 'merge') pulled in by ~x11-libs/qt-core-4.5.0_rc1[qt3support,-debug] required by ('ebuild', '/', 'x11-libs/qt- sql-4.5.0_rc1', 'merge') ~x11-libs/qt-core-4.5.0_rc1[-debug] required by ('ebuild', '/', 'x11-libs/qt-script-4.5.0_rc1', 'merge') ~x11-libs/qt-core-4.5.0_rc1[-debug] required by ('ebuild', '/', 'x11-libs/qt-test-4.5.0_rc1', 'merge') (and 250 more) mask all the qt 4.5 stuff. All of it. It will violently break everything. It didn't on my system... it turned kde 4.2 in a complete crash fest (starting with kdmgreet making it impossible to log in). beta was bad, rc1 was worse. And yes, I rebuilt stuff - and after that I downgraded to 4.4. and rebuild everything again - and oh look not one single crash since then - took only 6 hours of my life.
Re: [gentoo-user] qt-xxx-4.5.0_rc1 conflicts
On Thu, Feb 12, 2009 at 04:44:46PM +0100, Volker Armin Hemmann wrote: On Donnerstag 12 Februar 2009, Momesso Andrea wrote: On Thu, Feb 12, 2009 at 04:25:49PM +0100, Volker Armin Hemmann wrote: On Donnerstag 12 Februar 2009, Andrew Gaydenko wrote: Being on ~amd64 after syncing, 'emerge -pvDuN world' command shows plenty similar errors (for each qt-related package), one of last ones is shown below. How to resolve the issue? x11-libs/qt-core:4 ('ebuild', '/', 'x11-libs/qt-core-4.5.0_rc1', 'merge') pulled in by ~x11-libs/qt-core-4.5.0_rc1[qt3support,-debug] required by ('ebuild', '/', 'x11-libs/qt- sql-4.5.0_rc1', 'merge') ~x11-libs/qt-core-4.5.0_rc1[-debug] required by ('ebuild', '/', 'x11-libs/qt-script-4.5.0_rc1', 'merge') ~x11-libs/qt-core-4.5.0_rc1[-debug] required by ('ebuild', '/', 'x11-libs/qt-test-4.5.0_rc1', 'merge') (and 250 more) mask all the qt 4.5 stuff. All of it. It will violently break everything. It didn't on my system... it turned kde 4.2 in a complete crash fest (starting with kdmgreet making it impossible to log in). beta was bad, rc1 was worse. And yes, I rebuilt stuff - and after that I downgraded to 4.4. and rebuild everything again - and oh look not one single crash since then - took only 6 hours of my life. Looking at kde's blogosphere it looks more like a kde issue than a qt-4.5.0's one. Anyway, I don't have kde on my system and qt apps run just fine. === TopperH === pgpBtPn0rltXb.pgp Description: PGP signature
Re: [gentoo-user] qt-xxx-4.5.0_rc1 conflicts
On Thu, Feb 12, 2009 at 7:44 AM, Volker Armin Hemmann volkerar...@googlemail.com wrote: SNIP it turned kde 4.2 in a complete crash fest (starting with kdmgreet making it impossible to log in). beta was bad, rc1 was worse. And yes, I rebuilt stuff - and after that I downgraded to 4.4. and rebuild everything again - and oh look not one single crash since then - took only 6 hours of my life. Did you rebuild KDE or do you mean just running it after the qt build finished? - Mark
[gentoo-user] Re: qt-xxx-4.5.0_rc1 conflicts
Volker Armin Hemmann wrote: [...] it turned kde 4.2 in a complete crash fest (starting with kdmgreet making it impossible to log in). beta was bad, rc1 was worse. And yes, I rebuilt stuff - and after that I downgraded to 4.4. and rebuild everything again - and oh look not one single crash since then - took only 6 hours of my life. I don't see a bug report about it. Where did you file it?
Re: [gentoo-user] strange error during boot
on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 3:21 pm, Momesso Andrea wrote: On Thu, Feb 12, 2009 at 02:44:15PM +0100, Joost Roeleveld wrote: On Thu, February 12, 2009 2:26 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 2:05 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 10:52 am, John covici wrote: Hi. I just upgraded a gentoo system from about August 2008 to current -- including updating baselayout and openrt and now when I boot I get a series of messages quite early in the boot modprobe: fatal /sys is not mounted. Eventually it does boot and all seems to work with the exception of the script for my hsfmodem, but I am curious as to what those message mean and if there is a way to fix them. Any assistance would be appreciated. Did you include sysfs support to your kernel and do you have a directory '/sys'? (SYSFS) This can be found in: File systems / Pseudo filesystems in the kernel configuration. The '/sys' filesystem is as important as '/proc' these days. The plot thickens -- by the time I log in after booting, /sys is mounted with the correct file system. Still very strange. Hmm... so, something does solve the problem you are seeing at the beginning later on. Did you update all the configuration files (including the ones in /etc/init.d/.. )? It could be that something there is not set correctly. For now, I am assuming the issue is in the boot-sequence/runlevel. Can you check which services are in your boot-runlevel? I have: bootmisc, checkfs, checkroot, clock, consolefone, hostname, keymaps, localmount, modules, net.lo rmnologin and urandom. Think these are the default ones. Do you use an initrd? If yes, did you update this as well? I regenerated the initrd, but I am still using 2.6.20 kernel which I will update soon, but I wonder if this is the problem -- something wrong with the initrd, but regenerating did not fix it. In my boot level I have bootmisc@ consolefont@ device-mapper@ fsck@ hibernate-cleanup@ hostname@ hwclock@ keymaps@ localmount@ modules@ mtab@ net.lo@ procfs@ root@ swap@ sysctl@ termencoding@ urandom@ in my sysinit I have devfs@ dmesg@ udev@ Do you have device-mapper in your boot-level? In that case, you might want to check which init-script mounts the '/sys' filesystem as this script requires the /sys filesystem to be mounted. May I ask why you have this added as I don't use it with my LVM drives. http://bugs.gentoo.org/show_bug.cgi?id=258442 Helpful, but only if OP is using module-init-tools 3.6, which is currently in unstable for all archs. John, can you please confirm which 'module-init-tools' version you are using? Its 3.6 -- I have gone to complete unstable on that box. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] strange error during boot
on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 2:26 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 2:05 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 10:52 am, John covici wrote: Hi. I just upgraded a gentoo system from about August 2008 to current -- including updating baselayout and openrt and now when I boot I get a series of messages quite early in the boot modprobe: fatal /sys is not mounted. Eventually it does boot and all seems to work with the exception of the script for my hsfmodem, but I am curious as to what those message mean and if there is a way to fix them. Any assistance would be appreciated. Did you include sysfs support to your kernel and do you have a directory '/sys'? (SYSFS) This can be found in: File systems / Pseudo filesystems in the kernel configuration. The '/sys' filesystem is as important as '/proc' these days. The plot thickens -- by the time I log in after booting, /sys is mounted with the correct file system. Still very strange. Hmm... so, something does solve the problem you are seeing at the beginning later on. Did you update all the configuration files (including the ones in /etc/init.d/.. )? It could be that something there is not set correctly. For now, I am assuming the issue is in the boot-sequence/runlevel. Can you check which services are in your boot-runlevel? I have: bootmisc, checkfs, checkroot, clock, consolefone, hostname, keymaps, localmount, modules, net.lo rmnologin and urandom. Think these are the default ones. Do you use an initrd? If yes, did you update this as well? I regenerated the initrd, but I am still using 2.6.20 kernel which I will update soon, but I wonder if this is the problem -- something wrong with the initrd, but regenerating did not fix it. In my boot level I have bootmisc@ consolefont@ device-mapper@ fsck@ hibernate-cleanup@ hostname@ hwclock@ keymaps@ localmount@ modules@ mtab@ net.lo@ procfs@ root@ swap@ sysctl@ termencoding@ urandom@ in my sysinit I have devfs@ dmesg@ udev@ Do you have device-mapper in your boot-level? In that case, you might want to check which init-script mounts the '/sys' filesystem as this script requires the /sys filesystem to be mounted. May I ask why you have this added as I don't use it with my LVM drives. I don't really need it, but it was auto added by the ebuild. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] strange error during boot
On Thu, Feb 12, 2009 at 11:52:20AM -0500, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 3:21 pm, Momesso Andrea wrote: On Thu, Feb 12, 2009 at 02:44:15PM +0100, Joost Roeleveld wrote: On Thu, February 12, 2009 2:26 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 2:05 pm, John covici wrote: on Thursday 02/12/2009 Joost Roeleveld(jo...@antarean.org) wrote On Thu, February 12, 2009 10:52 am, John covici wrote: Hi. I just upgraded a gentoo system from about August 2008 to current -- including updating baselayout and openrt and now when I boot I get a series of messages quite early in the boot modprobe: fatal /sys is not mounted. Eventually it does boot and all seems to work with the exception of the script for my hsfmodem, but I am curious as to what those message mean and if there is a way to fix them. Any assistance would be appreciated. Did you include sysfs support to your kernel and do you have a directory '/sys'? (SYSFS) This can be found in: File systems / Pseudo filesystems in the kernel configuration. The '/sys' filesystem is as important as '/proc' these days. The plot thickens -- by the time I log in after booting, /sys is mounted with the correct file system. Still very strange. Hmm... so, something does solve the problem you are seeing at the beginning later on. Did you update all the configuration files (including the ones in /etc/init.d/.. )? It could be that something there is not set correctly. For now, I am assuming the issue is in the boot-sequence/runlevel. Can you check which services are in your boot-runlevel? I have: bootmisc, checkfs, checkroot, clock, consolefone, hostname, keymaps, localmount, modules, net.lo rmnologin and urandom. Think these are the default ones. Do you use an initrd? If yes, did you update this as well? I regenerated the initrd, but I am still using 2.6.20 kernel which I will update soon, but I wonder if this is the problem -- something wrong with the initrd, but regenerating did not fix it. In my boot level I have bootmisc@ consolefont@ device-mapper@ fsck@ hibernate-cleanup@ hostname@ hwclock@ keymaps@ localmount@ modules@ mtab@ net.lo@ procfs@ root@ swap@ sysctl@ termencoding@ urandom@ in my sysinit I have devfs@ dmesg@ udev@ Do you have device-mapper in your boot-level? In that case, you might want to check which init-script mounts the '/sys' filesystem as this script requires the /sys filesystem to be mounted. May I ask why you have this added as I don't use it with my LVM drives. http://bugs.gentoo.org/show_bug.cgi?id=258442 Helpful, but only if OP is using module-init-tools 3.6, which is currently in unstable for all archs. John, can you please confirm which 'module-init-tools' version you are using? Its 3.6 -- I have gone to complete unstable on that box. Until the bug gets fixed, mask current version, do the downgrade, and reboot. The same problem happened this morning to a guy in #gentoo-it on freenode, and was solved this way. === TopperH === pgpY9TdTqSiH3.pgp Description: PGP signature
Re: [gentoo-user] python-2.5.2-r7 build problems
On Thu, 12 Feb 2009 06:20:28 -0800, Mark Knecht wrote: You have more aggressive flags on the failing machine, have you tried using the more conservative (less ricey) flags? I have not and intend to do that today. The flags have been set like this since 2003 so I'm surprised that it might be something like this but it's clearly possible. I'm unqualified to say what part of the differences is making this set more aggressive. Line by line what's your opinion? -O3 vs -O2 ? Not much difference. -march=athlon-xp vs -march=i686 The former is better, providing you're using an AthlonXP. -funroll-loops You only have to look at http://funroll-loops.org/ to know this is a bad option... not using -fomit-frame-pointer That's pretty safe, the frame-pointer isn't much use anyway if you're compiling without debug symbols, which most build do by default. Strange taht after 6-years this would come up but stranger thing happen. Indeed. -- Neil Bothwick Obscenity is the crutch of inarticulate motherfuckers. signature.asc Description: PGP signature
Re: [gentoo-user] qt-xxx-4.5.0_rc1 conflicts
On Donnerstag 12 Februar 2009, Mark Knecht wrote: On Thu, Feb 12, 2009 at 7:44 AM, Volker Armin Hemmann volkerar...@googlemail.com wrote: SNIP it turned kde 4.2 in a complete crash fest (starting with kdmgreet making it impossible to log in). beta was bad, rc1 was worse. And yes, I rebuilt stuff - and after that I downgraded to 4.4. and rebuild everything again - and oh look not one single crash since then - took only 6 hours of my life. Did you rebuild KDE or do you mean just running it after the qt build finished? both. With and without rebuilding kde was a crash fest.
Re: [gentoo-user] Re: qt-xxx-4.5.0_rc1 conflicts
On Donnerstag 12 Februar 2009, Nikos Chantziaras wrote: Volker Armin Hemmann wrote: [...] it turned kde 4.2 in a complete crash fest (starting with kdmgreet making it impossible to log in). beta was bad, rc1 was worse. And yes, I rebuilt stuff - and after that I downgraded to 4.4. and rebuild everything again - and oh look not one single crash since then - took only 6 hours of my life. I don't see a bug report about it. Where did you file it? I did not file a bug because I found that it is a known problem of KDE.
[gentoo-user] emerge on new install has die econf failed
Hey Folks: I am building a new system, and the install is done, and I emerged a few things, vim for instance, and they went OK. Then I tried to emerge ntp apache samba postgresql php and I got --- ERROR: dev-libs/libpcre-7.8 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2345: Called econf '--with-match-limit-recursion=8192' '--enable-utf8' '--enable-unicode-properties' '--enable-cpp' '--enable-pcregrep-libz' '--enable-pcregrep-libbz2' '--enable-static' '--htmldir=/usr/share/doc/libpcre-7.8/html' '--docdir=/usr/share/doc/libpcre-7.8' * ebuild.sh, line 529: Called die * The specific snippet of code: * die econf failed * The die message: * econf failed -- then I tried to emerge ntp alone and got: - * ERROR: net-misc/ntp-4.2.4_p6 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2099: Called econf '--disable-linuxcaps' '--disable-parse-clocks' '--enable-ipv6' '--disable-debugging' '--with-crypto' * ebuild.sh, line 529: Called die * The specific snippet of code: * die econf failed * The die message: * econf failed - If I need to post additional info, just let me know, I haven't done this before so I'll need a little tutoring. Thanks - Joseph
Re: [gentoo-user] emerge on new install has die econf failed
Joseph Davis написав(ла): Hey Folks: I am building a new system, and the install is done, and I emerged a few things, vim for instance, and they went OK. Then I tried to emerge ntp apache samba postgresql php and I got --- ERROR: dev-libs/libpcre-7.8 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2345: Called econf '--with-match-limit-recursion=8192' '--enable-utf8' '--enable-unicode-properties' '--enable-cpp' '--enable-pcregrep-libz' '--enable-pcregrep-libbz2' '--enable-static' '--htmldir=/usr/share/doc/libpcre-7.8/html' '--docdir=/usr/share/doc/libpcre-7.8' * ebuild.sh, line 529: Called die * The specific snippet of code: * die econf failed * The die message: * econf failed -- then I tried to emerge ntp alone and got: - * ERROR: net-misc/ntp-4.2.4_p6 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2099: Called econf '--disable-linuxcaps' '--disable-parse-clocks' '--enable-ipv6' '--disable-debugging' '--with-crypto' * ebuild.sh, line 529: Called die * The specific snippet of code: * die econf failed * The die message: * econf failed - If I need to post additional info, just let me know, I haven't done this before so I'll need a little tutoring. Thanks - Joseph You must see what package prevents emerging in previous messages in terminal near first make [Error 1] etc. When I tried to compile kcontrol for amarok, I have got similar messages until reemerging kde-libs. -- Alexander Pilipovsky aka Engraver
[gentoo-user] Commenting out multiple lines in vim
Hi there, I can find numerous references on the net to this behaviour: In vim, you can just select the rectangular region with Ctrl-v, then type I#ESC. This will insert # in each line at the same column. Very convenient. EG: http://mail.python.org/pipermail/python-list/2001-May/084540.html http://hurley.wordpress.com/2007/06/13/vim-tip-comment-out-multiple-lines/ Yet it doesn't seem to work on any of my Gentoo systems. Is this something that is caused by a Gentoo-specific /etc/vimrc or has vim evolved? Any comments gratefully received. Stroller.
Re: [gentoo-user] Commenting out multiple lines in vim
Stroller ???(??): Hi there, I can find numerous references on the net to this behaviour: In vim, you can just select the rectangular region with Ctrl-v, then type I#ESC. This will insert # in each line at the same column. Very convenient. EG: http://mail.python.org/pipermail/python-list/2001-May/084540.html http://hurley.wordpress.com/2007/06/13/vim-tip-comment-out-multiple-lines/ Yet it doesn't seem to work on any of my Gentoo systems. Is this something that is caused by a Gentoo-specific /etc/vimrc or has vim evolved? Any comments gratefully received. Stroller. Exuse me, but it works on my computer :) And thanks about this topic, I didn't know about this feature! I selected region by Ctrl-v, pressed Shift-I and white selection disappeared, I pressed # and ESC and got this effect... My vimrc: scriptencoding utf-8 ^^ Please leave the above line at the start of the file. Default configuration file for Vim $Header: /var/cvsroot/gentoo-x86/app-editors/vim-core/files/vimrc-r3,v 1.1 2006/03/25 20:26:27 genstef Exp $ Written by Aron Griffis agrif...@gentoo.org Modified by Ryan Phillips rphill...@gentoo.org Modified some more by Ciaran McCreesh ciar...@gentoo.org Added Redhat's vimrc info by Seemant Kulleen seem...@gentoo.org You can override any of these settings on a global basis via the /etc/vim/vimrc.local file, and on a per-user basis via ~/.vimrc. You may need to create these. {{{ General settings The following are some sensible defaults for Vim for most users. We attempt to change as little as possible from Vim's defaults, deviating only where it makes sense set nocompatible Use Vim defaults (much better!) set bs=2 Allow backspacing over everything in insert mode set ai Always set auto-indenting on set history=50 keep 50 lines of command history set rulerShow the cursor position all the time set viminfo='20,\500Keep a .viminfo file. Don't use Ex mode, use Q for formatting map Q gq When doing tab completion, give the following files lower priority. You may wish to set 'wildignore' to completely ignore files, and 'wildmenu' to enable enhanced tab completion. These can be done in the user vimrc file. set suffixes+=.info,.aux,.log,.dvi,.bbl,.out,.o,.lo When displaying line numbers, don't use an annoyingly wide number column. This doesn't enable line numbers -- :set number will do that. The value given is a minimum width to use for the number column, not a fixed size. if v:version = 700 set numberwidth=3 endif }}} {{{ Modeline settings We don't allow modelines by default. See bug #14088 and bug #73715. If you're not concerned about these, you can enable them on a per-user basis by adding set modeline to your ~/.vimrc file. set nomodeline }}} {{{ Locale settings Try to come up with some nice sane GUI fonts. Also try to set a sensible value for fileencodings based upon locale. These can all be overridden in the user vimrc file. if v:lang =~? ^ko set fileencodings=euc-kr set guifontset=-*-*-medium-r-normal--16-*-*-*-*-*-*-* elseif v:lang =~? ^ja_JP set fileencodings=euc-jp set guifontset=-misc-fixed-medium-r-normal--14-*-*-*-*-*-*-* elseif v:lang =~? ^zh_TW set fileencodings=big5 set guifontset=-sony-fixed-medium-r-normal--16-150-75-75-c-80-iso8859-1,-taipei-fixed-medium-r-normal--16-150-75-75-c-160-big5-0 elseif v:lang =~? ^zh_CN set fileencodings=gb2312 set guifontset=*-r-* endif If we have a BOM, always honour that rather than trying to guess. if fileencodings !~? ucs-bom set fileencodings^=ucs-bom endif Always check for UTF-8 when trying to determine encodings. if fileencodings !~? utf-8 set fileencodings+=utf-8 endif Make sure we have a sane fallback for encoding detection set fileencodings+=default }}} {{{ Syntax highlighting settings Switch syntax highlighting on, when the terminal has colors Also switch on highlighting the last used search pattern. if t_Co 2 || has(gui_running) syntax on set hlsearch endif }}} {{{ Terminal fixes if term ==? xterm set t_Sb=^[4%dm set t_Sf=^[3%dm set ttymouse=xterm2 endif if term ==? gnome has(eval) Set useful keys that vim doesn't discover via termcap but are in the builtin xterm termcap. See bug #122562. We use exec to avoid having to include raw escapes in the file. exec set C-Left=\eO5D exec set C-Right=\eO5C endif }}} {{{ Filetype plugin settings Enable plugin-provided filetype settings, but only if the ftplugin directory exists (which it won't on livecds, for example). if isdirectory(expand($VIMRUNTIME/ftplugin)) filetype plugin on Uncomment the next line (or copy to your ~/.vimrc) for plugin-provided indent settings. Some people don't like these, so we won't turn them on by default. filetype indent on endif }}} {{{ Fix shell, see bug #101665. if == shell if executable(/bin/bash) set shell=/bin/bash elseif executable(/bin/sh) set
Re: [gentoo-user] Commenting out multiple lines in vim
On 12 Feb 2009, at 20:16, Alexander Pilipovsky wrote: Stroller написав(ла): Hi there, I can find numerous references on the net to this behaviour: In vim, you can just select the rectangular region with Ctrl-v, then type I#ESC. This will insert # in each line at the same column. Very convenient. ... Exuse me, but it works on my computer :) And thanks about this topic, I didn't know about this feature! I selected region by Ctrl-v, pressed Shift-I and white selection disappeared, I pressed # and ESC and got this effect... Blimey! I overlooked the instruction to use the escape key! Having recently made a resolution to take better advantage of vim's features I have only just learned selection using shift-v, so had to test again using ctrl-v before posting. I also tried both combinations using just i and also shift-I. *slaps self* Stroller.
Re: [gentoo-user] Commenting out multiple lines in vim
On Thu, Feb 12, 2009 at 07:53:30PM +, Stroller wrote: Hi there, I can find numerous references on the net to this behaviour: In vim, you can just select the rectangular region with Ctrl-v, then type I#ESC. This will insert # in each line at the same column. Very convenient. EG: http://mail.python.org/pipermail/python-list/2001-May/084540.html http://hurley.wordpress.com/2007/06/13/vim-tip-comment-out-multiple-lines/ Yet it doesn't seem to work on any of my Gentoo systems. Is this something that is caused by a Gentoo-specific /etc/vimrc or has vim evolved? Couple of things to check: - you're running vim not vi or vim-tiny which has a bunch of behaviour removed. Ensure that syntax highlighting works for example is what I do to make sure. ESC :help will show your version also - ensure you're not running with the 'compatible' setting. ESC :set nocompatible will make sure this is off Alan -- Alan a...@ufies.org - http://arcterex.net Beware of computer programmers that carry screwdrivers. -- Unknown
[gentoo-user] ibiblio dumps Gentoo distfiles to save space
Imagine my surprise when the nightly rsync of Gentoo distfiles with ibibilo resulted in my distfile repository getting totally deleted. After a few emails wit the admins at ibibilo I finally got the answer that I was looking for... the truth... Jerry, We are no longer rsyncing the distfiles due to space constraints on our distributions volume. Gentoo's own instructions for setting up a mirror recommend excluding the distfiles directory: http://www.gentoo.org/doc/en/rsync.xml If you need these files, you could try the other mirrors listed on this page: http://www.gentoo.org/main/en/mirrors2.xml Best, Matt I promptly emailed back an offer of two new 1,000 gig drives if they would put the gentoo distfiles back up and... no answer Guess they really don't care. -- * From the desk of: Jerome D. McBride 17:17:08 up 57 days, 23:24, 5 users, load average: 0.14, 0.09, 0.02 *
Re: [gentoo-user] emerge on new install has die econf failed
Alexander Pilipovsky wrote: Joseph Davis написав(ла): Hey Folks: I am building a new system, and the install is done, and I emerged a few things, vim for instance, and they went OK. Then I tried to emerge ntp apache samba postgresql php and I got --- ERROR: dev-libs/libpcre-7.8 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2345: Called econf '--with-match-limit-recursion=8192' '--enable-utf8' '--enable-unicode-properties' '--enable-cpp' '--enable-pcregrep-libz' '--enable-pcregrep-libbz2' '--enable-static' '--htmldir=/usr/share/doc/libpcre-7.8/html' '--docdir=/usr/share/doc/libpcre-7.8' * ebuild.sh, line 529: Called die * The specific snippet of code: * die econf failed * The die message: * econf failed -- then I tried to emerge ntp alone and got: - * ERROR: net-misc/ntp-4.2.4_p6 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2099: Called econf '--disable-linuxcaps' '--disable-parse-clocks' '--enable-ipv6' '--disable-debugging' '--with-crypto' * ebuild.sh, line 529: Called die * The specific snippet of code: * die econf failed * The die message: * econf failed - If I need to post additional info, just let me know, I haven't done this before so I'll need a little tutoring. Thanks - Joseph You must see what package prevents emerging in previous messages in terminal near first make [Error 1] etc. When I tried to compile kcontrol for amarok, I have got similar messages until reemerging kde-libs. I looked as you suggested, and this is what I found - I'm still clueless. which: no gtkdoc-rebase in (/usr/local/sbin:/sbin:/usr/sbin:/usr/lib/portage/bin:/usr/local/bin:/bin:/usr/bin:/opt/bin:/usr/i486-pc-linux-gnu/gcc-bin/4.1.2) make[5]: [install-data-local] Error 1 (ignored) make[5]: Leaving directory `/var/tmp/portage/dev-libs/glib-2.16.5/work/glib-2.16.5/docs/reference/gobject' make[4]: Leaving directory `/var/tmp/portage/dev-libs/glib-2.16.5/work/glib-2.16.5/docs/reference/gobject' Making install in gio make[4]: Entering directory `/var/tmp/portage/dev-libs/glib-2.16.5/work/glib-2.16.5/docs/reference/gio' make[5]: Entering directory `/var/tmp/portage/dev-libs/glib-2.16.5/work/glib-2.16.5/docs/reference/gio' make[5]: Nothing to be done for `install-exec-am'. installfiles=`echo ./html/*`; \ if test $installfiles = './html/*'; \ then echo '-- Nothing to install' ; \ else \ /bin/sh ../../../mkinstalldirs /var/tmp/portage/dev-libs/glib-2.16.5/image//usr/share/gtk-doc/html/gio; \ for i in $installfiles; do \ echo '-- Installing '$i ; \ /usr/bin/install -c -m 644 $i /var/tmp/portage/dev-libs/glib-2.16.5/image//usr/share/gtk-doc/html/gio; \ done; \ echo '-- Installing ./html/index.sgml' ; \ /usr/bin/install -c -m 644 ./html/index.sgml /var/tmp/portage/dev-libs/glib-2.16.5/image//usr/share/gtk-doc/html/gio || :; \ which gtkdoc-rebase /dev/null \ gtkdoc-rebase --relative --dest-dir=/var/tmp/portage/dev-libs/glib-2.16.5/image/ --html-dir=/var/tmp/portage/dev-libs/glib-2.16.5/image//usr/share/gtk-doc/html/gio ; \ fi mkdir -p -- /var/tmp/portage/dev-libs/glib-2.16.5/image//usr/share/gtk-doc/html/gio -- Installing ./html/GAppInfo.html
[gentoo-user] Re: qt-xxx-4.5.0_rc1 conflicts
Volker Armin Hemmann wrote: On Donnerstag 12 Februar 2009, Nikos Chantziaras wrote: Volker Armin Hemmann wrote: [...] it turned kde 4.2 in a complete crash fest (starting with kdmgreet making it impossible to log in). beta was bad, rc1 was worse. And yes, I rebuilt stuff - and after that I downgraded to 4.4. and rebuild everything again - and oh look not one single crash since then - took only 6 hours of my life. I don't see a bug report about it. Where did you file it? I did not file a bug because I found that it is a known problem of KDE. Hmm. No crashes here yet. Is it just me, or do fonts look somehow different with Qt 4.5? Not worse nor better. Just different. Or maybe it's my eyes playing tricks.
Re: [gentoo-user] ibiblio dumps Gentoo distfiles to save space
On Feb 12, 2009, at 5:23 PM, Jerry McBride mcbrid...@comcast.net wrote: Imagine my surprise when the nightly rsync of Gentoo distfiles with ibibilo resulted in my distfile repository getting totally deleted. After a few emails wit the admins at ibibilo I finally got the answer that I was looking for... the truth... Jerry, We are no longer rsyncing the distfiles due to space constraints on our distributions volume. Gentoo's own instructions for setting up a mirror recommend excluding the distfiles directory: http://www.gentoo.org/doc/en/rsync.xml If you need these files, you could try the other mirrors listed on this page: http://www.gentoo.org/main/en/mirrors2.xml Best, Matt I promptly emailed back an offer of two new 1,000 gig drives if they would put the gentoo distfiles back up and... no answer Guess they really don't care. -- *** *** *** From the desk of: Jerome D. McBride 17:17:08 up 57 days, 23:24, 5 users, load average: 0.14, 0.09, 0.02 *** *** *** There are quite a few mirrors available to sync from; so one's dropped support, it's a drop in the bucket. I'll admit, space concerns seem to be a bit odd of a complaint, maybe it was more along the lines of hosting fees? After all, a distribution server isn't exactly a low- bandwidth operation.
Re: [gentoo-user] emerge on new install has die econf failed
On Thu, 12 Feb 2009 16:36:31 -0600 Joseph Davis jos...@uh.edu wrote: I looked as you suggested, and this is what I found - I'm still clueless. which: no gtkdoc-rebase in (/usr/local/sbin:/sbin:/usr/sbin:/usr/lib/portage/bin:/usr/local/bin:/bin:/usr/bin:/opt/bin:/usr/i486-pc-linux-gnu/gcc-bin/4.1.2) make[5]: [install-data-local] Error 1 (ignored) Looks like non-critical error to me, something else probably happened even before that one. -- Mike Kazantsev // fraggod.net signature.asc Description: PGP signature
Re: [gentoo-user] Commenting out multiple lines in vim
090212 Stroller quoted: In vim, you can just select the rectangular region with Ctrl-v, then type I#ESC. This will insert # in each line at the same column. If you want to comment a series of lines m-n , it's quicker to do : :m,ns/^/#/ -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] AMD Turion64x2 CFLAGS
2009/2/12 Volker Armin Hemmann volkerar...@googlemail.com: On Donnerstag 12 Februar 2009, Zhang Jun wrote: Hi list, my laptop's cpu is AMD Turion64x2, I've installed both 32bits Debian testing and Gentoo on it, from Debian there is no SSE3 in /proc/cpuinfo, I am sure there is. But it is called 'pni' - its original name. and I used CFLAGS=-O2 -march=athlon-xp -fomit-frame-pointer -pipe on gentoo, and I can not see SSE3 in cpuinfo also, I emerged x86info, and SSE3 is in its output: #x86info x86info v1.21. Dave Jones 2001-2007 Feedback to da...@redhat.com. Found 2 CPUs -- CPU #1 Family: 15 Model: 72 Stepping: 2 CPU Model : Turion 64 X2 (BH-F2) Processor name string: AMD Turion(tm) 64 X2 Mobile Technology TL-52 Feature flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflsh mmx fxsr sse sse2 ht sse3 cmpxchg16b Extended feature flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 nx mmxext mmx fxsr ffxsr rdtscp lm 3dnowext 3dnow lahf/sahf CmpLegacy svm ExtApicSpace LockMovCr0 SVM: revision 1, 64 ASIDs Address Size: 48 bits virtual, 40 bits physical The physical package has 2 of 2 possible cores implemented. ... ... my question is: I can not see SSE3 in cpuinfo because I did not use -msse3 in CFLAGS ? no. Because it is called 'pni'. How about this cflags: march=k8-sse3 -O2 -msse3 (in case march gets filtered) -pipe ? on amd64 fomit-frame-pointer isn't needed anymore. thanks, I will add sse3 in my make.conf
Re: [gentoo-user] Can't login from terminal?
Hi, thanks! Looks like the system is unable to launch a shell for some reason, prehaps you can change it to something default, like /bin/sh, or just something else if it's bash already. Could you please give more details? How to change it to something default? Also, I'd double-check the logs - if something fails, there shoud be a message about it. Make sure you have syslog daemon running and not dropping any debug messages. I have checked the /var/log/faillog, which I'm not sure whether it's the right log file, and seems it only contain binary data(I read it from vi /var/log/faillog). -- wcw
Re: [gentoo-user] Commenting out multiple lines in vim
On 13 Feb 2009, at 00:53, Philip Webb wrote: 090212 Stroller quoted: In vim, you can just select the rectangular region with Ctrl-v, then type I#ESC. This will insert # in each line at the same column. If you want to comment a series of lines m-n , it's quicker to do : :m,ns/^/#/ I saw similar comments in my Google searches, but I am flummoxed how one could find it so. Is it only on my keyboard that forward-slash is a lower-case character that is accessed *without* the shift key deployed? How do you know m n? Surely it's easier just to highlight the lines? Stroller.
Re: [gentoo-user] ibiblio dumps Gentoo distfiles to save space
On 12 Feb 2009, at 22:23, Jerry McBride wrote: ... I promptly emailed back an offer of two new 1,000 gig drives if they would put the gentoo distfiles back up and... no answer Guess they really don't care. Is distfiles not all stuff that one would normally get from (for example) SourceForge its mirrors, anyway? The docs do seem to clearly indicate that distfiles should be omitted. Considering the cost of 1TB SCSI drives your offer was remarkably generous - I will be glad to take these disk off your hands if no-one else will. ;) Stroller.
Re: [gentoo-user] ibiblio dumps Gentoo distfiles to save space
On Thu, Feb 12, 2009 at 20:23, Jerry McBride mcbrid...@comcast.net wrote: Imagine my surprise when the nightly rsync of Gentoo distfiles with ibibilo resulted in my distfile repository getting totally deleted. After a few emails wit the admins at ibibilo I finally got the answer that I was looking for... the truth... Jerry, We are no longer rsyncing the distfiles due to space constraints on our distributions volume. Gentoo's own instructions for setting up a mirror recommend excluding the distfiles directory: http://www.gentoo.org/doc/en/rsync.xml If you need these files, you could try the other mirrors listed on this page: http://www.gentoo.org/main/en/mirrors2.xml Best, Matt I promptly emailed back an offer of two new 1,000 gig drives if they would put the gentoo distfiles back up and... no answer Guess they really don't care. Isn't default portage behavior NOT to sync distfiles? Some distfiles are hosted on mirrors not related to gentoo, others have no mirrors at all, leaving a single server to download from, so, I can't think of a reason to sync this specific folder, other than being a mirror yourself (is that the case?). -- Daniel da Veiga
Re: [gentoo-user] Commenting out multiple lines in vim
On 13.02.2009 07:48, Stroller wrote: On 13 Feb 2009, at 00:53, Philip Webb wrote: 090212 Stroller quoted: In vim, you can just select the rectangular region with Ctrl-v, then type I#ESC. This will insert # in each line at the same column. If you want to comment a series of lines m-n , it's quicker to do : :m,ns/^/#/ I saw similar comments in my Google searches, but I am flummoxed how one could find it so. Is it only on my keyboard that forward-slash is a lower-case character that is accessed *without* the shift key deployed? How do you know m n? Column and line numbers are shown on the lower right part of the screen. Surely it's easier just to highlight the lines? Not when you are working with the keyboard most of the time. Taking your hands off the keyboard to use the mouse is time consuming and becomes rather annoying. -- Eray
Re: [gentoo-user] Can't login from terminal?
On Fri, 13 Feb 2009 13:15:12 +0800 Chuanwen Wu wcw8...@gmail.com wrote: Could you please give more details? How to change it to something default? Well, that's pretty much the basics... Shells for each system user are defined in /etc/passwd, which should be edited by 'vipw' command. What I've meant is the case, when you, or something else changed '/etc/passwd', replacing '/bin/bash' with something like '/sbin/nologin' or some other path, which is not a valid shell. Actually, ssh shouldn't work with invalid shell like that as well, but one, for example, can add some commands to .bashrc which will work only in ssh environment (using some env vars, set by ssh, for example). Then, there might be some ssh-only shell, so I'd suggest to set shell to '/bin/sh' (which is actually bash, for gentoo) and disable all the configs it's using, like '~/.bashrc' or '/etc/bashrc' (see 'man bash', for full list). Also, Neil has made a good point that there might be something in /etc/profile, which is usually sourced by all bash-like shells. I have checked the /var/log/faillog, which I'm not sure whether it's the right log file, and seems it only contain binary data(I read it from vi /var/log/faillog). Syslog usually uses '/var/log/messages' as a collector for everything that is being sent to it, so I'd check that file first. And make sure the timestamps there are recent - it should mean that syslog is writing to it and is not dead. 'dmesg' command is usually a good source for failure messages too, but only on kernel level (when something really nasty happens). There might be some segfaults, produced by your shell, and usually indicate programming or compilation errors. -- Mike Kazantsev // fraggod.net
Re: [gentoo-user] Can't login from terminal?
HI, thanks! On Fri, Feb 13, 2009 at 3:11 PM, Mike Kazantsev mike_kazant...@fraggod.net wrote: On Fri, 13 Feb 2009 13:15:12 +0800 Chuanwen Wu wcw8...@gmail.com wrote: Could you please give more details? How to change it to something default? Well, that's pretty much the basics... Shells for each system user are defined in /etc/passwd, which should be edited by 'vipw' command. What I've meant is the case, when you, or something else changed '/etc/passwd', replacing '/bin/bash' with something like '/sbin/nologin' or some other path, which is not a valid shell. Hi, here is the root infomation in my /etc/passwd: root:x:0:0:root:/root:/bin/bash Actually, ssh shouldn't work with invalid shell like that as well, but one, for example, can add some commands to .bashrc which will work only in ssh environment (using some env vars, set by ssh, for example). Then, there might be some ssh-only shell, so I'd suggest to set shell to '/bin/sh' (which is actually bash, for gentoo) and disable all the configs it's using, like '~/.bashrc' or '/etc/bashrc' (see 'man bash', for full list). In the /root, there is no .bashrc, and in other users' home, the .bashrc is normal: /*** $ cat /home/wcw/.bashrc # /etc/skel/.bashrc # # This file is sourced by all *interactive* bash shells on startup, # including some apparently interactive shells such as scp and rcp # that can't tolerate any output. So make sure this doesn't display # anything or bad things will happen ! # Test for an interactive shell. There is no need to set anything # past this point for scp and rcp, and it's important to refrain from # outputting anything in those cases. if [[ $- != *i* ]] ; then # Shell is non-interactive. Be done now! return fi # Put your fun stuff here. /*/ Also, Neil has made a good point that there might be something in /etc/profile, which is usually sourced by all bash-like shells. Here is my /etc/profile, which I think is normal, too: /*/ # cat /etc/profile # /etc/profile: login shell setup # # That this file is used by any Bourne-shell derivative to setup the # environment for login shells. # # Load environment settings from profile.env, which is created by # env-update from the files in /etc/env.d if [ -e /etc/profile.env ] ; then . /etc/profile.env fi # 077 would be more secure, but 022 is generally quite realistic umask 022 # Set up PATH depending on whether we're root or a normal user. # There's no real reason to exclude sbin paths from the normal user, # but it can make tab-completion easier when they aren't in the # user's PATH to pollute the executable namespace. # # It is intentional in the following line to use || instead of -o. # This way the evaluation can be short-circuited and calling whoami is # avoided. if [ $EUID = 0 ] || [ $USER = root ] ; then PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:${ROOTPATH} else PATH=/usr/local/bin:/usr/bin:/bin:${PATH} fi export PATH unset ROOTPATH # Extract the value of EDITOR [ -z $EDITOR ] EDITOR=`. /etc/rc.conf 2/dev/null; echo $EDITOR` [ -z $EDITOR ] EDITOR=/bin/nano export EDITOR if [ -n ${BASH_VERSION} ] ; then # Newer bash ebuilds include /etc/bash/bashrc which will setup PS1 # including color. We leave out color here because not all # terminals support it. if [ -f /etc/bash/bashrc ] ; then # Bash login shells run only /etc/profile # Bash non-login shells run only /etc/bash/bashrc # Since we want to run /etc/bash/bashrc regardless, we source it # from here. It is unfortunate that there is no way to do # this *after* the user's .bash_profile runs (without putting # it in the user's dot-files), but it shouldn't make any # difference. . /etc/bash/bashrc else PS1='\...@\h \w \$ ' fi else # Setup a bland default prompt. Since this prompt should be useable # on color and non-color terminals, as well as shells that don't # understand sequences such as \h, don't put anything special in it. PS1=`whoa...@`uname -n | cut -f1 -d.` \$ fi for sh in /etc/profile.d/*.sh ; do if [ -r $sh ] ; then . $sh fi done unset sh /*/ Syslog usually uses '/var/log/messages' as a collector for everything that is being sent to it, so I'd check that file first. And make sure the timestamps there are recent - it should mean that syslog is writing to it and is not dead. I got the login information below from the tail of /var/log/messages: // Feb 13 15:47:18 Gentoo-F304-Server login[5735]: pam_unix(login:session): session opened