but if you decide to use an updated version fo fsck

Ah, I see. You do a nonstandard hack to the player, and put a nonstandard filesystem in place, and replace one of the base system files of the player with a different version, then you want me to document that for you.

Sorry, I have to draw the line somewhere, or my FAQ will soon turn into a full Linux FAQ.

And you wonder why I recommend the average joe avoid the EXT3 conversion.

heh, i don't mind if its in the faq or not.... i just found it as a source of confusion when i referred to it.

but here's for another argument for it.
why not just forget the umount /drive0 and /drive1, and just have it fsck -fay /drive0 and /drive1. that will work also.
its a matter of consistency =). if you're going to fsck mount points, do it for all mount points. if your going to fsck device paths, then do it for all device paths.

how about that?

The thread that generated the text for that FAQ entry was long and had many different opinions and arguments in it. The text that currently resides in the FAQ was reached by a consensus of several experts here on the BBS as being absolutely correct.

I will not change it again unless that same group of experts comes in here an fights it out with you and you can still convince them that they are wrong.

How about just noting that if you're living on the cutting edge and ust ext3 then to read this thread!

It's not like there isn't anything non-standard mentioned in the FAQs...there's one basically devoted to hijack for instance.

In reply to:

---

"fsck -fay /" fails, because /etc/fstab still contains 'ext2' as the filesystem. However when you use "fsck -fay /dev/hda5" it won't look at the fstab, but use whatever filesystem it can derive from the superblock, i.e. ext3.

---

Sounds good in theory, but the fs he is trying to fsck is the root partition which (assuming he followed the directions on my page) is still ext2. If you look at the usage info for the version of fsck I provide it does not support the 'fsck /mountpoint' syntax.

empeg:/empeg/bin# fsck
Usage: fsck [-panyrcdfvstFSV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j ext-journal]
[-E extended-options] device

I am not sure why this is different that the stock empeg fsck, but I will add a note to my info page noting the difference.

-Mike

If anyone here wants access to the Developer Info section on RioCar for this type of info, let me know.