> 2) In alpha's entry.S, many sys_ calls were changed to osf_ calls. Dosn't
> this break source-level compatiblity for the old names? (But I don't
> know the reason for those calls: perhaps we only need to worry about
> binary compatiblity.
No, it doesn't. Userland programs call the kernel by stuffing a
system call number into a register and invoking a trap. The system
call numbers are in <asm/unistd.h>. The names in <asm/unistd.h>
must stay the same for source compatibility, and the numbers in
<asm/unistd.h> and the table order in entry.S must stay the same
for binary compatibility. But the names you see in entry.S are
completely internal.
> 4) I think the "%%" -> "%" change in "100% soundblaster compatible" will
> cause xconfig to barf; it's better to make [menu]config display an extra
> "%". (in tcl/tk, % is a metachar)
Try it. It works for me in oldconfig, menuconfig, and xconfig. If you
look at kconfig.tk after it gets generated, you will see that this string
winds up in quotes.
The %% is a relic from drivers/sound/configure.c, function think_positively,
which says:
fprintf(stderr, prompt);
... where it should say:
fprintf(stderr, "%s", prompt);
Michael Chastain
<mailto:mec@shout.net>
"love without fear"