Chuck,
Perhaps I can suggest that you work against 3.1.8. We're "About to
Release It(tm)" as 3.2.0, the next stable release. Also, send me your
sourceforge ID and i'll give you CVS access. Go ahead and do a checkout
of the development branch, and work from there, but don't check anything
yet. We should probably have you wait until after the 3.2.0 release.
See the attached document for details...
Cheers, -Brian
Thus spake Chuck Morrison ([EMAIL PROTECTED]):
> OK, let me qualify that subject line.
>
> I have recompled si 3.0.1 for x86_64 (opteron) and created an
> autoinstallcd iso image. it will boot but fails when attmpting to mount
> the ramdisk. Originally the ramdisk size in the kernel was 4mb. I then
> set it to 64mb and copied the new kernel to
> /usr/src/systemimager/boot/x86_64/standard/kernel , recreated the iso
> and tried again.
>
> This time I got a little more information when it hung. The last
> messages are as follows:
>
> RAMDISK: Compressed image found at block 0
> Attempt to read beyond end of device
> 01:00:rw=0 want 922337028264841220, limit=4096
> isof_read_super: bread failed, dev=01:00 iso_blknum=17, block=-2147483648
> read_super_block: can't find reiserfs filesystem on (dev 01:00, block
> 16, size 4096)
> --- last line is repeated ---
>
> The size it want's is way out of line, it appears. Do I have a corrupted
> initrd.img ? do I need to recreate it ? I hate to waste too many CDs
> guessing.
>
> Chuck Morrison
>
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Sisuite-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/sisuite-devel
>
--
---------------------------------------------------------
Brian Elliott Finley Argonne, MCS Division
Phone: 630.631.6621 http://thefinleys.com
gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52
---------------------------------------------------------
Hi! I'm a .signature virus! Copy me into your signature to help me spread!
#
# "SystemImager"
#
# Copyright (C) 1999-2001 Brian Elliott Finley <[EMAIL PROTECTED]>
# Copyright (C) 2002 Bald Guy Software <[EMAIL PROTECTED]>
#
# $Id: DEVELOPER_GUIDELINES,v 1.7 2002/08/11 03:56:42 brianfinley Exp $
#
--------------------------------------------------------------------------------
Developer Guidelines
--------------------------------------------------------------------------------
o Current development branch is tagged "HEAD". This is the default.
Most developers will use this. To check out the development branch,
see "CVS Checkout Steps for Developers for the Development Branch"
below.
o The stable branch is only to be used for fixing bugs. To check out
the stable branch see "CVS Checkout Steps for Developers for the
Stable Branch (bug fixes only)" below.
o Only Brian Finley will modify CVS tags of any kind, such as for versioning
releases or creating development branches.
o Always get approval from Brian Finley prior to adding any new files or
directories to CVS.
o Try to mimick the style of the code that you are working in. This will
significantly improve your chances of it being accepted.
o Include a usage statement with every function/subroutine, no matter how
simple and self-explanatory that function is. Example:
# Usage:
# my $partition_tool = which_partition_tool();
sub which_partition_tool {
[... code here ...]
}
o When you close a bug or feature request, add an appropriate line to the
CHANGE.LOG that includes the bug or feature number. Be sure to include
your initials. -BEF-
o Documentation: Developers may make changes to the documentation source, but
must contact Denise Walters for approval prior to making any structural
changes. Denise may be contacted at: <[EMAIL PROTECTED]>
o Always give people credit in the CREDITS file.
o Have fun!
--------------------------------------------------------------------------------
CVS Reference Material
--------------------------------------------------------------------------------
o http://www.loria.fr/~molli/cvs/doc/cvs_toc.html
or
o http://cvsbook.red-bean.com/cvsbook.html
or
o http://www.cvshome.org/
--------------------------------------------------------------------------------
CVS Checkout Steps for Developers
(You should be able to just copy and paste commands 2-5)
--------------------------------------------------------------------------------
1) Set your username:
MY_CVS_USERNAME=your_cvs_user_name
2) Tell cvs to operate over ssh:
CVS_RSH=ssh
3) Set BRANCH_OPTS to choose your branch.
For the development branch (HEAD), cut and paste this:
BRANCH="HEAD"; BRANCH_OPTS=""
For the current stable branch, cut and paste this:
BRANCH="stable-2_0_x"; BRANCH_OPTS="-r $BRANCH"
4) Checkout the code:
cvs -z3 -d:ext:[EMAIL PROTECTED]:/cvsroot/systemimager co $BRANCH_OPTS systemimager
5) Rename the checked out source tree:
mv systemimager systemimager.$BRANCH
--------------------------------------------------------------------------------
Versioning
--------------------------------------------------------------------------------
o SystemImager uses kernel style versioning (X.Y.Z):
o X = major architectural change
o Y = feature release
o an odd number indicates a development release (leading up to an even numbered
stable release)
o an even number indicates a stable release
o Z = bug fix release (no new features)
o Development releases may be made available unofficially.
o Examples from the current tree (as of 2002.08.10):
o stable-2_0_x, getting bug fixes only
o HEAD, will continue on as HEAD
o When ready for an official release as 3.0.0, release candidate packages
will be made. These will be named 3.0.0rc1, 3.0.0rc2, etc.
o When 3.0.0 is finally released, the code in HEAD will be tagged as
stable-3_0_x. Feature development will continue in HEAD, and bug fixes
to the 3.0.x release will be made in HEAD and 3.0.x. Bug fix releases
will be made from the stable-3_0_x branch.
