[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [annoyance/non-feature] On OS X, every process is "occupying" CWD, m

From: Chet Ramey
Subject: Re: [annoyance/non-feature] On OS X, every process is "occupying" CWD, making disk ejects impossible after cd'ing into them.
Date: Tue, 16 Jan 2018 11:41:27 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.5.2

On 1/16/18 11:26 AM, Greg Wooledge wrote:
> On Tue, Jan 16, 2018 at 10:36:47PM +0800, Danyel Bayraktar wrote:
>> Initially I thought it was specific to the terminal emulator, but it is 
>> actually due to the design of OS X. My problem is that when cd’ing into the 
>> external drive to run an `ls`, I’m not really “using” it and should be able 
>> to eject it. The eject should only be impossible for the time span a process 
>> is actually running.
> This is not unique to OS X.  Every single Unix-based operating system
> works like this.  It has nothing to do with bash.  This is nothing new.
> It has been this way since the dawn of time.  You are not going to
> change anything.

Regardless of the merits of this proposal, OS X presents its own peculiar
set of logistical problems.  Apple stopped updating bash at bash-3.2,
since they don't like GPLv3, so any change that touched the base system
in any permanent way would have to end up going through them to backport.

If you want to set your login shell to something else (e.g.,
/usr/local/bin/bash), you could experiment with making the changes yourself
and just install your locally-modified version there.

That would only help with your shell processes; any other system process
using the shell (or, say, Finder) would not be affected.


``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    address@hidden    http://tiswww.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]