From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] rc scripts in /386/bin/aux
Date: Tue, 9 Aug 2011 18:29:36 -0400 [thread overview]
Message-ID: <12162ede86e628dc9638b5b07f7ac1b2@coraid.com> (raw)
In-Reply-To: <dbf351c577fa9336d0de898880908f55@orthanc.ca>
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
next prev parent reply other threads:[~2011-08-09 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 22:24 Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-08-09 22:29 ` erik quanstrom [this message]
2011-08-09 22:48 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-08-10 0:06 ` erik quanstrom
2011-08-10 0:07 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-08-10 0:24 ` andrey mirtchovski
2011-08-10 0:28 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-08-09 22:54 ` Jacob Todd
2011-08-09 22:59 ` John Floren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12162ede86e628dc9638b5b07f7ac1b2@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).