I can’t seem to do anything with this folder. I have a custom header file
which I usually
throw in there and it works fine on my 6.0 but using a fresh 6.1 install I
get tons of
errors trying to cp it in there as root. I can’t even change permissions of
the folder
as root.
Are you using the 6.1 beta or the GA release?
I think I remember hearing about similar problems in the intial beta.
Try downloading the GA if you haven’t already.
I can’t seem to do anything with this folder. I have a custom header file
which I usually
throw in there and it works fine on my 6.0 but using a fresh 6.1 install I
get tons of
errors trying to cp it in there as root. I can’t even change permissions of
the folder
as root.
Are you using the 6.1 beta or the GA release?
I think I remember hearing about similar problems in the intial beta.
Try downloading the GA if you haven’t already.
I can’t seem to do anything with this folder. I have a custom header file
which I usually
throw in there and it works fine on my 6.0 but using a fresh 6.1 install I
get tons of
errors trying to cp it in there as root. I can’t even change permissions of
the folder
as root.
Are you using the 6.1 beta or the GA release?
I think I remember hearing about similar problems in the intial beta.
Try downloading the GA if you haven’t already.
I downloaded the *.iso on 7 July 2001 and did a clean install of
all the x86 stuff.
It’s a problem with the DDK’s - deactivate them, and /usr/include gets
unlocked.
I’m not really doing anything with the DDKs right now anyway but that
seems rather weird to lockout access to a pretty important folder for
programming just because I want to program…
Are you using the 6.1 beta or the GA release?
I think I remember hearing about similar problems in the intial beta.
Try downloading the GA if you haven’t already.
I downloaded the *.iso on 7 July 2001 and did a clean install of
all the x86 stuff.
It’s a problem with the DDK’s - deactivate them, and /usr/include gets
unlocked.
I’m not really doing anything with the DDKs right now anyway but that
seems rather weird to lockout access to a pretty important folder for
programming just because I want to program…
It’s a problem with the DDK’s - deactivate them, and /usr/include gets
unlocked.
I’m not really doing anything with the DDKs right now anyway but that
seems rather weird to lockout access to a pretty important folder for
programming just because I want to program…
It is a bug which managed to slip through un-noticed. You
can work around the problem by doing the following:
mkdir /
mkdir /usr
mkdir /usr/include
This has been fixed internally but is not in the release.
Lee R. Copp <> Lee.R.Copp@michiganscientific.com> > wrote:
It’s a problem with the DDK’s - deactivate them, and /usr/include gets
unlocked.
I’m not really doing anything with the DDKs right now anyway but that
seems rather weird to lockout access to a pretty important folder for
programming just because I want to program…
It is a bug which managed to slip through un-noticed. You
can work around the problem by doing the following:
mkdir /
mkdir /usr
mkdir /usr/include
This has been fixed internally but is not in the release.