Re: [gentoo-user] Ever since a recent update, vim misbehaves when run as root

2010-07-30 Thread Steffen Loos

Am 30.07.2010 05:58, schrieb Walter Dnes:

On Thu, Jul 29, 2010 at 01:35:46PM -0700, Kevin O'Gorman wrote

I'm not exactly sure when, but starting a month or so ago, vim has been
acting weird when
I run it as root.  For one thing, there are messages
 Xlib: connection to :0.0 refused by server


   General rule... by default X apps cannot be run by any user other than
the one who started the X session.  This bites you when you launch X as
regular user, and then su -.  Is vim considered an X app?  Yes, if
you've emerged vim with the X USE flag enabled.  You have two options.

1) Get rid of the X-integration by going into /etc/portage/package.use
and adding the line...

app-editors/vim -X

You'll have to re-emerge vim after making that change.  This gets rid
of X-integration for vim.


... or you start with:
~# vim -X

regards,
Steffen



[gentoo-user] Access to an embedded microSDHC card?

2010-07-30 Thread Helmut Jarausch
Hi,

when I attach my Garmin GPSmap 62s with an installed microSDHC card to 
a USB port, I only see one device which is the internal storage of 
the Garmin. On Windows I see a second mass storage device (the microSD 
card) in addition.
How to access this internal SD card or how to debug the problem.

Many thanks for a hint,
Helmut.




Re: [gentoo-user] Ever since a recent update, vim misbehaves when run as root

2010-07-30 Thread Neil Bothwick
On Thu, 29 Jul 2010 23:58:38 -0400, Walter Dnes wrote:

 1) Get rid of the X-integration by going into /etc/portage/package.use
 and adding the line...
 
 app-editors/vim -X
 
 You'll have to re-emerge vim after making that change.  This gets rid
 of X-integration for vim.
 
 2) If you really really need the X-integration features, you can use the
 xhost command to enable all users on your machine to run X apps on
 your X session.

3) emerge x11-misc/sux and us that instead of su.


-- 
Neil Bothwick

Never argue with an idiot. First, they bring you down to their level.
Then they beat you with experience.


signature.asc
Description: PGP signature


Re: [gentoo-user] Access to an embedded microSDHC card?

2010-07-30 Thread Dan Johansson
On Friday 30 July 2010 10.03:11 Helmut Jarausch wrote:
 Hi,
 
 when I attach my Garmin GPSmap 62s with an installed microSDHC card to
 a USB port, I only see one device which is the internal storage of
 the Garmin. On Windows I see a second mass storage device (the microSD
 card) in addition.
 How to access this internal SD card or how to debug the problem.
 
 Many thanks for a hint,
 Helmut.

Do you have the  Probe all LUNs on each SCSI device 
(CONFIG_SCSI_MULTI_LUN=y) kernel parameter set?

-- 
Dan Johansson, http://www.dmj.nu
***
This message is printed on 100% recycled electrons!
***



Re: [gentoo-user] Access to an embedded microSDHC card?

2010-07-30 Thread Helmut Jarausch
On 07/30/10 10:25:07, Dan Johansson wrote:
 On Friday 30 July 2010 10.03:11 Helmut Jarausch wrote:
  Hi,
  
  when I attach my Garmin GPSmap 62s with an installed microSDHC card
 to
  a USB port, I only see one device which is the internal storage of
  the Garmin. On Windows I see a second mass storage device (the
 microSD
  card) in addition.
  How to access this internal SD card or how to debug the problem.
  
  Many thanks for a hint,
  Helmut.
 
 Do you have the  Probe all LUNs on each SCSI device 
 (CONFIG_SCSI_MULTI_LUN=y) kernel parameter set?
 

Thanks, Dan, I've never heard of that.
I'll try ASAP.

Helmut.


-- 
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany




[gentoo-user] eix shows keyworded packages on home PC, but not on server

2010-07-30 Thread Mark David Dumlao
Hi guys,
Eix is one of those packages where you just set it and forget it, and
apparently I've forgotten there was even anything to set.

I have a home PC running gentoo. If I do eix foo, and foo happens to
be keyworded unmasked in my package.keywords, I get for instance:
[I] dev-python/snakeoil
 Available versions:  yellow(~)0.3.6.4 (~)0.3.6.5
block-yellow(~)0.3.7/block-yellow/yellow
 Installed versions:  0.3.7(07:34:54  PHT Saturday, 10 July, 2010)
 Homepage:http://www.pkgcore.org/
 Description: Miscellaneous python utility code.

I try the same on a relatively young gentoo server I'm managing and
* dev-python/snakeoil
 Available versions:  yellow~0.3.6.4 ~0.3.6.5 ~0.3.7/yellow
 Homepage:http://www.pkgcore.org/
 Description: Miscellaneous python utility code.

It's unkeyworded, however, in my package.keywords in both machines:
(home machine)
madum...@trixie ~ $ grep snakeoil -r /etc/portage/package.keywords/
/etc/portage/package.keywords/autounmask-pkgcore:dev-python/snakeoil ~amd64

(server)
mas...@zen ~ $ sudo grep -r snakeoil /etc/portage/package.keywords/
/etc/portage/package.keywords/system.keywords:dev-python/snakeoil ~x86

Apparently I'm missing some environment variable, but I can't for the
life of me imagine how I've set it.
home PC
madum...@trixie ~/store/HeCares/Photo upload functionality $ cat /etc/eixrc
# /etc/eixrc
#
# In this file system-wide defaults for variables related to eix binaries
# are stored, i.e. the variables set in this file override the built-in
# defaults. Both can be overridden by ~/.eixrc and by environment variables.
#
# It is strongly recommended to set here only those variables which you
# want to *differ* from the built-in defaults (or for which you have a
# particular reason why the default should never change with an eix update).
#
# *Otherwise you might miss changes in the defaults in newer eix versions*
# which may result in confusing behavior of the eix binaries.
#
# ebuilds of =eix-0.10.3 (and =eix-0.7.4) used to set *all* variables in
# /etc/eixrc which is not recommended anymore. If you want to get such a file
# (i.e. a file where all variables are described and set to the current
# values resp. to the built-in default values) you can redirect the output
# of the options --dump or --dump-defaults, respectively.
#
# However once more: To avoid unexpected problems
#
#   *IT IS NOT RECOMMENDED TO SET _ALL_ VARIABLES* in /etc/eixrc
#
# Only set those for which you have a reason to do so!
#
# For the available variables and their defaults, see the output of the
# options --dump or --dump-defaults.
# For more detailed explanations see the manpage of eix.

madum...@trixie ~/store/HeCares/Photo upload functionality $ cat
/etc/eix-sync.conf
# eix-sync.conf
##  defines options to eix-sync, caching system for portage


#layman overlays to be synced (* means all)
*
/home PC

server
mas...@zen ~ $ cat /etc/eixrc
# /etc/eixrc
#
# In this file system-wide defaults for variables related to eix binaries
# are stored, i.e. the variables set in this file override the built-in
# defaults. Both can be overridden by ~/.eixrc and by environment variables.
#
# It is strongly recommended to set here only those variables which you
# want to *differ* from the built-in defaults (or for which you have a
# particular reason why the default should never change with an eix update).
#
# *Otherwise you might miss changes in the defaults in newer eix versions*
# which may result in confusing behavior of the eix binaries.
#
# ebuilds of =eix-0.10.3 (and =eix-0.7.4) used to set *all* variables in
# /etc/eixrc which is not recommended anymore. If you want to get such a file
# (i.e. a file where all variables are described and set to the current
# values resp. to the built-in default values) you can redirect the output
# of the options --dump or --dump-defaults, respectively.
#
# However once more: To avoid unexpected problems
#
#   *IT IS NOT RECOMMENDED TO SET _ALL_ VARIABLES* in /etc/eixrc
#
# Only set those for which you have a reason to do so!
#
# For the available variables and their defaults, see the output of the
# options --dump or --dump-defaults.
# For more detailed explanations see the manpage of eix.

mas...@zen ~ $ cat /etc/eix-sync.conf
cat: /etc/eix-sync.conf: No such file or directory
/server

All comments for the both of them, so it must be a default I'm missing
that's different for the 2 machines. Any ideas?
-- 
This email is:    [ ] actionable   [ ] fyi        [x] social
Response needed:  [ ] yes          [x] up to you  [ ] no
Time-sensitive:   [ ] immediate    [ ] soon       [ ] none



Re: [gentoo-user] nss_updatedb pam_ccreds

2010-07-30 Thread Vincent-Xavier JUMEL
Le 29 juillet à 18:50 Giampiero Gabbiani a écrit
 Hi all,
 I configured nss  pam in order to make LDAP authentication. In order to 
 have a proper authentication and attributes retrieving I added also ccreds 
 and nss_updatedb modifying /etc/pam.d/system-auth for the first and 
Did you tried to start nscd daemon to cache entries for the nsswitch
subsystem ?

I've been working around this for a while, and one of the best solution
is to have a slave LDAP on every single host.

Cheers
-- 
Rejoignez les 5521 adhérents de l'April http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org
+33 (0) 148 295 997 http://blog.thetys-retz.net/
GPG Id: EBEC C39A DAAE F766 9785  EF23 E76F 467D 2E14 CE70



Re: [gentoo-user] eix shows keyworded packages on home PC, but not on server

2010-07-30 Thread Mark David Dumlao
diff between the eix --dump of my PC and the server

===
madum...@trixie ~ $ diff -Naur PC server
--- PC  2010-07-30 19:54:38.0 +0800
+++ server  2010-07-30 19:55:05.0 +0800
@@ -126,7 +126,7 @@

 # STRING
 # The path to the ebuild.sh executable.
-EXEC_EBUILD_SH=%{EPREFIX_PORTAGE_EXEC}/usr/lib64/portage/bin/ebuild.sh
+EXEC_EBUILD_SH=%{EPREFIX_PORTAGE_EXEC}/usr/lib/portage/bin/ebuild.sh

 # STRING
 # The path to the tempfile generated by ebuild depend.
@@ -177,7 +177,7 @@
 # STRING
 # This variable is passed unchanged to ebuild.sh
 # Usually ebuild.sh uses it to calculate the PATH.
-PORTAGE_ROOTPATH=/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.3.4
+PORTAGE_ROOTPATH=/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.3.4:/usr/i686-pc-linux-gnu/x86_64-pc-linux-gnu/gcc-bin/4.4.4

 # STRING
 # This variable is passed unchanged to ebuild.sh
===

Seems to be just paths, don't see why that would cause a problem.

Both machines are using portage 2.1.8.3

On Fri, Jul 30, 2010 at 7:46 PM, Mark David Dumlao madum...@gmail.com wrote:
 Hi guys,
 Eix is one of those packages where you just set it and forget it, and
 apparently I've forgotten there was even anything to set.

 I have a home PC running gentoo. If I do eix foo, and foo happens to
 be keyworded unmasked in my package.keywords, I get for instance:
 [I] dev-python/snakeoil
     Available versions:  yellow(~)0.3.6.4 (~)0.3.6.5
 block-yellow(~)0.3.7/block-yellow/yellow
     Installed versions:  0.3.7(07:34:54  PHT Saturday, 10 July, 2010)
     Homepage:            http://www.pkgcore.org/
     Description:         Miscellaneous python utility code.

 I try the same on a relatively young gentoo server I'm managing and
 * dev-python/snakeoil
     Available versions:  yellow~0.3.6.4 ~0.3.6.5 ~0.3.7/yellow
     Homepage:            http://www.pkgcore.org/
     Description:         Miscellaneous python utility code.

 It's unkeyworded, however, in my package.keywords in both machines:
 (home machine)
 madum...@trixie ~ $ grep snakeoil -r /etc/portage/package.keywords/
 /etc/portage/package.keywords/autounmask-pkgcore:dev-python/snakeoil ~amd64

 (server)
 mas...@zen ~ $ sudo grep -r snakeoil /etc/portage/package.keywords/
 /etc/portage/package.keywords/system.keywords:dev-python/snakeoil ~x86

 Apparently I'm missing some environment variable, but I can't for the
 life of me imagine how I've set it.
 home PC
 madum...@trixie ~/store/HeCares/Photo upload functionality $ cat /etc/eixrc
 # /etc/eixrc
 #
 # In this file system-wide defaults for variables related to eix binaries
 # are stored, i.e. the variables set in this file override the built-in
 # defaults. Both can be overridden by ~/.eixrc and by environment variables.
 #
 # It is strongly recommended to set here only those variables which you
 # want to *differ* from the built-in defaults (or for which you have a
 # particular reason why the default should never change with an eix update).
 #
 # *Otherwise you might miss changes in the defaults in newer eix versions*
 # which may result in confusing behavior of the eix binaries.
 #
 # ebuilds of =eix-0.10.3 (and =eix-0.7.4) used to set *all* variables in
 # /etc/eixrc which is not recommended anymore. If you want to get such a file
 # (i.e. a file where all variables are described and set to the current
 # values resp. to the built-in default values) you can redirect the output
 # of the options --dump or --dump-defaults, respectively.
 #
 # However once more: To avoid unexpected problems
 #
 #   *IT IS NOT RECOMMENDED TO SET _ALL_ VARIABLES* in /etc/eixrc
 #
 # Only set those for which you have a reason to do so!
 #
 # For the available variables and their defaults, see the output of the
 # options --dump or --dump-defaults.
 # For more detailed explanations see the manpage of eix.

 madum...@trixie ~/store/HeCares/Photo upload functionality $ cat
 /etc/eix-sync.conf
 # eix-sync.conf
 ##  defines options to eix-sync, caching system for portage


 #layman overlays to be synced (* means all)
 *
 /home PC

 server
 mas...@zen ~ $ cat /etc/eixrc
 # /etc/eixrc
 #
 # In this file system-wide defaults for variables related to eix binaries
 # are stored, i.e. the variables set in this file override the built-in
 # defaults. Both can be overridden by ~/.eixrc and by environment variables.
 #
 # It is strongly recommended to set here only those variables which you
 # want to *differ* from the built-in defaults (or for which you have a
 # particular reason why the default should never change with an eix update).
 #
 # *Otherwise you might miss changes in the defaults in newer eix versions*
 # which may result in confusing behavior of the eix binaries.
 #
 # ebuilds of =eix-0.10.3 (and =eix-0.7.4) used to set *all* variables in
 # /etc/eixrc which is not recommended anymore. If you want to get such a file
 # (i.e. a file where all variables are described and set to the current
 # values resp. to the built-in default values) you can redirect the output
 # of the 

