From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: living in the console
Date: Sat, 3 Jun 2017 14:28:39 -0300 [thread overview]
Message-ID: <fa4ded9a-58ee-0709-62ad-1e286f89d869@F123.org> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1706030827410.2898@southernprince>
Oh, I have experienced on both environments and I can tell you that BASH
is way more powerful than any version of DOS, and the same is true for
just about any shell I have ever heard of.
But they are equivalent in the sense that they are both accessible and
in the case of Linux shell, worth learning and playing with.
Fernando
On 06/03/2017 10:30 AM, Linux for blind general discussion wrote:
> Mark Peveto here,
> I think i'm gonna put my dos project on hold for now, and concentrate on learning the linux console as best I can. It's not much different than the dos
> environment, so we'll see how I go there. Seems free dos is a bad choice, and I can't find anything else to use at the moment, so for now I'll just
> hang out in the linux console and learn how to live there.
> Thanks for everyone's input.
> And now, back to our regularly scheduled program.
>
>
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
-- strict thread matches above, loose matches on Subject: below --
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
[not found] ` <20170602170642.GA25350@lenovo.local>
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa4ded9a-58ee-0709-62ad-1e286f89d869@F123.org \
--to=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).