Re: [9fans] questions whose answers are only known by people who abandoned 9fans

[Jules Merit]

Begin Game Romero

On Oct 17, 2017 6:22 PM, "Kurt H Maier"  wrote:

> On Wed, Oct 18, 2017 at 11:56:12AM +1100, Rob Pike wrote:
> > It went away because it wasn't necessary.
>
> Thanks for the insight.
>
> khm
>
>

Re: [9fans] questions whose answers are only known by people who abandoned 9fans

[Kurt H Maier]

On Wed, Oct 18, 2017 at 11:56:12AM +1100, Rob Pike wrote:
> It went away because it wasn't necessary.

Thanks for the insight.

khm

Re: [9fans] questions whose answers are only known by people who abandoned 9fans

[Rob Pike]

It went away because it wasn't necessary.

-rob


On Wed, Oct 18, 2017 at 11:50 AM, Kurt H Maier  wrote:

> On Tue, Oct 17, 2017 at 05:46:22PM -0700, Kurt H Maier wrote:
> >
> > implementation of sam, the '@' operator (which behaved like '*' except
>
> The '@' operator (c=ANYNL) behaved like '.' (c=ANY) not '*' (c=STAR).
>
> Apologies for the egregious misinformation,
> khm
>
>

Re: [9fans] questions whose answers are only known by people who abandoned 9fans

[Kurt H Maier]

On Tue, Oct 17, 2017 at 05:46:22PM -0700, Kurt H Maier wrote:
> 
> implementation of sam, the '@' operator (which behaved like '*' except

The '@' operator (c=ANYNL) behaved like '.' (c=ANY) not '*' (c=STAR).  

Apologies for the egregious misinformation,
khm

[9fans] questions whose answers are only known by people who abandoned 9fans

[Kurt H Maier]

Speaking of letter capitalization, 

Between the v10/jerq implementation of sam and the plan 9
implementation of sam, the '@' operator (which behaved like '*' except
it also matched newlines) was removed.

Please make shit up to explain this and/or tell us if you actually know
why.

Thanks,
khm

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Tiago Natel]

AFAIK, NPROC is a env variable of mk.

On Oct 17, 2017 13:08, "Giacomo Tesio"  wrote:

> Also, why NPROC has been left uppercase? :-)
>
>
> Giacomo
>
> 2017-10-17 17:45 GMT+02:00 Giacomo Tesio :
>
>> In *rc* you use quotation marks when you want a syntax character to
>>> appear in an argument, or an argument that is the empty string, and at no
>>> other time. IFS is no longer used, *except in the one case where it was
>>> indispensable*: converting command output into argument lists during
>>> command substitution.
>>
>>
>> So, I undestood: it used to use IFS in that one case.
>>
>> I got it now: the fact that IFS was named ifs was not a relevant for the
>> discourse, and thus omitted.
>>
>> Still I'm a bit surprised that such change in the conventions provides no
>> practical advantage: the taste changes with age, but costs accumulate... :-)
>>
>>
>> BTW, thanks for your answers!
>>
>>
>> Giacomo
>>
>>
>> 2017-10-17 17:18 GMT+02:00 Charles Forsyth :
>>
>>> since for example the original Rc paper still referred to $IFS.
>>>
>>>
>>> really? the only references to IFS I can find are in comparisons of $ifs
>>> to the Bourne shell's $IFS
>>>
>>> On 17 October 2017 at 16:05, Giacomo Tesio  wrote:
>>>
 Really? Just aesthetics? :-o
 I supposed it had some practical goal I was missing, since for example
 the original Rc paper still referred to $IFS.

 This would flips the question a bit: I wonder why the same designers
 chose uppercase variable names while designing Unix... :-)


 Giacomo

 2017-10-17 16:39 GMT+02:00 Dan Cross :

> On Tue, Oct 17, 2017 at 10:38 AM, Giacomo Tesio 
> wrote:
> > Out of curiosity, do anybody know why Plan9 designers chose lowercase
> > variables over uppercase ones?
> >
> > At first, given the different conventions between rc and sh (eg
> $path is an
> > array, while $PATH is a string), I supposed Plan 9 designers wanted
> to
> > prevent conflict with unix tools relying to the older conventions.
> >
> > However, I'm not sure this was the main reason, as this also open to
> subtle
> > issues: if a unix shell modifies $IFS and then invoke an rc script,
> such
> > script will ignore the change and keep using the previous $ifs.
> >
> >
> > As far as I can see, APE does not attempt any translation between
> the two
> > conventions, so maybe I'm just missing something obvious...
> >
> >
> > Do anyone know what considerations led to such design decision?
>
> Aesthetics.
>
>

>>>
>>
>

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Charles Forsyth]

WAT! or should that be "wat!"

On 17 October 2017 at 22:49, Jules Merit 
wrote:

> Gun Control UTF8, sgi 0xfbc bowling for columbine
>
> On Tue, Oct 17, 2017 at 2:45 PM, Jules Merit
>  wrote:
> > E4M1 Charles, dm
> > E3M8 Dis 9/11
> >
> > On Tue, Oct 17, 2017 at 2:12 PM, Jules Merit
> >  wrote:
> >> 0x8000 ... obviously it wastes time when running plan9 as RTL in a
> >> HDL simulator.
> >>
> >> On Tue, Oct 17, 2017 at 11:28 AM, Anthony Martin 
> wrote:
> >>> Note that variables in the Mashey shell were single letters
> >>> in lower-case. $p was similar to $PATH in the Bourne shell.
> >>>
> >>> Maybe Tom just split the difference. Have you asked him? :)
> >>>
> >>>   Anthony
> >>>
>
>

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Jules Merit]

Gun Control UTF8, sgi 0xfbc bowling for columbine

On Tue, Oct 17, 2017 at 2:45 PM, Jules Merit
 wrote:
> E4M1 Charles, dm
> E3M8 Dis 9/11
>
> On Tue, Oct 17, 2017 at 2:12 PM, Jules Merit
>  wrote:
>> 0x8000 ... obviously it wastes time when running plan9 as RTL in a
>> HDL simulator.
>>
>> On Tue, Oct 17, 2017 at 11:28 AM, Anthony Martin  wrote:
>>> Note that variables in the Mashey shell were single letters
>>> in lower-case. $p was similar to $PATH in the Bourne shell.
>>>
>>> Maybe Tom just split the difference. Have you asked him? :)
>>>
>>>   Anthony
>>>

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Jules Merit]

E4M1 Charles, dm
E3M8 Dis 9/11

On Tue, Oct 17, 2017 at 2:12 PM, Jules Merit
 wrote:
> 0x8000 ... obviously it wastes time when running plan9 as RTL in a
> HDL simulator.
>
> On Tue, Oct 17, 2017 at 11:28 AM, Anthony Martin  wrote:
>> Note that variables in the Mashey shell were single letters
>> in lower-case. $p was similar to $PATH in the Bourne shell.
>>
>> Maybe Tom just split the difference. Have you asked him? :)
>>
>>   Anthony
>>

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Jules Merit]

0x8000 ... obviously it wastes time when running plan9 as RTL in a
HDL simulator.

On Tue, Oct 17, 2017 at 11:28 AM, Anthony Martin  wrote:
> Note that variables in the Mashey shell were single letters
> in lower-case. $p was similar to $PATH in the Bourne shell.
>
> Maybe Tom just split the difference. Have you asked him? :)
>
>   Anthony
>

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Anthony Martin]

Note that variables in the Mashey shell were single letters
in lower-case. $p was similar to $PATH in the Bourne shell.

Maybe Tom just split the difference. Have you asked him? :)

  Anthony

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Dan Cross]

On Tue, Oct 17, 2017 at 12:04 PM, Giacomo Tesio  wrote:
> Also, why NPROC has been left uppercase? :-)

I once had a mathematics professor who advised me not to look for
rationality or logic in nomenclature. I've found that, since taking
this advice to heart, my life is much less stressful.

- Dan C.

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Giacomo Tesio]

2017-10-17 18:00 GMT+02:00 Skip Tavakkolian :

> On Tue, Oct 17, 2017, 8:05 AM Giacomo Tesio  wrote:
>
>> Really? Just aesthetics? :-o
>>
>
>
>> This would flips the question a bit: I wonder why the same designers
>> chose uppercase variable names while designing Unix... :-)
>>
>
> Programs can evolve, why not names? There was no expectation that sh
> scripts would work in rc.
>


