- Lubos Rendek
ObjectiveThe following guide describes a basic installation of Logstash on Debian Linux.
Operating System and Software Versions
- Operating System: - Debian 9 (Stretch)
- Software: - Logstash 5.2
curlwill be used to download an appropriate Java JDK tarball.
ifconfigcommand has been deprecated and thus missing by default on Debian Linux, starting from Debian stretch.
# ifconfig -bash: ifconfig: command not foundThe new and recommended alternative for examining a network configuration on Debian Linux is
ipcommand. For example to use
ipcommand to display a network configuration run the following:
# ip addressThe above
ipcommand can be abbreviated to:
# ip aIf you still prefer to use
ifconfigas part of your daily sys admin routine, you can easily install it as part of the
5.6.29whereas the latest PHP source release is
7.1.0( given that there is no PHP 6 at all ).
Thanks to the new Zend Engine 3.0, your apps see up to 2x faster performance and 50% better memory consumption than PHP 5.6, allowing you to serve more concurrent users without adding any hardware. Designed and refactored for today’s workloads, PHP 7 is the ultimate choice for web developers today.
# apt-get install kannel
jessie-backportsrepository. So, the first step in getting Java 8 installed is to enable that repository.
/etc/apt/sources.listin your favorite text editor as
rootand add the following line.
# Backports repository deb http://httpredir.debian.org/debian jessie-backports main
# apt-get install python3-setuptoolsThe above command will also install Python 3 on your system. Next, use
easy_install3to install alternative Python package installer
# easy_install3 pip
/etc/ssh/sshd_configand change the following line:
FROM: PermitRootLogin without-password TO: PermitRootLogin yes
/lib/systemd/system/docker.servicewith your favorite text editor and replace the following line where
/new/path/dockeris a location of your new chosen docker directory:
FROM: ExecStart=/usr/bin/docker daemon -H fd:// TO: ExecStart=/usr/bin/docker daemon -g /new/path/docker -H fd://
So, you've decided to try out this thing you heard others talk about, called 'compiling a custom kernel'. If you are trying this as a hobby, or because you want to learn a new skill, very well – read on.
However, before we start, we will try to explain situations when this need arises and how to deal with it. Note that this is an extensive subject which needs much more in terms of space than we will provide here. You will learn the basics, what you need, what to do and what you'll achieve.
For more info, as usual, Google is your friend; also , the documentation resident in the kernel source tree will answer lots of questions. So, let's start with the beginning, with a last note : if need arises, we will publish more articles related to kernel compiling pertaining to other distros.
This is the last installment of our C development series, and arguably the most non-technical one. If you followed us from the beginning and practiced as much as possible, you now have some basic knowledge on C development and how to package your (favorite) application for two of the most used Linux distribution families, Debian and Redhat. This article is about the community, how to contribute, how to collaborate and finally, how to get your package in the official Debian archives. If you read the previous articles in the series you won't need any other technical knowledge; all you need is the will to put your knowledge to work for community's benefit.
You have an application, you packaged it and now you're anxious to upload it to the Debian archives (by the way, many of the ideas presented here apply to many Open Source projects: what differs usually is the way of doing things). We'd say not so fast. Take a minute to breathe and find ways to make yourself known to the community. Take some time to read the Debian New Maintainer's Guide, if you haven't already, and remember the key word here: community. Everyone is a volunteer, and we chose Debian especially because of its democratic views, and nobody is paid or forced in any way to do your bidding. Anyway, since we know how much you like to read guides and manuals, part of this article will consist of some sane advice regarding collaboration. First, get used to get by on your own. Nobody likes a person that, when he or she hits the first sign of trouble, instead of going to the best Internet friend, $SEARCH_ENGINE, start polluting the forums, mailing lists and IRC channels with puerile questions like "What gcc flags do I need to compile my code for i686?". The only thing you will gain is a less than friendly RTFM and lots of missing geek points. Yes, we know that the gcc manual is big and a sure shot for headaches, but reading the manual, then searching the net first is the Right Way (TM). No exceptions. You will make a first good impression when you show the other developers that you made your homework. On the other hand, giving beginners a hard time, especially when such behavior is not called for, will not get you any popularity. Remember that you were once like them, remember that you, as we all, still have a lot to learn, and perhaps point the person towards a resource you think is helpful. In this context, remember that word again: community. Your work doesn't mean much, despite the fact that it means the world to you, unless the community finds it useful. Collaborate with them and be ready to accept feedback, and be thankful for it, even though you might not like what you hear. Leave your pride at the door and remember that the best and maybe only way to make your software better is community feedback. But don't fall into extremes, and try to be impartial. Perhaps some people will try to put you down just for the fun of it: ignore them and concentrate on constructive criticism.
# apt-get udpateIf you have not done so yet install a
curlcommand which you will use to download Cran R-3.2.1 source code:
# apt-get install curl