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.
Try it and find out, i forget what /dev name is for jump drives.
In any case, if you have lots of free disk space, why not create a lookback device?
dd if=/dev/zero of=./loopdevice bs=512 count=1024
change the "count" number to the size you want, or remove it all together. If you remove it, then dd will run until all your free disk space is eaten up, so if you do this, monitor your free disk space in another terminal, and kill dd (by using ctrl-c) when it gets about as big as you want.
The command will create a empty file of a size of your choosing. You can then create a filesystem on by:
mounting it the device requires another option to mount:
Do note that flash media file systems have a limited number of writes (10,000-100,000). This means that journaling file systems may not be the best in the long run, as the journal will incur increased numbers of writes.
That being said, if it's just for experimentation (or you're willing to trash the drive after 100,000 writes... which is probably a long way off anyway) it's better than destroying your hard drive.
Remember that most USB-based drives will show up as /dev/sd*.
Depending on your perspective, that number can be a little or a lot. For occasional file transfers, you're more likely to physically break it first. If you (for some reason) want to run a database off it... well, you're likely to update it a few hundred times (minimum) a day.
Do note that flash media file systems have a limited number of writes (10,000-100,000)
Good point. Not enough people know about that. That's why I replaced some of my . directories and most-often-written-to directories, such as documents and game saves, with symlinks to hdd locations. Note that you can symlink from ext->FAT but not FAT->anything.
In my case it has been for experimentation and portablility. Plus, the drive I'm using is a lost-and-found 1GB Memorex. Somebody lost it, I found it. So when it dies it'll be no big loss because I do keep it backed up regularly.