Why does chmod +w not give write permission to other(o)

When I run chmod +w filename it doesn't give write permission to other, it just gives write permission to user and group.

After executing this command

chmod +w testfile.txt

running ls -l testfile.txt prints

-rw-rw-r-- 1 ravi ravi 20 Mar 10 18:09 testfile.txt

but in case of +r and +x it works properly.

I don't want to use chmod ugo+w filename.

edited Mar 14 '18 at 9:15

Anthony Geoghegan

7,56543954

asked Mar 10 '18 at 12:50

Ravi Sevta

17718

2

askubuntu.com/a/718782/158442
– muru
Mar 10 '18 at 13:01

1

If you don't want to use ugo, use a.
– muru
Mar 10 '18 at 13:02

yes, but i just want to know why +w not working.
– Ravi Sevta
Mar 10 '18 at 13:20

That's why I left two comments.
– muru
Mar 10 '18 at 13:22

@muru. You claim in your askubuntu answer that you reference above that "This behavior is POSIX-mandated, and so, not a bug". Please be advised that POSIX Application Usage text is non-normative and is therefore not mandated by POSIX.
– fpmurphy
Mar 11 '18 at 5:38

|
show 2 more comments

When I run chmod +w filename it doesn't give write permission to other, it just gives write permission to user and group.

After executing this command

chmod +w testfile.txt

running ls -l testfile.txt prints

-rw-rw-r-- 1 ravi ravi 20 Mar 10 18:09 testfile.txt

but in case of +r and +x it works properly.

I don't want to use chmod ugo+w filename.

edited Mar 14 '18 at 9:15

Anthony Geoghegan

7,56543954

asked Mar 10 '18 at 12:50

Ravi Sevta

17718

2

askubuntu.com/a/718782/158442
– muru
Mar 10 '18 at 13:01

1

If you don't want to use ugo, use a.
– muru
Mar 10 '18 at 13:02

yes, but i just want to know why +w not working.
– Ravi Sevta
Mar 10 '18 at 13:20

That's why I left two comments.
– muru
Mar 10 '18 at 13:22

@muru. You claim in your askubuntu answer that you reference above that "This behavior is POSIX-mandated, and so, not a bug". Please be advised that POSIX Application Usage text is non-normative and is therefore not mandated by POSIX.
– fpmurphy
Mar 11 '18 at 5:38

|
show 2 more comments

When I run chmod +w filename it doesn't give write permission to other, it just gives write permission to user and group.

After executing this command

chmod +w testfile.txt

running ls -l testfile.txt prints

-rw-rw-r-- 1 ravi ravi 20 Mar 10 18:09 testfile.txt

but in case of +r and +x it works properly.

I don't want to use chmod ugo+w filename.

edited Mar 14 '18 at 9:15

Anthony Geoghegan

7,56543954

asked Mar 10 '18 at 12:50

Ravi Sevta

17718

When I run chmod +w filename it doesn't give write permission to other, it just gives write permission to user and group.

After executing this command

chmod +w testfile.txt

running ls -l testfile.txt prints

-rw-rw-r-- 1 ravi ravi 20 Mar 10 18:09 testfile.txt

but in case of +r and +x it works properly.

I don't want to use chmod ugo+w filename.

linux command-line permissions chmod

edited Mar 14 '18 at 9:15

Anthony Geoghegan

7,56543954

asked Mar 10 '18 at 12:50

Ravi Sevta

17718

edited Mar 14 '18 at 9:15

Anthony Geoghegan

7,56543954

asked Mar 10 '18 at 12:50

Ravi Sevta

17718

edited Mar 14 '18 at 9:15

Anthony Geoghegan

7,56543954

edited Mar 14 '18 at 9:15

Anthony Geoghegan

7,56543954

edited Mar 14 '18 at 9:15

Anthony Geoghegan

7,56543954

asked Mar 10 '18 at 12:50

Ravi Sevta

17718

asked Mar 10 '18 at 12:50

