• Following are the minimum requirements for Fedora 29 workstation :-

• Recommended 2 GHz Dual Core processor.

• 2 GB RAM.

• 15 GB unallocated Hard Disk.

• Bootable Media (USB / DVD).

• Installation steps :-

(Step1) :- Download the fedora 29 workstation ISO file :–

Once the ISO file is downloaded ,then burn it either in USB or DVD and make it bootable.

(Step2) :- Boot your system with bootable media (USB or DVD) :–

Reboot your system.Set the boot medium as USB or DVD from Bios settings so system boots up with bootable media.

(Step3) :- Choose Start Fedora-Workstation-Live- 29 :–

When the system boots up with bootable media then to begin with installation on your system’s hard disk, choose “Start Fedora-Workstation-29 Live“

(Step4) :-Select Install to hard drive option :–

Select “Install to Hard Drive” option to install Fedora 29 on your system’s hard disk, you can also try Fedora on your system without installing it, for that select “Try Fedora” Option.

(Step5) :- Choose appropriate language for your Fedora 29 Installation :–

In this step choose your language which will be used during Fedora 29 Installation.

(Step6) :- Choose Installation destination and partition scheme :–

• In this step we will choose our installation destination, means on which hard disk we will do installation.
• In the next screen we will see the local available hard disk, select the disk that suits your installation and then choose how you want to create partitions.
• If you choose “Automatic” partition scheme, then installer will create the necessary partition for your system automatically but if you want to create your own customize partition scheme then choose “Custom” option.CLICK ON DONE !
• Now I show u that how to create LVM(Local Volume Manager) based custom partitions :–

In my case,

I have around 779 GiB unallocated hard drive, so I will be creating following partitions on it :-

• /home         >>> 450 GiB
• /(root)        >>> 240 GiB
• boot/efi     >>>2 GiB
• /boot         >>> 2 GiB
• /var           >>> 50 GiB
• swap         >>> 24 GiB

CLICK ON DONE ! AND CHOOSE “ACCEPT CHANGES”.

(Step7) :- Select the time zone and begin installation :–

• Here you can select the time zone which suits to your system and click on “Begin Installation”.

• In this step we can see Fedora 29 Installation has been started and it is in progress.
• Once the Installation is completed, you will be prompted to restart your system.
• Click on Quit and reboot your system.

Don’t forget the Change boot medium from Bios settings so your system boots up with hard disk.

(Step8) :- Set User name and Password and Start using Fedora 29. :–

•  Now specify the local account (user name) and its password, later this account will be used to login to the system.
• Click on Next

And finally, we will get below screen which confirms that we are ready to use Fedora 29.

• Click on “Start Using Fedora”

]]> https://www.emblogic.com/blog/02/installation-to-fedora-29-4/feed/ 0 https://www.emblogic.com/blog/02/installing-office-in-fedora/ https://www.emblogic.com/blog/02/installing-office-in-fedora/#comments Mon, 22 Feb 2016 10:18:26 +0000 http://www.emblogic.com/blog/?p=13299 Continue reading →]]> For 32 bit systems

#wget http://download.documentfoundation.org/libreoffice/stable/5.0.4/rpm/x86/LibreOffice_5.0.4_Linux_x86_rpm.tar.gz

For 64-bit systems

#wget http://download.documentfoundation.org/libreoffice/stable/5.0.4/rpm/x86_64/LibreOffice_5.0.4_Linux_x86-64_rpm.tar.gz

After this  all steps are common

#tar -xvf LibreOffice_5.0.4_Linux_x86_rpm.tar.gz
#cd LibreOffice_5.0.4.2_Linux_x86_rpm/

#yum localinstall RPMS/*.rpm

You can use these steps in any other RPM based distribution but keeping in mind the last step (that command will vary according to the distribution)

If we talk about firewall the first thing that comes to our mind is a software “Barrier” between a system and a network it may be either internal or external. The purpose of this software is to protect our system from various threats. This network security system, can be used to control incoming and outgoing network traffic based on a specific set of rules. This firewall can be used in various devices like routers .

Now if we talk about it is a kernel (or in other word a piece of software )acting on hardware.

So the kernel provides us with XTABLES which stores chins and all the rule ,act as a firewall in system. XTABLE consist of different modules for different protocols. The various modules are:-

