The 'poor user code' I was referring to are some of the newer utilities
that use syscalls only available in newer kernels (and end up getting psc
syscalls in this case). The latest version of psc works around this.
The psc module allows user-programs to make use of RTLinux so programmers
can use the RTLinux UNIX signals style interface rather than kernel
modules. If you're not using that then you can unload the psc module and
shouldn't have any trouble with the ID's. If you try it out and it fails
let me know, please. I can find out what's going on.
} > Make sure the psc.o module is not loaded. Poor user code and a mistake in
} > our early verions of psc would allow this.
} Actually, what is the psc.o module good for, and second,
} in which respect "poor user code" can influence the uid
} resolution in the non-rt side of the kernel?
}
} peterw
} --
} Dr. Peter Wurmsdobler
}
} CTM - Centre de Transfert des Microtechniques
} 39, av. de l'Observatoire, BP-1445, 25007 Besancon CEDEX 3
} TELEPHONE: +33 3 81 47 70 20 TELECOPIE: +33 3 81 47 70 21
} E-mail: [EMAIL PROTECTED]
}
} Ceterum censeo MIRCOSOFTem esse delendam..
}
} ----- End of forwarded message from [EMAIL PROTECTED] -----
} -- [rtl] ---
} To unsubscribe:
} echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
} echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
} --
} For more information on Real-Time Linux see:
} http://www.rtlinux.org/rtlinux/
----- End of forwarded message from [EMAIL PROTECTED] -----
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
