On Fri Aug 26 2005 - 05:33:43 EST, Erik Mouw wrote:
> I prefer tar because I have more experience with it, and it works.
>> The kernel people prefer cpio because they have experience with it, it
>> doesn't need too much code, and it works.
I know that experience dosen't come from packing the kernel source,
or the zillion other tar archives on the internet.
> It seems to be the most used archiver in the UNIX world.
>> You've been told that there are *technical* reasons not to use tar in
>> the kernel. The kernel developers never cared about what was most used
>> or what "the market wants", but only about what was *technically*
>> useful.
I haven't been told that.
>>Did you ever take some time to actually *understand* what ramfs is,
>>*why* it is used for initramfs, and why you can't use any filesystem
>>you like for an initramfs?
You can use tmpfs and that's sufficient.
You only need one initramfs and it should be tmpfs, but if you
have two make ramfs a little more robust (that word again!).
This is a definition of robust I found on the web:
Refers to software without bugs that handles abnormal conditions well.
It is often said that there is no software package totally bug free.
Any program can exhibit odd behavior under certain conditions, but a
robust program will not *lock up* the computer, cause damage to data or
send the user through an endless chain of dialog boxes without
purpose. Whether or not a program can be totally bug free will be
debated forever.
I'm sure if I gave ramfs a chance it would fit that definition to a tee.
> For one, if you do "dd if=/dev/zero of=foo" on a ramfs the system
> will lock up.
>> "Doctor, it hurts when I do this!" "Well, then don't do that."
>> You found a nice case of "Unix, rope, foot".
I guess you graduated from the Henny Youngman school of coding, the same
school the author of ramfs graduated from.
But seriously, you're obviously a coder/comedian and I hope you don't
confuse the two.
If Windows had that defeatest philosophy where would it be?
Ramfs has a more limited use than tmpfs and that may be sufficient,
because people know its limitations and stay within them, but
that's no reason to pat yourself on the back.
>>PS: I'm not going to hunt through my linux-kernel mailbox for replies
>>without proper In-Reply-To and References headers in the hope that I
>>stumble over a possible reply from you. Any reply without such
>>headers will most probably not been seen and just ignored.
You have to Cc me if you want that.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |