Dealing with Spaces in Filenames
Just grabbed a copy of the magazine from the bookstore but it was still the February edition. I am responding to callout at the end of the "Working the Shell" article on "Dealing with Spaces in Filenames" by Dave Taylor. This is my first time on the forum and I couldn't find an existing thread on this so I'm starting this one. Sorry if this is the wrong place to do this.
I'm a little unclear about some things Dave says on IFS. At one point, he quotes the Bash man page's IFS entry under the Shell Variables heading and then goes on to say that this doesn't really solve our filename problem. Later in the article he includes IFS in his possible solution paths. I'm not really sure if this is contradictory here or if I'm missing something.
As it happens, I do actually use IFS for exactly this purpose. The Bash man page is in dire need of an update. This is unfortunate because IFS is used in other areas of the Bash shell. This entry in the man page should reflect that broader scope. Actually, if you search the man page for IFS, you'll see many hits, notably under the Expansion > Word Splitting heading.
Here is how I use IFS for this purpose:
#!/bin/sh FILENAMES=$(ls) OIFS="$IFS" IFS=$'\n' for x in $FILENAMES do echo "$x" done IFS="$OIFS"
By setting IFS in this way, we are removing the space and tab portions of its definition. Now we are getting exactly what we want which is separation, or word splitting, on newline characters only.
It's important to note that a lot of people believe 'unset IFS' will revert revert IFS back to the default value. This is actually not true. This will really just set IFS to null. According to the man page, (which is accurate this time) when IFS is set to null and is used by a builtin it is assumed to be a space. This is in contrast to the default value of "\s\t\n". By creating and setting OIFS to equal IFS (the double quotes here are required to make this work correctly!) we can restore it to the original value later.
Is this what Dave was looking for?
P.S. The example script above will also handle the quoted filenames from the article.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide