[gentoo-amd64] System died going from 2005.0 to 2005.1

[gentoo-amd64] System died going from 2005.0 to 2005.1

[scotthathcock]

My system has developed serious problems related to the emul libs. The
advice given as a reply to my bug has made the system impossible to
upgrade using emerge. It is possible the problem dates back to the
2004.3->2005.0 upgrade, I don't know. 

Is there a way to build a "from scratch" 2005.1 system over the net
without having to download and boot from a CD? Will it leave my user
directories alone? The installation docs assume that you don't have a
runnig gentoo system and start with a boot CD.

Thanks,
Scott
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] System died going from 2005.0 to 2005.1

[Mark Knecht]

On 10/8/05, scotthathcock@comcast.net <scotthathcock@comcast.net> wrote:
>
> My system has developed serious problems related to the emul libs. The
> advice given as a reply to my bug has made the system impossible to
> upgrade using emerge. It is possible the problem dates back to the
> 2004.3->2005.0 upgrade, I don't know.
>
> Is there a way to build a "from scratch" 2005.1 system over the net
> without having to download and boot from a CD?

Not that I know of...

> Will it leave my user
> directories alone?

The install will not use partitions that you don't tell it to use. If
your /home directory is a separate partition then it should be safe as
you do not have to mount it. If the /home directory is part of some
other partition then you should be careful.

> The installation docs assume that you don't have a
> runnig gentoo system and start with a boot CD.
>

Right, but you can modify this a bit by not creating new partitions
for /home and jsut reusing what's there, again, if you made home a
separate parrtition.

If you have room then you might also create a new partition, if you
have space, and then copy /home/USERS to it for safe keeping.

Basically, do backups before you start with a new install.

Good luck,
Mark

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] System died going from 2005.0 to 2005.1

[Michael Kjorling]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2005-10-08 16:20 -0600, scotthathcock@comcast.net wrote:
> Is there a way to build a "from scratch" 2005.1 system over the net
> without having to download and boot from a CD? Will it leave my user

How about `emerge --oneshot --ask --deep --empty-tree world'?

- -- 
Michael Kjörling, michael@kjorling.com - http://michael.kjorling.com/
* ASCII Ribbon Campaign: Against HTML Mail, Proprietary Attachments *
* ..... No bird soars too high if he soars with his own wings ..... *
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDSEvxdY+HSb3praYRAvPtAJ9YRG+YVbYzFUJY6h0rul3obqjGfQCfaHO4
2EFq9kJjv6OU8HQ6u+5B6Wo=
=ged+
-----END PGP SIGNATURE-----
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] System died going from 2005.0 to 2005.1

[Nuitari]

> My system has developed serious problems related to the emul libs. The
> advice given as a reply to my bug has made the system impossible to
> upgrade using emerge. It is possible the problem dates back to the
> 2004.3->2005.0 upgrade, I don't know.
>
> Is there a way to build a "from scratch" 2005.1 system over the net
> without having to download and boot from a CD? Will it leave my user
> directories alone? The installation docs assume that you don't have a
> runnig gentoo system and start with a boot CD.

I had to install a few Gentoo systems over the net from preexisting Red 
Hat installations.

The way I usually did was:
1. Backup any important data (including /home etc)
2. Remove the swap from the system (swapoff)
3. Change the swap partition from 82 to type 83 (Linux) with fdisk
4. Reboot (if necessary after the fdisk)
5. Format that partition to the file system you want
6. Install a stage3 into that partition
7. Chroot into it, do the basic things you need to get your system 
working. Update the stage3 to the latest version. Get at least the 
password changed. network configured, ssh etc

If downtime is bad and there is enough space, install apache and mysql, 
configure them etc.

As I had to keep downtime to a minimum I'll follow along that patg.

8. Add the old root into gentoo's fstab so that it mounts somewhere.
    Add another line so that the old system /home is mounted as the new /home
    Do the same with databases and any other directory (such as mail queue
     etc) that you need to provide service.

9. Leave the chroot
10. Modify your boot loader to start with the new partition, with maybe a
     fallback to the old one.

11. Reboot
12. Log into the (hopefully) new system.
13. If everything is ok, start deleting the old system's file from the
     partition, be careful not to delete the home and database files (or
     anything mount binded).
14. Create a new directory on the oldroot and change to it.
15. Move the new system files to the newroot, preserving everything (tar
     is good for that). Take care to exclude /proc and /sys from it, but do
     create the directories. Also you should exclude /tmp and recreate it
     properly.
17. Update the fstab for the new system.
16. Kill the services, umount anything that you did in 8.

17. Modify your boot loader to load the old parttion.
18. Reboot
19. Check that everything is ok / works
20. Redo the swap partition.

Everything should come back fine. Of course, YMMV. You need about 1.5gb to 
do it for a simple system.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] System died going from 2005.0 to 2005.1

[Nuitari]

>> Is there a way to build a "from scratch" 2005.1 system over the net
>> without having to download and boot from a CD? Will it leave my user
>
> How about `emerge --oneshot --ask --deep --empty-tree world'?

That would work to, try it before the long procedure I posted
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] System died going from 2005.0 to 2005.1

[Tres Melton]

On Sat, 2005-10-08 at 16:20 -0600, scotthathcock@comcast.net wrote:
> My system has developed serious problems related to the emul libs. The
> advice given as a reply to my bug has made the system impossible to
> upgrade using emerge. It is possible the problem dates back to the
> 2004.3->2005.0 upgrade, I don't know. 
> 
> Is there a way to build a "from scratch" 2005.1 system over the net
> without having to download and boot from a CD? Will it leave my user
> directories alone? The installation docs assume that you don't have a
> runnig gentoo system and start with a boot CD.

I wouldn't do this without a developer telling you it is going to work
but....

Get a bootable Linux CD and boot from it and unzip the portage snapshot
and stage tarball onto your system as the manual says.  Then sync,
bootstrap, and emerge -e world.  That should get you back to where you
are functional.  Just use the newest 2005.1 stage on the install.

> Thanks,
> Scott
-- 
Tres Melton
IRC & Gentoo: RiverRat

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: System died going from 2005.0 to 2005.1

[Francesco Talamona]

On Sunday 09 October 2005 00:20, scotthathcock@comcast.net wrote:
> My system has developed serious problems related to the emul libs.
> The advice given as a reply to my bug has made the system impossible
> to upgrade using emerge. It is possible the problem dates back to the
> 2004.3->2005.0 upgrade, I don't know.

I had a lot of problem upgrading from 2004.3, that made my system unable 
to compile toolchain properly.

I experienced any kind of misterous erorrs and rebuilt my system many 
times. In the end was a very very idiot error on my side. When it was 
removed the upgrade was really smooth and following one to 2005.1 was 
so even that I hardly noticed it...

Are you sure it don't wort a try? If you post any details maybe someone 
can help without rebuilding from scratch; and, believe me, it's much 
more instructive!

> Is there a way to build a "from scratch" 2005.1 system over the net
> without having to download and boot from a CD? Will it leave my user
> directories alone? The installation docs assume that you don't have a
> runnig gentoo system and start with a boot CD.

There are a lot of other possibilities...

In addition to other methods posted I would say you can do something 
useful (depending on your problem) even without repartition...
Unpack a stage 3 in a folder, mount $PORTDIR $PKGDIR $DISTDIR on it, 
update and then extract the packages tou need with quickpkg (if you set 
buildpkg FEATURES in /etc/make.conf, it's faster).

When I lastly decided to rebuild my system I again used a rather 
aggressive method:
make available two partition and rsync their contents. At this point 
mount the one to upgrade, save /etc and unpack a stage3 over it 
(overwrite files with same name), edit /etc files from saved one, 
edit /etc/fstab and lilo or to boot from it, chroot into the new 
partition and update lilo (lilo -v, I don't know what you have to do 
with grub...). It's quite a dirty way, but it is really fast (rsync 
just what is really needed)

Anyway I think the best thing to do is try here to debug you problem 
before restart from scratch.

HTH...
Ciao
	Francesco

-- 
Linux Version 2.6.12-gentoo-r9, Compiled #2 Wed Aug 24 18:43:16 CEST 
2005
One 2.2GHz AMD Athlon 64 Processor, 2GB RAM, 4325.37 Bogomips Total
aemaeth
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: System died going from 2005.0 to 2005.1

