From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: Getting started with Debian
Date: Wed, 19 Feb 2020 09:51:58 -0500 [thread overview]
Message-ID: <alpine.NEB.2.21.2002190950470.18901@panix1.panix.com> (raw)
In-Reply-To: <6d42bdc1-f6c8-1e64-64e8-702f030cc84d@GMAIL.COM>
Those instructions will work on hard iron, additional steps are
necessary to properly prepare for virtual installs and I haven't got
into virtual installs so I can't help you with those.
On Wed, 19 Feb 2020, Linux for blind general discussion wrote:
> Date: Wed, 19 Feb 2020 08:25:07
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: blinux-list@redhat.com
> Subject: Re: Getting started with Debian
>
> I'm more referring to going from a totally fresh VM and doing it that way.
> \But, your instructions should work, correct?
>
> On 19/02/2020 11:26, Linux for blind general discussion wrote:
> > If you already have linux and wget on a system,
> > wget -bc
> > https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/10.3.0+nonfree/amd64/iso-dvd/firmware-10.3.0-amd64-DVD-1.iso
> > probably will help.
> > It starts up silent so hit the s key then hit enter to get a screen
> > reader going.
> > I'm recommending this since you can stack the deck in terms of most
> > awkward software and get a system installed.
> > Get into the main menu by hitting < repeatedly until the main numbered
> > menu comes up and choose the selection to check disk integrity first.
> > If that passes, you may want to consider setting notification priority
> > to low and saving installation logs to a mounted file system and then
> > continue the installation
> > A long long time ago, the main menu program on acbradio used to have
> > programs demonstrating linux installations one of which was a debian
> > installation from a now obsolete version of debian. You control your
> > flavor of distribution by editing /etc/apt/sources.list. And for now,
> > what you call testing is better known as bullseye.
> > I hope this helps.
> > On Wed, 19 Feb 2020,
> > Linux for blind general discussion wrote:
> >
> >> Date: Wed, 19 Feb 2020 05:23:40
> >> From: Linux for blind general discussion <blinux-list@redhat.com>
> >> To: Linux for blind general discussion <blinux-list@redhat.com>
> >> Subject: Getting started with Debian
> >>
> >> So, since Debian got brought up on the list...
> >>
> >> What all do I need to get started with it, exactly? I'd like to get a
> >> system
> >> up and going on debian-testing, and set it up how I want
> >>
> >> _______________________________________________
> >> Blinux-list mailing list
> >> Blinux-list@redhat.com
> >> https://www.redhat.com/mailman/listinfo/blinux-list
> >>
> >>
> >>
>
> _______________________________________________
> 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: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` 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=alpine.NEB.2.21.2002190950470.18901@panix1.panix.com \
--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).