blocks|key|2373286|text|Ubuntu使用/etc/init.d来存储SysVinit脚本，因为Ubuntu是基于Debian的，这就是Debian所使用的。红帽使用/etc/rc.d/init.d。我忘了Slackware的用途。只是没有标准的地点。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2373287|Ubuntu曾短暂地从SysVinit切换到新贵，但现在转向使用systemd。|entityMap|0|LINK|mutability|MUTABLE|url|http://upstart.ubuntu.com/^0|8|B|1Y|G|0|W|7|M|2|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@$9|W|A|X|1|Y]]|E|$]]]|H|$I|$5|J|K|L|E|$M|N]]]]

Ubuntu uses <code>/etc/init.d</code> to store SysVinit scripts because Ubuntu is based on Debian and that's what Debian uses. Red Hat uses <code>/etc/rc.d/init.d</code>. I forget what Slackware uses. There just isn't a standard location.
Ubuntu briefly switched from SysVinit to <a href="http://upstart.ubuntu.com/" rel="nofollow noreferrer">Upstart</a>, but has now turned to using <code>systemd</code>.

blocks|key|541206|text|/etc/init.d是SVR4的老历史位置。我忘了为什么redhat添加了/etc/rc.d/+level。我认为应该将事情隔离到rc.d上，但为了向后兼容性，需要添加一组符号链接。所以红帽中有/etc/init.d，只是它在其他地方有符号连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|541207|因此，标准位置是/etc/init.d，尽管它可能是一个符号链接，而不是一个真正的目录。|541208|有些非常老的Linux发行版用/etc/rc.local复制了BSD，但是几乎没有人再使用它了。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

/etc/init.d was the old historical location for SVR4. I forgot why redhat added the /etc/rc.d/ level. I think to isolate things onto rc.d, but then needed to add a bunch of symlinks anyway for backwards compatibility. So there is /etc/init.d in redhat, just it symlinks elsewhere.

So the standard location is /etc/init.d, though it may be a symlink not a real directory.

There were some really old Linux distros that copied BSD with /etc/rc.local but pretty much no one uses that anymore.

blocks|key|2373315|text|斯拉克瓦尔仍然使用/etc/rc.d|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2373316|FreeBSD使用/etc/rc.d和/usr/local/etc/rc.d|entityMap|0|LINK|mutability|MUTABLE|url|http://www.slackware.com/|1|http://www.freebsd.org/^0|9|9|0|5|0|0|9|9|J|J|0|7|1^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@$9|T|A|U|1|V]]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]]|H|$I|$5|J|K|L|E|$M|N]]|O|$5|J|K|L|E|$M|P]]]]

<a href="http://www.slackware.com/" rel="nofollow">Slackware</a> still uses <code>/etc/rc.d</code>

<a href="http://www.freebsd.org/" rel="nofollow">FreeBSD</a> uses <code>/etc/rc.d</code> and <code>/usr/local/etc/rc.d</code>

blocks|key|2373380|text|历史上，/etc/rc.d目录树表示一个Init系统，它遵循系统初始化的4.4BSD传统，通常称为rc+init系统。所有现代(免费/开放/网)BSD系统和Slackware+Linux都遵循这一传统。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2373381|/etc/init.d目录树表示遵循AT&T+UNIX、SunOS、Solaris系统初始化传统的System+(SysV)+init系统。这通常被称为SysV+Init系统。Debian本身在Wheezy系列中仍然遵循这一传统，但计划在Jessie系列中使用SystemD。历史上，RedHat和衍生品都使用过SysV+Init，但现在不再使用了。|2373382|此外，随着时间的推移，这两种init方案的特点已被采用的分布。|entityMap^0|4|9|1D|2|0|0|B|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|S|8|@]|D|@]|E|$]]]|J|$]]

Historically, the <code>/etc/rc.d</code> directory tree denotes an Init system which follows the 4.4 BSD tradition of system initialization, which is usually called the <code>rc</code> init system. All the modern (Free/Open/Net)BSD system and Slackware Linux follow this tradition.

The <code>/etc/init.d</code> directory tree denotes the System V (SysV) init system which follows the AT&amp;T UNIX, SunOS, Solaris tradition of system initialization. This is commonly called the SysV Init system. Debian proper still follows this tradition in the Wheezy series, but plans to use SystemD in the Jessie series. Historically, RedHat and derivatives have used SysV Init, but don't anymore.

Also, over time, features of both init schemes have been adopted by distributions.

blocks|key|2373394|text|实际上，至少在CentOS+6.8圣地亚哥，/etc/init.d只是/etc/rc.d的软链接。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|entityMap^0|M|B|Z|9^^$0|@$1|2|3|4|5|6|7|G|8|@$9|H|A|I|B|C]|$9|J|A|K|B|C]]|D|@]|E|$]]]|F|$]]

Actually, at least in CentOS 6.8 Santiago, <code>/etc/init.d</code> is just a softlink to <code>/etc/rc.d</code>.

blocks|key|541234|text|PuppyLinux具有/etc/rc.d和/etc/init.d，两者都不是符号链接。什么是符号链接是/etc/rc.d/init.d，它将一个级别链接到/etc/init.d+(我正在看一个基于Slackware的Puppy-也有基于Ubuntu的和其他版本)。每种方法都有一个README.txt，说明它们的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

PuppyLinux has both /etc/rc.d and /etc/init.d, neither being a symlink. What is a symlink is /etc/rc.d/init.d, which links up a level to /etc/init.d (I'm looking at a Slackware-based Puppy-- there are also Ubuntu-based and other flavors.) There's a README.txt in each, explaining their approach.

blocks|key|541286|text|好的，/etc/init.d是一个可以快速部署init脚本的地方。激活这个脚本的第二步是在它上运行一个chkconfig命令。假设您运行chkconfig+--add+<yourscript>，例如，将在/etc/init.d/<yourscript>和/etc/rc.d/rcX.d/S50<script>之间创建符号链接。X在rcX.d中表示脚本的运行级编号，S50表示脚本类型(其中有两种类型，S&+K，S告诉系统在启动脚本时启动脚本，K告诉系统关闭时优雅地退出脚本。S/K之后的数字代表了这些发生的顺序，如果您有一些脚本依赖于其他脚本首先是活动的)。默认情况下，如果脚本中没有指定运行级别，或者在发出运行级命令时，CentOS6会为运行级别2、3、4、5和运行级别0、1、6的K50创建S50脚本。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|entityMap^0|3|B|1F|9|1W|S|2U|O|3J|R^^$0|@$1|2|3|4|5|6|7|G|8|@$9|H|A|I|B|C]|$9|J|A|K|B|C]|$9|L|A|M|B|C]|$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]]|F|$]]

Ok so, <code>/etc/init.d</code> is a place where you can quickly deploy an init script. The second step towards activating this script is to run a <code>chkconfig</code> command on it. Say you run <code>chkconfig --add &lt;yourscript&gt;</code>, symbolic links will be created between <code>/etc/init.d/&lt;yourscript&gt;</code> and <code>/etc/rc.d/rcX.d/S50&lt;script&gt;</code> for example. X in rcX.d representing the runlevel number of the script, and S50 representing the script type (there are two of these types, S &amp; K, S tells the system to start the script when it boots up, and K tells the system to exit the script gracefully when you shut down. The number after S/K represents the order at which these happen, in case you have some scripts that depend on others being active first). By default, if no runlevel is specified inside the script or when you issue the runlevel command, CentOS6 creates S50 scripts for runlevels 2,3,4,5 and K50 for runlevels 0,1,6 .

