On Sun, 2019-09-08 at 14:21 -0700, Samuel Sieb wrote:
> On 9/8/19 6:13 AM, Patrick O'Callaghan wrote:
> > My question is: how can I add this as an option to my Grub
> > configuration to enable dual-boot directly from the Grub menu (i.e.
> > running on metal, not a VM)? In other words, BIOS boots us
On 9/8/19 2:43 PM, Tom Horsley wrote:
On Sun, 8 Sep 2019 14:21:59 -0700
Samuel Sieb wrote:
BIOS boots using MBR,
invokes Grub, which then (optionally) invokes UEFI to boot Windows. Or
is this not possible?
You can't because the EFI services would not be available.
Could you have a separate
On Sun, 8 Sep 2019 14:21:59 -0700
Samuel Sieb wrote:
> BIOS boots using MBR,
> > invokes Grub, which then (optionally) invokes UEFI to boot Windows. Or
> > is this not possible?
>
> You can't because the EFI services would not be available.
Could you have a separate grub instance that is UEFI
On 9/8/19 6:13 AM, Patrick O'Callaghan wrote:
My question is: how can I add this as an option to my Grub
configuration to enable dual-boot directly from the Grub menu (i.e.
running on metal, not a VM)? In other words, BIOS boots using MBR,
invokes Grub, which then (optionally) invokes UEFI to boo
I have an old-style MBR Grub configuration for F30. Converting the
system to UEFI seems like a hassle and doesn't provide an obvious
benefit for now (maybe next time I do a full install I'll go for it).
However I also run Windows 10 in a KVM/QEMU virtual machine. This has
its own dedicated drive a
On 12/27/2015 06:44 AM, Tim wrote:
Generally speaking, if you want to clone drives, you're much better off
booting from some third thing,
Clonezilla.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listin
On Mon, 28 Dec 2015 01:14:48 +1030
Tim wrote:
> Generally speaking, if you want to clone drives, you're much better off
> booting from some third thing, and copying from source to destination
> without any interference from an OS currently running from the drive
> you're copying.
Yep. I do that p
Philip Rhoades wrote:
>> I am interested to see if it is possible to boot on an existing disk -
>> say /dev/sda ("A") - and then manually create everything required on a
>> second disk - /dev/sdb ("B") eg:
Generally speaking, if you want to clone drives, you're much better off
booting from some th
Timothy,
Date: Sun, 27 Dec 2015 10:36:36 +0100
From: Timothy Murphy
To: users@lists.fedoraproject.org
Subject: Re: An Exercise: Manually creating a new boot disk from an
existingone
Message-ID:
Content-Type: text/plain; charset="ISO-8859-1"
Philip Rhoades wro
Philip Rhoades wrote:
> I am interested to see if it is possible to boot on an existing disk -
> say /dev/sda ("A") - and then manually create everything required on a
> second disk - /dev/sdb ("B") eg:
>
> - create the partition table and partitions on B
>
> - dd the existing boot track(s) from
People,
I am interested to see if it is possible to boot on an existing disk -
say /dev/sda ("A") - and then manually create everything required on a
second disk - /dev/sdb ("B") eg:
- create the partition table and partitions on B
- dd the existing boot track(s) from A to a file and then dd
On 30/12/11 15:10, Alan Cox wrote:
Agreed. But you have to *know* the drive serial number or UUID to do
that. And there is, of course, a high probability that you will not have
that information available.
It's in procfs, sysfs, ioctls and via dmesg. It's not hard to get at !
and if you are doin
> Agreed. But you have to *know* the drive serial number or UUID to do
> that. And there is, of course, a high probability that you will not have
> that information available.
It's in procfs, sysfs, ioctls and via dmesg. It's not hard to get at !
and if you are doing it in advance you can also u
On 12/29/2011 11:30 AM, Alan Cox wrote:
which disk the initial load occurred from? I did run dmidecode and found
nothing of value.
dmidecode is the wrong interface. EDD provides the drive to BIOS mapping
tables, DMI provides static configuration data.
Your two hard drives are otherwise (I pr
On Thu, 2011-12-29 at 16:30 +, Alan Cox wrote:
> > > which disk the initial load occurred from? I did run dmidecode and found
> > > nothing of value.
>
> dmidecode is the wrong interface. EDD provides the drive to BIOS mapping
> tables, DMI provides static configuration data.
>
> > Your two
> > which disk the initial load occurred from? I did run dmidecode and found
> > nothing of value.
dmidecode is the wrong interface. EDD provides the drive to BIOS mapping
tables, DMI provides static configuration data.
> Your two hard drives are otherwise (I presume) exactly alike.
Just use th
On 12/27/2011 11:21 AM, Jeffrey Ross wrote:
> On Sun, Dec 25, 2011 at 2:37 PM, Jeffrey Ross wrote:
>> Is there a way to identify which disk the BIOS is using to boot from (eg
>> disk 0 or 1) when I don't have physical access to the system to view the
>> BIOS settings?
> If both disks h
On Wed, Dec 28, 2011 at 12:12 AM, wrote:
>[...]
> In this case it turns out it was booting off of sda (which is what I
> suspected), I ended up taking a ride down to the datacenter and verifying
> the BIOS.
>
> The original question although no longer important remains, can you tell
> which disk
On 2011/12/27 07:12, j...@bubble.org wrote:
On Sun, Dec 25, 2011 at 2:37 PM, Jeffrey Ross wrote:
Is there a way to identify which disk the BIOS is using to boot from (eg
disk 0 or 1) when I don't have physical access to the system to view the
BIOS settings?
The situation is this, I have a mach
> On Sun, Dec 25, 2011 at 2:37 PM, Jeffrey Ross wrote:
>> Is there a way to identify which disk the BIOS is using to boot from (eg
>> disk 0 or 1) when I don't have physical access to the system to view the
>> BIOS settings?
>>
>> The situation is this, I have a machine at a remote location where
http://www.google.ca/search?q=police+officer+jeff+how+do+you+crack+fedora+linux+bios%3F&btnG=Search&hl=en&site=&gbv=1&sei=Z9j3TsOQEIOP8gOK_rimAQ
--
http://www.fastmail.fm - A fast, anti-spam email service.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscriptio
Boot disk?
From:
"Jeffrey Ross" [Add]
To:
"For users of Fedora" [Add]
Date:
Sun, 25 Dec 2011 1:37 PM (4 hours 28 minutes ago)
Show message - Delete attached message - Save copy of attached
message
Show full header
Is there a way to identify which di
On Sun, Dec 25, 2011 at 2:37 PM, Jeffrey Ross wrote:
> Is there a way to identify which disk the BIOS is using to boot from (eg
> disk 0 or 1) when I don't have physical access to the system to view the
> BIOS settings?
>
> The situation is this, I have a machine at a remote location where the
> s
On Sun, 2011-12-25 at 16:37 -0500, Jeffrey Ross wrote:
> Is there a way to identify which disk the BIOS is using to boot from (eg
> disk 0 or 1) when I don't have physical access to the system to view the
> BIOS settings?
>
> The situation is this, I have a machine at a remote location where the
On 12/26/2011 12:23 AM, Aaron Konstam wrote:
On Sun, 2011-12-25 at 23:53 +0200, Rares Aioanei wrote:
On 12/25/2011 11:37 PM, Jeffrey Ross wrote:
Is there a way to identify which disk the BIOS is using to boot from
(eg disk 0 or 1) when I don't have physical access to the system to
view the BIOS
On Sun, 2011-12-25 at 23:53 +0200, Rares Aioanei wrote:
> On 12/25/2011 11:37 PM, Jeffrey Ross wrote:
> > Is there a way to identify which disk the BIOS is using to boot from
> > (eg disk 0 or 1) when I don't have physical access to the system to
> > view the BIOS settings?
> >
> > The situation
On 12/25/2011 11:37 PM, Jeffrey Ross wrote:
Is there a way to identify which disk the BIOS is using to boot from
(eg disk 0 or 1) when I don't have physical access to the system to
view the BIOS settings?
The situation is this, I have a machine at a remote location where the
system runs RAID-
Is there a way to identify which disk the BIOS is using to boot from (eg
disk 0 or 1) when I don't have physical access to the system to view the
BIOS settings?
The situation is this, I have a machine at a remote location where the
system runs RAID-1 and both disks (0 and 1) can boot the syste
28 matches
Mail list logo