Re: [gentoo-user] Ever since a recent update, vim misbehaves when run as root

2010-07-30 Thread Bill Longman
On 07/29/2010 08:58 PM, Walter Dnes wrote:

 2) If you really really need the X-integration features, you can use the
 xhost command to enable all users on your machine to run X apps on
 your X session.  E.g. my machine is 192.168.123.249 so I ran...
 
   xhost +192.168.123.249
 
 ...to allow a 32-bit QEMU-KVM guest to run an X program on the 64-bit
 host's Xwindows session.

What you probably want here instead is:

xhost +local:

then the X app is not limited to using only IP but can choose whichever
transport it deems best. Of course the usual safety caveats apply. If
others are on your host, they'll have X access. If you're concerned
about that, then just give root permission:

xhost SI:localuser:root



Re: [gentoo-user] eix shows keyworded packages on home PC, but not on server

2010-07-30 Thread Bill Longman
On 07/30/2010 04:57 AM, Mark David Dumlao wrote:
 diff between the eix --dump of my PC and the server
 
 ===
 madum...@trixie ~ $ diff -Naur PC server
 --- PC2010-07-30 19:54:38.0 +0800
 +++ server2010-07-30 19:55:05.0 +0800
 @@ -126,7 +126,7 @@
 
  # STRING
  # The path to the ebuild.sh executable.
 -EXEC_EBUILD_SH=%{EPREFIX_PORTAGE_EXEC}/usr/lib64/portage/bin/ebuild.sh
 +EXEC_EBUILD_SH=%{EPREFIX_PORTAGE_EXEC}/usr/lib/portage/bin/ebuild.sh
 
  # STRING
  # The path to the tempfile generated by ebuild depend.
 @@ -177,7 +177,7 @@
  # STRING
  # This variable is passed unchanged to ebuild.sh
  # Usually ebuild.sh uses it to calculate the PATH.
 -PORTAGE_ROOTPATH=/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.3.4
 +PORTAGE_ROOTPATH=/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.3.4:/usr/i686-pc-linux-gnu/x86_64-pc-linux-gnu/gcc-bin/4.4.4
 
  # STRING
  # This variable is passed unchanged to ebuild.sh
 ===
 
 Seems to be just paths, don't see why that would cause a problem.
 
 Both machines are using portage 2.1.8.3
 
 On Fri, Jul 30, 2010 at 7:46 PM, Mark David Dumlao madum...@gmail.com wrote:
 Hi guys,
 Eix is one of those packages where you just set it and forget it, and
 apparently I've forgotten there was even anything to set.

 I have a home PC running gentoo. If I do eix foo, and foo happens to
 be keyworded unmasked in my package.keywords, I get for instance:
 [I] dev-python/snakeoil
 Available versions:  yellow(~)0.3.6.4 (~)0.3.6.5
 block-yellow(~)0.3.7/block-yellow/yellow
 Installed versions:  0.3.7(07:34:54  PHT Saturday, 10 July, 2010)
 Homepage:http://www.pkgcore.org/
 Description: Miscellaneous python utility code.

 I try the same on a relatively young gentoo server I'm managing and
 * dev-python/snakeoil
 Available versions:  yellow~0.3.6.4 ~0.3.6.5 ~0.3.7/yellow
 Homepage:http://www.pkgcore.org/
 Description: Miscellaneous python utility code.

 It's unkeyworded, however, in my package.keywords in both machines:
 (home machine)
 madum...@trixie ~ $ grep snakeoil -r /etc/portage/package.keywords/
 /etc/portage/package.keywords/autounmask-pkgcore:dev-python/snakeoil ~amd64

 (server)
 mas...@zen ~ $ sudo grep -r snakeoil /etc/portage/package.keywords/
 /etc/portage/package.keywords/system.keywords:dev-python/snakeoil ~x86

 Apparently I'm missing some environment variable, but I can't for the
 life of me imagine how I've set it.
 home PC
 madum...@trixie ~/store/HeCares/Photo upload functionality $ cat /etc/eixrc
 # /etc/eixrc
 #
 # In this file system-wide defaults for variables related to eix binaries
 # are stored, i.e. the variables set in this file override the built-in
 # defaults. Both can be overridden by ~/.eixrc and by environment variables.
 #
 # It is strongly recommended to set here only those variables which you
 # want to *differ* from the built-in defaults (or for which you have a
 # particular reason why the default should never change with an eix update).
 #
 # *Otherwise you might miss changes in the defaults in newer eix versions*
 # which may result in confusing behavior of the eix binaries.
 #
 # ebuilds of =eix-0.10.3 (and =eix-0.7.4) used to set *all* variables in
 # /etc/eixrc which is not recommended anymore. If you want to get such a file
 # (i.e. a file where all variables are described and set to the current
 # values resp. to the built-in default values) you can redirect the output
 # of the options --dump or --dump-defaults, respectively.
 #
 # However once more: To avoid unexpected problems
 #
 #   *IT IS NOT RECOMMENDED TO SET _ALL_ VARIABLES* in /etc/eixrc
 #
 # Only set those for which you have a reason to do so!
 #
 # For the available variables and their defaults, see the output of the
 # options --dump or --dump-defaults.
 # For more detailed explanations see the manpage of eix.

 madum...@trixie ~/store/HeCares/Photo upload functionality $ cat
 /etc/eix-sync.conf
 # eix-sync.conf
 ##  defines options to eix-sync, caching system for portage


 #layman overlays to be synced (* means all)
 *
 /home PC

 server
 mas...@zen ~ $ cat /etc/eixrc
 # /etc/eixrc
 #
 # In this file system-wide defaults for variables related to eix binaries
 # are stored, i.e. the variables set in this file override the built-in
 # defaults. Both can be overridden by ~/.eixrc and by environment variables.
 #
 # It is strongly recommended to set here only those variables which you
 # want to *differ* from the built-in defaults (or for which you have a
 # particular reason why the default should never change with an eix update).
 #
 # *Otherwise you might miss changes in the defaults in newer eix versions*
 # which may result in confusing behavior of the eix binaries.
 #
 # ebuilds of =eix-0.10.3 (and =eix-0.7.4) used to set *all* variables in
 # /etc/eixrc which is not recommended anymore. If you want to get such a file
 # (i.e. a file where all variables are described and set to the current
 # 

