The operating system we are building is called GNU.
Developing the GNU system is a big project.
It's called the GNU Project.
We developed many programs specifically for GNU,
and these are called GNU programs.
We developed some licenses, such as the GNU GPL.
But GNU is, first of all, the operating
They will have no clue that it is an OS unless we are VERY
explicit in calling it an OS. So we should refer to is as "the GNU
operating system".
Sure, there's no problem with saying "operating system" to help
clarify things.
___
Bug-hurd
when you build a program to work on an directory, all that you will need
from that package is the binary location.
I do not understand any of that. I think you need to give labels
to the various entities that you are talking about, and describe their
relationships clearly.
What you
What he's saying is,
rather than doing this, you should just have a utility that keeps the
PATH environment variable updated (by adding hte packages' bin/ and
sbin/ directories), updates ld.so.conf, and so on.
This would be a big step backward. It would result in gigantic PATH
val
I do not think that keep a loop symlink of USR->/ is a good idea,
since you will never be able to do a "find / -name
*something*". So, we need to correct those scripts. (* There are
scripts with references to /usr/python or /usr/local/perl)
Doesn't find know enough not
and when the time comes,
I don't think the time will ever come.
I agree completely; we should not suppose that we will
ever eliminate `/usr'.
___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd
