Public SourceMage Discussion List

["Wyatt Draggoo" <wyatt AT draggoo.com>]

Hey folks,

I've run across a problem, and am not sure whether it's something we can
fix in SMGL, or something that should be fixed at the source (or something
I'm repeatedly doing wrong ;).

I've been playing around with different filesystems (reiserfs, xfs and
jfs); specifically, playing around with crashing and recovery.  The problem
I'm having is that these tools (don't remember about reiserfs, but if I
remember my notes xfs and js do) put their fsck binaries in /usr/sbin.  I
have /usr in a separate partition though, so when the system comes up in an
unclean state, it tries to fsck / but can't find the binary because /usr
isn't mounted yet.  But it won't mount /usr until it can fsck /.

Is there a reason these aren't in /sbin?  Is there anything we can do to
the spell to move them to /sbin so they are present when the system comes
up with only / mounted?

Thanks,
Wyatt

--
Wyatt Draggoo
>From wyatt AT draggoo.com  Wed Apr 16 17:34:32 2003
Return-Path: <wyatt AT draggoo.com>
Delivered-To: sm-discuss AT lists.ibiblio.org
Received: from c001.snv.cp.net (h001.c001.snv.cp.net [209.228.32.115])
        by happyhouse.metalab.unc.edu (Postfix) with SMTP id 81D7F20064
        for <sm-discuss AT lists.ibiblio.org>;
        Wed, 16 Apr 2003 17:34:32 -0400 (EDT)
Received: (cpmta 6179 invoked from network); 16 Apr 2003 14:34:29 -0700
Received: from 209.228.32.131 (HELO mail.draggoo.com.criticalpath.net)
        by smtp.register-admin.com (209.228.32.115) with SMTP;
        16 Apr 2003 14:34:29 -0700
X-Sent: 16 Apr 2003 21:34:29 GMT
Received: from [130.76.32.21] by mail.draggoo.com with HTTP;
    Wed, 16 Apr 2003 14:34:22 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
To: sm-discuss AT lists.ibiblio.org
From: "Wyatt Draggoo" <wyatt AT draggoo.com>
X-Sent-From: wyatt AT draggoo.com
Date: Wed, 16 Apr 2003 14:34:22 -0700 (PDT)
X-Mailer: Web Mail 5.3.0-6_sol28
Message-Id: 
<20030416143429.2483.h017.c001.wm AT mail.draggoo.com.criticalpath.net>
Subject: [SM-Discuss] [Cauldron] Install Ideas...
X-BeenThere: sm-discuss AT lists.ibiblio.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Public SourceMage Discussion List <sm-discuss.lists.ibiblio.org>
List-Unsubscribe: <http://lists.ibiblio.org/mailman/listinfo/sm-discuss>,
        <mailto:sm-discuss-request AT lists.ibiblio.org?subject=unsubscribe>
List-Archive: <https://lists.ibiblio.org/sympa/arc/sm-discuss>
List-Post: <mailto:sm-discuss AT lists.ibiblio.org>
List-Help: <mailto:sympa AT lists.ibiblio.org?subject=HELP>
List-Subscribe: <http://lists.ibiblio.org/mailman/listinfo/sm-discuss>,
        <mailto:sm-discuss-request AT lists.ibiblio.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2003 21:34:33 -0000

Howdy all,

I thought I'd toss out the ideas that Ryan and I had about Cauldron.  I was
going to head up that project, but a change in job positions has left me
with zero free time to work on anything.  I really hope this situation
changes, but for right now, there's not a lot I can do about it.

Some of these are related to each other, but I'm going to throw them out in
the order I can remember them.  Both my notes and my code are on a backup
tape that got lost during the same move that drive crashed on.  I guess
there is something to be said for offsite backups. :)

1) Order of the installation:

I had planned to do the install in two parts.  The first part would ask all
the configuration questions, and keep the answers in a config file.  The
second part would read that file and perform the install.  This was to set
up automated installs where cauldron would look for a config file at the
beginning of the install, and start the install after a timed prompt using
the provided config file.  By the same token, the install would look for a
.config file for the kernel and compile the kernel using that file if the
previous portion of the install had been automated.

The only thing that I hadn't taken the time to figure out yet was how to
specify disk partitioning in the config file.  I use Solaris here at work,
and had thought of something along the lines of how Jumpstart partitions
the disks, but hadn't decided on anything.

2) Networking first.

To go along with the first part, I wanted to set up networking as one of
the first install options.  This in turn paves the way for network installs
(think of an install from a floppy instead of a CD).  The install would
pull the basesystem down from the net and then continue the install
process, downloading all the sources for a compile using the normal SMGL
tools.

3) Local SMGL Server.

This has been brought up on the list in the past couple of days, but I
think it is very important to cauldron.  By being able to specify a local
SMGL server in the initial config file, you could even keep the majority of
the config options, the kernel .config file, a custom grimoire (think
companies who only want a specific set of spells on their systems), and the
source file for that grimoire on a local server.

This may be confusing because I hadn't named the files yet. :)  Let me see
if I can describe the files in a walkthrough of the full, automated network
install:

a) System boots from a floppy, and searches for an init.cnf file (making up
names now for clarity).  This file has the networking options, and
specifies SMGL server.

b) System loads the network modules, and sets up the network according to
the init.cnf file.

c) System downloads the base system, and hands control off to Cauldron.

