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: [gentoo-dev] problems with new install
Date: Tue Apr 17 20:22:02 2001	[thread overview]
Message-ID: <20010417212119.B715@minime> (raw)

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

Hi all, I just installed a small system from a running system using
sys-i686-20010406.tgz

I made a fs, mounted it under /mnt and untared that bad-boy from my currently
running system, did all the steps in the install doc, did an init 1, then
chroot to the new system. I exited chrooted env, unmounted then booted cleanly
to gentoo. 

This is when the fun began ( I love this stuff )

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. 

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. 

I'd really like to get this running at _least_ to a point where I can start to
tinker with ports. I don't mind some hacking but I'd think at least the
authentication should work on initial install.

Other than these things everything seems to work fine, but I can't seem to add
a user and don't think I'd like to run as root all the time.

TIA
-- 
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 --]

             reply	other threads:[~2001-04-18  2:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 20:22 Ben Lutgens [this message]
2001-04-17 21:10 ` [gentoo-dev] problems with new install Daniel Robbins
2001-04-17 21:14   ` Daniel Robbins
2001-04-17 21:42   ` Ben Lutgens
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=20010417212119.B715@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