Mrs. Nicole | 18 Jul 09:07 2014
Picon

Hi

Business Proposal

--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Luigi Tarenga | 8 Jul 16:23 2014
Picon

bug in dash compile with buildroot

hi,
I send this bug report to both list because I'm not sure who will find 
this relevant.

I compiled a buildroot image for a laptop with atom so the build is for 
x86_64
architecture. In the build configuration I flagged to include dash and 
this get
compiled as static (this let me test the bug even on the host system).

While writing some test script (actually a init process written in dash) 
I hit this
strange bug:

# dash -c "( echo ciao) &)"
ciao
Segmentation fault

# dash -c "(echo ciao; /bin/true)&"
ciao

# dash -c "(echo ciao; /bin/true; echo ciao)&"
ciao
ciao
Segmentation fault

As you see if I put a subshell in background it dump. If in the same 
subshell I execute
an external command as last command it works.
I write this bug even to the buildroot team because if I rebuild dash 
(Continue reading)

Adam Borowski | 28 Jun 06:56 2014
Picon

[PATCH] \e in "echo" and "printf" builtins

Hi!

I'm not sure what's your policy towards extensions, but \e as \033 is
something ubiquitous in the Unix world.  C compilers (gcc, clang, icc and
tcc -- but not MSVC), perl, shells (bash and zsh -- but not dash), etc.

What about supporting it in dash as well?
Patch attached.

--

-- 
Gnome 3, Windows 8, Slashdot Beta, now Firefox Ribbon^WAustralis.  WTF is going
on with replacing usable interfaces with tabletized ones?
Roberts Barton | 24 Jun 16:10 2014
Picon

great proposition for us.

Good day,
I have something of importance which you will be interested in, it will be my utmost appreciation if you
contact me so I can furnish you with details.
Roberts
--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Petr Šabata | 24 Jun 14:40 2014
Picon

[PATCH] Fix build failure with gcc -Werror=format-security

This fix lets dash build with the abovementioned option.

Signed-off-by: Petr Šabata <contyk <at> redhat.com>
---
 src/jobs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/jobs.c b/src/jobs.c
index bf40204..f3af44d 100644
--- a/src/jobs.c
+++ b/src/jobs.c
 <at>  <at>  -427,7 +427,7  <at>  <at>  sprint_status(char *s, int status, int sigonly)
 				goto out;
 #endif
 		}
-		col = fmtstr(s, 32, strsignal(st));
+		col = fmtstr(s, 32, "%s", strsignal(st));
 #ifdef WCOREDUMP
 		if (WCOREDUMP(status)) {
 			col += fmtstr(s + col, 16, " (core dumped)");
--

-- 
1.9.3

--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Adam Buchbinder | 12 Jun 01:08 2014
Picon

[PATCH 1/2] [MAN] 0 and EXIT both work for exit traps.

I saw a discussion in which there was some confusion over whether or not
you can use a symbolic name, since the manpage doesn't specifically say so.

Signed-off-by: Adam Buchbinder <adam.buchbinder <at> gmail.com>
---
 ChangeLog  | 4 ++++
 src/dash.1 | 4 +++-
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog
index 2a39e34..81df8d1 100644
--- a/ChangeLog
+++ b/ChangeLog
 <at>  <at>  -1,3 +1,7  <at>  <at> 
+2014-06-11  Adam Buchbinder <adam.buchbinder <at> gmail.com>
+
+	* Clarify that 0 and EXIT are both acceptable for exit traps.	
+
 2013-08-23  Herbert Xu <herbert <at> gondor.apana.org.au>

 	* Propagate EXP_QPAT in subevalvar.
diff --git a/src/dash.1 b/src/dash.1
index 6241a61..a07a52d 100644
--- a/src/dash.1
+++ b/src/dash.1
 <at>  <at>  -2071,7 +2071,9  <at>  <at>  The signals are specified by signal number or as the name of the signal.
 If
 .Ar signal
 is
-.Li 0 ,
(Continue reading)

Kong Hui | 27 May 02:18 2014
Picon

Get back to me

I am a bank director from Hong Kong, I want you to be my partner in a
business project of mutual benefit. Get back to me if interested.

Thank you,
Kong Hui.

--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Islas, Denise | 20 Mar 22:41 2014

Email: agtbarrgregspencers <at> gmail.com


Congratulation You Won £750,000.00 e-Mail:agtbarrgregspencers <at> gmail.com
--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Adrian Bayford | 14 Mar 07:27 2014

Contact Mr Adrian on (gadrain <at> 8u8.hk)

My wife and i adrian won Jackpot Lottery and Decided to donate 2million dollars to you,
Contact Mr Adrian on (gadrain <at> 8u8.hk) For More Info
--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Jeroen van Dijke | 9 Mar 12:11 2014
Picon

Bug in man page

Hi,

There seems to be a bug in the dash man page, at least in 0.5.7. It reads:

            Precision:
                    An optional period, `.', followed by an optional digit string giving a precision which specifies the
number of digits to appear after the decimal point, for e and f formats, or the maximum number of
*characters* to be printed from a string (b and s for-
                    mats); if the digit string is missing, the precision is treated as zero;

dash behaves cuts to the number of bytes

$ length=10; printf "%.${length}s\n" "eeeeeeeeeeeeeeeeeeeeeeeee"
eeeeeeeeee
$ length=10; printf "%.${length}s\n" "ëëëëëëëëëëëëëëëëëëëëëëëëë”
ëëëëë

The  POSIX specification (2008) says:

precision Gives the minimum number of digits to appear for the d, o, i, u, x, or X conversion specifiers (the
field is padded with leading zeros), the number of digits to appear after the radix character for the e and f
conversion specifiers, the maximum number of significant digits for the g conversion specifier; or the
maximum number of *bytes* to be written from a string in the s conversion specifier. The precision shall
take the form of a ( '.' ) followed by a decimal digit string; a null digit string is treated as zero.

So it seems to me that “characters” should be changed to “bytes”.

Kind Regards,

Jeroen van Dijke--
(Continue reading)

Jason Miller | 7 Mar 20:43 2014

command lookup and POSIX

Reading this:

http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_09_01_01

Any built-in other than the special built-ins, or listed in the table
there should not be run unless it is present in the PATH.

dash however doesn't follow that:

PS1="% " dash

    % PATH=
    % /usr/bin/which [
    /usr/bin/which: no [ in ()
    % [ -x f ]
    % 

Of course I can't find a single shell that follows this, even when
enabling its respective strict POSIX mode.  I'm guessing it was added to
prevent changes in behaviors of existing scripts as shells add more
builtins.

However, changing dash to comply also seems of dubious value since there
are many shell scripts out there that depend on common built-ins not
listed in POSIX.

However DASH claims POSIX compliance so I thought I would at least
mention it now that I found it.

-Jason
(Continue reading)


Gmane