public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: re: living in the console
Date: Sat, 3 Jun 2017 14:13:29 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.1706031400270.7417@server2.shellworld.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1706030827410.2898@southernprince>

While I can agree that freedos might be a poor choice, I do not share your 
thought that Dos and Linux console are the same environment.
Speaking only for myself, at least as I have managed to experience things 
in such a limited way, often it takes three Linux programs to do the work 
of one DOS one.
I  joked  on the Debian development list that  to clap my hands In Linux 
I 
would  need one program for the right, one for the left, and one to bring 
the hands together.
and do not get me started on Linux command  sequences, laughs.
  In fact, personally that is why objective third party learning materials 
books for example, would be helpful for new users in general.
dos commands tend to do the same things, with universal files like 
autoexec.bat and config.sys doing the heavy lifting where loading and 
unloading   drivers and the like are concerned.
In Linux, you must know already, or learn with risks to your system how to 
do things.
When I started using DOS, I trained for two days in person with someone 
and have built on that training for decades.  Something comparative just 
does  not exist for Linux in my view.
And I would gladly pay for it, if it did.
Happy linuxhousewarming though,
Kare


On Sat, 3 Jun 2017, 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
>
>

  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
 ` Linux for blind general discussion [this message]
   ` 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=Pine.LNX.4.64.1706031400270.7417@server2.shellworld.net \
    --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).