From jmills at vmware.com  Mon Oct 10 09:59:38 2005
From: jmills at vmware.com (Jason Mills)
Date: Sun May  4 12:26:17 2008
Subject: [tinysofa-devel] Fatal line in dispatch.py (TCS 2.0u2 --
	anaconda-9.1)
Message-ID: <65B5F504434AD3469DC12E5564E3794D17E66F@PA-EXCH02.vmware.com>

While setting up PXE + KickStart driven installs of TCS 2.0u2, I've run into
a rather annoying problem:

The change made to /usr/lib/anaconda/dispatch.py line 64 (commenting out the
line) conflicts with the contents of /usr/lib/anaconda/kickstart.py in that,
"installtype" is still marked as a dispatch skip-step no matter what
code-path is followed, causing Anaconda much unhappiness.


Was this inadvertent, or is it part of a larger plan?

At the moment, no KickStart installs succeed due to this mismatch. :-/

Unfortunately, because of where the problem originates, both the anaconda
binary, and the stage1 boot media need to be rebuilt.

Thoughts?

-J
From jh at tinysofa.org  Mon Oct 10 10:05:38 2005
From: jh at tinysofa.org (Jaakko Heinonen)
Date: Sun May  4 12:26:17 2008
Subject: [tinysofa-devel] Fatal line in dispatch.py (TCS 2.0u2
	--	anaconda-9.1)
In-Reply-To: <65B5F504434AD3469DC12E5564E3794D17E66F@PA-EXCH02.vmware.com>
References: <65B5F504434AD3469DC12E5564E3794D17E66F@PA-EXCH02.vmware.com>
Message-ID: <20051010150538.GA28541@ws.jh.dy.fi>

On 2005-10-10, Jason Mills wrote:
> While setting up PXE + KickStart driven installs of TCS 2.0u2, I've run into
> a rather annoying problem:
> 
> At the moment, no KickStart installs succeed due to this mismatch. :-/

It has been fixed in svn. You can get updated installation images from here:

	http://jh.dy.fi/~jaakko/images-2005-10-02.tar.bz2

It's hasn't been yet decided when updated images (isos) will be released
officially.

-- 
Jaakko

From jmills at vmware.com  Mon Oct 10 11:11:24 2005
From: jmills at vmware.com (Jason Mills)
Date: Sun May  4 12:26:17 2008
Subject: [tinysofa-devel] Fatal line in dispatch.py (TCS
	2.0u2--	anaconda-9.1)
Message-ID: <65B5F504434AD3469DC12E5564E3794D17E683@PA-EXCH02.vmware.com>

Jaakko-

*Awesome!* The replacement files in the tar.bz2 file worked like a champ!


How about just posting the tar.bz2 ball in the same directory structure as
the TCS 2.0u2 .iso images, etc... as a KickStart specific update, rather than
re-rolling the .isos?


For those playing the home game, the filestructures replaced are:

  /images/*
  /images/pxeboot/*
  /tinysofa/base/*

-J


> -----Original Message-----
> From: tinysofa-devel-bounces@tinysofa.org 
> [mailto:tinysofa-devel-bounces@tinysofa.org]
>   On Behalf Of Jaakko Heinonen
> Sent: Monday, October 10, 2005 8:06 AM
> 
> On 2005-10-10, Jason Mills wrote:
> > While setting up PXE + KickStart driven installs of
> > TCS 2.0u2, I've run into a rather annoying problem:
> > 
> > At the moment, no KickStart installs succeed due to
> > this mismatch. :-/
> 
> It has been fixed in svn. You can get updated installation 
> images from here:
> 
> 	http://jh.dy.fi/~jaakko/images-2005-10-02.tar.bz2
> 
> It's hasn't been yet decided when updated images (isos)
> will be released officially.
> 
> -- 
> Jaakko