> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/man/man4/smbfs.4.md).

# smbfs.4

`smbfs` — 服务器消息块（SMB1/CIFS）文件系统

## 名称

`smbfs`

## 概要

`要将此驱动编译进内核，请将以下行添加到你的内核配置文件中：`

> option NETSMB

`或者，要在引导时以模块形式加载此驱动，请将以下行添加到 loader.conf(5) 中：`

```sh
smbfs_load="YES"
```

## 描述

SMB 驱动是 CIFS（Common Internet Filesystem）网络协议的实现。

`smbfs` 文件系统驱动仅支持已过时的 SMBv1 协议。`smbfs` 存在已知缺陷，可能有安全漏洞。`smbfs` 及其用户空间对应物 smbutil(1) 和 mount\_smbfs(8) 可能会在未来版本的 FreeBSD 中移除。建议用户改用 `filesystems/smbnetfs` port。

## 参见

smbutil(1), mount\_smbfs(8)

## 标准

> "Common Internet File System (CIFS) Protocol", December 2018.

> I. Heizer, P. Leach, D. Perry, "Common Internet File System Protocol (CIFS/1.0)", June 13, 1996.

## 历史

`smbfs` 设备驱动最早出现于 FreeBSD 4.4。

## 作者

`smbfs` 设备驱动由 Boris Popov <bp@FreeBSD.org> 编写。手册页由 Gordon Bergling <gbe@FreeBSD.org> 贡献。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://book.bsdcn.org/man/man4/smbfs.4.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
