I do have a mix of stable and unstable, and unfortunately a lot of things that need to be updated. In the past emerge has always been good about telling me which dependencies were masked, so I kind of assumed it would do it this time as well.

I'm going to try to clear away some of the non-blocked ...

I have a similar problem:

[blocks B ] <gnome-base/gail-1000 ("<gnome-base/gail-1000" is blocking x11-libs/gtk+-2.14.7-r2)
[blocks B ] <dev-python/gnome-python-2.22.1 ("<dev-python/gnome-python-2.22.1" is blocking dev-python/gnome-vfs-python-2.22.3, dev-python/libgnome-python-2.22.3, dev-python ...

I have a mythtv box with a PVR-350 using ivtv that's been running great for a long time now. I recently added a webcam (Logitech Communicate STX) and got it working with the gspcav1 driver.

The problem is that the webcam seems to come up as /dev/video0 or /dev/video1 randomly, and if it claims the ...

Are you trying to su from the root account to another account? If so then "auth sufficient pam_rootok.so" should
do it.

Otherwise, you'll need to uncomment the "auth sufficient pam_listfile.so item=ruser sense=allow onerr=fail file=/etc/security/suauth.nopass" line and set up a /etc/security ...

/etc/pam.d/su is identical as well:

#%PAM-1.0

auth sufficient pam_rootok.so

# If you want to restrict users begin allowed to su even more,
# create /etc/security/suauth.allow (or to that matter) that is only
# writable by root, and add users that are allowed to su to that
# file, one per line ...

The sudoers file is identical across systems. It contains the default root settings of:

root ALL=(ALL) ALL

On one of my Gentoo systems if I try to su to a regular user account it asks me to "reenter password". On other systems it doesn't do this, it just switches to the specified user.

So what have I changed to make su act this way?

A short update: I still don't know what's causing the original NFS error, but it's not what was preventing the client system from mounting the exported filesystems - that turned out to be a DNS error.

Running sshd on a non-standard port is all you need to avoid most scripted attacks.

It seems to be that way for the current (1.0.12) version. I just downgraded to 1.0.10 and it has the same problem. I also tried 1.1.0 (unstable) and it didn't work either.

I have another Gentoo system right next to this one and nfs runs fine on it. I'm beginning to think it has something to do with ...

rc-status output:


Runlevel: default
gkrellmd [ started ]
hdparm [ started ]
lm_sensors [ started ]
local [ started ]
metalog [ started ]
net.eth0 [ started ]
netmount [ started ]
nfs [ started ]
ntp-client [ started ]
ntpd [ started ]
postfix [ started ]
samba [ started ]
smartd ...

I get these errors when I start NFS on a new AMD64 X2 system I'm building:


Jun 10 17:13:24 [rpc.statd] Version 1.0.11 Starting
Jun 10 17:13:24 [nfsd] nfssvc: writing fds to kernel failed: errno 0 (Success)

I haven't been able to find out anything useful by searching for the error, and I'm a bit ...

I got it working with syslog-ng, but my main purpose for doing this was to debug some RADIUS authentication issues, and now that I have the logging working the RADIUS issues have gone away for the time being. I've spent so much time trying to figure out what is causing the problem that I'm not even ...

That would be unfortunate, but at least it explains what I'm (not) seeing.

I'll look into syslog-ng. Thanks for the info.

I need to set up logging from an Aironet 1100 WAP on my linux box running metalog, but I can't figure out how to configure metalog to actually listen to the data being sent by the Aironet.

The Aironet docs state:


The current software generates the following categories of syslog messages ...

That still sounds like the init scripts are doing something wrong. Try loading the wireless drivers manually and then using ifconfig to configure the port, like this:

ifconfig eth1 192.168.1.1 netmask 255.255.255.0

Did you update anything else at the same time as baselayout (like your kernel)?

Did you run the commands at the end of the baselayout emerge to symlink the net.eth* scritps to net.lo?

The problem was that when you emerged the new baselayout you were supposed to symlink the existing net.eth* init scripts to net.lo (it says this at the end of the emerge). Not doing this caused the network scripts to fail with the error message you posted because you would still be running the old ...

It's not an etc-update kind of update; when you emerge baselayout there's a message at the end telling you to create symlinks of the existing net.eth* scripts to net.lo. If you don't do that then you'll be running the wrong init script at boot time, and all kinds of things won't work.

And should I put the configuration file under vhosts (where the non-SSL host examples are defined) or modules (where the SSL host examples are)? I keep getting:

Init: (shs.ucdavis.edu:443) You configured HTTP(80) on the standard HTTPS(443) port!

errors no matter how I set it up.

My /etc/conf.d ...

I had a problem with my amavisd-new configuration for a few days and as a result I have 100+ e-mail messages sitting in /var/amavis/tmp. The amavis logs reported things like "PRESERVING EVIDENCE in /var/amavis/tmp/amavis-20060427T150022-19975". So the messages are there, and now that I've fixed ...

I just wanted to thank you for doing this. I was about halfway into getting Mythburn installed and running when I came across this post; I figure you saved me several hours of frustration.

I have it all running now and I've created an iso or two but haven't tested them out to see if they actually ...

Well, I got the cdrom and dvd entries by adding these lines to a new rules file:

KERNEL="hdd", SYMLINK="dvd"
KERNEL="hdd", SYMLINK="cdrom"

I think they worked before because of leftover devcie entries from when I was using devfs, and removing them (accidently) was what messed things up. Whatever ...

I don't think it actually creates the links, it just outputs what they should be for a given device. For example, if you run:

./cdsymlinks.dh hdd

it will output (in my case) 'cdrom dvd'. I presume some other part of udev then takes this and creates the actual links, but that's not working for me.

I made a line that says 'OUTPUT="CD DVD"' and rebooted but the device is still missing. I even tried running the cdsymlinks.sh script manually and it correctly identifies "cdrom dvd" if I give it the proper device name (hdd).

Any other ideas? I'll keep plugging away at it myself too.