[EMAIL PROTECTED] wrote:
> 
> Here's a stab at preliminary objectives for filesystem tasks. Please
> review, comment, or rip apart as previously requested :)
> 
> -Kara
> 

Now that my mind's cleared, a few more thoughts:

Just because a filesystem is in the kernel, do we need to test on it? 
Take a look at all the foreign filesystems out there.  I think we need
to stick to Linux filesystems (in the kernel, not ext3 or SGI's or IBM's
becuse they're not in the kernel): ext2, reiserfs for the moment.  But
then there's also /proc, usbdevfs, devfs, shm (/dev/shm).

As for files, we have: /etc/mtab, /etc/fstab, and let's not forget
/proc/mounts.

For programs, we have: mount, fsck (fsck.ext2 or whatever it's called on
your system), badblocks, debugfs and debugreiserfs.  Then there's
tune2fs.

Question: is there a level above this still, or is the "next level"
specific areas (like security, firewalls, etc.)?

Seems like we have a _lot_ to test on above a basic level.

Sorry this is taking so long.  Just finalized three contracts (it never
rains, but it pours) with a fourth in the wings.

Ciao,

David A. Bandel
-- 
Focus on the dream, not the competition.
                -- Nemesis Racing Team motto
--
This message was sent from the lpi-examdev mailing list.
Send `unsubscribe lpi-examdev' in the subject to [EMAIL PROTECTED] 
to leave the list.

Reply via email to