mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-29 21:41:00 +08:00
Merge remote-tracking branch 'LCTT/master'
This commit is contained in:
Xingyu Wang
commit
e833dcad36
78
published/20190712 MTTR is dead, long live CIRT.md
Normal file
78
published/20190712 MTTR is dead, long live CIRT.md
Normal file
@ -0,0 +1,78 @@
|
|||||||
|
[#]: collector: (lujun9972)
|
||||||
|
[#]: translator: (wxy)
|
||||||
|
[#]: reviewer: (wxy)
|
||||||
|
[#]: publisher: (wxy)
|
||||||
|
[#]: url: (https://linux.cn/article-11155-1.html)
|
||||||
|
[#]: subject: (MTTR is dead, long live CIRT)
|
||||||
|
[#]: via: (https://opensource.com/article/19/7/measure-operational-performance)
|
||||||
|
[#]: author: (Julie Gunderson https://opensource.com/users/juliegund/users/kearnsjd/users/ophir)
|
||||||
|
|
||||||
|
MTTR 已死，CIRT 长存
|
||||||
|
======
|
||||||
|
|
||||||
|
> 通过关注影响业务的事件，CIRT 是衡量运维绩效的更准确方法。
|
||||||
|
|
||||||
|
![Green graph of measurements][1]
|
||||||
|
|
||||||
|
IT 运维圈子的玩法正在发生变化，这意味着过去的规则越来越不合理。机构需要适当环境中的准确的、可理解的、且可操作的指标，以衡量运维绩效并推动关键业务转型。
|
||||||
|
|
||||||
|
越多的客户使用现代工具，他们管理的事件类型的变化越多，将所有这些不同事件粉碎到一个桶中以计算平均解决时间来表示运维绩效的意义就越少，这就是 IT 一直以来在做的事情。
|
||||||
|
|
||||||
|
### 历史与指标
|
||||||
|
|
||||||
|
历史表明，在分析信号以防止错误和误解时，背景信息是关键。例如，在 20 世纪 80 年代，瑞典建立了一个分析水听器信号的系统，以提醒他们在瑞典当地水域出现的俄罗斯潜艇。瑞典人使用了他们认为代表一类俄罗斯潜艇的声学特征 —— 但实际上是鲱鱼在遇到潜在捕食者时释放的[气泡声][2]。这种对指标的误解加剧了各国之间的紧张关系，几乎导致了战争。
|
||||||
|
|
||||||
|
![Funny fish cartoon][3]
|
||||||
|
|
||||||
|
<ruby>平均解决时间<rt>Mean Time To Resolve</rt></ruby>（MTTR）是运维经理用于获得实现目标洞察力的主要运维绩效指标。这是一项基于<ruby>系统可靠性工程<rt>systems reliability engineering</rt></ruby>的古老措施。MTTR 已被许多行业采用，包括制造、设施维护以及最近的 IT 运维，它代表了解决在特定时间段内创建的事件所需的平均时间。
|
||||||
|
|
||||||
|
MTTR 的计算方法是将所有事件（从事件创建时间到解决时间）所需的时间除以事件总数。
|
||||||
|
|
||||||
|
![MTTR formula][4]
|
||||||
|
|
||||||
|
正如它所说的，MTTR 是 **所有** 事件的平均值。MTTR 将高紧急事件和低紧急事件混为一谈。它还会重复计算每个单独的、未分组的事件，并得出有效的解决时间。它包括了在相同上下文中手动解决和自动解决的事件。它将在创建了几天（或几个月）甚至完全被忽略的事件混合在一起。最后，MTTR 包括每个小的瞬态突发事件（在 120 秒内自动关闭的事件），这些突发事件要么是非问题噪音，要么已由机器快速解决。
|
||||||
|
|
||||||
|
![Variability in incident types][5]
|
||||||
|
|
||||||
|
MTTR 将所有事件（无论何种类型）抛入一个桶中，将它们全部混合在一起，并计算整个集合中的“平均”解决时间。这种过于简单化的方法导致运维执行方式的的噪音、错误和误导性指示。
|
||||||
|
|
||||||
|
### 一种衡量绩效的新方法
|
||||||
|
|
||||||
|
<ruby>关键事件响应时间<rt>Critical Incident Response Time</rt></ruby>（CIRT）是评估运维绩效的一种更准确的新方法。PagerDuty 创立了 CIRT 的概念，但该方法可供所有人免费使用。
|
||||||
|
|
||||||
|
CIRT 通过使用以下技术剔除来自信号的噪声，其重点关注最有可能影响业务的事件：
|
||||||
|
|
||||||
|
1. 真正影响（或可能影响）业务的事件很少是低紧急事件，因此要排除所有低紧急事件。
|
||||||
|
2. 真正影响业务的事件很少（如果有的话）可以无需人为干预而通过监控工具自动解决，因此要排除未由人工解决的事件。
|
||||||
|
3. 在 120 秒内解决的短暂、爆发性和瞬态事件几乎不可能是真正影响业务的事件，因此要排除它们。
|
||||||
|
4. 长时间未被注意、提交或忽略（未确认、未解决）的事件很少会对业务造成影响；排除它们。注意：此阈值可以是特定于客户的统计推导数字（例如，高于均值的两个标准差），以避免使用任意数字。
|
||||||
|
5. 由单独警报产生的个别未分组事件并不代表较大的业务影响事件。因此，模拟具有非常保守的阈值（例如，两分钟）的事件分组以计算响应时间。
|
||||||
|
|
||||||
|
应用这些假设对响应时间有什么影响？简而言之，效果非常非常大！
|
||||||
|
|
||||||
|
通过在关键的、影响业务的事件中关注运维绩效，解决时间分布变窄并极大地向左偏移，因为现在它处理类似类型的事件而不是所有事件。
|
||||||
|
|
||||||
|
由于 MTTR 计算的响应时间长得多、人为地偏差，因此它是运维绩效较差的一个指标。另一方面，CIRT 是一项有意的措施，专注于对业务最重要的事件。
|
||||||
|
|
||||||
|
与 CIRT 一起使用的另一个关键措施是确认和解决事故的百分比。这很重要，因为它验证 CIRT（或 MTTA / MTTR）是否值得利用。例如，如果 MTTR 结果很低，比如 10 分钟，那听起来不错，但如果只有 42％ 的事件得到解决，那么 MTTR 是可疑的。
|
||||||
|
|
||||||
|
总之，CIRT 和确认、解决事件的百分比形成了一组有价值的指标，可以让你更好地了解运营的执行情况。衡量绩效是提高绩效的第一步，因此这些新措施对于实现机构的可持续、可衡量的改进周期至关重要。
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://opensource.com/article/19/7/measure-operational-performance
|
||||||
|
|
||||||
|
作者：[Julie Gunderson][a]
|
||||||
|
选题：[lujun9972][b]
|
||||||
|
译者：[wxy](https://github.com/wxy)
|
||||||
|
校对：[wxy](https://github.com/wxy)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]: https://opensource.com/users/juliegund/users/kearnsjd/users/ophir
|
||||||
|
[b]: https://github.com/lujun9972
|
||||||
|
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/metrics_lead-steps-measure.png?itok=DG7rFZPk (Green graph of measurements)
|
||||||
|
[2]: http://blogfishx.blogspot.com/2014/05/herring-fart-to-communicate.html
|
||||||
|
[3]: https://opensource.com/sites/default/files/uploads/fish.png (Funny fish cartoon)
|
||||||
|
[4]: https://opensource.com/sites/default/files/uploads/mttr.png (MTTR formula)
|
||||||
|
[5]: https://opensource.com/sites/default/files/uploads/incidents.png (Variability in incident types)
|
||||||
@ -1,5 +1,5 @@
|
|||||||
[#]: collector: (lujun9972)
|
[#]: collector: (lujun9972)
|
||||||
[#]: translator: ( )
|
[#]: translator: (anonymone )
|
||||||
[#]: reviewer: ( )
|
[#]: reviewer: ( )
|
||||||
[#]: publisher: ( )
|
[#]: publisher: ( )
|
||||||
[#]: url: ( )
|
[#]: url: ( )
|
||||||
|
|||||||
@ -0,0 +1,71 @@
|
|||||||
|
[#]: collector: (lujun9972)
|
||||||
|
[#]: translator: ( )
|
||||||
|
[#]: reviewer: ( )
|
||||||
|
[#]: publisher: ( )
|
||||||
|
[#]: url: ( )
|
||||||
|
[#]: subject: (NVMe over Fabrics enterprise storage spec enters final review process)
|
||||||
|
[#]: via: (https://www.networkworld.com/article/3411958/nvme-over-fabrics-enterprise-storage-spec-enters-final-review-process.html)
|
||||||
|
[#]: author: (Andy Patrizio https://www.networkworld.com/author/Andy-Patrizio/)
|
||||||
|
|
||||||
|
NVMe over Fabrics enterprise storage spec enters final review process
|
||||||
|
======
|
||||||
|
The NVMe over Fabric (NVMe-oF) architecture is closer to becoming a formal specification. It's expected improve storage network fabric communications and network performance.
|
||||||
|
![Gremlin / Getty Images][1]
|
||||||
|
|
||||||
|
NVM Express Inc., the developer of the [NVMe][2] spec for enterprise SSDs, announced that its NVMe-oF architecture has entered a final 45-day review, an important step toward release of a formal specification for enterprise SSD makers.
|
||||||
|
|
||||||
|
NVMe-oF stands for [NVMe over Fabrics][3], a mechanism to transfer data between a host computer and a target SSD or system over a network, such as Ethernet, Fibre Channel (FC), or InfiniBand. NVM Express first released the 1.0 spec of NVMe-oF in 2016, so this is long overdue.
|
||||||
|
|
||||||
|
**[ Read also: [NVMe over Fabrics creates data-center storage disruption][3] ]**
|
||||||
|
|
||||||
|
NVMe has become an important advance in enterprise storage because it allows for intra-network data sharing. Before, when PCI Express-based SSDs first started being used in servers, they could not easily share data with another physical server. The SSD was basically for the machine it was in, and moving data around was difficult.
|
||||||
|
|
||||||
|
With NVMe over Fabrics, it’s possible for one machine to directly reach out to another for data and have it transmitted over a variety of high-speed fabrics rather than just Ethernet.
|
||||||
|
|
||||||
|
### How NVMe-oF 1.1 improves storage network fabric communication
|
||||||
|
|
||||||
|
The NVMe-oF 1.1 architecture is designed to improve storage network fabric communications in several ways:
|
||||||
|
|
||||||
|
* Adds TCP transport supports NVMe-oF on current data center TCP/IP network infrastructure.
|
||||||
|
* Asynchronous discovery events inform hosts of addition or removal of target ports in a fabric-independent manner.
|
||||||
|
* Fabric I/O Queue Disconnect enables finer-grain I/O resource management.
|
||||||
|
* End-to-end (command to response) flow control improves concurrency.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
### New enterprise features for NVMe 1.4
|
||||||
|
|
||||||
|
The organization also announced the release of the NVMe 1.4 base specification with new “enterprise features” described as a further maturation of the protocol. The specification provides important benefits, such as improved quality of service (QoS), faster performance, improvements for high-availability deployments, and scalability optimizations for data centers.
|
||||||
|
|
||||||
|
Among the new features:
|
||||||
|
|
||||||
|
* Rebuild Assist simplifies data recovery and migration scenarios.
|
||||||
|
* Persistent Event Log enables robust drive history for issue triage and debug at scale.
|
||||||
|
* NVM Sets and IO Determinism allow for better performance, isolation, and QoS.
|
||||||
|
* Multipathing enhancements or Asymmetric Namespace Access (ANA) enable optimal and redundant paths to namespaces for high availability and full multi-controller scalability.
|
||||||
|
* Host Memory Buffer feature reduces latency and SSD design complexity, benefiting client SSDs.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
The upgraded NVMe 1.4 base specification and the pending over-fabric spec will be demonstrated at the Flash Memory Summit August 6-8, 2019 in Santa Clara, California.
|
||||||
|
|
||||||
|
Join the Network World communities on [Facebook][4] and [LinkedIn][5] to comment on topics that are top of mind.
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://www.networkworld.com/article/3411958/nvme-over-fabrics-enterprise-storage-spec-enters-final-review-process.html
|
||||||
|
|
||||||
|
作者：[Andy Patrizio][a]
|
||||||
|
选题：[lujun9972][b]
|
||||||
|
译者：[译者ID](https://github.com/译者ID)
|
||||||
|
校对：[校对者ID](https://github.com/校对者ID)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]: https://www.networkworld.com/author/Andy-Patrizio/
|
||||||
|
[b]: https://github.com/lujun9972
|
||||||
|
[1]: https://images.idgesg.net/images/article/2019/02/big_data_storage_businessman_walks_through_futuristic_data_center_by_gremlin_gettyimages-1098116540_2400x1600-100788347-large.jpg
|
||||||
|
[2]: https://www.networkworld.com/article/3280991/what-is-nvme-and-how-is-it-changing-enterprise-storage.html
|
||||||
|
[3]: https://www.networkworld.com/article/3394296/nvme-over-fabrics-creates-data-center-storage-disruption.html
|
||||||
|
[4]: https://www.facebook.com/NetworkWorld/
|
||||||
|
[5]: https://www.linkedin.com/company/network-world
|
||||||
@ -1,4 +1,3 @@
|
|||||||
IEAST is translating
|
|
||||||
### Unleash Your Creativity – Linux Programs for Drawing and Image Editing
|
### Unleash Your Creativity – Linux Programs for Drawing and Image Editing
|
||||||
|
|
||||||
By: [chabowski][1]
|
By: [chabowski][1]
|
||||||
@ -75,11 +74,11 @@ And indeed, the sky’s the limit on how creative a user wants to be when using
|
|||||||
|
|
||||||
(
|
(
|
||||||
|
|
||||||
_**2** votes, average: **5.00** out of 5_
|
_**2** votes, average: **5.00** out of 5_
|
||||||
|
|
||||||
)
|
)
|
||||||
|
|
||||||
_You need to be a registered member to rate this post._
|
_You need to be a registered member to rate this post._
|
||||||
|
|
||||||
Tags: [drawing][19], [Getting Started with Linux][20], [GIMP][21], [image editing][22], [Images][23], [InkScape][24], [KDE][25], [Krita][26], [Leap 42.3][27], [LibreOffice][28], [Linux Magazine][29], [Okular][30], [openSUSE][31], [PDF][32] Categories: [Desktop][33], [Expert Views][34], [LibreOffice][35], [openSUSE][36]
|
Tags: [drawing][19], [Getting Started with Linux][20], [GIMP][21], [image editing][22], [Images][23], [InkScape][24], [KDE][25], [Krita][26], [Leap 42.3][27], [LibreOffice][28], [Linux Magazine][29], [Okular][30], [openSUSE][31], [PDF][32] Categories: [Desktop][33], [Expert Views][34], [LibreOffice][35], [openSUSE][36]
|
||||||
|
|
||||||
|
|||||||
@ -1,79 +0,0 @@
|
|||||||
[#]: collector: (lujun9972)
|
|
||||||
[#]: translator: ( )
|
|
||||||
[#]: reviewer: ( )
|
|
||||||
[#]: publisher: ( )
|
|
||||||
[#]: url: ( )
|
|
||||||
[#]: subject: (MTTR is dead, long live CIRT)
|
|
||||||
[#]: via: (https://opensource.com/article/19/7/measure-operational-performance)
|
|
||||||
[#]: author: (Julie Gunderson https://opensource.com/users/juliegund/users/kearnsjd/users/ophir)
|
|
||||||
|
|
||||||
MTTR is dead, long live CIRT
|
|
||||||
======
|
|
||||||
By focusing on business-impacting incidents, CIRT is a more accurate way
|
|
||||||
to gauge ops performance.
|
|
||||||
![Green graph of measurements][1]
|
|
||||||
|
|
||||||
The game is changing for the IT ops community, which means the rules of the past make less and less sense. Organizations need accurate, understandable, and actionable metrics in the right context to measure operations performance and drive critical business transformation.
|
|
||||||
|
|
||||||
The more customers use modern tools and the more variation in the types of incidents they manage, the less sense it makes to smash all those different incidents into one bucket to compute an average resolution time that will represent ops performance, which is what IT has been doing for a long time.
|
|
||||||
|
|
||||||
### History and metrics
|
|
||||||
|
|
||||||
History shows that context is key when analyzing signals to prevent errors and misunderstandings. For example, during the 1980s, Sweden set up a system to analyze hydrophone signals to alert them to Russian submarines in local Sweden waters. The Swedes used an acoustic signature they thought represented a class of Russian submarines—but was actually [gas bubbles][2] released by herring when confronted by a potential predator. This misinterpretation of a metric increased tensions between the countries and almost resulted in a war.
|
|
||||||
|
|
||||||
![Funny fish cartoon][3]
|
|
||||||
|
|
||||||
Mean time to resolve (MTTR) is the main ops performance metric operations managers use to gain insight towards achieving their goals. It is an age-old measure based on systems reliability engineering. MTTR has been adopted across many industries, including manufacturing, facility maintenance, and, more recently, IT ops, where it represents the average time it takes to resolve incidents from the time they were created across a given period of time.
|
|
||||||
|
|
||||||
MTTR is calculated by dividing the time it takes to resolve all incidents (from the time of incident creation to time of resolution) by the total number of incidents.
|
|
||||||
|
|
||||||
![MTTR formula][4]
|
|
||||||
|
|
||||||
MTTR is exactly what it says: It's the average across _**all**_ incidents. MTTR smears together both high- and low-urgency incidents. It also repetitively counts each separate, ungrouped incident and results in a biased resolve time. It includes manually resolved and auto-resolved incidents in the same context. It mashes together incidents that are tabled for days (or months) after creation or are even completely ignored. Finally, MTTR includes every little transient burst (incidents that are auto-closed in under 120 seconds), which are either noisy non-issues or quickly resolved by a machine.
|
|
||||||
|
|
||||||
![Variability in incident types][5]
|
|
||||||
|
|
||||||
MTTR takes all incidents, regardless of type, throws them into a single bucket, mashes them all together, and calculates an "average" resolution time across the entire set. This overly simplistic method results in a noisy, erroneous, and misleading indication of how operations is performing.
|
|
||||||
|
|
||||||
### A new way of measuring performance
|
|
||||||
|
|
||||||
Critical incident response time (CIRT) is a new, significantly more accurate method to evaluate operations performance. PagerDuty developed the concept of CIRT, but the methodology is freely available for anyone to use.
|
|
||||||
|
|
||||||
CIRT focuses on the incidents that are most likely to impact business by culling noise from incoming signals using the following techniques:
|
|
||||||
|
|
||||||
1. Real business-impacting (or potentially impacting) incidents are very rarely low urgency, so rule out all low-urgency incidents.
|
|
||||||
2. Real business-impacting incidents are very rarely (if ever) auto-resolved by monitoring tools without the need for human intervention, so rule out incidents that were not resolved by a human.
|
|
||||||
3. Short, bursting, and transient incidents that are resolved within 120 seconds are highly unlikely to be real business-impacting incidents, so rule them out.
|
|
||||||
4. Incidents that go unnoticed, tabled, or ignored (not acknowledged, not resolved) for a very long time are rarely business-impacting; rule them out. Note: This threshold can be a statistically derived number that is customer-specific (e.g., two standard deviations above the mean) to avoid using an arbitrary number.
|
|
||||||
5. Individual, ungrouped incidents generated by separate alerts are not representative of the larger business-impacting incident. Therefore, simulate incident groupings with a very conservative threshold, e.g., two minutes, to calculate response time.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
What effect does applying these assumptions have on response times? In a nutshell, a very, very large effect!
|
|
||||||
|
|
||||||
By focusing on ops performance during critical, business-impacting incidents, the resolve-time distribution narrows and shifts greatly to the left, because now it is dealing with similar types of incidents rather than all events.
|
|
||||||
|
|
||||||
Because MTTR calculates a much longer, artificially skewed response time, it is a poor indicator of operations performance. CIRT, on the other hand, is an intentional measure focused on the incidents that matter most to business.
|
|
||||||
|
|
||||||
An additional critical measure that is wise to use alongside CIRT is the percentage of responders who are acknowledging and resolving incidents. This is important, as it validates whether the CIRT (or MTTA/MTTR for that matter) is worth utilizing. For example, if an MTTR result is low, say 10 minutes, it sounds great, but if only 42% of your responders are resolving their incidents, then that number is suspect.
|
|
||||||
|
|
||||||
In summary, CIRT and the percentage of responders who are acknowledging and resolving incidents form a valuable set of metrics that give you a much better idea of how operations is performing. Gauging performance is the first step to improving performance, so these new measures are key to achieving continuous cycles of measurable improvement for your organization.
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------------
|
|
||||||
|
|
||||||
via: https://opensource.com/article/19/7/measure-operational-performance
|
|
||||||
|
|
||||||
作者：[Julie Gunderson][a]
|
|
||||||
选题：[lujun9972][b]
|
|
||||||
译者：[译者ID](https://github.com/译者ID)
|
|
||||||
校对：[校对者ID](https://github.com/校对者ID)
|
|
||||||
|
|
||||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
|
||||||
|
|
||||||
[a]: https://opensource.com/users/juliegund/users/kearnsjd/users/ophir
|
|
||||||
[b]: https://github.com/lujun9972
|
|
||||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/metrics_lead-steps-measure.png?itok=DG7rFZPk (Green graph of measurements)
|
|
||||||
[2]: http://blogfishx.blogspot.com/2014/05/herring-fart-to-communicate.html
|
|
||||||
[3]: https://opensource.com/sites/default/files/uploads/fish.png (Funny fish cartoon)
|
|
||||||
[4]: https://opensource.com/sites/default/files/uploads/mttr.png (MTTR formula)
|
|
||||||
[5]: https://opensource.com/sites/default/files/uploads/incidents.png (Variability in incident types)
|
|
||||||
@ -1,5 +1,5 @@
|
|||||||
[#]: collector: (lujun9972)
|
[#]: collector: (lujun9972)
|
||||||
[#]: translator: ( )
|
[#]: translator: (MjSeven)
|
||||||
[#]: reviewer: ( )
|
[#]: reviewer: ( )
|
||||||
[#]: publisher: ( )
|
[#]: publisher: ( )
|
||||||
[#]: url: ( )
|
[#]: url: ( )
|
||||||
|
|||||||
@ -1,119 +0,0 @@
|
|||||||
[#]: collector: (lujun9972)
|
|
||||||
[#]: translator: (hello-wn)
|
|
||||||
[#]: reviewer: ( )
|
|
||||||
[#]: publisher: ( )
|
|
||||||
[#]: url: ( )
|
|
||||||
[#]: subject: (How to Create a User Account Without useradd Command in Linux?)
|
|
||||||
[#]: via: (https://www.2daygeek.com/linux-user-account-creation-in-manual-method/)
|
|
||||||
[#]: author: (Magesh Maruthamuthu https://www.2daygeek.com/author/magesh/)
|
|
||||||
|
|
||||||
How to Create a User Account Without useradd Command in Linux?
|
|
||||||
======
|
|
||||||
|
|
||||||
There are three commands are available in Linux to create an user account.
|
|
||||||
|
|
||||||
Did you ever tried to create a user account in Linux using manual method?
|
|
||||||
|
|
||||||
I mean to say without using an above three commands.
|
|
||||||
|
|
||||||
If you don’t know how to do that? we are here to help you on this and will show you in details.
|
|
||||||
|
|
||||||
Have you wondering, how it’s possible? If yes, don’t worry, as we have mentioned many times that anything can be done on Linux. It is one of the example.
|
|
||||||
|
|
||||||
Yes, we can create it. Are you excited to know more it?
|
|
||||||
|
|
||||||
* **[Three Methods To Create A User Account In Linux?][1]**
|
|
||||||
* **[Two Methods To Create Bulk Users In Linux][2]**
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
I don’t want to you to wait any more. Let’s do it right away.
|
|
||||||
|
|
||||||
To do so, first, we need to find out last created UID and GID information. Once you have these information handy then proceed to next step.
|
|
||||||
|
|
||||||
```
|
|
||||||
# cat /etc/passwd | tail -1
|
|
||||||
|
|
||||||
tuser1:x:1153:1154:Test User:/home/tuser1:/bin/bash
|
|
||||||
```
|
|
||||||
|
|
||||||
Based on the above output. Last created user UID is 1153 and GID is 1154. To experiment this, we are going to add `tuser2` in the system.
|
|
||||||
|
|
||||||
Now, add an entry of user details in /etc/passwd. There are seven fields exist and you need to add required details.
|
|
||||||
|
|
||||||
```
|
|
||||||
+-----------------------------------------------------------------------+
|
|
||||||
|username:password:UID:GID:Comments:User Home Directory:User Login Shell|
|
|
||||||
+-----------------------------------------------------------------------+
|
|
||||||
| | | | | | |
|
|
||||||
1 2 3 4 5 6 7
|
|
||||||
|
|
||||||
1- Username: This field indicates the User name. Characters length should be between 1 to 32.
|
|
||||||
2- Password (x): It indicates that encrypted password is stored at /etc/shadow file.
|
|
||||||
3- User ID: It indicates the user ID (UID) each user should be contain unique UID. UID (0-Zero) is reserved for root, UID (1-99) reserved for system users and UID (100-999) reserved for system accounts/groups
|
|
||||||
4- Group ID (GID): It indicates the group ID (GID) each group should be contain unique GID is stored at /etc/group file.
|
|
||||||
5- Comment/User ID Info: It indicates the command field. This field can be used to describe the user information.
|
|
||||||
6- Home directory (/home/$USER): It indicates the user's home directory.
|
|
||||||
7- shell (/bin/bash): It indicates the user's shell.
|
|
||||||
```
|
|
||||||
|
|
||||||
Add the user information in end of the file.
|
|
||||||
|
|
||||||
```
|
|
||||||
# vi /etc/passwd
|
|
||||||
|
|
||||||
tuser2:x:1154:1155:Test User2:/home/tuser2:/bin/bash
|
|
||||||
```
|
|
||||||
|
|
||||||
You have to create a group with same name. So, add a group details in /etc/group file as well.
|
|
||||||
|
|
||||||
```
|
|
||||||
# vi /etc/group
|
|
||||||
|
|
||||||
tuser2:x:1155:
|
|
||||||
```
|
|
||||||
|
|
||||||
Once you done the above two steps, then set a password for user.
|
|
||||||
|
|
||||||
```
|
|
||||||
# passwd tuser2
|
|
||||||
|
|
||||||
Changing password for user tuser2.
|
|
||||||
New password:
|
|
||||||
Retype new password:
|
|
||||||
passwd: all authentication tokens updated successfully.
|
|
||||||
```
|
|
||||||
|
|
||||||
Finally, try to login with newly created user.
|
|
||||||
|
|
||||||
```
|
|
||||||
# ssh [email protected]
|
|
||||||
|
|
||||||
[email protected]'s password:
|
|
||||||
Creating directory '/home/tuser2'.
|
|
||||||
|
|
||||||
$ls -la
|
|
||||||
|
|
||||||
total 16
|
|
||||||
drwx------. 2 tuser2 tuser2 59 Jun 17 09:46 .
|
|
||||||
drwxr-xr-x. 15 root root 4096 Jun 17 09:46 ..
|
|
||||||
-rw-------. 1 tuser2 tuser2 18 Jun 17 09:46 .bash_logout
|
|
||||||
-rw-------. 1 tuser2 tuser2 193 Jun 17 09:46 .bash_profile
|
|
||||||
-rw-------. 1 tuser2 tuser2 231 Jun 17 09:46 .bashrc
|
|
||||||
```
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------------
|
|
||||||
|
|
||||||
via: https://www.2daygeek.com/linux-user-account-creation-in-manual-method/
|
|
||||||
|
|
||||||
作者：[Magesh Maruthamuthu][a]
|
|
||||||
选题：[lujun9972][b]
|
|
||||||
译者：[译者ID](https://github.com/译者ID)
|
|
||||||
校对：[校对者ID](https://github.com/校对者ID)
|
|
||||||
|
|
||||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
|
||||||
|
|
||||||
[a]: https://www.2daygeek.com/author/magesh/
|
|
||||||
[b]: https://github.com/lujun9972
|
|
||||||
[1]: https://www.2daygeek.com/linux-user-account-creation-useradd-adduser-newusers/
|
|
||||||
[2]: https://www.2daygeek.com/linux-bulk-users-creation-useradd-newusers/
|
|
||||||
@ -1,5 +1,5 @@
|
|||||||
[#]: collector: (lujun9972)
|
[#]: collector: (lujun9972)
|
||||||
[#]: translator: ( )
|
[#]: translator: (hello-wn)
|
||||||
[#]: reviewer: ( )
|
[#]: reviewer: ( )
|
||||||
[#]: publisher: ( )
|
[#]: publisher: ( )
|
||||||
[#]: url: ( )
|
[#]: url: ( )
|
||||||
|
|||||||
85
sources/tech/20190726 The Future Of Red Hat At IBM.md
Normal file
85
sources/tech/20190726 The Future Of Red Hat At IBM.md
Normal file
@ -0,0 +1,85 @@
|
|||||||
|
[#]: collector: (lujun9972)
|
||||||
|
[#]: translator: ( )
|
||||||
|
[#]: reviewer: ( )
|
||||||
|
[#]: publisher: ( )
|
||||||
|
[#]: url: ( )
|
||||||
|
[#]: subject: (The Future Of Red Hat At IBM)
|
||||||
|
[#]: via: (https://www.linux.com/blog/future-red-hat-ibm)
|
||||||
|
[#]: author: (Swapnil Bhartiya https://www.linux.com/users/swapnil)
|
||||||
|
|
||||||
|
The Future Of Red Hat At IBM
|
||||||
|
======
|
||||||
|
|
||||||
|
![][1]
|
||||||
|
|
||||||
|
[Creative Commons Attribution-NonCommercial-NoDerivs][2]
|
||||||
|
|
||||||
|
Swapnil Bhartiya
|
||||||
|
|
||||||
|
IBM has a long history of [working with the open source community][3]. Way back in 1999, [IBM announced a $1billion investment in Linux][4]. IBM is also credited for creating one of the [most innovative advertisements about Linux.][5] But IBM’s acquisition of Red Hat raised some serious and genuine questions around IBM’s commitment to Open Source and the future of Red Hat at the big blue.
|
||||||
|
|
||||||
|
Red Hat CTO, Chris Wright, took it upon himself to address some of these concerns and answer people’s questions in [an AMA (Ask Me Anything) on Reddit.][6] Wright has evolved from being a Linux kernel developer to becoming the CTO of the world’s largest open source company. He has his pulse on both the business and community sides of the open source world.
|
||||||
|
|
||||||
|
**Red vs Blue:** Some of the most pressing questions asked during the AMA were around the future of open source and Red Hat at IBM. Red Hat has its unique identity and branding. You will often see people walking with their red hats on at open source events, you may even notice some permanent tattoos.
|
||||||
|
|
||||||
|
One Redditor asked if there were any plans to overhaul Red Hat branding to make it blue or purple, Wright said, “No, Red Hat is Red. We just announced the evolution of our logo in May, no plans for any other changes. We like the new logo and so do the associates who already got tattoos of it!”
|
||||||
|
|
||||||
|
**Kubernetes:** A Redditor asked about the future of Red Hat OpenShift and OKD (the Origin community distribution of Kubernetes). Wright assured that the acquisition doesn’t have any effect on OpenShift and OKD. Wright said that Red Hat is focused on delivering the industry’s most comprehensive enterprise Kubernetes platform – OpenShift - without changes.
|
||||||
|
|
||||||
|
As far as community engagement is concerned, “…upstream first development in Kubernetes and community ecosystem development in OKD are part of our product development process. Neither of those change,” he said. “The IBM acquisition can help accelerate the adoption of OpenShift given the increasing scale and reach in sales and services that IBM has.”
|
||||||
|
|
||||||
|
**Conflict of Culture:** IBM and Red Hat are two companies with different, and often conflicting cultures. While Red Hat employees are allowed and encouraged to contribute to open Source, IBMers do not have the same level of freedom. One ex-IBMer asked, “IBM has traditionally had very strict policies regarding contributing to non-IBM open source projects. I understand that Red Hat's culture is quite different in this regard; do you see IBM loosening up in this regard? Or will only the Red Hat division operate differently?”
|
||||||
|
|
||||||
|
Wright said that Red Hat would continue to operate the way it does with respect to allowing Red Hatters to contribute to open source projects.
|
||||||
|
|
||||||
|
IBM’s CTO of Open Source, Chris Ferris pitched in and said that for the past 5 years or so, the policy for IBMers contributing to open source on their own time was relaxed such that they could do so with their manager’s permission.
|
||||||
|
|
||||||
|
“In fact, we have been on a steady trend over the past 5 years or more to reduce the process barriers to both contributing to, and consuming open source and we continue to review our policies periodically. With the acquisition now complete, IBM has chosen to adopt the same policy towards contributing to open source on one’s own time as Red Hat has had historically. This is one important way that the Red Hat culture has benefited IBM developers.”
|
||||||
|
|
||||||
|
Adam Kaplan, Senior Software Engineer at Red Hat, contributed to the AMA and said that Red Hat employees are free to contribute as they see fit, even if a said contribution goes against Red Hat's business objectives.
|
||||||
|
|
||||||
|
**Future of Fedora & Gnome:** Red Hat is among the leading contributors to many open source projects that are being used by the larger open source community. Some Redditors expressed fear about the future of such projects that won’t be bringing in any revenue for IBM.
|
||||||
|
|
||||||
|
One user asked about Fedora, which is the upstream for Red Hat Enterprise Linux. Wright assured that Fedora and its path stays the same. “It is an important community Linux distribution and Red Hat's involvement will continue to be the same.”
|
||||||
|
|
||||||
|
Red Hat is one of the major contributors to Gnome, one of the biggest desktop environments for Linux and BSD. When asked about the future of Gnome, Wright said that nothing will change. “Certainly not to what we have contributed. More importantly, our future contributions will follow the same pattern,” he said. “We contribute to open source projects that are part of our product portfolio and focus on the areas that are important to our customers, which includes not just features but also long term maintainability (this becomes important in a codebase when you talk about architectural changes).”
|
||||||
|
|
||||||
|
**Sunset at Oracle:** Some Redditors drew a comparison with Oracle’s acquisition of Sun Microsystems. “I guess the biggest concern among the “Linux community” in general is that Red Hat might go down the path Solaris did after Oracle's acquisition. IBM is viewed as an old school company, a bit like Oracle in that sense. We have learned through press that IBM's plan is to use Red Hat to change IBMs perception and not the other way around. Hope it's true. How do you guys plan on addressing such concerns?
|
||||||
|
|
||||||
|
Wright said that Red Hat would continue to run as an independent company and the team would continue to do what it does best: engage with customers, partners, and open source communities to build open-source solutions.
|
||||||
|
|
||||||
|
“Those solutions focus on our hybrid cloud strategy. A key part of the acquisition is for IBM and Red Hat to work closely together to advance our customers’ journeys to an open hybrid cloud. You’ve seen mention of IBM’s plans to use Red Hat platforms as part of their offerings, so this is the other key piece here. We stay independent, we share a vision, and IBM is building from our core platforms,” he said.
|
||||||
|
|
||||||
|
Addressing a similar question that IBM has a history of buying companies and then breaking them up, Wright said, Red Hat will remain committed to the upstream work it does across the board. “It is a fundamental part of how we develop our software products. Things like Network Manager create desktop usability, and can even be the impetus behind more core distro improvements. The IBM acquisition doesn’t change this at all. I see the future of Red Hat as staying focused on our core mission and continuing to evolve with (upstream first!) open source and our customer's needs,” he said.
|
||||||
|
|
||||||
|
**IBM nukes all Open Source at Red Hat**: One Redditor asked what stops IBM from going nuclear and dismantling all of the open source work Red Hat has done?
|
||||||
|
|
||||||
|
Wright said that the reality of software is that open source has become the de facto means by which software is developed. “I often refer to this historic acquisition as an acknowledgment that open source has won. So, a simple way to look at this is the $34b value is about how important open source is to IBM’s strategy...again, open source has won!” he said, “Another way to look at it is the value that we’ve created with Red Hat is synonymous with open source. We wouldn’t exist without open source, it’s core to our strategy. And we (both Red Hat and IBM) are deeply vested in Red Hat’s continued success.”
|
||||||
|
|
||||||
|
**Take Away**
|
||||||
|
|
||||||
|
People should remember that by design, open source is protected from any such risk. If a company gets acquired and the code is at risk of being nuked, the community can fork the project and maintain it. Life goes on. Since everything that Red Hat does is open source, people can always take the code-base and maintain it themselves. open source code has escape velocities, it doesn’t go away with the companies that built it.
|
||||||
|
|
||||||
|
After reading the entire AMA, it’s fair to conclude that Red Hat is safe in the hands of IBM. It’s like a drop of color in a glass of water. The entire glass of water turns red. Red Hat has a very strong community-driven, open source culture. It’s very likely that IBM will be the one benefitting and transforming into an even more open source friendly company.
|
||||||
|
|
||||||
|
Rumor has it that one day Red Hat CEO Jim Whitehurst might become the CEO of IBM. When a Redditor asked the same question, whether Whitehurst will succeed Ginni Rometty as the CEO, Wright said, “I certainly don’t have a crystal ball, but I think Jim is a great CEO!”
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://www.linux.com/blog/future-red-hat-ibm
|
||||||
|
|
||||||
|
作者：[Swapnil Bhartiya][a]
|
||||||
|
选题：[lujun9972][b]
|
||||||
|
译者：[译者ID](https://github.com/译者ID)
|
||||||
|
校对：[校对者ID](https://github.com/校对者ID)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]: https://www.linux.com/users/swapnil
|
||||||
|
[b]: https://github.com/lujun9972
|
||||||
|
[1]: https://www.linux.com/sites/lcom/files/styles/rendered_file/public/dsc_7800.jpg?itok=Ch1vMOHq (Jim Whitehurst)
|
||||||
|
[2]: https://www.linux.com/licenses/category/creative-commons-attribution-noncommercial-noderivs
|
||||||
|
[3]: https://www-03.ibm.com/press/us/en/pressrelease/2262.wss
|
||||||
|
[4]: https://en.wikipedia.org/wiki/Linux_Technology_Center
|
||||||
|
[5]: https://www.youtube.com/watch?v=s7dTjpvakmA
|
||||||
|
[6]: https://www.reddit.com/r/linux/comments/cgu6aj/chris_wright_cto_of_red_hat_is_hosting_an_ama_at/
|
||||||
@ -0,0 +1,116 @@
|
|||||||
|
[#]: collector: "lujun9972"
|
||||||
|
[#]: translator: "hello-wn"
|
||||||
|
[#]: reviewer: " "
|
||||||
|
[#]: publisher: " "
|
||||||
|
[#]: url: " "
|
||||||
|
[#]: subject: "How to Create a User Account Without useradd Command in Linux?"
|
||||||
|
[#]: via: "https://www.2daygeek.com/linux-user-account-creation-in-manual-method/"
|
||||||
|
[#]: author: "Magesh Maruthamuthu https://www.2daygeek.com/author/magesh/"
|
||||||
|
|
||||||
|
# 在 Linux 中不使用 useradd 命令如何创建用户账号
|
||||||
|
|
||||||
|
Linux 中有三个命令可以用来创建用户账号。
|
||||||
|
|
||||||
|
你尝试过在 Linux 中手动创建用户吗？
|
||||||
|
|
||||||
|
我的意思是不使用上面说的三个命令。
|
||||||
|
|
||||||
|
如果你不知道怎么做，本文可以手把手教你，并向你展示细节部分。
|
||||||
|
|
||||||
|
你有没有想过，这怎么可能？别担心，正如我们多次提到的那样，在 Linux 上任何事都可以搞定。这只是其中一例。
|
||||||
|
|
||||||
|
是的，我们可以做到的。想了解更多吗？
|
||||||
|
|
||||||
|
- **[在 Linux 中创建用户的三种方法][1]**
|
||||||
|
- **[在 Linux 中批量创建用户的两种方法][2]**
|
||||||
|
|
||||||
|
话不多说，让我们开始吧。
|
||||||
|
|
||||||
|
首先，我们要找出最后创建的 UID 和 GID 信息。 掌握了这些信息之后，就可以继续下一步。
|
||||||
|
|
||||||
|
```
|
||||||
|
# cat /etc/passwd | tail -1
|
||||||
|
|
||||||
|
tuser1:x:1153:1154:Test User:/home/tuser1:/bin/bash
|
||||||
|
```
|
||||||
|
|
||||||
|
根据以上输出，最后创建的用户 UID 是 1153，GID 是 1154。为了试验，我们将在系统中添加 `tuser2` 用户。
|
||||||
|
|
||||||
|
现在，在`/etc/passwd` 文件中添加一条用户信息。 总共七个字段，你需要添加一些必要信息。
|
||||||
|
|
||||||
|
```
|
||||||
|
+-----------------------------------------------------------------------+
|
||||||
|
|username:password:UID:GID:Comments:User Home Directory:User Login Shell|
|
||||||
|
+-----------------------------------------------------------------------+
|
||||||
|
| | | | | | |
|
||||||
|
1 2 3 4 5 6 7
|
||||||
|
|
||||||
|
1- 用户名: 这个字段表示用户名称。字符长度必须在 1 到 32 之间。
|
||||||
|
2- 密码 (x): 表示存储在 /etc/shadow 文件中的加密密码。
|
||||||
|
3- 用户 ID: 表示用户 ID(UID)，每个用户都有独一无二的 UID。UID(0)保留给root用户，UID(1-99)保留给系统用户，UID (100-999)保留给系统账号/组。
|
||||||
|
4- 组 ID(GID): 表示 ID(GID) ，每个用户组都有独一无二的 GID，存储在 /etc/group 文件中。
|
||||||
|
5- 注释/用户 ID 信息: 表示命令字段，用于描述用户信息。
|
||||||
|
6- 主目录 (/home/$USER): 表示用户的主目录。
|
||||||
|
7- shell (/bin/bash): 表示用户使用的 shell。
|
||||||
|
```
|
||||||
|
|
||||||
|
在文件最后添加用户信息。
|
||||||
|
|
||||||
|
```
|
||||||
|
# vi /etc/passwd
|
||||||
|
|
||||||
|
tuser2:x:1154:1155:Test User2:/home/tuser2:/bin/bash
|
||||||
|
```
|
||||||
|
|
||||||
|
你需要创建相同名字的用户组。同样地，在`/etc/group`文件中添加用户组信息。
|
||||||
|
|
||||||
|
```
|
||||||
|
# vi /etc/group
|
||||||
|
|
||||||
|
tuser2:x:1155:
|
||||||
|
```
|
||||||
|
|
||||||
|
做完以上两步之后，给用户设置一个密码。
|
||||||
|
|
||||||
|
```
|
||||||
|
# passwd tuser2
|
||||||
|
|
||||||
|
Changing password for user tuser2.
|
||||||
|
New password:
|
||||||
|
Retype new password:
|
||||||
|
passwd: all authentication tokens updated successfully.
|
||||||
|
```
|
||||||
|
|
||||||
|
最后，试着登录新创建的用户。
|
||||||
|
|
||||||
|
```
|
||||||
|
# ssh [email protected]
|
||||||
|
|
||||||
|
[email protected]'s password:
|
||||||
|
Creating directory '/home/tuser2'.
|
||||||
|
|
||||||
|
$ls -la
|
||||||
|
|
||||||
|
total 16
|
||||||
|
drwx------. 2 tuser2 tuser2 59 Jun 17 09:46 .
|
||||||
|
drwxr-xr-x. 15 root root 4096 Jun 17 09:46 ..
|
||||||
|
-rw-------. 1 tuser2 tuser2 18 Jun 17 09:46 .bash_logout
|
||||||
|
-rw-------. 1 tuser2 tuser2 193 Jun 17 09:46 .bash_profile
|
||||||
|
-rw-------. 1 tuser2 tuser2 231 Jun 17 09:46 .bashrc
|
||||||
|
```
|
||||||
|
|
||||||
|
------
|
||||||
|
|
||||||
|
via: https://www.2daygeek.com/linux-user-account-creation-in-manual-method/
|
||||||
|
|
||||||
|
作者：[Magesh Maruthamuthu][a]
|
||||||
|
选题：[lujun9972][b]
|
||||||
|
译者：[hello-wn](https://github.com/hello-wn)
|
||||||
|
校对：[校对者ID](https://github.com/校对者ID)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]: https://www.2daygeek.com/author/magesh/
|
||||||
|
[b]: https://github.com/lujun9972
|
||||||
|
[1]: https://www.2daygeek.com/linux-user-account-creation-useradd-adduser-newusers/
|
||||||
|
[2]: https://www.2daygeek.com/linux-bulk-users-creation-useradd-newusers/
|
||||||
Loading…
Reference in New Issue
Block a user