From: tuxic@posteo.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ...recreating exactly the same applications on a new harddisc?
Date: Sun, 5 Apr 2020 10:17:41 +0200 [thread overview]
Message-ID: <20200405081741.o32ew747jluxa3qg@solfire> (raw)
In-Reply-To: <8b767f42-0945-ecd7-fcff-5fc0277841fd@spamtrap.tnetconsulting.net>
On 04/04 03:56, Grant Taylor wrote:
> On 4/4/20 11:34 AM, tuxic@posteo.de wrote:
> > Hi,
>
> Hi,
>
> > I am currently preparing a new harddisc as home for my new Gentoo
> > system.
> >
> > Is it possible to recreate exactlu the same pool of
> > applications/programs/libraries etc..., which my current system have -
> > in one go?
>
> Baring cosmic influences, I would expect so.
>
> > That is: Copy <something> from the current system into the chroot
> > environment, fire up emerge, go to bed and tommorow morning the new
> > system ready...?
> >
> > Does this <something> exists and is it reasonable to do it this way?
> >
> > Thanks for any hint in advance!
>
> I think that any given system is the product of it's various components.
> Change any of those components, and you change the product.
>
> I see the list of components as being at least:
>
> · world file
> · portage config (/etc/portage)
> · USEs
> · accepted keywords
> · accepted licenses
> · portage files (/usr/portage)
> · this significantly influences the version of packages that get
> installed, which is quite important
> · kernel
> · version
> · config
>
> Copying these things across should get you a quite similar system. I
> suspect you would be down to how different packages are configured.
>
> But the world file is only one of many parts that make up the system.
>
> I didn't include distfiles because theoretically, you can re-download files.
> However, I've run into cases where I wasn't able to download something and
> had to transfer (part of) distfiles too.
>
> If you're going to the trouble to keep a system this similar, why not simply
> copy the system from one drive / machine to another?
>
>
>
> --
> Grant. . . .
> unix || die
Hi,
a new morning... :)
Being on the way to install/setup the base system (mostly getting
stage3 uptodate) I came accross kinda inconsistency -- or at least
it looks like for me.
The system uses a 3T harddisc (and later a SSD) and therefore GPT.
GPT is the sister/brother of an U/EFI boot.
For that the documentation (AMD64 handbook):
https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks#Using_UEFI
says:
Default partitioning scheme
Throughout the remainder of the handbook, the following partitioning scheme will be used as a simple example layout:
Partition Filesystem Size Description
/dev/sda1 (bootloader) 2M BIOS boot partition
/dev/sda2 ext2 (or fat32 if UEFI is being used) 128M Boot/EFI system partition
/dev/sda3 (swap) 512M or higher Swap partition
/dev/sda4 ext4 Rest of the disk Root partition
and later on at https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/System
FILE /etc/fstabA full /etc/fstab example
/dev/sda2 /boot ext2 defaults,noatime 0 2
/dev/sda3 none swap sw 0 0
/dev/sda4 / ext4 noatime 0 1
/dev/cdrom /mnt/cdrom auto noauto,user 0 0
Here /boot changes from fat32 to ext2.
Since this is my first U/EFI system I am a little confused.
Currentlu it looks like the vmlinuz binaries will be installed on
a FAT32 filesystem. Since the kernel can be launched from a ext4
filesystem I cannot see, why this have to be a FAT32 filesystem.
My plan (if this is possible), is to U/EFI-boot grub, from which
I can select the kernel in question as it has been on my old
system (MBR based).
My current partition table looks like (only relevant parts shown):
Number Start End Size File system Name Flags
1 1049kB 3146kB 2097kB grub bios_grub
2 3146kB 137MB 134MB fat32 boot boot, esp
3 137MB 674MB 537MB linux-swap(v1) swap
4 674MB 269GB 268GB ext4 root
What did I messed up here?
Cheers!
Meino
next prev parent reply other threads:[~2020-04-05 8:17 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 17:34 [gentoo-user] ...recreating exactly the same applications on a new harddisc? tuxic
2020-04-04 17:59 ` [gentoo-user] " Ian Zimmerman
2020-04-04 18:03 ` tuxic
2020-04-05 17:41 ` Ian Zimmerman
2020-04-05 19:53 ` Jack
2020-04-05 19:57 ` Jack
2020-04-04 21:26 ` Neil Bothwick
2020-04-04 23:46 ` Peter Humphrey
2020-04-04 18:05 ` [gentoo-user] " Mark Knecht
2020-04-04 18:23 ` tuxic
2020-04-04 18:57 ` Mark Knecht
2020-04-04 18:33 ` Dale
2020-04-04 21:42 ` John Covici
2020-04-04 22:24 ` Dale
2020-04-04 18:25 ` Ashley Dixon
2020-04-04 19:05 ` tuxic
2020-04-04 19:29 ` Ashley Dixon
2020-04-04 19:30 ` Mark Knecht
2020-04-04 19:59 ` tuxic
2020-04-05 9:21 ` [OT] " Peter Humphrey
2020-04-05 9:29 ` Peter Humphrey
2020-04-04 21:56 ` Grant Taylor
2020-04-05 8:17 ` tuxic [this message]
2020-04-05 9:28 ` Ashley Dixon
2020-04-05 12:52 ` Neil Bothwick
2020-04-05 12:56 ` Ashley Dixon
2020-04-05 13:37 ` Michael
2020-04-05 14:56 ` Neil Bothwick
2020-04-05 18:08 ` Peter Humphrey
2020-04-05 19:39 ` Neil Bothwick
2020-04-06 10:17 ` Peter Humphrey
2020-04-06 21:02 ` antlists
2020-04-06 21:15 ` Neil Bothwick
2020-04-06 23:38 ` Michael
2020-04-07 15:23 ` antlists
2020-04-11 15:37 ` Marc Joliet
2020-04-08 1:02 ` William Kenworthy
2020-04-05 9:46 ` Michael
2020-04-05 10:52 ` tuxic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200405081741.o32ew747jluxa3qg@solfire \
--to=tuxic@posteo.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox