Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
just need quick help on this one what linux filesystem works best when networking with windows xp. as in fast and writeable not just readable. I have a 250gb hd with fat fs in my linux machine. I am switching from fc4 to debian. in fc4 i loose writing ability after the comp is on for more than 2 hrs. I have tried everything to stop this from happining. I want to know are there any fs in linux that both win and linux can read and write to besides fat.
So the drive is in the linux computer and Windows is on a different physical machine and you're moving data via a network? If that's right then you can use whatever filesystem you like. Computers talk to other computers over a network in a completely different language than they use when they are... playing with themselves. The filesystem used is irrelevant as when moving data it's first converted into a format the other computer will understand before it's sent. That way a linux computer formatted with XFS and a Windows machine formatted with NTFS can read and write to each other without any hassle at all, because the SMB protocol that is working in between the two machines is the universal language that they both understand
so if i format the 250gb in riserfs in the linux machine. i would be able to copy del modify and create on that hd if i am on the windows machine on the network or using the linux machine as an ftp modifing remotely assuiming proper permissions.
The filesystem used is irrelevant as when moving data it's first converted into a format the other computer will understand before it's sent. That way a linux computer formatted with XFS Windows machine formatted with NTFS can read and write to each other without any hassle at all
ahh i didnt no that ^ i didnt think writing to ntfs from linux was possible full stop
If it's over a network then filesystems don't even rate in the equation. If you've got a linux machine copying files to a Windows machine over a network, the Windows machine doesn't know what filesystem it's coming from nor does it care. Basically, you copy the file, Samba uses the linux filesystem drivers to pull the file off the disk and sent it to the Windows machine. The network stack in Windows reads this incoming data, figured out that it's a file transfer and uses it's native NTFS drivers to write the file to disk.
well explained cheers :-) ......that saves me worrying about ntfs write support does it not? if I just use samba .....say I wanted to transfer filea from 18.104.22.168 [tux linuxbox] to 192.168.168.232 [xpbox] c:\mysharedfolder
All network filesystems work on a file level: "open such-and-so file, move to byte #31234 and read 5678 bytes," and so on. So they don't care what kind of format is used by the drive.
Yes, Windows does contain an Installable File Systems (IFS) facility, and third-party drivers do exist for most formats. But usually, each computer uses a filesystem that is efficient and "friendly" for it. Even though FAT32 is comparatively-dirt, NTFS is quite well-designed. On Linux, I've had good success with ReiserFS as well as the venerable 'ext3'.