blocks|key|2373607|text|这是一个高层次的包罗万象的答案(希望如此)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2373608|从类似Unix系统的维基百科来看，rc这个词代表了“运行命令”这个短语。它用于包含命令启动信息的任何文件。据信，它起源于1965年某个时候，来自麻省理工学院兼容分时系统(CTSS)的runcom设施。从https://www.thegeekdiary.com/understanding-the-rc-scripts-in-linux/运行级中总结出来，这些目录是系统上包含启动和停止特定守护进程的shell脚本的目录，例如/etc/rc1.d/。大多数系统都有运行级别0-6的目录。为了避免脚本复制，rc#.d/目录中的文件实际上是指向/etc/init.d/目录中的脚本文件的符号链接。可以在/etc/init.d/目录中创建执行系统任务的自定义脚本，然后在/etc/rc#.d/目录中创建指向这些脚本的符号链接，以便在必要时启动或停止脚本。然而，对于某些任务，创建完整的System风格的init脚本(包括start和stop选项)是过分的；例如，有些任务需要在系统启动时执行一次，但永远不需要被终止，或者不需要每次系统更改运行时都运行，或者由于其他原因无法完全适应系统V+Init脚本的执行。|blockquote|offset|length|2373609|简单地说，实际上包含所有内容的目录框架是/etc/rc。|unordered-list-item|style|CODE|2373610|正如在CentOS+6中所指出的(在RHEL7.8中也是如此)，文件夹/etc/init.d是指向/etc/rc.d/init.d的链接|2373611|我基于使用RHEL、SLES、IRIX和其他发行版的理解是，"+linux“实际上只指linux内核，而制造商则希望将其称为是谁为您最终使用的linux创建了一个功能性发行版。而制造商可以做任何他们喜欢的事情，因为有各种各样的原因，这就是为什么你可以，也会发现微妙的差异，像这样。rc是一个很大程度上遵循的框架，每个人都会发布一个linux发行版，但要意识到它是一个框架，它实际上取决于他们如何在运行命令中编写所有代码，从而使操作系统启动和关闭。|2373612|提到了SysVinit的旧方式，现在提到了当前的SystemD方式。在linux中，这两项都是旧的方式，与新的现代服务和系统管理方式相比较，后者涵盖了包括启动关闭在内的所有内容。但是组成这个过程的代码文件位于run+commands目录框架下。为了向后兼容，基本上所有运行SystemD的新linux发行版仍然支持所有旧的SysVInit操作方式，只需保留现有的目录rc框架，并将重定向旧的sysvinit命令链接到相应的系统命令(我还没有见过这样的命令)。|2373613|最后，对于给定的linux，您希望至少在/etc/rc#.d、/etc/rc.d/和/etc/init.d下面快速查看一下，看看这些链接是如何连接起来的，并且在目录位置方面具有逻辑意义。不是一个versus另一个。它们是并驾齐驱的，主要原因是只有一个运行命令脚本的副本位于一个地方(在They+7.8中，即实际文件所在的/etc/rc.d/init.d/中)，但是正如您将看到的那样，在rc0+the+rc6下定义的脚本--它对应于基于运行级调用的脚本--都是链接。这一切都是关于管理混乱的文件。|entityMap|0|LINK|mutability|MUTABLE|url|https://www.thegeekdiary.com/understanding-the-rc-scripts-in-linux/^0|0|2T|1V|0|0|K|7|0|Z|B|1D|G|0|3W|2|0|3|8|O|7|2W|C|53|2|0|K|A|V|A|16|B|2P|6|4G|H^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@$E|12|F|13|1|14]]|A|$]]|$1|G|3|H|5|I|7|15|8|@$E|16|F|17|J|K]]|9|@]|A|$]]|$1|L|3|M|5|I|7|18|8|@$E|19|F|1A|J|K]|$E|1B|F|1C|J|K]]|9|@]|A|$]]|$1|N|3|O|5|I|7|1D|8|@$E|1E|F|1F|J|K]]|9|@]|A|$]]|$1|P|3|Q|5|I|7|1G|8|@$E|1H|F|1I|J|K]|$E|1J|F|1K|J|K]|$E|1L|F|1M|J|K]|$E|1N|F|1O|J|K]]|9|@]|A|$]]|$1|R|3|S|5|I|7|1P|8|@$E|1Q|F|1R|J|K]|$E|1S|F|1T|J|K]|$E|1U|F|1V|J|K]|$E|1W|F|1X|J|K]|$E|1Y|F|1Z|J|K]]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

