[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: trying to install bullseye for about 25th time.



On Friday, 10 June 2022 00:22:53 EDT David Wright wrote:
> On Thu 09 Jun 2022 at 15:44:48 (-0400), gene heskett wrote:
> > On Thursday, 9 June 2022 11:04:15 EDT David Wright wrote:
> > > On Thu 09 Jun 2022 at 03:46:12 (-0400), gene heskett wrote:
> > > > On Thursday, 9 June 2022 00:33:33 EDT David Wright wrote:
> > > > > On Tue 07 Jun 2022 at 16:24:02 (-0400), gene heskett wrote:
> > > > > > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote:
> > > > > > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett 
wrote:
> > > > > I always install my systems in this manner from my normal
> > > > > workstation.
> > > > 
> > > > This IS my normal workstation. But I imagine that I could reverse
> > > > the
> > > > path from one of my Dells dedicated to a task. Only one has a
> > > > comfy
> > > > chair though, the one normally running my biggest milling
> > > > machine,
> > > > out in the garage. I'll take my coffee cup out and try this from
> > > > there.
> > > 
> > > Unsurprisingly, I use the second most convenient machine to install
> > > onto that one. In addition, I lose the benefit of apt-cacher-ng for
> > > that particular installation process. If I'm installing a new
> > > release,
> > > then I save the normal cache's contents, and later import all its
> > > .deb
> > > files into apt-cacher-ng on my workstation's new installation.
> > > 
> > > One more convenience of installing like this is that you can have
> > > the
> > > release notes, your own aide-memoires, and other reference
> > > documents,
> > > open on the same machine while you're running the installer.
> > 
> > Here is that partitioner menu snapshot, obtained by a network ssh
> > login, smunched to 81kb base-64'd. Showing that d-i did not even
> > recognize the disk I want to use for this new install.
> > 
> > So how & what do I do to this virgin disk to make the d-i recognize
> > it so I can install to it?
> 
> Well, you already know what I would do as it's been posted on this
> list before: partition it with my personal favourite, gdisk.
> 
> But before I started, I would list /dev/disk/ to checkout all the
> installed disks, and their correspondence with the /dev/sd* or
> /dev/nvme0n* names. This avoid's mick's problem.
> 
> I'd then write a GPT-style partition table, and the partitions
> I wanted, create the EFI partition, and change the names of
> the other partitions to my requirements. (All my disks are named,
> and the partition LABELs and PARTLABELs are based on that name.)
> 
> But I haven't used LVMs, and their users might have a different
> strategy.
> 
I had some nightmares with LVM back in its younger days, and have shied 
away from it since. But I'd assume its more stable now than it was in 
ext3 days long ago.

> Cheers,
> David.
> 
> .


Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis




Reply to: