×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
edtf '/rob/raul.txt'
created a new file. I typed some stuff in it and saved it.
ADDLNK OBJ('/rob/raul.txt') NEWLNK('/rob/raul2.txt')
dspf '/rob/raul2.txt' shows contents of original file
rmvlnk '/rob/raul.txt' deletes original file but not link. Much UNlike
a
logical file.
dspf '/rob/raul2.txt'
No such path or directory.
wrklnk '/rob/raul*.txt'
Object link Type
raul2.txt SYMLNK
edtf '/rob/raul.txt'
DSPF '/rob/raul2.txt'
shows new contents of raul.txt
That all makes sense, believe it or not. When you create a new "file" in
unix or on the IFS, you are actually doing a few things, two of which are
"allocate an inode" and "make a hard link to the inode"
Now when you edit, cat, mv, et cetera that file, you are actually working
with the inode through its link. When you create another hard link, the
only difference between the two is the name. Both are just pointers to the
inode where the data is really stored. The system will retain the alloated
inode(s) for this object until the last hard link has been removed.
Makes some sense?
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Always live within your income, even if you have to borrow money to do so."
-- Josh Billings
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