Re: [gentoo-user] eix shows keyworded packages on home PC, but not on server

2010-07-30 Thread Mark David Dumlao
On Fri, Jul 30, 2010 at 9:47 PM, Bill Longman bill.long...@gmail.com wrote:
 What does eselect profile list show you on both hosts?
home PC
madum...@trixie ~ $ eselect profile list
Available profile symlink targets:
  [1]   default/linux/amd64/10.0
  [2]   default/linux/amd64/10.0/desktop *
  [3]   default/linux/amd64/10.0/desktop/gnome
  [4]   default/linux/amd64/10.0/desktop/kde
  [5]   default/linux/amd64/10.0/developer
  [6]   default/linux/amd64/10.0/no-multilib
  [7]   default/linux/amd64/10.0/server
  [8]   hardened/linux/amd64/10.0
  [9]   hardened/linux/amd64/10.0/no-multilib
  [10]  selinux/2007.0/amd64
  [11]  selinux/2007.0/amd64/hardened
  [12]  selinux/v2refpolicy/amd64
  [13]  selinux/v2refpolicy/amd64/desktop
  [14]  selinux/v2refpolicy/amd64/developer
  [15]  selinux/v2refpolicy/amd64/hardened
  [16]  selinux/v2refpolicy/amd64/server

server
mas...@zen ~ $ sudo eselect profile list
Available profile symlink targets:
  [1]   default/linux/x86/10.0 *
  [2]   default/linux/x86/10.0/desktop
  [3]   default/linux/x86/10.0/desktop/gnome
  [4]   default/linux/x86/10.0/desktop/kde
  [5]   default/linux/x86/10.0/developer
  [6]   default/linux/x86/10.0/server
  [7]   hardened/linux/x86/10.0
  [8]   selinux/2007.0/x86
  [9]   selinux/2007.0/x86/hardened
  [10]  selinux/v2refpolicy/x86
  [11]  selinux/v2refpolicy/x86/desktop
  [12]  selinux/v2refpolicy/x86/developer
  [13]  selinux/v2refpolicy/x86/hardened
  [14]  selinux/v2refpolicy/x86/server

