diff --git a/sources/news/20190802 Linux Smartphone Librem 5 is Available for Preorder.md b/sources/news/20190802 Linux Smartphone Librem 5 is Available for Preorder.md
new file mode 100644
index 0000000000..de4e87cf2f
--- /dev/null
+++ b/sources/news/20190802 Linux Smartphone Librem 5 is Available for Preorder.md	
@@ -0,0 +1,91 @@
+[#]: collector: (lujun9972)
+[#]: translator: ( )
+[#]: reviewer: ( )
+[#]: publisher: ( )
+[#]: url: ( )
+[#]: subject: (Linux Smartphone Librem 5 is Available for Preorder)
+[#]: via: (https://itsfoss.com/librem-5-available/)
+[#]: author: (Ankush Das https://itsfoss.com/author/ankush/)
+
+Linux Smartphone Librem 5 is Available for Preorder
+======
+
+Purism recently [announced][1] the final specs for its [Librem 5 smartphone][2]. This is not based on Android or iOS – but built on [PureOS][3], which is an [open-source alternative to Android][4].
+
+Along with the announcement, the Librem 5 is also available for [pre-orders for $649][5] (as an early bird offer till 31st July) and it will go up by $50 following the date. It will start shipping from Q3 of 2019.
+
+![][6]
+
+Here’s what Purism mentioned about Librem 5 in its blog post:
+
+_**We believe phones should not track you nor exploit your digital life.**_
+
+_The Librem 5 represents the opportunity for you to take back control and protect your private information, your digital life through free and open source software, open governance, and transparency. The Librem 5 is_ **_a phone built on_ [_PureOS_][3]**_, a fully free, ethical and open-source operating system that is_ _**not based on Android or iOS**_ _(learn more about [why this is important][7])._
+
+_We have successfully crossed our crowdfunding goals and will be delivering on our promise. The Librem 5’s hardware and software development is advancing [at a steady pace][8], and is scheduled for an initial release in Q3 2019. You can preorder the phone at $649 until shipping begins and regular pricing comes into effect. Kits with an external monitor, keyboard and mouse, are also available for preorder._
+
+### Librem 5 Specifications
+
+From what it looks like, Librem 5 definitely aims to provide better privacy and security. In addition to this, it tries to avoid using anything from Google or Apple.
+
+While the idea is good enough – how does it hold up as a commercial smartphone under $700?
+
+![Librem 5 Smartphone][9]
+
+Let us take a look at the tech specs:
+
+![Librem 5][10]
+
+On paper the tech specs seems to be good enough. Not too great – not too bad. But, what about the performance? The user experience?
+
+Well, we can’t be too sure about it – unless we use it. So, if you are pre-ordering it – take that into consideration.
+
+[][11]
+
+Suggested read  Linux Games Get A Performance Boost for AMD GPUs Thanks to Valve's New Compiler
+
+### Lifetime software updates for Librem 5
+
+Of course, the specs aren’t very pretty when compared to the smartphones available at this price range.
+
+However, with the promise of lifetime software updates – it does look like a decent offering for open source enthusiasts.
+
+### Other Key Features
+
+Purism also highlights the fact that Librem 5 will be the first-ever [Matrix][12]-powered smartphone. This means that it will support end-to-end decentralized encrypted communications for messaging and calling.
+
+In addition to all these, the presence of headphone jack and a user-replaceable battery makes it a pretty solid deal.
+
+### Wrapping Up
+
+Even though it is tough to compete with the likes of Android/iOS smartphones, having an alternative is always good. Librem 5 may not prove to be an ideal smartphone for every user – but if you are an open-source enthusiast and looking for a simple smartphone that respects privacy and security without utilizing Google/Apple services, this is for you.
+
+Also the fact that it will receive lifetime software updates – makes it an interesting smartphone.
+
+What do you think about Librem 5? Are you thinking to pre-order it? Let us know your thoughts in the comments below.
+
+--------------------------------------------------------------------------------
+
+via: https://itsfoss.com/librem-5-available/
+
+作者：[Ankush Das][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://itsfoss.com/author/ankush/
+[b]: https://github.com/lujun9972
+[1]: https://puri.sm/posts/librem-5-smartphone-final-specs-announced/
+[2]: https://itsfoss.com/librem-linux-phone/
+[3]: https://pureos.net/
+[4]: https://itsfoss.com/open-source-alternatives-android/
+[5]: https://shop.puri.sm/shop/librem-5/
+[6]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2019/08/librem-5-linux-smartphone.jpg?resize=800%2C450&ssl=1
+[7]: https://puri.sm/products/librem-5/pureos-mobile/
+[8]: https://puri.sm/posts/tag/phones
+[9]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2019/07/librem-5-smartphone.jpg?ssl=1
+[10]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2019/07/librem-5-specs.png?ssl=1
+[11]: https://itsfoss.com/linux-games-performance-boost-amd-gpu/
+[12]: http://matrix.org
diff --git a/sources/talk/20190731 Cisco simplifies Kubernetes container deployment with Microsoft Azure collaboration.md b/sources/talk/20190731 Cisco simplifies Kubernetes container deployment with Microsoft Azure collaboration.md
new file mode 100644
index 0000000000..423cd7180a
--- /dev/null
+++ b/sources/talk/20190731 Cisco simplifies Kubernetes container deployment with Microsoft Azure collaboration.md	
@@ -0,0 +1,67 @@
+[#]: collector: (lujun9972)
+[#]: translator: ( )
+[#]: reviewer: ( )
+[#]: publisher: ( )
+[#]: url: ( )
+[#]: subject: (Cisco simplifies Kubernetes container deployment with Microsoft Azure collaboration)
+[#]: via: (https://www.networkworld.com/article/3429116/cisco-simplifies-kubernetes-container-deployment-with-microsoft-azure-collaboration.html)
+[#]: author: (Michael Cooney https://www.networkworld.com/author/Michael-Cooney/)
+
+Cisco simplifies Kubernetes container deployment with Microsoft Azure collaboration
+======
+Microsoft's Azure Kubernetes Service (AKS) has been added to the Kubernetes managed services that natively integrate with the Cisco Container Platform.
+![Viti / Getty Images][1]
+
+Cisco seeks to enhance container deployment with a service to let enterprise customers run containerized applications across both Cisco-based on-premises environments and in the Microsoft Azure cloud.
+
+Customers can now further simplify deploying and managing Kubernetes clusters on-premises and in Azure Kubernetes Service (AKS) with one tool, using common identify and control policies, reducing manual tasks and ultimately time-to-market for their application environments, wrote Cisco’s Kip Compton, senior vice president of the company’s Cloud Platform and Solutions group in a [blog][2] about the work. 
+
+[RELATED: How to make hybrid cloud work][3]
+
+Specifically, AKS has been added to Kubernetes managed services that natively integrate with the [Cisco Container Platform][4]. Cisco introduced its Kubernetes-based Container Platform in January 2018 and said it allows for self-service deployment and management of container clusters. 
+
+Cisco has added multivendor support to the platform, including support of SAP’s Data Hub to integrate large data sets that may be in public clouds, such as Amazon Web Services, Hadoop, Microsoft or Google, and integrate them with private cloud or enterprise apps such as SAP S/4 HANA.
+
+Kubernetes, originally designed by Google, is an open-source-based system for developing and orchestrating containerized applications. Containers can be deployed across multiple server hosts and Kubernetes orchestration lets customers build application services that span multiple containers, schedule those containers across a cluster, scale those containers and manage the container health. 
+
+Cisco has been working to further integrate with Azure services for quite a while  now.  For example, the [Cisco Integrated System for Microsoft Azure Stack][5] lets organizations access development tools, data repositories, and related Azure services to reinvent applications and gain new information from secured data. Azure Stack provides the same APIs and user interface as the Azure public cloud.
+
+In future phases, the Cisco Container Platform will integrate more features to support Microsoft Windows container applications with the potential to leverage virtual-kubelet or Windows node pools in Azure, Compton stated. “In addition, we will support Azure Active Directory common identity integration for both on-prem and AKS clusters so customer/applications experience a single consistent environment across hybrid cloud.”
+
+In addition, Cisco has a substantial portfolio of offerings running in the Azure cloud and available in the Azure Marketplace.  For example,  the company offers its Cloud Services Router, CSV1000v, as well as Meraki vMX, Stealthwatch Cloud, the Adaptive Security Virtual Appliance and its Next Generation Firewall. 
+
+The Azure work broadens Cisco’s drive into cloud.  For example Cisco and [Amazon Web Services (AWS) offer][6] enterprise customers an integrated platform that promises to help them more simply build, secure and connect Kubernetes clusters across private data centers and the AWS cloud. 
+
+The package, Cisco Hybrid Solution for Kubernetes on AWS, combines Cisco, AWS and open-source technologies to simplify complexity and helps eliminate challenges for customers who use Kubernetes to enable deploying applications on premises and across the AWS cloud in a secure, consistent manner.  The hybrid service integrates Cisco Container Platform (CCP) and Amazon Elastic Container Service for Kubernetes (EKS), so customers can provision clusters on premises and on EKS in the cloud.
+
+Cisco [also released a cloud-service program][7] on its flagship software-defined networking (SDN) software that will let customers manage and secure applications running in the data center or in Amazon Web Service cloud environments. The service, Cisco Cloud application centric infrastructure (ACI) for AWS lets users configure inter-site connectivity, define policies and monitor the health of network infrastructure across hybrid environments, Cisco said.
+
+Meanwhile, Cisco and Google have done extensive work on their own joint cloud-development activities to help customers more easily build secure multicloud and hybrid applications everywhere from on-premises data centers to public clouds. 
+
+Cisco and Google have been working closely together since October 2017, when the companies said they were working on an open hybrid cloud platform that bridges on-premises and cloud environments. That package, [Cisco Hybrid Cloud Platform for Google Cloud][8], became generally available in September 2018. It lets customer develop enterprise-grade capabilities from Google Cloud-managed Kubernetes containers that include Cisco networking and security technology as well as service mesh monitoring from Istio.
+
+Join the Network World communities on [Facebook][9] and [LinkedIn][10] to comment on topics that are top of mind.
+
+--------------------------------------------------------------------------------
+
+via: https://www.networkworld.com/article/3429116/cisco-simplifies-kubernetes-container-deployment-with-microsoft-azure-collaboration.html
+
+作者：[Michael Cooney][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/Michael-Cooney/
+[b]: https://github.com/lujun9972
+[1]: https://images.idgesg.net/images/article/2019/07/africa_guinea_conakry_harbor_harbour_shipping_containers_cranes_by_viti_gettyimages-1154922310_2400x1600-100802866-large.jpg
+[2]: https://www.networkworld.com/cms/article/%20https:/blogs.cisco.com/news/cisco-microsoft%20%E2%80%8E
+[3]: https://www.networkworld.com/article/3119362/hybrid-cloud/how-to-make-hybrid-cloud-work.html#tk.nww-fsb
+[4]: https://www.networkworld.com/article/3252810/cisco-unveils-container-management-on-hyperflex.html
+[5]: https://blogs.cisco.com/datacenter/cisco-integrated-system-for-microsoft-azure-stack-it-is-here-and-shipping
+[6]: https://www.networkworld.com/article/3319782/cisco-aws-marriage-simplifies-hybrid-cloud-app-development.html
+[7]: https://www.networkworld.com/article/3388679/cisco-taps-into-aws-for-data-center-cloud-applications.html
+[8]: https://cloud.google.com/cisco/
+[9]: https://www.facebook.com/NetworkWorld/
+[10]: https://www.linkedin.com/company/network-world
diff --git a/sources/talk/20190731 VMware-s Bitfusion acquisition could be a game-changer for GPU computing.md b/sources/talk/20190731 VMware-s Bitfusion acquisition could be a game-changer for GPU computing.md
new file mode 100644
index 0000000000..4946824820
--- /dev/null
+++ b/sources/talk/20190731 VMware-s Bitfusion acquisition could be a game-changer for GPU computing.md	
@@ -0,0 +1,58 @@
+[#]: collector: (lujun9972)
+[#]: translator: ( )
+[#]: reviewer: ( )
+[#]: publisher: ( )
+[#]: url: ( )
+[#]: subject: (VMware’s Bitfusion acquisition could be a game-changer for GPU computing)
+[#]: via: (https://www.networkworld.com/article/3429036/vmwares-bitfusion-acquisition-could-be-a-game-changer-for-gpu-computing.html)
+[#]: author: (Andy Patrizio https://www.networkworld.com/author/Andy-Patrizio/)
+
+VMware’s Bitfusion acquisition could be a game-changer for GPU computing
+======
+VMware will integrate Bitfusion technology into vSphere, bolstering VMware’s strategy of supporting AI- and ML-based workloads by virtualizing hardware accelerators.
+![Vladimir Timofeev / Getty Images][1]
+
+In a low-key move that went under the radar of a lot of us, last week VMware snapped up a startup called Bitfusion, which makes virtualization software for accelerated computing. It improves performance of virtual machines by offloading processing to accelerator chips, such as GPUs, FPGAs, or other custom ASICs.
+
+Bitfusion provides sharing of GPU resources among isolated GPU compute workloads, allowing workloads to be shared across the customer’s network. This way workloads are not tied to one physical server but shared as a pool of resources, and if multiple GPUs are brought to bear, performance naturally increases.
+
+“In many ways, Bitfusion offers for hardware acceleration what VMware offered to the compute landscape several years ago. Bitfusion also aligns well with VMware’s ‘Any Cloud, Any App, Any Device’ vision with its ability to work across AI frameworks, clouds, networks, and formats such as virtual machines and containers,” said Krish Prasad, senior vice president and general manager of the Cloud Platform Business Unit at VMware, in a [blog post][2] announcing the deal.
+
+**[ Also read: [After virtualization and cloud, what's left on premises?][3] ]**
+
+When the acquisition closes, VMware will integrate Bitfusion technology into vSphere. Prasad said the inclusion of Bitfusion will bolster VMware’s strategy of supporting artificial intelligence- and machine learning-based workloads by virtualizing hardware accelerators.
+
+“Multi-vendor hardware accelerators and the ecosystem around them are key components for delivering modern applications. These accelerators can be used regardless of location in the environment—on-premises and/or in the cloud,” he wrote. The platform can be extended to support other accelerator chips, such as FGPAs and ASICs, he wrote.
+
+Prasad noted that hardware accelerators today are deployed “with bare-metal practices, which force poor utilization, poor efficiencies, and limit organizations from sharing, abstracting, and automating the infrastructure. This provides a perfect opportunity to virtualize them—providing increased sharing of resources and lowering costs.”
+
+He added: “The platform can share GPUs in a virtualized infrastructure as a pool of network-accessible resources rather than isolated resources per server.”
+
+This is a real game-changer, much the way VMware added storage virtualization and software-defined networks (SDN) to expand the use of vSphere. It gives them a major competitive advantage over Microsoft Hyper-V and Linux’s KVM now as well.
+
+By virtualizing and pooling GPUs, it lets users bring multiple GPUs to bear rather than locking one physical processor to a server and application. The same applies to FPGAs and the numerous AI processor chips either on or coming to market.
+
+### VMware also buys Uhana
+
+That wasn’t VMware’s only purchase. The company also acquired Uhana, which provides an AI engine specifically for telcos and other carriers that discovers anomalies in the network or application, prioritizes them based on their potential impact, and automatically recommends optimization strategies. That means improved network operations and operational efficiently.
+
+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/3429036/vmwares-bitfusion-acquisition-could-be-a-game-changer-for-gpu-computing.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/2018/08/clouded_view_of_data_center_server_virtualization_by_vladimir_timofeev_gettyimages-600404124_1200x800-100768156-large.jpg
+[2]: https://blogs.vmware.com/vsphere/2019/07/vmware-to-acquire-bitfusion.html
+[3]: https://https//www.networkworld.com/article/3232626/virtualization/extreme-virtualization-impact-on-enterprises.html
+[4]: https://www.facebook.com/NetworkWorld/
+[5]: https://www.linkedin.com/company/network-world
diff --git a/sources/talk/20190801 Cisco assesses the top enterprise SD-WAN technology drivers.md b/sources/talk/20190801 Cisco assesses the top enterprise SD-WAN technology drivers.md
new file mode 100644
index 0000000000..b6f845b4a7
--- /dev/null
+++ b/sources/talk/20190801 Cisco assesses the top enterprise SD-WAN technology drivers.md	
@@ -0,0 +1,96 @@
+[#]: collector: (lujun9972)
+[#]: translator: ( )
+[#]: reviewer: ( )
+[#]: publisher: ( )
+[#]: url: ( )
+[#]: subject: (Cisco assesses the top enterprise SD-WAN technology drivers)
+[#]: via: (https://www.networkworld.com/article/3429186/cisco-assesses-the-top-enterprise-sd-wan-technology-drivers.html)
+[#]: author: (Michael Cooney https://www.networkworld.com/author/Michael-Cooney/)
+
+Cisco assesses the top enterprise SD-WAN technology drivers
+======
+Cisco SD-WAN customer National Instruments touts benefits of the technology: Speed, efficiency, security, cost savings
+![Getty Images][1]
+
+Cisco this week celebrated the [second anniversary][2] of its purchase of SD-WAN vendor Viptela and reiterated its expectation that 2019 will see the [technology change][3] enterprise networks in major ways.
+
+In a blog outlining trends in the SD-WAN world, Anand Oswal, Cisco senior vice president, engineering, in the company’s Enterprise Networking Business described how SD-WAN technology has changed the network for one of its customers,  test and measurement systems vendor National Instruments. 
+
+**More about SD-WAN**
+
+  * [How to buy SD-WAN technology: Key questions to consider when selecting a supplier][4]
+  * [How to pick an off-site data-backup method][5]
+  * [SD-Branch: What it is and why you’ll need it][6]
+  * [What are the options for security SD-WAN?][7]
+
+
+
+“The existing WAN greatly constrained video conferencing, slowed large software transfers, and couldn’t provide acceptable application performance,” [Oswald wrote][8].  Implementing SD-WAN turned those issues around by:
+
+  * Reducing MPLS spending by 25% while increasing bandwidth by 3,075%
+  * Categorizing traffic by function and type, sending backup traffic over the Internet under an SLA, eliminating bandwidth bottleneck on MPLS circuits
+  * Reducing the time for software updates to replicate across the network from 8 hours to 10 minutes
+  * Adding new internet-based services used to take months, but with the agility of SD-WAN, new services can be deployed in the cloud immediately
+  * Eliminating the need for call -dmission controls and limiting video quality for conferencing
+
+
+
+National Instruments' bandwidth requirements were growing10 to 25 percent per year, overwhelming the budget, Luis Castillo, global network team manager told Cisco in a [case study][9] of the SD-WAN project. “Part of the problem was that these sites can have very different requirements. R&D shops need lots of bandwidth. One site may have a special customer that requires unique segmentation and security. Our contact centers need to support mission-critical voice services. All of that is dependent on the WAN, which means escalating complexity and constantly growing costs.”
+
+After the shift to SD-WAN, the company no longer has 80 people with diverse IT workloads copeting for a sinlge 10-Mbit circuit, Castillo says.
+
+It’s not just cost savings by supplementing or replacing MPLS with direct internet connections that is motivating the transition to software-defined WAN architecture, Oswald said.   “It’s also about gaining flexibility and stability with intelligent, continuously monitored connections to multicloud resources and SaaS applications that are fueling the current SD-WAN transition.”
+
+In its most recent [SD-WAN Infrastructure Forecast][10], IDC researchers talked about a number of other factors driving SD-WAN evolution.
+
+"First, traditional enterprise WANs are increasingly not meeting the needs of today's modern digital businesses, especially as it relates to supporting SaaS apps and multi- and hybrid-cloud usage. Second, enterprises are interested in easier management of multiple connection types across their WAN to improve application performance and end-user experience," said [Rohit Mehra][11], vice president, [Network Infrastructure][12] at IDC. "Combined with the rapid embrace of SD-WAN by leading communications service providers globally, these trends continue to drive deployments of SD-WAN, providing enterprises with dynamic management of hybrid WAN connections and the ability to guarantee high levels of quality of service on a per-application basis."
+
+IDC also said that the SD-WAN infrastructure market continues to be highly competitive with sales increasing 64.9% in 2018 to $1.37 billion. IDC stated Cisco holds the largest share of the SD-WAN infrastructure market, with VMware coming in second followed by Silver Peak, Nokia-Nuage, and Riverbed.
+
+IDC also [recently wrote][13] about how security is also a key driver in recent SD-WAN deployments. 
+
+“With SD-WAN, mission-critical traffic and assets can be partitioned and protected against vulnerabilities in other parts of the enterprise. This use case appears to be especially popular in verticals such as retail, healthcare, and financial,” IDC wrote. 
+
+"SD-WAN can also protect application traffic from threats within the enterprise and from outside by leveraging a full stack of security solutions included in SD-WAN such as next-gen firewalls, IPS, URL filtering, malware protection, and cloud security. 
+
+These security features can enable Layer 3-7 protection for WAN traffic regardless of where it's headed - to the cloud or to the data center, IDC wrote.
+
+Application traffic to the cloud straight from the branch can now be secured using an internet or cloud gateway, IDC wrote. Users, applications and their data at the branch edge can be protected by the stack of security solutions incorporated into the SD-WAN on-premises appliance, vCPE or router, which typically includes  next-gen firewall, intrusion protection, malware protection and URL filtering, IDC wrote.
+
+Cisco [most recently][14] added support for its cloud-based security gateway – known as Umbrella – to its SD-WAN software offerings.  According to Cisco, Umbrella can provide the first line of defense against threats on the internet. By analyzing and learning from internet activity patterns, Umbrella automatically uncovers attacker infrastructure and blocks requests to malicious destinations before a connection is even established — without adding latency for users. With Umbrella, customers can stop phishing and malware infections earlier, identify already infected devices faster and prevent data exfiltration, Cisco says.
+
+The Umbrella announcement is on top of other recent SD-WAN security enhancements the company has made. In May Cisco added support for Advanced Malware Protection (AMP) to its million-plus ISR/ASR edge routers in an effort to reinforce branch- and core-network malware protection across the SD-WAN. AMP support is added to a menu of security features already included in Cisco's SD-WAN software including support for URL filtering, Snort Intrusion Prevention, the ability to segment users across the WAN and embedded platform security, including the Cisco Trust Anchor module.
+
+Last year Cisco added its Viptela SD-WAN technology to the IOS XE version 16.9.1 software that runs its core ISR/ASR routers.
+
+Join the Network World communities on [Facebook][15] and [LinkedIn][16] to comment on topics that are top of mind.
+
+--------------------------------------------------------------------------------
+
+via: https://www.networkworld.com/article/3429186/cisco-assesses-the-top-enterprise-sd-wan-technology-drivers.html
+
+作者：[Michael Cooney][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/Michael-Cooney/
+[b]: https://github.com/lujun9972
+[1]: https://images.idgesg.net/images/article/2018/08/2_networks_smart-city_iot_connected-100769196-large.jpg
+[2]: https://www.networkworld.com/article/3193888/why-cisco-needs-sd-wan-vendor-viptela.html
+[3]: https://blog.cimicorp.com/?p=3781
+[4]: https://www.networkworld.com/article/3323407/sd-wan/how-to-buy-sd-wan-technology-key-questions-to-consider-when-selecting-a-supplier.html
+[5]: https://www.networkworld.com/article/3328488/backup-systems-and-services/how-to-pick-an-off-site-data-backup-method.html
+[6]: https://www.networkworld.com/article/3250664/lan-wan/sd-branch-what-it-is-and-why-youll-need-it.html
+[7]: https://www.networkworld.com/article/3285728/sd-wan/what-are-the-options-for-securing-sd-wan.html?nsdr=true
+[8]: https://blogs.cisco.com/author/anandoswal
+[9]: https://www.cisco.com/c/dam/en_us/services/it-case-studies/ni-case-study.pdf
+[10]: https://www.idc.com/getdoc.jsp?containerId=prUS45380319
+[11]: https://www.idc.com/getdoc.jsp?containerId=PRF003513
+[12]: https://www.idc.com/getdoc.jsp?containerId=IDC_P2
+[13]: https://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise-networks/intelligent-wan/idc-tangible-benefits.pdf
+[14]: https://www.networkworld.com/article/3402079/cisco-offers-cloud-based-security-for-sd-wan-resources.html
+[15]: https://www.facebook.com/NetworkWorld/
+[16]: https://www.linkedin.com/company/network-world
diff --git a/sources/talk/20190801 Failure is a feature in blameless DevOps.md b/sources/talk/20190801 Failure is a feature in blameless DevOps.md
new file mode 100644
index 0000000000..d4a13a4e68
--- /dev/null
+++ b/sources/talk/20190801 Failure is a feature in blameless DevOps.md	
@@ -0,0 +1,77 @@
+[#]: collector: (lujun9972)
+[#]: translator: ( )
+[#]: reviewer: ( )
+[#]: publisher: ( )
+[#]: url: ( )
+[#]: subject: (Failure is a feature in blameless DevOps)
+[#]: via: (https://opensource.com/article/19/8/failure-feature-blameless-devops)
+[#]: author: (Alex Bunardzic https://opensource.com/users/alex-bunardzic)
+
+Failure is a feature in blameless DevOps
+======
+In blameless DevOps culture, failure is more than an option; it's our
+friend.
+![failure sign at a party, celebrating failure][1]
+
+DevOps is just another term for _value stream development_. What does _value stream_ mean?
+
+Value is what arises during our interactions with customers and stakeholders. Once we get into value stream development, we quickly realize that value is not an entity. Value constantly changes. Value is a process. Value is a flow.
+
+Hence the term _stream_. Value is only value if it's a stream. And this streaming of value is what we call continuous integration (CI).
+
+### How do we generate value?
+
+No matter how carefully we specify value, its expectations tend to change. Therefore, the only realistic way to define and generate value is to solicit feedback.
+
+But it's obvious that no one is volunteering feedback. People are busy. We need to solicit feedback from our customers and stakeholders, but somehow, they always have something more pressing to do. Even if we throw a tantrum and insist that they stop what they're doing and give us much-needed feedback, at best we'd get a few lukewarm comments. Very little to go by. People are busy.
+
+We slowly learn that the most efficient and effective way to solicit feedback is to fail. Failure is a sure-fire way to make our customers and stakeholders drop everything, sit up, and pay attention. If we refuse to fail, we continue marching down the development path confidently, only to discover later that we're in the wrong.
+
+Agile DevOps culture is about dropping this arrogant stance and adopting the attitude of humility. We admit that we don't know it all, and we commit to a more humble approach to working on the value stream.
+
+It is of paramount importance to fail as soon as possible. That way, failure is not critical; it is innocuous, easy to overcome, easy to fix. But we need feedback to know how to fix it. The best feedback is reaction to failure.
+
+Let's illustrate this dynamic visually:
+
+![Value generation via feedback loop][2]
+
+Value generation via a feedback loop from continuous solicitation
+
+This figure illustrates the dynamics of producing value by soliciting feedback in a continuous, never-ending fashion.
+
+### Where does failure fit?
+
+Where in the above process do we see failure? Time for another diagram:
+
+![Failure is central to feedback loop][3]
+
+Failure is the central driving force enabling the delivery of value stream.
+
+_Failure is center stage_. Without failure, nothing useful ever gets done. From this, we conclude that failure is our friend.
+
+### How do we know we failed?
+
+In the ~~good~~ bad old days of waterfall methodology, the prime directive was "Failure is not an option." We worked under the pressure that every step must be a fully qualified success. We were going out of our way to avoid getting any feedback. Feedback was reserved for the momentous Big Bang event; the point when we all got an earful on how much the system we built missed the mark.
+
+That was, in a nutshell, the traditional way of learning that we failed. With the advent of agile and DevOps, we underwent cultural transformation and embraced incremental, iterative development processes. Each iteration starts with a mini failure, fixes it, and keeps going (mini being the keyword here). But how do we know if we failed?
+
+The only way to know for sure is to have a measurable test or goal. The measurable test will let us know if—and how—we failed.
+
+Now that we have set the stage and exposed the fundamentals of the blameless, failure-centric culture, the next article in this series will dive into a more detailed exposition on how to iterate over failed attempts to satisfy measurable tests and goals.
+
+--------------------------------------------------------------------------------
+
+via: https://opensource.com/article/19/8/failure-feature-blameless-devops
+
+作者：[Alex Bunardzic][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/alex-bunardzic
+[b]: https://github.com/lujun9972
+[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/fail_failure_celebrate.png?itok=LbvDAEZF (failure sign at a party, celebrating failure)
+[2]: https://opensource.com/sites/default/files/uploads/valuestreamfeedbackloop.jpg (Value generation via feedback loop)
+[3]: https://opensource.com/sites/default/files/uploads/valuestreamfeedbackloopfailure.jpg (Failure is central to feedback loop)
diff --git a/sources/tech/20190628 How to Install and Use R on Ubuntu.md b/sources/tech/20190628 How to Install and Use R on Ubuntu.md
index abbbeef6a2..84699fbc8e 100644
--- a/sources/tech/20190628 How to Install and Use R on Ubuntu.md	
+++ b/sources/tech/20190628 How to Install and Use R on Ubuntu.md	
@@ -1,5 +1,5 @@
 [#]: collector: (lujun9972)
-[#]: translator: (guevaraya)
+[#]: translator: ( )
 [#]: reviewer: ( )
 [#]: publisher: ( )
 [#]: url: ( )
diff --git a/sources/tech/20190801 GitHub Pages is a CI-CD pipeline.md b/sources/tech/20190801 GitHub Pages is a CI-CD pipeline.md
new file mode 100644
index 0000000000..cad16c5512
--- /dev/null
+++ b/sources/tech/20190801 GitHub Pages is a CI-CD pipeline.md	
@@ -0,0 +1,74 @@
+[#]: collector: (lujun9972)
+[#]: translator: ( )
+[#]: reviewer: ( )
+[#]: publisher: ( )
+[#]: url: ( )
+[#]: subject: (GitHub Pages is a CI/CD pipeline)
+[#]: via: (https://opensource.com/article/19/8/github-pages-cicd-pipeline)
+[#]: author: (Katie McLaughlin https://opensource.com/users/glasnt)
+
+GitHub Pages is a CI/CD pipeline
+======
+Integrating just a little bit of automation into your workflow can
+greatly improve your productivity and development velocity.
+![An intersection of pipes.][1]
+
+One of GitHub's superpowers is the ability to _magically_ turn your documentation into a website. If you configure a [GitHub Page][2] for your **docs/** folder on your AwesomeProject website, you'll end up with **yourname.github.io/awesomeproject**, showing your documentation, all for free.
+
+But it's not actually magic. Sadly, even though we have taught glass to think, we can still only thank the advanced application of technology for anything that appears to be magical.
+
+GitHub Pages is just an integrated pathway within GitHub to help you set up a Jekyll project. [Jekyll][3] is a static site generator, written in Ruby. Out of the box you can quickly generate websites using markdown files that are then merged into pre-formatted HTML templated themes. There are many [default themes][4] available for GitHub Pages, or you can use one of the many [free templates][5] out there.
+
+![Jekyll Themes screenshot][6]
+
+There are many open source licensed templates available for use.
+
+When you first set up GitHub Pages, you declare which branch you want to build from and the domain you want to use. When you merge into that branch, GitHub goes and takes your Jekyll site, renders it, and hosts it for you on that domain. You don't have to do anything else. No FTP transfers onto a server. No server costs. [No GitHub costs][7]. This is all the power of automation.
+
+### Turning it up to 11 with Netlify PR previews
+
+One of the limitations of this system is when you're working with pull requests (PRs). If you want to test your code, you have to run Jekyll locally. This isn't [terribly difficult][8], but when you're reviewing someone else's PR, say when it's related to the documentation on a project's homepage, you want to be able to see what the new website will look like if you merge the PR. Especially if there could be issues with the changes that are proposed (particularly large changes, changes to the theme/layout, etc)
+
+Normally, you'd have to go to the PR, clone the fork of the repo and check out the branch that was used for the PR, merge that code into your local master, build _that_ version of the code in Jekyll, and open the local server to look at the changes.
+
+But the great thing is, you can automate this.
+
+One such service is [Netlify][9]. You can use Netlify to host your projects, but you can also use its [Deploy Previews][10] feature to generate Jekyll sites for any PR on your project automatically.
+
+Its [continuous deployment][11] docs show how to set up Netlify to automatically build your site any time a PR is opened or updated. The results of that build are available as a temporary website that is linked in the "Checks" section at the bottom of the PR, uniquely named for the PR and project. You can have multiple active PRs and Netlify will update the previews independently!
+
+This has greatly improved the website development process for [PyCon AU][12], which is using GitHub Pages to host the [2019 event website][13]. We heavily borrowed this idea and the Netlify setup from [DjangoCon US][14], which has every [DjangoCon website][15] on GitHub. Well, [most of them][16], as there is an ongoing project to ensure that every DjangoCon conference website is archived for prosperity.
+
+### Machines do the work, so people have time to code
+
+CI and CD have many benefits, but integrating just a little bit of automation into your workflow can greatly improve your productivity and development velocity.
+
+--------------------------------------------------------------------------------
+
+via: https://opensource.com/article/19/8/github-pages-cicd-pipeline
+
+作者：[Katie McLaughlin][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/glasnt
+[b]: https://github.com/lujun9972
+[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/LAW-Internet_construction_9401467_520x292_0512_dc.png?itok=RPkPPtDe (An intersection of pipes.)
+[2]: https://help.github.com/en/articles/configuring-a-publishing-source-for-github-pages
+[3]: https://jekyllrb.com/
+[4]: https://pages.github.com/themes/
+[5]: http://jekyllthemes.org/
+[6]: https://opensource.com/sites/default/files/uploads/jekyll-themes.png (Jekyll Themes screenshot)
+[7]: https://github.com/pricing
+[8]: https://jekyllrb.com/docs/
+[9]: https://www.netlify.com/
+[10]: https://www.netlify.com/blog/2017/10/31/introducing-public-deploy-logs-for-open-source-sites/
+[11]: https://www.netlify.com/docs/continuous-deployment/
+[12]: http://2019.pycon-au.org
+[13]: https://github.com/pyconau/2019.pycon-au.org
+[14]: https://2019.djangocon.us/
+[15]: https://github.com/djangocon
+[16]: https://github.com/djangocon/djangocon-archive-project
diff --git a/sources/tech/20190801 Linux permissions 101.md b/sources/tech/20190801 Linux permissions 101.md
new file mode 100644
index 0000000000..cfbc3d0a29
--- /dev/null
+++ b/sources/tech/20190801 Linux permissions 101.md	
@@ -0,0 +1,346 @@
+[#]: collector: (lujun9972)
+[#]: translator: ( )
+[#]: reviewer: ( )
+[#]: publisher: ( )
+[#]: url: ( )
+[#]: subject: (Linux permissions 101)
+[#]: via: (https://opensource.com/article/19/8/linux-permissions-101)
+[#]: author: (Alex Juarez https://opensource.com/users/mralexjuarezhttps://opensource.com/users/marcobravohttps://opensource.com/users/greg-p)
+
+Linux permissions 101
+======
+Knowing how to control users' access to files is a fundamental system
+administration skill.
+![Penguins][1]
+
+Understanding Linux permissions and how to control which users have access to files is a fundamental skill for systems administration.
+
+This article will cover standard Linux file systems permissions, dig further into special permissions, and wrap up with an explanation of default permissions using **umask**.
+
+### Understanding the ls command output
+
+Before we can talk about how to modify permissions, we need to know how to view them. The **ls** command with the long listing argument (**-l**) gives us a lot of information about a file.
+
+
+```
+$ ls -lAh
+total 20K
+-rwxr-xr--+ 1 root root    0 Mar  4 19:39 file1
+-rw-rw-rw-. 1 root root    0 Mar  4 19:39 file10
+-rwxrwxr--+ 1 root root    0 Mar  4 19:39 file2
+-rw-rw-rw-. 1 root root    0 Mar  4 19:39 file8
+-rw-rw-rw-. 1 root root    0 Mar  4 19:39 file9
+drwxrwxrwx. 2 root root 4.0K Mar  4 20:04 testdir
+```
+
+To understand what this means, let's break down the output regarding the permissions into individual sections. It will be easier to reference each section individually.
+
+Take a look at each component of the final line in the output above:
+
+
+```
+`drwxrwxrwx. 2 root root 4.0K Mar  4 20:04 testdir`
+```
+
+Section 1 | Section 2 | Section 3 | Section 4 | Section 5 | Section 6 | Section 7
+---|---|---|---|---|---|---
+d | rwx | rwx | rwx | . | root | root
+
+Section 1 (on the left) reveals what type of file it is.
+
+d | Directory
+---|---
+- | Regular file
+l | A soft link
+
+The [info page][2] for **ls** has a full listing of the different file types.
+
+Each file has three modes of access:
+
+  * the owner
+  * the group
+  * all others
+
+
+
+Sections 2, 3, and 4 refer to the user, group, and "other users" permissions. And each section can include a combination of **r** (read), **w** (write), and **x** (executable) permissions.
+
+Each of the permissions is also assigned a numerical value, which is important when talking about the octal representation of permissions.
+
+Permission | Octal Value
+---|---
+Read | 4
+Write | 2
+Execute | 1
+
+Section 5 details any alternative access methods, such as SELinux or File Access Control List (FACL).
+
+Method | Character
+---|---
+No other method | -
+SELinux | .
+FACLs | +
+Any combination of methods | +
+
+Sections 6 and 7 are the names of the owner and the group, respectively.
+
+### Using chown and chmod
+
+#### The chown command
+
+The **chown** (change ownership) command is used to change a file's user and group ownership.
+
+To change both the user and group ownership of the file **foo** to **root**, we can use these commands:
+
+
+```
+$ chown root:root foo
+$ chown root: foo
+```
+
+Running the command with the user followed by a colon (**:**) sets both the user and group ownership.
+
+To set only the user ownership of the file **foo** to the **root** user, enter:
+
+
+```
+`$ chown root foo`
+```
+
+To change only the group ownership of the file **foo**, precede the group with a colon:
+
+
+```
+`$ chown :root foo`
+```
+
+#### The chmod command
+
+The **chmod** (change mode) command controls file permissions for the owner, group, and all other users who are neither the owner nor part of the group associated with the file.
+
+The **chmod** command can set permissions in both octal (e.g., 755, 644, etc.) and symbolic (e.g., u+rwx, g-rwx, o=rw) formatting.
+
+Octal notation assigns 4 "points" to **read**, 2 to **write**, and 1 to **execute**. If we want to assign the user **read** permissions, we assign 4 to the first slot, but if we want to add **write** permissions, we must add 2. If we want to add **execute**, then we add 1. We do this for each permission type: owner, group, and others.
+
+For example, if we want to assign **read**, **write**, and **execute** to the owner of the file, but only **read** and **execute** to group members and all other users, we would use 755 in octal formatting. That's all permission bits for the owner (4+2+1), but only a 4 and 1 for the group and others (4+1).
+
+> The breakdown for that is: 4+2+1=7; 4+1=5; and 4+1=5.
+
+If we wanted to assign **read** and **write** to the owner of the file but only **read** to members of the group and all other users, we could use **chmod** as follows:
+
+
+```
+`$ chmod 644 foo_file`
+```
+
+In the examples below, we use symbolic notation in different groupings. Note the letters **u**, **g**, and **o** represent **user**, **group**, and **other**. We use **u**, **g**, and **o** in conjunction with **+**, **-**, or **=** to add, remove, or set permission bits.
+
+To add the **execute** bit to the ownership permission set:
+
+
+```
+`$ chmod u+x foo_file`
+```
+
+To remove **read**, **write**, and **execute** from members of the group:
+
+
+```
+`$ chmod g-rwx foo_file`
+```
+
+To set the ownership for all other users to **read** and **write**:
+
+
+```
+`$ chmod o=rw`
+```
+
+### The special bits: Set UID, set GID, and sticky bits
+
+In addition to the standard permissions, there are a few special permission bits that have some useful benefits.
+
+#### Set user ID (suid)
+
+When **suid** is set on a file, an operation executes as the owner of the file, not the user running the file. A [good example][3] of this is the **passwd** command. It needs the **suid** bit to be set so that changing a password runs with root permissions.
+
+
+```
+$ ls -l /bin/passwd
+-rwsr-xr-x. 1 root root 27832 Jun 10  2014 /bin/passwd
+```
+
+An example of setting the **suid** bit would be:
+
+
+```
+`$ chmod u+s /bin/foo_file_name`
+```
+
+#### Set group ID (sgid)
+
+The **sgid** bit is similar to the **suid** bit in the sense that the operations are done under the group ownership of the directory instead of the user running the command.
+
+An example of using **sgid** would be if multiple users are working out of the same directory, and every file created in the directory needs to have the same group permissions. The example below creates a directory called **collab_dir**, sets the **sgid** bit, and changes the group ownership to **webdev**.
+
+
+```
+$ mkdir collab_dir
+$ chmod g+s collab_dir
+$ chown :webdev collab_dir
+```
+
+Now any file created in the directory will have the group ownership of **webdev** instead of the user who created the file.
+
+
+```
+$ cd collab_dir
+$ touch file-sgid
+$ ls -lah file-sgid
+-rw-r--r--. 1 root webdev 0 Jun 12 06:04 file-sgid
+```
+
+#### The "sticky" bit
+
+The sticky bit denotes that only the owner of a file can delete the file, even if group permissions would otherwise allow it. This setting usually makes the most sense on a common or collaborative directory such as **/tmp**. In the example below, the **t** in the **execute** column of the **all others** permission set indicates that the sticky bit has been applied.
+
+
+```
+$ ls -ld /tmp
+drwxrwxrwt. 8 root root 4096 Jun 12 06:07 /tmp/
+```
+
+Keep in mind this does not prevent somebody from editing the file; it just keeps them from deleting the contents of a directory.
+
+We set the sticky bit with:
+
+
+```
+`$ chmod o+t foo_dir`
+```
+
+On your own, try setting the sticky bit on a directory and give it full group permissions so that multiple users can read, write and execute on the directory because they are in the same group.
+
+From there, create files as each user and then try to delete them as the other.
+
+If everything is configured correctly, one user should not be able to delete users from the other user.
+
+Note that each of these bits can also be set in octal format with SUID=4, SGID=2, and Sticky=1.
+
+
+```
+$ chmod 4744
+$ chmod 2644
+$ chmod 1755
+```
+
+#### Uppercase or lowercase?
+
+If you are setting the special bits and see an uppercase **S** or **T** instead of lowercase (as we've seen until this point), it is because the underlying execute bit is not present. To demonstrate, the following example creates a file with the sticky bit set. We can then add/remove the execute bit to demonstrate the case change.
+
+
+```
+$ touch file cap-ST-demo
+$ chmod 1755 cap-ST-demo
+$ ls -l cap-ST-demo
+-rwxr-xr-t. 1 root root 0 Jun 12 06:16 cap-ST-demo
+
+$ chmod o-x cap-X-demo
+$ ls -l cap-X-demo
+-rwxr-xr-T. 1 root root 0 Jun 12 06:16 cap-ST-demo
+```
+
+#### Setting the execute bit conditionally
+
+To this point, we've set the **execute** bit using a lowercase **x**, which sets it without asking any questions. We have another option: using an uppercase **X** instead of lowercase will set the **execute** bit only if it is already present somewhere in the permission group. This can be a difficult concept to explain, but the demo below will help illustrate it. Notice here that after trying to add the **execute** bit to the group privileges, it is not applied.
+
+
+```
+$ touch cap-X-file
+$ ls -l cap-X-file
+-rw-r--r--. 1 root root 0 Jun 12 06:31 cap-X-file
+$ chmod g+X cap-X-file
+$ ls -l cap-X-file
+-rw-r--r--. 1 root root 0 Jun 12 06:31 cap-X-file
+```
+
+In this similar example, we add the execute bit first to the group permissions using the lowercase **x** and then use the uppercase **X** to add permissions for all other users. This time, the uppercase **X** sets the permissions.
+
+
+```
+$ touch cap-X-file
+$ ls -l cap-X-file
+-rw-r--r--. 1 root root 0 Jun 12 06:31 cap-X-file
+$ chmod g+x cap-X-file
+$ ls -l cap-X-file
+-rw-r-xr--. 1 root root 0 Jun 12 06:31 cap-X-file
+$ chmod g+x cap-X-file
+$ chmod o+X cap-X-file
+ls -l cap-X-file
+-rw-r-xr-x. 1 root root 0 Jun 12 06:31 cap-X-file
+```
+
+### Understanding umask
+
+The **umask** masks (or "blocks off") bits from the default permission set in order to define permissions for a file or directory. For example, a 2 in the **umask** output indicates it is blocking the **write** bit from a file, at least by default.
+
+Using the **umask** command without any arguments allows us to see the current **umask** setting. There are four columns: the first is reserved for the special suid, sgid, or sticky bit, and the remaining three represent the owner, group, and other permissions.
+
+
+```
+$ umask
+0022
+```
+
+To understand what this means, we can execute **umask** with a **-S** (as shown below) to get the result of masking the bits. For instance, because of the **2** value in the third column, the **write** bit is masked off from the group and other sections; only **read** and **execute** can be assigned for those.
+
+
+```
+$ umask -S
+u=rwx,g=rx,o=rx
+```
+
+To see what the default permission set is for files and directories, let's set our **umask** to all zeros. This means that we are not masking off any bits when we create a file.
+
+
+```
+$ umask 000
+$ umask -S
+u=rwx,g=rwx,o=rwx
+
+$ touch file-umask-000
+$ ls -l file-umask-000
+-rw-rw-rw-. 1 root root 0 Jul 17 22:03 file-umask-000
+```
+
+Now when we create a file, we see the default permissions are **read** (4) and **write** (2) for all sections, which would equate to 666 in octal representation.
+
+We can do the same for a directory and see its default permissions are 777. We need the **execute** bit on directories so we can traverse through them.
+
+
+```
+$ mkdir dir-umask-000
+$ ls -ld dir-umask-000
+drwxrwxrwx. 2 root root 4096 Jul 17 22:03 dir-umask-000/
+```
+
+### Conclusion
+
+There are many other ways an administrator can control access to files on a system. These permissions are basic to Linux, and we can build upon these fundamental aspects. If your work takes you into FACLs or SELinux, you will see that they also build upon these first rules of file access.
+
+--------------------------------------------------------------------------------
+
+via: https://opensource.com/article/19/8/linux-permissions-101
+
+作者：[Alex Juarez][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/mralexjuarezhttps://opensource.com/users/marcobravohttps://opensource.com/users/greg-p
+[b]: https://github.com/lujun9972
+[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/linux-penguins.png?itok=yKOpaJM_ (Penguins)
+[2]: https://www.gnu.org/software/texinfo/manual/info-stnd/info-stnd.html
+[3]: https://www.theurbanpenguin.com/using-a-simple-c-program-to-explain-the-suid-permission/