[gentoo-dev] problems with new install

[gentoo-dev] problems with new install

[Ben Lutgens]

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

Re: [gentoo-dev] problems with new install

[Daniel Robbins]

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 ;)

> 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? -->

# tar xzvpf ...

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

> 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.

> 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.

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.

> 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.

Achim didn't include the "vipw" and "vigr" tools in build.tbz2?

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] problems with new install

[Daniel Robbins]

On Tue, Apr 17, 2001 at 09:09:25PM -0600, Daniel Robbins wrote:

> Achim didn't include the "vipw" and "vigr" tools in build.tbz2?

Um... I guess these wouldn't help with no "vi" :)

Silly me,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] problems with new install

[Ben Lutgens]

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

Re: [gentoo-dev] problems with new install

[Daniel Robbins]

On Tue, Apr 17, 2001 at 10:40:47PM -0500, Ben Lutgens wrote:

> >Hey!  A www.sistina.com (LVM) person trying Gentoo Linux!  Thanks ;)
> 
> That's right. I am sistina's Senior Sysadmin. :-)

Nice to meet you :)

> >Did you extract the tarball using the "p" option? -->
> 
> Doh! Ooops. 

daemontools is very picky about directory permissions, so that's why your syslog
was fried.  It's easy to forget the "p" option since it's normally not used when
extracting your typical source tarball.

> 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. 

Unfortunately, I don't think you have "vi" at this point.  Try grabbing the
portage tree from your non-chrooted system, and then copy it to /usr/portage
under your chrooted system.  Then, add the CFLAGS that you want to
/etc/make.conf and then one quick hack -- copy wget from your real system to
/usr/bin on your Gentoo Linux system.  We forgot to add that to build.tbz2.
Then, create the /etc/resolv.conf and hosts files, and wget should then be
able to download from the chrooted environment.  At this point, Portage is
ready for use.

You're ready to merge gcc, binutils, flex and all that good stuff (look for
Achim's previous email for what needs to be remerged).  Use the emerge program:

# emerge foo-1.0.ebuild

To see what *would* be merged (without actually merging), use the --pretend option:

# emerge --pretend foo-1.0.ebuild

After merging the essentials (gcc, binutils, flex), make sure you merge the new
1.5 version of Portage in sys-apps.

Then, to install all essential packages on your system, type:

# emerge system

This will cause everything in /usr/portage/sys-* to be merged automatically -- and
in the proper order.  Nearly everything (if not everything) should compile cleanly,
though you may have a few problems since Achim is in the middle of upgrading to a
new readline on CVS.  Let us know your progress and we'll try to resolve any problems
you have.

After "emerge system" completes successfully, you should have a complete base Gentoo
Linux system.

> 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.

you should be able to simply rename /etc/pam.d/userpadd to useradd, and things should
work.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] problems with new install

[Achim Gottinger]

Daniel Robbins wrote:
> 
> On Tue, Apr 17, 2001 at 10:40:47PM -0500, Ben Lutgens wrote:
> 
> > >Hey!  A www.sistina.com (LVM) person trying Gentoo Linux!  Thanks ;)
> >
> 
> Unfortunately, I don't think you have "vi" at this point.  Try grabbing the
> portage tree from your non-chrooted system, and then copy it to /usr/portage
> under your chrooted system.  Then, add the CFLAGS that you want to
> /etc/make.conf and then one quick hack -- copy wget from your real system to
> /usr/bin on your Gentoo Linux system.  We forgot to add that to build.tbz2.
> Then, create the /etc/resolv.conf and hosts files, and wget should then be
> able to download from the chrooted environment.  At this point, Portage is
> ready for use.

daniel sys-i686... contains all sys apps it's not build.tbz2. So vi is
there and joe also.
> 

I never used -p to extrac the tarball here, but I can remember that I
had this syslog problem here too.
I don't know how I fixed it but it was a real banal thing.
Unfortunately I don't have the sys tarball here, ibiblio is still
unavailable and sourceforge gives me 4k
so I can not test it at the moment.
Jerry told me he had a problem with the kernel on that tarball. He ment
root gets allways mounted ro and he
must manualy remount, then things work.
I took a look into initscripts-install and svc-syslog/klog should not
have caused the syslog problem (well I'm
awake too long this day). I'll test it after a few hours of sleep.

Hmm, I remember a similar problem when /var had a 700 permission. I
tested it a second ago and I got that error report:

multilog: fatal: unable to open directory /var/log/syslog.d: access
denied.

This can be the cause.

bye achim~


> --
> Daniel Robbins                                  <drobbins@gentoo.org>
> President/CEO                                   http://www.gentoo.org
> Gentoo Technologies, Inc.
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] problems with new install

