[9fans] rc scripts in /386/bin/aux

[9fans] rc scripts in /386/bin/aux

[Lyndon Nerenberg (VE6BBM/VE7TFX)]

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.

Re: [9fans] rc scripts in /386/bin/aux

[erik quanstrom]

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

Re: [9fans] rc scripts in /386/bin/aux

[Lyndon Nerenberg (VE6BBM/VE7TFX)]

> 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 alternate pain is in the respective mkfiles.  Munging the namespace
(once) seems like the cleaner approach in my view.

Re: [9fans] rc scripts in /386/bin/aux

[Jacob Todd]

[-- Attachment #1: Type: text/plain, Size: 297 bytes --]

On Aug 9, 2011 6:30 PM, "erik quanstrom" <quanstro@labs.coraid.com> wrote:
>
> On Tue Aug  9 18:26:01 EDT 2011, lyndon@orthanc.ca wrote:
> the tradition has been to copy scripts into /$cputype/bin/$somesubdir
> for every arch.
>
I've always been under the impression they went in /rc/bin/.

[-- Attachment #2: Type: text/html, Size: 456 bytes --]

Re: [9fans] rc scripts in /386/bin/aux

[John Floren]

On Tue, Aug 9, 2011 at 3:54 PM, Jacob Todd <jaketodd422@gmail.com> wrote:
>
> On Aug 9, 2011 6:30 PM, "erik quanstrom" <quanstro@labs.coraid.com> wrote:
>>
>> On Tue Aug  9 18:26:01 EDT 2011, lyndon@orthanc.ca wrote:
>> the tradition has been to copy scripts into /$cputype/bin/$somesubdir
>> for every arch.
>>
> I've always been under the impression they went in /rc/bin/.

Try creating /rc/bin/aux and sticking a file in there--can you see it
if you do 'ls /bin/aux'? Not unless you do a 'bind -a /rc/bin/aux
/bin/aux'. It's an artifact of the fact that we don't have recursive
unions under Plan 9--we can either specifically bind every
subdirectory of /rc/bin into /bin, or we can just stick the scripts
into /386/bin/subdir/

John

Re: [9fans] rc scripts in /386/bin/aux

[erik quanstrom]

On Tue Aug  9 18:49:07 EDT 2011, lyndon@orthanc.ca wrote:
> > 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 alternate pain is in the respective mkfiles.  Munging the namespace
> (once) seems like the cleaner approach in my view.

to paraphrase russ, the bike shed is painted and the painter
has left.

- erik

Re: [9fans] rc scripts in /386/bin/aux

[Lyndon Nerenberg (VE6BBM/VE7TFX)]

> to paraphrase russ, the bike shed is painted and the painter
> has left.

And there's nothing worse than a fucking art critic.

Re: [9fans] rc scripts in /386/bin/aux

[andrey mirtchovski]

Please don't touch the artwork.

Do work carefully amongst the artwork.

Re: [9fans] rc scripts in /386/bin/aux

[Lyndon Nerenberg (VE6BBM/VE7TFX)]

> Please don't touch the artwork.
>
> Do work carefully amongst the artwork.

And never, ever, ask the artist for his motivation.