mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
20131114-1 选题
This commit is contained in:
parent
0a0f505f50
commit
2112677d84
290
sources/10 basic examples of linux netstat command.md
Normal file
290
sources/10 basic examples of linux netstat command.md
Normal file
@ -0,0 +1,290 @@
|
||||
10 basic examples of linux netstat command
|
||||
================================================================================
|
||||
### Netstat ###
|
||||
|
||||
Netstat is a command line utility that can be used to list out all the network (socket) connections on a system. It lists out all the tcp, udp socket connections and the unix socket connections. Apart from connected sockets it can also list listening sockets that are waiting for incoming connections. So by verifying an open port 80 you can confirm if a web server is running on the system or not. This makes it a very useful tool for network and system administrators. So in this tutorial we shall be checking out few examples of how to use netstat to find information about network connections and open ports on a system.
|
||||
|
||||
Here is a quick intro to netstat from the man pages
|
||||
|
||||
> netstat - Print network connections, routing tables, interface statistics, masquerade connections, and multicast memberships
|
||||
|
||||
### 1. List out all connections ###
|
||||
|
||||
The first and most simple command is to list out all the current connections. Simply run the netstat command with the a option.
|
||||
|
||||
$ netstat -a
|
||||
|
||||
Active Internet connections (servers and established)
|
||||
Proto Recv-Q Send-Q Local Address Foreign Address State
|
||||
tcp 0 0 enlightened:domain *:* LISTEN
|
||||
tcp 0 0 localhost:ipp *:* LISTEN
|
||||
tcp 0 0 enlightened.local:54750 li240-5.members.li:http ESTABLISHED
|
||||
tcp 0 0 enlightened.local:49980 del01s07-in-f14.1:https ESTABLISHED
|
||||
tcp6 0 0 ip6-localhost:ipp [::]:* LISTEN
|
||||
udp 0 0 enlightened:domain *:*
|
||||
udp 0 0 *:bootpc *:*
|
||||
udp 0 0 enlightened.local:ntp *:*
|
||||
udp 0 0 localhost:ntp *:*
|
||||
udp 0 0 *:ntp *:*
|
||||
udp 0 0 *:58570 *:*
|
||||
udp 0 0 *:mdns *:*
|
||||
udp 0 0 *:49459 *:*
|
||||
udp6 0 0 fe80::216:36ff:fef8:ntp [::]:*
|
||||
udp6 0 0 ip6-localhost:ntp [::]:*
|
||||
udp6 0 0 [::]:ntp [::]:*
|
||||
udp6 0 0 [::]:mdns [::]:*
|
||||
udp6 0 0 [::]:63811 [::]:*
|
||||
udp6 0 0 [::]:54952 [::]:*
|
||||
Active UNIX domain sockets (servers and established)
|
||||
Proto RefCnt Flags Type State I-Node Path
|
||||
unix 2 [ ACC ] STREAM LISTENING 12403 @/tmp/dbus-IDgfj3UGXX
|
||||
unix 2 [ ACC ] STREAM LISTENING 40202 @/dbus-vfs-daemon/socket-6nUC6CCx
|
||||
|
||||
The above command shows all connections from different protocols like tcp, udp and unix sockets. However this is not quite useful. Administrators often want to pick out specific connections based on protocols or port numbers for example.
|
||||
|
||||
### 2. List only TCP or UDP connections ###
|
||||
|
||||
To list out only tcp connections use the t options.
|
||||
|
||||
$ netstat -at
|
||||
Active Internet connections (servers and established)
|
||||
Proto Recv-Q Send-Q Local Address Foreign Address State
|
||||
tcp 0 0 enlightened:domain *:* LISTEN
|
||||
tcp 0 0 localhost:ipp *:* LISTEN
|
||||
tcp 0 0 enlightened.local:36310 del01s07-in-f24.1:https ESTABLISHED
|
||||
tcp 0 0 enlightened.local:45038 a96-17-181-10.depl:http ESTABLISHED
|
||||
tcp 0 0 enlightened.local:37892 ABTS-North-Static-:http ESTABLISHED
|
||||
.....
|
||||
|
||||
Similarly to list out only udp connections use the u option.
|
||||
|
||||
$ netstat -au
|
||||
Active Internet connections (servers and established)
|
||||
Proto Recv-Q Send-Q Local Address Foreign Address State
|
||||
udp 0 0 *:34660 *:*
|
||||
udp 0 0 enlightened:domain *:*
|
||||
udp 0 0 *:bootpc *:*
|
||||
udp 0 0 enlightened.local:ntp *:*
|
||||
udp 0 0 localhost:ntp *:*
|
||||
udp 0 0 *:ntp *:*
|
||||
udp6 0 0 fe80::216:36ff:fef8:ntp [::]:*
|
||||
udp6 0 0 ip6-localhost:ntp [::]:*
|
||||
udp6 0 0 [::]:ntp [::]:*
|
||||
|
||||
The above output shows both ipv4 and ipv6 connections.
|
||||
|
||||
### 3. Disable reverse dns lookup for faster output ###
|
||||
|
||||
By default, the netstat command tries to find out the hostname of each ip address in the connection by doing a reverse dns lookup. This slows down the output. If you do not need to know the host name and just the ip address is sufficient then suppress the hostname lookup with the n option.
|
||||
|
||||
$ netstat -ant
|
||||
Active Internet connections (servers and established)
|
||||
Proto Recv-Q Send-Q Local Address Foreign Address State
|
||||
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN
|
||||
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
|
||||
tcp 0 0 192.168.1.2:49058 173.255.230.5:80 ESTABLISHED
|
||||
tcp 0 0 192.168.1.2:33324 173.194.36.117:443 ESTABLISHED
|
||||
tcp6 0 0 ::1:631 :::* LISTEN
|
||||
|
||||
The above command shows ALL TCP connections with NO dns resolution. Got it ? Good.
|
||||
|
||||
### 4. List out only listening connections ###
|
||||
|
||||
Any network daemon/service keeps an open port to listen for incoming connections. These too are like socket connections and are listed out by netstat. To view only listening ports use the l options.
|
||||
|
||||
$ netstat -tnl
|
||||
Active Internet connections (only servers)
|
||||
Proto Recv-Q Send-Q Local Address Foreign Address State
|
||||
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN
|
||||
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
|
||||
tcp6 0 0 ::1:631 :::* LISTEN
|
||||
|
||||
Now we can see only listening tcp ports/connections. If you want to see all listening ports, remove the t option. If you want to see only listening udp ports use the u option instead of t.
|
||||
Make sure to remove the 'a' option, otherwise all connections would get listed and not just the listening connections.
|
||||
|
||||
### 5. Get process name/pid and user id ###
|
||||
|
||||
When viewing the open/listening ports and connections, its often useful to know the process name/pid which has opened that port or connection. For example the Apache httpd server opens port 80. So if you want to check whether any http server is running or not, or which http server is running, apache or nginx, then track down the process name.
|
||||
|
||||
The process details are made available by the 'p' option.
|
||||
|
||||
~$ sudo netstat -nlpt
|
||||
Active Internet connections (only servers)
|
||||
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
|
||||
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 1144/dnsmasq
|
||||
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 661/cupsd
|
||||
tcp6 0 0 ::1:631 :::* LISTEN 661/cupsd
|
||||
|
||||
When using the p option, netstat must be run with root privileges, otherwise it cannot detect the pids of processes running with root privileges and most services like http and ftp often run with root privileges.
|
||||
|
||||
Along with process name/pid its even more useful to get the username/uid owning that particular process. Use the e option along with the p option to get the username too.
|
||||
|
||||
$ sudo netstat -ltpe
|
||||
Active Internet connections (only servers)
|
||||
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
|
||||
tcp 0 0 enlightened:domain *:* LISTEN root 11090 1144/dnsmasq
|
||||
tcp 0 0 localhost:ipp *:* LISTEN root 9755 661/cupsd
|
||||
tcp6 0 0 ip6-localhost:ipp [::]:* LISTEN root 9754 661/cupsd
|
||||
|
||||
The above example lists out Listening connections of Tcp type with Process information and Extended information.
|
||||
The extended information contains the username and inode of the process. This is a useful command for network administrators.
|
||||
|
||||
**Note** - If you use the n option with the e option, the uid would be listed and not the username.
|
||||
|
||||
### 6. Print statistics ###
|
||||
|
||||
The netstat command can also print out network statistics like total number of packets received and transmitted by protocol type and so on.
|
||||
|
||||
To list out statistics of all packet types
|
||||
|
||||
$ netstat -s
|
||||
Ip:
|
||||
32797 total packets received
|
||||
0 forwarded
|
||||
0 incoming packets discarded
|
||||
32795 incoming packets delivered
|
||||
29115 requests sent out
|
||||
60 outgoing packets dropped
|
||||
Icmp:
|
||||
125 ICMP messages received
|
||||
0 input ICMP message failed.
|
||||
ICMP input histogram:
|
||||
destination unreachable: 125
|
||||
125 ICMP messages sent
|
||||
0 ICMP messages failed
|
||||
ICMP output histogram:
|
||||
destination unreachable: 125
|
||||
... OUTPUT TRUNCATED ...
|
||||
|
||||
To print out statistics of only select protocols like TCP or UDP use the corresponding options like t and u along with the s option. Simple!
|
||||
|
||||
### 7. Display kernel routing information ###
|
||||
|
||||
The kernel routing information can be printed with the r option. It is the same output as given by the route command. We also use the n option to disable the hostname lookup.
|
||||
|
||||
$ netstat -rn
|
||||
Kernel IP routing table
|
||||
Destination Gateway Genmask Flags MSS Window irtt Iface
|
||||
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
|
||||
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
|
||||
|
||||
### 8. Print network interfaces ###
|
||||
|
||||
The netstat command can also print out the information about the network interfaces. The i option does the task.
|
||||
|
||||
$ netstat -i
|
||||
Kernel Interface table
|
||||
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
|
||||
eth0 1500 0 31611 0 0 0 27503 0 0 0 BMRU
|
||||
lo 65536 0 2913 0 0 0 2913 0 0 0 LRU
|
||||
|
||||
The above output contains information in a very raw format. To get a more human friendly version of the output use the e option along with i.
|
||||
|
||||
$ netstat -ie
|
||||
Kernel Interface table
|
||||
eth0 Link encap:Ethernet HWaddr 00:16:36:f8:b2:64
|
||||
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
|
||||
inet6 addr: fe80::216:36ff:fef8:b264/64 Scope:Link
|
||||
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
|
||||
RX packets:31682 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:27573 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:1000
|
||||
RX bytes:29637117 (29.6 MB) TX bytes:4590583 (4.5 MB)
|
||||
Interrupt:18 Memory:da000000-da020000
|
||||
|
||||
lo Link encap:Local Loopback
|
||||
inet addr:127.0.0.1 Mask:255.0.0.0
|
||||
inet6 addr: ::1/128 Scope:Host
|
||||
UP LOOPBACK RUNNING MTU:65536 Metric:1
|
||||
RX packets:2921 errors:0 dropped:0 overruns:0 frame:0
|
||||
TX packets:2921 errors:0 dropped:0 overruns:0 carrier:0
|
||||
collisions:0 txqueuelen:0
|
||||
RX bytes:305297 (305.2 KB) TX bytes:305297 (305.2 KB)
|
||||
|
||||
The above output is similar to the output shown by the ifconfig command.
|
||||
|
||||
### 9. Get netstat output continuously ###
|
||||
|
||||
Netstat can output connection information continuously with the c option.
|
||||
|
||||
$ netstat -ct
|
||||
|
||||
The above command will output tcp connections continuously.
|
||||
|
||||
### 10. Display multicast group information ###
|
||||
|
||||
The g option will display the multicast group information for IPv4 and IPv6 protocols.
|
||||
|
||||
$ netstat -g
|
||||
IPv6/IPv4 Group Memberships
|
||||
Interface RefCnt Group
|
||||
--------------- ------ ---------------------
|
||||
lo 1 all-systems.mcast.net
|
||||
eth0 1 224.0.0.251
|
||||
eth0 1 all-systems.mcast.net
|
||||
lo 1 ip6-allnodes
|
||||
lo 1 ff01::1
|
||||
eth0 1 ff02::fb
|
||||
eth0 1 ff02::1:fff8:b264
|
||||
eth0 1 ip6-allnodes
|
||||
eth0 1 ff01::1
|
||||
wlan0 1 ip6-allnodes
|
||||
wlan0 1 ff01::1
|
||||
|
||||
### More examples of netstat command ###
|
||||
|
||||
Okay, we covered the basic examples of netstat command above. Now its time to do some geek stuff with style.
|
||||
|
||||
### Print active connections ###
|
||||
|
||||
Active socket connections are in "ESTABLISHED" state. So to get all current active connections use netstat with grep as follows
|
||||
|
||||
$ netstat -atnp | grep ESTA
|
||||
(Not all processes could be identified, non-owned process info
|
||||
will not be shown, you would have to be root to see it all.)
|
||||
tcp 0 0 192.168.1.2:49156 173.255.230.5:80 ESTABLISHED 1691/chrome
|
||||
tcp 0 0 192.168.1.2:33324 173.194.36.117:443 ESTABLISHED 1691/chrome
|
||||
|
||||
To watch a continous list of active connections, use the watch command along with netstat and grep
|
||||
|
||||
$ watch -d -n0 "netstat -atnp | grep ESTA"
|
||||
|
||||
### Check if a service is running ###
|
||||
|
||||
If you want to check if a server like http,smtp or ntp is running or not, use grep again.
|
||||
|
||||
$ sudo netstat -aple | grep ntp
|
||||
udp 0 0 enlightened.local:ntp *:* root 17430 1789/ntpd
|
||||
udp 0 0 localhost:ntp *:* root 17429 1789/ntpd
|
||||
udp 0 0 *:ntp *:* root 17422 1789/ntpd
|
||||
udp6 0 0 fe80::216:36ff:fef8:ntp [::]:* root 17432 1789/ntpd
|
||||
udp6 0 0 ip6-localhost:ntp [::]:* root 17431 1789/ntpd
|
||||
udp6 0 0 [::]:ntp [::]:* root 17423 1789/ntpd
|
||||
unix 2 [ ] DGRAM 17418 1789/ntpd
|
||||
|
||||
So we found that ntp server is running. Grep for http or smtp or whatever you are looking for.
|
||||
|
||||
Well, that was most of what netstat is used for. If you are looking for more advanced information or want to dig deeper, read up the netstat manual (man netstat).
|
||||
|
||||
And do leave your feedback and suggestions in the comments box below.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.binarytides.com/linux-netstat-command-examples/
|
||||
|
||||
译者:[译者ID](https://github.com/译者ID) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:
|
||||
[2]:
|
||||
[3]:
|
||||
[4]:
|
||||
[5]:
|
||||
[6]:
|
||||
[7]:
|
||||
[8]:
|
||||
[9]:
|
||||
[10]:
|
||||
[11]:
|
||||
[12]:
|
79
sources/Apache OpenOffice vs. LibreOffice.md
Normal file
79
sources/Apache OpenOffice vs. LibreOffice.md
Normal file
@ -0,0 +1,79 @@
|
||||
Apache OpenOffice vs. LibreOffice
|
||||
================================================================================
|
||||
> The two open source office productivity suites are similar, yet one appears to have a slight advantage.
|
||||
|
||||
[Apache OpenOffice][1] and [LibreOffice][2] are the modern descendants of OpenOffice.org. For the last few years, almost all Linux distributions have included LibreOffice as their default office suite. However, in the past eighteen months, OpenOffice has reappeared, newly organized into an Apache project, and free software users now have the choice of two full-featured suites instead of one.
|
||||
|
||||
Users also have the difficulty of deciding between two almost-identical choices. The two diverged three years ago, and while that can be a long period in software development, in this case, the differences are only starting to become obvious. While considerable cleanup has gone on behind the scenes, the feature sets and underlying logic in both has mutated in only minor ways from the days of OpenOffice.org.
|
||||
|
||||
Here and there, you can find new features in the individual applications, especially in the Writer word processor. However, most of the differences are at a higher level, in support for formats and fonts, the policy towards extensions, and, most of all, in the efforts to modernize and standardize the interface.
|
||||
|
||||
### Differences in the Apps ###
|
||||
|
||||
Most of the features in LibreOffice's and OpenOffice's applications are the same. In Draw, there appear to be no difference at all. In Impress, the main difference is that LibreOffice's latest release includes support for controlling a slide show from an Android device. And although the selection of slide backgrounds differs between the two, either selection should be adequate unless you are looking for a favorite. Similarly, the greatest difference between the two versions of the Calc spreadsheet is that, in LibreOffice's, you can create data forms.
|
||||
|
||||
Even in Writer, the most popular application, the differences are generally in a minor key. In LibreOffice, the status bar at the bottom of the editing window now includes a word and character count. In addition, LibreOffice's comments can be anchored to paragraphs rather than a single point, and, in a correction of a longstanding bug, in footnotes now display besides the text to which they refer. LibreOffice also adds a simplified Find field, similar to one in a web browser, while omitting the option to insert a graphical horizontal line -- a feature that few must have used for the last decade or more.
|
||||
|
||||
### Formats and Fonts ###
|
||||
|
||||
Some of the more noticeable differences fall under the category of format and font support. For instance, OpenOffice continues to support saving to formats that have gone out of fashion, such as AportisDoc (Palm) and Pocket Word. It can open .docx files, but, unlike LibreOffice, not save to it.
|
||||
|
||||
LibreOffice also has the advantage in font support. The latest version supports OpenType, the preferred format for modern fonts because of its support for multiple languages and advanced typography. Even more importantly, by going to File -> Properties -> Fonts, you can embed fonts into the document, eliminating with a single click the need to ensure font compatibility.
|
||||
|
||||
Such features give LibreOffice a decided edge when exchanging files with Microsoft Office users. In general, neither OpenOffice nor LibreOffice interact best with Microsoft formats when a document is mostly text and contains a minimum of tables, draw objects, and complex formatting. In both, for example, you are best off sharing something like a brochure in .PDF format rather than the native Open Document Format.
|
||||
|
||||
However, if you do exchange native and Microsoft formats, LibreOffice has some decided advantages. Not only does it both read and write to recent Microsoft formats, but its advantages in font handling removes any need for font subsitution -- a major cause of problems when exchanging files. While other problems remain, such as differences in feature implementation, LibreOffice should generally be the more reliable handler of Microsoft Office files.
|
||||
|
||||
### Extension Policies ###
|
||||
|
||||
Both OpenOffice and LibreOffice support well-rounded collections of extensions that can be downloaded and added in minutes to enhance or alter features. In most cases, an extension that works with one will work with the other.
|
||||
|
||||
The difference is that, with LibreOffice, you don't have to install the most popular extensions. Instead, LibreOffice installs with them already enabled or integrated. These extensions include Lightproof, a basic grammar checker; Report Builder for summarizing and printing from data bases; Presentation Minimizer for reducing the size of presentations; Wiki Publisher for blogging, and Presentation Console for delivering slide shows, as well as a number of others.
|
||||
|
||||
All these extensions are available for OpenOffice as well. The difference is that, with OpenOffice, you need to know about them and deliberately find them. Effectively, this limitation makes a number of features unavailable to new users. When OpenOffice (and LibreOffice) have made such efforts in recent releases to provide useful modern templates and clip art, this omission is a crippling oversight, especially when it is so easily corrected.
|
||||
|
||||
### Interfaces in Transition ###
|
||||
|
||||
In the twelve years that Sun Microsystems and Oracle have owned the OpenOffice.org code, the interface, like so many features, was almost entirely neglected. The result is that today, both OpenOffice and LibreOffice are suites with a healthy set of features, but interfaces that are generally stuck in the mid-1990s. Some superficial aspects have been removed, but far more remains to be updated.
|
||||
|
||||
In the latest release, OpenOffice's efforts to overhaul the interface have been restricted largely to the sidebar, an feature that has to be specifically enabled in LibreOffice from Tools -> Options -> LibreOffice -> Advance, and is labeled as "experimental."
|
||||
|
||||
The sidebar is a collection of features, primarily for manual formatting. Since this use comes at the expense of encouraging the use of styles, as the logic of the code intends, it is easy to dismiss. However, at its best, the sidebar is an immense simplification of some of the tabs for formatting characters and paragraphs, such as the Border tab in all applications, and the Format tab for spreadsheet cells. With luck, its re-conceptualization of controls will eventually find its way to the menus and style dialogue windows.
|
||||
|
||||
LibreOffice has been even more adventuresome. For example, the task pane in Impress, while similar to the sidebar, summarizes most of the steps in slide design in the names of its tabs.
|
||||
|
||||
But it is the Writer editing window where most of LibreOffice's interface improvements have taken place. A word and character count has been added to the status bar at the bottom of the window, and the cramped sub-menus for managing and editing templates have been replaced with a stream-lined interface in which buttons replace drop-down menus.
|
||||
|
||||
Even more obvious, the main text frame has been reduced in LibreOffice to cross-hairs at the four corners. In the same way, headers and footers are invisible until you click where they should be, when four small right angles indicate their borders.
|
||||
|
||||
A less successful effort is a tab in LibreOffice's editing window for managing headers and footers. Aside from the fact that the tab encourages manual formatting, it has the annoying habit of hiding part of the first line of a new page as it is typed.
|
||||
|
||||
These efforts are far from complete, although LibreOffice has also rearranged options in a number of dialogue windows. At times, they make LibreOffice a disconcerting mixture of vintage interfaces and modern minimalism that can be disconcerting to move between. However, at least LibreOffice is trying to address the long-delayed problem of the interfaces -- something OpenOffice has not had much time to consider.
|
||||
|
||||
### Making a Choice ###
|
||||
|
||||
An average user, whose documents are rarely longer than two or three pages, would often have to check the title bar to be sure whether they were using LibreOffice or OpenOffice. However, depending on their needs, advanced users will probably find LibreOffice currently has a small, but definite advantage.
|
||||
|
||||
This advantage is hardly to be unexpected. For one thing, LibreOffice had many months to advance while OpenOffice was concerned with setting up governance and doing a code audit. These tasks might be useful and necessary, but they do not make for improvements in the code that ordinary users are likely to notice.
|
||||
|
||||
For another, the LibreOffice fork was begun largely by members of [Go-oo][3], an unofficial fork of OpenOffice.org that wanted to accelerate change. While Apache OpenOffice was forming, LibreOffice attracted talent around the world who wanted to code and were excited by the idea that everything was suddenly up for reconsideration.
|
||||
|
||||
Nobody has any done a census, but my impression is that when the OpenOffice.org community divided, the more adventurous contributors chose to focus on LibreOffice, although a few, such as the semi-independent documentation team, deliberately work for both projects.
|
||||
|
||||
However, the most important advantage for LibreOffice is what might be called the license-drain. That is, while the Apache License is compatible with LibreOffice's Lesser GNU General Public License, the Less GNU General Public License is incompatible with the Apache License. In other words, while LibreOffice can borrow code freely from OpenOffice, OpenOffice cannot borrow at all from LibreOffice. Strictly speaking, it must do clean-room implementations of features it wants to borrow from LibreOffice.
|
||||
|
||||
This situation may change, especially since Apache OpenOffice enjoys enormous name recognition compared to LibreOffice. Yet LibreOffice has quickly earned widespread support and has an active community that has done more in three years than OpenOffice.org managed in twelve.
|
||||
|
||||
For now, whether you use Apache OpenOffice or LibreOffice is likely to make very little difference unless you need a particular feature. However, I suspect that, unless something unexpected happens, LibreOffice's slight advantage is only going to widen. Whichever you decide on, you may want to schedule a re-evaluation in a few years' time.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.datamation.com/applications/apache-openoffice-vs.-libreoffice-1.html
|
||||
|
||||
译者:[译者ID](https://github.com/译者ID) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.openoffice.org/
|
||||
[2]:http://www.libreoffice.org/
|
||||
[3]:https://en.wikipedia.org/wiki/Go-oo
|
@ -0,0 +1,41 @@
|
||||
Daily Ubuntu Tips – Change Samba Workgroup And Computer Name
|
||||
================================================================================
|
||||
Here’s another question new users to Ubuntu asked the most. The answer to the question is simple but when you’re new to anything, it takes time to fully understand it.
|
||||
|
||||
Here’s the question we received few days ago;
|
||||
|
||||
> How to change samba workgroup name and computer name in Ubuntu?
|
||||
|
||||
For most computer Ubuntu users, changing their computer name is the least thing on their list, let alone samba workgroup. A few power users may want to learn how to do this easily with using Ubuntu.
|
||||
|
||||
When it comes to changing the computer name in Ubuntu, we’ve written a simple post on that which can be [found here][1]. Follow the this simple guide on [changing your computer name in Ubuntu][1] to accomplish your goal.
|
||||
|
||||
There maybe other ways to changing your PC name in Ubuntu but this is the easiest and fastest. For those using Ubuntu server, you can use vi or vim to edit the hostname and hosts files. Using vi or vim maybe difficult for most so only someone with knowledge of using these editors should use it.
|
||||
|
||||
To change Samba workgroup in Ubuntu, press **Ctrl – Alt – T** on your keyboard to open the terminal. When it opens, run the commands below to edit Samba’s configure file.
|
||||
|
||||
sudo gedit /etc/samba/smb.conf
|
||||
|
||||
When the file opens, make sure the line starting with workgroup in the [global] section has the word or value you want the workgroup to be. For example, if you want the workgroup to be UBGP, replace WORKGROUP with that and save the file. In most cases, you’ll have to restart the computer for the change to apply.
|
||||
|
||||
![](http://www.liberiangeek.net/wp-content/uploads/2013/11/workgroupubuntu.png)
|
||||
|
||||
This is how you change your computer name as well as its workgroup in Ubuntu. Remember, if you are doing this to share or access Windows files and folders, you must also install Samba. Without Samba, it would be difficult sharing files with Windows.
|
||||
|
||||
To install Samba, run the commands below.
|
||||
|
||||
sudo apt-get install samba
|
||||
|
||||
Please come back and check out other future tips about Ubuntu.
|
||||
|
||||
Enjoy!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.liberiangeek.net/2013/11/daily-ubuntu-tips-change-samba-workgroup-and-computer-name/
|
||||
|
||||
译者:[译者ID](https://github.com/译者ID) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.liberiangeek.net/2013/10/daily-ubuntu-tips-change-computer-name/
|
@ -0,0 +1,45 @@
|
||||
Daily Ubuntu Tips – Get Geary, A Lightweight Email Reader In Ubuntu
|
||||
================================================================================
|
||||
As you may already know, Ubuntu comes with its own email client called Thunderbird that allows you to setup email accounts to send and receive emails. It also support IMAP protocol which services like Gmail, Yahoo Mail and Microsoft Outlook support.
|
||||
|
||||
Thunderbird is a great email client and does everything an email client supposed to do, but if you’re looking for an alternative that is lightweight and built around GNOME, then you may want to try Geary.
|
||||
|
||||
Geary is a free email program that lets you quickly and effortlessly read emails with a simple interface based around conversations. The entire discuss is read from a single pane without you having to click from one message to another.
|
||||
|
||||
Geary also support IMAP protocol which will let you send and receive emails using your online webmail accounts from Google, Yahoo and Microsoft.
|
||||
|
||||
For users with Ubuntu 13.10, Geary is already available from Ubuntu Software Center. All they have to do is run the commands below to install Geary.
|
||||
|
||||
sudo apt-get install geary
|
||||
|
||||
For previous versions of Ubuntu, press **Ctrl – Alt – T** on your keyboard to open the terminal. When opens, run the commands below to add its PPA repository.
|
||||
|
||||
sudo add-apt-repository ppa:yorba/ppa
|
||||
|
||||
Next, run the commands below to update your system and install Geary.
|
||||
|
||||
sudo apt-get update && sudo apt-get install geary
|
||||
|
||||
When you launch Geary the first time, it wants you to setup email accounts from Gmail, Yahoo or Microsoft.
|
||||
|
||||
![](http://www.liberiangeek.net/wp-content/uploads/2013/11/gearyubuntu.png)
|
||||
|
||||
The setup is pretty easy, just enter your account info and Geary will attempt to automatically configure your account.
|
||||
|
||||
To uninstall Geary, first remove its PPA repository from your system by running the commands below.
|
||||
|
||||
sudo add-apt-repository -r ppa:yorba/ppa
|
||||
|
||||
Then run the commands below to remove Geary.
|
||||
|
||||
sudo apt-get remove geary
|
||||
|
||||
That’s it.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.liberiangeek.net/2013/11/daily-ubuntu-tips-get-geary-a-lightweight-email-reader-in-ubuntu/
|
||||
|
||||
译者:[译者ID](https://github.com/译者ID) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
@ -0,0 +1,100 @@
|
||||
Outreach Program for Women Seeks New Linux Kernel Interns
|
||||
================================================================================
|
||||
The interns who worked with The Linux Foundation as part of the [FOSS Outreach Program for Women][1] this summer come from diverse backgrounds and levels of experience, but they now have at least one thing in common (besides their gender). They can all add “Linux kernel hacker” to their resume.
|
||||
|
||||
![](http://www.linux.com/images/stories/41373/OPW-kernel-contributions-9.jpg)
|
||||
|
||||
*Outreach Program for Women ranked among the top contributors to Linux kernel 3.12. Source: LWN.net.*
|
||||
|
||||
Lisa Nguyen, Xenia Ragiadakou, Elena Ufimtseva, Laura Vasilescu and Tulin Izer were among the seven women out of 41 applicants who received $5,000 stipends each as part of the first group of OPW interns sponsored by the Linux Foundation. They worked full time with kernel developers at Intel, Oracle, and Citrix for three months and tackled projects that included the x86 boot process and vNUMA topolgy. They were also able to take advantage of a $500 travel scholarship to attend and speak at LinuxCon in New Orleans or Edinburgh.
|
||||
|
||||
“It's not often that I'd get to say, 'I volunteered at LinuxCon North America, spoke at LinuxCon North America, and met Linus Torvalds in three days!" said Nguyen, whose internship focused on Xen block drivers with Konrad Rzeszutek Wilk at Oracle.
|
||||
|
||||
In addition to learning how to build and submit kernel patches, making new friends and colleagues and generally conquering their fears, the interns made significant contributions to the Linux kernel.
|
||||
|
||||
“I'm not scared touching kernel code anymore,” said Izer, who worked with Peter P. Waskiewicz Jr. at Intel on parallelizing the x86 boot process. “This was my first contribution to an open source project and I'm really proud of it. I intend to keep doing this for a long time.”
|
||||
|
||||
### Top Kernel Contributors ###
|
||||
|
||||
As a group, OPW was listed as a top contributor to the 3.11 kernel, coming in No. 13 with 230 changesets submitted, according to the [August kernel report on LWN][2]. And intern Xenia Ragiadakou was among the top 10 most active developers contributing 100 changesets to 3.11.
|
||||
|
||||
“My main project was to add trace events and write a trace-cmd plugin for parsing the traces in human readable format to facilitate xhci (driver) debugging,” said Ragiadakou, who worked with Intel kernel developer Sarah Sharp on the project. “I learned how to use git, how to use static code analysis tools, how to send patches, how to tune my debug logs, how the usb subsystem is assembled, how xhci driver is implemented.”
|
||||
|
||||
On the 3.12 kernel, OPW again ranked among the top companies contributing, this time at No. 11 with 19,649 lines of code changed, [according to LWN's][3] analysis in October. That represents 2.7 percent of all changes made during this latest development cycle.
|
||||
|
||||
After their internships ended in September, most of the women have continued to work on the projects they started and plan to keep it up.
|
||||
|
||||
“I think it's cool to be a kernel contributor and I wanted to do this for some time,” said Vasilescu, who worked with Carolyn Wyborny and Anjali Singhai at Intel on features for ethtool in the igb driver.
|
||||
|
||||
“I still have to learn how to stop. Sometimes, oh well, often, I cannot stop,” said Ufimtseva, who worked on vNUMA topolgy for paravirtual guests in Xen with Stefano Stabellini, Dario Fargiolli and George Dunlap at Citrix. “I keep working and later it contributes into the quality of code. But it is so engaging!”
|
||||
|
||||
The deadline for the next round of Linux kernel internships is Nov. 11. Applicants should have some basic knowledge of C or C++ and boolean algebra. Some experience with operating systems, Linux/Unix, and Git is nice but not required. For more information on the available projects and how to apply, visit the [OPW page on Kernel Newbies][4].
|
||||
|
||||
### Lisa Nguyen ###
|
||||
|
||||
![](http://www.linux.com/images/stories/41373/lisa-nguyen-kernel-intern-2.jpg)
|
||||
|
||||
**Lisa Nguyen worked on Xen block drivers with Konrad Rzeszutek Wilk at Oracle.**
|
||||
|
||||
I earned multiple college degrees in Computer Science, Digital Forensics, and Information Security before I became an OPW kernel intern. I have used Linux continuously for the past two years, and I have taken multiple roles in the Linux community including project manager, manpage author, LinuxCon session coordinator, and kernel contributor.
|
||||
|
||||
**Why did you apply to work on the Linux kernel with the OPW?**
|
||||
|
||||
I wanted a challenge and move out of my comfort zone. I wanted to give software development another chance, because I dealt with confidence issues in the past. One day, I decided that I wanted to pursue a career in Linux instead of becoming a digital forensics analyst. The timing couldn't have been better when I read about the OPW program through the Linux Foundation's post on Google+ and thought, "What do I have to lose if I don't try?"
|
||||
|
||||
### Elena Ufimtseva ###
|
||||
|
||||
![](http://www.linux.com/images/stories/41373/elena-ufimtseva-kernel-intern.jpg)
|
||||
|
||||
**Elena Ufimtseva worked on vNUMA topolgy for paravirtual guests in Xen with Stefano Stabellini, Dario Fargiolli, George Dunlap at Citrix.**
|
||||
|
||||
I worked as a Linux system admin for quite some time and there were different projects I was a part of. I graduated with a Master Degree in Computer Science at St.-Petersburg University in Russian Federation.
|
||||
|
||||
**Why did you apply to work on the Linux kernel with the OPW?**
|
||||
|
||||
I felt I want to create software, system software, low-level. Not java :). I had that feeling that I can work on complex problems and solve them. I always check on latest Linux news and I think the one that truly caught my attention was Greg's presentation at Google a few years ago about Linux kernel development community organization and patches application process. I thought 'wow, that sounds great!'
|
||||
|
||||
### Laura Vasilescu ###
|
||||
|
||||
![](http://www.linux.com/images/stories/41373/laura-vasilescu-kernel-intern-2.jpg)
|
||||
|
||||
**Laura Vasilescu worked with Carolyn Wyborny and Anjali Singhai on features for ethtool in the igb driver.**
|
||||
|
||||
I consider myself a geek and I have a huge interest for improving the education system (especially in Romania). As a student, I volunteered myself as an undergraduate teaching assistant at my university and as a member of the Romanian Open Source Education Association. My technical expertise is in networking, operating systems and low-level programming.
|
||||
|
||||
**Why did you apply to work on the Linux kernel with the OPW?**
|
||||
|
||||
I think is cool to be a kernel contributor and I wanted to do this for some time.
|
||||
|
||||
### Tulin Izer ###
|
||||
|
||||
![](http://www.linux.com/images/stories/41373/Tulin-Izer-kernel-intern-2.jpg)
|
||||
|
||||
**Tulin Izer worked with Peter Waskiewicz at Intel on parallelizing the x86 boot process. **
|
||||
|
||||
I'm from Turkey. I'm a computer engineering student at Galatasaray University in Istanbul. This is my final year.
|
||||
|
||||
**Why did you apply to work on the Linux kernel with the OPW?**
|
||||
|
||||
I was interested in operating systems and programming in C but I didn't have any experience with kernel development, I thought this would be a good place to start.
|
||||
|
||||
### Xenia Ragiadakou ###
|
||||
|
||||
Currently I study Computer Science at the University of Crete. I have finished some other studies in the past, on Economics and on Eastern Europe Studies. The reason that I decided to change field once again is because I got bored. I don't know how that sounds. I realized that my organism needed something more applicable, creative and dynamic. So, I decided to enter the Computer Science department. Now, my spirit rests peaceful :) I think coding suits me perfectly. It 's like a game and also I enjoy the developers' mentality.
|
||||
|
||||
**Why did you apply to work on the Linux kernel with the OPW?**
|
||||
|
||||
I wanted since a long time to participate in an open source project but i was thinking that I'm not competent enough to do so. There were three factors that drove me to apply. 1) The fact that OPW is aimed at women made me feel more comfortable. 2) The fact that there were projects on linux kernel because I like working on systems. 3) The fact that the introduction to Linux kernel development was smooth and took place quite early, during the application process.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.linux.com/news/featured-blogs/200-libby-clark/746687-outreach-program-for-women-seeks-new-linux-kernel-interns/
|
||||
|
||||
译者:[译者ID](https://github.com/译者ID) 校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:https://wiki.gnome.org/OutreachProgramForWomen
|
||||
[2]:http://lwn.net/Articles/563977/
|
||||
[3]:http://lwn.net/Articles/570483/
|
||||
[4]:http://kernelnewbies.org/OPWIntro
|
Loading…
Reference in New Issue
Block a user