Re: [gentoo-dev] Re: [Fwd: [gentoo-admin] Building a second system]

[Bart Verwilst]

Euhm.. Isn't it much easier to just for example:

mkdir /mnt/my_new_system
cd /mnt_my_new_system
tar -xvjpf /path/to/stagex-i486-1.4_rc2.tbz2
mount -o bind /proc /mnt/my_new_system/proc
mount -o bind /usr/portage /mnt/my_new_system/usr/portage
cp /etc/resolv.conf /mnt/my_new_system/etc
chroot /mnt/my_new_system  /bin/bash
env-update 
source /etc/profile
nano -w /etc/make.conf

and so on...

On Monday 06 January 2003 01:02, Arnold deVos wrote:
||  I have exactly the same need.  A powerful Athlon building packages for a
|| an older 486 or pentium box (eg firewall or other appliance).   I have
|| experimented with the following ideas:
||
||  1 -
||
||      - create a /my486Image hierarchy
||      - setup the /my486Image/etc/make.conf  for cross compiling.
||      - export ROOT=/my486image (instead of /)
||      - use emerge from within the host (Athlon) system.
||
||  Unfortunately emerge seems to touch stuff outside of ROOT such as the
||  package db.
||
||  2 -
||
||      - create a normal chroot environment for the 486
||      - mount the Athlon enviroment within this as /hostAlthonImage.
||      - Set the PATH to /hostAthlonImage/bin:/hostAthlonImage/usr/bin etc
|| etc - use emerge (ie /hostAthlonImage/usr/bin/emerge)
||
||  The problem is the ld.so library path.   Its tricky to get ld.so to load
||  runtime .so's from /hostAthlonImage and not from the chroot's /usr/lib
||
||  Of these solutions I think (1) is more promising but looks like I need to
||  check the emerge source to find the gotcha's.
||
||  It would be really useful if the fakeroot emerge facility mentioned by
||  drobbins on the gentoo frontpage was available.  (I can't find it. Anyone
||  know how to use this feature?)
||
||
||  - Arnold
||
||  "John Nilsson" <john@×××××××.nu> wrote in message
||  news:1041689680.27164.65.camel@××××××××××××××.nu...
||
||  > If I do it this way I would have to compile an entire bootstrap
||  > environment for the 486. Also I wouldn't get the benefits of having gcc
||  > optimized for the athlon.
||  > What I would like is to write a simple script to use when upgrading the
||  > server. Change the makefile and compile 486 optimized staticly linked
||  > binaries to packages that are later merged into the server.
||  >
||  > On Sat, 2003-01-04 at 14:52, Timo A. Hummel wrote:
||  > > I don't know if it's the correct list, but I did it as follows to
||  > > compile a pentium optimized system:
||  > >
||  > > I plugged in the 4GB hdd of my Pentium system, created the file
||  > > systems, setup a chroot environment and did the whole gentoo install
||  > > from there. worked like a charm, which was pretty good since I don't
||  > > have a keyboard on my Pentium system. It's pretty straightforward,
||  > > and shouldn't give any problems. Remember to set the make.conf
||  > > correctly.
||  > >
||  > > cheers,
||  > >  Timo
||  > >
||  > > On Sat, 2003-01-04 at 14:01, John Nilsson wrote:
||  > > > which is the correct mailing list for this kind of question?
||  > > >
||  > > > ___________________________________________________________________
||  > > >___
||  > > >
||  > > > From: John Nilsson <john@×××××××.nu>
||  > > > To: gentoo-admin@g.o
||  > > > Subject: [gentoo-admin] Building a second system
||  > > > Date: 04 Jan 2003 12:52:51 +0100
||  > > >
||  > > > I would like to use my current athlon-xp optimized system to
||  > > > compile a base system for a 486. How do I go about it?
||  > > > I suppose I would have to keep an 486 optimized copy of glibc
||
||  somewhere, how?
||
||  > > > It would be nice to have a more or less permanent setup so I can
||
||  upgrade
||
||  > > > packages easily later on.
||  > > >
||  > > > --
||  > > > gentoo-admin@g.o mailing list
||  > > >
||  > > >
||  > > >
||  > > >
||  > > > ___________________________________________________________________
||  > > >___
||  > > >
||  > > > --
||  > > > gentoo-dev@g.o mailing list
||  > >
||  > > --
||  > > Timo A. Hummel <timo.hummel@×××.net>
||  > >
||  > >
||  > > --
||  > > gentoo-dev@g.o mailing list
||  >
||  > --
||  > gentoo-dev@g.o mailing list
||
||  --
||  gentoo-dev@g.o mailing list

-- 
Bart Verwilst
Gentoo Linux Developer, Desktop Team
Gent, Belgium

--
gentoo-dev@g.o mailing list