>Right now, I have a driver (the audio subsystem I'm working on) which
>will ultimately want to be integrated into Nevada. But it wants to
>access some fields in the uarea of the process that opened the driver
>initially -- specifically the command and arguments.
>
>My code currently does this horribly non-DDI compliant method:
>
> if (ttoproc(curthread)) {
> bcopy(PTOU(ttoproc(curthread))->u_comm,
> c->c_command, sizeof (c->c_command));
> bcopy(PTOU(ttoproc(curthread))->u_psargs,
> c->c_psargs, sizeof (c->c_psargs));
> }
>
>
I can only say: Gross!
I'm surprised that you need to do this in a driver, apparently it also
means that you have a set of applications you need to change differently.
Certainly, anything in Solaris should be fixed when the audio framework
is changed, including GNOME and other programs.
What programs are we talking about? And what exactly do you differently
for those applications?
And if I happen to use one of those names for one of my applications,
will it work differently if I rename it?
Casper
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
