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.
You could try mounting the floppy and using dd to see what's there. As to how you "lost" things, most Linux file operations are blocked and buffered, and changes are not written to a drive before the block is full. umounting a drive will flush the buffer to the drive, and eject normally unmounts the drive before ejecting it. If you manually removed the floppy before the last buffer was written and the disk directory updated (usually about 30 seconds of inactivity will trigger this), the information in the last buffer never made it to the disk, so it can't be there to be recovered.
If you manually removed the floppy before the last buffer was written and the disk directory updated ..., the information in the last buffer never made it to the disk, so it can't be there to be recovered.
Yes, that did happen once or twice, but something else happened too. The disk is half full despite ls not showing anything. The files are there, but the i-nodes or something got messed up.
You could try mounting the floppy and using dd to see what's there.
I don't understand, how does dd do that? I thought it just copies an image.
dd if=/media/floppy should do it, but check the manual pages for details and options. Note that, by setting offsets and byte counts you should be able to rebuild the files.
You refer to i-nodes on the floppy. Does that imply that you created a Linux file system on the floppy? (mkfs.e2fs, for example, does work for a floppy, but most people use floppies for porting between systems, and FAT is much more commonly used for that.)
dd if=/media/floppy should do it, but check the manual pages for details and options.
I/O error trying to copy from the unmounted disk.
Can't copy a directory after the disk is mounted.
No files copied, and I still don't understand what dd is supposed to be doing.
You refer to i-nodes on the floppy. Does that imply that you created a Linux file system on the floppy?
No, it implies that I don't know what I'm talking about. It's just a regular vfat format. All I know is that a bunch of files aren't showing up in ls anymore, and df says the disk is half full with ls showing nothing in it.