public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ben Lutgens <blutgens@sistina.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] problems with new install
Date: Tue Apr 17 21:42:02 2001	[thread overview]
Message-ID: <20010417224047.A802@minime> (raw)
In-Reply-To: <20010417210925.A16787@cvs.gentoo.org>; from drobbins@gentoo.org on Tue, Apr 17, 2001 at 09:09:25PM -0600

[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]

On Tue, Apr 17, 2001 at 09:09:25PM -0600, Daniel Robbins wrote:
>On Tue, Apr 17, 2001 at 09:21:19PM -0500, Ben Lutgens wrote:
>> Hi all, I just installed a small system from a running system using
>> sys-i686-20010406.tgz
>
>Hey!  A www.sistina.com (LVM) person trying Gentoo Linux!  Thanks ;)

That's right. I am sistina's Senior Sysadmin. :-)

>
>> The first and formost thing I noticed was that syslog spitting out errors
>> everytime the logger tries to make an entry (it can't access
>> /var/log/syslog.d/ dir) so I change the perms, now it says it can't lock the
>> dir. So my syslog is still broken. 
>
>Did you extract the tarball using the "p" option? -->

Doh! Ooops. 

># tar xzvpf ...
>
>If not, then tar didn't preserve the literal directory permissions and this
>is probably causing some problems for you. 

I'll try again. 


>> Next I try to add a user using adduser and that application won't even run, I
>> get "PAM authentication failed" I did however change roots password and am
>> still able to login. 
>
>This is a relatively ancient bug that desperately needs fixing.  I'm not sure
>exactly why PAM is barfing.  If I remember correctly, it can be fixed by zapping
>a file in /etc/pam.d.

Which one, I'll try using vipw and vigr and try to login but I don't think
it'll let me, something in pam's busted for sure. I you can post a fix on the
website (A FAQ question?) that would be great. 


>I agree.  One of the downsides of doing a major development project in your
>"spare" time is that you are forced to step away from development even when
>there are little quirks like this that you know need fixing.  However, I don't
>think there are any major quirks beyond this one.

Well, I rather like the fact that it's mostly hands-on stuff, and if I can get
the authentication thing straight I can hack the rest of it.

Ports man, I love it. Finally a distro with ports.

>Achim didn't include the "vipw" and "vigr" tools in build.tbz2?
>
Didn't try them yet, but on a previous install I used useradd and that worked
o.k. but I still couldn't login with the use I added.
-- 
Ben Lutgens		cell: 612.670.4789
Sistina Software Inc.	worl: 612.379.3951
Code Monkey Support (A.K.A. System Administrator)

Kernel panic: I have no root and I want to scream

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2001-04-18  3:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 20:22 [gentoo-dev] problems with new install Ben Lutgens
2001-04-17 21:10 ` Daniel Robbins
2001-04-17 21:14   ` Daniel Robbins
2001-04-17 21:42   ` Ben Lutgens [this message]
2001-04-17 22:12     ` Daniel Robbins
2001-04-17 23:07       ` Achim Gottinger
2001-04-18 10:22         ` Daniel Robbins
2001-04-18 10:45         ` Ben Lutgens
2001-04-18 10:36       ` Ben Lutgens
2001-04-17 22:13     ` Achim Gottinger
2001-04-17 21:12 ` Achim Gottinger
2001-04-18  9:47   ` Ben Lutgens
2001-04-18 10:25     ` Achim Gottinger
2001-04-18 10:56       ` Ben Lutgens
2001-04-18 11:09         ` Daniel Robbins
2001-04-18 12:01           ` Ben Lutgens
2001-04-18 11:18         ` Achim Gottinger
2001-04-18 11:21           ` Daniel Robbins
2001-04-18 12:05             ` Ben Lutgens
2001-04-18 12:04           ` Ben Lutgens
2001-04-18 11:30         ` Achim Gottinger
2001-04-18 11:58           ` Ben Lutgens
2001-04-17 22:10 ` Achim Gottinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010417224047.A802@minime \
    --to=blutgens@sistina.com \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox