Derek Glidden wrote:
> On Sun, 2003-04-06 at 12:18, Norbert Cartagena wrote:
>
>>I'm wondering what file system I should make C. After all, in A I will
>>be installing both Linux and Windows (which I need for my job). I
>>preffer to have a journaled file system (prefferably ReiserFS), but from
>>what I've seen, it looks like FAT32 is about the only thing which is
>>commonly read between Windows and Linux. Is there a free or inexpensive
>>tool which I can use on Windows which will allow me to read a Journaled
>>Linux file system?
>
>
> I would recommend that you get the cheapest little machine you can slap
> together, put the drive in it, and make it exported via NFS and Samba.
> You don't really need much to be a file server - a 486 with 32MB would
> probably be sufficient if it's got a decent network card. If you can
> scrape together a cheapie Pentium-class machine, you'll get PCI and you
> can use 100MB, which will make it that much faster.
>
> Otherwise, yes, you are pretty much going to have to make it FAT32 to be
> able to see it from both Linux and Windows, and the Linux FAT32
> implementation has known problems/bugs that can potentially lead to data
> loss. (There used to be tools that let you see ext2 filesystems from
> Windows, but I don't know how long it's been since they've been updated,
> or if they'll work with "modern" versions of Windows OS's.)
>
> You REALLY DON'T want to make it FAT32 native under Linux. The
> fileserver is your best option.
>
ICH!!! Unfortunatelly, doing that isn't an option at the moment. Since I
don't think I'll be writing anything to it from windows, anyways (think
glorified game box with VPN functionality), I think I might just make it
Ext3 and use the explore2fs tool, which Jay suggested. *Sigh* Oh well.
> P.S. SGI's XFS rocks all over other Linux journaling FSs.
>
Excuse the heavy brow, but why?
Thanks,
Gnorb
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:00:50 EDT