Jun 262014
 

Article first published on Urfix’s blog

The SCP protocol is a network protocol, based on the BSD RCP protocol, which supports file transfers between hosts on a network. SCP uses Secure Shell (SSH) for data transfer and utilizes the same mechanisms for authentication, thereby ensuring the authenticity and confidentiality of the data in transit. A client can send (upload) files to a server, optionally including their basic attributes (permissions, timestamps). Clients can also request files or directories from a server (download). SCP runs over TCP port 22 by default. Like RCP, there is no RFC that defines the specifics of the protocol.

SCP is an awesome tool. Learn it, Love it, Use it….
Continue reading »

Flattr this!

Jun 242014
 

A not so common guide, article by   first posted on http://www.refining-linux.org

The UNIX philosophy is based on the DRY principle which declares: “Don’t repeat yourself”. Therefore, a program just does what it’s made for and uses libraries or even other programs on your system to do a more advanced job. Some of these auxiliary programs are user definable and probably you already know the EDITOR environment variable, which specifies your default editor for the console. This is used, e.g., for the command visudo, which opens your /etc/sudoers file safely, or by svn to input a commit comment. But another important component is your console pager, which is used to display textual content on the console.

As a system administrator or a more advanced Linux user you surely know man and how to use it. man shows you the (probably localized) contents of your system’s manual pages for a specific command or file, at least you might think so, but actually that’s wrong or let’s say: not completely the truth. man selects which manpage to show, but the display itself is managed by your pager. Of course, not only man makes use of the pager, also commands like mail use it (which might not exist on your system if you don’t have an MTA installed), so this is a very basic program.

I assume, you have already used your pager very often, which is nothing else than more, less or lv (which is also a good pager but very seldom installed by default and therefore rarely known). Most of the time, you use them to display the contents of log files or configurations, which you don’t want to alter, but that’s not all. As mentioned before, other programs use your pager as well and there is a way to configure which one to take and of course also how to use it.

Continue reading »

Flattr this!

Jun 162014
 

Tee

The command “tee” it’s one of the basic commands that you should find in any system, yet it’s not so popular or use, this command reads standard input and writes it to both standard output and one or more files, effectively duplicating its input. It is primarily used in conjunction with pipes and filters. The command is named after the T-splitter used in plumbing.

In short if you want to redirect the STDOUT of any command as well as printing it to the screen, tee is the right tool to use, let’s see some practical use of this command.
Continue reading »

Flattr this!

Jun 102014
 

slackarchArticle by Velimir Baksa

On many sites there are a lot of information about Ubuntu or its successor, Mint, these distributions are excellent, very good for those who have never seen anything on Linux, but maybe someone could be more interested in having a greater freedom of action and try something that goes beyond a well-marked path, so what do you think of the GNU/Linux Arch and Slackware distributions ?

Many things are spoken around Arch and Slackware. And also many myths are around surrounding these two distributions, for someone they are hard to install, hard to use, hard for administration, good only for geeks.

Many myths about Arch/Slackware and I should say also Gentoo aren’t true. Both, Arch and Slackware, bring only the best to the operating system experience. BSD elegance and Linux kernel. Great customization, great user experience and unique philosophy. Today quality and simplicity don’t go together. But let’s take a look at some of the main aspects of a GNU/linux Distribution.
Continue reading »

Flattr this!

May 292014
 

Today I want to repost for my readers a really interesting article by Gionatan Danti first posted on his blog http://www.ilsistemista.net/, I hope you enjoy it as much as I do

File compression is an old trick: one of the first (if not the first) program capable of compressing files was “SQ”, in the early 1980s, but the first widespread, mass-know compressor probably was ZIP (released in 1989).

In other word, compressing a file to save space is nothing new and, while current TB-sized, low costs disks provide plenty of space, sometime compression is desirable because it not only reduces the space needed to store data, but it can even increase I/O performance due to the lower amount of bits to be written or read to/from the storage subsystem. This is especially true when comparing the ever-increasing CPU speed to the more-or-less stagnant mechanical disk performance (SSDs are another matter, of course).

While compression algorithms and programs varies, basically we can distinguish to main categories: generic lossless compressors and specialized, lossy compressors.

If the last categories include compressors with quite spectacular compression factor, they can typically be used only when you want to preserve the general information as a whole, and you are not interested in a true bit-wise precise representation of the original data. In other word, you can use a lossy compressor for storing an high-resolution photo or a song, but not for storing a compressed executable on your disk (executable need to be perfectly stored, bit per bit) or text log files (we don’t want to lose information on text files, right?).

So, for the general use case, lossless compressors are the way to go. But what compressor to use from the many available? Sometime different programs use the same underlying algorithm or even the same library implementation, so using one or another is a relatively low-important choice. However, when comparing compressors using different compression algorithms, the choice must be a weighted one: you want to privilege high compression ratio or speed? In other word, you need a fast and low-compression algorithm or a slow but more effective one?

In this article, we are going to examine many different compressors based on few different compressing libraries:

  • lz4, a new, high speed compression program and algorithm
  • lzop, based on the fast lzo library, implementing the LZO algorithm
  • gzip and pigz (multithreaded gzip), based on the zip library which implements the ZIP alg
  • bzip2 and pbzip2 (multithreaded bzip2), based on the libbzip2 library implementing the Burrows–Wheeler compressing scheme
  • 7-zip, based mainly (but not only) on the LZMA algorithm
  • xz, another LZMA-based program

Continue reading »

Flattr this!