[9fans] /lib/namespace vs /rc/bin/*rc - Plan9
This is a discussion on [9fans] /lib/namespace vs /rc/bin/*rc - Plan9 ; why are some devices bound in /lib/namespace while some others
are bound in /rc/bin/*rc? for example: '#$'.
- erik...
-
[9fans] /lib/namespace vs /rc/bin/*rc
why are some devices bound in /lib/namespace while some others
are bound in /rc/bin/*rc? for example: '#$'.
- erik
-
Re: [9fans] /lib/namespace vs /rc/bin/*rc
> why are some devices bound in /lib/namespace while some others
> are bound in /rc/bin/*rc? for example: '#$'.
/lib/namespace gets run every time you
create a fresh name space.
termrc and cpurc are for initializing the machine.
for example,
'#t' should be in the termrc/cpurc so that the
bootup programs can have it, but it doesn't
need to be in everyone's.
russ
-
Re: [9fans] /lib/namespace vs /rc/bin/*rc
right. i'm not sure i see the advantage of hiding #t. surely
this isn't a performance argument?
- erik
On Tue Apr 24 17:47:12 EDT 2007, rsc@swtch.com wrote:
> > why are some devices bound in /lib/namespace while some others
> > are bound in /rc/bin/*rc? for example: '#$'.
>
> /lib/namespace gets run every time you
> create a fresh name space.
> termrc and cpurc are for initializing the machine.
>
> for example,
> '#t' should be in the termrc/cpurc so that the
> bootup programs can have it, but it doesn't
> need to be in everyone's.
>
> russ
-
Re: [9fans] /lib/namespace vs /rc/bin/*rc
> right. i'm not sure i see the advantage of hiding #t. surely
> this isn't a performance argument?
i see no point to putting a file into everyone's
name space when only one user has permission
to open it or when approximately everyone will
have no need for it.
you are free to customize the system if you wish
to use it in a different way.
russ