Re: [PATCH v3 6/6] docs/zh_CN: how-to: document case-sensitive APFS setup

Weijie Yuan <[email protected]>
Newsgroups org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
On Thu, Aug 13, 2026 at 02:23:23AM +0800, Chen Miao wrote:
> The APFS volume used by macOS is case-insensitive by default, while the
> kernel tree contains file names that differ only in case. Document the
> diskutil commands needed to identify the APFS container and add a
> case-sensitive volume before cloning the tree.
> 
> Signed-off-by: Chen Miao <[email protected]>

Acked-by: Weijie Yuan <[email protected]>

> ---
>  Documentation/translations/zh_CN/how-to.rst | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/Documentation/translations/zh_CN/how-to.rst b/Documentation/translations/zh_CN/how-to.rst
> index 9ec2384e1..e1d3d2b8b 100644
> --- a/Documentation/translations/zh_CN/how-to.rst
> +++ b/Documentation/translations/zh_CN/how-to.rst
> @@ -102,6 +102,14 @@ Linux 发行版和简单地使用 Linux 命令行,那么可以迅速开始了
>  开头的命令。**请注意**,最新版本 Sphinx 的文档编译速度有极大提升,强烈建议
>  您通过 pip/pypi 安装最新版本 Sphinx。
>  
> +macOS 默认使用不区分文件名大小写的 APFS 卷,而内核源码树中存在仅大小写
> +不同的文件。在执行 ``git clone`` 前,可在现有 APFS 容器中创建一个额外的大小写
> +敏感卷(先用 ``diskutil apfs list`` 找到容器标识符,并将下面的 ``diskX`` 替换为该标识符)::
> +
> +	diskutil apfs addVolume diskX APFSX Linux
> +
> +然后将内核源码克隆到新卷中。
> +
>  如果您处于一个多用户环境中,为了避免对其他人造成影响,建议您配置单用户
>  sphinx 虚拟环境,即只需要执行::

Nit: In the subsequent content of this article, all commands use "make",
not "gmake". So, is it necessary to mention the content of the patch
[5/6] here? (Use gmake from Homebrew instead of make from Apple), like a
cross-reference, to lead the macOS users to get more detailed info.

But I'm fine with currunt wordings. Because if you try to use 'make',
you'll get 

  Makefile:15: *** GNU Make >= 4.0 is required. Your Make version is 3.81.  Stop.

then, you should realize that Homebrew had told you that you should run
'gmake' instead of 'make'.

Thanks.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.