here's a high level all encompassing answer (hopefully)
<blockquote>
from wikipedia
In the context of Unix-like systems, the term rc stands for the phrase &quot;run commands&quot;. It is used for any file that contains startup information for a command. It is believed to have originated sometime in 1965 at a runcom facility from the MIT Compatible Time-Sharing System (CTSS).
</blockquote>
<blockquote>
summarized from <a href="https://www.thegeekdiary.com/understanding-the-rc-scripts-in-linux/" rel="nofollow noreferrer">https://www.thegeekdiary.com/understanding-the-rc-scripts-in-linux/</a>
Runlevels are implemented as directories on the system which contain shell scripts to start and stop specific daemons, e.g. /etc/rc1.d/. Most systems have directories for runlevels 0-6.
To avoid script duplication the files in the rc#.d/ directories are actually symbolic links to script files located in the /etc/init.d/ directory.
Custom scripts to carry out tasks on the system can be created in the /etc/init.d/ directory and then symbolic links to those scripts can be created in the /etc/rc#.d/ directories to start or stop the scripts as necessary. For some tasks, however, creating full-blown System V-style init scripts, complete with start and stop options, is overkill; some tasks, for example, need to be executed once when the system boots up, but never need to be killed, or do not need to be run every time the system changes runlevels, or for other reasons are not totally amenable to execution from a System V Init script.
</blockquote>
<ul>
<li>In simplest terms the directory framework actually containing everything is <code>/etc/rc</code>.</li>
<li>As what pointed out in CentOS 6, which is also true to now in RHEL 7.8, the folder <code>/etc/init.d</code> is a link pointing to <code>/etc/rc.d/init.d</code></li>
<li>My understanding based on using RHEL, SLES, IRIX, and playing with other distributions is that &quot;linux&quot; refers really only to the linux kernel and it is up to the manufacturer are however you want to call it for who makes a functional distribution of linux that you end up using. And that manufacturer can do things however they like for a myriad of reasons which is why you can and will find subtle differences such as this. The <code>rc</code> is a framework which is largely followed by everyone giving out a linux distribution, but realize it is a framework and it really comes down to how they write all that code in the run commands to make the operating system start up and shutdown.</li>
<li>The mention of the old way of <code>SysVinit</code> and now the current way of <code>SystemD</code>. These two items are and old way vs the new [modern] way of service and system management in linux that encompasses everything inclusive of start up to shut down. But the code [files] that make this up resides under the <code>run commands</code> directory framework. And for backwards compatibility basically all new linux distributions running SystemD still support all the old SysVInit way of doing things by simply keeping the existing directory <code>rc</code> framework and linking [redirecting] the old sysvinit commands to the corresponding systemd ones (I have not seen any yet that do not).</li>
<li>In the end for your given linux ditro you are using you want to at leas take a quick look under <code>/etc/rc#.d</code> and <code>/etc/rc.d/</code> and <code>/etc/init.d</code> to see how that all links up and make logical sense in regards to directory locations. It's not one <code>versus</code> the other. They go hand in hand, the primary reason so that only one copy of a run command [script] is located in one place (in RHEL7.8 that is <code>/etc/rc.d/init.d/</code> where the actual file resides) but as you will see the scripts defined under rc0 thru rc6 which corresponds to what gets called based on runlevel are all links. It's all about managing the mess [of files].</li>
</ul>

Is ubuntu's <code>/etc/init.d</code> directory exactly equivalent (functionally) to what I presume to be the more standard <code>/etc/rc.d/</code> (at least on arch)? Is there any particular reason canonical used init.d instead of rc.d for startup scripts?

/etc/rc.d vs /etc/init.d

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

ubuntu的/etc/init.d目录是否与我所认为的更标准的/etc/rc.d/ (至少在arch上)完全等同(功能上的)？对于启动脚本，规范使用init.d而不是rc.d有什么特殊的原因吗？

问/etc/rc.d vs /etc/init.d
EN

回答 8

Unix & Linux用户

Unix & Linux用户

Unix & Linux用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问/etc/rc.d vs /etc/init.dEN

回答 8

Unix & Linux用户

Unix & Linux用户

Unix & Linux用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问/etc/rc.d vs /etc/init.d
EN