08-27-2010
We only know as much as you tell us, and a makefile without the files it works on is not a lot. A silly makefile doesn't tell me a thing about your file layout,
I still don't know after asking three times if you ever fixed your use of tar, in fact the most I've gotten from you -- beyond abuse -- is one ls readout of only a quarter of the files I asked for. A real listing of
all the hardlinked input (and output) files could have been helpful(and would still be), but you treat it like an RTFM.
If you're trying to create an ISO with rock-ridge hard links, yes, that is a problem. Is the input truly Rock Ridge? Usually on livecd's I see compressed filesystems done as cramfs and the like.
Preserving hard links doesn't seem to matter to me when creating a read-only filesystem. The permissions, contents, and owners are still all as they should be, and nothing will ever be able to change it.
Last edited by Corona688; 08-27-2010 at 12:50 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
what is link? and soft link? how about hard one and symbolic link.
and inode.
i get confuse about this links. could anyone help me with full explainsion?
thks
Gusla (5 Replies)
Discussion started by: gusla
5 Replies
2. UNIX for Dummies Questions & Answers
hi, i am in a directory, have 2 files as below
then do a ls -l gives the below
lrwxrwxrwx 1 root system 23 Mar 08 2001 filea -> /adir/filea
lrwxrwxrwx 1 root system 23 Mar 08 2001 filea -> /adir/fileb
now, when i do a cd /adir, the system said, adir not... (5 Replies)
Discussion started by: yls177
5 Replies
3. UNIX for Dummies Questions & Answers
hi
i have a hardlink how can i find the source of it (2 Replies)
Discussion started by: jpriyank
2 Replies
4. UNIX for Dummies Questions & Answers
From what I understand a symbolic link is alot like a shortcut where it points to another file. if the original file is deleted the symbolic link is rendered useless but a symbolic link can be deleted without any problem.
A hard link is like a copy of the file itself but pointing to the same... (3 Replies)
Discussion started by: cue
3 Replies
5. UNIX for Advanced & Expert Users
Hard links for directories are not permitted by default. But in some flavor of Unix, super user can create hard links for directories by some other way? Is that true? Is it possible in latest version of BSD or other unix? (2 Replies)
Discussion started by: bbala
2 Replies
6. Shell Programming and Scripting
Ksh newbie here, so please bear with me.
I'm currently writing a script that searches through a directory and displays files with multiple hard links. The way I have it set up, is that it displays the i-node number and then each of the link names. In addition to this, I need to know if there... (7 Replies)
Discussion started by: Unknown50862
7 Replies
7. Solaris
When loooking at files in a directory using ls, how can I tell if I have a hard link or soft link? (11 Replies)
Discussion started by: Harleyrci
11 Replies
8. AIX
Hi
I'm logged in as root in an aix box
Which command will list all the soft links and hard links present in the server ? (2 Replies)
Discussion started by: newtoaixos
2 Replies
9. UNIX for Dummies Questions & Answers
Hai,
give me a simple example for soft and hard links.
this will work for soft link ?? ln -s (2 Replies)
Discussion started by: Ramesh M
2 Replies
10. Shell Programming and Scripting
Hi team, i am writing a purge script to delete softlinks and hardlinks on linux system which are 3/10/30 days old. To test the script i need to create links with old timestamp, i am able to cange timestamp for files but not for links.
i tried touch -h option but this option is not available on... (1 Reply)
Discussion started by: Satyak
1 Replies
LEARN ABOUT CENTOS
mkzftree
MKZFTREE(1) H. Peter Anvin MKZFTREE(1)
NAME
mkzftree - Create a zisofs/RockRidge compressed file tree
SYNOPSIS
mkzftree [OPTIONS]... INPUT OUTPUT
DESCRIPTION
Takes an input file tree (INPUT) and create a corresponding compressed file tree (OUTPUT) that can be used with an appropriately patched
mkisofs(8) to create a transparent-compression ISO 9660/Rock Ridge filesystem using the "ZF" compression records.
OPTIONS
-f, --force
Always compress all files, even if they get larger when compressed.
-z level, --level level
Select compression level (1-9, default is 9). Lower compression levels are faster, but typically result in larger output.
-u, --uncompress
Uncompress an already compressed tree. This can be used to read a compressed filesystem on a system which cannot read them
natively.
-p parallelism, --parallelism parallelism
Compress in parallel. The parallelism value indicates how many compression threads are allowed to run.
-x, --one-filesystem
Do not cross filesystem boundaries, but create directory stubs at mount points.
-X, --strict-one-filesystem
Do not cross filesystem boundaries, and do not create directory stubs at mount points.
-C path, --crib-path path
Steal ("crib") files from another directory if it looks (based on name, size, type and modification time) like they match entries in
the new filesystem. The "crib tree" is usually the compressed version of an older version of the same workload; this thus allows
for "incremental rebuilds" of a compressed filesystem tree. The files are hardlinked from the crib tree to the output tree, so if
it is desirable to keep the link count correct the crib path should be deleted before running mkisofs. The crib tree must be on the
same filesystem as the output tree.
-l, --local
Do not recurse into subdirectories, but create the directories themselves.
-L, --strict-local
Do not recurse into subdirectories, and do not create directories.
-F, --file
Indicates that INPUT may not necessarily be a directory; this allows operation on a single file. Note especially that if -F is
specified, and INPUT is a symlink, the symlink itself will be copied rather than whatever it happens to point to.
-s, --sloppy
Treat file modes, times and ownership data as less than precious information and don't abort if they cannot be set. This may be
useful if running mkisofs on an input tree you do not own.
-v, --verbose
Increase the program verbosity.
-V value, --verbosity value
Set the program verbosity to value.
-q, --quiet
Issue no messages whatsoever, including error messages. This is the same as specifying -V 0.
-h, --help
Display a brief help message.
-w, --version
Display the release version.
BUGS
Long options (beginning with --) may not work on all systems. See the message printed out by mkzftree -h to see if this applies to your
system.
Inode change times (ctimes) are not copied. This is a system limitation and applies to all file copy programs.
If using the parallel option (-z) the access times (atimes) on directories may or may not be copied. If it is important that the atimes on
directories are copied exactly, avoid using -z.
AUTHOR
Written by H. Peter Anvin <hpa@zytor.com>.
COPYRIGHT
Copyright (C) 2001-2002 H. Peter Anvin.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
SEE ALSO
mkisofs(8)
zisofs-tools 30 July 2001 MKZFTREE(1)