d) Cauldron checks the SMGL server for the smgl.cnf file.  This is the file
with the rest of the install options, including partitioning, timezones,
etc.

e) Cauldron performs the install according to the smgl.cnf file.

f) Cauldron checks the server for a kernel config file.  If found, it
downloads this file and uses it to compil the kernel.  If not found, it
compiles the kernel with a default configuration.

g) Because the install is automated, a continuation init script is added
that will continue the install after a reboot.  Upon reboot, this script
will perform the scribe update and sorcery rebuild.

h) Lastly, cauldron checks for a spells.cnf file, which is a list of spells
to be cast.  These are cast on the fresh system.

Keep in mind that this is for the fully automated install, and that any of
this should be able to be overridden or done manually.  Boot from the
floppy and do a manual install from the network, for instance.

My goal was to be able to boot from a single floppy (or boot of the network
even, although I've never played with that) and be able to walk away and
come back in a few hours (or, in reality, the next morning :) to a fully
compiled, updated sorcery system with a known set of spells already cast.

Writing it all down in an email makes it seem quite complicated, but broken
down I don't think it's all that bad.  It's a boot floppy, two or three
config files either on the floppy or on a server, and a server with the
files shared out some way, be it ftp, http, nfs, etc.

This could even pave the way for fully tested installs set up directly on
sourcemage.org.  Have a spell list for a gaming system, a server system,
etc.  This is probably way off in the future, though... :)

Anyway, I thought I'd share my thoughts.  I think this would be a very
flexible system, and very powerful, both for individual users and for
businesses that need to roll out large install bases.

Wyatt

--
Wyatt Draggoo
>From charkins AT upl.cs.wisc.edu  Wed Apr 16 17:37:51 2003
Return-Path: <charkins AT upl.cs.wisc.edu>
Delivered-To: sm-discuss AT lists.ibiblio.org
Received: from enterprise.upl.cs.wisc.edu (enterprise.upl.cs.wisc.edu
        [128.105.45.69])
        by happyhouse.metalab.unc.edu (Postfix) with ESMTP id 6F19F20070
        for <sm-discuss AT lists.ibiblio.org>;
        Wed, 16 Apr 2003 17:37:51 -0400 (EDT)
Received: from data.upl.cs.wisc.edu (data.upl.cs.wisc.edu [128.105.45.42])
        by enterprise.upl.cs.wisc.edu (Postfix) with ESMTP
        id 28DDE27F76; Wed, 16 Apr 2003 16:37:51 -0500 (CDT)
Received: by data.upl.cs.wisc.edu (Postfix, from userid 26694)
        id CA07617AC5; Wed, 16 Apr 2003 16:37:50 -0500 (CDT)
Received: from localhost (localhost [127.0.0.1])
        by data.upl.cs.wisc.edu (Postfix) with ESMTP
        id B3E8F13C8F; Wed, 16 Apr 2003 16:37:50 -0500 (CDT)
Date: Wed, 16 Apr 2003 16:37:50 -0500 (CDT)
From: Casey Harkins <charkins AT upl.cs.wisc.edu>
To: Wyatt Draggoo <wyatt AT draggoo.com>
Subject: Re: [SM-Discuss] Disk tools in /usr/[s]bin...
In-Reply-To: 
<20030416135255.21111.h017.c001.wm AT mail.draggoo.com.criticalpath.net>
Message-ID: <Pine.LNX.4.44.0304161634280.25830-100000 AT data.upl.cs.wisc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: sm-discuss AT lists.ibiblio.org
X-BeenThere: sm-discuss AT lists.ibiblio.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Public SourceMage Discussion List <sm-discuss.lists.ibiblio.org>
List-Unsubscribe: <http://lists.ibiblio.org/mailman/listinfo/sm-discuss>,
        <mailto:sm-discuss-request AT lists.ibiblio.org?subject=unsubscribe>
List-Archive: <https://lists.ibiblio.org/sympa/arc/sm-discuss>
List-Post: <mailto:sm-discuss AT lists.ibiblio.org>
List-Help: <mailto:sympa AT lists.ibiblio.org?subject=HELP>
List-Subscribe: <http://lists.ibiblio.org/mailman/listinfo/sm-discuss>,
        <mailto:sm-discuss-request AT lists.ibiblio.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2003 21:37:51 -0000



On Wed, 16 Apr 2003, Wyatt Draggoo wrote:

> Is there a reason these aren't in /sbin?  Is there anything we can do to
> the spell to move them to /sbin so they are present when the system comes
> up with only / mounted?

I just cast xfsprogs to test. I thought just an sedit line would be needed
in BUILD to correct the install locations, however, they installed to
/sbin here without any modifications. Haven't test jfs yet. I'm using
devel sorcery, test grimoire.

root@zorak:~# gaze installed xfsprogs
2.3.6

root@zorak:~# gaze install xfsprogs | grep bin
/sbin
/sbin/fsck.xfs
/sbin/mkfs.xfs
/sbin/xfs_repair
/usr/sbin
/usr/sbin/xfs_admin
/usr/sbin/xfs_bmap
/usr/sbin/xfs_check
/usr/sbin/xfs_db
/usr/sbin/xfs_freeze
/usr/sbin/xfs_growfs
/usr/sbin/xfs_info
/usr/sbin/xfs_logprint
/usr/sbin/xfs_mkfile
/usr/sbin/xfs_ncheck
/usr/sbin/xfs_rtcp


-casey