Ravi Sevta

17718

asked Mar 10 '18 at 12:50

Ravi Sevta

17718

2

askubuntu.com/a/718782/158442
– muru
Mar 10 '18 at 13:01

1

If you don't want to use ugo, use a.
– muru
Mar 10 '18 at 13:02

yes, but i just want to know why +w not working.
– Ravi Sevta
Mar 10 '18 at 13:20

That's why I left two comments.
– muru
Mar 10 '18 at 13:22

@muru. You claim in your askubuntu answer that you reference above that "This behavior is POSIX-mandated, and so, not a bug". Please be advised that POSIX Application Usage text is non-normative and is therefore not mandated by POSIX.
– fpmurphy
Mar 11 '18 at 5:38

|
show 2 more comments

2

askubuntu.com/a/718782/158442
– muru
Mar 10 '18 at 13:01

1

If you don't want to use ugo, use a.
– muru
Mar 10 '18 at 13:02

yes, but i just want to know why +w not working.
– Ravi Sevta
Mar 10 '18 at 13:20

That's why I left two comments.
– muru
Mar 10 '18 at 13:22

@muru. You claim in your askubuntu answer that you reference above that "This behavior is POSIX-mandated, and so, not a bug". Please be advised that POSIX Application Usage text is non-normative and is therefore not mandated by POSIX.
– fpmurphy
Mar 11 '18 at 5:38

askubuntu.com/a/718782/158442
– muru
Mar 10 '18 at 13:01

If you don't want to use ugo, use a.
– muru
Mar 10 '18 at 13:02

yes, but i just want to know why +w not working.
– Ravi Sevta
Mar 10 '18 at 13:20

That's why I left two comments.
– muru
Mar 10 '18 at 13:22

@muru. You claim in your askubuntu answer that you reference above that "This behavior is POSIX-mandated, and so, not a bug". Please be advised that POSIX Application Usage text is non-normative and is therefore not mandated by POSIX.
– fpmurphy
Mar 11 '18 at 5:38

|
show 2 more comments

3 Answers
3

active

oldest

votes

+r means ugo+r

+x means ugo+x

but +w means ug+w

because the umask value is 002, when you change umask to 000, by executing

umask 000

in your terminal then

chmod +w file

will set permissions to ugo+w

Note that umask 000 doesn't mean that everybody can read and write all your files, file permissions are also important as suggested by ilkkachu.

edited 5 mins ago

answered Mar 10 '18 at 13:21

P_Yadav

1,5253922

2

umask 000 means everyone that has some kind of access to a user account on your machine (which may include programs running server services ofc) can read and write all the files you make with that mask active and don't change, to be clear
– StarWeaver
Mar 11 '18 at 7:12

1

"+r means ugo=r" -- no, it doesn't, it means to set the r bit for those parties where the umask allows it. This is clearly stated in the manuals of e.g. GNU chmod and FreeBSD chmod, as well as the standard. Same for +x. For +w you're right, for the case of that particular umask.
– ilkkachu
Mar 14 '18 at 10:09

2

Also, setting umask to 0 doesn't mean that everybody can read and write all your files, since many applications create files that are particularly private with mode 0600, meaning that the group and others don't get any access, regardless of the umask.
– ilkkachu
Mar 14 '18 at 10:09

@ilkkachu +r means ugo=r, this was related to the situation described in the question. That was not general.
– P_Yadav
Mar 14 '18 at 11:06

1

@Debian_yadav, that's exactly the point: the umask is an important part of how +r behaves, not a sidenote. Besides, even assuming umask 002, chmod +r doesn't mean chmod ugo=r, it means chmod ugo+r
– ilkkachu
Mar 14 '18 at 13:09

add a comment |

With:

chmod +<perms>

the perms are added to user, group and other but with the umask still applying. It makes sure the file is not granted more permission than a newly created file would.

If you want to add the perms to user, groups and other regardless of the umask, use

chmod a+<perms>

