[±¤-°í] ´ã¹è ÇÇ¿ì½Ã´Â ºÐµéÀº ¹Ýµå½Ã º¸¼¼¿ä.

Title: O³ªµµÀ̹ø¿£²À¼º°øÇÒ¼öÀÖ´Ù.ÇÑ´Þ´ã¹è°ª3¸¸¿øÁ¤µµ¸¸ÅõÀÚÇϽøéÇÇ¿ì½Ã¸é¼­²÷À»¼öÀÖ½À´Ï´Ù. O ³ªµµ À̹ø¿£ ²À ¼º°ø ÇÒ ¼ö ÀÖ´Ù. ÇÑ´Þ ´ã¹è°ª 3¸¸¿ø Á¤µµ¸¸ ÅõÀÚÇϽøé ÇÇ¿ì½Ã¸é¼­ ²÷À» ¼ö ÀÖ½À´Ï´Ù. ½Å¿ëÄ«µå ±¸ÀÔÇϽŠ¸ðµçºÐ²² 200¸¸¿ø »ó´çÀÇ ¾ÆÄí¾Æ¹Ì³×¶ö Á¤¼ö±â ÁõÁ¤ À̺¥Æ®¸¦ ½Ç½ÃÇÕ´Ï´Ù.  

·§ÃŴʵäÔÚÏß²éѯ¿ªÍ¨

Title: ʹÓÃ˵Ã÷ ¹¤ÓûÉÆÆäÊ£¬±ØÏÈÀûÆäÆ÷£¡ Öйú·§ÃÅÐÐÒµÒ»´óʢʡªÓ¢ºº·§ÃÅË«Ïò²éѯµç×Ӵʵ侭¹ý¼è¿àµÄŬÁ¦ÖÕÓÚµ®ÉúÁË£¡ÊÇ·§ÃÅÖÆÔìÉÌ¡¢Ê¯ÓÍ¡¢Ê¯»¯¡¢»¯¹¤µÈÐÐÒµ²¿Ãŵķ§ÃÅÓû§¡¢·§ÃÅÏúÊÛ¹«Ë¾¡¢Íâó¹«Ë¾¡¢¿ÆÑÐÔºËù´ÓÊ·§ÃÅÉè¼ÆÑо¿ÈËÔ±¼°¿Æ¼¼·­ÒëÈËÔ±µÄµÃÁ¦ÖúÊÖ£¬»¶Ó­Ê¹Óã¡  ÖÚËùÖÜÖª£¬·­ÒëÀë²»¿ª´Êµä£¬²é´Ê

联合购买电子E刊二○○二年第十期!

___ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd

Re: I am slowly going crazy 1,2,3,4,5,6 switch

> Any hints would be appriciated. Try this: http://www.walfield.org/papers/hurd-misc/manual-bootstrap.txt ___ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd

¿Ïµµ ±ÝÀϼöÇù¼ö»ê ÀÔ´Ï´Ù[Á¤º¸]

Title: ±ÝÀϼöÇù¼ö»ê ±¤°í¸ÞÀÏ.            ¿Ïµµ ±ÝÀϼö»ê¾÷Çùµ¿Á¶ÇÕÀÇ ÀÚ»ç ±ÝÀϼöÇù¼ö»êÀÔ´Ï´Ù.   ÀúÈñ ¼öÇù¼ö»ê¿¡¼­´Â ûÁ¤ÇØ¿ª ¿Ïµµ¿¡¼­ ³ª¿À´Â ¸ðµç ¼ö»ê¹°, ƯÈ÷ ´Ù½Ã¸¶ ¸¦ °¡Áö°í ¿©·¯°¡Áö »óÇ°È­ Çϴµ¥ ¼º°øÇÏ¿© Àü±¹¿¡ À¯Åë°ú ¼¼°è ¿©·¯³ª¶ó¿¡ ÀÚ¶û½º·´°Ô ¼öÃâÇÏ´Â ±ÝÀϼöÇù¼ö»ê ÀÔ´Ï´Ù. º

I am slowly going crazy 1,2,3,4,5,6 switch

Ok, I've changed hostmux to use getaddrinfo, but I am having a problem. I CAN'T hostmux to WORK. Anyway, I can't give any useful debugging information because I can't get any. I get the same results when I compile hostmux from within the Hurd sources and as a standalone program, a bit of make

Re: core file writing

Can you put this into gdb and test it if you get a chance? I'm CC'ing to bug-hurd, in hopes that someone else might test this out and follow up either with fixes or confirmation that it works. I'm not quite sure if gdb's "gcore" will be happy doing just the memory part when there is no make_core

Re: core file writing

> Yes. I saw this afternoon how to walk through memory with vm_region and > I think I have this part of it in hand. Basic idea as I understand it > is: Well, inexactly, yes. There is also some old unfinshied code in hurd/exec/ that did some of this. I pointed you at vminfo because that is a wo

Re: core file writing

Roland McGrath wrote: > > The proc server is not really much involved. You need to understand the > structure of the system and what Mach tasks and threads are about in some > detail before attempting to work on this. I can always attempt. Whether I succeed or not depends on my understanding. I

