From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Tue, 9 Aug 2011 18:29:36 -0400 To: 9fans@9fans.net Message-ID: <12162ede86e628dc9638b5b07f7ac1b2@coraid.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] rc scripts in /386/bin/aux Topicbox-Message-UUID: 0d5190c2-ead7-11e9-9d60-3106f5b1d025 On Tue Aug 9 18:26:01 EDT 2011, lyndon@orthanc.ca wrote: > I was surprised to stumble across a handful of rc scripts in > /386/bin/aux. Shouldn't this directory contain only 386 binary > executables? With the exception of the vmware script, none of these > are specific to the 386 hardware platform in any way. > > Shouldn't we have an /rc/bin/aux directory and do a 'bind -a > /rc/bin/aux /bin/aux' at the appropriate point during bootup? > > The candidates for relocation are cropmarks, grabit, hardcopy, and > vmware. unless something radical has happened recently, vmware only runs on 386. union directories are just one level. so if aux is in /$cputype/bin, then /rc/bin/aux will never be seen. one could make /lib/namespace more complicated to make /bin/aux a union directory as well, but that sounds like a lot of work for no particular gain. the tradition has been to copy scripts into /$cputype/bin/$somesubdir for every arch. - erik