which is short for

chmod ugo+<perms>

answered Mar 10 '18 at 22:28

Stéphane Chazelas

300k54564913

It means that +x and a+x are not equal.
– P_Yadav
Mar 10 '18 at 23:07

1

I like to have links: man7.org/linux/man-pages/man1/chmod.1.html „If none of these are given, the effect is as if (a) were given, but bits that are set in the umask are not affected.“
– tehnicaorg
Mar 13 '18 at 21:20

add a comment |

You need to specify to whom you are giving the permissions to, such as other, by using chmod o+w testfile.txt

answered Mar 10 '18 at 12:54

Jaken551

1658

1

yes, but i think +w gives permission to all( user, group and other).
– Ravi Sevta
Mar 10 '18 at 12:56

To give permissions to all users, use chmod a+w testfile.txt. Use u for user, g for group, o for other, and a for all.
– Jaken551
Mar 10 '18 at 13:00

if chmod a+w filename, chmod +w filename and chmod ugo+w filename are alternative to each other then why not just use +w
– Ravi Sevta
Mar 10 '18 at 13:04

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f429421%2fwhy-does-chmod-w-not-give-write-permission-to-othero%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

+r means ugo+r

+x means ugo+x

but +w means ug+w

because the umask value is 002, when you change umask to 000, by executing

umask 000

in your terminal then

chmod +w file

will set permissions to ugo+w

Note that umask 000 doesn't mean that everybody can read and write all your files, file permissions are also important as suggested by ilkkachu.

edited 5 mins ago

answered Mar 10 '18 at 13:21

P_Yadav

1,5253922

2

umask 000 means everyone that has some kind of access to a user account on your machine (which may include programs running server services ofc) can read and write all the files you make with that mask active and don't change, to be clear
– StarWeaver
Mar 11 '18 at 7:12

1

"+r means ugo=r" -- no, it doesn't, it means to set the r bit for those parties where the umask allows it. This is clearly stated in the manuals of e.g. GNU chmod and FreeBSD chmod, as well as the standard. Same for +x. For +w you're right, for the case of that particular umask.
– ilkkachu
Mar 14 '18 at 10:09

2

Also, setting umask to 0 doesn't mean that everybody can read and write all your files, since many applications create files that are particularly private with mode 0600, meaning that the group and others don't get any access, regardless of the umask.
– ilkkachu
Mar 14 '18 at 10:09

@ilkkachu +r means ugo=r, this was related to the situation described in the question. That was not general.
– P_Yadav
Mar 14 '18 at 11:06

1

@Debian_yadav, that's exactly the point: the umask is an important part of how +r behaves, not a sidenote. Besides, even assuming umask 002, chmod +r doesn't mean chmod ugo=r, it means chmod ugo+r
– ilkkachu
Mar 14 '18 at 13:09

add a comment |

+r means ugo+r

+x means ugo+x

but +w means ug+w

because the umask value is 002, when you change umask to 000, by executing

umask 000

in your terminal then

chmod +w file

will set permissions to ugo+w

Note that umask 000 doesn't mean that everybody can read and write all your files, file permissions are also important as suggested by ilkkachu.

edited 5 mins ago

answered Mar 10 '18 at 13:21

P_Yadav

1,5253922

2

umask 000 means everyone that has some kind of access to a user account on your machine (which may include programs running server services ofc) can read and write all the files you make with that mask active and don't change, to be clear
– StarWeaver
Mar 11 '18 at 7:12

1

"+r means ugo=r" -- no, it doesn't, it means to set the r bit for those parties where the umask allows it. This is clearly stated in the manuals of e.g. GNU chmod and FreeBSD chmod, as well as the standard. Same for +x. For +w you're right, for the case of that particular umask.
– ilkkachu
Mar 14 '18 at 10:09

2

Also, setting umask to 0 doesn't mean that everybody can read and write all your files, since many applications create files that are particularly private with mode 0600, meaning that the group and others don't get any access, regardless of the umask.
– ilkkachu
Mar 14 '18 at 10:09

@ilkkachu +r means ugo=r, this was related to the situation described in the question. That was not general.
– P_Yadav
Mar 14 '18 at 11:06

1

@Debian_yadav, that's exactly the point: the umask is an important part of how +r behaves, not a sidenote. Besides, even assuming umask 002, chmod +r doesn't mean chmod ugo=r, it means chmod ugo+r
– ilkkachu
Mar 14 '18 at 13:09

add a comment |

+r means ugo+r

+x means ugo+x

but +w means ug+w

because the umask value is 002, when you change umask to 000, by executing

umask 000

in your terminal then

chmod +w file

will set permissions to ugo+w

Note that umask 000 doesn't mean that everybody can read and write all your files, file permissions are also important as suggested by ilkkachu.

edited 5 mins ago

answered Mar 10 '18 at 13:21

P_Yadav

1,5253922

+r means ugo+r

+x means ugo+x

but +w means ug+w

because the umask value is 002, when you change umask to 000, by executing

umask 000

in your terminal then

chmod +w file

will set permissions to ugo+w

Note that umask 000 doesn't mean that everybody can read and write all your files, file permissions are also important as suggested by ilkkachu.

edited 5 mins ago

answered Mar 10 '18 at 13:21

P_Yadav

1,5253922

edited 5 mins ago

answered Mar 10 '18 at 13:21

P_Yadav

1,5253922

answered Mar 10 '18 at 13:21

P_Yadav

1,5253922

answered Mar 10 '18 at 13:21

P_Yadav

1,5253922

2

umask 000 means everyone that has some kind of access to a user account on your machine (which may include programs running server services ofc) can read and write all the files you make with that mask active and don't change, to be clear
– StarWeaver
Mar 11 '18 at 7:12

1

"+r means ugo=r" -- no, it doesn't, it means to set the r bit for those parties where the umask allows it. This is clearly stated in the manuals of e.g. GNU chmod and FreeBSD chmod, as well as the standard. Same for +x. For +w you're right, for the case of that particular umask.
– ilkkachu
Mar 14 '18 at 10:09

2

Also, setting umask to 0 doesn't mean that everybody can read and write all your files, since many applications create files that are particularly private with mode 0600, meaning that the group and others don't get any access, regardless of the umask.
– ilkkachu
Mar 14 '18 at 10:09

@ilkkachu +r means ugo=r, this was related to the situation described in the question. That was not general.
– P_Yadav
Mar 14 '18 at 11:06

1

@Debian_yadav, that's exactly the point: the umask is an important part of how +r behaves, not a sidenote. Besides, even assuming umask 002, chmod +r doesn't mean chmod ugo=r, it means chmod ugo+r
– ilkkachu
Mar 14 '18 at 13:09

add a comment |

2

umask 000 means everyone that has some kind of access to a user account on your machine (which may include programs running server services ofc) can read and write all the files you make with that mask active and don't change, to be clear
– StarWeaver
Mar 11 '18 at 7:12

1

"+r means ugo=r" -- no, it doesn't, it means to set the r bit for those parties where the umask allows it. This is clearly stated in the manuals of e.g. GNU chmod and FreeBSD chmod, as well as the standard. Same for +x. For +w you're right, for the case of that particular umask.
– ilkkachu
Mar 14 '18 at 10:09

2

Also, setting umask to 0 doesn't mean that everybody can read and write all your files, since many applications create files that are particularly private with mode 0600, meaning that the group and others don't get any access, regardless of the umask.
– ilkkachu
Mar 14 '18 at 10:09

@ilkkachu +r means ugo=r, this was related to the situation described in the question. That was not general.
– P_Yadav
Mar 14 '18 at 11:06

1

@Debian_yadav, that's exactly the point: the umask is an important part of how +r behaves, not a sidenote. Besides, even assuming umask 002, chmod +r doesn't mean chmod ugo=r, it means chmod ugo+r
– ilkkachu
Mar 14 '18 at 13:09

