Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 03 Feb 1997 16:24:35 -0800
From:      "Todd S. Hansen" <tshansen@ucsd.edu>
To:        David Nugent <davidn@unique.usn.blaze.net.au>
Cc:        Greg Lehey <grog@lemis.de>, FreeBSD Questions <questions@FreeBSD.org>
Subject:   Re: Can't send local mail (or use bash) after recompiling kernel
Message-ID:  <32F681C3.41C67EA6@ucsd.edu>
References:  <32F320E7.6A3@ucsd.edu> <199702021113.MAA11222@freebie.lemis.de> <19970203023339.PI13773@usn.blaze.net.au>

next in thread | previous in thread | raw e-mail | index | archive | help
Yeah!!!
That worked.
Here is my idea of how the problem occured as I agree that the cause is
important to id.

1. I recompiled the kernel with a couple of options that may have been
buggy.

I think it was one or both of these combined. 

pseudo-device snp0
pseudo-device vn  #vnode filesystem driver

Anyway, when I compiled it modified permissions on six directories (I
know I couldn't have done that myself without knowing it). 
Then by running you magic commands, it check them and switched them
back.

Anyway, now it appears to work. 
My kernel has currenlt vn active and snp0 deactivated and it appears to
work. But, I haven't recompiled the kernel since I did the mtree. But, I
have a fix for the problem so I can experiment with it and find the
problem now :-)

Thanks a lot everyone that helped me out. Sure saved me a bunch of work
on mid-term week.
	-Taco


David Nugent wrote:
> 
> grog@lemis.de writes:
> > > seems to be working fine. Then I tried to send mail to my friend (local
> > > account) and it gave me an error that it could not execute mail.local. I
> > > have checked the file it listed (directory too) and it has the correct
> > > priviliges as a matter of fact, anybody can execute it.
> ~
> >
> > There's no reason to believe that this problem relates to the kernel,
> > so installing another kernel will probably not help much.  I'd guess
> > that you have a directory permission problem.  Check these:
> >
> > $ ls -ld /usr/bin /bin /usr/libexec
> > drwxr-xr-x  2 bin  bin  1024 Feb  1 15:41 /bin
> > drwxr-xr-x  2 bin  bin  6144 Feb  1 15:53 /usr/bin
> > drwxr-xr-x  5 bin  bin  1024 Feb  1 15:53 /usr/libexec
> 
> FWIW, I find that the following commands help:
> 
>         cd / ; mtree -deU -f /etc/mtree/BSD.root.dist
>         cd /usr ; mtree -deU -f /etc/mtree/BSD.usr.dist
>         cd /var ; mtree -deU -f /etc/mtree/BSD.var.dist
> 
> mtree is great for sorting out problems like this.
> 
> > Reinstalling a complete operating system is overkill for just about
> > any problem you might have.
> 
> Amen.
> 
> And the second problem is to discover how it happened in the
> first place. I'd feel very uneasy indeed finding things like
> this.
> 
> Regards,
> 
> David Nugent - Unique Computing Pty Ltd - Melbourne, Australia
> Voice +61-3-9791-9547  Data/BBS +61-3-9792-3507  3:632/348@fidonet
> davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/

-- 

Todd Hansen, KD6YPS (Taco)
tshansen@ucsd.edu
taco@mad.scientist.com
http://sehplib.ucsd.edu/~tshansen/
ftp://tshansen.reshall.ucsd.edu/index.htm
Wintalk click here: http://tshansen.reshall.ucsd.edu/taco.wtk

"Whenever any form of government becomes destructive...it is the right
of the people to alter or to abolish it"  - Declaration Of Independence



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32F681C3.41C67EA6>