> surely : echo bad permissions >[1=2]
I think you may be right.
On 12/04/2010 06:34, EBo wrote:
if(! ls -ld $home>[2=] | grep -s '^d-rwx.* '$user){
echo bad permissions
exit homeless
}
surely : echo bad permissions >[1=2]
EBo said:
>
> > > Hunting on the we it looks like Ron Cox is the goto person for that
> > > (http://bitbucket.org/rsc/vx32/changesets/ dated 2009-12-27):
> >
> > Ah, my bad. I was looking at the old, pre-bitbucket repository (in my
> > defense, still linked from swtch.com/9vx). I take it back.
> > Hunting on the we it looks like Ron Cox is the goto person for that
> > (http://bitbucket.org/rsc/vx32/changesets/ dated 2009-12-27):
>
> Ah, my bad. I was looking at the old, pre-bitbucket repository (in my
> defense, still linked from swtch.com/9vx). I take it back.
hmmm... the sources I a
On Apr 12, 2010, at 22:53, EBo wrote:
On Apr 12, 2010, at 11:23, hiro wrote:
and what is src/9vx/a/devcap.c ?
As far as my system and (as far as I can tell) the
Mercurial repository: fictional. Something you'd
like to share with the class?
Hunting on the we it looks like Ron Cox is the got
> On Apr 12, 2010, at 11:23, hiro wrote:
>
> > and what is src/9vx/a/devcap.c ?
>
> As far as my system and (as far as I can tell) the
> Mercurial repository: fictional. Something you'd
> like to share with the class?
Hunting on the we it looks like Ron Cox is the goto person for that
(http://b
On Apr 12, 2010, at 11:23, hiro wrote:
and what is src/9vx/a/devcap.c ?
As far as my system and (as far as I can tell) the
Mercurial repository: fictional. Something you'd
like to share with the class?
PGP.sig
Description: This is a digitally signed message part
> > the problem you're addressing can't be addressed well through #Z.
> > unix systems act differently than plan 9 ones do. there are a host
> > of locking, etc. questions that #Z doesn't handle either. it would be
> > easier
> > to use a plan 9 fs (ken fs, cwfs, fossil). then you wouldn't need
and what is src/9vx/a/devcap.c ?
On 4/12/10, erik quanstrom wrote:
>> 2010/4/12 hiro <23h...@googlemail.com>:
>> > I have not the slightest idea about the complexity involved; And I
>> > think I misunderstand how much of plan9 is actually running in a
>> > sandbox. But what if we wanted to have a
And the users are running in single sandboxes?
On 4/12/10, erik quanstrom wrote:
>> 2010/4/12 hiro <23h...@googlemail.com>:
>> > I have not the slightest idea about the complexity involved; And I
>> > think I misunderstand how much of plan9 is actually running in a
>> > sandbox. But what if we wa
2010/4/12 erik quanstrom :
>> 2010/4/12 hiro <23h...@googlemail.com>:
>> > I have not the slightest idea about the complexity involved; And I
>> > think I misunderstand how much of plan9 is actually running in a
>> > sandbox. But what if we wanted to have a working security system for
>> > multiple
> 2010/4/12 hiro <23h...@googlemail.com>:
> > I have not the slightest idea about the complexity involved; And I
> > think I misunderstand how much of plan9 is actually running in a
> > sandbox. But what if we wanted to have a working security system for
> > multiple users in 9vx. Would it be - or
2010/4/12 hiro <23h...@googlemail.com>:
> I have not the slightest idea about the complexity involved; And I
> think I misunderstand how much of plan9 is actually running in a
> sandbox. But what if we wanted to have a working security system for
> multiple users in 9vx. Would it be - or is it - po
I have not the slightest idea about the complexity involved; And I
think I misunderstand how much of plan9 is actually running in a
sandbox. But what if we wanted to have a working security system for
multiple users in 9vx. Would it be - or is it - possible?
On 4/12/10, erik quanstrom wrote:
>> C
> you must also exit if ~ $user none. i'd also recommend
> aborting if ~ $home /. you don't want none making
> files in /. on a regular plan 9 system, that's no worry, but
> 9vx, ...
I also tried to add test -z $user for the null string. It turns out that
user=`{cat /dev/user} dies with the e
> Can't we then fix 9vx?
> (Stepping in to the tradition of concern of reception: This is not a
> rhetoric question)
it's not 9vx, but #Z. and no, #Z is going to be limited by
the underlying system.
- erik
On 4/12/10, erik quanstrom wrote:
>> Following on several peoples advice and a suggested code snippet from Erik
>> I've added the following before the check for profile:
>>
>> if(! test -d $home){
>> echo no home directory $home
>> exit homeless
>> }
>> if(! ls -ld $home >[2=] | grep -s
erik quanstrom said:
> > Following on several peoples advice and a suggested code snippet from Erik
> > I've added the following before the check for profile:
> >
> > if(! test -d $home){
> > echo no home directory $home
> > exit homeless
> > }
> > if(! ls -ld $home >[2=] | grep -s '^d-r
> Following on several peoples advice and a suggested code snippet from Erik
> I've added the following before the check for profile:
>
> if(! test -d $home){
> echo no home directory $home
> exit homeless
> }
> if(! ls -ld $home >[2=] | grep -s '^d-rwx.* '$user){
> echo bad perm
Anthony Sorace said:
> On a "real" plan 9 system, you create the user at the file server
> console, then log in as that user and run newuser. That first step
> creates /usr/$user. The analogue in 9vx is at least 'mkdir /usr/
> $user', and (less likely) possibly creating the actual user in th
> create the user dir on the host machine. run 9vx -u $user and then run
> /sys/lib/newuser.
>
> you seem to be following the wiki instructions on how to add a new
> user. they are not valid for 9vx, since it usually uses the hosts
> filesystem.
is there already a 9vx specific tutorial?
EBo -
Anthony Sorace said:
> On a "real" plan 9 system, you create the user at the file server
> console, then log in as that user and run newuser. That first step
> creates /usr/$user. The analogue in 9vx is at least 'mkdir /usr/
> $user', and (less likely) possibly creating the actual user in th
On a "real" plan 9 system, you create the user at the file server
console, then log in as that user and run newuser. That first step
creates /usr/$user. The analogue in 9vx is at least 'mkdir /usr/
$user', and (less likely) possibly creating the actual user in the
unix world, depending on yo
On Sun, Apr 11, 2010 at 7:04 PM, EBo wrote:
>
>> newuser assumes that your home directory exists, and on a
>> normal plan 9 install, it's likely not possible to create anything
>> in /usr without doing it on the fs console.
>
> Maybe I am missing something here, but this is not a normal plan9 inst
> newuser assumes that your home directory exists, and on a
> normal plan 9 install, it's likely not possible to create anything
> in /usr without doing it on the fs console.
Maybe I am missing something here, but this is not a normal plan9 install, but
9vx. There I can create a user's directory
> When we try to cd to $home, it does not exist (as checked by the previous if),
> and $cwd is set to / by default... The following patch simply makes $home
> before cd'ing to it.
>
> Is this supposed to be the expected nehaviour?
>
> EBo --
>
> =
> --- a/sys/lib/newus
I'm playing around with 9vx and have split up (re)building 9vx from the the
9vx root file system provided in the tarball 9vx-0.12.tar.gz
When I first start 9vx from a clean build and run /sys/lib/newuser it builds
the user directory in /$user instead of /usr/$user. The problem appears to
arize f
27 matches
Mail list logo
