On Tue, 30 Mar 2021 17:20:11 +0300
George Shuklin wrote:
> My point was that 'sh' approach (including
> bash and dash) is really, really bad. Bash as a programming language
> is super tricky, with lots of landmines and almost no validation
> whatsoever for errors (there is a bit, but way less
On 26/03/2021 16:59, Dan Ritter wrote:
George Shuklin wrote:
But it's all software. Debian can't change sh to be 'not sh'. And any
changes in a build stack are touching vast amount of software with extremely
complex use-cases, so it's almost impossible to 'replace'. You can 'add' a
new one, but
El dom, 28 mar 2021 a las 9:48, Andrew M.A. Cater
() escribió:
> Have a look at the FAQ posted to this list once a month
> for some ideas on how this list works. If something solves the problem / you
> find a good answer that might help someone else, adding something like
> subject line - [SOLVED]
Hi.
El sáb, 27 mar 2021 a las 23:18, Cmdte Alpha Tigre Z
() escribió:
> [many things]
Sorry, I forgot to finish writing my titles on my past post,
so if you need them, here are the lines where a different section
begin:
Line 344: 2.5. To Mr. Greg Wooledge.
Line 367: 2.6. To someone anonymous,
On Fri, Mar 26, 2021 at 07:11:24PM +0530, Susmita/Rajib wrote:
> My illustrious Team Leaders and Movers of the Debian List,
>
We are all volunteers - the salutation is fine, but we're no more than
volunteers here.
> It has often been advised by experienced users of Debian for the
> learners to
Thanks dear Cmdte Alpha.
It was indeed very informative.
Thanks also to all who’re contributing, a lot to read here.
— *a silent reader*.
On Sun, Mar 28, 2021 at 3:19 AM Cmdte Alpha Tigre Z
wrote:
> Oh dear, so much opposition here, isn't it?
>
> Please take your time and patience to read my
Oh dear, so much opposition here, isn't it?
Please take your time and patience to read my whole message,
I put some titles so you can jump where you need to.
1. ANSWER TO SUSMITA/RAJIB
Dear Susmita/Rajib, thanks for sharing your opinion.
It is very ambitious what you are proposing.
1.1.
Greg Wooledge wrote:
> On Fri, Mar 26, 2021 at 10:59:20AM -0400, Dan Ritter wrote:
> > To be completely clear, Debian did change sh from Bourne-ish sh
> > to dash in Squeeze -- 2006 or so.
>
> Squeeze was released in 2011.
...
> The change from bash to dash as the default /bin/sh happened in
On Fri, Mar 26, 2021 at 10:46:23AM -0500, David Wright wrote:
> On Fri 26 Mar 2021 at 19:11:24 (+0530), Susmita/Rajib wrote:
> > It is clearly noticed that wide applications of tricks with wildcards,
> > regex and redirections aren't simply available in the man pages.
Nor should they be. The man
On Fri, Mar 26, 2021 at 10:59:20AM -0400, Dan Ritter wrote:
> To be completely clear, Debian did change sh from Bourne-ish sh
> to dash in Squeeze -- 2006 or so.
Squeeze was released in 2011.
Debian originally used bash as /bin/sh (as most Linux distributions did,
back in those days). At some
On Fri 26 Mar 2021 at 19:11:24 (+0530), Susmita/Rajib wrote:
[ … ]
>
> Even the book that I have procured — The Linux Command Line, A
> Complete Introduction, by William Shotts — has all codes spread (or
> s[t]rewn) across many pages and has to be brought together by exhaustive
> note taking.
Unfortunately this is a bit of a mess but you need to understand the
history and politics here.
First off, Debian, as well as the other Unix and Linux distributions
are a collection of lots of different things from differnet places and
you get an operating system out of it all. Something like
George Shuklin wrote:
> But it's all software. Debian can't change sh to be 'not sh'. And any
> changes in a build stack are touching vast amount of software with extremely
> complex use-cases, so it's almost impossible to 'replace'. You can 'add' a
> new one, but it just make xkcd #927.
To be
On 26/03/2021, to...@tuxteam.de wrote:
... ... [snipped] ... ...
>> Shouldn't all codes and tricks involving them be available for
>> everyone to use, but still have the system so robust that it can't be
>> hacked?
>
> I think "all" is a very tall order: the
On 26/03/2021 15:41, Susmita/Rajib wrote:
Even the book that I have procured — The Linux Command Line, A
Complete Introduction, by William Shotts — has all codes spread (or
sprewn) across many pages and has to be brought together by exhaustive
note taking.
It is clearly noticed that wide
Susmita/Rajib wrote:
> It is clearly noticed that wide applications of tricks with wildcards,
> regex and redirections aren't simply available in the man pages.
>
> So is it then not necessary to have a repository of codes, with all
> permutations & combinations of possibilities with
On Fri, Mar 26, 2021 at 07:11:24PM +0530, Susmita/Rajib wrote:
> My illustrious Team Leaders and Movers of the Debian List,
[...]
> Shouldn't all codes and tricks involving them be available for
> everyone to use, but still have the system so robust that it can't be
> hacked?
I think "all" is a
My illustrious Team Leaders and Movers of the Debian List,
It has often been advised by experienced users of Debian for the
learners to focus more on man pages.
I shall seek a few examples before i place my questions.
Let us for instance look at the man page of ls at:
18 matches
Mail list logo
