public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: A Live Boot Image for the Mac that Talks
Date: Sat, 1 Feb 2020 18:15:59 -0600	[thread overview]
Message-ID: <10e5062a-cb11-97d5-e394-2042b9dedfaf@gmail.com> (raw)
In-Reply-To: <d75a7b21-75c1-ee44-5d35-71129cfeea51@verizon.net>

I'm curious about this as well. I've used dd to create bootable USB 
sticks for years. Here's just one page that instructs you to use dd from 
the command line 
https://linuxize.com/post/how-to-create-a-bootable-linux-usb-drive/


On 2/1/20 5:32 PM, Linux for blind general discussion wrote:
> I may be wrong, but I seem to remember instructions to do just that to 
> create a bootable source for installing a distribution. Do you know 
> where I can read about this subject?  Thanks!
>
>
> Al
>
>
> On 2/1/20 6:07 PM, Linux for blind general discussion wrote:
>> dd is not a good command for burning usb sticks and this is probably why
>> you had a failure.
>>
>> On Sat, 1 Feb 2020, Linux for blind general discussion wrote:
>>
>>> Date: Sat, 1 Feb 2020 18:01:42
>>> From: Linux for blind general discussion <blinux-list@redhat.com>
>>> To: blinux-list@redhat.com
>>> Subject: Re: A Live Boot Image for the Mac that Talks
>>>
>>> I suspect I am about to learn something so here's the deal:
>>>
>>>     I downloaded the iso image and used dd to pour it in to a
>>> thumb drive
>>>
>>> dd if=imagefile of=/dev/sdd in this case and away it went.
>>>
>>>     Several minutes later, the roughly 1-gig file ended up on
>>> the thumb drive.
>>>
>>>     The mac is old enough not to have the T2 chip so if the
>>> drive is bootable, it should boot which it does not.
>>>
>>>     If you plug the drive in, a message pops up stating that
>>> it is unreadable on this computer
>>>
>>>     How do I get the Mac to boot off of that drive?
>>>
>>> Martin McCormick
>>>
>>>
>>> _______________________________________________
>>> 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

-- 
Christopher (CJ)
Chaltain at Gmail


  reply	other threads:[~ UTC|newest]

Thread overview: 16+ 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
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion [this message]
           ` 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]                 ` <20200202.053250.708.97@192.168.1.118>
                   ` 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=10e5062a-cb11-97d5-e394-2042b9dedfaf@gmail.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).