[Sisuite-docs] Re: [Sisuite-users] Re: [SystemImager-discuss] Next Problem

[dann f. <da...@da...>]

i've added sisuite-docs to the cc list - doc discussion at the end.

On Wed, Jul 23, 2003 at 07:29:00AM -0700, Steve G wrote:
...
> I've reached an uneasy truce with systemimager. I've had to
> hack the install scripts because parted does not work for
> me. My server is an athlon system and the target machines
> are pentium based. Some how...some way, it pulls athlon
> libraries across the network. The pentium machines croak.

systemimager links the binaries it builds against libraries
reduced from your building system.  if your server has libaries
optimized for a specific subarch, then your boel won't run
on conflicting subarches.

i build releases on debian, where this shouldn't be a problem.

> So what I've done is create a bootable parted disk which
> runs the parted commands and then I use another disk to do
> the systemimager install. The next problem I run into is
> that systemimager does not setup grub on the boot
> partition. To get around this I use the following patch:

...

make sure you're running the latest systemconfigurator.
i know that the last couple releases have had plenty of grub
fixes.

>  *Documentation
>  1) no sample local.cfg. Book says its in /usr/share/doc.
>  Maybe the name in the book is wrong?

the install_docs rule wasn't installing it - i've fixed it
in my tree, so the debs will begin including it.  the spec
file will need to be updated too.

>  2) Subjects need better organization. 
>    2.a)Chapter 2 should cover installation. For some reason
>    chapter 3 starts off by covering installation again,
> even
>    though chapter 2 did this. Take the xtra words in 
>    chapter 3 & put it in chapter 2.

can you be more specific?  i see that chapter 3 refers to chapter 2
in the intro, but otherwise describes the imaging processes.

>    2.b) Chapter 3 would be better if its outline were this:
>      3.0 Checking out your system after installation - go
>      over rsync, dhcp, tcp_wrappers, firewall, etc.
>      3.1 Creating a golden image
>      3.2 creating an autoinstall boot disk
>      3.3 creating an autoinstall cd-rom
>      3.4 setting up a Pxe based install
>      3.5 loading an image onto target machine - this goes
>      over the steps to get it going for all 3 ways.
>      3.6 updating a golden image
>      3.7 client side initiated update
>      3.8 server side initiated update
>      3.9 removing or renaming images
>      3.10 Building your own image - its in faq, but should
>      be in the main documentation

right now, chapter 3 mostly consists of a step-by-step process,
assuming a linear progression through the steps.  switching
to a more "goal-oriented" (as bdale would say) set of steps,
which happen to be in a workable order, sounds like a better
way of organizing it, and looks like what you are suggesting,
at a high level.  currently, i think we are lacking a reference
quality.  Denise: what do you think?