SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
I plug in my mp3 player or flash stick in usb port then gnome dropline mount it. Then when I try to upload some files copy screen appears and everything seems fine, but when I unplug and plug again the device there is no newly uploaded information on it(like I didn't upload anything). When I try again it usually works, but not the first time.
Perhaps you're just not giving it enough time. Most disk writing is done asynchronously, which means that the data is actually stored in a buffer for some time before it's written to the disk. Always make sure you properly unmount a drive before you remove it, or use the "safely remove" option if it has one, to ensure that the buffered data gets written out. You can seriously corrupt your filesystem if you don't (been there, done that).
Right-click the icon on the GNOME desktop and "eject" or "unmount" it first. Linux doesn't actually write to the disk immediately (by default). Since flash memory must be written in blocks of a specific size, data is written from a RAM buffer to avoid damage to the disk from rapid data writing. When you "eject" it, the data is finalized and written from the buffer to the flash memory. On Windows, this is similar, but people more often end up with corrupt data from unsafe ejects rather than data that isn't written at all.
Right-click the icon on the GNOME desktop and "eject" or "unmount" it first. Linux doesn't actually write to the disk immediately (by default). Since flash memory must be written in blocks of a specific size, data is written from a RAM buffer to avoid damage to the disk from rapid data writing. When you "eject" it, the data is finalized and written from the buffer to the flash memory. On Windows, this is similar, but people more often end up with corrupt data from unsafe ejects rather than data that isn't written at all.
Hi,
Might I add that you can use the 'sync' command from the cli. This will force the buffers to be written to the device.
From cli do 'info coreutils sync' to get the information.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