I'm not that familiar with how the profile affects eix though.



Re: [gentoo-user] Ever since a recent update, vim misbehaves when run as root

2010-07-30 Thread Kevin O'Gorman
On Fri, Jul 30, 2010 at 6:43 AM, Bill Longman bill.long...@gmail.comwrote:

 On 07/29/2010 08:58 PM, Walter Dnes wrote:

  2) If you really really need the X-integration features, you can use the
  xhost command to enable all users on your machine to run X apps on
  your X session.  E.g. my machine is 192.168.123.249 so I ran...
 
xhost +192.168.123.249
 
  ...to allow a 32-bit QEMU-KVM guest to run an X program on the 64-bit
  host's Xwindows session.

 What you probably want here instead is:

 xhost +local:

 then the X app is not limited to using only IP but can choose whichever
 transport it deems best. Of course the usual safety caveats apply. If
 others are on your host, they'll have X access. If you're concerned
 about that, then just give root permission:

 xhost SI:localuser:root

 Thanks -- that was what I was trying to remember, so I just emerged it.

Looks like something I should be able to do in my .bashrc and just forget
about.


-- 
Kevin O'Gorman, PhD


Re: [gentoo-user] Ever since a recent update, vim misbehaves when run as root

2010-07-30 Thread Kevin O'Gorman
On Fri, Jul 30, 2010 at 7:59 AM, Kevin O'Gorman kogor...@gmail.com wrote:



 then the X app is not limited to using only IP but can choose whichever
 transport it deems best. Of course the usual safety caveats apply. If
 others are on your host, they'll have X access. If you're concerned
 about that, then just give root permission:

 xhost SI:localuser:root

 xhost +local:
 Thanks -- that was what I was trying to remember, so I just emerged it.

 Looks like something I should be able to do in my .bashrc and just forget
 about.

 Actually, it doesn't work.

ke...@treat ~ $ xhost si:localhost:root
localhost:root being added to access control list
X Error of failed request:  BadValue (integer parameter out of range for
operation)
  Major opcode of failed request:  109 (X_ChangeHosts)
  Value in failed request:  0xe
  Serial number of failed request:  7
  Current serial number in output stream:  9

ke...@treat ~ $ xhost SI:localhost:root
localhost:root being added to access control list
X Error of failed request:  BadValue (integer parameter out of range for
operation)
  Major opcode of failed request:  109 (X_ChangeHosts)
  Value in failed request:  0xe
  Serial number of failed request:  7
  Current serial number in output stream:  9
ke...@treat ~ $

What's worse, the xhost man page refers me to Xauthority(7) which does not
exist, and I did
not find it with a quick check by eix.

What did work was
  xhost +r...@localhost


-- 
Kevin O'Gorman, PhD


Re: [gentoo-user] eix shows keyworded packages on home PC, but not on server

