Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
tar cvpf - / --exclude=/home/jake/backup --exclude=/proc --exclude=/mnt | split -b 1000m - linux
in order to back up my HD, so I can copy it to a bigger one. The thing is, tar isn't excluding the directories I want it to. My assumption is that I put the exclude arguments in the wrong spot. When I run this, it's in /home/jake/backup(a NFS mounted drive, hence the splitting), because otherwise it just writes the split files directly to whatever directory I'm in.
what I ended up doing was mounting my root drive again, and just tarring that directory, it excludes /proc and /mnt, becuase I just mounted the root partition. I just realized that I forgot to exclude the backup directory. Bummer. Maybe I'll try the command above tonight(as I'm at school right now)
actuallly, as the backup directory was mounted across a network, it didn't get mounted w/ the root parition. However, where I mounted the root partition(/floppy), it copied the directory it was mounted to as well. So now when I try and untar it, it's going to untar to /floppy/<everything that was previously in />. Is there any way to fix this? I was thinking, in /floppy
I don't know either. I actually ended up using the command
tar cvpf - floppy/ | split -b 1000m - /home/jake/backup/linux
where floppy is the drive mounted a second time. It worked for my linux parition, but when I tried the above command to tar up my windows partition(changed /home/jake/backup/linux to /home/jake/backup/windows), it quit on me, and it was almost done. It had like 1.6 GB more to go, and then it quit w/ the error
Did tar list any previous errors? I've never seen that message by itself but, since you're using the verbose flag, it'd be hard to notice an error. Try routing standard out to /dev/null or not using the verbose flag?
I thought the 'v' meant verbose? I didn't see any other errors, but then again, I wasn't watching every line that came across the screen. How do I route stdout to /dev/null when it's piped, the way it currently is?
The 'v' does mean verbose. It lists all of the names of the files as it processes them. If you have that on, a non-fatal error might be displayed and then float off of the top of the screen. Honestly, I'm not sure about the pipe... some kind of weird terminal magic makes that work.
If you leave the v flag out, it will still display the error messages but not the names of the files.