On Tue 02 May 2023 at 12:10:48 (+0200), DdB wrote:
> I notice, that, even though i did change the name of the sda2 partition,
> the PARTLABEl remained unchanged.
It's rather confusing that gdisk (my preferred partitioner, which
I use outside the installer) refers to the PARTLABEL as the
DdB wrote:
...
> I notice, that, even though i did change the name of the sda2 partition,
> the PARTLABEl remained unchanged.
> This proves my previous post wrong and i am sorry for the confusion,
> this may have caused. You were correct all along.
> DdB
yes, but i also recall you saying
Am 02.05.2023 um 05:50 schrieb David Wright:
> On Tue 02 May 2023 at 02:21:20 (+0200), DdB wrote:
>> Am 01.05.2023 um 21:38 schrieb David Wright:
>>> And PARTLABELs aren't interfered with even by the installer.
>>
>> This at least i can contradict for a fact.
>
> So is this post the rebuttal, or
On 5/1/23 17:13, DdB wrote:
Am 01.05.2023 um 19:46 schrieb David Christensen:
Reading the above plus your previous post "Looking for
inspiration/advice/best practices on system upgrade", it seems that you
are making things too complicated.
I would pick one machine, disable/ disconnect/
On Tue 02 May 2023 at 02:21:20 (+0200), DdB wrote:
> Am 01.05.2023 um 21:38 schrieb David Wright:
> > And PARTLABELs aren't interfered with even by the installer.
>
> This at least i can contradict for a fact.
So is this post the rebuttal, or are you posting the evidence elsewhere?
> VM is
Am 01.05.2023 um 21:38 schrieb David Wright:
> And PARTLABELs aren't interfered with even by the installer.
This at least i can contradict for a fact. VM is functional with known
and documented partlabels, then the installer handles partitions
(reformat is permitted) and the UUID's AND the
Am 01.05.2023 um 19:46 schrieb David Christensen:
> Reading the above plus your previous post "Looking for
> inspiration/advice/best practices on system upgrade", it seems that you
> are making things too complicated.
>
>
> I would pick one machine, disable/ disconnect/ uninstall all of the
>
Am 01.05.2023 um 10:33 schrieb Michel Verdier:
> Le 1 mai 2023 DdB a écrit :
>
>> Any suggestions/questions/hints from the power-users in here?
>> ... would be wildly appreciated ...
>
> When installing you have to stop on your first problem. The others could
> be created from it. It's longer
On Mon 01 May 2023 at 13:08:56 (+0200), DdB wrote:
> One explanation of my choice to stick with PARTUUID's:
> In my overall stategy of using my computer, i am sometimes copying (dd)
> whole partitions into a backup, a secondary partition or a VM, which can
> easily lead to difficulties, if the
On 4/30/23 18:11, DdB wrote:
Hello list,
after receiving so much good advice, i finally made up my mind and began
playing through the installation (debian bullseye, current stable) in my
simulation-VM in order to learn about the pitfalls to avoid. After more
than a dozen tries, i am running out
On Mon, May 01, 2023 at 01:08:56PM +0200, DdB wrote:
> Am 01.05.2023 um 10:23 schrieb Michel Verdier:
> > Le 1 mai 2023 DdB a écrit :
> >
> >> But omitting GNOME from the list lead to a system failing to boot with
> >> tons of messages stating the absense of all kind of gnome parts.
> >
> > To
Am 01.05.2023 um 10:23 schrieb Michel Verdier:
> Le 1 mai 2023 DdB a écrit :
>
>> But omitting GNOME from the list lead to a system failing to boot with
>> tons of messages stating the absense of all kind of gnome parts.
>
> To install without gnome I select the task ssh server then after I
>
Le 1 mai 2023 DdB a écrit :
> Any suggestions/questions/hints from the power-users in here?
> ... would be wildly appreciated ...
When installing you have to stop on your first problem. The others could
be created from it. It's longer but easier to cope with. So give us full
details on your
Le 1 mai 2023 DdB a écrit :
> But omitting GNOME from the list lead to a system failing to boot with
> tons of messages stating the absense of all kind of gnome parts.
To install without gnome I select the task ssh server then after I
manually select what I want, and a WM if needed.
On Mon 01 May 2023 at 03:11:56 (+0200), DdB wrote:
> For example, when i allow the use of the swap partition, it gets
> reformatted and another PARTUUID is assigned to it, leading to failures
> booting other systems from that disk.
The easy way to avoid that problem is to use LABEL rather than
Hello list,
after receiving so much good advice, i finally made up my mind and began
playing through the installation (debian bullseye, current stable) in my
simulation-VM in order to learn about the pitfalls to avoid. After more
than a dozen tries, i am running out of fuel, because i am
Hello everyone,
I partly solved my problem and I would like to share my solution:
Until now, I thought that the EFI removable media path (\EFI\BOOT\BOOTX64.EFI)
is really a fallback location, i.e. a location for putting the boot loader that
just always works. Therefore I thought that I could
On Thu 27 Apr 2023 at 10:18:56 (+0700), Max Nikulin wrote:
> On 26/04/2023 22:57, Valentin Caracalla wrote:
> > the issue with the BIOS boot interface (see my original posting) is still
> > unsolved
>
> I had impression that there was no issue with booting in BIOS (legacy,
> compatibility, CSM)
On 26/04/2023 22:57, Valentin Caracalla wrote:
the issue with the BIOS boot interface (see my original posting) is still
unsolved
I had impression that there was no issue with booting in BIOS (legacy,
compatibility, CSM) mode, of course when it is chosen in firmware/BIOS
setup (requires
Hello Max,
thanks a lot for your input! I do, however, believe that the problem has a
different cause. I came to that conclusion, mainly because the issue with the
BIOS boot interface (see my original posting) is still unsolved, but also
because I tried using the EFI removable media path
David Wright (12023-04-25):
> Don't knock it! The Human Era is much easier for us to parse than
;-)
> the French Republican calendar (pre 2018).
I had not realized I had fans devoted to the point of tracking the eras
of my mail attribution. ;-)²
Regards,
--
Nicolas George
signature.asc
Greg Wooledge (12023-04-25):
> find /mnt/boot/efi -exec ls -dl {} +
zsh
ls -dl /mnt/boot/efi/**/*
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
On Wed 26 Apr 2023 at 09:14:25 (+0700), Max Nikulin wrote:
> On 26/04/2023 00:42, Nicolas George wrote:
> > Steve McIntyre (12023-04-25):
[ … ]
> P.S. Nicolas, it seems your mailer has issues with parsing or
> formatting timestamps.
Don't knock it! The Human Era is much easier for us to parse
On Wed, Apr 26, 2023 at 09:34:11AM +0700, Max Nikulin wrote:
> On 26/04/2023 05:02, Valentin Caracalla wrote:
> >
> > user@host:~$ ls -dl $(find /mnt/boot/efi)
>
> find /mnt/boot/efi -print0 | xargs -0 ls -dl --
>
> should be more resistant to peculiar file names, but it does not matter in
>
On 26/04/2023 05:02, Valentin Caracalla wrote:
user@host:~$ ls -dl $(find /mnt/boot/efi)
find /mnt/boot/efi -print0 | xargs -0 ls -dl --
should be more resistant to peculiar file names, but it does not matter
in this case.
...
-rwxr-xr-x 1 root root 126 Apr 25 13:59
On 26/04/2023 00:42, Nicolas George wrote:
Steve McIntyre (12023-04-25):
If you do not intend to install a Microsoft bootloader or anything
besides GRUB, 16 megaoctets is plenty enough, probably can work with
less.
Please STOP giving this advice to people!
That was not advice, that was
Valentin Caracalla (12023-04-26):
> EFI variables are not supported on this system.
To install GRUB in UEFI, you need to have booted the kernel in UEFI.
Try to find a live image that does, and you can reinstall GRUB from
there.
Regards,
--
Nicolas George
signature.asc
Description: PGP
Here's the output you requested:
user@host:~$ ls -dl $(find /mnt/boot/efi)
drwxr-xr-x 3 root root 32768 Jan 1 1970 /mnt/boot/efi
drwxr-xr-x 3 root root 32768 Apr 25 13:59 /mnt/boot/efi/EFI
drwxr-xr-x 2 root root 32768 Apr 25 13:59 /mnt/boot/efi/EFI/debian
-rwxr-xr-x 1 root root
Steve McIntyre (12023-04-25):
> >If you do not intend to install a Microsoft bootloader or anything
> >besides GRUB, 16 megaoctets is plenty enough, probably can work with
> >less.
> Please STOP giving this advice to people!
That was not advice, that was information. Make your own advice with it.
Nicolas George wrote:
>Max Nikulin (12023-04-25):
>> 0.5GB is usually enough, e.g. 550MiB recommended by
>> https://www.rodsbooks.com/gdisk/advice.html#esp_sizing)
>
>If you do not intend to install a Microsoft bootloader or anything
>besides GRUB, 16 megaoctets is plenty enough, probably can work
Max Nikulin (12023-04-25):
> 0.5GB is usually enough, e.g. 550MiB recommended by
> https://www.rodsbooks.com/gdisk/advice.html#esp_sizing)
If you do not intend to install a Microsoft bootloader or anything
besides GRUB, 16 megaoctets is plenty enough, probably can work with
less.
Regards,
--
On 25/04/2023 21:40, Valentin Caracalla wrote:
I checked my partition table using "sudo parted /dev/sda print"
Number Start End Size File system Name Flags
1 1049kB 128GB 128GB fat32 init boot, esp
2 128GB 256GB 128GB ext4 root
Please, show
vorubergeh...@tutanota.com wrote:
>By the way:
>
>The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the
>following will not show a GRUB command line:
>
>sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda
>
>The same thing works for the BIOS boot interface, however (as in
Valentin Caracalla (12023-04-25):
> The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the
> following will not show a GRUB command line:
>
> sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda
Oh, I must check if the KVM virtual machine booting on UEFI I have been
toying
By the way:
The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the
following will not show a GRUB command line:
sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda
The same thing works for the BIOS boot interface, however (as in my original
recipe).
I apologize for the formatting in my last post, I don't know what happened. And
many thanks for your help!
I checked my partition table using "sudo parted /dev/sda print" and it didn't
show any flags for partition 1 (the "init" partition). Therefore I manually set
the flags using "sudo parted
Valentin Caracalla writes:
> But this doesn't work either. Same problem here. However I can make
> such an EFI installation using official installation media on the same
> machine and that does work.
That recipe (and the whole post) was hard to read but don't you need
some flags for the ESP
> I can't see anything wrong with the script. Did that installation use> GPT
> and a BIOS Boot Partition though?The successful installation (with official
> installation media) used aBIOS partition table, but I prefer GPT.> I guess I
> have to ask, why not just use UEFI?I also tried that and I
There are a few things I forgot to say:
The recipe I posted earlier is executed on a system installed on the external
drive /dev/sdb, which I call the installer system. It is also a Debian system,
with the recipe's dependencies installed. To reproduce the issue (if you want),
I suggest using a
Valentin Caracalla writes:
> Previously, I've successfully installaed Debian using official
> installation media on this machine (also using BIOS boot interface),
> so I know that it works in principle.
I can't see anything wrong with the script. Did that installation use
GPT and a BIOS Boot
Hello everyone,
I'm trying to install Debian on my Asus UX31A using command line utilities like
debootstrap and grub-install. However, the installed system is not bootable.
The problem is that the internal drive (which I install the system to) doesn't
show up in the boot menu (which is what
> For some unknown reason, network configuration (wireless networks
> etc.) in NetworkManager includes the MAC address of the local NIC
> too, so you may need to fix those up after transfer.
This sucks, indeed. I can't understand why they do that (maybe as an
option, I could see
ottavio2006-usenet2...@yahoo.com wrote:
>I have an old Thinkpad on its last legs which I cannot shutdown (long
>story). Then I have a slightly better Thinkpad with similar hard
>drive. Debian is split into three partitions (root. home and swap)/
>
>I'll recreate a similar partitioning from a live
On Mon 14 Nov 2022 at 14:53:34 (+), Ottavio Caruso wrote:
> I have an old Thinkpad on its last legs which I cannot shutdown (long
> story). Then I have a slightly better Thinkpad with similar hard
> drive. Debian is split into three partitions (root. home and swap)/
>
> I'll recreate a
* On 2022 14 Nov 09:16 -0600, Ottavio Caruso wrote:
> I have an old Thinkpad on its last legs which I cannot shutdown (long
> story). Then I have a slightly better Thinkpad with similar hard
> drive. Debian is split into three partitions (root. home and swap)/
>
> I'll recreate a similar
On 11/14/22 06:53, Ottavio Caruso wrote:
I have an old Thinkpad on its last legs which I cannot shutdown (long
story). Then I have a slightly better Thinkpad with similar hard
drive. Debian is split into three partitions (root. home and swap)/
I'll recreate a similar partitioning from a live
> On 14 Nov 2022, at 15:15, Ottavio Caruso
> wrote:
>
> [..] copy the data on the new drive, reinstall grub and modify
> fstab.
>
> Will this work?
Depends on what kind of “copy” you make. You will need to keep ownership,
permissions and links intact. And possibly more.
I would install
I have an old Thinkpad on its last legs which I cannot shutdown (long
story). Then I have a slightly better Thinkpad with similar hard
drive. Debian is split into three partitions (root. home and swap)/
I'll recreate a similar partitioning from a live usb on the newer
laptop, then I'll mount the
On Tue 15 Feb 2022 at 14:20:55 (-0500), Felix Miata wrote:
> David Wright composed on 2022-02-15 10:11 (UTC-0600):
>
> > Is anything else required for B to become a "native EFI" installation?
>
> > This conversion process will, I think, make the system boot into
> > the EFI-ed B by default. If I
David Wright composed on 2022-02-15 10:11 (UTC-0600):
> Is anything else required for B to become a "native EFI" installation?
> This conversion process will, I think, make the system boot into
> the EFI-ed B by default. If I want to make E boot by default again,
> should I boot E and run
served partitions) ² have been overwritten with Debian
installation E.
The disk has all the necessary components: GPT partitioning, with
a protective MBR and BIOS boot partition for B's use, and the
original ESP for E's (and B's future) use, plus shared /home
(encrypted), and a random encryp
On Tue, Feb 15, 2022 at 12:31:58PM +0200, Anssi Saari wrote:
> Thomas Anderson writes:
>
> > I am curious, what would happen if I threw a fully functionally,
> >
> > Linux installation (HDD) into an entirely different hardware configuration:
> >
> > Different Process AMD->Intel?
> >
> > Ram/mobo
Thomas Anderson writes:
> I am curious, what would happen if I threw a fully functionally,
>
> Linux installation (HDD) into an entirely different hardware configuration:
>
> Different Process AMD->Intel?
>
> Ram/mobo I assume doesn't matter?
>
> I half expect it to boot up, and be fully
Thanks for replies. It all makes sense once I get the answers. =)
On 2/15/22 07:29, to...@tuxteam.de wrote:
On Tue, Feb 15, 2022 at 01:58:24AM +0100, Thomas Anderson wrote:
I am curious, what would happen if I threw a fully functionally,
Linux installation (HDD) into an entirely different
On Tue, Feb 15, 2022 at 01:58:24AM +0100, Thomas Anderson wrote:
> I am curious, what would happen if I threw a fully functionally,
>
> Linux installation (HDD) into an entirely different hardware configuration:
It depends :-)
It starts with the bootloader: different hardware boots in very
On 2022-02-14 19:58, Thomas Anderson wrote:
> I am curious, what would happen if I threw a fully functionally,
>
> Linux installation (HDD) into an entirely different hardware configuration:
>
> Different Process AMD->Intel?
>
> Ram/mobo I assume doesn't matter?
>
> I half expect it to boot
I am curious, what would happen if I threw a fully functionally,
Linux installation (HDD) into an entirely different hardware configuration:
Different Process AMD->Intel?
Ram/mobo I assume doesn't matter?
I half expect it to boot up, and be fully functional.
But, I have not tested it.
I am
Am Montag, 10. Januar 2022, 16:21:25 CET schrieb Eric S Fraga:
Had a similar issue with a notebook from Dell some time ago.
The reason was, that the binary firmware did not exist on on the installer
cdrom or dvd. The network interface was just too new!
This is a problem with debian's policy and
On Saturday, 8 Jan 2022 at 20:07, Andrew M.A. Cater wrote:
> If you can bear it: reinstall, using the unofficial image, including
> non-free firmware.
I had to do this for a recently purchased Dell laptop with Intel NIC
on-board. Worked just fine this way but wouldn't install without the
sciguy composed on 2022-01-08 12:13 (UTC-0500):
> It seems the root of my problem is in Microsoft's choice to take over
> the EFI in a recent update, thereby supplanting GRUB, which was there
> before. GRUB was a technology I understood fairly well; EFI is not. Can
> anyone suggest, or point
etting a network, and so
> the installation remains half-finished.
>
> Somehow, after changing this over to Debian, where the installation failed
> for the same reason, Windows 10 EFI detected the incomplete installation and
> now offers "finishing the Debian installation" as a boot opt
the installation remains half-finished.
>
> Somehow, after changing this over to Debian, where the installation
> failed for the same reason, Windows 10 EFI detected the incomplete
> installation and now offers "finishing the Debian installation" as a
> boot opt
to Debian, where the installation
failed for the same reason, Windows 10 EFI detected the incomplete
installation and now offers "finishing the Debian installation" as a
boot option when I reboot.
It seems the root of my problem is in Microsoft's choice to take over
the EFI in a rec
On 10/12/21 21:47, Andrei POPESCU wrote:
On Ma, 12 oct 21, 00:02:50, David Christensen wrote:
On 10/11/21 23:58, Andrei POPESCU wrote:
On Lu, 11 oct 21, 13:56:28, David Christensen wrote:
On 10/11/21 13:39, Andrei POPESCU wrote:
ZFS has native encryption now, any particular reason to
On Ma, 12 oct 21, 00:02:50, David Christensen wrote:
> On 10/11/21 23:58, Andrei POPESCU wrote:
> > On Lu, 11 oct 21, 13:56:28, David Christensen wrote:
> > > On 10/11/21 13:39, Andrei POPESCU wrote:
>
> > > > ZFS has native encryption now, any particular reason to prefer using a
> > > > LUKS
On Mon, 11 Oct 2021 14:03:50 -0700
David Christensen wrote:
> On 10/11/21 13:13, Joe wrote:
> > On Mon, 11 Oct 2021 12:29:48 -0700
> > David Christensen wrote:
> >
> >
> >> I must detach e-mail attachments and save them on the server
> >
> > You could run an IMAP server on your server,
On 10/11/21 23:58, Andrei POPESCU wrote:
On Lu, 11 oct 21, 13:56:28, David Christensen wrote:
On 10/11/21 13:39, Andrei POPESCU wrote:
ZFS has native encryption now, any particular reason to prefer using a
LUKS container instead?
I use LUKS because ZFS native encryption was not available
On Lu, 11 oct 21, 13:56:28, David Christensen wrote:
> On 10/11/21 13:39, Andrei POPESCU wrote:
> > On Lu, 11 oct 21, 12:29:48, David Christensen wrote:
> > >
> > > Once Debian is running, I suggest that you connect the HDD, partition the
> > > HDD using GPT, create one partition using 95% of
On 10/11/21 13:13, Joe wrote:
On Mon, 11 Oct 2021 12:29:48 -0700
David Christensen wrote:
I must detach e-mail attachments and save them on the server
You could run an IMAP server on your server, set up an account in your
email client with a suitable directory structure and drag and drop
On 10/11/21 13:39, Andrei POPESCU wrote:
On Lu, 11 oct 21, 12:29:48, David Christensen wrote:
Once Debian is running, I suggest that you connect the HDD, partition the
HDD using GPT, create one partition using 95% of available space, initialize
a LUKS container inside the partition, and create
On Lu, 11 oct 21, 12:29:48, David Christensen wrote:
>
> Once Debian is running, I suggest that you connect the HDD, partition the
> HDD using GPT, create one partition using 95% of available space, initialize
> a LUKS container inside the partition, and create a ZFS pool with name
> "data" and
On Mon, 11 Oct 2021 12:29:48 -0700
David Christensen wrote:
> I must detach
> e-mail attachments and save them on the server
You could run an IMAP server on your server, set up an account in your
email client with a suitable directory structure and drag and drop old
email into archives,
On 10/11/21 04:18, Josef Strýček wrote:
Hi,
I have a question how to partition new debain installation.I have 64GB ssd
and 500GB hdd. Can I have / on ssd with ext4 and hdd with btrfs /hame /var
/tmp /opt.
You should be able to achieve that layout with the Debian installer
(d-i) by
Hi Josef,
On Mon, Oct 11, 2021 at 01:18:55PM +0200, Josef Strýček wrote:
> I have a question how to partition new debain installation.I have 64GB ssd
> and 500GB hdd. Can I have / on ssd with ext4 and hdd with btrfs /hame /var
Of course.
> /tmp /opt. Could you recommend layout for ssd and hdd,
On Lu, 11 oct 21, 13:18:55, Josef Strýček wrote:
>
> Hi,
>
> I have a question how to partition new debain installation.I have 64GB ssd
> and 500GB hdd. Can I have / on ssd with ext4 and hdd with btrfs /hame /var
>
> /tmp /opt.
Sure you can.
> Could you recommend layout for ssd and hdd, that
On Mon, Oct 11, 2021 at 01:18:55PM +0200, Josef Strýček wrote:
>
> Hi,
>
> I have a question how to partition new debain installation.I have 64GB ssd
> and 500GB hdd. Can I have / on ssd with ext4 and hdd with btrfs /hame /var
>
> /tmp /opt. Could you recommend layout for ssd and hdd, that ssd
Hi,
I have a question how to partition new debain installation.I have 64GB ssd
and 500GB hdd. Can I have / on ssd with ext4 and hdd with btrfs /hame /var
/tmp /opt. Could you recommend layout for ssd and hdd, that ssd is not
overwritten unnecessarily and ideal filesystem for ssd and hdd.
Hi,
Fred 1 wrote:
> hope I can change it and rebuild the netinstall ISO with jigdo maybe ?
Jigdo is not suitable for making changes to the ISO which it reconstructs.
(It is rather suitable for reducing the download effort with ISOs which
are slightly changed towards an ISO which you already
Fred 1 writes:
I would like to know where the installation pulls the list of Debian
mirrors.
hope I can change it and rebuild the netinstall ISO with jigdo maybe ?
It would be nice if I could manually add a custom one during install, but I
didn't see such option, strictly just pick from
On 24/08/2021 02:00, Dan Ritter wrote:
Fred 1 wrote:
I would like to know where the installation pulls the list of Debian
mirrors.
hope I can change it and rebuild the netinstall ISO with jigdo maybe ?
It would be nice if I could manually add a custom one during install, but I
didn't see
Fred 1 wrote:
> I would like to know where the installation pulls the list of Debian
> mirrors.
>
> hope I can change it and rebuild the netinstall ISO with jigdo maybe ?
>
> It would be nice if I could manually add a custom one during install, but I
> didn't see such option, strictly just
On Tue 24 Aug 2021 at 01:36:41 +1000, Fred 1 wrote:
> I would like to know where the installation pulls the list of Debian
> mirrors.
>
> hope I can change it and rebuild the netinstall ISO with jigdo maybe ?
>
> It would be nice if I could manually add a custom one during install, but I
>
Am Montag, 23. August 2021, 17:36:41 CEST schrieb Fred 1:
Hi,
you do not need to reinstall. You will find a list of debian mirrors on the
website of debian.
Then you can entry or edit the mirror in the file /etc/apt/sources.list. You
can also use deb.debian.org as debian repo in this file.
I would like to know where the installation pulls the list of Debian
mirrors.
hope I can change it and rebuild the netinstall ISO with jigdo maybe ?
It would be nice if I could manually add a custom one during install,
but I didn't see such option, strictly just pick from the list
Yes, unfortunately, this is necessary to use SEV. Please take a look at these
instructions.
https://libvirt.org/kbase/launch_security_sev.html
https://developer.amd.com/sev/
The settings memtune, uefi, iommu are required to use launchSecurity = sev
The use for secured KVM using AMD Secure
There is no need to PM me. I am subscribed to the mailinglist.
On Tue, Aug 10, 2021 at 02:06:04PM +0200, Office onFocus wrote:
> these are my iso files:
>
[...]
> wget
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.10.0-amd64-netinst.iso
> wget
>
On Mon, Aug 09, 2021 at 02:04:49PM +0200, Office onFocus wrote:
> I cannot start an installation of a debian * .iso (install, live, ..) from
> any installation medium.
>
> This problem affects all Debian images. There are no problems with Ubuntu or
> CentOS! As soon as you
> boot the ISO and
I cannot start an installation of a debian * .iso (install, live, ..) from any
installation medium.
This problem affects all Debian images. There are no problems with Ubuntu or
CentOS! As soon as you
boot the ISO and click Install, there is no error message and the boot process
begins again
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
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
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
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
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
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)
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
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
[ 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
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
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
1 - 100 of 1352 matches
Mail list logo