[Daniel Robbins]

On Wed, Apr 18, 2001 at 06:38:01AM +0200, Achim Gottinger wrote:

> daniel sys-i686... contains all sys apps it's not build.tbz2. So vi is
> there and joe also.

Oops, sorry.  For some reason I thought he was using build.tbz2.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] problems with new install

[Ben Lutgens]

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

On Wed, Apr 18, 2001 at 06:38:01AM +0200, Achim Gottinger wrote:
>Daniel Robbins wrote:
>> 
>daniel sys-i686... contains all sys apps it's not build.tbz2. So vi is
>there and joe also.
>> 
>
>I never used -p to extrac the tarball here, but I can remember that I
>had this syslog problem here too.
>I don't know how I fixed it but it was a real banal thing.
>Unfortunately I don't have the sys tarball here, ibiblio is still
>unavailable and sourceforge gives me 4k

Yeah sourceforge has outgrown thier bandwidth it seems. That download was a
real pain, I am on a 10MBps line and it was like pulling teeth.

>so I can not test it at the moment.
>Jerry told me he had a problem with the kernel on that tarball. He ment
>root gets allways mounted ro and he
>must manualy remount, then things work.
>I took a look into initscripts-install and svc-syslog/klog should not
>have caused the syslog problem (well I'm
>awake too long this day). I'll test it after a few hours of sleep.

Nope, those services where already setup properly, most likely it's a /var
perms thing.


>Hmm, I remember a similar problem when /var had a 700 permission. I
>tested it a second ago and I got that error report:
>
>multilog: fatal: unable to open directory /var/log/syslog.d: access
>denied.

Exact same error message I get.

>This can be the cause.
>
>bye achim~
>
>
>> --
>> Daniel Robbins                                  <drobbins@gentoo.org>
>> President/CEO                                   http://www.gentoo.org
>> Gentoo Technologies, Inc.
>> 
>> _______________________________________________
>> gentoo-dev mailing list
>> gentoo-dev@gentoo.org
>> http://www.gentoo.org/mailman/listinfo/gentoo-dev
>
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@gentoo.org
>http://www.gentoo.org/mailman/listinfo/gentoo-dev

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

Re: [gentoo-dev] problems with new install

[Ben Lutgens]

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

On Tue, Apr 17, 2001 at 10:11:23PM -0600, Daniel Robbins wrote:
>
>Nice to meet you :)

Thanks!

>
>> >Did you extract the tarball using the "p" option? -->

Well this time I did, and still multilog is whining. It's gonna irritate me
untill I fix it, I rebooted into my running system as I need to copy my
modules for my kernel (LVM and GFS modules needed to mount my former root
partition so I can get to the iso of gentoo to mount it with the loop device
:-)

I love this stuff.


>> Doh! Ooops. 
>
>daemontools is very picky about directory permissions, so that's why your syslog
>was fried.  It's easy to forget the "p" option since it's normally not used when
>extracting your typical source tarball.

Well, I did use the p option this time so I'm assuming something happend
before I untarred it.

>Unfortunately, I don't think you have "vi" at this point.  Try grabbing the
>portage tree from your non-chrooted system, and then copy it to /usr/portage
>under your chrooted system.  Then, add the CFLAGS that you want to
>/etc/make.conf and then one quick hack -- copy wget from your real system to
>/usr/bin on your Gentoo Linux system.  We forgot to add that to build.tbz2.
>Then, create the /etc/resolv.conf and hosts files, and wget should then be
>able to download from the chrooted environment.  At this point, Portage is
>ready for use.

I have vim actually. I do need to get the kernel recompiled with reiserfs


>
>You're ready to merge gcc, binutils, flex and all that good stuff (look for
>Achim's previous email for what needs to be remerged).  Use the emerge program:
>
># emerge foo-1.0.ebuild
>
>To see what *would* be merged (without actually merging), use the --pretend option:

can I take all this stuff off the iso I downloaded?


>
># emerge --pretend foo-1.0.ebuild
>
>After merging the essentials (gcc, binutils, flex), make sure you merge the new
>1.5 version of Portage in sys-apps.
>
>Then, to install all essential packages on your system, type:
>
># emerge system
>
>This will cause everything in /usr/portage/sys-* to be merged automatically -- and
>in the proper order.  Nearly everything (if not everything) should compile cleanly,
>though you may have a few problems since Achim is in the middle of upgrading to a
>new readline on CVS.  Let us know your progress and we'll try to resolve any problems
>you have.
>
>After "emerge system" completes successfully, you should have a complete base Gentoo
>Linux system.


