Difference between Hardlink and Softlink

-


What is the difference between Hard Links and Soft Links

Apart from the concept of pointers in C hardlinks and Softlinks work differently. 

Every file has an inode number. This number is like an address similar to that of your house so whoever has it can go your house. So the hardlinks knows about the address and softlink only knows about the house and not the address.
Hardlink points to the inode number of the file so even if you change the name of file hardlink still has the address of the file hence will still have an access of the file. Coming to the part of Softlinks they point to the “file” rather than the address so the moment the original file is moved or renamed or deleted the softlink doesn’t work. Hardlinks work only on the same system or disks. Here we have a benefit that Softlinks can work on within multiple systems and disks. However if a old file is removed and a new files is added with the same name as previous then hardlink will fail but the softlink will still work. Thus hardlinks only worls for files and not for directories. Do remember Linux never allows users to create hardlinks associated with directories and only with files so no need of running smart. Howvever we all face miseries so to links directories one may use softlinks

Lets us simplify about hardlinks and softlinks by examples.

Step 1. Create a directory "linkf" (only for example set yours freely) Move to this new directory and create two new files named as 
"sfile" and "hfile". Cat data in each file as shown in below .gif 




Step 2. Create a softlink and a hardlink for each of the files above. soflink for "sfile" and hardlink for "hfile" 


Step 3. Search the inode number of each link and comparing it with their source files



Step 4.  If inode numbers have been found then rename the "sfile" to "sfile_new" and "hfile" to "hfile_new" 
Then do a ls command and cat both links. 
We observe that the color of soflinks change to red indicating missing or malfunctioning


 Thus this is all about the concept of hardlinks and softlinks.

 You can refer to this page too. 
For inodes refer this page.

 So Long :) 

Comments

Post a Comment

Popular posts from this blog

SR Flip Flop Verilog Code

-
Image
SR Flip Flop Verilog Code

The SR or Set-Reset Flip-Flop works a memory storage element. It can store a single bit of memory working with two inputs named set and reset. When the output Q is 0 then the flip-flop is said to be reset and when it is 1 then it is said to be Set. The output remains between 0 and 1 and is entirely dependent on the inputs. 
However, one must not get confused with SR Latch and SR Flip Flop. It must be remembered that a latch is level triggered and a flip-flop is edge triggered. Also, SR Latch does not have any feedback, whereas the SR Flip Flop has feedback from its output. Similarly, like latch, an SR Flip Flop can be contrasted with both NAND gates as well as Nor Gate as both serve as the universal gates.

The output of SR Flip Flop is called Qn+1 and Q’n+1 (Q bar). There always exists a present value of Q, so the actual output gives the next value of Q hence the name Qn+1. The outputs are always inverted, i.e. if Qn+1 is x then Q’n+1 will always be the 1s c…
Read more

SPI Working with Verilog Code

-
Image
SPI Verilog Code

Serial Peripheral Interfacing or simply saying SPI is a communication protocol used between devices to communicate with. They certainly have to talk in the same language or rather say synchronized signals to perform any action.
A particular SPI protocol consists of Microcontroller as Master and another microcontroller or IC as a slave. It is basically a master-slave relationship that exists here. The relationship of SPI can have Multi-master and slaves too. Each master has 4 wire lines at least to communicate with a single slave.
1. The first wire is called the SCL (Serial Clock). Serial Clock works in a tick-tock fashion as soon as the master selects the slave.
2. The second wire is MISO(Master IN Slave Out). This wire acts as an input to the final behavior of the signals sent to the slave. The slave sends the data bit by bit on this line which it synchronizes with the SCL line.
3. The third wire is MOSI (Master Out Slave IN) This wire acts as a carrier which only se…
Read more

Verilog Code for I2C Protocol

-
Image
[VISIT NEW POST FOR I2C HERE ] I2C PROTOCOL HolaAmigos
I2C devices have been around us for a long time. If you have done any Arduino projects with any peripherals such as Bluetooth (HC-05) or Gyroscope (MPU6050) or Barometer etc you might be surprised you have already used I2C devices. Yes
An I2C basically consists of a master microcontroller and a slave device which responds to the requests of the master. A slave cannot operate on its own. It can't even communicate with other slaves without having any permission from the master.
      You may have come across multi-master schematic but it becomes much more complex to handle such situation because of data leakage and also it requires more than 1 microcontrollers. So if you are using an I2C you cannot use any other non-I2C device on the same bus as both SDA and SCL lines are in conjunction with the I2C module. If you find this facility somewhere you are being fooled seriously !!!  I2C works on 2 signals as SCL and SDA                   …
Read more