2010-07-30 Thread Bill Longman
On 07/30/2010 07:46 AM, Mark David Dumlao wrote:
 On Fri, Jul 30, 2010 at 9:47 PM, Bill Longman bill.long...@gmail.com wrote:
 What does eselect profile list show you on both hosts?
 home PC
 madum...@trixie ~ $ eselect profile list
 Available profile symlink targets:
   [1]   default/linux/amd64/10.0
   [2]   default/linux/amd64/10.0/desktop *
   [3]   default/linux/amd64/10.0/desktop/gnome
   [4]   default/linux/amd64/10.0/desktop/kde
   [5]   default/linux/amd64/10.0/developer
   [6]   default/linux/amd64/10.0/no-multilib
   [7]   default/linux/amd64/10.0/server
   [8]   hardened/linux/amd64/10.0
   [9]   hardened/linux/amd64/10.0/no-multilib
   [10]  selinux/2007.0/amd64
   [11]  selinux/2007.0/amd64/hardened
   [12]  selinux/v2refpolicy/amd64
   [13]  selinux/v2refpolicy/amd64/desktop
   [14]  selinux/v2refpolicy/amd64/developer
   [15]  selinux/v2refpolicy/amd64/hardened
   [16]  selinux/v2refpolicy/amd64/server
 
 server
 mas...@zen ~ $ sudo eselect profile list
 Available profile symlink targets:
   [1]   default/linux/x86/10.0 *
   [2]   default/linux/x86/10.0/desktop
   [3]   default/linux/x86/10.0/desktop/gnome
   [4]   default/linux/x86/10.0/desktop/kde
   [5]   default/linux/x86/10.0/developer
   [6]   default/linux/x86/10.0/server
   [7]   hardened/linux/x86/10.0
   [8]   selinux/2007.0/x86
   [9]   selinux/2007.0/x86/hardened
   [10]  selinux/v2refpolicy/x86
   [11]  selinux/v2refpolicy/x86/desktop
   [12]  selinux/v2refpolicy/x86/developer
   [13]  selinux/v2refpolicy/x86/hardened
   [14]  selinux/v2refpolicy/x86/server
 
 I'm not that familiar with how the profile affects eix though.

The profile affects the default USE settings. This is a very important
Gentoo concept.



Re: [gentoo-user] All of a sudden, no apache2. No clue why.