1 > iptables applies to IPv4

2> ip6tables to IPv6

3> arptables to ARP

4> ebtables for Ethernet frames

SO our current focus will be on iptables ,what is IPTABLES ???

Its a built in firewall application fro configuring the tables provided by the LINUX KERNEL FIREWALL . Two major things associated with these utilities or application are its chain and rule.

iptables is command that uses the concept of chains to handle the network traffic .It places the rules into chains which are checked against the network traffic.Decisions are made as to what to do with the packets based on these rules (i.e whether the packet should be accepted or dropped). The predefined chains  are as follows

PREROUTING: Packets will enter this chain before a routing decision is made.

INPUT: Packet is going to be locally delivered. It does not have anything to do with processes having an opened socket; local delivery is controlled by the “local-delivery” routing table: ip route show table local.

FORWARD: All packets that have been routed and were not for local delivery will traverse this chain.

OUTPUT: Packets sent from the machine itself will be visiting this chain.

POSTROUTING: Routing decision has been made. Packets enter this chain just before handing them off to the hardware.

Tables associated with Iptables are :-

Filter table , NAT table, Raw Table, Mangle Table

Rules are :- ACCEPT , DROP, QUEUE, RETURN

Their are various flags associated with iptables like

-A      to add a rule

-p      to indicate the protocol

-s       to indicate the source of packet

-d      to indicate the destination

-dport    port number of the destination port

-sport     port number of the source port

their are various other flags for which u can refer the man page

You can use the iptables service using command:-

service iptables start/stop/restart/status

When you are working on an already installed linux distribution, the grub package will be bydefault installed on the system.

I will be showing you, the example’s of working with grub-legacy. Because any grub version number thats in the form 0.9x is grub-legacy now.(Please note the fact that grub-legacy is no longer under active developement.)

For this example, i will be working on a Red hat enterprise linux 5.

[root@localhost ~]# rpm -qa | grep grub
grub-0.97-13.5
[root@localhost ~]#

the above shown package, will also provide you with a command called grub-install.

[root@localhost ~]# whereis grub-install
grub-install: /sbin/grub-install /usr/share/man/man8/grub-install.8.gz
[root@localhost ~]# rpm -qf /sbin/grub-install
grub-0.97-13.5

[root@localhost ~]# grub-install /dev/sda
Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.
# this device map was generated by anaconda
(hd0)     /dev/sda
[root@localhost ~]#

In the above command, it will install grub in the MBR of the hard disk /dev/sda.
the above command result tells you an important fact to understand. It tells that, there is a device map file, and is asking us to check and confirm whether the file is correct or not.

Device map file is used by grub to identify the OS device names in a precise way. GRUB uses this file to map the device names of BIOS to operating system device names.This was devised, because there was inconstancies with, Linux operating system’s device naming convention.

This file is configurable as per your requirement.

In the above example output of the /boot/grub/device.map tells that (hd0) in grub means /dev/sda in the operating system.

Whenever you install GRUB, on any of your partition, it gets installed and images are put under the directory “boot” in that partition.
If you want to install grub, under a directory other than the default “boot”, you need to specify the boot directory with a command line argument to grub-install command.

Imagine that you want to install grub, on one of your external hard disk, and is currently mounted under /mydisk. lets see how to do it.

[root@localhost ~]# grub-install --root-directory=/mydisk/grub/ /dev/sdb

Example: Windows and Unix.

Micro kernel : Kernel Image = Kernel Core. Services are build in to special modules which can be loaded and unloaded as per need.

We have another type of kernel integration technique called

Modular, this is derived from best of micro and monolithic kernel) In

Modular kernel integration:  Kernel Image = (Kernel core + IPC service modules +Memory  module +Process Management module). All other modules are loadable kernel modules.

Example: Linux kernel

1. First stop and disable the gnome network manager from running on boot.

#systemctl stop NetworkManager.service
#systemctl disable NetworkManager.service

2. Now start and enable the network service to run on boot.

#systemctl restart network.service
#systemctl enable network.service

Set the Static Address
1. Check which interface(s) you want to set as static.

