Skip to contentSkip to conversation

manpage: updatemount.cifs manpage with info aboutincomplete options

PATCH Pavel Shilovskiy 1 participant 1 message Jan 16, 2018 2 messages not in the archive

Subsystems (2)
lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

Hi Zhang,

I am expecting to release the next stable version in 3-4 weeks.

Best regards,
Pavel Shilovskiy

-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, January 15, 2018 12:50 AM
To: [email protected]
Cc: [email protected]; [email protected]; Pavel Shilovskiy <[email protected]>
Subject: 答复: Re: 答复: Re: [PATCH] manpage: updatemount.cifs manpage with info aboutincomplete options

Thanks.
By the way, when will the next stable version be released?

------------------原始邮件------------------
发件人: <[email protected]>;
收件人:张贤伟10129966; <[email protected]>;
抄送人: <[email protected]>; <[email protected]>;
日 期 :2018年01月02日 23:56
主 题 :Re: 答复: Re: [PATCH] manpage: updatemount.cifs manpage with info aboutincomplete options Yes, we'll be merging it -- thank you!

I'm in the process of handing off cifs-utils maintainership to Pavel, and he's working on getting his account set up correctly. Once that's done, we'll merge this patch soon afterward.

-- Jeff

Quoted 102 lines · On Tue, 2018-01-02 at 18:17 +0800, [email protected] wrote:

So, could merge the patch?

------------------原始邮件------------------
发件人: <[email protected]>;
收件人: <[email protected]>;
抄送人:张贤伟10129966; <[email protected]>;
日 期 :2017年12月08日 22:30
主 题 :Re: [PATCH] manpage: update mount.cifs manpage with info aboutincomplete options

Quoted 1 line

Anyone have thoughts on this?

My reaction is that it is more work to remove the aliases, and not likely to improve usability in this case to remove the alias - so better to leave the aliases in.

Quoted 68 lines · Jeff Layton
Quoted 53 lines · On Fri, 2017-12-08 at 15:11 +0800, [email protected] wrote:

This commit a1f3acd40b265f134a97a739a6898b3958d206b9 modified mount parameters, but not updated mount.cifs manpage. Fix it.

---
mount.cifs.rst | 10 +++++-----

1 file changed, 5 insertions(+), 5 deletions(-)
mount.cifs.rst index renamed from mount.cifs.rst +0 -0

023ff34..a4445b8 100644

mount.cifs.rst +1 -1
@@ -48,7 +48,7 @@ OPTIONS
 *******
 
 
-username=arg
+username=arg|user=arg

specifies the username to connect as. If this is not given, then the environment variable USER is used.

mount.cifs.rst +0 -0
@@ -64,7 +64,7 @@ username=arg

non-superuser mount. It is therefore recommended to use the full ``username=`` option name.

mount.cifs.rst +1 -1
-password=arg
+password=arg|pass=arg

specifies the CIFS password. If this option is not given then the environment variable PASSWD is used. If the password is not specified directly or indirectly via an argument to mount, mount.cifs will @@ -76,7 +76,7 @@ password=arg variable or via a credentials file (see below) or entered at the password prompt will be read correctly.

mount.cifs.rst +1 -1
-credentials=filename
+credentials=filename|cred=filename

specifies a file that contains a username and/or password and optionally the name of the workgroup. The format of the file is::

mount.cifs.rst +0 -0
@@ -159,12 +159,12 @@ dir_mode=arg If the server does not support 

the CIFS Unix extensions this overrides the default mode for directories.

mount.cifs.rst +1 -1
-ip=arg
+ip=arg|addr=arg

sets the destination IP address. This option is set automatically if the server name portion of the requested UNC name can be resolved so rarely needs to be specified by the user.

mount.cifs.rst +1 -1
-domain=arg
+domain=arg|dom=arg|workgroup=arg

sets the domain (workgroup) of the user.

Quoted 1 line

guest

Honestly, I'd really prefer to move this in the other direction and have the kernel/userland programs stop accepting some of these aliases. They don't add anything to usability and they are a long-term maintenance burden.

We'd probably need a 2-3 releases where we accept the aliases and throw a warning when someone tries to use them. Then we can just rip out support for them.

That said, if the consensus is to keep the aliases in, then I'll just plan to merge this patch.

Quoted 12 lines

Anyone have thoughts on this?
--
Jeff Layton <[email protected]>
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvger
.kernel.org%2Fmajordomo-info.html&data=02%7C01%7Cpshilov%40microsoft .com%7C53711e2a8d6541b8465408d55bf50df5%7C72f988bf86f141af91ab2d7cd0 11db47%7C1%7C0%7C636516030427477830&sdata=bn5w0N9GfggOhQxhKA9SI2W6X7 9DWnWyEavefeJCp7A%3D&reserved=0

Quoted 4 lines

--
Thanks,

Steve

--
Jeff Layton <[email protected]>