mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-21 02:10:11 +08:00
Merge branch 'master' of https://github.com/LCTT/TranslateProject
This commit is contained in:
commit
f12d476dbb
@ -1,3 +1,4 @@
|
||||
翻译中 by Linux-pdz
|
||||
How to create desktop shortcut or launcher on Linux
|
||||
================================================================================
|
||||
If you have a program you use regularly on Linux desktop, you may want to create a "desktop shortcut", so you can launch the program by simply clicking on the shortcut. While most GUI programs automatically create their desktop shortcut during installation, some GUI programs or terminal applications may require you to set up associated shortcuts manually.
|
||||
@ -77,4 +78,4 @@ via: http://xmodulo.com/2013/11/create-desktop-shortcut-launcher-linux.html
|
||||
[1]:http://www.flickr.com/photos/xmodulo/10848506344/
|
||||
[2]:http://www.flickr.com/photos/xmodulo/10848418496/
|
||||
[3]:http://www.flickr.com/photos/xmodulo/10848506284/
|
||||
[4]:http://www.flickr.com/photos/xmodulo/10848922593/
|
||||
[4]:http://www.flickr.com/photos/xmodulo/10848922593/
|
||||
|
@ -1,43 +0,0 @@
|
||||
(translating by whatever1992)
|
||||
|
||||
Red Hat prepares for 64-bit ARM servers
|
||||
================================================================================
|
||||
> ARM processors could lead to server racks with thousands of nodes, the Red Hat ARM chief predicts
|
||||
|
||||
IDG News Service - Enterprise open-source software vendor Red Hat is keeping an eye on the development of 64-bit ARM processors for servers, building up expertise in case the nascent platform takes hold in the data center.
|
||||
|
||||
"You don't see us in the market today with commercial offerings, but what we are building a competency ahead of some of the 64-bit technology that is coming. So further down the line, if we do have a need to respond to the market, we will have the capability to do that," said Jon Masters, chief ARM architect at Red Hat. Masters spoke Friday at the USENIX LISA (Large Installation System Administration) conference in Washington, D.C.
|
||||
|
||||
The ARM processor represents a "sea change in computing," Masters said. While already the dominant architecture for smartphone and embedded computing devices, ARM processors could also play a role in the data center. Over the past year, servers based on ARM processors have started to show up in the server market. HP is already selling ARM-based servers with its Moonshot line.
|
||||
|
||||
For the data center, because of its low-power design, ARM could bring about an age of hyperscale computing, in which thousands of tiny compute nodes can be packed into a single server rack. "It is a fundamental difference in terms of the sheer scale of what we will be able to build in the near future," Masters said.
|
||||
|
||||
The ARM processors may not run at the speed of x86 processors, but they can offer most of the performance with a fraction of the energy usage, meaning more processors can be packed into a smaller space. "You can take the same technology that goes into your cell phone and make that part of a dense server design" Masters said.
|
||||
|
||||
Many jobs do not require the fastest processors available, he said. Instead the workloads can be spread across more processors. "It's about how much data I can move, not necessarily how much compute I can do," he said. Cloud computing and Web applications, for instance, would do equally well spread out across multiple servers as they would running on fewer, but faster servers.
|
||||
|
||||
ARM's design could also simplify data-center operations. ARM's system on a chip design can eliminate the need for managing many of the external components of servers. For instance, an ARM processor could offer fabric interconnectivity, reducing the need for external cables and top-of-the-rack switches.
|
||||
|
||||
"The days of having discrete cabling for every single blade are numbered," he said.
|
||||
|
||||
There is still a lot of work that needs to be done to bring about hyperscale computing, Masters said.
|
||||
|
||||
ARM licenses its architecture rather than selling processors as Intel does. As a result, there is a fair amount of variation among the different ARM processors from vendors. "There is a lot of gratuitous variation that we don't need to have," Masters said. This can be problematic for data centers that need uniform systems so they can be managed en masse.
|
||||
|
||||
[Linaro][1] is an industry group working to build core open-source software for the ARM platform and part of its mission has been to standardize ARM. Red Hat engineers play a major role in the Linaro Enterprise Group, or LEG, which has been working to standardize the software so users can get one version of Linux to run across ARM processors from multiple vendors. "Those are fundamental expectations in the enterprise space," Masters said.
|
||||
|
||||
"We do need to focus on how to make them fundamentally compatible so you can add value further up the stack," he said.
|
||||
|
||||
Another issue is the support of peripherals, which hasn't been standardized across 32-bit ARM processors. Masters said that LEG is looking into using the ACPI (Advanced Configuration and Power Interface) standard or UEFI (Unified Extensible Firmware Interface) for 64-bit ARM processors. Over time, ARM will offer an automated bus-like capability that will work like PCI buses offer on x86 machines.
|
||||
|
||||
Masters said that Red Hat has not made any announcements about when it would release a version of Red Hat Enterprise Linux for ARM, but he did note that the Fedora Project, the community Linux distribution that tests many of the applications that go into RHEL, now offers a distribution for ARM.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.computerworld.com/s/article/9243921/Red_Hat_prepares_for_64_bit_ARM_servers?taxonomyId=122
|
||||
|
||||
译者:[译者ID](https://github.com/译者ID) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.linaro.org/
|
@ -1,173 +0,0 @@
|
||||
NearTan占坑
|
||||
SBackup: A Simple Backup Solution For Your Linux Desktop
|
||||
================================================================================
|
||||
**SBackup**, Simple Backup, is an Open Source, easy to use backup solution intended for desktop use. It can backup any subset of files and folders. All configuration is accessable via Gnome interface. File and paths can be included and excluded directly or by regex, It supports local and as well as remote backups. Though it looks simple, it has many features to meet the advanced backup functionality.
|
||||
|
||||
### Features ###
|
||||
|
||||
SBackup will do the following things for you:
|
||||
|
||||
- It creates both compressed and uncompressed backups.
|
||||
- It can split uncompressed backups into multiple parts.
|
||||
- It support of multiple backup profiles. You can create and edit the profiles as per your requirement, but you can’t delete the default profile.
|
||||
- It has options such as logging, email notification and status icon presenting progress and notifications.
|
||||
- It supports scheduled backups and manual backups.
|
||||
- It can backup files either to local destinations (e.g. hard disk) or remote destinations (e.g. NAS over FTP).
|
||||
|
||||
### Install SBackup On Ubuntu, Linux Mint and Debian ###
|
||||
|
||||
SBackup is available in the default repositories of Ubuntu, Debian and Linux Mint. So just install it using command:
|
||||
|
||||
sudo apt-get install sbackup
|
||||
|
||||
### Launch SBackup ###
|
||||
|
||||
Open up SBackup either from Dash or Menu.
|
||||
|
||||

|
||||
|
||||
It will look like as shown below.
|
||||
|
||||

|
||||
|
||||
### SBackup Profiles ###
|
||||
|
||||
Initially SBackup won’t have any user profiles. Only “default profile” will be available. Be mindful that you can’t delete the default profile. To create a new profile, go to Tools -> Profile Manager. You will have a following like window.
|
||||
|
||||

|
||||
|
||||
Click Add to create a new profile, let me name the profile as “sk”.
|
||||
|
||||

|
||||
|
||||
Now a new profile has been created. If you want to use your custom profile, just select the profile and click Edit.
|
||||
|
||||

|
||||
|
||||
Now you may see that SBackup profile has been switched to “sk” profile.
|
||||
|
||||

|
||||
|
||||
However you can use default profile and edit it as per your requirements if you wish.
|
||||
|
||||
**Important Note**: If you launch it from a normal user you can’t schedule the backup. To schedule your backup you must run SBackup as root user. As see you in the above screenshots, the schedule tab is greyed out, because i launched it from a normal user.
|
||||
|
||||
In this how-to tutorial, i am going to use **default profile** with root user privileges.
|
||||
|
||||
Open up your Terminal and run the following command to open SBackup with root user privileges.
|
||||
|
||||
sudo sbackup-config-gtk
|
||||
|
||||
The above command will open SBackup with default profile with administrative mode.
|
||||
|
||||

|
||||
|
||||
### General ###
|
||||
|
||||
In General section you can define how often do you want to do a full backup. The default option is 7 days. By default SBackup will do full backup every 7 days. Then you can define the compression format for your backup file.
|
||||
|
||||

|
||||
|
||||
### Include ###
|
||||
|
||||
This tab pretty self-explanatory. You can include the files/folders that you want to backup using SBackup. Here you can either select individual files or entire folder to backup. I deleted all directories in the include section and added single directory called “Resume”.
|
||||
|
||||

|
||||
|
||||
### Exclude ###
|
||||
|
||||
Just like Include tab, we can define the files/folders path to exclude from being backed-up by SBackup. Just select the path of the files/folders that needs to be excluded from backup. By default SBackup will exclude the /media, /var/run/, /var/cache/, /var/spool/ and /vat/tmp/ directories.
|
||||
|
||||

|
||||
|
||||
Further more, you can add the file types that you want to exclude from backup such mp3 or avi etc. By default SBackup exclude files such as mp3, avi, mpeg, mkv, ogg and iso from backup. If you want to include them in your backup, just select and click remove to add them in your backup. Also if you want to add some other file types in the exclude list, just add them by clicking on the add button.
|
||||
|
||||

|
||||
|
||||
By default SBackup won’t backup the folders .gvfs, .thumbnails, .Trash and .cache etc.
|
||||
|
||||

|
||||
|
||||
Also you can omit the files/folders of certain size from backup. Here i excluded the files/folders which are bigger than 100MB in size.
|
||||
|
||||

|
||||
|
||||
### Destination ###
|
||||
|
||||
This is the path where you want to store your backup file. As i mentioned above, you can backup files/folders either in your local hard drive or to an external destination such as FTP, NAS etc. Here i am going to save my backups in /home/sk/My Backup directory.
|
||||
|
||||

|
||||
|
||||
**Note:** Make sure that destination has enough free space to store the backup.
|
||||
|
||||
### Schedule ###
|
||||
|
||||
In this section you can schedule the backups at a particular time. Click on the **Simple** radio button and select your schedule type such as hourly, daily, weekly and monthly.
|
||||
|
||||

|
||||
|
||||
If you’re good at command line crontab, select custom and define the cron job. If you select the daily schedule type, a cron job will be created in the **/etc/cron.daily/** location.
|
||||
|
||||
sudo ls -l /etc/cron.daily/sbackup
|
||||
|
||||
Sample output:
|
||||
|
||||
lrwxrwxrwx 1 root root 33 Nov 8 15:34 /etc/cron.daily/sbackup -> /usr/share/sbackup/sbackup-launch
|
||||
|
||||
### Purging ###
|
||||
|
||||
This section gives you the option to delete the backup files after a particular period. By default, your backup files will be deleted after 30 days.
|
||||
|
||||

|
||||
|
||||
### Report ###
|
||||
|
||||
Report is the final section. From here you can define to receive the mail notification directly in your inbox after the backups got finished. Enter your mail id, smtp server address, email username and password and click Test settings. Be mindful that, before test the mail settings save the configuration by clicking on the Save Configuration button on the Tool bar.
|
||||
|
||||

|
||||
|
||||
You’ll see a message “Test Successful” after testing your mail settings.
|
||||
|
||||
### Start Backup ###
|
||||
|
||||
If you want to start backup immediately, click **Make Backup now button** on the SBackup tool bar.
|
||||
|
||||

|
||||
|
||||
A new window will open. Click Yes to create backup.
|
||||
|
||||

|
||||
|
||||
Now you can see that a backup process will be started in the background. You can monitor the progress of the backup by means of the status indicator displayed in the notification area.
|
||||
|
||||
After completing the backup, close SBackup and check for your backup in the destination directory. In my case my destination directory is /home/sk/My Backup.
|
||||
|
||||

|
||||
|
||||
### Restore backup ###
|
||||
|
||||
From your Terminal run command:
|
||||
|
||||
sudo sbackup-restore-gtk
|
||||
|
||||
In the SBackup restoration window, select the date to get the list of the available backups and select the any one of the available snapshots. Click on the any one of the files to restore on the Restoration management pane. Once you done, click **restore** to save them in the default location or click **restore as** to save the files in a custom location.
|
||||
|
||||

|
||||
|
||||
Now the data will be restored from the selected backup. That’s it.
|
||||
|
||||
### Sources: ###
|
||||
|
||||
- [https://launchpad.net/sbackup][1]
|
||||
- [http://sourceforge.net/projects/sbackup/][2]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.unixmen.com/linux-desktop-backup-made-easy-sbackup/
|
||||
|
||||
译者:[译者ID](https://github.com/译者ID) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:https://launchpad.net/sbackup
|
||||
[2]:http://sourceforge.net/projects/sbackup/
|
@ -1,39 +0,0 @@
|
||||
Making Linux More Accessible
|
||||
================================================================================
|
||||
A startling fact is that there are in excess of a billion people who have some type of disability. That represents approximately 15% of the world's population with a physical, sensory or mental limitation that interferes with their ability to move, see, hear or learn. 350 million people in the world are partially sighted or blind. The faster computer technology evolves, the more excluded these individuals would become without development in computer software that seeks to address their needs.
|
||||
|
||||
Accessibility is the degree to which products, devices, services, or environments are available to as many people as possible whatever their circumstances. Accessibility can be viewed as the ability to access and benefit from a system or entity. Accessibility is paramount. Social inclusion is not an act of charity but a fundamental human right.
|
||||
|
||||
We have witnessed Linux software and distributions that have made strides to help make everyone socially inclusive. For example, the GNOME Accessibility Project develops open source accessibility solutions for graphical user interfaces. Ubuntu has an Accessibility Team that aims to make Ubuntu usable by a broad a spectrum of people as possible. Special mention should also go to the Vinux Project, which is a Ubuntu derived distribution optimised for the needs of blind and partially sighted users.
|
||||
|
||||
There are also lots of individual software applications that offer different accessibility features. This article seeks to identify some of the finest open source software that is available that helps to enable individuals make full use of computer-based technology whatever their physical or sensory abilities.
|
||||
|
||||
So let's explore the 8 universal access tools at hand. For each application we have compiled its own portal page, a full description with an in-depth analysis of its features, a screenshot, together with links to relevant resources and reviews.
|
||||
|
||||
### Universal Access ###
|
||||
|
||||
- [Easystroke][1] Gesture recognition program
|
||||
- [Simon][2] Flexible speech recognition software
|
||||
- [Orca Screen Reader][3] Scriptable screen reader
|
||||
- [Julius][4] Two-pass large vocabulary continuous speech recognition engine
|
||||
- [Florence Virtual Keyboard][5] Extensible scalable virtual keyboard
|
||||
- [Caribou][6] Configurable on screen keyboard with scanning mode
|
||||
- [Dasher][7] Graphical predictive text input system
|
||||
- [xvkbd][8] Virtual (graphical) keyboard program
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.linuxlinks.com/article/20131109042823957/UniversalAccess.html
|
||||
|
||||
译者:[译者ID](https://github.com/译者ID) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://sourceforge.net/apps/trac/easystroke/
|
||||
[2]:http://simon-listens.org/
|
||||
[3]:https://wiki.gnome.org/Orca
|
||||
[4]:http://julius.sourceforge.jp/
|
||||
[5]:http://florence.sourceforge.net/english.html
|
||||
[6]:https://wiki.gnome.org/Caribou
|
||||
[7]:http://www.inference.phy.cam.ac.uk/dasher/
|
||||
[8]:http://homepage3.nifty.com/tsato/xvkbd/
|
@ -1,136 +0,0 @@
|
||||
Translating----------------geekpi
|
||||
|
||||
21 The Linux Kernel: Configuring the Kernel Part 17
|
||||
================================================================================
|
||||

|
||||
|
||||
Aloha! This next article will cover various drivers.
|
||||
|
||||
First, the "virtio console" is a virtual console that is used with hypervisors.
|
||||
|
||||
The "IPMI top-level message handler" is a message manager for the IPMI system. IPMI stands for Intelligent Platform Management Interface. IPMI is an interface for managing the system via network without using a shell.
|
||||
|
||||
"/dev/nvram support" permits the system to read and write memory in the real time clock's memory. Generally, this feature is used for saving data during a power loss.
|
||||
|
||||
The next driver supports the Siemens R3964 packet protocol (Siemens R3964 line discipline). This is a device-to-device protocol.
|
||||
|
||||
Now, we can move on to PCMCIA character devices. However, most of the drivers here are vendor/device specific.
|
||||
|
||||
The RAW driver allows block devices to be bound to the device files /dev/raw/rawN (RAW driver (/dev/raw/rawN)). The advantage to this is efficient zero-copy. However, most software will still prefer to access the storage through /dev/sd** or /dev/hd**.
|
||||
|
||||
Next, the maximum number of RAW devices can be supported is set.
|
||||
|
||||
The following driver makes the device file /dev/hpet (HPET - High Precision Event Timer).
|
||||
|
||||
NOTE: Many of you may be wondering why enabling these device file matter. Well, these device files serve as an interface between the software and hardware.
|
||||
|
||||
The HPET timers can be mapped with this driver (Allow mmap of HPET). Mapping is the process of making a list of address in memory of devices and files. The files can then be found faster by getting the address from the memory and then commanding the hard-drive to get the data from the address.
|
||||
|
||||
|
||||
The "Hangcheck timer" is used to detect whether of not the system has locked-up.
|
||||
This timer watches for locked-up processes. As soon as a process freezes, a timer starts. After the timer goes off, if the process has not restarted or closed, then the timer will force the process to close.
|
||||
|
||||
Linus Torvalds Quote: Portability is for people who cannot write new programs.
|
||||
|
||||
The TPM security chip that uses Trusted Computing Group's specification will need this driver (TPM Hardware Support).
|
||||
|
||||
Now, we can move on to I2C devices. I2C stands for Inter-Integrated Circuit and is spoken as "eye two see". However, some people say "eye squared see". I2C is a serial bus standard.
|
||||
|
||||
Some old software used I2C adapters as class devices, but software now does not do that (Enable compatibility bits for old user-space). So, this driver will offer backwards compatibility for older software.
|
||||
|
||||
Next, the I2C device files can be made (I2C device interface).
|
||||
|
||||
I2C can support multiplexing with this driver (I2C bus multiplexing support).
|
||||
|
||||
I2C can support GPIO-controlled multiplexing with this driver (GPIO-based I2C multiplexer).
|
||||
|
||||
Various tests can be performed on I2C and SMBus with this driver for developers (I2C/SMBus Test Stub).
|
||||
|
||||
The I2C system will produce debugging messages with this feature enabled (I2C Core debugging messages).
|
||||
|
||||
The next driver produces additional I2C debugging messages (I2C Algorithm debugging messages).
|
||||
|
||||
Linus Torvalds Quote: The main reason there are no raw devices [in Linux] is that I personally think that raw devices are a stupid idea.
|
||||
|
||||
The following driver will cause the I2C drivers to produce debugging messages (I2C Bus debugging messages).
|
||||
|
||||
Next, we have Serial Peripheral Interface support (SPI support). SPI is a synchronous serial protocol used on SPI buses.
|
||||
|
||||
After that, there is a driver for High speed synchronous Serial Interface support (HSI support). HSI is a synchronous serial protocol.
|
||||
|
||||
PPS can also be supported by the Linux kernel (PPS support).
|
||||
|
||||
The "IP-over-InfiniBand" driver allows IP packets to be transported over InfiniBand.
|
||||
|
||||
After that, there is a debugging driver for IP-over-InfiniBand (IP-over-InfiniBand debugging).
|
||||
|
||||
SCSI's RDMA protocol can also travel over InfiniBand (InfiniBand SCSI RDMA Protocol).
|
||||
|
||||
There is also an extension for the iSCSI protocol to transmit over InfiniBand (iSCSI Extensions for RDMA (iSER)).
|
||||
|
||||
Sometimes, errors occur in the core system that the whole system must know (EDAC (Error Detection And Correction) reporting). This driver sends the core errors to the system. Generally, such low-level errors are reported in the processor and then seen by this driver to let other system processes know about or handle the error.
|
||||
|
||||
This driver provides legacy support for EDAC to use older versions of sysfs (EDAC legacy sysfs).
|
||||
|
||||
EDAC can be set to send debugging information to the logging system of Linux (Debugging).
|
||||
|
||||
Linus Torvalds Quote: Nobody actually creates perfect code the first time around, except me.
|
||||
|
||||
The Machine Check Exceptions (MCEs) are converted to a readable form via this driver (Decode MCEs in human-readable form (only on AMD for now)).
|
||||
MCEs are hardware errors detected by the CPU. MCEs usually trigger kernel panics.
|
||||
|
||||
The decoding process for MCE to a readable form can be injected to test error handling (Simple MCE injection interface over /sysfs).
|
||||
|
||||
The next driver allows errors to be detected in memory and then corrected (Main Memory EDAC (Error Detection And Correction) reporting).
|
||||
|
||||
Next, there are many drivers that detect and correct errors on specific hardware sets.
|
||||
|
||||
Linus Torvalds Quote: Theory and practice sometimes clash. And when that happens, theory loses. Every single time.
|
||||
|
||||
Now, we can move on to the "Real Time Clock". This is commonly abbreviated "RTC". The RTC keeps track of time.
|
||||
|
||||

|
||||
|
||||
The next setting allows us to make the Linux system use the time from the RTC as the time on the "wall clock" (Set system time from RTC on startup and resume). The wall clock is the clock on the desktop or the time seen using the "date" command.
|
||||
|
||||
Alternately, the wall clock can get the time from an NTP server and then sync with the RTC (Set the RTC time based on NTP synchronization).
|
||||
|
||||
Some systems have more than one RTC, so the user must set which is the default (RTC used to set the system time).
|
||||
It is best to make the first one (/dev/rtc0) the primary clock.
|
||||
|
||||
Debugging abilities can be set for the RTC system (RTC debug support).
|
||||
|
||||
The RTC can use various interfaces for giving the operating system the current time. Using sysfs will require this driver (/sys/class/rtc/rtcN (sysfs)) while using proc will require this driver (/proc/driver/rtc (procfs for rtcN)). Special RTC character devices can be made and used (/dev/rtcN (character devices)). The shell command "hwclock" uses /dev/rtc, so the RTC character devices are needed.
|
||||
|
||||
The next driver allows interrupts of the RTC to be emulated on the /dev/ interface (RTC UIE emulation on dev interface). This driver reads the clock time and allows the new time to be retrieved from /dev/.
|
||||
|
||||
The RTC system can be tested with the test driver (Test driver/device).
|
||||
|
||||
Next, we will discuss the Direct Memory Access system.
|
||||
DMA is the process of hardware accessing the memory independently of the processor. DMA increases system performance because the processor will have less to do if the hardware is performing more tasks for itself. Otherwise, the hardware would be waiting for the processor to complete the task.
|
||||
|
||||
The debugging engine is for debugging the DMA system (DMA Engine debugging).
|
||||
|
||||
Next, there are many vendor/device specific drivers for DMA support.
|
||||
|
||||
Some DMA controllers support big endian reading and writing with this driver (Use big endian I/O register access).
|
||||
|
||||
Big endian refers to the arrangement of the binary code. The number system used in English speaking countries places the largest end of the number on the left. For example, in the number 17, the most left numbers place is the tens place which is larger than the ones place. In big endian, each byte is arranged with the largest portion on the left. A byte is eight bits. Example: 10110100. Each place has a value of 128, 64, 32, 16, 8, 4, 2, and 1 respectively. So the byte mentioned converts to the decimal number 180.
|
||||
|
||||
The DMA system can use the network to reduce CPU usage (Network: TCP receive copy offload).
|
||||
|
||||
The "DMA Test Client" is used for testing the DMA system.
|
||||
|
||||
In the next article, we will discuss the display/video drivers. Mahalo!
|
||||
|
||||
REFERENCE: The quotes from Linus Torvalds came from this site: [http://en.wikiquote.org/wiki/Linus_Torvalds][1]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.linux.org/threads/the-linux-kernel-configuring-the-kernel-part-17.4875/
|
||||
|
||||
译者:[译者ID](https://github.com/译者ID) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://en.wikiquote.org/wiki/Linus_Torvalds
|
@ -1,3 +1,4 @@
|
||||
翻译中 by Linux-pdz
|
||||
Ubuntu vs. openSUSE: Weighing different styles of corporate control
|
||||
================================================================================
|
||||
*Ubuntu and openSUSE approach their Linux distros in much different ways. Which do you prefer?*
|
||||
@ -28,4 +29,4 @@ via: http://www.networkworld.com/community/node/84250
|
||||
|
||||
译者:[译者ID](https://github.com/译者ID) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
40
translated/Making Linux More Accessible.md
Normal file
40
translated/Making Linux More Accessible.md
Normal file
@ -0,0 +1,40 @@
|
||||
让Linux更友好
|
||||
================================================================================
|
||||
一个令人吃惊的事实是,多于十亿人多多少少有着某种程度的残疾。就是说全球大约15%的人在生理上、感知上、心智上有缺陷,导致他们难以活动、看和听,以及学习。世界上3.5亿人有不同程度的视觉障碍。计算机技术发展地越快,这些人就越会被疏远,除非有计算机软件的开发可以满足他们的需求。
|
||||
|
||||
可用性是表示一个产品、设备、服务或者环境在不考虑具体细节的情况下能被多少人使用的程度。可用性可以被看作接触和利用一个系统或者实体的能力。可用性至关重要。社会和谐不是一个慈善行动,而是人类基本的权利。
|
||||
|
||||
我们见证了Linux软件和发行版本在使每个人融入社会方面做的突出贡献。举个例子来说,GNOME Accessibility Project 为图形界面用户开发了开源的可用性解决方案。Ubuntu有一个可用性团队致力于使Ubuntu能被更广范围的人使用。不得不提的是Vinux Project,一个基于Ubuntu的发行版本,针对失明和视力有障碍的用户进行了优化。
|
||||
|
||||
也有很多单独的应用软件提供了不同的可用性功能。这篇文章试图找出一些顶尖的开源软件,它们能帮助人们充分利用计算机技术,不论他们的生理和知觉功能如何。
|
||||
|
||||
让我们了解一下手边的8个通用辅助工具。我们为每个应用编写了它字节的入口页面,完整地、深入地分析了它们的功能,包含截屏和相关资源链接。
|
||||
|
||||
|
||||
### 通用辅助 ###
|
||||
|
||||
- [Easystroke][1] Gesture recognition program
|
||||
- [Simon][2] Flexible speech recognition software
|
||||
- [Orca Screen Reader][3] Scriptable screen reader
|
||||
- [Julius][4] Two-pass large vocabulary continuous speech recognition engine
|
||||
- [Florence Virtual Keyboard][5] Extensible scalable virtual keyboard
|
||||
- [Caribou][6] Configurable on screen keyboard with scanning mode
|
||||
- [Dasher][7] Graphical predictive text input system
|
||||
- [xvkbd][8] Virtual (graphical) keyboard program
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.linuxlinks.com/article/20131109042823957/UniversalAccess.html
|
||||
|
||||
译者:[boredivan](https://github.com/boredivan) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://sourceforge.net/apps/trac/easystroke/
|
||||
[2]:http://simon-listens.org/
|
||||
[3]:https://wiki.gnome.org/Orca
|
||||
[4]:http://julius.sourceforge.jp/
|
||||
[5]:http://florence.sourceforge.net/english.html
|
||||
[6]:https://wiki.gnome.org/Caribou
|
||||
[7]:http://www.inference.phy.cam.ac.uk/dasher/
|
||||
[8]:http://homepage3.nifty.com/tsato/xvkbd/
|
42
translated/Red Hat prepares for 64-bit ARM servers.md
Normal file
42
translated/Red Hat prepares for 64-bit ARM servers.md
Normal file
@ -0,0 +1,42 @@
|
||||
Red Hat 准备64位ARM服务器
|
||||
================================================================================
|
||||
> ARM处理器可能带来具有成千上万的节点的服务器机架,Red Hat的ARM首席预测
|
||||
|
||||
IDG新闻服务 - 企业开源软件供应商Red Hat公司正在密切关注服务器的64位ARM处理器的发展,为保持在数据中心的新生平台建立专业体系。
|
||||
|
||||
“你们在当今的商业产品市场看不到我们,但我们已经建立了超越如今一些64位技术的能力。所以接下来,如果我们有一个需要应对的市场,我们将有能力应对,”Red Hat首席ARM设计师Jon Masters说。这是Masters周五在华盛顿特区举行的USENIX LISA(大型安装系统管理)会议上提出的。
|
||||
|
||||
ARM处理器代表了“计算上翻天覆地的变化,”Masters说。虽然已经在智能手机和嵌入式计算设备占据主导地位,ARM处理器架构还可以在数据中心发挥作用。在过去的一年中,基于ARM处理器的服务器已经开始出现在服务器市场。惠普已经开始销售基于ARM架构的Moonshot系列服务器。
|
||||
|
||||
对于数据中心,ARM可能会带来超大规模计算时代因其低功耗设计,这样数千个微型计算节点可以打包成一个服务器机架。“我们在不久的将来能够建立起完全区别于现今的规模。”Masters说。
|
||||
|
||||
ARM处理器可能无法以x86处理器的速度运行,但它们可以提供大部分的性能而只消耗一小部分使用量,这意味着在一个较小的空间可以打包更多的处理器。“你可以用你手机中相同的技术,作为高密度服务器设计的一部分”Masters说。
|
||||
|
||||
他说,许多工作并不需要最快的处理器。相反,工作负载可以分布在更多的处理器上。“这和我能移动多少数据有关系,并不一定和我能做多少计算有关,”他说。例如,云计算和Web应用程序运行在多个服务器上,和运行在较少但速度更快的服务器上的表现会同样出色。
|
||||
|
||||
ARM的设计也可以简化数据中心操作。ARM系统上芯片设计可以解决管理许多服务器的外部元件的需要。例如,ARM处理器可以提供构造的互联互通,减少外部电缆和顶级机架交换机的需要。
|
||||
|
||||
“每一个刀片都具有离散布线已经指日可待了, ”他说。
|
||||
|
||||
超大规模计算还需要做大量的工作,Masters说。
|
||||
|
||||
ARM授权架构而和英特尔卖处理器不一样。其结果是,从不同供应商提供的不同的ARM处理器有相当程度的变化。“有很多我们不需要的,不必要的变化,”Masters说。 ”这可能成为需要统一系统来管理集体的数据中心的一个问题。
|
||||
|
||||
[Linaro][1]是一个致力于为ARM平台和部分已经标准化ARM任务开发核心开源软件的产业群。Red Hat的工程师发挥了重要作用,Linaro企业集团,或称为LEG,一直在努力规范软件,让用户可以得到一个能运行在不同供应商提供的ARM处理器的Linux版本。”这些都是在企业领域的基本期望,”Masters说。
|
||||
|
||||
“我们需要把重心放在如何使它们从根本上兼容,这样你可以进一步增加堆栈的值,”他说。
|
||||
|
||||
另一个问题是还没标准化的32位ARM处理器被的外部设备支持。Masters说,LEG正在考虑使用64位ARM处理器的ACPI(高级配置和电源接口)标准或UEFI(统一可扩展固件接口)。随着时间的推移,ARM将提供一个自动化类总线能力,比如将提供支持x86的机器的PCI总线。
|
||||
|
||||
Masters说,Red Hat还没有发布任何关于什么时候会发布一个ARM架构的Red Hat企业Linux版本的通知,但他明确指出,测试了许多RHEL应用程序的社区Linux发行版Fedora项目,现在已经为ARM提供了一个分布。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.computerworld.com/s/article/9243921/Red_Hat_prepares_for_64_bit_ARM_servers?taxonomyId=122
|
||||
|
||||
译者:[whatever1992](https://github.com/whatever1992) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.linaro.org/
|
||||
|
@ -0,0 +1,174 @@
|
||||
|
||||
SBackup: 在 linux 下的一个简单的备份软件
|
||||
================================================================================
|
||||
|
||||
**SBackup** 是一个开源易用的简单备份软件。它可以备份任意文件或者文件夹的一部分。所有的配置文件可以通过 Gnome 界面进行访问。文件和路径可以直接通过正则表达式进行添加和排除。它支持本地备份和远程备份。虽然它看起来简单,但是它有着许多常见的高级备份功能。
|
||||
|
||||
### 特点 ###
|
||||
|
||||
SBackup 可以完成以下工作
|
||||
|
||||
- 可以创建压缩和未压缩的备份
|
||||
- 可以把未压缩的备份分割成多份文件
|
||||
- 支持多份备份配置。每个人都可以根据自己的需求创建并修改自己的配置文件,但是不能删除默认配置文件
|
||||
- 有多种选项,如日志、邮件通知、以状态图标的形式展现和提醒
|
||||
- 支持计划任务备份和手动备份
|
||||
- 可以备份到本地(如硬盘),也可以备份到远程(如通过 FTP 访问 NAS)
|
||||
|
||||
### 在 Ubuntu、Linux Mint 和 Debian 上安装 SBackup ###
|
||||
|
||||
SBackup 可在 Ubuntu、Linux Mint 和 Debian 的默认仓库中获得,所以只要运行以下命令即可安装
|
||||
|
||||
sudo apt-get install sbackup
|
||||
|
||||
### 运行 SBackup ###
|
||||
|
||||
通过 Dash 或者 Menu 打开 SBackup
|
||||
|
||||

|
||||
|
||||
将会看到如下界面
|
||||
|
||||

|
||||
|
||||
### SBackup 配置 ###
|
||||
|
||||
最初的 SBackup 没有任何用户自定义的配置文件,只有默认的配置文件。需要注意的是,用户不能删除默认的配置文件。若要创建一个新的配置文件,点击 Tools -> Profile Manager,将看到如下窗口
|
||||
|
||||

|
||||
|
||||
单击 Add 来创建新配置文件,例子的文件用“sk”来命名
|
||||
|
||||

|
||||
|
||||
现在已经创建了新的配置文件。若要设置配置,先选择配置文件,再单击 Edit
|
||||
|
||||

|
||||
|
||||
现在看到 SBackup 的配置文件已经被切换到“sk”
|
||||
|
||||

|
||||
|
||||
当然,也可以根据不同人的需求来修改默认配置文件
|
||||
|
||||
**注意事项**:如果你用普通用户运行 SBackup,计划任务备份不能生效,你需要用 root 用户来运行。如上图所示,因为我是以普通用户运行 Sbackup,所以 Schedule 选项是灰色不可选中状态。
|
||||
|
||||
在本教程中,我将以 root 权限运行 SBackup,并且使用的是**默认配置**
|
||||
|
||||
打开终端,运行以下命令来以 root 权限运行 SBackup
|
||||
|
||||
sudo sbackup-config-gtk
|
||||
|
||||
上面的命令将以 root 权限打开默认配置的 SBackup
|
||||
|
||||

|
||||
|
||||
### General ###
|
||||
|
||||
在 General 选项内,你可以选择多久进行一次完整备份,默认是7天。每7天 SBackup 将会进行一次完整的备份。你也可以选择备份的压缩格式。
|
||||
|
||||

|
||||
|
||||
### Include ###
|
||||
|
||||
这个选项不需要解释太多,你可以添加 SBackup 要备份的文件或目录。这里可以选择备份单独的文件或者完整的目录,我删除了所有的目录仅仅保留了“Resume”
|
||||
|
||||

|
||||
|
||||
### Exclude ###
|
||||
|
||||
如同 Include 选项,我们可以选择备份时排除的文档和目录,只需要选择要排除的文档和目录的路径即可。在默认配置下,/media, /var/run/, /var/cache/, /var/spool/ 和 /vat/tmp/ 目录均被排除
|
||||
|
||||

|
||||
|
||||
更进一步的是,你可以增加备份时排除文件的类型,像 mp3 和 avi 等等。在默认配置下,mp3, avi, mpeg, mkv, ogg 和 iso 是被排除不被备份的。如果你想备份这些文件,只要选中然后点击 remove。当然,如果要排除其他类型的文件,只需要点击 add 然后增加。
|
||||
|
||||

|
||||
|
||||
在默认配置下,SBackup 不会备份.gvfs, .thumbnails, .Trash 和 .cache 这些文件夹
|
||||
|
||||

|
||||
|
||||
同时你也可以在备份时根据文件大小来排除某些文档和文件夹,这里我排除了体积超过100MB 的文档和文件夹。
|
||||
|
||||

|
||||
|
||||
### Destination ###
|
||||
|
||||
在这里你可以选择备份存放的路径,正如我之前提到的,你可以把备份的文档或文件夹存放在硬盘或者远程的 FTP 或 NAS。这里我将把备份保存在 /home/sk/My Backup 目录下。
|
||||
|
||||

|
||||
|
||||
**提示:** 在备份前确认目录有足够的空间保存备份文件
|
||||
|
||||
### Schedule ###
|
||||
|
||||
在这部分,你可以计划具体的备份时间。点击 **Simple** 选项,可以按小时、每日、星期、月来设置你的计划备份时间。
|
||||
|
||||

|
||||
|
||||
如果你擅长使用命令行来计划任务,则可以使用 cron 来操作。当你开启每日备份计划时,cron 命令在 **/etc/cron.daily/** 目录中创建计划文件
|
||||
|
||||
sudo ls -l /etc/cron.daily/sbackup
|
||||
|
||||
示例的输出显示
|
||||
|
||||
lrwxrwxrwx 1 root root 33 Nov 8 15:34 /etc/cron.daily/sbackup -> /usr/share/sbackup/sbackup-launch
|
||||
|
||||
### Purging ###
|
||||
|
||||
在这部分内,可以删除超过一定时间的备份文件。在默认配置下,超过30天的备份文件将被删除。
|
||||
|
||||

|
||||
|
||||
### Report ###
|
||||
|
||||
Report 是最后一个选项卡,在这里你可以设置接收备份完成通知的邮箱。输入你的邮箱ID、SMTP服务地址、邮箱用户名、密码后,点击 Test mail settings。需要留意的是,在保存设置前要先测试邮件功能。
|
||||
|
||||

|
||||
|
||||
你将在完成测试邮箱后看到 “Test Successful” 字样。
|
||||
|
||||
### 开始备份 ###
|
||||
|
||||
点击 SBackup 工具栏上的 **Make Backup now button** 按钮立即开始备份。
|
||||
|
||||

|
||||
|
||||
弹出一个窗口,点击 Yes 开始创建备份文件。
|
||||
|
||||

|
||||
|
||||
现在备份的进程已经在后台开始运行,你可以通过在通知栏上的状态显示来监视备份的进程。(这句话不太确定)
|
||||
|
||||
完成备份之后,关闭 SBackup ,并且确认备份文件保存在指定的目录。例子中我保存的目录是/home/sk/My Backup。
|
||||
|
||||

|
||||
|
||||
### 恢复文件 ###
|
||||
|
||||
在终端中运行命令
|
||||
|
||||
sudo sbackup-restore-gtk
|
||||
|
||||
在 SBackup 的恢复窗口,选择可用的备份日期和快照,在 Restoration Management 面板中选择任意一个要恢复的文件,单击 **restore** 保存到默认位置或者单击 **restore as** 保存到指定的位置。
|
||||
|
||||

|
||||
|
||||
现在文件已经从备份中恢复,就这么简单。
|
||||
|
||||
### 来源: ###
|
||||
|
||||
- [https://launchpad.net/sbackup][1]
|
||||
- [http://sourceforge.net/projects/sbackup/][2]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.unixmen.com/linux-desktop-backup-made-easy-sbackup/
|
||||
|
||||
译者:[NearTan](https://github.com/NearTan) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:https://launchpad.net/sbackup
|
||||
[2]:http://sourceforge.net/projects/sbackup/
|
@ -0,0 +1,129 @@
|
||||
戴文的Linux内核专题:21 配置内核 (17)
|
||||
================================================================================
|
||||

|
||||
|
||||
你好!这篇文章会覆盖不同的驱动。
|
||||
|
||||
首先"virtio console"是一种用于hypervisors的虚拟控制台驱动。
|
||||
|
||||
"IPMI top-level message handler"是用于IPMI系统的消息管理器。IPMI代表的是"Intelligent Platform Management Interface"(智能平台管理系统)。IPMI是一种不需要shell通过网络管理系统的接口。
|
||||
|
||||
"/dev/nvram support"允许系统读取和写入实时时钟的内存。通常上,这个特性用于在掉电时保存数据。
|
||||
|
||||
下面一个驱动支持Siemens R3964包驱动(Siemens R3964 line discipline)。这个是设备对设备协议
|
||||
|
||||
现在,我们可以进入PCMCIA字符设备驱动。然而,大多数这里的驱动是供货商/设备特定的。
|
||||
|
||||
原始块设备驱动允许块设备绑定到设备文件上/dev/raw/rawN(RAW driver (/dev/raw/rawN))。这么做的好处是高效的零拷贝。然而,大多数软件更偏好通过/dev/sd** 或者 /dev/hd**访问存储设备。
|
||||
|
||||
下面,可以设置支持的原始设备的最大数量。
|
||||
|
||||
下面的驱动可以生成设备文件/dev/hpet (HPET - High Precision Event Timer)。
|
||||
|
||||
注意:你们中很多人可能会想知道为什么要启用这些设备文件问题。好的,这些设备文件充当了一个软件和硬件之间的接口。
|
||||
|
||||
通过这个驱动可以映射HPET驱动(Allow mmap of HPET)。映射是一个生成设备和文件在内存中的地址列表。文件接着可以通过内存地址更快地找到并且接着指挥硬盘从地址中得到数据。
|
||||
|
||||
"Hangcheck timer"用于检测系统是否被锁定。这个定时器监视着锁定进程。当一个进程被冻结了,定时器就开启。当定时器停止后,如果进程还没有重启或者关闭,那么定时器会强迫进程关闭。
|
||||
|
||||
引用Linus Torvalds的话:可移植性是对于那些无法写新程序的人而言的。
|
||||
|
||||
使用Trusted Computing Group(可信赖计算组)规范的TPM安全芯片会需要这个驱动(TPM Hardware Support)。
|
||||
|
||||
现在,我们可以进入I2C设备。I2C代表的是"Inter-Integrated Circuit"(内部集成电路)并经常被成为"eye two see"。然而,一些人会说"eye squared see"。I2C是一种串行总线标准。
|
||||
|
||||
一些旧的软件将I2C适配器作为类设备,但是如今的软件不会这么做(Enable compatibility bits for old user-space)。所以,这个驱动会提供对旧软件的向后支持。
|
||||
|
||||
接下来,可以生成I2C设备文件(I2C device interface)。
|
||||
|
||||
I2C可以通过这个驱动提供复用支持(I2C bus multiplexing support)。
|
||||
|
||||
I2C可以通过这个驱动支持GPIO控制的复用(GPIO-based I2C multiplexer)。
|
||||
|
||||
对于开发者用这个驱动可以在I2C和SMBus上执行不同的测试(I2C/SMBus Test Stub)。
|
||||
|
||||
I2C系统启用这个特性可以生成调试信息(I2C Core debugging messages)。
|
||||
|
||||
下一个驱动生成额外的I2C调试信息(I2C Algorithm debugging messages)。
|
||||
|
||||
引用Linus Torvalds的话:Linux中没有原始设备的原因似乎我个人任何原始设备是一个愚蠢的注意。
|
||||
|
||||
下面的驱动会使I2C驱动生成调试信息(I2C Bus debugging messages)。
|
||||
|
||||
接下来,我们有串行外设接口(Serial Peripheral Interface)支持(SPI support)。SPi是一种用于SPI总线的同步串行协议。
|
||||
|
||||
在这之后,有一个驱动用于高速同步串行接口(High speed synchronous Serial Interface support)支持(HSI support)。HSI是一种同步串行协议。
|
||||
|
||||
PPS同样在Linux内核中支持(PPS support)。
|
||||
|
||||
"IP-over-InfiniBand"驱动支持IP包通过InfiniBand(译注:一种无限带宽技术)传输。
|
||||
|
||||
在这之后,有一个调试驱动用于IP-over-InfiniBand(IP-over-InfiniBand debugging)。
|
||||
|
||||
SCSI的RDMA协议同样可以通过InfiniBand传输(InfiniBand SCSI RDMA Protocol)。
|
||||
|
||||
这里同样有一种通过InfiniBand传输iSCSI协议的扩展(iSCSI Extensions for RDMA (iSER))。
|
||||
|
||||
有时候,错误发生在了整个系统必须知道的核心系统中(EDAC (Error Detection And Correction) reporting)。这个驱动发送核心给系统。通常地,这类底层错误由处理器中报告并接着由这个驱动让其他系统进程知道或者处理错误。
|
||||
|
||||
这个驱动提供了在老版本中的sysfs中使用的过时EDAC的支持(EDAC legacy sysfs)。
|
||||
|
||||
EDAC可以用来设置发送调试信息给Linux的日志系统(Debugging)。
|
||||
|
||||
引用Linus Torvalds的话:没有人可以第一次创造如此好的代码,除了我。
|
||||
|
||||
"Machine Check Exceptions"(机器检测异常)(MCEs)通过这个驱动被转化成可读的信息(Decode MCEs in human-readable form (only on AMD for now))。MCEs是由CPU检测到的硬件错误。MCEs通常触发内核错误。
|
||||
|
||||
将MCE解码成可读的形式的过程可以被注射用于测试错误处理(Simple MCE injection interface over /sysfs)。
|
||||
|
||||
下一个驱动允许错误在内存中被检测到并纠正(Main Memory EDAC (Error Detection And Correction) reporting)。
|
||||
|
||||
下面,还有很多用于特定设备组的检测和纠正错误的驱动。
|
||||
|
||||
引用Linus Torvalds的话:理论和实践有时会冲突。那这个发生时,理论输了。每次都是。
|
||||
|
||||
现在我们可以进入实时时钟("Real Time Clock")。这通常缩写为"RTC"。RTC一直跟随着时间。
|
||||
|
||||

|
||||
|
||||
下面的设定允许用户在Linux系统中使用RTC时间作为"挂钟"时间(Set system time from RTC on startup and resume)。这个挂钟是我们在桌面上或者通过"date"命令看到的时间。
|
||||
|
||||
另外,挂钟可以通过NTP服务器得到时间并与RTC同步(Set the RTC time based on NTP synchronization)。
|
||||
|
||||
一些系统有几个RTC,所以用户必须设置哪一个是默认 (RTC used to set the system time)。最好设置第一个(/dev/rtc0)为主时钟。
|
||||
|
||||
可以设置RTC系统的调试特性(RTC debug support)。
|
||||
|
||||
RTC可以使用不同的接口给予操作系统当前时间。使用sysfs会需要这个驱动(/sys/class/rtc/rtcN (sysfs)),而似乎用proc需要这个驱动 (/proc/driver/rtc (procfs for rtcN))。特殊的RTC字符设备可以生成并使用 (/dev/rtcN (character devices))。shell命令"hwclock"使用/dev/rtc,所以RTC字符设备。
|
||||
|
||||
下一个驱动允许在/dev接口上模拟RTC中断(RTC UIE emulation on dev interface)。这个驱动读取时钟时间并允许新的时间从/dev中检索。
|
||||
|
||||
RTC系统可以通过测试驱动测试(Test driver/device)。
|
||||
|
||||
下面,我们会讨论直接内存访问系统。DMA是硬件独立于处理器的内存访问过程。DMA增加的系统性能因为处理器将做得更少如果硬件自身做了更多的任务。不然,硬件会等待处理器完成任务。
|
||||
|
||||
这是调试DMA系统的调试引擎(DMA Engine debugging)。
|
||||
|
||||
接下来,有许多的供货商/设备特定驱动用于DMA支持。
|
||||
|
||||
一些DMA通过这个驱动支持大端读取和写入(Use big endian I/O register access)。
|
||||
|
||||
大端指的是二进制码的排列。英语国家的数字系统将数字的最大端放在左边。比如,数字17,最左的数字是放置十位的地方大于个位。在大端中,每字节最大的放在左边。字节有8位。比如:10110100。每一处都有相应的值128、64、32、16、8、4、2、1。所以提到的为被转换成十进制180。
|
||||
|
||||
DMA系统可以使用网络减小CPU使用(Network: TCP receive copy offload)。
|
||||
|
||||
"DMA Test Client"用于测试DMA系统。
|
||||
|
||||
下一篇文章中,我们会讨论显示/视频驱动。谢谢!
|
||||
|
||||
参考:Linus Torvalds的引用来自于:[http://en.wikiquote.org/wiki/Linus_Torvalds][1]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.linux.org/threads/the-linux-kernel-configuring-the-kernel-part-17.4875/
|
||||
|
||||
译者:[geekpi](https://github.com/geekpi) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://en.wikiquote.org/wiki/Linus_Torvalds
|
Loading…
Reference in New Issue
Block a user