Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
ext3 is backward compatible with ext2. they are in essence the same file system. just one has a journal that is saved for the kernel and the other doesent. You can actually switch between the 2 in linux by removing and readding the journal at will. So the driver works for both of them. Ive had issues with this driver in question tho installing programs from windows into the ext2 drive but its not a major issue.
You cannot create files in NTFS with a : in the file name in windows XP? and as far as I know $ files are system files and dont need backed up anyway. All this file system nonsense i belive in the future will be void as the harddrive is a dying technology closeing on its limits quickly.
Hopefull in the future the seperation between ram and storage will be a vitual one and not physical due to magnetic ram.
nx5000 : That's why I'd never offer it to someone else. I've already had 2 scary fsck moments after plugging into XP and using that driver!!
1) The ":" & "$" situation should not be a problem though. If the files exist - whatever they are - I just want them copied. I don't want to have to think about interpretations which can be subjectively made by each OS. Like the old Nike advert says : "Just DO IT!!".
2) if you're referring to the quantum uncertainty principle then I believe we are a little way from that hurdle just yet... :-)
I'm using a Linksys NSLU2 NAS device and have opted for ext3 as the filesystem on my external HDD (sensible, I think).
I've been using your ext2 driver utility (version : Ext2IFS_1_10c.exe) as it is very useful for accessing ext2/ext3 filesystems. As far as I'm aware it's the only one with write access.
I do have a couple of issues which I'd like to submit to you and hope you can advise/rectify.
1. It crashes when I try to copy any files containing the chars "$" or ":".
2. I often get filesystem errors after using it and reconnecting the HDD to the NSLU2 or to a Linux server.
So I've taken your advice.
I was trying to find a _useful_ ext2/3 filesystem driver for XP. I was inviting comments from other members in the forum and also advising of the problems I had encountered - to warn people if you like.
I thought that this was the purpose of such forums.
Since you obviously feel that I was labouring a point - then please will you tell me why?
My latest post regarding ext2fs was in reply to exvor who had stated that files containing ":" and "$" were not valid files to copy. I was _exploring_ the option that he was correct and as such, had not considered this to be a bug. That is why I had not sent this in a formal report to the author(s) of ext2fs - otherwise criticisms abound in relation to unnecessarily posting to authors concerning features which are not bugs.
I have posted to authors on 2 previous occasions which have resulted in a satisfactory outcome.
I thought I knew what I was doing until I read your post.
I too have been looking for a better solution as fat32 is a dog when it comes to permissions and stuff and the ext2 driver in windows is very imcompleate. Hopefully vista can smooth my woes with windows but probably not knowing Microshaft.
Why do you need to exchange/modify files with permission?
I mean if you have windows, you can access some linux files as read-only (only to view some files) but otherwise I don't see a reason to write on a linux fs from windows?
If you want to exchange downloaded things, go with fat. Linux can set permissions on the mounted vfat system. It's simple and supported from both sides as read-write (well, file size can be a limitation under fat..)
In my case I wanted a univeral home parttion where my home for my user could be the same drive in linux and windows. So this is why i neede permissions other then what fat can provide. Ive since choped up the drive on that laptop so its not really an issue for me anymore. full ext2 file system support in winders would be nice but i can live with what we have now.