[Duncan]

Nuitari posted <Pine.LNX.4.63.0510081830160.22462@melchior.nuitari.net>,
excerpted below,  on Sat, 08 Oct 2005 18:47:20 -0400:

>> My system has developed serious problems related to the emul libs. The
>> advice given as a reply to my bug has made the system impossible to
>> upgrade using emerge. It is possible the problem dates back to the
>> 2004.3->2005.0 upgrade, I don't know.
>>
>> Is there a way to build a "from scratch" 2005.1 system over the net
>> without having to download and boot from a CD? Will it leave my user
>> directories alone? The installation docs assume that you don't have a
>> runnig gentoo system and start with a boot CD.
> 
> I had to install a few Gentoo systems over the net from preexisting Red 
> Hat installations.

As others have stated, there are likely other ways to do it (try emerge
--emptytree first, if that doesn't work, try Tres's suggestion, untarring
the stage tarball over your existing setup, then emerge --emptytree).

However, Nuitari's general method, installing from an existing system into
new partitions, while still being able to use the existing system while
you are doing it, works fine.  I used it myself, coming from Mandrake.

There is, however, an official document to help, proven to work as it has
been used by many, so you don't have to worry that Nuitari forgot a step
or something.  =8^)  It's called the "Alternative Installation Guide", and
is actually mentioned in the Gentoo Handbook, Part 1 (Installation),
Chapter 1 (About), under "What are my Options".

The direct link to the Alternatve Installation Guide is:

http://www.gentoo.org/doc/en/altinstall.xml .

You'll want Chapter 6, Installing Gentoo from an existing Linux
Distribution, direct link:

http://www.gentoo.org/doc/en/altinstall.xml#doc_chap6

Basically, that tells you how to use a chroot off of an existing
installation, describing how this method differs from the normal
installation method described in the handbook (thus, you still use the
handbook for most of the installation). During the first part of the
process, while you are still in the chroot, you can continue doing your
normal stuff in other sessions outside the chroot, which allows you to
take all the time you need getting the new installation up and running. 
You can actually stop working on the install and continue using your old
system for a couple weeks, if you get busy and don't have time to work on
it, because your old system continues to work as it did before you started
the new install.

As I said, it only details how this method differs from a normal install,
so you'll want the regular handbook install section available as well. 
Here's the general amd64 handbook link:

http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] System died going from 2005.0 to 2005.1

[Paul de Vrieze]

[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]

On Sunday 09 October 2005 05:03, Tres Melton wrote:
> On Sat, 2005-10-08 at 16:20 -0600, scotthathcock@comcast.net wrote:
> > My system has developed serious problems related to the emul libs. The
> > advice given as a reply to my bug has made the system impossible to
> > upgrade using emerge. It is possible the problem dates back to the
> > 2004.3->2005.0 upgrade, I don't know.
> >
> > Is there a way to build a "from scratch" 2005.1 system over the net
> > without having to download and boot from a CD? Will it leave my user
> > directories alone? The installation docs assume that you don't have a
> > runnig gentoo system and start with a boot CD.
>
> I wouldn't do this without a developer telling you it is going to work
> but....
>
> Get a bootable Linux CD and boot from it and unzip the portage snapshot
> and stage tarball onto your system as the manual says.  Then sync,
> bootstrap, and emerge -e world.  That should get you back to where you
> are functional.  Just use the newest 2005.1 stage on the install.

It should get you workable. But if you do this, you should backup your /etc 
directory above all. tar will hapilly overwrite whatever you put there, and 
you'd like to keep that. What I like to do is the following:

Create a directory somewhere on a partition with enough space. Unpack the 
stage3 tarball there. (or stage1 or 2 depending on preference). Chroot into 
the directory. Find the package that is causing the pain (likely gcc, glibc, 
binutils) create binary packages of those using "emerge --buildpkg". Then 
copy those binary packages to the normal location in your system (out of the 
chroot) and merge them (you can just point to the .tbz2 files even though 
portage warns you against it, as binary packages know their category). Then 
you've got a good chance to get your system working again. You could even do 
this with the whole system.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]