Title: Àü¿øÀϱⱤ°í¸ÞÀÏ
½Å¹ß¸íÇ°ÀÌ ¿Ï¼ºµÇ¸é ±ÍÇϲ² ¸ÕÀú ¼±º¸Àϱî ÇÕ´Ï´Ù.¿øÄ¡ ¾ÊÀ¸½Ç °æ¿ì ¼ö½Å°ÅºÎ¸¦ ´·ÁÁÖ¼¼¿ä!
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/m
I've added a script that the Hurd will install as /bin/fakeroot. I think
this will be sufficiently compatible to the Debian/Linux fakeroot package
to use it for building Debian packages, but that has yet to be tried. This
is a trivial script that brings together three independent features, all o
Title: form-mail
Á¤º¸Åë½ÅºÎ ±Ç°í »çÇ׿¡ ÀÇ°Å Á¦¸ñ¿¡
[±¤°í]¶ó°í Ç¥±âÇÑ ±¤°í ¸ÞÀÏÀÔ´Ï´Ù.¼ö½ÅÀ» ¿øÄ¡ ¾ÊÀ¸½Ã¸é
¼ö½Å°ÅºÎ¸¦
´·¯ÁÖ¼¼¿ä
¾È³çÇϽʴϱî?
°íÇ°°Ý ¼¼»ó»ç´Â À̾߱Ⱑ ÀÖ´Â
I've added a new mode of operation to the settrans command, in the form of
the new option --chroot. I have not tested this code, so please try it out
for me.
settrans --chroot is a way to start a filesystem translator that need not
be attached to any parent filesystem node as an active translato
Roland McGrath <[EMAIL PROTECTED]> writes:
> You are atypical. On my system, for any given build I do, all the files
> fit in core and are already in the cache if I've done a previous compile
> recently, and the only disk activity is writing of new bits that the
> computation rarely blocks on.
Jeroen Dekkers <[EMAIL PROTECTED]> writes:
> But I was talking about a filesystem where it doesn't matter if there
> is data loss in the case of a crash. For example, I wouldn't care if
> the data of my glibc build is lost or corrupted. In that case we don't
> need it and providing an option whic
On Sat, May 04, 2002 at 03:06:58PM -0700, Thomas Bushnell, BSG wrote:
> Jeroen Dekkers <[EMAIL PROTECTED]> writes:
>
> > Sorry for my stupidity, but I don't see why fsck can't remove the
> > corrupted part and replace it with some sane stuff. It knows how the
> > filesystem should look like, so i
> I have found that compiling is a disk-bound activity since about
> 1988, on every system I've used...When I build a Linux kernel, the
> disk is continuously bumping along.
You are atypical. On my system, for any given build I do, all the files
fit in core and are already in the cache if I've d
Á¤º¸Åë½ÅºÎ ±Ç°í »çÇ׿¡ ÀÇ°Å Á¦¸ñ¿¡[±¤°í] ¶ó°í Ç¥±âÇÑ ±¤°í
¸ÞÀÏÀÔ´Ï´Ù.
¼ö½ÅÀ» ¿øÄ¡¾ÊÀ¸¸é ¼ö½Å°ÅºÎ¸¦ ´·¯ÁÖ¼¼¿ä.
Jeroen Dekkers <[EMAIL PROTECTED]> writes:
> Sorry for my stupidity, but I don't see why fsck can't remove the
> corrupted part and replace it with some sane stuff. It knows how the
> filesystem should look like, so it can change it so that it will look
> like that. Could you please explain why t
[EMAIL PROTECTED] (Niels Möller) writes:
> Right, it would improve the speed significantly, but it wouldn't get
> rid of the "harddisk is thrashing hard all the time while I'm
> compiling, even if I have plenty of RAM and all the source files are
> cached"-behaviour.
I have found that compiling
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
> [EMAIL PROTECTED] (Niels Möller) writes:
>
> > I guess I should have asked for the ratio B/A. If that's small, as you
> > claim, there should be a significant gain. _If_ it turned out that A
> > and B were of the same size, then the gain would b
On Sat, May 04, 2002 at 02:11:48PM -0700, Thomas Bushnell, BSG wrote:
> Jeroen Dekkers <[EMAIL PROTECTED]> writes:
>
> > > The bugs that happen are *not* merely that you lose occasional object
> > > files. You can get arbitrary corruption.
> >
> > And then fsck can repair that in the case of a
(À̸ÞÀÏ µ¥ÀÌŸ 8000¸¸°³¿Í(¹«·á) ¼ö½Ê°³ ÇÁ·Î±×·¥ À» Á¦°øÇÕ´Ï´Ù)
°Ô½ÃÆÇ µ¥ÀÌŸ µî ·¹µå½ºÆÄÀ̵å 4.0 Á¤Ç° µîµî ¼ö½Ê°³
ÇÁ·Î±×·¥
ÀÌ ´Üµ·300.000¿ø ÀÔ´Ï´Ù »ç½Ç ·¹µå ½ºÆÄÀÌ´õ 1°³°ª¹Û¿¡ ¾ÊµÇ´Â
¾×¼öÀÔ´Ï´Ù
Á¤Ç°250.000¿ø...¸ÞÀÏ µ¥ÀÌŸ´Â 1000¸¸°³´Â ÇѸÅÀÏ Á¦°Å Áߺ¹Á¦°Å
ѱ¸¿©
³ª¸ÓÁö µ¥ÀÌŸµµ ·¹µå½ºÆÄÀÌ´
Jeroen Dekkers <[EMAIL PROTECTED]> writes:
> > The bugs that happen are *not* merely that you lose occasional object
> > files. You can get arbitrary corruption.
>
> And then fsck can repair that in the case of a crash, right?
No.
The normal rules--the ones that I describe as "bug free" keep
[EMAIL PROTECTED] (Niels Möller) writes:
> I guess I should have asked for the ratio B/A. If that's small, as you
> claim, there should be a significant gain. _If_ it turned out that A
> and B were of the same size, then the gain would be quite small,
> decreasing the number of required syncs at
On Sat, May 04, 2002 at 01:22:58PM -0700, Thomas Bushnell, BSG wrote:
> Jeroen Dekkers <[EMAIL PROTECTED]> writes:
>
> > I think that for compilation we don't need to synchronize everything
> > to be sure the filesystem the compilation happens on has an
> > inconsistent. It doesn't really matter
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
> I'm quite sure it would help a lot.
Ok, that's good to know.
> Number (A) is quite large. Number (B), which is the case you asked
> about, is quite small.
I guess I should have asked for the ratio B/A. If that's small, as you
claim, there sho
[EMAIL PROTECTED] (Niels Möller) writes:
> I'd like to know if implementing the new scheme would really help
> making the statement "The Hurd is significantly slower than Linux for
> things like big compiles" false. If it's an optimization that's worth
> the effort.
I'm quite sure it would help
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
> [EMAIL PROTECTED] (Niels Möller) writes:
>
> > Does anybody have any idea how often this case occurs with typical
> > activities like compilation?
>
> What's the point of the question: to decide if we can ignore the
> issue, or to decide if the
Jeroen Dekkers <[EMAIL PROTECTED]> writes:
> I think that for compilation we don't need to synchronize everything
> to be sure the filesystem the compilation happens on has an
> inconsistent. It doesn't really matter if you lose some objects
> files. Maybe it would be a nice thing to provide this
On Sat, May 04, 2002 at 08:34:20PM +0200, Niels M?ller wrote:
> Thanks for the explanation. I'm trying to understand what consequences
> for performance can be expected.
>
> [EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
>
> > There are cases (as noted before) where the following sequence aris
Title: Untitled Document
¡Ø º» ¸ÞÀÏÀº
Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀÇ°ÅÇÑ '±¤°í' ¸ÞÀÏÀÔ´Ï´Ù. ¡Ø
e-mailÁÖ¼Ò´Â ÀÎÅͳݻ󿡼 ÃëµæÇÏ¿´À¸¸ç, ÁÖ¼Ò¿Ü ¾î¶°ÇÑ °³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö ¾Ê½À´Ï´Ù
°³¿îÇÑ ¾Æħ Æí¾ÈÇÑ ÇϷ縦
Ãß±¸ÇÏ´Â ³×¶¼·ç¸¶´ÏÀÔ´Ï´Ù.
³×¶¼·ç¸¶´Ï´Â "Àá½Ãµ¿¾
Title: Untitled Document
¡Ø º» ¸ÞÀÏÀº
Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀÇ°ÅÇÑ '±¤°í' ¸ÞÀÏÀÔ´Ï´Ù. ¡Ø
e-mailÁÖ¼Ò´Â ÀÎÅͳݻ󿡼 ÃëµæÇÏ¿´À¸¸ç, ÁÖ¼Ò¿Ü ¾î¶°ÇÑ °³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö ¾Ê½À´Ï´Ù
°³¿îÇÑ ¾Æħ Æí¾ÈÇÑ ÇϷ縦
Ãß±¸ÇÏ´Â ³×¶¼·ç¸¶´ÏÀÔ´Ï´Ù.
³×¶¼·ç¸¶´Ï´Â "Àá½Ãµ¿¾
[EMAIL PROTECTED] (Niels Möller) writes:
> Does anybody have any idea how often this case occurs with typical
> activities like compilation?
What's the point of the question: to decide if we can ignore the
issue, or to decide if the solution has to be terribly efficient?
> With the current code
The talk about child hurds and faking devices has brought a question to
my mind, which I hope you can shed some light on.
We do need some abstraction that represents control over the hardware.
Like the Mach master device port. If you have a send right to that,
you can do whatever you like with th
Thanks for the explanation. I'm trying to understand what consequences
for performance can be expected.
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
> There are cases (as noted before) where the following sequence arises:
>
> write block A
> write block B
> write block A again
>
> and wher
Title: °Ãß!! ¼ºÀε¿¿µ»ó
±ÍÇÏÀÇ ¸ÞÀÏÁÖ¼Ò´Â À¥¼ÇÎ Áß¿¡¼ ¾Ë°Ô µÈ°ÍÀ̸ç, E_Mail ÁÖ¼Ò ¿Ü¿¡, ´Ù¸¥ Á¤º¸´Â °®°í ÀÖÁö ¾Ê½À´Ï´Ù.
´õ ÀÌ»ó ÀÌ¿Í À¯»çÇÑ Á¤º¸¿¡ °üÇÑ À̸ÞÀÏÀÇ ¼ö½Å°ÅºÎ¸¦ ¿øÇϽøé
¼ö½Å°ÅºÎ ¸¦ ´·¯ ÁÖ¼¼¿ä.
ÀÌ Á¤º¸³»¿ëÀº û¼Ò³âÀ¯ÇظÅü¹°·Î¼ Á¤º¸Åë½Å¸ÁÀÌ¿ë ÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü ¹
Title: Litoo newsletter
Litoo's
letter
(May, 2002)
Quick search
(author, title or commentary)
Letter FREE
Email:
Register Unregister
(Si vous souhaitez
recevoir notre lettre en
¢º °¡°ÝÆı«!!! ¹«Çѱâ´É!!!
Çϳª.¸ÅÁ÷¼¥ Ãʱâ¼ÂÆúñ ¹«·á : Ãʱâ¼ÂÆúñ ¹«·áÀ̹ǷΠ¸Å¿ù 3¸¸¿ø »ç¿ë·á¸¸À¸·Î ¼îÇθô¿î¿µ
µÑ.¸ÅÁ÷¼¥ 1°³¿ù ¹«·á»ç¿ë : 1°³¿ùµ¿¾È ¹«·á·Î ¸¶À½²¯ »ç¿ëÇÏ½Ã°í °áÁ¤ÇϽʽÿä
¼Â.½Ç½Ã°£ ÀÚµ¿¾÷±×·¹À̵å : ¼îÇθôÀÇ ±â´ÉÀÌ ÀÚµ¿ÀûÀ¸·Î ¾÷±×
O º» ¸ÞÀÏÀº Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀÇ°ÅÇÑ [±¤°í] ¸ÞÀÏÀÔ´Ï´ÙO
e-mailÁÖ¼Ò´Â ÀÎÅͳݻ󿡼 ÃëµæÇÏ¿´À¸¸ç, ÁÖ¼Ò¿Ü ¾î¶°ÇÑ °³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö ¾Ê½À´Ï´Ù
¼ö½Å°ÅºÎ
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://ma
»çÀü¿¡
±ÍÇÏÀÇ Çã¶ô¾øÀÌ ¸ÞÀÏÀ» µå·Á Áø½ÉÀ¸·Î »ç°úµå¸³´Ï´Ù.
±ÍÇÏ¿¡°Ô
»çÀüÇã¶ôÀ» ¹ÞÁö ¾Ê°í ¸ÞÀÏÀ» º¸³»°Ô µÇ¾î Áø½ÉÀ¸·Î »ç°úµå¸³´Ï´Ù.
ÀúÈñ´Â ±ÍÇÏÀÇ À̸ÞÀÏ ÀÌ¿Ü¿
[¼ö½Å°ÅºÎ]
O º» ¸ÞÀÏÀº Á¤º¸Åë½Å¸Á
ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀÇ°ÅÇÑ [±¤°í] ¸ÞÀÏÀÔ´Ï´Ù. e-mailÁÖ¼Ò´Â ÀÎÅͳݻ󿡼 ÃëµæÇÏ¿´À¸¸ç, ÁÖ¼Ò¿Ü
¾î¶°ÇÑ °³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö ¾Ê½À´Ï´Ù. ¼ö½ÅÀ» ¿øÇÏÁö ¾ÊÀ¸½Ã¸é ¼ö½Å°ÅºÎ¸¦ ÇØ Áֽʽÿä.
[¼ö½Å°ÅºÎ]
O Çã¶ô¾øÀÌ ¸ÞÀÏÀ» º¸³»¼ Á˼
Title: :: web agency - inpiritz
º» ¸ÞÀÏÀº Á¤º¸Åë½ÅºÎ ±Ç°í »çÇ׿¡ ÀÇ°Å
Á¦¸ñ¿¡ [±¤°í]¶ó Ç¥½ÃµÈ ±¤°í ¸ÞÀÏÀÔ´Ï´Ù.
¼ö½Å°ÅºÎ
¹öÆ°À» Ŭ¸¯ÇÏ½Ã¸é ¼ö½Å°ÅºÎ󸮰¡ ÀÌ·ç¾î Áý´Ï´Ù.
___
Bug-hurd mailing list
[
[¼ö½Å°ÅºÎ]
O º» ¸ÞÀÏÀº Á¤º¸Åë½Å¸Á
ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀÇ°ÅÇÑ [±¤°í] ¸ÞÀÏÀÔ´Ï´Ù. e-mailÁÖ¼Ò´Â ÀÎÅͳݻ󿡼 ÃëµæÇÏ¿´À¸¸ç, ÁÖ¼Ò¿Ü
¾î¶°ÇÑ °³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö ¾Ê½À´Ï´Ù. ¼ö½ÅÀ» ¿øÇÏÁö ¾ÊÀ¸½Ã¸é ¼ö½Å°ÅºÎ¸¦ ÇØ Áֽʽÿä.
[¼ö½Å°ÅºÎ]
O Çã¶ô¾øÀÌ ¸ÞÀÏÀ» º¸³»¼ Á˼
Title: http://www.1212tour.com/¿¡¼ È®ÀÎ ¹Ù¶ø´Ï´Ù.
Äܵµ¿©Çà,
ÇØ¿Ü¿©Çà,
Á¹¾÷¿©Çàµî ¿©ÇàÀÇ ¸ðµç °Í
http://www.1212tour.com¿ï¸ªµµ
ºÀ·¡ÆøÆ÷
Title: Untitled Document
è!º·fj)b b²Ðn«v !¶Úþf¢ ?¨¥©ÿ+-wèý» êÝ
»çÀü¿¡
±ÍÇÏÀÇ Çã¶ô¾øÀÌ ¸ÞÀÏÀ» µå·Á Áø½ÉÀ¸·Î »ç°úµå¸³´Ï´Ù.
±ÍÇÏ¿¡°Ô
»çÀüÇã¶ôÀ» ¹ÞÁö ¾Ê°í ¸ÞÀÏÀ» º¸³»°Ô µÇ¾î Áø½ÉÀ¸·Î »ç°úµå¸³´Ï´Ù.
ÀúÈñ´Â ±ÍÇÏÀÇ À̸ÞÀÏ ÀÌ¿Ü¿
O º» ¸ÞÀÏÀº Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀÇ°ÅÇÑ [±¤°í] ¸ÞÀÏÀÔ´Ï´ÙO e-mailÁÖ¼Ò´Â ÀÎÅͳݻ󿡼 ÃëµæÇÏ¿´À¸¸ç, ÁÖ¼Ò¿Ü ¾î¶°ÇÑ °³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö ¾Ê½À´Ï´Ù
39 matches
Mail list logo
