Summer Special From Sunguard 32191

2001-07-13 Thread RVToys7
Title: Home Page Submit NOW  for your  FREE CATALOG! Go aheadÿ97treat yourself.  Browse through The RV Toy StoreÿAE Catalog! Check out our own exclusive, 18-year industry-leading Sunguardÿ99 line ... including tons of goodies for your RVÿ97& Tow Car too!  Check it out

Re: sending ports in reply msg

2001-07-13 Thread Marcus Brinkmann
On Thu, Jul 12, 2001 at 08:01:13PM -0400, Roland McGrath wrote: > proc_setexecdata never deallocates the old port rights. Isn't the following code doing the job? if (std_port_array) { for (i = 0; i < n_std_ports; i++) mach_port_deallocate (mach_task_self (), std_port_array[i]

Re: More on oskit-mach debugging

2001-07-13 Thread Igor Khavkine
Jeroen Dekkers wrote: > > On Fri, Jul 13, 2001 at 09:21:57AM -0400, Igor Khavkine wrote: > > Now if I was still linking with the version of oskit in the Hurd archives > > all my problems would be solved and I would be able to boot properly. > > However, I have compiled my own version of OSKit to

Re: More on oskit-mach debugging

2001-07-13 Thread Jeroen Dekkers
On Fri, Jul 13, 2001 at 09:21:57AM -0400, Igor Khavkine wrote: > Now if I was still linking with the version of oskit in the Hurd archives > all my problems would be solved and I would be able to boot properly. > However, I have compiled my own version of OSKit to get debigging > symbols. Now I ge

More on oskit-mach debugging

2001-07-13 Thread Igor Khavkine
Hi, all. After a bit more of oskit-mach debugging I've had some partial success. My network card is now working with the OSKit driver. All I had to do is change the [oskit]/linux/src/drivers/net/tulip.c file to a newer version. Since I knew my card was working with linux-2.2.19, I just took the d

RE: inquiry 20208

2001-07-13 Thread Kandee3
Title: Take Control Of Your Conference Calls Long Distance ConferencingOnly 18 Cents Per Minute Connects Up To 100 Participants! No setup fees No contracts or monthly fees Call anytime, from anywhere, to anywhere International Dial In 18 cen

Re: sending ports in reply msg

2001-07-13 Thread Thomas Bushnell, BSG
Roland McGrath <[EMAIL PROTECTED]> writes: > proc_getexecdata and proc_setexecdata both seem to be totally broken. > It seems like they have never actually been called. Surely true. > I think the only correct thing for proc_getexecdata to do is add a user ref > to each port and then set *portsp