[gentoo-user] Re: Anyone setup Gentoo on an Archos 101
Eliezer Croitoru eliezer at ngtech.co.il writes: http://www.archos.com/products/ta/archos_101it/tabletpc.html?country=kglang=en i have one and i dont want to risk it's usage with gentoo. This is the first I've heard of Archos, and it seems to me like a great idea. The company says you can install any OS you want, and you can even dual-boot OS's -- so that *seems* to imply that you can re-install the factory OS if your experiments go bad. Am I being too optimistic here? well it's kind of more then simple to restore cause they have some bios like thing that you can restore the device basic os with it. but the thing is that it works with initramfs and some rootfs that i dont even know how to understand. Thanks for the input. I'll have to ponder this a bit more. James
[gentoo-user]Upgrade to gnome 3.2
Did anyone has some good ideas to upgrade the gnome to 3.2 ? I followed the Upgrade to Gnome 3.2 Guide , but i confused that it seems didn't say howto upgrade to Gnome 3.2 , Can anyone give me some idea? -- 好好学习，天天向上！！！
Re: [gentoo-user]Upgrade to gnome 3.2
Hi, To install gnome 3.2, make sure that you attached 3D-acceleration graphic card in your machine or not. if no problem just run emerge -p gnome as a root or sudo emerge -p gnome as a normal user to check what is yout own flag(feature). of course you can refer my make.conf to find what use flag is used. my make.conf is attached in this message. 2012/4/26 赵佳晖 jiahui.tar...@gmail.com: Did anyone has some good ideas to upgrade the gnome to 3.2 ? I followed the Upgrade to Gnome 3.2 Guide , but i confused that it seems didn't say howto upgrade to Gnome 3.2 , Can anyone give me some idea? -- 好好学习，天天向上！！！ make.conf Description: Binary data
[gentoo-user] Setting basic ALSA defaults
Hi guys,
I've got a a little nettop which I'm trying to set up for XBMC. As I don't
normally use Linux on the desktop, but primarily for headless servers, this has
been a little bit of a journey for me, but I now have X11 and the nVidia
drivers working, and basic audio playback.
So this particular system (eMachines 1401) defaults to the headphone output,
and I've learned that to get it to output over HDMI I have to run:
aplay -vvD plug:hdmi file.wav
I also, then, have to enter alsamixer and unmute the S/PDIF 1 output (that
seems to be muted by default on this system) and audio starts coming through on
the TV.
So I want to set, of course, HDMI as the default output, so I created an
/etc/asound.conf and put the following in it:
pcm.!default {
type hw
card 0
device 3
}
ctl.!default {
type hw
card 0
device 3
}
This is great! Now when I run aplay I can omit the -D $devicename flag and
everything's good.
Now I have to admit, I figured out the above more or less by trial and error
(that, for instance, I can't describe the output as card 0,3, but I have to
have the separate device line), and the pcm and ctl parts, and the
structure I just copied of the documentation at the ALSA website. I don't find
that documentation very clear.
So this is problematic the next time I reboot, because all of a sudden, now
alsamixer doesn't work. In fact, I can demonstrate that the problem is related
directly to this file:
# alsamixer
cannot open mixer: Invalid argument
# rm /etc/asound.conf
# alsamixer
# echo $?
0
#
So could anyone possibly explain this for me, please?
I'm liable to have another question or two in a moment, but I'd initially just
really love to understand why the alsa documentation says to have separate
pcm.!default and ctl.!default definitions (instead of a single
everything.!default) and why alsamixer has now broke.
Many thanks in advance for any help you can offer,
Stroller.
Re: [gentoo-user] Setting basic ALSA defaults
On Wed, Apr 25, 2012 at 07:58:54PM +0100, Stroller wrote:
Hi guys,
I've got a a little nettop which I'm trying to set up for XBMC. As I don't
normally use Linux on the desktop, but primarily for headless servers, this
has been a little bit of a journey for me, but I now have X11 and the nVidia
drivers working, and basic audio playback.
So this particular system (eMachines 1401) defaults to the headphone output,
and I've learned that to get it to output over HDMI I have to run:
aplay -vvD plug:hdmi file.wav
I also, then, have to enter alsamixer and unmute the S/PDIF 1 output (that
seems to be muted by default on this system) and audio starts coming through
on the TV.
So I want to set, of course, HDMI as the default output, so I created an
/etc/asound.conf and put the following in it:
pcm.!default {
type hw
card 0
device 3
}
ctl.!default {
type hw
card 0
device 3
}
This is great! Now when I run aplay I can omit the -D $devicename flag and
everything's good.
Now I have to admit, I figured out the above more or less by trial and error
(that, for instance, I can't describe the output as card 0,3, but I have to
have the separate device line), and the pcm and ctl parts, and the
structure I just copied of the documentation at the ALSA website. I don't
find that documentation very clear.
So this is problematic the next time I reboot, because all of a sudden, now
alsamixer doesn't work. In fact, I can demonstrate that the problem is
related directly to this file:
# alsamixer
cannot open mixer: Invalid argument
# rm /etc/asound.conf
# alsamixer
# echo $?
0
#
So could anyone possibly explain this for me, please?
I'm liable to have another question or two in a moment, but I'd initially
just really love to understand why the alsa documentation says to have
separate pcm.!default and ctl.!default definitions (instead of a single
everything.!default) and why alsamixer has now broke.
Many thanks in advance for any help you can offer,
Stroller.
Just a shot in the dark here, Stroller, but I once had a problem with using
a mixer app (not alsamixer, which worked). I couldn't get it to start, and
it kept on giving an error like your's above for alsamixer. The problem was
that the kernel module, snd-mixer-oss was not loading by default, and when I
loaded that module, all was good. HTH.
Terry
[gentoo-user] 3.2.12 Kenel wont boot
Hello, OK, I manage quite a few gentoo systems. ONE of them is being a BIT _ _ ! and I cannot figure out what is obviously simple I have already migrated most system that I manage to the 3.2.12 kernel (not testing kernels for me at this time). Background: The system is an old HP AMD dual core laptop: AMD Turion(tm) 64 X2 Mobile Technology TL-56 The error message is this: Root-NFS: no NFS server address VFS: Unable to mount root fs via NFS, try floppy VFS: Cannot open root device sda4 or unknown block (2,0) Please append a correct root= boot option; here are the available partitions: oboo 1048575 sr0 driver:sr Kernel panic - not syncing : VFS : Unable to mount root fs on unknown block(2,0) PID:1,comm : swapper /0 Not tainted 3.2.12-gentoo#2 The other (3) series kernels boot and run just fine: from grub.conf: #0 title= Linux 3.2.1-gentoo root(hd0,1) kernel /boot/kernel-3.2.1-gentoo root=/dev/sda4 #1 title= Linux 3.2.12-gentoo root(hd0,1) kernel /boot/kernel-3.2.12-gentoo root=/dev/sda4 #2 title= Linux 3.0.6-gentoo root(hd0,1) kernel /boot/kernel-3.0.6-gentoo root=/dev/sda4 I can even scp over a kernel from a single processor AMD64 laptop and it boots and runs just fine. When I make a new kernel, I do what I have done for years with Gentoo: cd /usr/src rm linux ln -sf latest.kernel linux cd linux make menuconfig save any changes make make models_install cp System.map /boot/System.map-3.2.12-gentoo cp arch/x86_64/boot/bzImage /boot/kernel-3.2.12-gentoo cp .config /boot/config-3.2.12-gentoo So all I can think of is NFS is the difference? I cannot seem to flesh out way the new kernel will not boot on this system and many others are just fine maybe I'm missing support for the sr driver ? ideas? James
Re: [gentoo-user] 3.2.12 Kenel wont boot
The error just means it cannot find any device called /dev/sda4, but can only find your CD (sr0). I get this when booting from a usbkey and I need to tell the kernel to wait 5-10 seconds before detecting hdds. I also had this error when I used a config from my normal computers onto an older computer that used IDE and PATA (these were disabled in kernel). Good luck! On Wed, Apr 25, 2012 at 4:17 PM, James wirel...@tampabay.rr.com wrote: Hello, OK, I manage quite a few gentoo systems. ONE of them is being a BIT _ _ ! and I cannot figure out what is obviously simple I have already migrated most system that I manage to the 3.2.12 kernel (not testing kernels for me at this time). Background: The system is an old HP AMD dual core laptop: AMD Turion(tm) 64 X2 Mobile Technology TL-56 The error message is this: Root-NFS: no NFS server address VFS: Unable to mount root fs via NFS, try floppy VFS: Cannot open root device sda4 or unknown block (2,0) Please append a correct root= boot option; here are the available partitions: oboo 1048575 sr0 driver:sr Kernel panic - not syncing : VFS : Unable to mount root fs on unknown block(2,0) PID:1,comm : swapper /0 Not tainted 3.2.12-gentoo#2 The other (3) series kernels boot and run just fine: from grub.conf: #0 title= Linux 3.2.1-gentoo root(hd0,1) kernel /boot/kernel-3.2.1-gentoo root=/dev/sda4 #1 title= Linux 3.2.12-gentoo root(hd0,1) kernel /boot/kernel-3.2.12-gentoo root=/dev/sda4 #2 title= Linux 3.0.6-gentoo root(hd0,1) kernel /boot/kernel-3.0.6-gentoo root=/dev/sda4 I can even scp over a kernel from a single processor AMD64 laptop and it boots and runs just fine. When I make a new kernel, I do what I have done for years with Gentoo: cd /usr/src rm linux ln -sf latest.kernel linux cd linux make menuconfig save any changes make make models_install cp System.map /boot/System.map-3.2.12-gentoo cp arch/x86_64/boot/bzImage /boot/kernel-3.2.12-gentoo cp .config /boot/config-3.2.12-gentoo So all I can think of is NFS is the difference? I cannot seem to flesh out way the new kernel will not boot on this system and many others are just fine maybe I'm missing support for the sr driver ? ideas? James
Re: [gentoo-user] 3.2.12 Kenel wont boot
well ... what is filesystem of sr? then ... did you check that filesystem item [M] instead of [*] ?? if you want to use some specific file system you may make sure whether you checked correspond filesystem by * or not. I don't know how did you set many objects but I believe that you already know what this problem causes Cheers :D Seong-ho, Cho 2012/4/26 James wirel...@tampabay.rr.com: Hello, OK, I manage quite a few gentoo systems. ONE of them is being a BIT _ _ ! and I cannot figure out what is obviously simple I have already migrated most system that I manage to the 3.2.12 kernel (not testing kernels for me at this time). Background: The system is an old HP AMD dual core laptop: AMD Turion(tm) 64 X2 Mobile Technology TL-56 The error message is this: Root-NFS: no NFS server address VFS: Unable to mount root fs via NFS, try floppy VFS: Cannot open root device sda4 or unknown block (2,0) Please append a correct root= boot option; here are the available partitions: oboo 1048575 sr0 driver:sr Kernel panic - not syncing : VFS : Unable to mount root fs on unknown block(2,0) PID:1,comm : swapper /0 Not tainted 3.2.12-gentoo#2 The other (3) series kernels boot and run just fine: from grub.conf: #0 title= Linux 3.2.1-gentoo root(hd0,1) kernel /boot/kernel-3.2.1-gentoo root=/dev/sda4 #1 title= Linux 3.2.12-gentoo root(hd0,1) kernel /boot/kernel-3.2.12-gentoo root=/dev/sda4 #2 title= Linux 3.0.6-gentoo root(hd0,1) kernel /boot/kernel-3.0.6-gentoo root=/dev/sda4 I can even scp over a kernel from a single processor AMD64 laptop and it boots and runs just fine. When I make a new kernel, I do what I have done for years with Gentoo: cd /usr/src rm linux ln -sf latest.kernel linux cd linux make menuconfig save any changes make make models_install cp System.map /boot/System.map-3.2.12-gentoo cp arch/x86_64/boot/bzImage /boot/kernel-3.2.12-gentoo cp .config /boot/config-3.2.12-gentoo So all I can think of is NFS is the difference? I cannot seem to flesh out way the new kernel will not boot on this system and many others are just fine maybe I'm missing support for the sr driver ? ideas? James
Re: [gentoo-user] 3.2.12 Kenel wont boot
James wrote: Hello, OK, I manage quite a few gentoo systems. ONE of them is being a BIT _ _ ! and I cannot figure out what is obviously simple I have already migrated most system that I manage to the 3.2.12 kernel (not testing kernels for me at this time). Background: The system is an old HP AMD dual core laptop: AMD Turion(tm) 64 X2 Mobile Technology TL-56 The error message is this: Root-NFS: no NFS server address VFS: Unable to mount root fs via NFS, try floppy VFS: Cannot open root device sda4 or unknown block (2,0) Please append a correct root= boot option; here are the available partitions: oboo 1048575 sr0 driver:sr Kernel panic - not syncing : VFS : Unable to mount root fs on unknown block(2,0) PID:1,comm : swapper /0 Not tainted 3.2.12-gentoo#2 The other (3) series kernels boot and run just fine: from grub.conf: #0 title= Linux 3.2.1-gentoo root(hd0,1) kernel /boot/kernel-3.2.1-gentoo root=/dev/sda4 #1 title= Linux 3.2.12-gentoo root(hd0,1) kernel /boot/kernel-3.2.12-gentoo root=/dev/sda4 #2 title= Linux 3.0.6-gentoo root(hd0,1) kernel /boot/kernel-3.0.6-gentoo root=/dev/sda4 I can even scp over a kernel from a single processor AMD64 laptop and it boots and runs just fine. When I make a new kernel, I do what I have done for years with Gentoo: cd /usr/src rm linux ln -sf latest.kernel linux cd linux make menuconfig save any changes make make models_install cp System.map /boot/System.map-3.2.12-gentoo cp arch/x86_64/boot/bzImage /boot/kernel-3.2.12-gentoo cp .config /boot/config-3.2.12-gentoo So all I can think of is NFS is the difference? I cannot seem to flesh out way the new kernel will not boot on this system and many others are just fine maybe I'm missing support for the sr driver ? ideas? James OK. I'm used to looking for something stupid that I do so I can't help but notice something missing. In the list of commands for the new kernel, I notice the command to copy the old config over is missing. You did copy the config over right? When I run into this, it's because I forgot to put the root file system type in the kernel. Example: The root partition has ext3 and I forgot to build it into the kernel. Some people out of habit build it has a module which also doesn't work. ^_^ Also, make sure the stage files are in /boot too. Hope that helps. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS=--quiet-build=n
Re: [gentoo-user] Setting basic ALSA defaults
On 25 April 2012, at 20:49, ny6...@gmail.com wrote: ... Just a shot in the dark here, Stroller, but I once had a problem with using a mixer app (not alsamixer, which worked). I couldn't get it to start, and it kept on giving an error like your's above for alsamixer. The problem was that the kernel module, snd-mixer-oss was not loading by default, and when I loaded that module, all was good. HTH. Thanks for the suggestion, but that didn't work. I had to recompile my kernel for the new module, then reboot: # alsamixer cannot open mixer: Invalid argumentxmbc ~ # lsmod | grep -i snd_mix # lsmod | grep -i snd snd_hda_codec_hdmi 23052 1 snd_hda_codec_realtek 311454 1 snd_hda_intel 23052 1 snd_hda_codec 77939 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel snd_hwdep 6540 1 snd_hda_codec snd_pcm81875 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec snd_timer 20907 1 snd_pcm snd64619 8 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer soundcore 6858 1 snd snd_page_alloc 8021 2 snd_hda_intel,snd_pcm # modprobe -v snd-mixer-oss insmod /lib/modules/3.0.3/kernel/sound/core/oss/snd-mixer-oss.ko # alsamixer cannot open mixer: Invalid argument # I didn't really expect it to work, to be honest, as the difference seems to be entirely in the file. If I start the music playing in one console using `aplay -vv file.wav` (i.e. the /etc/asound.conf file is present and tells aplay to use HDMI out) then move to another terminal window and run `alsamixer` then I get this cannot open mixer: Invalid argument error. If I then delete /etc/asound.conf, alsamixer works perfectly and I can mute and unmute the S/PDIF. Stroller.
Re: [gentoo-user] Setting basic ALSA defaults
On 25 April 2012, at 19:58, Stroller wrote: ... So this is problematic the next time I reboot, because all of a sudden, now alsamixer doesn't work. In fact, I can demonstrate that the problem is related directly to this file: # alsamixer cannot open mixer: Invalid argument # rm /etc/asound.conf # alsamixer # echo $? 0 # So could anyone possibly explain this for me, please? Ok, fixed this. `alsamixer -c 0` makes it work. I was sure I tried this before, and it didn't work. Confusion is compounded here, because I'm using my laptop, working by SSH, and if I leave the nettop for too long the TV screen blanks; this onboard audio requires the nVidia drivers to be loaded, and this screen blanking also causes the audio to stop. I keep forgetting to notice this! If anyone could explain how I make card 0 the default for alsamixer, too, then I'd be very grateful. That question leads on to… I'm liable to have another question or two in a moment, but I'd initially just really love to understand why the alsa documentation says to have separate pcm.!default and ctl.!default definitions (instead of a single everything.!default) TIA, Stroller.
Re: [gentoo-user] 3.2.12 Kenel wont boot
Am 25.04.2012 22:55, schrieb Dale: James wrote: Hello, OK, I manage quite a few gentoo systems. ONE of them is being a BIT _ _ ! and I cannot figure out what is obviously simple I have already migrated most system that I manage to the 3.2.12 kernel (not testing kernels for me at this time). Background: The system is an old HP AMD dual core laptop: AMD Turion(tm) 64 X2 Mobile Technology TL-56 The error message is this: Root-NFS: no NFS server address VFS: Unable to mount root fs via NFS, try floppy VFS: Cannot open root device sda4 or unknown block (2,0) Please append a correct root= boot option; here are the available partitions: oboo 1048575 sr0 driver:sr Kernel panic - not syncing : VFS : Unable to mount root fs on unknown block(2,0) PID:1,comm : swapper /0 Not tainted 3.2.12-gentoo#2 The other (3) series kernels boot and run just fine: from grub.conf: #0 title= Linux 3.2.1-gentoo root(hd0,1) kernel /boot/kernel-3.2.1-gentoo root=/dev/sda4 #1 title= Linux 3.2.12-gentoo root(hd0,1) kernel /boot/kernel-3.2.12-gentoo root=/dev/sda4 #2 title= Linux 3.0.6-gentoo root(hd0,1) kernel /boot/kernel-3.0.6-gentoo root=/dev/sda4 I can even scp over a kernel from a single processor AMD64 laptop and it boots and runs just fine. When I make a new kernel, I do what I have done for years with Gentoo: cd /usr/src rm linux ln -sf latest.kernel linux cd linux make menuconfig save any changes make make models_install cp System.map /boot/System.map-3.2.12-gentoo cp arch/x86_64/boot/bzImage /boot/kernel-3.2.12-gentoo cp .config /boot/config-3.2.12-gentoo So all I can think of is NFS is the difference? I cannot seem to flesh out way the new kernel will not boot on this system and many others are just fine maybe I'm missing support for the sr driver ? Like Simon said, sr is your optical drive. I guess you are missing something in the HDD driver stack. Maybe you should post your kernel config and lspci. Or, like Simon suggested, the drives don't spin up fast enough. OK. I'm used to looking for something stupid that I do so I can't help but notice something missing. In the list of commands for the new kernel, I notice the command to copy the old config over is missing. You did copy the config over right? Thought the same. Using `make oldconfig` is also highly recommended. When I run into this, it's because I forgot to put the root file system type in the kernel. Example: The root partition has ext3 and I forgot to build it into the kernel. Some people out of habit build it has a module which also doesn't work. ^_^ I think that is a different error (unknown super block, unsupported features or something similar). Also, make sure the stage files are in /boot too. Hope that helps. Dale :-) :-) signature.asc Description: OpenPGP digital signature
[gentoo-user] Just a heads-up, I think =sys-libs/glibc-2.14.1-r3 is a stinker.
I've had two segfaults I'd never seen before. One in sudo and one in rdesktop. Updates later when I get things better tracked down. -- :wq
Re: [gentoo-user] Just a heads-up, I think =sys-libs/glibc-2.14.1-r3 is a stinker.
On Wed, Apr 25, 2012 at 10:09 PM, Michael Mol mike...@gmail.com wrote: I've had two segfaults I'd never seen before. One in sudo and one in rdesktop. Updates later when I get things better tracked down. I had a gcc segfault in my atom server, with MAKEOPTS=-j5. With MAKEOPTS=-j1, I got undefined references while linking some modules. My desktop and my laptop, however, compiled it without problems. I haven't had the time to check it, but it seems weird. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Just a heads-up, I think =sys-libs/glibc-2.14.1-r3 is a stinker.
On Wed, Apr 25, 2012 at 11:50 PM, Canek Peláez Valdés can...@gmail.com wrote: On Wed, Apr 25, 2012 at 10:09 PM, Michael Mol mike...@gmail.com wrote: I've had two segfaults I'd never seen before. One in sudo and one in rdesktop. Updates later when I get things better tracked down. I had a gcc segfault in my atom server, with MAKEOPTS=-j5. With MAKEOPTS=-j1, I got undefined references while linking some modules. My desktop and my laptop, however, compiled it without problems. I haven't had the time to check it, but it seems weird. Regards. Right now, normal emerging of anything fails for me. gdb segfaults on spawn. Bash segfaults on spawn. I can 'sudo busybox sh', though. Working with the guys in #gentoo-chat, figuring this thing out. -- :wq
Re: [gentoo-user] Just a heads-up, I think =sys-libs/glibc-2.14.1-r3 is a stinker.
On Wed, Apr 25, 2012 at 11:50 PM, Canek Peláez Valdés can...@gmail.com wrote: On Wed, Apr 25, 2012 at 10:09 PM, Michael Mol mike...@gmail.com wrote: I've had two segfaults I'd never seen before. One in sudo and one in rdesktop. Updates later when I get things better tracked down. I had a gcc segfault in my atom server, with MAKEOPTS=-j5. With MAKEOPTS=-j1, I got undefined references while linking some modules. My desktop and my laptop, however, compiled it without problems. I haven't had the time to check it, but it seems weird. Replacing with a binpackage from packages.gentooexperimental.org got bash working. Now I'm seeing if I can re-emerge gcc, binutils and glibc. If that goes through, I'm going to restart the emerge -e; my resume stack is probably toast. -- :wq
Re: [gentoo-user] Just a heads-up, I think =sys-libs/glibc-2.14.1-r3 is a stinker.
On Thu, Apr 26, 2012 at 12:37 AM, Michael Mol mike...@gmail.com wrote: On Wed, Apr 25, 2012 at 11:50 PM, Canek Peláez Valdés can...@gmail.com wrote: On Wed, Apr 25, 2012 at 10:09 PM, Michael Mol mike...@gmail.com wrote: I've had two segfaults I'd never seen before. One in sudo and one in rdesktop. Updates later when I get things better tracked down. I had a gcc segfault in my atom server, with MAKEOPTS=-j5. With MAKEOPTS=-j1, I got undefined references while linking some modules. My desktop and my laptop, however, compiled it without problems. I haven't had the time to check it, but it seems weird. Replacing with a binpackage from packages.gentooexperimental.org got bash working. Now I'm seeing if I can re-emerge gcc, binutils and glibc. If that goes through, I'm going to restart the emerge -e; my resume stack is probably toast. Ok, yes. This version of glibc, =sys-libs/glibc-2.14.1-r3, is crud. At least, if you're doing parallel building. Out of my three machines, the 8-core box got bit by it, the 4-core box got bit by it, but the 2-core laptop sailed past. I have a hunch that setting MAKEOPTS=-j1 will fix it for me, and I'm letting that run as I head off to sleep in a few minutes. -- :wq
Re: [gentoo-user] Just a heads-up, I think =sys-libs/glibc-2.14.1-r3 is a stinker.
On Thu, Apr 26, 2012 at 1:16 AM, Michael Mol mike...@gmail.com wrote: On Thu, Apr 26, 2012 at 12:37 AM, Michael Mol mike...@gmail.com wrote: On Wed, Apr 25, 2012 at 11:50 PM, Canek Peláez Valdés can...@gmail.com wrote: On Wed, Apr 25, 2012 at 10:09 PM, Michael Mol mike...@gmail.com wrote: I've had two segfaults I'd never seen before. One in sudo and one in rdesktop. Updates later when I get things better tracked down. I had a gcc segfault in my atom server, with MAKEOPTS=-j5. With MAKEOPTS=-j1, I got undefined references while linking some modules. My desktop and my laptop, however, compiled it without problems. I haven't had the time to check it, but it seems weird. Replacing with a binpackage from packages.gentooexperimental.org got bash working. Now I'm seeing if I can re-emerge gcc, binutils and glibc. If that goes through, I'm going to restart the emerge -e; my resume stack is probably toast. Ok, yes. This version of glibc, =sys-libs/glibc-2.14.1-r3, is crud. At least, if you're doing parallel building. Out of my three machines, the 8-core box got bit by it, the 4-core box got bit by it, but the 2-core laptop sailed past. I have a hunch that setting MAKEOPTS=-j1 will fix it for me, and I'm letting that run as I head off to sleep in a few minutes. Note, my experiences and instructions are specific to amd64 boxes. I don't know if other boxes are affected, and the workaround I'm writing below is not appropriate for anything but amd64. Incidentally, you'll know if your box got bit if you do a large set of emerges which include building glibc, and everything after glibc's 'Install' phase fails. Don't trust emerge's output; at this point, bash is segfaulting on startup, which makes emerge utterly unreliable, even as it tries to tell you the cause for errors. DO NOT close your open shells; you won't be able to launch bash until you've fixed this. To work around, you'll need a root shell. If you have any shell at all, you should be able to get a root shell by running sudo busybox sh in any of your remaining shells which have sudoer access. grab glibc-2.14.1-r3.tbz2 from http://packages.gentooexperimental.org/packages/amd64-unstable/sys-libs/ using wget. At least in my situation, wget still worked. Move the tarball to your / directory: mv glibc-2.14.1-r3.tbz2 / and unpack it tar xvjpf glibc-2.14.1-r3.tbz2 You should now have bash back, which means you'll have emerge back, and probably the rest of your system. -- :wq
Re: [gentoo-user] Postgres suddenly can't access files in its /etc directory
On Mon, April 23, 2012 3:21 pm, nap...@squareownz.org wrote: I'm unsure if I should be posting this to the -hardened mailing list as I'm using the hardened profile but all of a sudden I'm getting a rather strange error when trying to start postgres. # /etc/init.d/postgresql-9.1 start * Caching service dependencies ... [ ok ] * The following file(s) are not readable by 'postgres': * /etc/postgresql-9.1/postgresql.conf * /etc/postgresql-9.1/pg_ident.conf * /etc/postgresql-9.1/pg_hba.conf * HINT: Try: 'chmod 644 /etc/postgresql-9.1/*.conf' * ERROR: postgresql-9.1 failed to start That's what I'm getting when I attempt to start it and I don't seem to have modified anything. Looking into the init script I can see it's doing su postgres -c test -r /etc/postgresql-9.1/pg_hba.conf and the like but the output of: su postgres -c test -r /etc/postgresql-9.1/pg_hba.conf || echo fail is fail... so I'm quite at a loss as to what could be going on here. All of the files are owned by postgres, have the correct permissions (I ran chmod 644 as it hinted) and it should be able to traverse to the directory as everything has the execute bit from /etc onwards. Any tips? I don't have much experience with Hardenened, but are you certain that any permissions (including ACLs) are set correctly for PostgreSQL to access all its files? Do you have sec-policy/selinux-postgresql installed? And did you re-emerge this after the update? -- Joost
