“A conceptual understanding of file systems, especially data structure and related terms, will help you become a successful system administrator. I have seen many new Linux system administrator without any clue about file systems. The conceptual knowledge can be applied to restore file systems in an emergency situation.”
Not a bad article but I was able to spot three typos in under one minute…
not a complete UNIX/linux article: non of the BSDs filesystem were mention like the FFS aka UFS. BSDs are also a popular UNIX like OSs.
not a complete UNIX/linux article: non of the BSDs filesystem were mention
Not a complete Linux article either. There are more Linux filesystems than ext2/3 (and at least JFS, Reiser and XFS are used in production environments)
The remove-by-inode part is cute but you can delete his examples without it,
touch “la*
rm “”la*”
and
touch “+Xy +8”
rm “+Xy +8”
work just fine.
The rest seems more like a file-handling 101, nothing much conceptual to see here and I don’t think it really furthers the understanding of file-systems.
Hans Reiser’s homepage has an article about many of the concepts of current filesystems on the frontpage ( http://www.namesys.com/ )
Test the commands you recommend first or end up looking the n00b. Some sort of bizarro shell that doesn’t care about matching quotation marks?
Maybe shell-commands 101.
The commands work very well under bash.
Anyway, the point was that you can use quotation marks (or escape sequences or whatever your shell provides) to handle weird file names.
Edited 2006-02-01 11:01
I’m sorry kids but no shell on earth will let you enter an unmatched quote, what planet are you trying that on? If you escape those odd quotes with a back slash, then and only then will that work.
You can mod that down all you want but there is no excuse for flaming someone’s factual article with non-sensical un-tested shell commands. I find such silly syntax far more insulting. Respect your shell and get to know it. Besides that and to the point wildcards are a piss poor substitute for surgical removal by inode of badly named files. If you refuse to do it properly then at least check your pattern with an ls first.