Le 16/01/2017 à 11:56, Darac Marjal a écrit :
BIOS will typically only boot from one drive (That said, both BIOS and
UEFI often have mechanisms to choose what that drive is).
UEFI behaves differently. It mostly uses boot entries pointing at EFI
executable files which can be located on any dri
Hi,
Hans wrote:
> > If you do not understand me yet, take this discussion as closed.
Mark Fletcher wrote:
> No, mate, we UNDERSTOOD you from the beginning, the problem is that
> _what you are describing is impossible_.
To be exacting: It obviously goes beyond the imagination of the people
here,
On Mon, Jan 16, 2017 at 12:45:51PM +0100, Hans wrote:
> It makes a grub.cfg on PHYSICAL harddrive ONE and
> a second one on PHYSICAL harddrive TWO and both are identical.
>
> But as both shall be different, according to the drive I want start from.
>
> If you do not understand me yet, take this d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jan 16, 2017 at 12:45:51PM +0100, Hans wrote:
> It makes a grub.cfg on PHYSICAL harddrive ONE and
> a second one on PHYSICAL harddrive TWO and both are identical.
>
> But as both shall be different, according to the drive I want start from.
>
It makes a grub.cfg on PHYSICAL harddrive ONE and
a second one on PHYSICAL harddrive TWO and both are identical.
But as both shall be different, according to the drive I want start from.
If you do not understand me yet, take this discussion as closed.
Thanks for the try.
Best
Hans
On Mon, Jan 16, 2017 at 12:05:06PM +0100, Hans wrote:
You all did not understand me, maybe caused by my bad English.
update-grub is ALWAYS changing grub.cfg on BOTH drives, same from which system
it is started. And I want it only have changed on THAT DRIVE, I am running AT
THE MOMENT. The other
You all did not understand me, maybe caused by my bad English.
update-grub is ALWAYS changing grub.cfg on BOTH drives, same from which system
it is started. And I want it only have changed on THAT DRIVE, I am running AT
THE MOMENT. The other drive shall be then stayed untouched!
Hope this makes
On Sat, Jan 14, 2017 at 10:50:47AM +0100, Hans wrote:
Hi list,
this is the situation:
I have debian installed on my first harddrive and kali-linux on my
second
harddrive. When a new kernel version is installed, update-grub is always
editing both harddrives. Is there a way, to avoid this?
So,
Le 14/01/2017 à 11:31, Hans a écrit :
Am Samstag, 14. Januar 2017, 11:17:57 CET schrieb Pascal Hambourg:
What do you mean exactly ?
update-grub does not "edit any hard drive", it just regenerates the file
/boot/grub/grub.cfg.
Yes, and it does it on BOTH physical harrdrives.
So, I do not wa
Am Samstag, 14. Januar 2017, 11:17:57 CET schrieb Pascal Hambourg:
> What do you mean exactly ?
> update-grub does not "edit any hard drive", it just regenerates the file
> /boot/grub/grub.cfg.
Yes, and it does it on BOTH physical harrdrives.
>
> > So, I do not want, that an upgrade of the kali
Le 14/01/2017 à 10:50, Hans a écrit :
I have debian installed on my first harddrive and kali-linux on my second
harddrive. When a new kernel version is installed, update-grub is always
editing both harddrives. Is there a way, to avoid this?
What do you mean exactly ?
update-grub does not "edit
Hi list,
this is the situation:
I have debian installed on my first harddrive and kali-linux on my second
harddrive. When a new kernel version is installed, update-grub is always
editing both harddrives. Is there a way, to avoid this?
So, I do not want, that an upgrade of the kali-kernel touch
12 matches
Mail list logo