# ifconfig
em1: flags=4163 mtu 1500
inet 192.168.1.148 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::dad3:85ff:feae:dd4c prefixlen 64 scopeid 0×20 ether d8:d3:85:ae:dd:4c txqueuelen 1000 (Ethernet)
RX packets 929 bytes 90374 (88.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1010 bytes 130252 (127.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 19

lo: flags=73mtu 16436
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0×10
loop txqueuelen 0 (Local Loopback)
RX packets 32 bytes 3210 (3.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 32 bytes 3210 (3.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

2. Next edit the config file for the required interface.

vim /etc/sysconfig/network-scripts/ifcfg-em1

3. Edit the config file to look similar to the following.

Change the BOOTPROTO from “dhcp” to “static”. Also adding IPADDR, NETMASK, BROADCAST and NETWORK variables and make sure ONBOOT is set to yes.

UUID=”e88f1292-1f87-4576-97aa-bb8b2be34bd3″
NM_CONTROLLED=”yes”
HWADDR=”D8:D3:85:AE:DD:4C”
BOOTPROTO=”static”
DEVICE=”em1″
ONBOOT=”yes”
IPADDR=192.168.1.2
NETMASK=255.255.255.0
BROADCAST=192.168.1.255
NETWORK=192.168.1.0
GATEWAY=192.168.1.1

Exit the editor by pressing ‘:wq’ and enter.

4. Restart the network service to apply the settings.

systemctl restart network.service

source : https://fedoraproject.org/

router based connection.
peer to peer connection.

Router Based Connection

In this type of connection it is assumed that your laptop is already in the network, lets say your ip to be 192.168.1.3 and you machine has ssh support.Now in Raspberry it is important that it has ssh support as well. Connect your raspberry pi into the router using a network cable, your raspberry will now have an ip address that was provided by the dhcp server. our next step is to find out the ip address of raspberry pi. In order to get the ip address of raspberry pi we could type ifconfig and look for “inet addr: x.x.x.x” if your raspberry is connected to a monitor. else if it is headless ( without a monitor) then we could look at the ip table of your router by seeing who is connected to the network. now that we know the ip address we could do the following from host machine

$ ssh pi@192.168.1.3

where 192.168.1.3 is the ip address of Raspberry provided by dhcp server.

Peer To Peer Connection

In a peer to peer based connection the Raspberry and host machine is directly connected to each other using a network cable. In order to do this we need static ip’s at both the ends. so we need to make the following change in /etc/network/interfaces file host machine, (note: dont forget to take a backup of /etc/network/interfaces file)

$sudo vim /etc/network/interfaces

auto eth0
iface eth0 inet static
address 192.168.10.2
netmask 255.255.255.0

add the above shown line to the file.

do the same in Raspberry pi as well but the only difference is that the ip address should be 192.168.10.3, note that the network id 192.168.10 should remain same.

after doing this restart the network service by typing the command or by restarting the machine.

$sudo /etc/init.d/networking restart.

then do a

$ssh pi@192.168.10.3

and now it will ask for password, provide the password. So you are now logged it to raspberry pi via ssh.

Source

www.emblogic.com

When a computer or other networked device connects to a network, its DHCP client software in the operating system sends a broadcast query requesting necessary information. Any DHCP server on the network may service the request. The DHCP server manages a pool of IP addresses and information about client configuration parameters such as default gateway, domain name, the name servers, time servers. On receiving a request, the server may respond with specific information for each client, as previously configured by an administrator, or with a specific address and any other information valid for the entire network, and the time period for which the allocation (lease) is valid. A host typically queries for this information immediately after booting, and periodically thereafter before the expiration of the information. When an assignment is refreshed by the client computer, it initially requests the same parameter values, but may be assigned a new address from the server, based on the assignment policies set by administrators.

On large networks that consist of multiple links, a single DHCP server may service the entire network when aided by DHCP relay agents located on the interconnecting routers. Such agents relay messages between DHCP clients and DHCP servers located on different subnets.

Depending on implementation, the DHCP server may have three methods of allocating IP-addresses:

• dynamic allocation: A network administrator reserves a range of IP addresses for DHCP, and each client computer on the LAN is configured to request an IP address from the DHCP server during network initialization. The request-and-grant process uses a lease concept with a controllable time period, allowing the DHCP server to reclaim (and then reallocate) IP addresses that are not renewed.
• automatic allocation: The DHCP server permanently assigns an IP address to a requesting client from the range defined by the administrator. This is like dynamic allocation, but the DHCP server keeps a table of past IP address assignments, so that it can preferentially assign to a client the same IP address that the client previously had.
• static allocation: The DHCP server allocates an IP address based on a preconfigured mapping to each client’s MAC address. This feature is variously called static DHCP assignment by DD-WRT, fixed-address by the dhcpd documentation, address reservation by Netgear, DHCP reservation or static DHCP by Cisco and Linksys, and IP address reservation or MAC/IP address binding by various other router manufacturers.

DHCP is used for Internet Protocol version 4 (IPv4), as well as IPv6. While both versions serve the same purpose, the details of the protocol for IPv4 and IPv6 are sufficiently different that they may be considered separate protocols.^[2] IPv6 devices may alternatively use stateless address autoconfiguration. IPv4 hosts may use link-local addressing to achieve limited local connectivity.

Static Linking and Static Libraries is the result of the linker making copy of all used library functions to the executable file. Static Linking creates larger binary files, and need more space on disk and main memory. Examples of static libraries (libraries which are statically linked) are, .a files in Linux and .lib files in Windows.

Steps to create a static library Let us create and use a Static Library in UNIX or UNIX like OS.
1. Create a C file that contains functions in your library.

We have created only one file for simplicity. We can also create multiple files in a library.

2. Create a header file for the library

3. Compile library files.

 gcc -c lib_mylib.c -o lib_mylib.o

4. Create static library. This step is to bundle multiple object files in one static library (see ar for details). The output of this step is static library.

 ar rcs lib_mylib.a lib_mylib.o

5. Now our static library is ready to use. At this point we could just copy lib_hello_static.a somewhere else to use it. For demo purposes, let us keep the library in the current directory.

Let us create a driver program that uses above created static library.
1. Create a C file with main function

 gcc -c lib_mylib.c -o lib_mylib.o

 ar rcs lib_mylib.a lib_mylib.o

gcc -c driver.c -o driver.o

gcc -o driver driver.o -L. -l_mylib

./driver 
fun() called from a static library

2. Compile the driver program.

use the following commands on terminal

mkfs.vfat /dev/sdb1

sdb1 is you node name(that can be check through ‘dmesg’ or ‘fdisk -l’)

you can also change the your pd name by using following command on terminal

mkfs.vfat -n ‘desired pd name’ /dev/sdb1

For example NFS server could be a Linux system and Unix could be a client. But it can’t be a window system because window is not NFS compatible. The NFS server exports one or more directories to the client systems, and the client systems mount one or more of the shared directories to local directories called mount points. After the share is mounted, all I/O operations are written back to the server, and all clients notice the change as if it occurred on the local filesystem.

A manual refresh is not needed because the client accesses the remote filesystem as if it were local.because access is granted by IP address, a username and password are not required. However, there are security risks to consider because the NFS server knows nothing about the users on the client system.

Configure nfs server

• Network configuration in Linux

1. A linux server with ip address 192.168.0.254 and hostname Server
2. A linux client with ip address 192.168.0.1 and hostname Client1
3. Updated /etc/hosts file on both linux system
4. Running portmap and xinetd services
5. Firewall should be off on server

• Three rpm are required to configure nfs server. nfs, portmap, xinetd check them if not found then install

1. Now check nfs, portmap, xinetd service in system service it should be on

#setup
Select  System service
from list
[*]portmap [*]xinetd [*]nfs

2.Now restart xinetd and portmap service

1. To keep on these services after reboot on then via chkconfig command
2. After reboot verify their status. It must be in running condition
3. now create a /data directory and grant full permission to it
4. now open /etc/exports filesave file with :wq and exit
5. also restart nfs daemons with expotfs

6. verify with showmount command that you have successfully shared data folder

configure client system

1. ping form nfs server and check the share folder
2. now mount this share folder on mnt mount point. To test this share folder change directory to mnt and create a test file
3. After use you should always unmount from mnt mount point
4. create a mount point, by making a directory
5. now open /etc/fstab file
6. after reboot check /temp directory it should show all the shared data

Any Linux system can operate as an FTP server. It has to run only the server software—an FTP daemon with the appropriate configuration. Transfers are made between user accounts on client and server systems. A user on the remote system has to log in to an account on a server and can then transfer files to and from that account’s directories only.

A special kind of user account, named ftp, allows any user to log in to it with the username “anonymous.” This account has its own set of directories and files that are considered public, available to anyone on the network who wants to download them.

The numerous FTP sites on the Internet are FTP servers supporting FTP user accounts with anonymous login. Any Linux system can be configured to support anonymous FTP access, turning them into network FTP sites. Such sites can work on an intranet or on the Internet.

1.Configuring the ftp Server

The vsftpd RPM package is required to configure a Red Hat Enterprise Linux system as an ftp server. If it is not already installed, install it with rpm commands as described in our pervious article. After it is installed, start the service as root with the command service vsftpd start . The system is now an ftp server and can accept connections. To configure the server to automatically start the service at boot time, execute the command chkconfig vsftpd on as root. To stop the server, execute the command service vsftpd stop. To verify that the server is running, use the command service vsftpd status.

2.Configure vsftpd server

In this example we will configure a vsftpd server and will transfer files from client side.

For this example we are using three systems one linux server one linux clients and one windows xp clients.

• A linux server with ip address 192.168.0.254 and hostname Server
• A linux client with ip address 192.168.0.1 and hostname Client1
• A window client with ip address 192.168.0.2 and hostname Client2
• Updated /etc/hosts file on both linux system
• Running portmap and xinetd services
• Firewall should be off on server

4.Check LAN card driver is installed or not.

LAN driver is the top most part for network. To check it run setup command

Select network configuration from list.

5.Check firewall status

Firewall is the necessary security part of Linux system which is connected to Internet. But in exam we are not going to use Internet so it’s good practice to disable it.

6.To disable firewall run setup commands.

• Now select firewall configuration from list and click on run tool.
• Select disable and click on ok and quit to return on command prompt.
• System reboot require to take effect so reboot system with reboot -f commands.

7.Check portmap and xinetd package status

Almost every Linux server needs these two rpm to function properly. First check that these rpm are install or not. If no rpm is install then install them via rpm commands.

• If you have rpm then check there status via setup commands.
• Now select system service from menu.
• put a star in front the portmap service.
• Now put star in front the xinetd service.
• Click on ok and select quit to come back on command prompt.

8.Now restart these two service.

• To keep on these services after reboot on then via chkconfig command.
• After reboot verify their status. It must be in running condition.
• Once you have successfully completed these steps you are ready to configure the Linux server .

 In 1991, a Finnish student named Linus Benedict Torvalds made the kernel of a now popular operating system. He released Linux version 0.01 on September 1991, and on February 1992, he licensed the kernel under the GPL license. The GNU General Public License (GPL) allows people to use, own, modify, and distribute the source code legally and free of charge. This permits the kernel to become very popular because anyone may download it for free. Now that anyone can make their own kernel, it may be helpful to know how to obtain, edit, configure, compile, and install the Linux kernel.

A kernel is the core of an operating system. The operating system is all of the programs that manages the hardware and allows users to run applications on a computer. The kernel controls the hardware and applications. Applications do not communicate with the hardware directly, instead they go to the kernel. In summary, software runs on the kernel and the kernel operates the hardware. Without a kernel, a computer is a useless object.

There are many reasons for a user to want to make their own kernel. Many users may want to make a kernel that only contains the code needed to run on their system. For instance, my kernel contains drivers for FireWire devices, but my computer lacks these ports. When the system boots up, time and RAM space is wasted on drivers for devices that my system does not have installed. If I wanted to streamline my kernel, I could make my own kernel that does not have FireWire drivers. As for another reason, a user may own a device with a special piece of hardware, but the kernel that came with their latest version of Ubuntu lacks the needed driver. This user could download the latest kernel (which is a few versions ahead of Ubuntu’s Linux kernels) and make their own kernel that has the needed driver. However, these are two of the most common reasons for users wanting to make their own Linux kernels.

Before we download a kernel, we should discuss some important definitions and facts. The Linux kernel is a monolithic kernel. This means that the whole operating system is on the RAM reserved as kernel space. To clarify, the kernel is put on the RAM. The space used by the kernel is reserved for the kernel. Only the kernel may use the reserved kernel space. The kernel owns that space on the RAM until the system is shutdown. In contrast to kernel space, there is user space. User space is the space on the RAM that the user’s programs own. Applications like web browsers, video games, word processors, media players, the wallpaper, themes, etc. are all on the user space of the RAM. When an application is closed, any program may use the newly freed space. With kernel space, once the RAM space is taken, nothing else can have that space.

The Linux kernel is also a preemptive multitasking kernel. This means that the kernel will pause some tasks to ensure that every application gets a chance to use the CPU. For instance, if an application is running but is waiting for some data, the kernel will put that application on hold and allow another program to use the newly freed CPU resources until the data arrives. Otherwise, the system would be wasting resources for tasks that are waiting for data or another program to execute. The kernel will force programs to wait for the CPU or stop using the CPU. Applications cannot unpause or use the CPU without the kernel allowing them to do so.

This article is about the operating system.The Unix operating system was conceived and implemented in 1969 at AT&T’s Bell Laboratories in the United States by Ken Thompson, Dennis Ritchie, Douglas McIlroy, and Joe Ossanna. It was first released in 1971, and initially, was written entirely in assembly language, a common practice at the time. Later, in a key pioneering approach in 1973, Unix was re-written in the programming language C by Dennis Ritchie (with exceptions to the kernel and I/O). The availability of an operating system written in a high-level language allowed easier portability to different computer platforms.

With AT&T being required to license the operating system’s source code to anyone who asked (due to an earlier antitrust case forbidding them from entering the computer business),Unix grew quickly and became widely adopted by academic institutions and businesses. In 1984, AT&T divested itself of Bell Labs. Free of the legal obligation requiring free licensing, Bell Labs began selling Unix as a proprietary product.

Linux is any Unix-like and POSIX-compliant computer operating system assembled under the model of free and open source software development and distribution. The main form of distribution are Linux distributions. The defining component of Linux is the Linux kernel, an operating system kernel first released on 5 October 1991, by Linus Torvalds. Because it considers Linux to be a variant of the GNU operating system, initiated in 1983 by Richard Stallman, the Free Software Foundation prefers the name GNU/Linux when referring to the operating system as a whole .

Linux was originally developed as a free operating system for Intel x86-based personal computers. It has since been ported to more computer hardware platforms than any other operating system. It is a leading operating system on servers and other big iron systems such as mainframe computers and supercomputers: as of June 2013, more than 95% of the world’s 500 fastest supercomputers run some variant of Linux,including all the 44 fastest. Linux also runs on embedded systems (devices where the operating system is typically built into the firmware and highly tailored to the system) such as mobile phones,tablet computers, network routers, building automation controls, televisions and video game consoles; the Android system in wide use on mobile devices is built on the Linux kernel.

The development of Linux is one of the most prominent examples of free and open source software collaboration: the underlying source code may be used, modified, and distributed — commercially or non-commercially — by anyone under licenses such as the GNU General Public License. Typically, Linux is packaged in a format known as a Linux distribution for desktop and server use. Some popular mainstream Linux distributions include Debian (and its derivatives such as Ubuntu and Linux Mint), Fedora (and its derivatives such as the commercial Red Hat Enterprise Linux and its open equivalent CentOS), Mandriva/Mageia, openSUSE (and its commercial derivative SUSE Linux Enterprise Server), and Arch Linux. Linux distributions include the Linux kernel, supporting utilities and libraries and usually a large amount of application software to fulfill the distribution’s intended use.

A distribution oriented toward desktop use will typically include the windowing systems X11 and Wayland and an accompanying desktop environment such as GNOME or the KDE Software Compilation. Some such distributions may include a less resource intensive desktop such as LXDE or Xfce for use on older or less powerful computers. A distribution intended to run as a server may omit all graphical environments from the standard install and instead include other software to set up and operate a LAMP or a LYCE solution stack. Because Linux is freely redistributable, anyone may create a distribution for any intended use.

]]> https://www.emblogic.com/blog/12/article-on-linux-administration/feed/ 0 https://www.emblogic.com/blog/06/ssh-server/ https://www.emblogic.com/blog/06/ssh-server/#comments Mon, 24 Jun 2013 09:17:55 +0000 http://www.emblogic.com/blog/?p=6581 Implemented SSH server completely…

Able to send as well as receive data using scp…

Now , thorough with the SSH server!!!!