How to connect raspberry pi to Linux computer via ethernet

yes I have figured it out using my 3 year linux experience.

so how to connect raspberry pi to our linux computer via ethernet port so that if dont have router we can make our laptop as router.

first  i am using arch linux.
so ubuntu procedure may be different here. i am sorry.

steps:

first i used this

https://wiki.archlinux.org/index.php/Dhcpd

and then

according to this wiki

i set up ethernet my ethernet is enp7s0
so

# ip link set up dev enp7s0

# ip addr add 192.168.2.1/24 dev enp7s0

according to this oh i am sorry this font i dont know how to change it may be i will check that later.

first

explanation:

we have to assign static ip to our ethernt port so that it can assign ip addressed to device connects to it.

according to wiki 

comment down all subnet masks.

and put this

# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#

# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;

default-lease-time 600;
max-lease-time 7200;

# Use this to enble / disable dynamic dns updates globally.
#ddns-update-style none;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the 
# DHCP server to understand the network topology.

#subnet 10.152.187.0 netmask 255.255.255.0 {
#}

# This is a very basic subnet declaration.

# subnet 10.254.239.0 netmask 255.255.255.224 {
#  range 10.254.239.10 10.254.239.20;
#  option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
# }


  subnet 192.168.2.0 netmask 255.255.255.0 {
  range 192.168.2.201 192.168.2.250;
  option domain-name-servers 192.168.2.254;
  option domain-name "example.org";
  option routers 192.168.2.254;
  option broadcast-address 192.168.2.255;
  default-lease-time 600;
  max-lease-time 7200;
}

# subnet 192.168.2.0 netmask 255.255.255.0 {
#  range 192.168.2.0 192.168.2.250;
#  # option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
# }

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.

#subnet 10.254.239.32 netmask 255.255.255.224 {
#  range dynamic-bootp 10.254.239.40 10.254.239.60;
#  option broadcast-address 10.254.239.31;
#  option routers rtr-239-32-1.example.org;
#}

# A slightly different configuration for an internal subnet.
# subnet 10.5.5.0 netmask 255.255.255.224 {
#   range 10.5.5.26 10.5.5.30;
#   option domain-name-servers ns1.internal.example.org;
#   option domain-name "internal.example.org";
#   option routers 10.5.5.1;
#   option broadcast-address 10.5.5.31;
#   default-lease-time 600;
#   max-lease-time 7200;
# }

# Hosts which require special configuration options can be listed in
# host statements.   If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

# host passacaglia {
#   hardware ethernet 0:0:c0:5d:bd:95;
#   filename "vmunix.passacaglia";
#   server-name "toccata.example.com";
# }

# Fixed IP addresses can also be specified for hosts.   These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP.   Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.


# host fantasia {
#   hardware ethernet 08:00:07:26:c0:a5;
#   fixed-address fantasia.example.com;
# }
host raspberrypi{

#static ip address to raspberry pi
 hardware ethernet B8:27:EB:66:A4:65;
 fixed-address 192.168.2.104;
}
# You can declare a class of clients and then do address allocation
# based on that.   The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

class "foo" {
  match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
}

shared-network 224-29 {
  subnet 10.17.224.0 netmask 255.255.255.0 {
    option routers rtr-224.example.org;
  }
  subnet 10.0.29.0 netmask 255.255.255.0 {
    option routers rtr-29.example.org;
  }
  pool {
    allow members of "foo";
    range 10.17.224.10 10.17.224.250;
  }
  pool {
    deny members of "foo";
    range 10.0.29.10 10.0.29.230;
  }
}

just copy and paste nothing else.

than start

systemctl start dhcpd4@enp7s0

and connect your raspberry pi to laptop and than

use ping -I enp7s0 192.168.2.104 

and bam its working so this is how we can actually connect raspberry pi to linux without using router

another tip

use create_ap tools to create hotspot i used 

sudo ./create_ap   wlp6s0 enp7s0 MyAccessPoint

wlp6s0 is my wifi interface.

and now you can do whatever on that wifi network

love linux its easy if you have some knowledge on linux

if dont have knowledge mail me i will help you or comment below 

thank you.

edited :

please disable first

systemctl stop dhcpcd@enp7s0.service