Macintosh users may be a minority, but they are quite loyal to their operating system and loathe to give it up. Mac OS stores its files in HFS (hierarchical file system) format, which uses a return character to separate lines in text files, rather than a newline character as in Linux/UNIX. If you have files on a Macintosh floppy disk that you wish to get on your Linux system, several options are available.
Just as “m” commands deal with DOS disks, “h” commands work for Macintosh disks. These commands are named and behave just as any Linux user might expect. For example, to change directories on your Linux system, you type cd path; to do so with a Mac volume, you type hcd path. In other words, you just add an “h” as the first character of the command name. In some cases, the base command name is taken from DOS rather than UNIX—I guess to make the h tools consistent with the m tools. The most frequently used h utilities are:
hcd path: change working directory on the disk; default is the root (/) directory
hdel names: delete a file or files on the disk
hcopy source destination: copy a file to or from an HFS disk
hdir: list the files on the disk; hls also works for this purpose
hmkdir path: create a directory on the disk; hrmdir removes a directory on the disk
hmount device_name: mount the HFS disk at this location; humount unmounts the disk
Other available commands are hformat, hpwd, hrename, hvol and hatrib. For details on these HFS utilities and their options, see the man pages.
Wild cards are permitted in specifying path names, but be aware that if you use “*” to mean “every file in the directory”, it will not be interpreted that way. For example, typing hcopy * . will look for the filenames on the HFS floppy in the current directory , instead of getting all the files off the HFS floppy as you would expect.
Another method for manipulating Mac disks is the hfs shell. This shell, based on Tcl, provides the same type of options as the h commands: mount (m), umount (u), cd (c), dir (d), mkdir (m), rmdir (r), etc. The difference is only in the way the command is specified. For example, to mount the disk with hfs, you type:
hmountFinally, Robert Leslie's program xhfs provides a graphical user interface to the hfs commands. It is easy to use and quite intuitive. Just type:
xhfsand up pops a window displaying available options (see Figure 1). A click of the mouse on the button next to the option you want, and you are on your way to having those files on your system in Linux format.
If a friend sends you a Macintosh file, don't forget you need to get rid of those pesky return characters. The tr command (see “A Little Devil Called tr” by Hans de Vreught, LJ, September 1998) is the best tool for doing this. Typing
tr '\015' '\012' <
will do the trick.
Another good resource for these commands and others is Linux for Dummies Quick Reference, 2nd Edition by Phil Hughes.
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!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
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