umask 000 means everyone that has some kind of access to a user account on your machine (which may include programs running server services ofc) can read and write all the files you make with that mask active and don't change, to be clear
– StarWeaver
Mar 11 '18 at 7:12

"+r means ugo=r" -- no, it doesn't, it means to set the r bit for those parties where the umask allows it. This is clearly stated in the manuals of e.g. GNU chmod and FreeBSD chmod, as well as the standard. Same for +x. For +w you're right, for the case of that particular umask.
– ilkkachu
Mar 14 '18 at 10:09

Also, setting umask to 0 doesn't mean that everybody can read and write all your files, since many applications create files that are particularly private with mode 0600, meaning that the group and others don't get any access, regardless of the umask.
– ilkkachu
Mar 14 '18 at 10:09

@ilkkachu +r means ugo=r, this was related to the situation described in the question. That was not general.
– P_Yadav
Mar 14 '18 at 11:06

@Debian_yadav, that's exactly the point: the umask is an important part of how +r behaves, not a sidenote. Besides, even assuming umask 002, chmod +r doesn't mean chmod ugo=r, it means chmod ugo+r
– ilkkachu
Mar 14 '18 at 13:09

add a comment |

With:

chmod +<perms>

the perms are added to user, group and other but with the umask still applying. It makes sure the file is not granted more permission than a newly created file would.

If you want to add the perms to user, groups and other regardless of the umask, use

chmod a+<perms>

which is short for

chmod ugo+<perms>

answered Mar 10 '18 at 22:28

Stéphane Chazelas

300k54564913

It means that +x and a+x are not equal.
– P_Yadav
Mar 10 '18 at 23:07

1

I like to have links: man7.org/linux/man-pages/man1/chmod.1.html „If none of these are given, the effect is as if (a) were given, but bits that are set in the umask are not affected.“
– tehnicaorg
Mar 13 '18 at 21:20

add a comment |

With:

chmod +<perms>

the perms are added to user, group and other but with the umask still applying. It makes sure the file is not granted more permission than a newly created file would.

If you want to add the perms to user, groups and other regardless of the umask, use

chmod a+<perms>

which is short for

chmod ugo+<perms>

answered Mar 10 '18 at 22:28

Stéphane Chazelas

300k54564913

It means that +x and a+x are not equal.
– P_Yadav
Mar 10 '18 at 23:07

1

I like to have links: man7.org/linux/man-pages/man1/chmod.1.html „If none of these are given, the effect is as if (a) were given, but bits that are set in the umask are not affected.“
– tehnicaorg
Mar 13 '18 at 21:20

add a comment |

With:

chmod +<perms>

the perms are added to user, group and other but with the umask still applying. It makes sure the file is not granted more permission than a newly created file would.

If you want to add the perms to user, groups and other regardless of the umask, use

chmod a+<perms>

which is short for

chmod ugo+<perms>

answered Mar 10 '18 at 22:28

Stéphane Chazelas

300k54564913

With:

chmod +<perms>

the perms are added to user, group and other but with the umask still applying. It makes sure the file is not granted more permission than a newly created file would.

If you want to add the perms to user, groups and other regardless of the umask, use

chmod a+<perms>

which is short for

chmod ugo+<perms>

answered Mar 10 '18 at 22:28

Stéphane Chazelas

300k54564913

answered Mar 10 '18 at 22:28

Stéphane Chazelas

300k54564913

answered Mar 10 '18 at 22:28

Stéphane Chazelas

300k54564913

answered Mar 10 '18 at 22:28

Stéphane Chazelas

300k54564913

It means that +x and a+x are not equal.
– P_Yadav
Mar 10 '18 at 23:07

1

I like to have links: man7.org/linux/man-pages/man1/chmod.1.html „If none of these are given, the effect is as if (a) were given, but bits that are set in the umask are not affected.“
– tehnicaorg
Mar 13 '18 at 21:20

add a comment |

It means that +x and a+x are not equal.
– P_Yadav
Mar 10 '18 at 23:07

1

I like to have links: man7.org/linux/man-pages/man1/chmod.1.html „If none of these are given, the effect is as if (a) were given, but bits that are set in the umask are not affected.“
– tehnicaorg
Mar 13 '18 at 21:20

It means that +x and a+x are not equal.
– P_Yadav
Mar 10 '18 at 23:07

I like to have links: man7.org/linux/man-pages/man1/chmod.1.html „If none of these are given, the effect is as if (a) were given, but bits that are set in the umask are not affected.“
– tehnicaorg
Mar 13 '18 at 21:20

add a comment |

You need to specify to whom you are giving the permissions to, such as other, by using chmod o+w testfile.txt

answered Mar 10 '18 at 12:54

Jaken551

1658

1

yes, but i think +w gives permission to all( user, group and other).
– Ravi Sevta
Mar 10 '18 at 12:56

To give permissions to all users, use chmod a+w testfile.txt. Use u for user, g for group, o for other, and a for all.
– Jaken551
Mar 10 '18 at 13:00

if chmod a+w filename, chmod +w filename and chmod ugo+w filename are alternative to each other then why not just use +w
– Ravi Sevta
Mar 10 '18 at 13:04

add a comment |

You need to specify to whom you are giving the permissions to, such as other, by using chmod o+w testfile.txt

answered Mar 10 '18 at 12:54

Jaken551

1658

1

yes, but i think +w gives permission to all( user, group and other).
– Ravi Sevta
Mar 10 '18 at 12:56

To give permissions to all users, use chmod a+w testfile.txt. Use u for user, g for group, o for other, and a for all.
– Jaken551
Mar 10 '18 at 13:00

if chmod a+w filename, chmod +w filename and chmod ugo+w filename are alternative to each other then why not just use +w
– Ravi Sevta
Mar 10 '18 at 13:04

add a comment |

You need to specify to whom you are giving the permissions to, such as other, by using chmod o+w testfile.txt

answered Mar 10 '18 at 12:54

Jaken551

1658

You need to specify to whom you are giving the permissions to, such as other, by using chmod o+w testfile.txt

answered Mar 10 '18 at 12:54

Jaken551

1658

answered Mar 10 '18 at 12:54

Jaken551

1658

answered Mar 10 '18 at 12:54

Jaken551

1658

answered Mar 10 '18 at 12:54

Jaken551

1658

1

yes, but i think +w gives permission to all( user, group and other).
– Ravi Sevta
Mar 10 '18 at 12:56

To give permissions to all users, use chmod a+w testfile.txt. Use u for user, g for group, o for other, and a for all.
– Jaken551
Mar 10 '18 at 13:00

if chmod a+w filename, chmod +w filename and chmod ugo+w filename are alternative to each other then why not just use +w
– Ravi Sevta
Mar 10 '18 at 13:04

add a comment |

1

yes, but i think +w gives permission to all( user, group and other).
– Ravi Sevta
Mar 10 '18 at 12:56

To give permissions to all users, use chmod a+w testfile.txt. Use u for user, g for group, o for other, and a for all.
– Jaken551
Mar 10 '18 at 13:00

if chmod a+w filename, chmod +w filename and chmod ugo+w filename are alternative to each other then why not just use +w
– Ravi Sevta
Mar 10 '18 at 13:04

yes, but i think +w gives permission to all( user, group and other).
– Ravi Sevta
Mar 10 '18 at 12:56

To give permissions to all users, use chmod a+w testfile.txt. Use u for user, g for group, o for other, and a for all.
– Jaken551
Mar 10 '18 at 13:00

if chmod a+w filename, chmod +w filename and chmod ugo+w filename are alternative to each other then why not just use +w
– Ravi Sevta
Mar 10 '18 at 13:04

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Unix & Linux Stack Exchange!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Sstrhsrtj