看分區說明 說是 都裝在 /USR下了 也有的說是在那裏編譯就裝在哪裏 那RPM軟件管理器裝的裝在哪裏? 本身下載而後MAKE INSTALL的默認裝在哪裏?html
編譯的時候./configure --prefix=/usr這樣的參數能夠設置目錄node
程序確實都是在/usr下。這裏有個概念和windows不同。linux下庫文件都是共享的,也就是說可執行程序放一塊兒,而後庫文件放一塊兒。windows下是一個程序一個目錄,庫文件沒法共享。因此一個程序可能功能很少,可是程序很大。linux下程序可能很是小。不過依賴某種庫。這就靠rpm或者apt或者pacman之類的解決了linux
/bin或者/usr/bin或者/usr/locale/bin下所有都是可執行程序或者腳本,/sbin,/usr/sbin,/usr/locale/sbin下也是可執行程序,不過都是不經常使用或者須要root權限程序,/lib,/usr/lib,/usr/locale/lib下都是運行庫。ubuntu
/下一級目錄都是基本系統。/usr/下一級目錄都是用戶的程序文件。發行版不一樣,可能定義有點不同,某些發行版不須要/usr/locale這個目錄,有些須要。你會發現其實/usr和/下目錄很象,/usr/locale也和/usr下目錄結構很象windows
若是整個系統都是你本身編譯,你甚至能夠不要/usr目錄,全部程序都放在/bin,/sbin下都是能夠的ide
.rpm程序裏面安裝到哪裏了是看編譯打包的時候定義安裝到何處就是何處。.deb也是同樣的url
有具體命令看包安裝到何處了,具體man rpm或者man debspa
以上: linux的應用都安裝到哪裏?.net
refer: Filesystem Hierarchy Standard/ wiki/ 百科unix
linux 是由文件組成的, 各個文件不是獨立存在的, 相互之間存在依賴關係
A hardlink isn't a pointer to a file, it's a directory entry (a file) pointing to the same inode. Even if you change the name of the other file, a hardlink still points to the file. If you replace the other file with a new version (by copying it), a hardlink will not point to the new file. You can only have hardlinks within the same filesystem. With hardlinks you don't have concept of the original files and links, all are equal (think of it as a reference to an object). It's a very low level concept.
On the other hand, a symlink is actually pointing to another path (a file name); it resolves the name of the file each time you access it through the symlink. If you move the file, the symlink will not follow. If you replace the file with another one, keeping the name, the symlink will point to the new file. Symlinks can span filesystems. With symlinks you have very clear distinction between the actual file and symlink, which stores no info beside the path about the file it points to.
refer: what-is-the-difference-between-a-hard-link-and-a-symbolic-link