Re: [PATCH] bash: add socket server support

2013-11-26 Thread Mike Frysinger
On Thursday 14 November 2013 00:50:33 Piotr Grzybowski wrote: > I can think of an attack, just provide me with ip address of the host > :) and a root account password and login :) > > I agree that most systems have other abilities to do the (almost) > same, but yet, all systems (that is to say m

Re: [PATCH] bash: add socket server support

2013-11-26 Thread Mike Frysinger
On Wednesday 13 November 2013 06:39:45 Irek Szczesniak wrote: > On Wed, Nov 13, 2013 at 7:35 AM, Piotr Grzybowski wrote: > > Hi Everyone, hi Joel, > > > > the idea is nice, and I can really see that it is useful, but I would > > > > be extremely careful with introducing those kind of changes, it

Re: [PATCH] bash: add socket server support

2013-11-26 Thread Mike Frysinger
On Thursday 14 November 2013 11:32:18 Cedric Blancher wrote: > On 13 November 2013 15:46, Joel Martin wrote: > > On Wed, Nov 13, 2013 at 6:39 AM, Irek Szczesniak wrote: > >> The other problems I see is: > >> How can the script get access to the data returned by accept()? Unlike > >> ksh93 bash4 has

Re: bash 4.3 and 4.2 trouble with associative arrays assigned by ``printf -v''

2013-11-26 Thread NBaH
Le 26/11/2013 14:59, dnade@orange.com a écrit :> For the record, in bash 4.2.25 (Ubuntu LTS 12.04) you can work around your issue with : > > printf -v "aa["ind2"]" %s "" > > or > > printf -v "aa["ind2"]" %s > hi, right! as I had to deal with variables expanding to things like '\x3C', '%s'

RE: bash 4.3 and 4.2 trouble with associative arrays assigned by ``printf -v''

2013-11-26 Thread dnade.ext
For the record, in bash 4.2.25 (Ubuntu LTS 12.04) you can work around your issue with : printf -v "aa["ind2"]" %s "" or printf -v "aa["ind2"]" %s D -- Damien Nadé Astek Sud-Est pour France Télécom - Orange/OF/DSIF/DFY/SFY/DO Sophia Antipolis - France / Tel : 04 97 46 28 74 > -M

Re: continuously evaluated prompts/environmental variables

2013-11-26 Thread Greg Wooledge
On Tue, Nov 26, 2013 at 03:38:17AM -0500, Chris F.A. Johnson wrote: > On Mon, 25 Nov 2013, Edward Peschko wrote: > >Is there a way to have the prompt - or any other environmental > >variable - change in this way, based off external command? > > Use single quotes: > > PS1='`whoami`@`hostname`'

Re: continuously evaluated prompts/environmental variables

2013-11-26 Thread Andreas Schwab
Pierre Gaston writes: > PS1='`whoami`@`hostname`' PS1='\u@\h' Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."

Re: continuously evaluated prompts/environmental variables

2013-11-26 Thread Pierre Gaston
On Tue, Nov 26, 2013 at 7:21 AM, Edward Peschko wrote: > All, > > I was wondering if there was a way to make an environmental variable > be evaluated each time it was accessed. In other words, with: > > export PS1="`whoami`@`hostname`" > > This works for the first time that the prompt is evaluate

Re: continuously evaluated prompts/environmental variables

2013-11-26 Thread Chris F.A. Johnson
On Mon, 25 Nov 2013, Edward Peschko wrote: All, I was wondering if there was a way to make an environmental variable be evaluated each time it was accessed. In other words, with: export PS1="`whoami`@`hostname`" This works for the first time that the prompt is evaluated, what I would like to

continuously evaluated prompts/environmental variables

2013-11-26 Thread Edward Peschko
All, I was wondering if there was a way to make an environmental variable be evaluated each time it was accessed. In other words, with: export PS1="`whoami`@`hostname`" This works for the first time that the prompt is evaluated, what I would like to have is a prompt to be continuously evaluated,