This is all great stuff to add to the installation guide!

>
>> 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.
>
>you should be able to simply rename /etc/pam.d/userpadd to useradd, and things should
>work.
>
>Best Regards,
>
>-- 
>Daniel Robbins					<drobbins@gentoo.org>
>President/CEO					http://www.gentoo.org 
>Gentoo Technologies, Inc.			
>
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@gentoo.org
>http://www.gentoo.org/mailman/listinfo/gentoo-dev

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

Re: [gentoo-dev] problems with new install

[Achim Gottinger]

Ben Lutgens wrote:
> 
> 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.

Again, rename /etc/pam.d/userpadd to /etc/pam.d/useradd and it will
work. But you must create the users homedir. After that you can user
passwd to add a password for that user.

bye achim~

> --
> 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
> 
>   ------------------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature

Re: [gentoo-dev] problems with new install

[Achim Gottinger]

Ben Lutgens wrote:
> 
> 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.

Rhm, I thought I fixed this issue in this sys. Take a look at /etc/pam.d
there must be three files useradd groupadd and shadow, both with the
same content.
Arg I took a quick look and found a typing bug. rename userpadd to
useradd. :/

Sorry for the inconvenience this sys is a snapshot release.

This syslog thing sounds realy strange, I will take a look at it later
(4:30am here).
Maybe remerging gluelog/daemontools (both in sys-apps) solves this
problem.
If you don't speak polis you should also remerge the man package in
sys-apps. 

achim~
> 
> 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
> 
>   ------------------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature

Re: [gentoo-dev] problems with new install

[Ben Lutgens]

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

On Wed, Apr 18, 2001 at 04:42:49AM +0200, Achim Gottinger wrote:
>Ben Lutgens wrote:
>
>Rhm, I thought I fixed this issue in this sys. Take a look at /etc/pam.d
>there must be three files useradd groupadd and shadow, both with the
>same content.
>Arg I took a quick look and found a typing bug. rename userpadd to
>useradd. :/

I thought userpass looked odd, but didn't give it a second thought. 

>
>Sorry for the inconvenience this sys is a snapshot release.

Well, I stumbled acrodd the rc4 dir that was free of the preN tag and assumed
I had found the next "stable" rc before it was posted to the website, I'd
suggest a README in that dir outlining a couple caveats and warnings. 

>Maybe remerging gluelog/daemontools (both in sys-apps) solves this
>problem.
>If you don't speak polis you should also remerge the man package in
>sys-apps. 

Doh! :-) O.k. will do, I'll keep posting bugs and such. It's kinda nice ot be
able to help out a new distro especially one with developers so eager to help.


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

Re: [gentoo-dev] problems with new install

[Achim Gottinger]

> I thought userpass looked odd, but didn't give it a second thought.
> 
I fixed this bug on cvs.
> >
> Well, I stumbled acrodd the rc4 dir that was free of the preN tag and assumed
> I had found the next "stable" rc before it was posted to the website, I'd
> suggest a README in that dir outlining a couple caveats and warnings.

Yes, i'll move it to a snashot subdir.
> 
> >Maybe remerging gluelog/daemontools (both in sys-apps) solves this
> >problem.
> >If you don't speak polis you should also remerge the man package in
> >sys-apps.
> 
> Doh! :-) O.k. will do, I'll keep posting bugs and such. It's kinda nice ot be
> able to help out a new distro especially one with developers so eager to help.

Hmm, olease checp the permission of /var first. I think it has 700 in
the tarball, because I did
alot of things manually while I prepared it.

Ignore all the other suggestions I wrote yesterday, it was 4am here and
I was not fully awake. :)

Yes, getting bug reports is really neccesarry since we are 4-5
developers for 500 packages, so we can
not test everything intensive.

bye achim~

> 
> --
> 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
> 
>   ------------------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature

Re: [gentoo-dev] problems with new install

[Ben Lutgens]

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

On Wed, Apr 18, 2001 at 05:56:34PM +0200, Achim Gottinger wrote:
>
>> I thought userpass looked odd, but didn't give it a second thought.
>> 
>I fixed this bug on cvs.

Auth works, I had to simple rename userpadd to useradd as you said. thanks.

>> >
>> Well, I stumbled acrodd the rc4 dir that was free of the preN tag and assumed
>> I had found the next "stable" rc before it was posted to the website, I'd
>> suggest a README in that dir outlining a couple caveats and warnings.
>
>Yes, i'll move it to a snashot subdir.
>> 
>Hmm, olease checp the permission of /var first. I think it has 700 in
>the tarball, because I did
>alot of things manually while I prepared it.

O.k. /var is 755 /var/log is 755  and /var/log/syslog.d is 755 and I still get 
multilog: fatal: unable to lock directory /var/log/syslog.d: access denied

they are owned by root.root and are not suid or sgid.

You guys included LVM tools in the distro? Holy crap! SWEET!

>
>Ignore all the other suggestions I wrote yesterday, it was 4am here and
>I was not fully awake. :)
>
>Yes, getting bug reports is really neccesarry since we are 4-5
>developers for 500 packages, so we can
>not test everything intensive.
>
>bye achim~
>
>> 
>> --
>> 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
>> 
>>   ------------------------------------------------------------------------
>>    Part 1.2Type: application/pgp-signature
>
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@gentoo.org
>http://www.gentoo.org/mailman/listinfo/gentoo-dev

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

Re: [gentoo-dev] problems with new install

[Daniel Robbins]

On Wed, Apr 18, 2001 at 11:54:55AM -0500, Ben Lutgens wrote:

> O.k. /var is 755 /var/log is 755  and /var/log/syslog.d is 755 and I still get 
> multilog: fatal: unable to lock directory /var/log/syslog.d: access denied
> 
> they are owned by root.root and are not suid or sgid.
> 
> You guys included LVM tools in the distro? Holy crap! SWEET!

do this:

# cd /var/log
# chown daemon.root syslog.d klog.d
# chmod 0700 syslog.d klog.d

Both of these directories should have been owned by daemon.  This should fix
it.  rm any files inside syslog.d and klog.d just to be sure.

Yep, LVM tools are included by default, although I think they are 0.9.1-beta4
or 5 and not beta-7.  I'll make sure that our next kernel includes the latest
LVM patches and tools.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] problems with new install

[Ben Lutgens]

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

On Wed, Apr 18, 2001 at 11:08:25AM -0600, Daniel Robbins wrote:
>On Wed, Apr 18, 2001 at 11:54:55AM -0500, Ben Lutgens wrote:
>
>> O.k. /var is 755 /var/log is 755  and /var/log/syslog.d is 755 and I still get 
>> multilog: fatal: unable to lock directory /var/log/syslog.d: access denied
>> 
>> they are owned by root.root and are not suid or sgid.
>> 
>> You guys included LVM tools in the distro? Holy crap! SWEET!
>
>do this:

Cool.


># cd /var/log
># chown daemon.root syslog.d klog.d
># chmod 0700 syslog.d klog.d
>
>Both of these directories should have been owned by daemon.  This should fix
>it.  rm any files inside syslog.d and klog.d just to be sure.
>
>Yep, LVM tools are included by default, although I think they are 0.9.1-beta4
>or 5 and not beta-7.  I'll make sure that our next kernel includes the latest
>LVM patches and tools.

Cool! let me know if I can be of any help. My cube is right next to the build
master for LVM and GFS. I'd love to help out anyway I can. 

The sys package I used has 0.9.1_beta6 (which is what my kernel was compiled
with) which makes me happy. GFS is taking steps to be as fast as reiser as a
local fs. There are some bad things with 2.4 memory management that cause me
to tell you NOT to include it yet :-) This machine is running GFS on LVM as
root. I am in the process of migrating it to Reiser on LVM under Gentoo.

>Best Regards,
>
>-- 
>Daniel Robbins					<drobbins@gentoo.org>
>President/CEO					http://www.gentoo.org 
>Gentoo Technologies, Inc.			
>
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@gentoo.org
>http://www.gentoo.org/mailman/listinfo/gentoo-dev

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

Re: [gentoo-dev] problems with new install

[Achim Gottinger]

> 
> O.k. /var is 755 /var/log is 755  and /var/log/syslog.d is 755 and I still get
> multilog: fatal: unable to lock directory /var/log/syslog.d: access denied
> 
> they are owned by root.root and are not suid or sgid.

This is going to get mysterious.
How about /var/lib/supervise/{control,services}
I'm downloading the sys tarball right now. ibiblio's bandwith problem
seems fixed I get full 80K now.

> 
> You guys included LVM tools in the distro? Holy crap! SWEET!

holy or crap? Daniel wrote an article about LVM for IBM so now we have
it. 
It's a must for a bleeding edge distro. :)
I'm planning to test GFS too, since nfs<->reiserfs is a mess at the
moment.

achim~

Re: [gentoo-dev] problems with new install

[Daniel Robbins]

On Wed, Apr 18, 2001 at 06:49:19PM +0200, Achim Gottinger wrote:

> This is going to get mysterious.  How about
> /var/lib/supervise/{control,services} I'm downloading the sys tarball right
> now. ibiblio's bandwith problem seems fixed I get full 80K now.

