¾È³çÇϼ¼¿ä...½ÃÆ®Áö.¶ìº®Áö Àü¹®Á¡ ÀÔ´Ï´ÙÀûÀº µ·À¸·Î Áý¾ÈºÐÀ§±â¸¦ »õ·Ó°Ô ¹Ù²ã º¸¼¼¿ä!
-.½ÌÅ©´ë »öÀ» ¹Ù²Ù½Ã°í ½ÍÀ¸½ÅºÐ.+++±×¸²À» Ŭ¸¯ÇÏ¸é ¹Ù·Î °©´Ï´Ù+++
-.À¯¸®Ã¢¿¡ ¸ÚÁø ±×¸²À» ºÙÀÌ°í ½ÍÀ¸½Å ºÐ
.
-.Ä¿Æ°ÀÇ ¿ªÇÒµµ ´ë½ÅÇÏ¸ç ½Ç³»ºÐÀ§±â ¿¬Ãâ ¹× ÇÁ¶óÀ̹ö½Ã º¸È£¿¡µµ À¯¿ëÇÕ´Ï´Ù.-. À¯¸®Ã¢ÀÌ ±úÁ
Title: ½õ³Ì»õÔËÍø
±×µ¿¾È ³í¹®¹× ·¹Æ÷Æ® ÀڷḦ ã¾Æ À̸®Àú¸® Çì¸Å¿´À» °Å¶ó »ý°¢ÇÕ´Ï´Ù.
ÀúÈñ nonmunok°¡ »õ·Ó°Ô ´ÜÀåÀ» ÇÏ°í ¿©·¯ºÐÀ» ã¾Æ°©´Ï´Ù..
³í¹®ÀÚ·á¹× ·¹Æ÷Æ® ÀÚ·á ¹«·áÁ¦°ø°ú ÇÔ²² Åë°ÔºÐ¼®, ÃÊ·ÏÀÛ¼º, ÄÚÆÃ, ¼³¹®ÀÛ¼º,
³í¹®ÀÔ·Â
¹× ¼öÁ¤ÀÛ¾÷°ú ÇÔ²² ¿ÀÇÁ¶óÀÎÀ¸·Î ³í¹® ÀÚ·á Ä«ÇÇ ÀÛ¾÷±îÁö Çѹø¿¡ ¸ðµç°ÍÀÌ ÀÌ·ç¾îÁöµµ
·Ï
* [Thomas Bushnell, BSG]
> Right. If you want copy-gid-on-setgid, then you need to inherit
> setgid. If not, then not.
Obviously correct. I was assuming that setgid was not inherited, but it
is. Just to be sure, I tested it, too.
So we end up with the SysV/Linux way being able to emulate t
Title: Network Center°¡ µå¸®´Â Event
¡¡
±ÍÇÏÀÇ ½Â¶ô¾øÀÌ È«º¸¼º ÀüÀÚ ¿ìÆíÀ»
º¸³»°Ô µÈ Á¡ Á¤ÁßÈ÷ »ç°ú µå¸³´Ï´Ù. Á¤º¸Åë½Å¸ÁÀÌ¿ëÃËÁø¹ý ±ÔÁ¤À» ÁؼöÇÏ¿© ±¤°í¸ÞÀÏÀÓÀ» Ç¥½ÃÇÏ¿´À¸¸ç, ¼ö½Å°ÅºÎ ÀåÄ¡¸¦
¸¶·ÃÇÏ°í ÀÖ½À´Ï´Ù.
±ÍÇÏÀÇ ÀüÀÚ ¿ìÆí ÁÖ¼Ò´Â
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> On Fri, Apr 26, 2002 at 02:15:53PM -0700, Thomas Bushnell, BSG wrote:
> > I was just told that the setgid bit does get inherited on the new
> > directories.
>
> Not in the Hurd, though. I guess this would only be so if you activate
> the sysvgroup
[EMAIL PROTECTED] (Paul Jarc) writes:
> [EMAIL PROTECTED] (Thomas Bushnell, BSG) wrote:
> > (You only inherit gid if you are a member of the group.)
>
> False.
Sorry, you're correct. It is, however, no security hole of the sort
that was being implied.
__
On Fri, Apr 26, 2002 at 02:15:53PM -0700, Thomas Bushnell, BSG wrote:
> I was just told that the setgid bit does get inherited on the new
> directories.
Not in the Hurd, though. I guess this would only be so if you activate
the sysvgroups option (assuming you are cool with such an option)
> >
[EMAIL PROTECTED] (Thomas Bushnell, BSG) wrote:
> (You only inherit gid if you are a member of the group.)
False.
$ ls -ld foo
drwxr-sr-x2 prj 12348 Apr 26 17:21 foo
$ id
uid=500(prj) gid=65534(default) groups=65534(default),500(prj),300(users)
$ mkdir foo/bar
$ ls -ld foo/ba
Title: ÃÖ°í 73% Àú·ÅÇÑ "±â¾÷Àü¿ë ÇÒÀÎ ÀüÈ ¼ºñ½º"
ha
KT ´ëºñ ±¹Á¦ÀüÈ ÃÖ°í 73%,½Ã¿ÜÀüÈ ÃÖ°í 37%, À̵¿ÀüÈ ÃÖ°í 16%
Àú·ÅÇÏ¿©, Æò±Õ 50% Àý°¨È¿°ú°¡ ÀÖ½À´Ï´Ù.
KT ¿Í °°Àº ±¤Åë½Å¸ÁÀ» ÀÌ¿ëÇÏ¿©, ÀÎÅͳÝÆù ¼ºñ½º¿Í´Â ´Þ¸® ÃÖÀ
Oystein Viggen <[EMAIL PROTECTED]> writes:
> The difference is that the SysV way won't work for more than one level
> of directories. Once you start making dirs within dirs[1], your sgid is
> not inherited, and group ownership falls back to your default group,
> instead of what you want.
I was
Title: °³² ¾ÆÀÌƼ ±³À°¼¾ÅÍ!
°³² IT ±³À°¼¾ÅÍ
±³À°»
On Sunday 14 April 2002 03:35, Thomas Bushnell, BSG wrote:
> Roland McGrath <[EMAIL PROTECTED]> writes:
> > It seems reasonable to me to leave it up to the filesystem-specific code
> > to decide what nodes it might need to lock, and just give it enough
> > information to avoid deadlock. I have in
> How about making it a libdiskfs option (assuming it is diskfs making this
> decision)? Linux has this option for mount:
That sounds fine to me. It is very easy to implement.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/li
Title: ¢Æ Çϳª·Î ¶óÀÌÇÁ Ŭ·´¿¡ ¿À½Å°ÍÀ» ȯ¿µÇÕ´Ï´Ù.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
On Fri, Apr 26, 2002 at 10:35:52AM -0700, Thomas Bushnell, BSG wrote:
> As long as the setgid bit is inherited too, then yeah, this works as
> well.
Yes, it is on Linux.
> But I think I'd prefer to leave the Hurd as-is. Among other things,
> it will help Debian out and make portability *better
On Fri, Apr 26, 2002 at 09:57:44AM -0700, Thomas Bushnell, BSG wrote:
> The reason why the copy-gid-from directory behavior is better:
How about making it a libdiskfs option (assuming it is diskfs making this
decision)? Linux has this option for mount:
grpid or bsdgroups / nogrpid or sys
Oystein Viggen <[EMAIL PROTECTED]> wrote:
> The difference is that the SysV way won't work for more than one level
> of directories. Once you start making dirs within dirs[1], your sgid is
> not inherited, and group ownership falls back to your default group,
> instead of what you want.
False.
$
On Fri, Apr 26, 2002 at 09:57:44AM -0700, Thomas Bushnell, BSG wrote:
> Marcus Brinkmann <[EMAIL PROTECTED]> writes:
>
> > > I think that I prefer Linux's behaviour.
> >
> > I think, too, esp because of the sgid flag. I wonder what Thomas thinks.
>
> The reason why the copy-gid-from directory
Cher client,
Vous venez de vous inscrire à la lettre d'information de Litoo
L'adresse électronique communiquée est: [EMAIL PROTECTED]
Cette lettre vous sera envoyée mensuellement voir deux fois par mois
exceptionnellement
Elle vous tiendra au courant de nos nouvelles parutions et des développ
Cher client,
Vous venez de vous inscrire à la lettre d'information de Litoo
L'adresse électronique communiquée est: [EMAIL PROTECTED]
Cette lettre vous sera envoyée mensuellement voir deux fois par mois
exceptionnellement
Elle vous tiendra au courant de nos nouvelles parutions et des développ
Cher client,
You just have been registered to Litoo newsletter
Your email is: [EMAIL PROTECTED]
This letter will be sent monthly and excepionnaly twice a month
You will be aware about litoo's new releases and new events
To help us, you can tell your friends to register themselves to our letter
* [Paul Jarc]
> This works with the SysV (aka Linux) behavior as well: if a directory
> is setgid, any files created within it inherit the group id, and any
> directories created within it inherit both the group id and the setgid
> bit.
The difference is that the SysV way won't work for more th
[EMAIL PROTECTED] (Paul Jarc) writes:
> This works with the SysV (aka Linux) behavior as well: if a directory
> is setgid, any files created within it inherit the group id, and any
> directories created within it inherit both the group id and the setgid
> bit.
As long as the setgid bit is inheri
[EMAIL PROTECTED] (Thomas Bushnell, BSG) wrote:
> A given project might be group "foobie", and all the people working on
> that project are in the group. They use a umask of 002. Everything
> works Just Great! Because when they create files or directories
> inside the project, they automaticall
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> > I think that I prefer Linux's behaviour.
>
> I think, too, esp because of the sgid flag. I wonder what Thomas thinks.
The reason why the copy-gid-from directory behavior is better:
Imagine a rich set of groups on your computer--representing pro
º» ¸ÞÀÏÀº Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀÇ°ÅÇÑ [±¤°í] ¸ÞÀÏÀÔ´Ï´Ù.
e-mailÁÖ¼Ò´Â ÀÎÅͳݻ󿡼 ÃëµæÇÏ¿´À¸¸ç,ÁÖ¼Ò¿Ü ¾î¶°ÇÑ°³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö¾Ê½À´Ï´Ù.
º» ¸ÞÀÏÀº ÀÏȸ¼º
À̹ǷΠ¼ö½Å°ÅºÎ¸¦ ÇϽÇÇÊ¿ä°¡
¾ø½À´Ï´Ù.
±Û·Î¹ß¾îÇпø
º» ¸ÞÀÏÀº Á¤º¸Åë½ÅºÎ ±Ç°í »çÇ׿¡ ÀÇ°Å Á¦¸ñ¿¡ [±¤°í]¶ó Ç¥½ÃµÈ ±¤°í ¸ÞÀÏÀÔ´Ï´Ù.º» ³»¿ëÀº
½ºÆÔ¸ÞÀÏÀÇ À¯Çü¿¡ ¾Æ¹«°Íµµ ¼ÓÇÏÁö ¾Ê½À´Ï´Ù.(ÇǶó¹Ìµå, Çà¿îÀÇÆíÁö, ¼ºÀΰü·ÃÈ«º¸ µî)¶ÇÇÑ ±ÍÇÏÀÇ À̸ÞÀÏ
Please accept our sincere apology if the e-mail repeats
itself due to group-mailing system despite
the refusal of receiving of them.
..¾È³çÇϼ¼¿ä? ÇÑ¿ïµðÁöÅØÁÖ½Äȸ»ç(º¸À̽ºÅ©¶ô¼ðÃÑÆÇ)ÀÔ´Ï´Ù . ±Ý¹ø ÀúÈñȸ»ç¿¡¼
"º¸À̽ºÅ©¶ô¼ð"°³¹ß (½Ç¿ë
ƯÇã) ÇÏ¿© Àü±¹ Áö¿ªÀûÀ¸·Î ÀÌ»ç¾÷¿¡ ÇÔ²²
µ¿ÂüÇÏ½Ç ºÐ( ´ë¸®
On Thu, Apr 25, 2002 at 08:33:06PM -0400, Joshua Judson Rosen wrote:
> > , and relieves us from fixing the broken package build scripts (I am
> > not sure how many there are. Potentially many, but as long as you
> > build as root in root owned directories
>
> or use fakeroot?
Please port it to
Title: The Road to Millionaire!!
The
Road to Millionaire!!
´ç½ÅÀº ¹é¸¸ÀåÀÚÀÇ ±æÀ» °ÉÀ¸½Ã°Ú½À´Ï±î?
[Yes][No]
¼ö½Å°ÅºÎ
¹é¸¸ÀåÀÚŬ·´ Ä¿¹Â´ÏƼ ±¸°æ¿À¼¼¿© ! ÿÿ
32 matches
Mail list logo
