Red HatThis forum is for the discussion of Red Hat 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.
or close to that (refer to man page of find, if that doesn't work). Of course you can use any parameters find supports, to create the list of files to delete. Before actually removing, it's not a bad idea to run 'ls' instead of 'rm', for example, to have find print out the list it's going to work on, so you know what you're doing. Find is a nice tool for things like that, in addition to grep, xargs and such.
Yet another way, if your shell is bash and extglob is enabled (I'm sure other shells have things like it and more) is to do something like
Code:
rm PATH/!(*.txt)
I'm not very comfortable with that and it will try and fail to remove subdirectories, if any, but it's a possibility.
On the find, to follow along with b0uncer and to get closer to what you were asking, you could do
Code:
find . -type f ! -name '*.txt' -execdir rm {} +
I'd leave in BrianK's '-type f' to avoid just that subdir problem and find can find negated expressions. (-execdir is just a bit of paranoia.) If recursing subdirs is a problem, there's '-maxdepth 1'. (A lot of these are GNUisms.)
Doesn't much matter, as you have your problem solved but it might be useful to others with similar issues.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.