2010-07-30 Thread Kyle Bader
   * Starting apache2 ...
  (98)Address already in use: make_sock: could not bind to address
  64.166.164.49:80
  no listening sockets available, shutting down
  Unable to open
  logs   [

Strace will probably reveal which log file can't be opened, something
like this will probably do the trick:

strace /path/to/apache2 -D module list -d /path/to/apache2dir

 And that's a DNS listener, an NTP listener, and firefox as a client, not a
 listener.  Though it makes me want to track down 1e100.net and find out who
 they are.

Google:

   Domain Name: 1E100.NET
   Registrar: MARKMONITOR INC.
   Whois Server: whois.markmonitor.com
   Referral URL: http://www.markmonitor.com
   Name Server: NS1.GOOGLE.COM
   Name Server: NS2.GOOGLE.COM
   Name Server: NS3.GOOGLE.COM
   Name Server: NS4.GOOGLE.COM

Registrant:
DNS Admin
Google Inc.
1600 Amphitheatre Parkway
 Mountain View CA 94043
US
dns-ad...@google.com +1.650253 Fax: +1.6506188571

-- 

Kyle



Re: [gentoo-user] eix shows keyworded packages on home PC, but not on server

2010-07-30 Thread Mark David Dumlao
On Fri, Jul 30, 2010 at 11:51 PM, Bill Longman bill.long...@gmail.com wrote:
 The profile affects the default USE settings. This is a very important
 Gentoo concept.

emerge --info eix on both machines:

PC:
app-portage/eix-0.20.5 was built with the following:
USE=bzip2 (multilib) nls sqlite -debug -doc -hardened -optimization
-strong-optimization -tools
LDFLAGS=-Wl,-O1

server:
app-portage/eix-0.20.5 was built with the following:
USE=bzip2 nls sqlite -debug -doc -hardened -optimization
-strong-optimization -tools
LDFLAGS=-Wl,-O1


The only difference between the USE flags of both machines is that my
local eix was built with multilib. I don't know any documentation
references that say how that should affect eix output settings, which
shouldn't be related.

Just to clarify, emerge detects that the packages are keyworded on
both machines. It's just not being outputted by eix. And there's no
reason why multilib should cause eix to change the output settings.
-- 
This email is:    [ ] actionable   [ ] fyi        [ ] social
Response needed:  [ ] yes          [ ] up to you  [ ] no
Time-sensitive:   [ ] immediate    [ ] soon       [ ] none



Re: [gentoo-user] eix shows keyworded packages on home PC, but not on server

2010-07-30 Thread Bill Longman
On 07/30/2010 09:26 AM, Mark David Dumlao wrote:
 On Fri, Jul 30, 2010 at 11:51 PM, Bill Longman bill.long...@gmail.com wrote:
 The profile affects the default USE settings. This is a very important
 Gentoo concept.
 
 emerge --info eix on both machines:
 
 PC:
 app-portage/eix-0.20.5 was built with the following:
 USE=bzip2 (multilib) nls sqlite -debug -doc -hardened -optimization
 -strong-optimization -tools
 LDFLAGS=-Wl,-O1
 
 server:
 app-portage/eix-0.20.5 was built with the following:
 USE=bzip2 nls sqlite -debug -doc -hardened -optimization
 -strong-optimization -tools
 LDFLAGS=-Wl,-O1
 
 
 The only difference between the USE flags of both machines is that my
 local eix was built with multilib. I don't know any documentation
 references that say how that should affect eix output settings, which
 shouldn't be related.
 
 Just to clarify, emerge detects that the packages are keyworded on
 both machines. It's just not being outputted by eix. And there's no
 reason why multilib should cause eix to change the output settings.

I mean to say that the profile sets the *global* USE settings. If you
were to compare euse -i between the two machines, you would see that
some flags are +D and some are +C, for instance. The ones that are
set by the profile are +D. If you peruse the portage/profiles you'll
see that the make.defaults files are setting different USE values. Not
to mention that you are on different architectures between the two, so
some packages will be masked and some not depending upon the
architecture. It's not a matter of how eix was built, it's a matter of
the configuration of the host.

Is that what you were trying to resolve? Or do I not understand your
question? Can you put a package mask in just *any* file below
package.keywords/ and as long as it matches it will be valid?



[gentoo-user] Re: USB SDHC Card Reader works, but only if mounted first in WinXP virtual machine

2010-07-30 Thread Paul Hartman
On Wed, Jul 28, 2010 at 9:37 AM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
 Hi,

 I have a USB SDHC card reader whose partition table is not read, and
 device node not created, when plugged into my Gentoo Linux computer. I
 posted about this a year or two ago but was never able to get it
 working, until I recently made an accidental discovery:

 If I let a VMWare WinXP take control of the USB device, on the same
 physical linux machine as above, the card reader mounts normally in
 the virtual WinXP. Then, if I release the USB device from VMware,
 Linux takes control of the device back and can read the partition
 table and creates the device node normally. After that everything
 works fine, I can copy files to/from etc. and everything seems normal.

BradN on the Forums suggested hdparm -z to force the kernel to
re-read the partition table, and this works. Much easier than using a
virtual machine!



Re: [gentoo-user] All of a sudden, no apache2. No clue why.

2010-07-30 Thread Kevin O'Gorman
On Fri, Jul 30, 2010 at 9:12 AM, Kyle Bader kyle.ba...@gmail.com wrote:

* Starting apache2 ...
   (98)Address already in use: make_sock: could not bind to address
   64.166.164.49:80
   no listening sockets available, shutting down
   Unable to open
   logs
 [

 Strace will probably reveal which log file can't be opened, something
 like this will probably do the trick:

 strace /path/to/apache2 -D module list -d /path/to/apache2dir

  And that's a DNS listener, an NTP listener, and firefox as a client, not
 a
  listener.  Though it makes me want to track down 1e100.net and find out
 who
  they are.

 Google:


I should have known that.  1e100 is a mathematical/programming synonym for
google.
Amusing.

I do most of this in gmail, so those connections look normal.

I don't know what the usual module list is, so I guess I have to go trolling
throught the
init.d scripts to figure it out, unless somebody knows a better way.

-- 
Kevin O'Gorman, PhD


[gentoo-user] pecl-cairo ~x86 overlay?

2010-07-30 Thread Michael M
Hello list, I need to install Cairo bindings for dev-lang/php-5*.  Is there
a pecl-cairo overlay for ~x86?  I've tried unmasking this package and adding
the keyword ~amd64 and it seems to want to install with emerge but my system
is ~x86.

According to this site it is only ~amd64, but I cannot understand why.
http://gpo.zugaina.org/dev-php5/pecl-cairo

Thanks for any help.

-- 
Hope is more than just a postponed disappointment ~ Epica