David Wright composed on 2021-07-04 10:29 (UTC-0500):
> On Tue 29 Jun 2021 at 13:26:04 (-0400), Felix Miata wrote:
>> David Wright composed on 2021-06-29 11:16 (UTC-0500):
...
>>> I don't understand the attraction of messing about with boot flags
>>> in order to choose which primary partition to
On Tue 29 Jun 2021 at 13:26:04 (-0400), Felix Miata wrote:
> David Wright composed on 2021-06-29 11:16 (UTC-0500):
> > On Thu 24 Jun 2021 at 00:07:56 (-0400), Felix Miata wrote:
> >> David Wright composed on 2021-06-22 10:50 (UTC-0500):
>
> >> I'm not sure there is "a" definition. One could be any
David Wright composed on 2021-06-29 11:16 (UTC-0500):
> On Thu 24 Jun 2021 at 00:07:56 (-0400), Felix Miata wrote:
>> David Wright composed on 2021-06-22 10:50 (UTC-0500):
>> I'm not sure there is "a" definition. One could be any code that a Windows
>> installation would not replace. Another cou
On Thu 24 Jun 2021 at 00:07:56 (-0400), Felix Miata wrote:
> David Wright composed on 2021-06-22 10:50 (UTC-0500):
> > On Fri 11 Jun 2021 at 16:57:35 (-0400), Felix Miata wrote:
>
> >> OTOH, putting a bootloader on the MBR of a disk on a PC designed for
> >> Windows is a
> >> relative newcomer to
David Wright composed on 2021-06-22 10:50 (UTC-0500):
> On Fri 11 Jun 2021 at 16:57:35 (-0400), Felix Miata wrote:
>> OTOH, putting a bootloader on the MBR of a disk on a PC designed for Windows
>> is a
>> relative newcomer to the world of booting such a PC. I've been installing
>> operating sys
On Mi, 23 iun 21, 19:43:14, Richard Hector wrote:
>
> Is that something that needs to be done by one company? Perhaps because of
> how SecureBoot is implemented?
For a logistic point of view, at least for x86, Microsoft appears to be
the natural choice: many mainboard manufacturers, but most ha
On 22/06/21 12:54 am, Steve McIntyre wrote:
[ Apologies, missed this last week... ]
to...@tuxteam.de wrote:
On Mon, Jun 14, 2021 at 09:20:52AM +0300, Andrei POPESCU wrote:
On Vi, 11 iun 21, 15:07:11, Greg Wooledge wrote:
>
> Secure Boot (Microsoft's attempt to stop you from using Linux) reli
On Fri 11 Jun 2021 at 16:57:35 (-0400), Felix Miata wrote:
> Greg Wooledge composed on 2021-06-11 15:07 (UTC-0400):
> > On Fri, Jun 11, 2021 at 09:38:37PM +0300, Semih Ozlem wrote:
>
> >> How to check where grub is installed? And what is a friendly guide to
> >> learning about grub?
>
> > GRUB sh
On Mon, Jun 21, 2021 at 12:54:31PM +, Steve McIntyre wrote:
> [ Apologies, missed this last week... ]
No need to apologise: I appreciate the detailed answer.
> > - do you know any other alternative CA besides Microsoft [...]
> I've been in a number of discussions about this over the last few
[ Apologies, missed this last week... ]
to...@tuxteam.de wrote:
>
>On Mon, Jun 14, 2021 at 09:20:52AM +0300, Andrei POPESCU wrote:
>> On Vi, 11 iun 21, 15:07:11, Greg Wooledge wrote:
>> >
>> > Secure Boot (Microsoft's attempt to stop you from using Linux) relies on
>> > UEFI booting, and therefor
On Mon, Jun 14, 2021 at 06:07:50AM -0400, Kenneth Parker wrote:
> Okay. I am running Debian Bullseye (selected earlier, during its testing
> phase, because I needed its level of QEMU to import a VM from Mint 20's
> QEMU: Buster's QEMU refused). My computer is an HP EliteDesk 705 G1-SFF.
>
> I h
On Mon, 14 Jun 2021 11:41:37 +0200
wrote:
> "Any sufficiently advanced malice is indistinguishable from
> stupidity"
>
> (some call that "plausible deniability").
>
>
"People would rather appear stupid than evil".
--
Joe
On Mon, Jun 14, 2021 at 4:45 AM Thomas Schmitt wrote:
> Hi,
>
> Greg Wooledge wrote:
> > > > Secure Boot (Microsoft's attempt to stop you from using Linux)
>
> Andrei POPESCU wrote:
> > > While I'm not a fan of Microsoft:
> > > https://wiki.debian.org/SecureBoot#What_is_UEFI_Secure_Boot_NOT.3
> >
On Mon, Jun 14, 2021 at 10:46:34AM +0200, Thomas Schmitt wrote:
> Hi,
>
> Greg Wooledge wrote:
> > > > Secure Boot (Microsoft's attempt to stop you from using Linux)
>
> Andrei POPESCU wrote:
> > > While I'm not a fan of Microsoft:
> > > https://wiki.debian.org/SecureBoot#What_is_UEFI_Secure_Boot
Hi,
Greg Wooledge wrote:
> > > Secure Boot (Microsoft's attempt to stop you from using Linux)
Andrei POPESCU wrote:
> > While I'm not a fan of Microsoft:
> > https://wiki.debian.org/SecureBoot#What_is_UEFI_Secure_Boot_NOT.3
> > "Microsoft act as a Certification Authority (CA) for SB, and they wil
On Mon, Jun 14, 2021 at 09:20:52AM +0300, Andrei POPESCU wrote:
> On Vi, 11 iun 21, 15:07:11, Greg Wooledge wrote:
> >
> > Secure Boot (Microsoft's attempt to stop you from using Linux) relies on
> > UEFI booting, and therefore this was one of the driving forces behind it,
> > but not the *only* d
On Vi, 11 iun 21, 15:07:11, Greg Wooledge wrote:
>
> Secure Boot (Microsoft's attempt to stop you from using Linux) relies on
> UEFI booting, and therefore this was one of the driving forces behind it,
> but not the *only* driving force. If your machine doesn't use Secure Boot,
> don't worry abou
(I wrote this over 12 hours ago, before I went to bed, and forgot to send
first.)
Joe composed on 2021-06-12 07:59 (UTC+0100):
> It doesn't help that the BIOS is broken, that it does not honour the
> EFI DefaultBoot, and always rewrites entry if I change it.
Joe wrote:
>
>Grub lives in more than one place: most of it is in /boot/grub, but
>there is a first-stage bootloader which calls this. To be honest,
>I don't know for sure where that lives on a GPT disk, on the old
>DOS-type partition it would live at the start of either the whole hard
>drive or th
Andrew M.A. Cater wrote:
...
> These sound like either: broken versions of UEFI / broken installations or,
> exceptionally, a broken manufacturer somewhere.
>
> It may be worth revisiting installations when Bulleseye comes out to
> get something that works and is supportable for the next few years
On Sat, 12 Jun 2021 11:47:16 +
"Andrew M.A. Cater" wrote:
> On Sat, Jun 12, 2021 at 07:09:29AM -0400, songbird wrote:
> > Joe wrote:
> > ...
> > > It doesn't help that the BIOS is broken, that it does not honour
> > > the EFI DefaultBoot, and always rewrites entry if I change
> > > it.
On Sat, 12 Jun 2021 07:09:29 -0400
songbird wrote:
> Joe wrote:
> ...
> > It doesn't help that the BIOS is broken, that it does not honour the
> > EFI DefaultBoot, and always rewrites entry if I change it.
> > Fortunately, it does honour NextBoot, or I'd never be able to get it
> > booted in
On Sat, Jun 12, 2021 at 07:09:29AM -0400, songbird wrote:
> Joe wrote:
> ...
> > It doesn't help that the BIOS is broken, that it does not honour the
> > EFI DefaultBoot, and always rewrites entry if I change it.
> > Fortunately, it does honour NextBoot, or I'd never be able to get it
> > boot
Joe wrote:
...
> It doesn't help that the BIOS is broken, that it does not honour the
> EFI DefaultBoot, and always rewrites entry if I change it.
> Fortunately, it does honour NextBoot, or I'd never be able to get it
> booted into buster. But it worked with stretch. I could try installing
> s
On Fri, 11 Jun 2021 18:24:43 -0400
Felix Miata wrote:
> Joe composed on 2021-06-11 20:14 (UTC+0100):
>
> > I have a netbook which booted fine into grub on stretch,
> > but an upgrade to buster killed that, and to boot into buster I
> > have to use a rescue medium and use efibootmgr to set NextBo
Joe composed on 2021-06-11 20:14 (UTC+0100):
> I have a netbook which booted fine into grub on stretch,
> but an upgrade to buster killed that, and to boot into buster I have to
> use a rescue medium and use efibootmgr to set NextBoot to the right
> entry. Nobody here seems able to help, and I gav
On Sat, Jun 12, 2021 at 12:52:47AM +0300, Semih Ozlem wrote:
> Yes I am running in UEFI mode, but the partitioning is MBR and not GPT. Is
> this a problem? Which is preferred when?
Really, GPT is the future. The "MBR" disk label is another product of
the 1980s. It doesn't even support disks over
Dear Greg, and everyone else thanks for the detailed responses.
By UEFI versus Legacy Boot you mean things that are determined in BIOS
settings correct?
Yes I am running in UEFI mode, but the partitioning is MBR and not GPT. Is
this a problem? Which is preferred when? Why would legacy boot be pre
Greg Wooledge composed on 2021-06-11 15:07 (UTC-0400):
> On Fri, Jun 11, 2021 at 09:38:37PM +0300, Semih Ozlem wrote:
>> How to check where grub is installed? And what is a friendly guide to
>> learning about grub?
> GRUB should be installed on the *disk* (not on a partition) that you
> intend t
On Fri, 11 Jun 2021 21:38:37 +0300
Semih Ozlem wrote:
> I reinstalled the system, including an efi partition (500MiB) and the
> problem was fixed.
>
> How to check where grub is installed? And what is a friendly guide to
> learning about grub?
I don't like quoting specific sources, as they go o
On Fri, Jun 11, 2021 at 09:38:37PM +0300, Semih Ozlem wrote:
> I reinstalled the system, including an efi partition (500MiB) and the
> problem was fixed.
This suggests that you booted the installer in UEFI mode, rather than in
Legacy mode. If you boot the installer in UEFI mode, you are expected
I reinstalled the system, including an efi partition (500MiB) and the
problem was fixed.
How to check where grub is installed? And what is a friendly guide to
learning about grub?
Richard Owlett , 11 Haz 2021 Cum, 20:17 tarihinde şunu
yazdı:
> On 06/11/2021 11:31 AM, Semih Ozlem wrote:
> > Hi ev
On 06/11/2021 11:31 AM, Semih Ozlem wrote:
Hi everyone,
I am using 64bit with 4GiB system memory Intel COre i3-7100U @ 2.40 GHZ
machine. I installed debian on a usb (sandisk cruzer blade 2.0 32 GB). I
created a single partition.
At the moment the system does not boot. From the installation medi
Hi everyone,
I am using 64bit with 4GiB system memory Intel COre i3-7100U @ 2.40 GHZ
machine. I installed debian on a usb (sandisk cruzer blade 2.0 32 GB). I
created a single partition.
At the moment the system does not boot. From the installation media grub
menu shows up.
Is there a way without
Hello
Kent West (<[EMAIL PROTECTED]>) wrote:
> Sreelal Chandrasenan wrote:
>> [...]
>> Even Debian could not detect the ethernetcard on the P4 board,
>> though it was detected by Redhat 9.X and Windows 2K. It is an Intel
>> Pro 100 based card. I tried different Debain CDs, still I am getting
>
Hello
Sreelal Chandrasenan (<[EMAIL PROTECTED]>) wrote:
> One of the Pentium 4 box, when I instaled the Debian linux, I got
> nano_1.0.6_2_i386.deb corrupt error and I am unable to proceed further
> with installation. I tried multiple times and I could not succeed. I
> could install debian on oth
>
> --
> From: Sreelal Chandrasenan
> Sent: Monday, December 15, 2003 9:25:22 AM
> To: Debian User (E-mail)
> Subject: FW: Debian installation issue
> Auto forwarded by a Rule
>
>
>
-Original Message-
From: Sreelal Chandrase
Sreelal Chandrasenan wrote:
One of the Pentium 4 box, when I instaled the Debian linux, I got nano_1.0.6_2_i386.deb corrupt error and I am unable to proceed further with installation.
I tried multiple times and I could not succeed. I could install debian on other Pentium3 systems using the same CD
-Original Message-
From: Sreelal Chandrasenan
Sent: Monday, December 15, 2003 9:09 AM
To: [EMAIL PROTECTED]
Subject: Debian installation issue
One of the Pentium 4 box, when I instaled the Debian linux, I got
nano_1.0.6_2_i386.deb corrupt error and I am unable to proceed further
One of the Pentium 4 box, when I instaled the Debian linux, I got
nano_1.0.6_2_i386.deb corrupt error and I am unable to proceed further with
installation.
I tried multiple times and I could not succeed. I could install debian on other
Pentium3 systems using the same CD without any problem.
E
40 matches
Mail list logo
