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:
commit
20622712d2
@ -0,0 +1,72 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (FCC boosts Wi-Fi 6 spectrum five-fold)
|
||||
[#]: via: (https://www.networkworld.com/article/3540288/fcc-boosts-wi-fi-6-spectrum-five-fold.html)
|
||||
[#]: author: (Jon Gold https://www.networkworld.com/author/Jon-Gold/)
|
||||
|
||||
FCC boosts Wi-Fi 6 spectrum five-fold
|
||||
======
|
||||
The Federal Communications Commission has approved a chunk of wireless spectrum called the 6GHz band for unlicensed use by Wi-Fi 6, and gear that supports it could be available by the end of the year.
|
||||
[tejasp][1] [(CC0)][2]
|
||||
|
||||
The Federal Communications commission has opened up a wide swath of wireless spectrum for unlicensed use by Wi-Fi devices, which will lead to Wi-Fi access points that have greatly expanded capacity.
|
||||
|
||||
It’s a huge victory for the Wi-Fi industry, as the ruling means that the amount of spectrum available for Wi-Fi just about quintupled in an instant. That means big, spacious channels – and a lot more channels overall – that can handle a lot more data and a lot more connections at the same time, according to Aruba vice president of wireless strategy and standards Chuck Lukaszewski.
|
||||
|
||||
[[Get regularly scheduled insights by signing up for Network World newsletters.]][3]
|
||||
|
||||
“Overnight, you’re going to see an additional gigabit per second or more of potential throughput,” he said.
|
||||
|
||||
That’s a major upside, certainly, even if “overnight” might be a slightly optimistic view of when [Wi-Fi 6E][4] – the trade name for the new version of Wi-Fi that will take advantage of the new spectrum – hits the market. While some of the necessary standards haven’t yet been finalized by the IEEE, the basic ability to use 6GHz frequencies is already written into the existing Wi-Fi 6 specification.
|
||||
|
||||
Broadcom director of product marketing and government affairs Chris Szymanski said that the main technical hurdle to implementing Wi-Fi 6E will be new radios, but that his company is among those that has already been designing and building compatible silicon.
|
||||
|
||||
“I expect that the FCC will provide guidance on how to certify devices in the next few months,” he said. “I expect product available in the US in the late fall before the holidays.”
|
||||
|
||||
Enterprise uptake will likely have to wait until compatible smartphones, laptops and the like are on shelves because existing Wi-Fi 6 cliets won’t be able to take advantage of the new 6Ghz spectrum.
|
||||
|
||||
**[ [Take this mobile device management course from PluralSight and learn how to secure devices in your company without degrading the user experience.][5] ]**
|
||||
|
||||
New access points are likely to have three radios in them, as opposed to the usual two, noted senior vice president of Ruckus Wireless and cloud at Commscope Bart Giordano. One each for the existing 2.4GHz and 5GHz bands, and a third for 6Ghz.
|
||||
|
||||
“Antennas will be very similar because these spectrums sit next to one another,” he said, “but there’s specific tunings you have to do.”
|
||||
|
||||
The driving force behind the spectrum expansion is the bottomless demand for capacity caused by the increasing use of wireless just about everywhere. The FCC’s announcement cites projections from Cisco that say about 60% of worldwide data traffic will move across Wi-Fi links within the next two years.
|
||||
|
||||
Incumbent licensed users of parts of the 6GHz spectrum – which are mostly businesses using microwave links for wireless backhaul and public safety services – are far less pleased by the FCC’s decision. The Utilities Technology Council is one of several groups critical of earlier proposals to open the 6GHz band to broad-based unlicensed use, saying earlier that assurances that existing users would be protected from interference are unconvincing.
|
||||
|
||||
“We have and will continue to provide the FCC with technical detail demonstrating the very real interference potential from unlicensed use across all parts of the band and the need for thoroughly tested automated frequency coordination (AFC) to protect incumbent users,” the group said in a statement. “While we appreciate the FCC proposing to require AFC for the standard-power access points, these measures must also be applied to all unlicensed devices in the band to prevent interference to mission-critical utility communications systems.”
|
||||
|
||||
Farpoint Group principal and Network World contributor Craig Mathias said that it’s not going to be a smooth process, but argues that the opening of 6GHz spectrum was too great an opportunity to ignore.
|
||||
|
||||
“Yes, it’s a mess – spectral re-allocations always are,” he said. “[But] I don't see any issues here that can't be addressed, and more unlicensed spectrum is of course always desirable.”
|
||||
|
||||
Incumbent users of the 6GHz spectrum are unlikely to see the type of interference they’re particularly worried about, he added, given the nature of the connections currently in use and the safeguards in the new rule that are designed to protect existing networks.
|
||||
|
||||
“Point-to-point microwave links operate at fairly high power and use both directional antennas and error-checking protocols to ensure reliability and otherwise deal with typical radio issues beyond interference, like the various forms of fading,” said Mathias. “A nearby Wi-Fi transmitter will be operating at much lower power and use its own signal-integrity-management techniques as well. So likely no issues in the vast majority of cases, especially if history is any guide.”
|
||||
|
||||
Join the Network World communities on [Facebook][6] and [LinkedIn][7] to comment on topics that are top of mind.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.networkworld.com/article/3540288/fcc-boosts-wi-fi-6-spectrum-five-fold.html
|
||||
|
||||
作者:[Jon Gold][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/Jon-Gold/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://pixabay.com/en/wifi-wireless-device-wi-fi-1371030/
|
||||
[2]: https://creativecommons.org/publicdomain/zero/1.0/
|
||||
[3]: https://www.networkworld.com/newsletters/signup.html
|
||||
[4]: https://www.networkworld.com/article/3238664/80211-wi-fi-standards-and-speeds-explained.html
|
||||
[5]: https://pluralsight.pxf.io/c/321564/424552/7490?u=https%3A%2F%2Fwww.pluralsight.com%2Fcourses%2Fmobile-device-management-big-picture
|
||||
[6]: https://www.facebook.com/NetworkWorld/
|
||||
[7]: https://www.linkedin.com/company/network-world
|
@ -0,0 +1,89 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Red Hat Enterprise Linux 8.2 Hits the stage)
|
||||
[#]: via: (https://www.networkworld.com/article/3540189/red-hat-enterprise-linux-82-hits-the-stage.html)
|
||||
[#]: author: (Sandra Henry-Stocker https://www.networkworld.com/author/Sandra-Henry_Stocker/)
|
||||
|
||||
Red Hat Enterprise Linux 8.2 Hits the stage
|
||||
======
|
||||
RHEL 8.2 has new capabilities for management of hybrid-cloud environments and container tools to help fuel cloud-native development.
|
||||
Stephen Lawson/IDG
|
||||
|
||||
Red Hat Enterprise Linux (RHEL) 8.2 brings new features that include expanded monitoring capabilities in Red Hat Insights for and new container tools, including containerized versions of Skopeo and Buildah.
|
||||
|
||||
Red Hat says RHEL 8.2 is arriving at a time when, because of the Covid-19 pandemic, a growing percentage of IT staffers are working remotely. Their ability to support the management and monitoring of operations and their ability to detect and address problems has never been more critical, and upgrades to Red Hat Insights are designed to help.
|
||||
|
||||
[[Get regularly scheduled insights by signing up for Network World newsletters.]][1]
|
||||
|
||||
### Red Hat Insights
|
||||
|
||||
[Red Hat Insights][2], is Red Hat’s operations and security-risk-management offering and helps detect, diagnose and remediate potential problems before they affect production systems or end users. It was included in RHEL in May 2019.
|
||||
|
||||
The latest updates include:
|
||||
|
||||
* Improved visibility and security for managing large, complex environments
|
||||
* Policy and patch services to help determine which product advisories apply and guidance for problem remediation
|
||||
* A "drift service" to make it easier to compare baselines, shape strategies that reduce complexity, and make troubleshooting easier
|
||||
|
||||
|
||||
|
||||
### Monitoring and performance updates
|
||||
|
||||
RHEL 8.2 brings some performance upgrades includeing:
|
||||
|
||||
* Improved resource management with Control Groups (cgroup) v2, which is designed to reserve and set limits on memory usage to help prevent processes from overconsuming memory and causing system failures or slowdowns.
|
||||
* Optimizing performance-sensitive workloads via NUMA and sub-NUMA service policies.
|
||||
* Performance Co-Pilot (PCP) 5.0.2 which adds collection agents for Microsoft SQL Server 2019 to gather and analyze SQL Server metrics to draw a clearer picture of database and operating-system performance.
|
||||
* Red Hat subscription watch,a service for viewing and managing RHEL and Red Hat OpenShift Container Platform subscriptions.
|
||||
|
||||
|
||||
|
||||
### Evolving container tools
|
||||
|
||||
RHEL 8.2 includes new container tools that are supported for 24 months as part of Red Hat's Tech Preview, which provides early access to new products. The tools include Buildah for building and Skopeo for transferring container images.
|
||||
|
||||
The new relase also introduces Udica, a policy tool for containerized SELinux that can make it less likely that processes will break out of containers and cause problems to other containers or the host.
|
||||
|
||||
[][3]
|
||||
|
||||
Red Hat Enterprise Linux 8.2 also introduces enhancements to the Red Hat Universal Base Image, including:
|
||||
|
||||
* OpenJDK and .NET 3.0 for developing certification-ready cloud-native Red Hat applications
|
||||
* **Improved access to source code associated with a given image through a single command**, making it easier for Red Hat partners to meet source code requirements for open source licensing needs.
|
||||
|
||||
|
||||
|
||||
### Ease of use
|
||||
|
||||
Other new features are meant to make it easier to manage RHEL:
|
||||
|
||||
* RHEL subscription registration as part of the installation process, making it easier to on-board new installations.
|
||||
* Enabling Red Hat Insights during installation to simplify the launch of Insights for Red Hat Enterprise Linux deployments.
|
||||
* Refinement and control of the Red Hat Enterprise Linux life cycle with testing for in-place upgrades, Red Hat Insights rules to help with upgrades, and the [Convert2 RHEL][4] tool that can help shift workloads from unsupported clones like CentOS to RHEL.
|
||||
|
||||
|
||||
|
||||
Join the Network World communities on [Facebook][5] and [LinkedIn][6] to comment on topics that are top of mind.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.networkworld.com/article/3540189/red-hat-enterprise-linux-82-hits-the-stage.html
|
||||
|
||||
作者:[Sandra Henry-Stocker][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/Sandra-Henry_Stocker/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://www.networkworld.com/newsletters/signup.html
|
||||
[2]: https://www.redhat.com/en/blog/expanding-management-operational-and-security-risks-new-red-hat-insights
|
||||
[3]: https://www.networkworld.com/blog/itaas-and-the-corporate-storage-technology/?utm_source=IDG&utm_medium=promotions&utm_campaign=HPE22140&utm_content=sidebar (ITAAS and Corporate Storage Strategy)
|
||||
[4]: https://www.redhat.com/en/blog/convert2rhel-how-update-rhel-systems-place-subscribe-rhel
|
||||
[5]: https://www.facebook.com/NetworkWorld/
|
||||
[6]: https://www.linkedin.com/company/network-world
|
@ -1,202 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (4 Git scripts I can't live without)
|
||||
[#]: via: (https://opensource.com/article/20/4/git-extras)
|
||||
[#]: author: (Vince Power https://opensource.com/users/vincepower)
|
||||
|
||||
4 Git scripts I can't live without
|
||||
======
|
||||
The Git Extras repo hosts more than 60 scripts that add to Git's basic
|
||||
functionality. Here's how to install, use, and contribute to it.
|
||||
![Person using a laptop][1]
|
||||
|
||||
In 2005, [Linus Torvalds][2] created [Git][3] to replace the proprietary distributed source control management solution that he had previously used to maintain the Linux kernel. Since then, Git has become a dominant version-control solution for open source and cloud-native development teams.
|
||||
|
||||
Even feature-rich applications like Git don't have every feature that people want or need, so they make the effort to create them. In the case of Git, that person would be [TJ Holowaychuk][4]. His [Git Extras][5] project hosts more than 60 "extras" with features that expand Git's basic functionality.
|
||||
|
||||
### Using Git Extras
|
||||
|
||||
Here's how to use four of the most popular Git Extras.
|
||||
|
||||
#### git-ignore
|
||||
|
||||
git-ignore is a convenient extra that allows you to manually add file types and comments to the **.git-ignore** file without having to open a text editor. It works with both the global ignore file for your user account and the individual ignore file for the repository you are working in.
|
||||
|
||||
Executing git-ignore without a parameter will list the global ignore file first, then the local ignore files.
|
||||
|
||||
|
||||
```
|
||||
$ git ignore
|
||||
Global gitignore: /home/alice/.gitignore
|
||||
# Numerous always-ignore extensions
|
||||
*.diff
|
||||
*.err
|
||||
*.orig
|
||||
*.rej
|
||||
*.swo
|
||||
*.swp
|
||||
*.vi
|
||||
*~
|
||||
*.sass-cache
|
||||
|
||||
# OS or Editor folders
|
||||
Thumbs.db
|
||||
\---------------------------------
|
||||
Local gitignore: .gitignore
|
||||
nbproject
|
||||
```
|
||||
|
||||
#### git-info
|
||||
|
||||
git-info retrieves all the information you need to get your head in the context of a repo you are working with. It includes any remote URLs, remote branches, local branches, configuration info, and the last commit.
|
||||
|
||||
|
||||
```
|
||||
$ git info
|
||||
|
||||
## Remote URLs:
|
||||
|
||||
origin [git@github.com][6]:sampleAuthor/git-extras.git (fetch)
|
||||
origin [git@github.com][6]:sampleAuthor/git-extras.git (push)
|
||||
|
||||
## Remote Branches:
|
||||
|
||||
origin/HEAD -> origin/master
|
||||
origin/myBranch
|
||||
|
||||
## Local Branches:
|
||||
|
||||
myBranch
|
||||
* master
|
||||
|
||||
## Most Recent Commit:
|
||||
|
||||
commit e3952df2c172c6f3eb533d8d0b1a6c77250769a7
|
||||
Author: Sample Author <[sampleAuthor@gmail.com][7]>
|
||||
|
||||
Added git-info command.
|
||||
|
||||
Type ´git log´ for more commits, or ´git show <commit id>´ for full commit details.
|
||||
|
||||
## Configuration (.git/config):
|
||||
|
||||
color.diff=auto
|
||||
color.status=auto
|
||||
color.branch=auto
|
||||
user.name=Sample Author
|
||||
user.email=[sampleAuthor@gmail.com][7]
|
||||
core.repositoryformatversion=0
|
||||
core.filemode=true
|
||||
core.bare=false
|
||||
core.logallrefupdates=true
|
||||
core.ignorecase=true
|
||||
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
|
||||
remote.origin.url=[git@github.com][6]:mub/git-extras.git
|
||||
branch.master.remote=origin
|
||||
branch.master.merge=refs/heads/master
|
||||
```
|
||||
|
||||
#### git-mr and git-pr
|
||||
|
||||
These extras do similar things and work in basically the same way.
|
||||
|
||||
* git-mr checks out a merge request from GitLab
|
||||
* git-pr checks out a pull request on GitHub
|
||||
|
||||
|
||||
|
||||
In either case, you just need the merge or pull request number or the full URL, and it will fetch the remote reference, check out the branch, and adjust the config, so Git knows which branch it will replace.
|
||||
|
||||
|
||||
```
|
||||
$ git mr 51
|
||||
From gitlab.com:owner/repository
|
||||
* [new ref] refs/merge-requests/51/head -> mr/51
|
||||
Switched to branch 'mr/51'
|
||||
```
|
||||
|
||||
#### git-release
|
||||
|
||||
By combining **commit**, **tag**, and **push** into a single command, git-release saves a lot of keystrokes for executing three commands that often run in sequence.
|
||||
|
||||
To commit with a specific **<tagname>** and a custom message:
|
||||
|
||||
|
||||
```
|
||||
`$ git release 0.1.0 -m <+ powerful feature added>`
|
||||
```
|
||||
|
||||
#### Other extras
|
||||
|
||||
These are just four of the 60+ Git Extras in the repo. To access the full list of commands available in Git Extras, either review the [Commands.md][8] file in the source repository or run the following command after you install Git Extras.
|
||||
|
||||
|
||||
```
|
||||
`$ git extras --help`
|
||||
```
|
||||
|
||||
### Install Git Extras
|
||||
|
||||
The main prerequisite for Git Extras is having the command-line version of Git installed. If you plan to build from source, you also need additional utilities (e.g., **make**) to be available.
|
||||
|
||||
If you are using a recent version of macOS, Git Extras installation is best handled using [Homebrew][9] (as with most open source tools):
|
||||
|
||||
|
||||
```
|
||||
`$ brew install git-extras`
|
||||
```
|
||||
|
||||
On Linux, Git Extras is available on each platform's native package manager. Sometimes, you need to enable an extra repository, like [EPEL][10] on CentOS, then run a single command:
|
||||
|
||||
|
||||
```
|
||||
`$ sudo yum install git-extras`
|
||||
```
|
||||
|
||||
Full installation instructions for other Linux distributions, BSD, and other platforms are available in the [Installation.md][11] file in the repository.
|
||||
|
||||
### Contributing
|
||||
|
||||
Do you have a piece of functionality you think is missing from Git and have built or want to build a script to handle it? Why not share it with the world by making it part of the Git Extras distribution!
|
||||
|
||||
To do so, contribute the functionality to the Git Extras repository. There are more specific details in the [CONTRIBUTING.md][12] file in the repository, but the basics are easy:
|
||||
|
||||
1. Create a Bash script that handles the functionality.
|
||||
2. Create a basic man file so people will know how to use it.
|
||||
3. Update the command list and completion scripts to let people know the functionality exists.
|
||||
4. Run the integrity check to make sure you didn't break anything.
|
||||
5. Create a pull request for your functionality.
|
||||
|
||||
|
||||
|
||||
Contributing to Git Extras will go a long way towards making life a little easier for your fellow Git users. You can learn more about it in the project's [README][13].
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/4/git-extras
|
||||
|
||||
作者:[Vince Power][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/vincepower
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/laptop_screen_desk_work_chat_text.png?itok=UXqIDRDD (Person using a laptop)
|
||||
[2]: https://en.wikipedia.org/wiki/Linus_Torvalds
|
||||
[3]: https://git-scm.com/
|
||||
[4]: https://github.com/tj
|
||||
[5]: https://github.com/tj/git-extras
|
||||
[6]: mailto:git@github.com
|
||||
[7]: mailto:sampleAuthor@gmail.com
|
||||
[8]: https://github.com/tj/git-extras/blob/master/Commands.md
|
||||
[9]: https://brew.sh/
|
||||
[10]: https://fedoraproject.org/wiki/EPEL
|
||||
[11]: https://github.com/tj/git-extras/blob/master/Installation.md
|
||||
[12]: https://github.com/tj/git-extras/blob/master/CONTRIBUTING.md
|
||||
[13]: https://github.com/tj/git-extras/blob/master/Readme.md
|
@ -0,0 +1,55 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (What you need to know about open source ad blockers)
|
||||
[#]: via: (https://opensource.com/article/20/4/ad-blockers)
|
||||
[#]: author: (Joshua Pearce https://opensource.com/users/jmpearce)
|
||||
|
||||
What you need to know about open source ad blockers
|
||||
======
|
||||
Three open source ad blockers were tested against a "no ad blocker"
|
||||
control.
|
||||
![Browser of things][1]
|
||||
|
||||
A new [study][2] meant to investigate energy conservation of free and open source ad blockers has unexpectedly shown that Internet ads are wasting shocking amounts of your time.
|
||||
|
||||
More importantly, the results show how you can get that time back. The study estimates that the average Internet user would save over 100 hours a year by using [uBlock Origi][3][n][3][,][3] a free and open source ad blocker. uBlock Origin was the most effective ad blocker tested, but all ad blockers save time, energy and money according to the study.
|
||||
|
||||
![Ad blocker screen comparison][4]
|
||||
|
||||
The results show that page load time dropped 11% with [AdBlock+][5], 22% with [Privacy Badger][6], and 28% with [uBlock Origi][3][n][3]. These are not significant on a single page, but Internet users spend more than half of their time online rapidly clicking through websites, spending less than 15 seconds on a given page. With all these clicks, the additional time to load ads really starts to add up.
|
||||
|
||||
The article _[Energy Conservation with Open Source Ad Blockers][7]_, published in the journal _Technologies,_ was originally conceived to address rising energy consumption. Internet-related electricity consumption is rising rapidly as global Internet users spend more than 6.5 hours per day online. Americans, for example, have more than doubled the time they spend online since 2000 to almost 24 hours a week. Open source ad blockers have the potential to reduce the time, and thus the electricity, spent by eliminating ads during Internet browsing and video streaming.
|
||||
|
||||
In the study, three open source ad blockers were tested against a "no ad blocker" control. Page load times were recorded for browsing a representative selection of the most-accessed websites worldwide, including web searching (Google, Yahoo, Bing), information (Weather.com, Wikipedia), and news sites (CNN, Fox, New York Times). In addition, the study analyzed the time spent watching ads on videos for both trending and non-trending content. This part of the study was more challenging due to the lack of data on the ratio of YouTube watching time spent on trending vs. non-trending content. The time wasted viewing ads per video ranged from 0.06% up to a staggering 21%. Thus, the total hours lost to loading ads was only recorded for browsing.
|
||||
|
||||
Overall, the results showed that the energy wasted loading ads is not trivial. As a lot of the electricity used for running computers continues to come from coal, which causes air pollution and premature death, the study analyzed the potential for ad blockers to save American lives. The results were shocking: the energy conserved if everyone in the United States used the open source ad blocker would save over 36 American lives per year.
|
||||
|
||||
Electricity costs money, so cutting ads could also save consumers money. In the United States, if all Internet users enabled Privacy Badger on their computers, Americans would save more than $91 million annually. Globally, the results of the investigation were even more striking. uBlock Origin could save global consumers more than $1.8 billion a year.
|
||||
|
||||
This study was done before everyone was forced to stay home because of the COVID-19 pandemic, so all the values can be viewed as conservative underestimates. Overall, the study found open source ad blockers are a potentially effective technology for energy conservation.
|
||||
|
||||
Although free and open source ad blockers save energy and are good for the environment, you are probably going to use them primarily to block annoying ads and save yourself time.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/4/ad-blockers
|
||||
|
||||
作者:[Joshua Pearce][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/jmpearce
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/browser_desktop_website_checklist_metrics.png?itok=OKKbl1UR (Browser of things)
|
||||
[2]: https://www.mdpi.com/2227-7080/8/2/18
|
||||
[3]: https://github.com/gorhill/uBlock
|
||||
[4]: https://opensource.com/sites/default/files/uploads/os_ad_blocker_story_.png (Ad blocker screen comparison)
|
||||
[5]: https://adblockplus.org/
|
||||
[6]: https://privacybadger.org/
|
||||
[7]: https://www.academia.edu/42434401/Energy_Conservation_with_Open_Source_Ad_Blockers
|
@ -0,0 +1,76 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (What Happened to IPv5? Why there is IPv4, IPv6 but no IPv5?)
|
||||
[#]: via: (https://itsfoss.com/what-happened-to-ipv5/)
|
||||
[#]: author: (John Paul https://itsfoss.com/author/john/)
|
||||
|
||||
What Happened to IPv5? Why there is IPv4, IPv6 but no IPv5?
|
||||
======
|
||||
|
||||
If you have spent any amount of time in the world of the internet, you should have heard about the IPv4 and IPv6 protocols that our computers use every day.
|
||||
|
||||
One question that you might be asking is: Why there is no IPv5? Why IPv6 came after IPv4 and not IPv5? Was there ever a IPv5 and if yes, whatever happened to IPv5?
|
||||
|
||||
The answer is yes, there was an IPv5…sort of. Let me quickly explain a few things around it.
|
||||
|
||||
### The early history of the internet
|
||||
|
||||
![ARPA Logical Map in 1977 | Image courtesy: Wikipedia][1]
|
||||
|
||||
In the late 1960s, the US Department of Defense’s [Advanced Research Projects Agency][2] (ARPA) started a [project][3] to link computers across the country. The initial goal was to create a networked system of all of the ARPA-funded computers across the country.
|
||||
|
||||
Since this was the first time a network of this scale was put together, they were also creating the technology and hardware as they went. One of the first things they worked was an internet protocol (IP) named [Transmission Control Protocol][4] (TCP). This protocol “reliable, ordered, and error-checked delivery of a stream of octets (bytes) between applications running on hosts communicating via an IP network”. Basically, it made sure data got where it needed to go safely.
|
||||
|
||||
Originally, TCP was designed to be [“a host-level, end-to-end protocol and a packaging and routing protocol”][5]. However, they realized that they needed to split the protocol to make it more manageable. It was decided that IP would handle packaging and routing.
|
||||
|
||||
By this time TCP had gone through three versions, so the new protocol became known as IPv4.
|
||||
|
||||
### The birth of IPv5
|
||||
|
||||
IPv5 started life under a different name: Internet Stream Protocol (or ST). It was created to experiment with streaming voice and video [“by Apple, NeXT, and Sun Microsystems”][6].
|
||||
|
||||
This new protocol was capable of “transferring data packets on specific frequencies while maintaining communication”.
|
||||
|
||||
### So what happened to IPv5?
|
||||
|
||||
![][7]
|
||||
|
||||
IPv5 was never accepted as an official internet protocol. This was mainly due to the 32-bit limitation.
|
||||
|
||||
IPV5 used the same addressing system as IPv4. Each address was made up of four sets of numbers between 0 and 255. This limited the number of possible addresses to [4.3 billion][6].
|
||||
|
||||
In the early 1970s, that might have seemed like more than the world would ever need. However, the explosive growth of the Internet proved that idea wrong. In 2011, the world officially ran out of the IPv4 addresses.
|
||||
|
||||
In the 1990s, a new project was started to work on the next generation of internet protocol (IPng). This led to the 128-bit IPv6. An IPv6 address contains a [“series of eight 4-character hexadecimal numbers”][6] that can contain numbers from 0 to 9 and letters from A to F. Unlike IPv4, IPv6 had trillions of possible addresses, so we should be safe for a while.
|
||||
|
||||
Meanwhile, IPv5 laid the groundwork for the voice-over-IP technology that we use to communicate all over the world today. **So, I guess in some small way, you could say that IPv5 still survives to this day**.
|
||||
|
||||
I hope you liked this anecdote about internet history. You may read some other [trivia article about Linux and tech in general][8].
|
||||
|
||||
If you found this article interesting, please take a minute to share it on social media, Hacker News or [Reddit][9].
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/what-happened-to-ipv5/
|
||||
|
||||
作者:[John Paul][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/john/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/04/Arpa_internet.png?fit=800%2C573&ssl=1
|
||||
[2]: https://en.wikipedia.org/wiki/DARPA
|
||||
[3]: https://en.wikipedia.org/wiki/ARPANET
|
||||
[4]: https://en.wikipedia.org/wiki/Transmission_Control_Protocol
|
||||
[5]: https://fcw.com/articles/2006/07/31/what-ever-happened-to-ipv5.aspx
|
||||
[6]: https://www.lifewire.com/what-happened-to-ipv5-3971327
|
||||
[7]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/04/what-happened-to-ipv5.png?ssl=1
|
||||
[8]: https://itsfoss.com/category/story/
|
||||
[9]: https://reddit.com/r/linuxusersgroup
|
192
translated/tech/20200420 4 Git scripts I can-t live without.md
Normal file
192
translated/tech/20200420 4 Git scripts I can-t live without.md
Normal file
@ -0,0 +1,192 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (wxy)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (4 Git scripts I can't live without)
|
||||
[#]: via: (https://opensource.com/article/20/4/git-extras)
|
||||
[#]: author: (Vince Power https://opensource.com/users/vincepower)
|
||||
|
||||
4 个不可或缺的 Git 脚本
|
||||
======
|
||||
|
||||
> Git Extras 版本库包含了 60 多个脚本,它们是 Git 基本功能的补充。以下是如何安装、使用和贡献的方法。
|
||||
|
||||
![Person using a laptop][1]
|
||||
|
||||
2005 年,[Linus Torvalds][2] 创建了 [Git][3],以取代他之前用于维护 Linux 内核的专有的分布式源码控制管理解决方案。从那时起,Git 已经成为开源和云原生开发团队的主流版本控制解决方案。
|
||||
|
||||
但即使是像 Git 这样功能丰富的应用程序,也没有人们想要或需要的每个功能,所以人们会花大力气去创建这些功能。就 Git 而言,这个人就是 [TJ Holowaychuk][4]。他的 [Git Extras][5] 项目承载了 60 多个“附加功能”,这些功能扩展了 Git 的基本功能。
|
||||
|
||||
### 使用 Git 附加功能
|
||||
|
||||
下面介绍一下如何使用四种最受欢迎的 Git 附加功能。
|
||||
|
||||
#### git-ignore
|
||||
|
||||
`git ignore` 是一个方便的附加功能,它可以让你手动添加文件类型和注释到 `.git-ignore` 文件中,而不需要打开文本编辑器。它可以操作你的个人用户帐户的全局忽略文件和单独用于你正在工作的版本库的忽略文件。
|
||||
|
||||
在没有参数的情况下执行 `git ignore` 会先列出全局忽略文件,然后是本地的忽略文件。
|
||||
|
||||
```
|
||||
$ git ignore
|
||||
Global gitignore: /home/alice/.gitignore
|
||||
# Numerous always-ignore extensions
|
||||
*.diff
|
||||
*.err
|
||||
*.orig
|
||||
*.rej
|
||||
*.swo
|
||||
*.swp
|
||||
*.vi
|
||||
*~
|
||||
*.sass-cache
|
||||
|
||||
# OS or Editor folders
|
||||
Thumbs.db
|
||||
---------------------------------
|
||||
Local gitignore: .gitignore
|
||||
nbproject
|
||||
```
|
||||
|
||||
#### git-info
|
||||
|
||||
`git info` 可以检索你所需要的所有信息,以获取你正在使用的版本库的上下文信息。它包括远程 URL、远程分支、本地分支、配置信息和最后一次的提交信息。
|
||||
|
||||
```
|
||||
$ git info
|
||||
|
||||
## Remote URLs:
|
||||
|
||||
origin git@github.com:sampleAuthor/git-extras.git (fetch)
|
||||
origin git@github.com:sampleAuthor/git-extras.git (push)
|
||||
|
||||
## Remote Branches:
|
||||
|
||||
origin/HEAD -> origin/master
|
||||
origin/myBranch
|
||||
|
||||
## Local Branches:
|
||||
|
||||
myBranch
|
||||
* master
|
||||
|
||||
## Most Recent Commit:
|
||||
|
||||
commit e3952df2c172c6f3eb533d8d0b1a6c77250769a7
|
||||
Author: Sample Author <sampleAuthor@gmail.com>
|
||||
|
||||
Added git-info command.
|
||||
|
||||
Type ´git log´ for more commits, or ´git show <commit id>´ for full commit details.
|
||||
|
||||
## Configuration (.git/config):
|
||||
|
||||
color.diff=auto
|
||||
color.status=auto
|
||||
color.branch=auto
|
||||
user.name=Sample Author
|
||||
user.email=sampleAuthor@gmail.com
|
||||
core.repositoryformatversion=0
|
||||
core.filemode=true
|
||||
core.bare=false
|
||||
core.logallrefupdates=true
|
||||
core.ignorecase=true
|
||||
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
|
||||
remote.origin.url=git@github.com:mub/git-extras.git
|
||||
branch.master.remote=origin
|
||||
branch.master.merge=refs/heads/master
|
||||
```
|
||||
|
||||
#### git-mr 和 git-pr
|
||||
|
||||
这些附加功能的作用类似,工作方式也基本相同。
|
||||
|
||||
* `git mr` 检出来自 GitLab 的合并请求。
|
||||
* `git pr` 检出来自 GitHub 的拉取请求。
|
||||
|
||||
无论是哪种情况,你只需要合并请求号、拉取请求号或完整的 URL,它就会抓取远程引用,检出分支,并调整配置,这样 Git 就知道要替换哪个分支了。
|
||||
|
||||
```
|
||||
$ git mr 51
|
||||
From gitlab.com:owner/repository
|
||||
* [new ref] refs/merge-requests/51/head -> mr/51
|
||||
Switched to branch 'mr/51'
|
||||
```
|
||||
|
||||
#### git-release
|
||||
|
||||
通过将 `commit`、`tag` 和 `push` 合并到一个命令中,`git release` 可以节省大量的按键来执行这三个命令,而这三个命令往往是依次运行的。
|
||||
|
||||
要用特定的 `<tagname>` 和自定义消息提交:
|
||||
|
||||
```
|
||||
$ git release 0.1.0 -m <+ powerful feature added>
|
||||
```
|
||||
|
||||
#### 其他附加功能
|
||||
|
||||
这只是该版本库中 60 多个 Git 附加功能中的四个命令。要访问 Git Extras 中的全部命令,请查看该源代码库中的 [Commands.md][8] 文件,或者在安装 Git Extras 后运行以下命令。
|
||||
|
||||
```
|
||||
$ git extras --help
|
||||
```
|
||||
|
||||
### 安装 Git 附加功能
|
||||
|
||||
使用 Git 附加功能的主要前提是安装了 Git 的命令行版本。如果你打算从源码中构建,还需要有额外的工具(例如:`make`)。
|
||||
|
||||
如果你使用的是最新版本的 macOS,那么 Git 附加功能的安装最好使用 [Homebrew][9](和大多数开源工具一样)。
|
||||
|
||||
```
|
||||
$ brew install git-extras
|
||||
```
|
||||
|
||||
在 Linux 上,每个平台的原生包管理器中都有 Git Extras。有时,你需要启用一个额外的仓库,比如在 CentOS 上的 [EPEL][10],然后运行一条命令。
|
||||
|
||||
```
|
||||
$ sudo yum install git-extras
|
||||
```
|
||||
|
||||
其他 Linux 发行版、BSD 和其他平台的完整安装说明可以在该版本库的 [Installation.md][11] 文件中找到。
|
||||
|
||||
### 贡献
|
||||
|
||||
你是否你认为 Git 中有缺少的功能,并且已经构建了一个脚本来处理它?为什么不把它作为 Git Extras 发布版的一部分,与全世界分享呢?
|
||||
|
||||
要做到这一点,请将该功能贡献到 Git Extras 仓库中。更多具体细节请参见仓库中的 [CONTRIBUTING.md][12] 文件,但基本的操作方法很简单。
|
||||
|
||||
1. 创建一个处理该功能的 Bash 脚本。
|
||||
2. 创建一个基本的 man 文件,让大家知道如何使用它。
|
||||
3. 更新命令列表和补完脚本,让人们知道这个功能的存在。
|
||||
4. 运行完整性检查,确保你没有破坏任何东西。
|
||||
5. 为你的功能创建一个拉取请求。
|
||||
|
||||
向 Git Extras 贡献贡献,会让你的 Git 用户的生活更轻松一些。你可以在项目的 [README][13] 中了解更多。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/4/git-extras
|
||||
|
||||
作者:[Vince Power][a]
|
||||
选题:[lujun9972][b]
|
||||
译者:[wxy](https://github.com/wxy)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/vincepower
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/laptop_screen_desk_work_chat_text.png?itok=UXqIDRDD (Person using a laptop)
|
||||
[2]: https://en.wikipedia.org/wiki/Linus_Torvalds
|
||||
[3]: https://git-scm.com/
|
||||
[4]: https://github.com/tj
|
||||
[5]: https://github.com/tj/git-extras
|
||||
[6]: mailto:git@github.com
|
||||
[7]: mailto:sampleAuthor@gmail.com
|
||||
[8]: https://github.com/tj/git-extras/blob/master/Commands.md
|
||||
[9]: https://brew.sh/
|
||||
[10]: https://fedoraproject.org/wiki/EPEL
|
||||
[11]: https://github.com/tj/git-extras/blob/master/Installation.md
|
||||
[12]: https://github.com/tj/git-extras/blob/master/CONTRIBUTING.md
|
||||
[13]: https://github.com/tj/git-extras/blob/master/Readme.md
|
Loading…
Reference in New Issue
Block a user