They can! For sure! But usually they evolve towards a goal... and I'm a
curious person.. :-)

Also this is not about sh scripts run by rc, but sh script run by an sh
shell started by rc.
Or, rc scripts run by an rc shell invoked by an sh.

Just to explain, for example, you could have an sh script that changes
$USER and then invoke psu that would keep using the previous $user.


Giacomo

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Giacomo Tesio]

Also, why NPROC has been left uppercase? :-)


Giacomo

2017-10-17 17:45 GMT+02:00 Giacomo Tesio :

> In *rc* you use quotation marks when you want a syntax character to
>> appear in an argument, or an argument that is the empty string, and at no
>> other time. IFS is no longer used, *except in the one case where it was
>> indispensable*: converting command output into argument lists during
>> command substitution.
>
>
> So, I undestood: it used to use IFS in that one case.
>
> I got it now: the fact that IFS was named ifs was not a relevant for the
> discourse, and thus omitted.
>
> Still I'm a bit surprised that such change in the conventions provides no
> practical advantage: the taste changes with age, but costs accumulate... :-)
>
>
> BTW, thanks for your answers!
>
>
> Giacomo
>
>
> 2017-10-17 17:18 GMT+02:00 Charles Forsyth :
>
>> since for example the original Rc paper still referred to $IFS.
>>
>>
>> really? the only references to IFS I can find are in comparisons of $ifs
>> to the Bourne shell's $IFS
>>
>> On 17 October 2017 at 16:05, Giacomo Tesio  wrote:
>>
>>> Really? Just aesthetics? :-o
>>> I supposed it had some practical goal I was missing, since for example
>>> the original Rc paper still referred to $IFS.
>>>
>>> This would flips the question a bit: I wonder why the same designers
>>> chose uppercase variable names while designing Unix... :-)
>>>
>>>
>>> Giacomo
>>>
>>> 2017-10-17 16:39 GMT+02:00 Dan Cross :
>>>
 On Tue, Oct 17, 2017 at 10:38 AM, Giacomo Tesio 
 wrote:
 > Out of curiosity, do anybody know why Plan9 designers chose lowercase
 > variables over uppercase ones?
 >
 > At first, given the different conventions between rc and sh (eg $path
 is an
 > array, while $PATH is a string), I supposed Plan 9 designers wanted to
 > prevent conflict with unix tools relying to the older conventions.
 >
 > However, I'm not sure this was the main reason, as this also open to
 subtle
 > issues: if a unix shell modifies $IFS and then invoke an rc script,
 such
 > script will ignore the change and keep using the previous $ifs.
 >
 >
 > As far as I can see, APE does not attempt any translation between the
 two
 > conventions, so maybe I'm just missing something obvious...
 >
 >
 > Do anyone know what considerations led to such design decision?

 Aesthetics.


>>>
>>
>

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Skip Tavakkolian]

On Tue, Oct 17, 2017, 8:05 AM Giacomo Tesio  wrote:

> Really? Just aesthetics? :-o
>


> This would flips the question a bit: I wonder why the same designers chose
> uppercase variable names while designing Unix... :-)
>

Programs can evolve, why not names? There was no expectation that sh
scripts would work in rc.


>
> Giacomo
>
> 2017-10-17 16:39 GMT+02:00 Dan Cross :
>
>> On Tue, Oct 17, 2017 at 10:38 AM, Giacomo Tesio  wrote:
>> > Out of curiosity, do anybody know why Plan9 designers chose lowercase
>> > variables over uppercase ones?
>> >
>> > At first, given the different conventions between rc and sh (eg $path
>> is an
>> > array, while $PATH is a string), I supposed Plan 9 designers wanted to
>> > prevent conflict with unix tools relying to the older conventions.
>> >
>> > However, I'm not sure this was the main reason, as this also open to
>> subtle
>> > issues: if a unix shell modifies $IFS and then invoke an rc script, such
>> > script will ignore the change and keep using the previous $ifs.
>> >
>> >
>> > As far as I can see, APE does not attempt any translation between the
>> two
>> > conventions, so maybe I'm just missing something obvious...
>> >
>> >
>> > Do anyone know what considerations led to such design decision?
>>
>> Aesthetics.
>>
>>
>

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Teodoro Santoni]

Hi,

2017-10-17 16:38 GMT+02:00, Giacomo Tesio :
> Out of curiosity, do anybody know why Plan9 designers chose lowercase
> variables over uppercase ones?
>
> At first, given the different conventions between rc and sh (eg $path is an
> array, while $PATH is a string), I supposed Plan 9 designers wanted to
> prevent conflict with unix tools relying to the older conventions.
>
> However, I'm not sure this was the main reason, as this also open to subtle
> issues: if a unix shell modifies $IFS and then invoke an rc script, such
> script will ignore the change and keep using the previous $ifs.
>
>
> As far as I can see, APE does not attempt any translation between the two
> conventions, so maybe I'm just missing something obvious...
>
>
> Do anyone know what considerations led to such design decision?
>
>
> Giacomo
>


Probably a matter of taste and different user behaviours, plan9
developers weren't just the same developers from unix.

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Giacomo Tesio]

>
> In *rc* you use quotation marks when you want a syntax character to
> appear in an argument, or an argument that is the empty string, and at no
> other time. IFS is no longer used, *except in the one case where it was
> indispensable*: converting command output into argument lists during
> command substitution.


So, I undestood: it used to use IFS in that one case.

I got it now: the fact that IFS was named ifs was not a relevant for the
discourse, and thus omitted.

Still I'm a bit surprised that such change in the conventions provides no
practical advantage: the taste changes with age, but costs accumulate... :-)


BTW, thanks for your answers!


Giacomo


2017-10-17 17:18 GMT+02:00 Charles Forsyth :

> since for example the original Rc paper still referred to $IFS.
>
>
> really? the only references to IFS I can find are in comparisons of $ifs
> to the Bourne shell's $IFS
>
> On 17 October 2017 at 16:05, Giacomo Tesio  wrote:
>
>> Really? Just aesthetics? :-o
>> I supposed it had some practical goal I was missing, since for example
>> the original Rc paper still referred to $IFS.
>>
>> This would flips the question a bit: I wonder why the same designers
>> chose uppercase variable names while designing Unix... :-)
>>
>>
>> Giacomo
>>
>> 2017-10-17 16:39 GMT+02:00 Dan Cross :
>>
>>> On Tue, Oct 17, 2017 at 10:38 AM, Giacomo Tesio 
>>> wrote:
>>> > Out of curiosity, do anybody know why Plan9 designers chose lowercase
>>> > variables over uppercase ones?
>>> >
>>> > At first, given the different conventions between rc and sh (eg $path
>>> is an
>>> > array, while $PATH is a string), I supposed Plan 9 designers wanted to
>>> > prevent conflict with unix tools relying to the older conventions.
>>> >
>>> > However, I'm not sure this was the main reason, as this also open to
>>> subtle
>>> > issues: if a unix shell modifies $IFS and then invoke an rc script,
>>> such
>>> > script will ignore the change and keep using the previous $ifs.
>>> >
>>> >
>>> > As far as I can see, APE does not attempt any translation between the
>>> two
>>> > conventions, so maybe I'm just missing something obvious...
>>> >
>>> >
>>> > Do anyone know what considerations led to such design decision?
>>>
>>> Aesthetics.
>>>
>>>
>>
>

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Charles Forsyth]

>
> since for example the original Rc paper still referred to $IFS.


really? the only references to IFS I can find are in comparisons of $ifs to
the Bourne shell's $IFS

On 17 October 2017 at 16:05, Giacomo Tesio  wrote:

> Really? Just aesthetics? :-o
> I supposed it had some practical goal I was missing, since for example the
> original Rc paper still referred to $IFS.
>
> This would flips the question a bit: I wonder why the same designers chose
> uppercase variable names while designing Unix... :-)
>
>
> Giacomo
>
> 2017-10-17 16:39 GMT+02:00 Dan Cross :
>
>> On Tue, Oct 17, 2017 at 10:38 AM, Giacomo Tesio  wrote:
>> > Out of curiosity, do anybody know why Plan9 designers chose lowercase
>> > variables over uppercase ones?
>> >
>> > At first, given the different conventions between rc and sh (eg $path
>> is an
>> > array, while $PATH is a string), I supposed Plan 9 designers wanted to
>> > prevent conflict with unix tools relying to the older conventions.
>> >
>> > However, I'm not sure this was the main reason, as this also open to
>> subtle
>> > issues: if a unix shell modifies $IFS and then invoke an rc script, such
>> > script will ignore the change and keep using the previous $ifs.
>> >
>> >
>> > As far as I can see, APE does not attempt any translation between the
>> two
>> > conventions, so maybe I'm just missing something obvious...
>> >
>> >
>> > Do anyone know what considerations led to such design decision?
>>
>> Aesthetics.
>>
>>
>

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Giacomo Tesio]

Really? Just aesthetics? :-o
I supposed it had some practical goal I was missing, since for example the
original Rc paper still referred to $IFS.

This would flips the question a bit: I wonder why the same designers chose
uppercase variable names while designing Unix... :-)


Giacomo

2017-10-17 16:39 GMT+02:00 Dan Cross :

> On Tue, Oct 17, 2017 at 10:38 AM, Giacomo Tesio  wrote:
> > Out of curiosity, do anybody know why Plan9 designers chose lowercase
> > variables over uppercase ones?
> >
> > At first, given the different conventions between rc and sh (eg $path is
> an
> > array, while $PATH is a string), I supposed Plan 9 designers wanted to
> > prevent conflict with unix tools relying to the older conventions.
> >
> > However, I'm not sure this was the main reason, as this also open to
> subtle
> > issues: if a unix shell modifies $IFS and then invoke an rc script, such
> > script will ignore the change and keep using the previous $ifs.
> >
> >
> > As far as I can see, APE does not attempt any translation between the two
> > conventions, so maybe I'm just missing something obvious...
> >
> >
> > Do anyone know what considerations led to such design decision?
>
> Aesthetics.
>
>

Re: [9fans] Why Plan 9 uses $ifs instead of $IFS?

[Dan Cross]

On Tue, Oct 17, 2017 at 10:38 AM, Giacomo Tesio  wrote:
> Out of curiosity, do anybody know why Plan9 designers chose lowercase
> variables over uppercase ones?
>
> At first, given the different conventions between rc and sh (eg $path is an
> array, while $PATH is a string), I supposed Plan 9 designers wanted to
> prevent conflict with unix tools relying to the older conventions.
>
> However, I'm not sure this was the main reason, as this also open to subtle
> issues: if a unix shell modifies $IFS and then invoke an rc script, such
> script will ignore the change and keep using the previous $ifs.
>
>
> As far as I can see, APE does not attempt any translation between the two
> conventions, so maybe I'm just missing something obvious...
>
>
> Do anyone know what considerations led to such design decision?

Aesthetics.

[9fans] Why Plan 9 uses $ifs instead of $IFS?

[Giacomo Tesio]

Out of curiosity, do anybody know why Plan9 designers chose lowercase
variables over uppercase ones?

At first, given the different conventions between rc and sh (eg $path is an
array, while $PATH is a string), I supposed Plan 9 designers wanted to
prevent conflict with unix tools relying to the older conventions.

However, I'm not sure this was the main reason, as this also open to subtle
issues: if a unix shell modifies $IFS and then invoke an rc script, such
script will ignore the change and keep using the previous $ifs.


As far as I can see, APE does not attempt any translation between the two
conventions, so maybe I'm just missing something obvious...


Do anyone know what considerations led to such design decision?


Giacomo

Re: [9fans] Change of plan9 partition size

[Pavel Klinkovský]

>
> I just created a new partition of PLAN9 type there (according to
>> https://9p.io/wiki/plan9/setting_up_Venti/index.html), saved and
>> rebooted...
>>
>> ...and system failed to boot:
>>
>> boot: can't connect to file server: '/boot/kfs' does not exists
>>
>
> It seems the boot process does not like two PLAN9 partitions on SD.
>

I was wrong.
The problem is in disk/fdisk which probably damaged the partition table
disabling subsequent reboot.

If I partitioned SD under Linux, the problem was over...

Pavel