[net.unix-wizards] strncpy

guy@rlgvax.UUCP (Guy Harris) (09/01/83)

The kernel does not use "strncmp" at all for comparing directory entries.
Given this, there is a bug in "fsck" (V7, S3, 4.1BSD) where it will NOT zero
out the full d_name portion of a directory entry when it is reattaching an
orphan file to "lost+found".  If the slot being used for that had a pathname
longer than the (6 or 7, depending on which UNIX) characters used by the
reattachment name, you will end up with a totally inaccessible file with a
null character in the middle of its name.

	Guy Harris
	{seismo,mcnc,we13,brl-bmd,allegra}!rlgvax!guy

hal@cornell.UUCP (Hal Perkins) (09/04/83)

Why are so many articles about C also posted to unix-wizards?  Is there
any need for this?

The reason I complain is that there is a lot of traffic in both news
groups.  I read these groups in my spare time (when waiting for troff
or TeX to do something, for instance), and I rarely have time to read
through both of these groups in one sitting.  Readnews appears to be
unable to filter articles posted to several groups unless you read all
of the groups at the same time.

Of course, the real solution would be to fix the news programs so they
would remember what articles have been read, regardless of when.  This
is a long standing bug, and it is pretty annoying that it hasn't been
fixed sometime in the last few releases of readnews.

But even if the news stuff is fixed, why can't all the C articles be
posted to net.lang.c, all the micro stuff to net.micro, and just the
Unix operating system items to net.unix-wizards?  It would be easier
to filter through the tremendous amount of stuff in unix-wizards if
as much of it as possible were posted to more relevent specialized
groups.

Arrrrgh


Hal Perkins                         UUCP: {decvax|vax135|...}!cornell!hal
Cornell Computer Science            ARPA: hal@cornell  BITNET:  hal@crnlcs

jbray%bbn-unix@sri-unix.UUCP (09/14/83)

From:  James Bray <jbray@bbn-unix>

I would like to join a discussion of extensions to C if one should start.
Here are some ideas that I have just had lying around in a file:

Needs a "restart" construct to reenter a for loop (as for example when having
slept in it and needing to completely recommence);

Loops of all kinds, and perhaps all scopes, should be nameable. Break,
continue, and the proposed restart could accept these labels as an optional
argument: when used in this way, it would indicate that the desired action be
performed on the given scope, with the default being as for the current usage;

These are a couple of ideas which might help C to become a genuinely goto-less
language. They should reduce or eliminate the need for "goto loop" and
"goto out" which one sees so often in the kernel.

--Jim Bray