Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Mar 1995 16:32:35 -0600 (CST)
From:      jbryant@server.iadfw.net
To:        phk@ref.tfs.com (Poul-Henning Kamp)
Cc:        freebsd-hackers@FreeBSD.org
Subject:   Re: What happened to my include files!@#
Message-ID:  <199503302232.QAA14830@server.iadfw.net>
In-Reply-To: <199503302034.MAA14343@ref.tfs.com> from "Poul-Henning Kamp" at Mar 30, 95 12:34:20 pm

next in thread | previous in thread | raw e-mail | index | archive | help
In reply:
> From: Poul-Henning Kamp <phk@ref.tfs.com>
> Subject: Re: What happened to my include files!@#
> To: jbryant@server.iadfw.net
> Date: Thu, 30 Mar 1995 12:34:20 -0800 (PST)
> Cc: freebsd-hackers@FreeBSD.org
> 
> > After having relative success with the 950210 snap, I just installed the 
> > 950322 snap on my system yesterday hoping to solve a few problems.
> > 
> > 1). How did the include files get screwed up?
> > 
> > 2). Many passwd file operations do not now work, including the passwd(1) 
> > command.
> 
> You need to change the owner for /usr/bin/passwd
> 
> > The matcd info cannot be changed via the -c flag either.  I attempted to 
> > assign a different port for matcd0 and it always comes back that matcd0 
> > is unknown when giving any command using it at the config> prompt.
> On the list.

Thanks.  Upon doing this, I was able to get my password back to normal.  
One more problem in the distribution showed up though.

I'll have to double check the distribution again, but I could swear I had 
skey.access deleted in /etc prior to installing the snap dist.  I was 
damn lucky I still had a shell open from which to rm /etc/skey.access...

If /etc/skey.access is in the distribution itself, I suggest it be 
renamed to something like skey.access.sample so that those of us using 
the old-style passwords won't be locked out of our systems.

Also, I think I should elaborate on exactly what happened with the 
include files.  It seems that upon installing the new snapshot, 
/usr/include/sys, and several other subdirectories of /usr/include were 
deleted and replaced with symlinks to /sys/sys and it's subdirectories.

The problem here is that /usr/src/sys/sys was deleted during install, and 
apparently not installed from the distribution.

The second problem here is that I feel that general shell users [at least 
here] should not have access to the OS sources.  I understand that it is 
probably a real pain to keep /usr/include in sync with the kernel 
includes, but from a security standpoint, why not keep the includes the 
way they were...

The old way:

chown root:wheel /usr/src
chmod 700 /usr/src

The new way:

[a lot more bs]

Regardless, the include files I need just do not exist on my system 
anymore.  My question: did I screw up the install, or did someone screw up 
the release?

Jim
-- 
All opinions expressed are mine, if you   | "I will not be pushed, stamped,
think otherwise, then go jump into turbid | briefed, debriefed, indexed, or
radioactive waters and yell WAHOO !!!     | numbered!" - #1, "The Prisoner"
     jbryant@server.iadfw.net, System administrator, Internet America



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503302232.QAA14830>