(no subject)

Title: www.informesuteis.com.br   Edição 05 - ANO 1 - março de 2002www.informesuteis.com.br Especial Mulher - Dia internacional da mulher - 8 de março - como a mulher vem vencendo

Re: core file writing

The proc server is not really much involved. You need to understand the structure of the system and what Mach tasks and threads are about in some detail before attempting to work on this. Certainly writing an ELF core file is the right thing to do. How to store the memory is clear, and that par

Re: oskit-mach: device_write

> In order to trigger the bug again, I setted data_count to 4. bytes_written > return the value 18677512. But bytes_written does not match to size which > the driver returns: That is pretty strange. There are two things here that are not right. That value from ops->write_inband (61) is bogus for

Re: oskit-mach/libstore breakage

Roland McGrath <[EMAIL PROTECTED]> writes: > > libstore uses device_map with size and offset being null. > > Urmph. To my mind, this just illustrates that the current io_map interface > model is really wrong and that an io_map call that takes offset and size > parameters is the way to go (as

½ÎÀÌÆ® µî·ÏÇϼ¼¿ä

¡á15¸¸¿ø¼îÇθô¡Ý Á¦°ø¼­ºñ½º*20,000¿© »óÇ° °ø±Þ.Á¾ÇÕ¸ô ¹× Àü¹®¸ô *ÁÖ¹®, ¹è¼Û, ¹ÝÇ°, »óÇ°°ü¸® ¹°·ù ¿ø½ºÅé¼­ºñ½º*(´ç»ç¿¡¼­ ¸ðµÎó¸®) ¢º¼îÇθô±Ã±ÝÁõ ¢ºÆǸŻóÇ°º¸±â ¢ºµðÀÚÀκ¸±â ¢º¼ÀÇú¸±â1 ¢º¼ÀÇú¸±â2 ¢º¼ÀÇú¸±â3 ¢º¼ÀÇú¸±â4 ¢º¼ÀÇú¸±â5 ¡á¾÷¼Ò¿ëȨÆäÀÌÁö9¸¸9õ¿ø ¢º¸Þ´º¾ó µÑ·¯º¸±â ¢ºÈ¸»ç¿¬Çõ¹×º¸µµÀ

Re: oskit-mach: device_write

Sorry for being so unclear, I'm trying to be more specific. I was referring to this (stolen from the mach docs): kern_return_t device_write (device_t device, dev_mode_t mode, recnum_t recnum, io_buf_ptr_t data

Re: core file writing

On Mon, Mar 04, 2002 at 04:38:42PM -0700, Jon Arney wrote: > Roland: > > Since you said it's not really very hard to do, I thought I'd make > an attempt at it with your permission. You don't need any permission to hack, it's free software! :) Jeroen Dekkers -- Jabber supporter - http://www.jab

Re: core file writing

On Mon, Mar 04, 2002 at 04:38:42PM -0700, Jon Arney wrote: > Roland: > > Since you said it's not really very hard to do, I thought I'd make > an attempt at it with your permission. I'm sure he will give it to you :) > I am guided by other elf core writers (such as Linux's) and it seems > to be

Re: MIG installation problems

On Tue, Mar 05, 2002 at 06:49:22PM +0100, Dorian Vallant wrote: > Hello Hurd Team, > > I have a problem with the MIG. The error is: > . > . > make install > . > gcc migcom.o parser.tab.o lexxer.o error.o string.o type.o routine.o > statement.o global.o vprint.o header.o user.o server.o utils.o

[±¤-°í] ´ã¹è ÇÇ¿ì½Ã´Â ºÐµéÀº ¹Ýµå½Ã º¸¼¼¿ä.

Title: O³ªµµÀ̹ø¿£²À¼º°øÇÒ¼öÀÖ´Ù.ÇÑ´Þ´ã¹è°ª3¸¸¿øÁ¤µµ¸¸ÅõÀÚÇϽøéÇÇ¿ì½Ã¸é¼­²÷À»¼öÀÖ½À´Ï´Ù. O ³ªµµ À̹ø¿£ ²À ¼º°ø ÇÒ ¼ö ÀÖ´Ù. ÇÑ´Þ ´ã¹è°ª 3¸¸¿ø Á¤µµ¸¸ ÅõÀÚÇϽøé ÇÇ¿ì½Ã¸é¼­ ²÷À» ¼ö ÀÖ½À´Ï´Ù. ½Å¿ëÄ«µå ±¸ÀÔÇϽŠ¸ðµçºÐ²² 200¸¸¿ø »ó´çÀÇ ¾ÆÄí¾Æ¹Ì³×¶ö Á¤¼ö±â ÁõÁ¤ À̺¥Æ®¸¦ ½Ç½ÃÇÕ´Ï´Ù.  

Re: hostname again.

> Roland, can you compare the current behavior of dir-mkfile.c with the > open mode bits, and make a suggestion about what you think we should > do? This is our own function, so we can tweak the semantics as we > please. I changed it to mask out the same bits as done in dir_lookup.