What about /var/lib/supervise/{control,services}?  Permissions?

> > You guys included LVM tools in the distro? Holy crap! SWEET!

> holy or crap? Daniel wrote an article about LVM for IBM so now we have it.
> It's a must for a bleeding edge distro. :) I'm planning to test GFS too,
> since nfs<->reiserfs is a mess at the moment.

Also, Samba is a good alternative since mounting smb shares is working really
well these days.  Not sure if file locking is supported on mounted smb shares
(although it is supported by Samba itself).

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] problems with new install

[Ben Lutgens]

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

On Wed, Apr 18, 2001 at 11:20:53AM -0600, Daniel Robbins wrote:
>On Wed, Apr 18, 2001 at 06:49:19PM +0200, Achim Gottinger wrote:
>
>> This is going to get mysterious.  How about
>> /var/lib/supervise/{control,services} I'm downloading the sys tarball right
>> now. ibiblio's bandwith problem seems fixed I get full 80K now.
>
>What about /var/lib/supervise/{control,services}?  Permissions?
>
>> > You guys included LVM tools in the distro? Holy crap! SWEET!
>
>> holy or crap? Daniel wrote an article about LVM for IBM so now we have it.
>> It's a must for a bleeding edge distro. :) I'm planning to test GFS too,
>> since nfs<->reiserfs is a mess at the moment.
>
>Also, Samba is a good alternative since mounting smb shares is working really
>well these days.  Not sure if file locking is supported on mounted smb shares
>(although it is supported by Samba itself).

Stay clear of GFS on 2.4 for the time being, Ken (The lead architecht and
genius of GFS)

>
>Best Regards,
>
>-- 
>Daniel Robbins					<drobbins@gentoo.org>
>President/CEO					http://www.gentoo.org 
>Gentoo Technologies, Inc.			
>
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@gentoo.org
>http://www.gentoo.org/mailman/listinfo/gentoo-dev

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

Re: [gentoo-dev] problems with new install

[Ben Lutgens]

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

On Wed, Apr 18, 2001 at 06:49:19PM +0200, Achim Gottinger wrote:
>> 
>> O.k. /var is 755 /var/log is 755  and /var/log/syslog.d is 755 and I still get
>> multilog: fatal: unable to lock directory /var/log/syslog.d: access denied
>> 
>> they are owned by root.root and are not suid or sgid.
>
>This is going to get mysterious.
>How about /var/lib/supervise/{control,services}
>I'm downloading the sys tarball right now. ibiblio's bandwith problem
>seems fixed I get full 80K now.
>
>> 
>> You guys included LVM tools in the distro? Holy crap! SWEET!
>
>holy or crap? Daniel wrote an article about LVM for IBM so now we have
>it. 
>It's a must for a bleeding edge distro. :)
>I'm planning to test GFS too, since nfs<->reiserfs is a mess at the
>moment.

Take it from me, GFS is much better with NFS than reiser, we have a patch
against NFS that helps out where Ken fixed some assumptions that the NFS folks
made that caused race conditions that were not triggered by ext2.

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

Re: [gentoo-dev] problems with new install

[Achim Gottinger]

> 
> O.k. /var is 755 /var/log is 755  and /var/log/syslog.d is 755 and I still get
> multilog: fatal: unable to lock directory /var/log/syslog.d: access denied
> 
/var/log/syslog.d must be owned by daemon.wheel

/var/lib/supervise/services/{syslog,klog}/run must be owned by
root.wheel (perm 750)

achim~

Re: [gentoo-dev] problems with new install

[Ben Lutgens]

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

On Wed, Apr 18, 2001 at 07:01:01PM +0200, Achim Gottinger wrote:
>> 
>> O.k. /var is 755 /var/log is 755  and /var/log/syslog.d is 755 and I still get
>> multilog: fatal: unable to lock directory /var/log/syslog.d: access denied
>> 
>/var/log/syslog.d must be owned by daemon.wheel
>
>/var/lib/supervise/services/{syslog,klog}/run must be owned by
>root.wheel (perm 750)

Thanks, sorry bout all this. After the install /var/log/syslog.d was owned by
bin.wheel.

>
>achim~
>
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@gentoo.org
>http://www.gentoo.org/mailman/listinfo/gentoo-dev

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

Re: [gentoo-dev] problems with new install

[Achim Gottinger]

Ben Lutgens wrote:
> 
> 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.
> 
Try "rc-update add svc-syslog" and "rc-update add sys-klog" and things
should work.

> 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.
> 

You must create the users homedir manual then you can login 

achim~