systeminstaller-users — SystemInstaller user support list.

[Systeminstaller-users] error upon issueing make

[Plessinger, J. <Jos...@UH...>]

After downloading the  system installer  tar file  I  attempted to
install system installer and  received the following messages on  the
make command. Any thoughts would be helpful.

 

systeminstaller-1.04]# make

Makefile:1143: warning: overriding commands for target `manifest'

Makefile:754: warning: ignoring old commands for target `manifest'

cp bin/mksimachine blib/script/mksimachine

/usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)"
blib/script/mksimachine

cp bin/buildimage blib/script/buildimage

/usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)"
blib/script/buildimage

cp bin/mksidisk blib/script/mksidisk

/usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)"
blib/script/mksidisk

cp tksis/tksis blib/script/tksis

/usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)" blib/script/tksis

cp bin/mksiimage blib/script/mksiimage

/usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)"
blib/script/mksiimage

cp bin/mksirange blib/script/mksirange

/usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)"
blib/script/mksirange

cp bin/mkdhcpconf blib/script/mkdhcpconf

/usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)"
blib/script/mkdhcpconf

cp bin/mkpkgcache blib/script/mkpkgcache

/usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)"
blib/script/mkpkgcache

cp bin/simigratedb blib/script/simigratedb

/usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)"
blib/script/simigratedb

Unrecognized switch: --section  (-h will show valid options).

make: *** [manifypods] Error 29

[root@uhtrain101 systeminstaller-1.04]#



Visit us at www.UHhospitals.org.

The enclosed information is STRICTLY CONFIDENTIAL and is intended for the use of the addressee only. University Hospitals and its affiliates disclaim any responsibility for unauthorized disclosure of this information to anyone other than the addressee.

Federal and Ohio law protect patient medical information, including psychiatric_disorders, (H.I.V) test results, A.I.Ds-related conditions, alcohol, and/or drug_dependence or abuse disclosed in this email. Federal regulation (42 CFR Part 2) and Ohio Revised Code section 5122.31 and 3701.243 prohibit disclosure of this information without the specific written consent of the person to whom it pertains, or as otherwise permitted by law.

[Systeminstaller-users] A web interface for Syetm Imager

[<dam...@fr...>]

Hi,

I've written a web gui (php/mysql/perl) to manage my system imager server :

static dhcp : add ip address to mac address and reload dhcpd server,
system imager : configuration of different images and relation between hostname
to deploy and image
historic : an historic allow user to show which configuration affected to a
hostname.

every x minutes, a crontab take the informations written by user and configure
the server.

are you interested ?

many things must be added to this project but it looks like being veru user
friendly and very useful

zerotyler

[Systeminstaller-users] Compute Cluster Linux Distro

[David M. B. <da...@al...>]

Hi,
I'm a research assistant/programmer/system admin at Alexander Technology, a=
n=20
Australian tech startup with a close association with the Australian Nation=
al=20
University (ANU). Alexander Technology specialise in low-end High Performan=
ce=20
Computing (HPC) solutions, that is for budgets generally less than $100k.
In this market, the barriers to entry are relatively high. 90% of people wh=
o=20
need such systems do not have the know-how to build and configure them; the=
=20
overhead of selling small clusters with an IBM/HP/DELL business model is su=
ch=20
that they simply reject such requests.
Our mission is to help all the scientist who could benefit to do so.
One part of this mission is to develop a linux distro that targets this are=
a.=20
It would provide nice interfaces to configure, deploy and manage small=20
clusters.
System Installer is likely to be a core component of this project.
We are interested in collaborating with the SI-Suite projects.
Best regards,
David Michael Barr
=A0
Researcher
=A0
Alexander Technology
=A0
Tel: +61 (0)2 6125 5136
Mob: +61 (0)434 388 348
=46ax: +61 (0)2 6162 4023
http://www.alexandertechnology.com
da...@al...

Innovations Building
Australian National University ACT 0200
Australia

Re: [Systeminstaller-users] Problem creating INITRD on Debian Sarge 2.6.8 with SI 3.5.3

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

On Wed, 2005-11-09 at 16:42 +0000, Roger Lucas wrote:
> I don=FFt know if this makes sense, but perhaps someone can shed some
> light on it.
>=20
> =20
>=20
> I am running Debian Sarge 2.6.8 and have installed the 3.5.3 release
> of SystemInstaller along with SystemConfigurator 2.2.2.  I chose the
> latest 3.5.3 release as I needed LVM support.  I have run it
> successfully on one machine, but it took a VERY long time in
> =B4si_prepareclient=A1.  When I tried it on another machine,
> =B4si_prepareclient=A1 failed when building the initrd file.  The two
> machines seemed to do similar things when running =B4si_prepareclient=A1=
,
> but the unexpected behaviour was a whole load of modules being
> reloaded/restarted during the creation of initrd.  This took a long
> time on the first machine, but the script continued without error.  On
> the second machine, this caused a failure.
>=20
> =20
>=20
> When I looked through the code in
> =B4UseYourOwnKernel.pm:_create_new_initrd()=A1, there was a line:
>=20
>             run_cmd("find $staging_dir -depth -exec touch -t
> 196912311900 '{}' ';'");

You should probably contact the sisuite-users list.  Neither of the
files you mention are part of the systeminstaller package.

[Systeminstaller-users] Problem creating INITRD on Debian Sarge 2.6.8 with SI 3.5.3

[Roger L. <ro...@pl...>]

I don't know if this makes sense, but perhaps someone can shed some light on
it.

 

I am running Debian Sarge 2.6.8 and have installed the 3.5.3 release of
SystemInstaller along with SystemConfigurator 2.2.2.  I chose the latest
3.5.3 release as I needed LVM support.  I have run it successfully on one
machine, but it took a VERY long time in "si_prepareclient".  When I tried
it on another machine, "si_prepareclient" failed when building the initrd
file.  The two machines seemed to do similar things when running
"si_prepareclient", but the unexpected behaviour was a whole load of modules
being reloaded/restarted during the creation of initrd.  This took a long
time on the first machine, but the script continued without error.  On the
second machine, this caused a failure.

 

When I looked through the code in
"UseYourOwnKernel.pm:_create_new_initrd()", there was a line:

            run_cmd("find $staging_dir -depth -exec touch -t 196912311900
'{}' ';'");

 

It seemed to be this that was triggering the modules to be reloaded.  When I
commented out this line, the problem disappeared and the "si_prepareclient"
suddenly ran smoothly (and completed much more quickly).

 

I don't understand what is going on.  As far as I can tell, all that this
line does is change the date stamps on all the files in the staging
directory.

 

Any ideas ?

 

Thanks,

 

Roger

[Systeminstaller-users] TORQUE 2.0

[Amber W. <a_w...@ya...>]

Hi,

I would like to announce that TORQUE Resource Manager
2.0 was just released, and can be downloaded at
www.clusterresources.com/torque.  

TORQUE, which is built on OpenPBS is one of the most
widely used open source batch schedulers.  TORQUE's
improvements since the last patch include an improved
start up feature for quick startup of downed nodes,
enhanced internal diagnostics, simplified install, and
improved API reporting abilities.

TORQUE is a community project with contributions from
NCSA, OSC, USC, the U.S. Department of Energy, Sandia,
PNNL, University of Buffalo, TeraGrid and many other
leading edge HPC organizations.

We invite you to download and try TORQUE and visit our
user community www.clusterresources.com/torque.  We
welcome feedback and patch submissions.

Regards,

Amber 



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

[Systeminstaller-users] Re: Thanks for the help

[Nick I <clu...@gm...>]

 Hi.

Thanks to the response from many in the community I have added sections
about diskless clusters and information on 32-bit and 64-bit processors at
the site I help run,
www.ClusterBuilder.org.<http://www.clusterbuilder.org/>I also added a
section called Ask the Cluster Expert (
http://www.clusterbuilder.org/pages/ask-the-expert.php) for people to submi=
t
questions they have about cluster and grid computing. I post the questions
at an FAQ page (http://www.clusterbuilder.org/pages/ask-the-expert/faq.php)
and then research the answer as well as allow those knowledgeable in the
community to submit a response to the question. I want to build a valuable
knowledgebase of high performance computing information.

I need you to share your knowledge by adding to the question responses and
also submitting questions/answers to common problems you've experienced in
the past and are experiencing now.

A sample question could be about provisioning managers on clusters..

Thanks,
Nick

[Systeminstaller-users] pushing OS changes using systeminstaller - is it possible?

[stu w. <st...@em...>]

Here is our situation:

We have need of changing the OS on our servers quickly and remotely.  I 
have good images with systemimager of all our supported OSs and have had 
no luck yet getting any of the command line utilities provided with that 
suite to work as far as pushing a new OS goes. 

I downloaded and have installed systeminstaller, and when I bring up the 
tksis it does not see any of the images that we pulled with 
systemimager.  I've glanced through the readme and man pages, but see no 
way to let systeminstaller know that these images exist, much less a way 
to push them out.

Any help, suggestions or advice would be much appreciated.  I'm a newbie 
to both pieces of software and have very little time left to get this 
wonderful idea working.

Stu Wells

[Systeminstaller-users] Thanks for the help

[Nick I <clu...@gm...>]

Hi,

Thanks you everyone for submitting links about HPC related projects
and sites to Cluster Builder (http://www.clusterbuilder.org). Upon
suggestions sent by the HPC community, I added sections for Grid
middleware and end-user applications under the "Software" category.

I want to continue making Cluster Builder a helpful research tool for
HPC related information. So I'd like to know, based upon your
experience, if there are any other important components you run on
your cluster that I failed to note, or are there changes you would
make in how I listed the applications.

Please go ahead and respond to this email in the user list so that
others can give their opinions as well. Links that you mention in the
user list I will be sure to include on Cluster Builder.

Thanks for the help,
Nick

[Systeminstaller-users] Systeminstaller links

[Nick I <clu...@gm...>]

Hi,

I work on a Web site at www.clusterbuilder.org.  The site highlights a
broad spectrum of high performance computing related technologies.  It
has links to reviews, comparisons, pricing and other information
related to the many HPC solutions available. The site also allows for
you to complete one request-for-quote form and have multiple hardware
vendors of your choice provide pricing quotes to you.

We need knowledgeable cluster users to submit sites that have proved a
valuable resources to them.  One particular area that we want to make
sure is complete is provisioning managers, which SystemInstaller is
listed under. Please take a minute and submit additional links
associated with SystemInstaller, Provisioning Managers or other areas
that will benefit the HPC community. (To submit content for the site,
click on the Submit Content section on www.clusterbuilder.org).

Thank you for your help.

Nick

Re: [Systeminstaller-users] Do you have the linux kernel supporting bcm4400 of NIC!

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

On Thu, Nov 20, 2003 at 03:03:17AM -0800, jidong wrote:
>   I ask that in the OSCAR mail list,one kind people 
> said I need a kernel supporting a bcm4400 ,he also
> said the SI team will gave me a perfect answer.

they were probably correct.  the systemimager manual has a section
in the FAQ on how to add a driver.

[Systeminstaller-users] Do you have the linux kernel supporting bcm4400 of NIC!

[jidong <jid...@ya...>]

hello:
  Now I am using OSCAR kit to construct a cluster . I have 
12 homogenous nodes.I installed the RedHat9.0 in a node 
that will work as the server node(or master node) .The
node has a integrated NIC,and its type is bcm4400.The 
RedHat 9.0 doesn't support it,so I download a driver .
After I installed the driver of bcm4400,all is Ok.
  I started OSCAR install.In the step 6,when I installed the
client nodes,the client nodes cann't complete install.
  In the client nodes,the part useful message is as follows:
"
#ifconfig_loopback
#load_my_modules
#read_local_cfg
#checking for floppy diskette
#you may see some "wrong magic" errors here, and that is normal.
#no floppy diskette in drive
.........
.........
#starting_network
#IP address not set by local.cfg, I will use DHCP
 
#sleep0
 
#sending on LPF/lo/<null>
#sending on socket/fallback/fallback-net
#DHCP is cover on lo to 255.255.255.255 port 67 interval 7
#DHCP is cover on lo to 255.255.255.255 port 67 interval 17
#DHCP is cover on lo to 255.255.255.255 port 67 interval 17
#DHCP is cover on lo to 255.255.255.255 port 67 interval 19
 
#no DHCPoffers received
#no working lease inpersistent database sleeping
#I couldn't configure the network interface using DHCP.
#
"
  In the client shell,I input the command 'ifconfig',
only the 'lo', doesn't have 'eth0';
  I ask that in the OSCAR mail list,one kind people 
said I need a kernel supporting a bcm4400 ,he also
said the SI team will gave me a perfect answer.
  
  Thank you for answers!


---------------------------------
Do you Yahoo!?
Free Pop-Up Blocker - Get it now

[Systeminstaller-users] make test failed test 1

[Laurent C. <Lau...@ex...>]

Hi,

I got the following trace while running make test :

~/systeminstaller-1.01> make test
Makefile:1059: warning: overriding commands for target `manifest'
Makefile:726: warning: ignoring old commands for target `manifest'
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" 
"test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/commands.......# Test 1 got: '512' (t/commands.t at line 10)
#   Expected: '0'
t/commands.......FAILED test 1                                               
        Failed 1/2 tests, 50.00% okay
t/env............ok                                                          
t/image..........ok                                                          
t/package........ok                                                          
t/package_rpm....ok                                                          
t/partition......ok                                                          
Failed Test  Stat Wstat Total Fail  Failed  List of Failed
-------------------------------------------------------------------------------
t/commands.t                2    1  50.00%  1
Failed 1/6 test scripts, 83.33% okay. 1/18 subtests failed, 94.44% okay.
make: *** [test_dynamic] Error 29


-- 
Cluster HPC Team -- Linux IA-32/IA-64
Open Source R&D Dept.
Bull SA

[Systeminstaller-users] ask for help about oscar cluster

[ͯ¶Ë <ton...@ma...>]

hi,

   when install a oscar cluster, at the begining, everything seems to proceed
normally.I can watch the  network traffic come over from the  server  node to the
client nodes and  all the files appear to be installed.  However, when I  reboot
the client node, I get the following messages:  
<long list of unresolved  symbol  errors regarding mptscsi.o>
ERROR:/bin/insmod exited abnormally!
mounting   /proc filesystem 
Creating  root   device   
Mounting root filesystem
kmod:failed to exec /sbin/modprobe -s -k block-major-8, errno = 2
mount:  error 6
mounting  ext2 
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2     
Freeing unused  kernel memory: 384k freed  
Kernel panic: No init found. Try passing init=option to kernel.
 <the system hangs here>


  What'scurious to me about this is that the same SCSI controller
is in each of the machines,however the problem seems to  be that  the
drivers for the SCSI controller are never loaded  upon  reboot after network
installation.
  Thanks for all of your help.

                                                       

[Systeminstaller-users] Re: send me that again please fhyimnxsswza tex

[Julianne S. <7oo...@qu...>]

<html>
<head>
<title>Hy sweet</title>
</head>
<body>
<p><font face=3D"Arial">Hi Sylvia!<br>
Me and Lisa are back online with our new site!<br>
We put on all Lisa's nude shots!<br>
There's also a movie of me and Lisa nude on the street!<br>
Come and visit us, 
<a href=3D"http://www.geocities.com/e_omar_77/"><b>this is our site</b></a=
>.<br>
We hope to meet you again on Kerkira's nudist beach this year!<br>
We will be at Kerkira from August 1 to September 5.<br>
Don't forget to 
<a href=3D"http://www.geocities.com/f_omar_77/"><b>visit our website</b></=
a>!<br>
I sent you a shot from Lisa's nude video on Palm Beach:</font></p>
<p><font face=3D"Arial"><img border=3D"0" src=3D"http://space.virgilio.it/=
hos...@vi.../thumb.jpg"></font></p>
<p><font face=3D"Arial">See you soon!<br>
<br>
Darren &amp; Lisa.</font></p>
</body>
</html>cvajrxavcxnv 
vftzcfabyuyqssb oszabby y vi
h   l avihnv qf

jl
degwvkofbzg f

[Systeminstaller-users] Make Test Failure

[Mark B. <mar...@ni...>]

make test
Makefile:1067: warning: overriding commands for target `manifest'
Makefile:720: warning: ignoring old commands for target `manifest'
Skip blib/lib/SystemInstaller/Image/Kernel_ia64.pm (unchanged)
Skip blib/lib/SystemInstaller/Package/Deb.pm (unchanged)
Skip blib/lib/SIS/Image.pm (unchanged)
Skip blib/lib/SystemInstaller/Image/Kernel_iseries.pm (unchanged)
Skip blib/lib/SIS/Component.pm (unchanged)
Skip blib/lib/SystemInstaller/Package.pm (unchanged)
Skip blib/lib/SIS/Client.pm (unchanged)
Skip blib/lib/SystemInstaller/Tk/Main.pm (unchanged)
Skip blib/lib/SystemInstaller/PackageBest.pm (unchanged)
Skip blib/lib/SystemInstaller/Tk/Help.pm (unchanged)
Skip blib/lib/SystemInstaller/Passwd.pm (unchanged)
Skip blib/lib/SystemInstaller/Partition.pm (unchanged)
Skip blib/lib/Util/IP.pm (unchanged)
Skip blib/lib/SystemInstaller/Package/Rpm.pm (unchanged)
Skip blib/lib/SystemInstaller/Tk/Image.pm (unchanged)
Skip blib/lib/SystemInstaller/Package/RpmNoScripts.pm (unchanged)
Skip blib/lib/SystemInstaller/Tk/Common.pm (unchanged)
Skip blib/lib/SIS/Adapter.pm (unchanged)
Skip blib/lib/SIS/DB.pm (unchanged)
Skip blib/lib/SystemInstaller/PackageBest/Rpm.pm (unchanged)
Skip blib/lib/Tk/SISTree.pm (unchanged)
Skip blib/lib/SystemInstaller/Tk/VdiskPreinst.pm (unchanged)
Skip blib/lib/SystemInstaller/Image.pm (unchanged)
Skip blib/lib/SystemInstaller/Tk/GetImage.pm (unchanged)
Skip blib/lib/SystemInstaller/Package/Suse.pm (unchanged)
Skip blib/lib/SystemInstaller/Machine.pm (unchanged)
Skip blib/lib/SystemInstaller/Partition/IA.pm (unchanged)
Skip blib/lib/SystemInstaller/Tk/AddClients.pm (unchanged)
Skip blib/lib/SystemInstaller/Tk/UpdateClient.pm (unchanged)
Skip blib/lib/SystemInstaller/Env.pm (unchanged)
Skip blib/lib/SystemInstaller/Image/Kernel_x86.pm (unchanged)
Skip blib/lib/SystemInstaller/Env.pm.bak (unchanged)
Skip blib/lib/SystemInstaller/Log.pm (unchanged)
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/commands.......NOK 1# Test 1 got: '512' (t/commands.t at line 10)          
#   Expected: '0'
t/commands.......FAILED test 1                                               
        Failed 1/2 tests, 50.00% okay
t/env............ok                                                          
t/image..........ok                                                          
t/package........ok                                                          
t/package_rpm....ok                                                          
t/partition......ok                                                          
Failed Test  Stat Wstat Total Fail  Failed  List of Failed
-------------------------------------------------------------------------------
t/commands.t                2    1  50.00%  1
Failed 1/6 test scripts, 83.33% okay. 1/18 subtests failed, 94.44% okay.
make: *** [test_dynamic] Error 29

perl -V
Summary of my perl5 (revision 5.0 version 8 subversion 0) configuration:
  Platform:
    osname=linux, osvers=2.4.19-gentoo-r10, archname=i686-linux
    uname='linux swcals.dresser.com 2.4.19-gentoo-r10 #4 smp thu jan 2 03:56:05 cst 2003 i686 intel(r) pentium(r) iii cpu family 1133mhz genuineintel gnulinux '
    config_args='-des -Darchname=i686-linux -Dcc=gcc -Dprefix=/usr -Dvendorprefix=/usr -Dsiteprefix=/usr -Dlocincpth=  -Doptimize=-march=pentium3 -O3 -pipe -Duselargefiles -Dd_dosuid -Dd_semctl_semun -Dscriptdir=/usr/bin -Dman3ext=3pm -Dcf_by=Gentoo -Ud_csh -Di_gdbm -Di_db -Di_ndbm'
    hint=recommended, useposix=true, d_sigaction=define
    usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef
    useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
    use64bitint=undef use64bitall=undef uselongdouble=undef
    usemymalloc=n, bincompat5005=undef
  Compiler:
    cc='gcc', ccflags ='-DPERL5 -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
    optimize='-march=pentium3 -O3 -pipe',
    cppflags='-DPERL5 -DPERL5 -fno-strict-aliasing'
    ccversion='', gccversion='3.2.1 20021207 (Gentoo Linux 3.2.1-20021207)', gccosandvers=''
    intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
    d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
    ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
    alignbytes=4, prototype=define
  Linker and Libraries:
    ld='gcc', ldflags =' -L/usr/local/lib'
    libpth=/usr/local/lib /lib /usr/lib
    libs=-lnsl -lndbm -lgdbm -ldb -ldl -lm -lc -lcrypt -lutil
    perllibs=-lnsl -ldl -lm -lc -lcrypt -lutil
    libc=/lib/libc-2.3.1.so, so=so, useshrplib=false, libperl=libperl.a
    gnulibc_version='2.3.1'
  Dynamic Linking:
    dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic'
    cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib'


Characteristics of this binary (from libperl): 
  Compile-time options: USE_LARGE_FILES
  Built under linux
  Compiled at Feb 10 2003 12:51:41
  @INC:
    /usr/lib/perl5/5.8.0/i686-linux
    /usr/lib/perl5/5.8.0
    /usr/lib/perl5/site_perl/5.8.0/i686-linux
    /usr/lib/perl5/site_perl/5.8.0
    /usr/lib/perl5/site_perl/5.6.1
    /usr/lib/perl5/site_perl
    /usr/lib/perl5/vendor_perl/5.8.0/i686-linux
    /usr/lib/perl5/vendor_perl/5.8.0
    /usr/lib/perl5/vendor_perl
    .


-- 
"One of the best ways to get yourself a reputation as a dangerous citizen
these days is to go about repeating the very phrases which our founding
fathers used in the great struggle for independence." 
				-- Charles Austin Beard (1874-1948)

[Systeminstaller-users] GUILLERMINA Wants it now tfn sifz qhygronezvo

[Les W. <349...@ao...>]

<p>Curious sys...@li... ?? I think you are.........
<a href=3D"http://qata@80.235.78.213"></p>
<p><img src=3D"http://breath@www.adultrag.com/byot/tn4790/sierra.jpg=
?yard"> </a></p>
<br>
<br>
<br>
<br>SHHHHHHHHHHH!
<br>
<br>
<a href=3D"http://distortion@80.235.78.213/r.php">cease my involvement w=
ith this promotion</a></font></td>


o wubxk l 
tsmndzyvrhz oqkeg sggnm fa ubj
tca

Re: [Sisuite-devel] Re: [Systeminstaller-users] Does systeminstaller support.LVM and RAID

[Brian E. F. <br...@bg...>]

Thanks, Gerry.

I've put LVM on the list for post-3.2.  (3.2 is about to freeze.)

BTW, I agree about the number of lists.  Perhaps we'll do something
about that soon.

Regards,

-Brian



Thus spake grenoml (gr...@ya...):
> Mike,
>   Thanks for the reply.  As I mentioned in one of my other posts to one
> of the sis lists (BTW: too many lists!):
>   Thought I would ask again since December.  I would like to
> use SIS, but unless it has at least LVM support we can't.  If you don't
> have it yet, LVM can't be that hard to add to the kernel (although I
> believe it does require at least a 2.4 level kernel).  Talk to
> Heinz (The LVM Guy) over at Sistina (http://www.sistina.com).  LVM has
> been great. Absolutely zero problems.  With it you can forget about
> filesystem sizing.  You can add,delete,shrink,expand filesystems at
> will.  Got a webserver running out of space?  No problem just throw in
> another disk and add it to the existing volume - presto, instant space.
>    No changes to software or configs.  Did I say I really like LVM? :-)
> 
> Thanks,
> Gerry Reno
> 
> 
> --- Michael Chase-Salerno <mi...@ch...> wrote:
> > I don't think the SystemImager boot kernel supports LVM, so that work
> > would need to happen before SIS as a whole could support it. I'm
> > copying
> > this to sisuite-devel so someone there can correct me if I am
> > mistaken.
> > 
> > As to SW raid. I did look at this a while ago, and I think its
> > possible
> > to get it working with a carefully built disk table file, but I never
> > got more architected support going. Unlike LVM, SW raid is supported
> > by
> > SystemImager, so you can use it if you have a golden client or if you
> > can get a good autoinstallscript.conf file created.
> > 
> > Mike
> > 
> > On Sat, 2003-04-19 at 17:39, grenoml wrote:
> > > Does systeminstaller support Logical Volume Manager (LVM) and
> > software
> > > RAID?
> > > 
> > > Thanks,
> > > Gerry Reno
> > > 
> > > 
> > > __________________________________________________
> > > Do you Yahoo!?
> > > The New Yahoo! Search - Faster. Easier. Bingo
> > > http://search.yahoo.com
> > > 
> > > 
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > Systeminstaller-users mailing list
> > > Sys...@li...
> > > https://lists.sourceforge.net/lists/listinfo/systeminstaller-users
> > -- 
> > Michael Chase-Salerno           br...@us...
> > IBM Linux Systems Technology    Poughkeepsie, NY 
> > System Installation Suite       www.sisuite.org
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Systeminstaller-users mailing list
> > Sys...@li...
> > https://lists.sourceforge.net/lists/listinfo/systeminstaller-users
> 
> 
> __________________________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo
> http://search.yahoo.com
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Sisuite-devel mailing list
> Sis...@li...
> https://lists.sourceforge.net/lists/listinfo/sisuite-devel

-- 
---------------------------------------------------------
 Brian Elliott Finley                Phone: 630.803.8183
 GPG: 3FF8 D096 0E0C D3F3 29B7  6518 D20B 1931 10F8 EE52
---------------------------------------------------------

[Systeminstaller-users] Imaging problems

[Charles H. <cho...@hi...>]

First of all let me apologize I was not using systeminstaller to deploy
the image.  And thus this was the wrong group to deploy to.  I have
however figured out what my problem was.

I pulled the image off of a server with the kernel for an Athalon Chip
installed.

When I tried to deploy the image out onto another system I didn't take
into account the "specialized" kernel.  I was trying to use an Athalon
compiled kernel on a K6-2 300 and thus the kernel couldn't load and that
is what caused my chroot error.

Re: [Systeminstaller-users] Changing an install script to Deploy across two Drives

[Michael Chase-S. <mi...@ch...>]

Since you posted to the systeminstaller list, I assume you used one of
the systeminstaller tool (tksis, mksiimage, buildimage) to build this
image on the server. If so, the proper way to do what you are attempting
is to re-run the mksidisk command with a new disk table that describes
the partitions the way you want them. See the mksidisk man page for
details. After rerunning mksidisk, recreate the autoinstallscript and
you should be fine.

Mike
 
On Mon, 2003-05-12 at 19:55, Charles Holbrook wrote:
> I have gone in and edited three seperate files in an attempt to move
> /usr/local to a seperate drive, /dev/hdd1 to be exact.  The install
> seems to be partially sucessfull.  Autoinstall partitions both disks and
> starts copying all of the filesystem over.  However when it gets to the
> point of running
> chroot /a/ systemconfigurator --configsi --stdin <<EOF
> I get an illegal operation
> 
> The three files I edited were www4.image01a.master
> /etc/hosts --> /var/lib/systemimager/scripts/hosts
> /etc/systemimager/mounted_filesystems
> 
> The changes made to these three file systems were to allow /usr/local to
> be installed on a second drive (/dev/hdd1) All of the scripts worked
> fine but came up with the chroot error.
> 
> I changed all of the files I modified back to my original files (yes I
> actually made copies of those files before modifying them) and I am
> still getting the same error.  I have gone through the manual for
> systemimager and looked at the FAQ.  I have checked to make sure the
> image has the same version of both systemconfigurator and systemimager
> installed and both are the same.  None of the files within the image
> itself were modified.
> 
> And now for the long part.  Below are the original
> www4.image.01a.master, mounted_filesystems, and autoinstallscript.conf
> 
> #### BEGIN AUTOINSTALLSCRIPT.CONF ###
> <!--
>   This file contains partition information about the disks on your
> golden
>   client.  It is stored here in a generic format that is used by your
>   SystemImager server to create an autoinstall script for cloning this
>   system.
>   
>   You can change the information in this file to affect how your target
>   machines are installed.  See "man autoinstallscript.conf" for details.
> -->
> 
> <config>
>   <!--
>    This disk's output was brought to you by the partition tool "sfdisk".
>    And by the numbers 4 and 5 and the letter Q.
>   -->
>   <disk dev="/dev/hda" label_type="msdos" unit_of_measurement="MB">
>     <part  num="1"  size="2023"  p_type="primary"  p_name="-" 
> flags="boot" />
>     <part  num="2"  size="2997"  p_type="primary"  p_name="-"  flags="-"
> />
>     <part  num="3"  size="2573"  p_type="primary"  p_name="-"  flags="-"
> />
>     <part  num="4"  size="*"  p_type="extended"  p_name="-"  flags="lba"
> />
>     <part  num="5"  size="1051"  p_type="logical"  p_name="-"  flags="-"
> />
>     <part  num="6"  size="*"  p_type="logical"  p_name="-"  flags="-" />
>   </disk>
> 
>   <fsinfo  line="10" real_dev="/dev/hda1" mount_dev="LABEL=/" mp="/" 
> fs="ext3" options="defaults" dump="1" pass="1" />
>   <fsinfo  line="20" real_dev="none" mp="/dev/pts"  fs="devpts"
> options="gid=5,mode=620" dump="0" pass="0" />
>   <fsinfo  line="30" real_dev="none" mp="/proc"  fs="proc"
> options="defaults" dump="0" pass="0" />
>   <fsinfo  line="40" real_dev="none" mp="/dev/shm"  fs="tmpfs"
> options="defaults" dump="0" pass="0" />
>   <fsinfo  line="50" real_dev="/dev/hda2" mount_dev="LABEL=/tmp"
> mp="/tmp"  fs="ext3" options="defaults" dump="1" pass="2" />
>   <fsinfo  line="60" real_dev="/dev/hda6" mount_dev="LABEL=/usr/local"
> mp="/usr/local"  fs="ext3" options="defaults" dump="1" pass="2" />
>   <fsinfo  line="70" real_dev="/dev/hda3" mount_dev="LABEL=/var/lib"
> mp="/var/lib"  fs="ext3" options="defaults" dump="1" pass="2" />
>   <fsinfo  line="80" real_dev="/dev/hda5" mp="swap"  fs="swap"
> options="defaults" dump="0" pass="0" />
> </config>
> 
> ### END AUTOINSTALLSCRIPT.CONF
> 
> ### BEGIN MOUNTED_FILESYSTEMS
> 
> /dev/hda2 on / type ext3 (rw)
> none on /proc type proc (rw)
> usbdevfs on /proc/bus/usb type usbdevfs (rw)
> /dev/hda1 on /boot type ext3 (rw)
> none on /dev/pts type devpts (rw,gid=5,mode=620)
> none on /dev/shm type tmpfs (rw)
> /dev/hda6 on /usr/local type ext3 (rw)
> 
> 
> ### END MOUNTED_FILESYSTEMS
> 
> ### BEGIN WWW9.SH (www4.image.01a.master)
> 
> #!/bin/sh
> 
> #
> # "SystemImager"
> #
> #  Copyright (C) 1999-2001 Brian Elliott Finley
> <bri...@ba...>
> #  Copyright (C) 2002 Bald Guy Software
> <bri...@ba...>
> #
> # This master autoinstall script was created with SystemImager v3.0.1
> 
> VERSION=3.0.1
> 
> PATH=/sbin:/bin:/usr/bin:/usr/sbin:/tmp
> ARCH=`uname -m \
> | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e s/arm.*/arm/ -e
> s/sa110/arm/`
> 
> shellout() {
>   exec cat /etc/issue ; exit 1
> }
> 
> # Pull in variables left behind by the linuxrc script.
> # This information is passed from the linuxrc script on the autoinstall
> media 
> # via /tmp/variables.txt.  Apparently the shell we use in BOEL is not 
> # intelligent enough to take a "set -a" parameter.
> #
> . /tmp/variables.txt || shellout
> 
> [ -z $IMAGENAME ] && IMAGENAME=www4.image.01a
> [ -z $OVERRIDES ] && OVERRIDES="www4.image.01a"
> 
> ### BEGIN Check to be sure this not run from a working machine ###
> # Test for mounted SCSI or IDE disks
> mount | grep [hs]d[a-z][1-9] > /dev/null 2>&1
> [ $? -eq 0 ] &&  echo Sorry.  Must not run on a working machine... &&
> shellout
> 
> # Test for mounted software RAID devices
> mount | grep md[0-9] > /dev/null 2>&1
> [ $? -eq 0 ] &&  echo Sorry.  Must not run on a working machine... &&
> shellout
> 
> # Test for mounted hardware RAID disks
> mount | grep c[0-9]+d[0-9]+p > /dev/null 2>&1
> [ $? -eq 0 ] &&  echo Sorry.  Must not run on a working machine... &&
> shellout
> ### END Check to be sure this not run from a working machine ###
> 
> 
> ### BEGIN Stop RAID devices before partitioning begins ###
> # Q1) Why did they get started in the first place?  
> # A1) So we can pull a local.cfg file off a root mounted software RAID
> system.
> #     They may not be started on your system -- they would only be
> started if
> #     you did the stuff in Q3 below.
> #
> # Q2) Why didn't my local.cfg on my root mounted software RAID work for
> me 
> #     with the standard kernel flavour?
> # A2) The standard kernel flavour uses modules for the software RAID
> drivers --
> #     therefore, software RAID is not available at the point in the boot
> process
> #     where BOEL needs to read the local.cfg file.  They are only pulled
> over 
> #     when this script is run, which is, of course, only runnable if it
> was
> #     pulled over the network using the settings that you would have
> wanted it
> #     to get from the local.cfg file, which it couldn't.  Right?
> #
> # Q3) Whatever.  So how do I make it work with a local.cfg file on my
> root
> #     mounted software RAID?  
> # A3) Compile an autoinstall kernel with software RAID, and any other
> drivers 
> #     you might need built in (filesystem, SCSI drivers, etc.).
> #
> # Find running raid devices
> if [ -f /proc/mdstat ]; then
>   RAID_DEVICES=` cat /proc/mdstat | grep ^md | sed 's/ .*$//g' `
> 
>   # raidstop will not run unless a raidtab file exists
>   echo "" >> /etc/raidtab || shellout
> 
>   # turn dem pesky raid devices off!
>   for RAID_DEVICE in ${RAID_DEVICES}
>   do
>     DEV="/dev/${RAID_DEVICE}"
>     # we don't do a shellout here because, well I forgot why, but we
> don't.
>     echo "raidstop ${DEV}" && raidstop ${DEV}
>   done
> fi
> ### END Stop RAID devices before partitioning begins ###
> 
> 
> ### BEGIN partition /dev/hda ###
> echo "Partitioning /dev/hda..."
> echo "Old partition table for /dev/hda:"
> parted -s -- /dev/hda print
> 
> # Create disk label.  This ensures that all remnants of the old label,
> whatever
> # type it was, are removed and that we're starting with a clean label.
> echo "parted -s -- /dev/hda mklabel msdos || shellout"
> parted -s -- /dev/hda mklabel msdos || shellout
> 
> # Get the size of the destination disk so that we can make the
> partitions fit properly.
> DISK_SIZE=`parted -s /dev/hda print | grep 'Disk geometry for' | sed
> 's/^.*-//g' | sed 's/\..*$//' `
> [ -z $DISK_SIZE ] && shellout
> END_OF_LAST_PRIMARY=0
> 
> echo "Creating partition /dev/hda1."
> START_MB=$END_OF_LAST_PRIMARY
> END_MB=$(echo "scale=3; ($START_MB + 2023)" | bc)
> echo "parted -s -- /dev/hda mkpart primary ext2 $START_MB $END_MB ||
> shellout"
> parted -s -- /dev/hda mkpart primary ext2 $START_MB $END_MB || shellout
> END_OF_LAST_PRIMARY=$END_MB
> echo parted -s -- /dev/hda set 1 boot on || shellout
> parted -s -- /dev/hda set 1 boot on || shellout
> 
> echo "Creating partition /dev/hda2."
> START_MB=$END_OF_LAST_PRIMARY
> END_MB=$(echo "scale=3; ($START_MB + 2997)" | bc)
> echo "parted -s -- /dev/hda mkpart primary ext2 $START_MB $END_MB ||
> shellout"
> parted -s -- /dev/hda mkpart primary ext2 $START_MB $END_MB || shellout
> END_OF_LAST_PRIMARY=$END_MB
> 
> echo "Creating partition /dev/hda3."
> START_MB=$END_OF_LAST_PRIMARY
> END_MB=$(echo "scale=3; ($START_MB + 2573)" | bc)
> echo "parted -s -- /dev/hda mkpart primary ext2 $START_MB $END_MB ||
> shellout"
> parted -s -- /dev/hda mkpart primary ext2 $START_MB $END_MB || shellout
> END_OF_LAST_PRIMARY=$END_MB
> 
> echo "Creating partition /dev/hda4."
> START_MB=$END_OF_LAST_PRIMARY
> END_MB=$(( $DISK_SIZE - 0 ))
> echo "parted -s -- /dev/hda mkpart extended $START_MB $END_MB ||
> shellout"
> parted -s -- /dev/hda mkpart extended $START_MB $END_MB || shellout
> END_OF_LAST_PRIMARY=$END_MB
> END_OF_LAST_LOGICAL=$START_MB
> echo parted -s -- /dev/hda set 4 lba on || shellout
> parted -s -- /dev/hda set 4 lba on || shellout
> 
> echo "Creating partition /dev/hda5."
> START_MB=$END_OF_LAST_LOGICAL
> END_MB=$(echo "scale=3; ($START_MB + 1051)" | bc)
> echo "parted -s -- /dev/hda mkpart logical ext2 $START_MB $END_MB ||
> shellout"
> parted -s -- /dev/hda mkpart logical ext2 $START_MB $END_MB || shellout
> END_OF_LAST_LOGICAL=$END_MB
> 
> echo "Creating partition /dev/hda6."
> START_MB=$END_OF_LAST_LOGICAL
> END_MB=$(( $DISK_SIZE - 0 ))
> echo "parted -s -- /dev/hda mkpart logical ext2 $START_MB $END_MB ||
> shellout"
> parted -s -- /dev/hda mkpart logical ext2 $START_MB $END_MB || shellout
> END_OF_LAST_LOGICAL=$END_MB
> 
> echo "New partition table for /dev/hda:"
> echo "parted -s -- /dev/hda print"
> parted -s -- /dev/hda print
> ### END partition /dev/hda ###
> 
> 
> ### BEGIN swap and filesystem creation commands ###
> echo "Load additional filesystem drivers."
> modprobe reiserfs
> modprobe ext2
> modprobe ext3
> modprobe jfs
> modprobe xfs
> 
> echo "mke2fs -j /dev/hda1 || shellout"
> mke2fs -j /dev/hda1 || shellout
> echo "tune2fs -L / /dev/hda1"
> tune2fs -L / /dev/hda1
> echo "mkdir -p /a/ || shellout"
> mkdir -p /a/ || shellout
> echo "mount /dev/hda1 /a/ -t ext3 -o defaults || shellout"
> mount /dev/hda1 /a/ -t ext3 -o defaults || shellout
> 
> echo "mke2fs -j /dev/hda2 || shellout"
> mke2fs -j /dev/hda2 || shellout
> echo "tune2fs -L /tmp /dev/hda2"
> tune2fs -L /tmp /dev/hda2
> echo "mkdir -p /a/tmp || shellout"
> mkdir -p /a/tmp || shellout
> echo "mount /dev/hda2 /a/tmp -t ext3 -o defaults || shellout"
> mount /dev/hda2 /a/tmp -t ext3 -o defaults || shellout
> 
> echo "mke2fs -j /dev/hda6 || shellout"
> mke2fs -j /dev/hda6 || shellout
> echo "tune2fs -L /usr/local /dev/hda6"
> tune2fs -L /usr/local /dev/hda6
> echo "mkdir -p /a/usr/local || shellout"
> mkdir -p /a/usr/local || shellout
> echo "mount /dev/hda6 /a/usr/local -t ext3 -o defaults || shellout"
> mount /dev/hda6 /a/usr/local -t ext3 -o defaults || shellout
> 
> echo "mke2fs -j /dev/hda3 || shellout"
> mke2fs -j /dev/hda3 || shellout
> echo "tune2fs -L /var/lib /dev/hda3"
> tune2fs -L /var/lib /dev/hda3
> echo "mkdir -p /a/var/lib || shellout"
> mkdir -p /a/var/lib || shellout
> echo "mount /dev/hda3 /a/var/lib -t ext3 -o defaults || shellout"
> mount /dev/hda3 /a/var/lib -t ext3 -o defaults || shellout
> 
> echo "mkswap -v1 /dev/hda5 || shellout"
> mkswap -v1 /dev/hda5 || shellout
> echo "swapon /dev/hda5 || shellout"
> swapon /dev/hda5 || shellout
> 
> ### END swap and filesystem creation commands ###
> 
> 
> ### BEGIN mount proc in image for tools like System Configurator ###
> echo "mkdir -p /a/proc || shellout"
> mkdir -p /a/proc || shellout
> echo "mount proc /a/proc -t proc -o defaults || shellout"
> mount proc /a/proc -t proc -o defaults || shellout
> ### END mount proc in image for tools like System Configurator ###
> 
> 
> # Filler up!
> rsync -av --exclude=lost+found/ --numeric-ids $IMAGESERVER::$IMAGENAME/
> /a/ || shellout
> 
> # Leave notice of which image is installed on the client
> echo $IMAGENAME > /a/etc/systemimager/IMAGE_LAST_SYNCED_TO || shellout
> 
> 
> ### BEGIN generate new fstab file from autoinstallscript.conf ###
> cat <<'EOF' > /a/etc/fstab
> LABEL=/	/	ext3	defaults	1	1
> none	/dev/pts	devpts	gid=5,mode=620	0	0
> none	/proc	proc	defaults	0	0
> none	/dev/shm	tmpfs	defaults	0	0
> LABEL=/tmp	/tmp	ext3	defaults	1	2
> LABEL=/usr/local	/usr/local	ext3	defaults	1	2
> LABEL=/var/lib	/var/lib	ext3	defaults	1	2
> /dev/hda5	swap	swap	defaults	0	0
> EOF
> ### END generate new fstab file from autoinstallscript.conf ###
> 
> 
> ### BEGIN overrides ###
> for OVERRIDE in $OVERRIDES
> do
>     rsync -av --numeric-ids $IMAGESERVER::overrides/$OVERRIDE/ /a/ ||
> echo "Override directory $OVERRIDE doesn't seem to exist, but that may
> be OK."
> done
> ### END overrides ###
> 
> 
> ##################################################################
> #
> # Uncomment the line below to leave your hostname blank.
> # Certain distributions use this as an indication to take on the
> # hostname provided by a DHCP server.  The default is to have
> # SystemConfigurator assign your clients the hostname that
> # corresponds to the IP address the use during the install.
> # (If you used to use static_dhcp, is your man.)
> #
> #HOSTNAME=""
> 
> 
> ### BEGIN systemconfigurator ###
> # Configure the client's hardware, network interface, and boot loader.
> echo "Iamhavingproblems"
> chroot /a/ systemconfigurator --verbose --debug --configsi --stdin <<EOL
> || shellout
> 
> [NETWORK]
> HOSTNAME = $HOSTNAME
> DOMAINNAME = $DOMAINNAME
> 
> [INTERFACE0]
> DEVICE = eth0
> TYPE = dhcp
> EOL
> ### END systemconfigurator ###
> 
> 
> ### BEGIN Unmount filesystems ###
> echo "umount /a/var/lib || shellout"
> umount /a/var/lib || shellout
> 
> echo "umount /a/usr/local || shellout"
> umount /a/usr/local || shellout
> 
> echo "umount /a/tmp || shellout"
> umount /a/tmp || shellout
> 
> echo "umount /a/proc || shellout"
> umount /a/proc || shellout
> 
> echo "umount /a/ || shellout"
> umount /a/ || shellout
> 
> ### END Unmount filesystems ###
> 
> 
> # Tell the image server we're done.
> rsync $IMAGESERVER::scripts/imaging_complete > /dev/null 2>&1
> 
> # Take network interface down
> ifconfig eth0 down || shellout
> 
> # Cause the system to make noise and display an "I'm done." message
> ralph="sick"
> count="1"
> while [ $ralph="sick" ]
> do
>     echo -n -e "\\a"
>     [ $count -lt 60 ] && echo "I've been done for $count seconds. 
> Reboot me already!"
>     [ $(($count / 60 * 60)) = $count ] && echo "I've been done for
> $(($count / 60)) minutes now.  Reboot me already!"
>     sleep 1
>     count=$(($count + 1))
> done
> 
> 
> ### END WWW9.SH (www4.image.01a.master)
> 
> 
> 
> 
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
> 
> _______________________________________________
> Systeminstaller-users mailing list
> Sys...@li...
> https://lists.sourceforge.net/lists/listinfo/systeminstaller-users
-- 
Michael Chase-Salerno           br...@us...
IBM Linux Systems Technology    Poughkeepsie, NY 
System Installation Suite       www.sisuite.org

[Systeminstaller-users] Changing an install script to Deploy across two Drives

[Charles H. <cho...@hi...>]

I have gone in and edited three seperate files in an attempt to move
/usr/local to a seperate drive, /dev/hdd1 to be exact.  The install
seems to be partially sucessfull.  Autoinstall partitions both disks and
starts copying all of the filesystem over.  However when it gets to the
point of running
chroot /a/ systemconfigurator --configsi --stdin <<EOF
I get an illegal operation

The three files I edited were www4.image01a.master
/etc/hosts --> /var/lib/systemimager/scripts/hosts
/etc/systemimager/mounted_filesystems

The changes made to these three file systems were to allow /usr/local to
be installed on a second drive (/dev/hdd1) All of the scripts worked
fine but came up with the chroot error.

I changed all of the files I modified back to my original files (yes I
actually made copies of those files before modifying them) and I am
still getting the same error.  I have gone through the manual for
systemimager and looked at the FAQ.  I have checked to make sure the
image has the same version of both systemconfigurator and systemimager
installed and both are the same.  None of the files within the image
itself were modified.

And now for the long part.  Below are the original
www4.image.01a.master, mounted_filesystems, and autoinstallscript.conf

#### BEGIN AUTOINSTALLSCRIPT.CONF ###
<!--
  This file contains partition information about the disks on your
golden
  client.  It is stored here in a generic format that is used by your
  SystemImager server to create an autoinstall script for cloning this
  system.
  
  You can change the information in this file to affect how your target
  machines are installed.  See "man autoinstallscript.conf" for details.
-->

<config>
  <!--
   This disk's output was brought to you by the partition tool "sfdisk".
   And by the numbers 4 and 5 and the letter Q.
  -->
  <disk dev="/dev/hda" label_type="msdos" unit_of_measurement="MB">
    <part  num="1"  size="2023"  p_type="primary"  p_name="-" 
flags="boot" />
    <part  num="2"  size="2997"  p_type="primary"  p_name="-"  flags="-"
/>
    <part  num="3"  size="2573"  p_type="primary"  p_name="-"  flags="-"
/>
    <part  num="4"  size="*"  p_type="extended"  p_name="-"  flags="lba"
/>
    <part  num="5"  size="1051"  p_type="logical"  p_name="-"  flags="-"
/>
    <part  num="6"  size="*"  p_type="logical"  p_name="-"  flags="-" />
  </disk>

  <fsinfo  line="10" real_dev="/dev/hda1" mount_dev="LABEL=/" mp="/" 
fs="ext3" options="defaults" dump="1" pass="1" />
  <fsinfo  line="20" real_dev="none" mp="/dev/pts"  fs="devpts"
options="gid=5,mode=620" dump="0" pass="0" />
  <fsinfo  line="30" real_dev="none" mp="/proc"  fs="proc"
options="defaults" dump="0" pass="0" />
  <fsinfo  line="40" real_dev="none" mp="/dev/shm"  fs="tmpfs"
options="defaults" dump="0" pass="0" />
  <fsinfo  line="50" real_dev="/dev/hda2" mount_dev="LABEL=/tmp"
mp="/tmp"  fs="ext3" options="defaults" dump="1" pass="2" />
  <fsinfo  line="60" real_dev="/dev/hda6" mount_dev="LABEL=/usr/local"
mp="/usr/local"  fs="ext3" options="defaults" dump="1" pass="2" />
  <fsinfo  line="70" real_dev="/dev/hda3" mount_dev="LABEL=/var/lib"
mp="/var/lib"  fs="ext3" options="defaults" dump="1" pass="2" />
  <fsinfo  line="80" real_dev="/dev/hda5" mp="swap"  fs="swap"
options="defaults" dump="0" pass="0" />
</config>

### END AUTOINSTALLSCRIPT.CONF

### BEGIN MOUNTED_FILESYSTEMS

/dev/hda2 on / type ext3 (rw)
none on /proc type proc (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
/dev/hda1 on /boot type ext3 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)
/dev/hda6 on /usr/local type ext3 (rw)


### END MOUNTED_FILESYSTEMS

### BEGIN WWW9.SH (www4.image.01a.master)

#!/bin/sh

#
# "SystemImager"
#
#  Copyright (C) 1999-2001 Brian Elliott Finley
<bri...@ba...>
#  Copyright (C) 2002 Bald Guy Software
<bri...@ba...>
#
# This master autoinstall script was created with SystemImager v3.0.1

VERSION=3.0.1

PATH=/sbin:/bin:/usr/bin:/usr/sbin:/tmp
ARCH=`uname -m \
| sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e s/arm.*/arm/ -e
s/sa110/arm/`

shellout() {
  exec cat /etc/issue ; exit 1
}

# Pull in variables left behind by the linuxrc script.
# This information is passed from the linuxrc script on the autoinstall
media 
# via /tmp/variables.txt.  Apparently the shell we use in BOEL is not 
# intelligent enough to take a "set -a" parameter.
#
. /tmp/variables.txt || shellout

[ -z $IMAGENAME ] && IMAGENAME=www4.image.01a
[ -z $OVERRIDES ] && OVERRIDES="www4.image.01a"

### BEGIN Check to be sure this not run from a working machine ###
# Test for mounted SCSI or IDE disks
mount | grep [hs]d[a-z][1-9] > /dev/null 2>&1
[ $? -eq 0 ] &&  echo Sorry.  Must not run on a working machine... &&
shellout

# Test for mounted software RAID devices
mount | grep md[0-9] > /dev/null 2>&1
[ $? -eq 0 ] &&  echo Sorry.  Must not run on a working machine... &&
shellout

# Test for mounted hardware RAID disks
mount | grep c[0-9]+d[0-9]+p > /dev/null 2>&1
[ $? -eq 0 ] &&  echo Sorry.  Must not run on a working machine... &&
shellout
### END Check to be sure this not run from a working machine ###


### BEGIN Stop RAID devices before partitioning begins ###
# Q1) Why did they get started in the first place?  
# A1) So we can pull a local.cfg file off a root mounted software RAID
system.
#     They may not be started on your system -- they would only be
started if
#     you did the stuff in Q3 below.
#
# Q2) Why didn't my local.cfg on my root mounted software RAID work for
me 
#     with the standard kernel flavour?
# A2) The standard kernel flavour uses modules for the software RAID
drivers --
#     therefore, software RAID is not available at the point in the boot
process
#     where BOEL needs to read the local.cfg file.  They are only pulled
over 
#     when this script is run, which is, of course, only runnable if it
was
#     pulled over the network using the settings that you would have
wanted it
#     to get from the local.cfg file, which it couldn't.  Right?
#
# Q3) Whatever.  So how do I make it work with a local.cfg file on my
root
#     mounted software RAID?  
# A3) Compile an autoinstall kernel with software RAID, and any other
drivers 
#     you might need built in (filesystem, SCSI drivers, etc.).
#
# Find running raid devices
if [ -f /proc/mdstat ]; then
  RAID_DEVICES=` cat /proc/mdstat | grep ^md | sed 's/ .*$//g' `

  # raidstop will not run unless a raidtab file exists
  echo "" >> /etc/raidtab || shellout

  # turn dem pesky raid devices off!
  for RAID_DEVICE in ${RAID_DEVICES}
  do
    DEV="/dev/${RAID_DEVICE}"
    # we don't do a shellout here because, well I forgot why, but we
don't.
    echo "raidstop ${DEV}" && raidstop ${DEV}
  done
fi
### END Stop RAID devices before partitioning begins ###


### BEGIN partition /dev/hda ###
echo "Partitioning /dev/hda..."
echo "Old partition table for /dev/hda:"
parted -s -- /dev/hda print

# Create disk label.  This ensures that all remnants of the old label,
whatever
# type it was, are removed and that we're starting with a clean label.
echo "parted -s -- /dev/hda mklabel msdos || shellout"
parted -s -- /dev/hda mklabel msdos || shellout

# Get the size of the destination disk so that we can make the
partitions fit properly.
DISK_SIZE=`parted -s /dev/hda print | grep 'Disk geometry for' | sed
's/^.*-//g' | sed 's/\..*$//' `
[ -z $DISK_SIZE ] && shellout
END_OF_LAST_PRIMARY=0

echo "Creating partition /dev/hda1."
START_MB=$END_OF_LAST_PRIMARY
END_MB=$(echo "scale=3; ($START_MB + 2023)" | bc)
echo "parted -s -- /dev/hda mkpart primary ext2 $START_MB $END_MB ||
shellout"
parted -s -- /dev/hda mkpart primary ext2 $START_MB $END_MB || shellout
END_OF_LAST_PRIMARY=$END_MB
echo parted -s -- /dev/hda set 1 boot on || shellout
parted -s -- /dev/hda set 1 boot on || shellout

echo "Creating partition /dev/hda2."
START_MB=$END_OF_LAST_PRIMARY
END_MB=$(echo "scale=3; ($START_MB + 2997)" | bc)
echo "parted -s -- /dev/hda mkpart primary ext2 $START_MB $END_MB ||
shellout"
parted -s -- /dev/hda mkpart primary ext2 $START_MB $END_MB || shellout
END_OF_LAST_PRIMARY=$END_MB

echo "Creating partition /dev/hda3."
START_MB=$END_OF_LAST_PRIMARY
END_MB=$(echo "scale=3; ($START_MB + 2573)" | bc)
echo "parted -s -- /dev/hda mkpart primary ext2 $START_MB $END_MB ||
shellout"
parted -s -- /dev/hda mkpart primary ext2 $START_MB $END_MB || shellout
END_OF_LAST_PRIMARY=$END_MB

echo "Creating partition /dev/hda4."
START_MB=$END_OF_LAST_PRIMARY
END_MB=$(( $DISK_SIZE - 0 ))
echo "parted -s -- /dev/hda mkpart extended $START_MB $END_MB ||
shellout"
parted -s -- /dev/hda mkpart extended $START_MB $END_MB || shellout
END_OF_LAST_PRIMARY=$END_MB
END_OF_LAST_LOGICAL=$START_MB
echo parted -s -- /dev/hda set 4 lba on || shellout
parted -s -- /dev/hda set 4 lba on || shellout

echo "Creating partition /dev/hda5."
START_MB=$END_OF_LAST_LOGICAL
END_MB=$(echo "scale=3; ($START_MB + 1051)" | bc)
echo "parted -s -- /dev/hda mkpart logical ext2 $START_MB $END_MB ||
shellout"
parted -s -- /dev/hda mkpart logical ext2 $START_MB $END_MB || shellout
END_OF_LAST_LOGICAL=$END_MB

echo "Creating partition /dev/hda6."
START_MB=$END_OF_LAST_LOGICAL
END_MB=$(( $DISK_SIZE - 0 ))
echo "parted -s -- /dev/hda mkpart logical ext2 $START_MB $END_MB ||
shellout"
parted -s -- /dev/hda mkpart logical ext2 $START_MB $END_MB || shellout
END_OF_LAST_LOGICAL=$END_MB

echo "New partition table for /dev/hda:"
echo "parted -s -- /dev/hda print"
parted -s -- /dev/hda print
### END partition /dev/hda ###


### BEGIN swap and filesystem creation commands ###
echo "Load additional filesystem drivers."
modprobe reiserfs
modprobe ext2
modprobe ext3
modprobe jfs
modprobe xfs

echo "mke2fs -j /dev/hda1 || shellout"
mke2fs -j /dev/hda1 || shellout
echo "tune2fs -L / /dev/hda1"
tune2fs -L / /dev/hda1
echo "mkdir -p /a/ || shellout"
mkdir -p /a/ || shellout
echo "mount /dev/hda1 /a/ -t ext3 -o defaults || shellout"
mount /dev/hda1 /a/ -t ext3 -o defaults || shellout

echo "mke2fs -j /dev/hda2 || shellout"
mke2fs -j /dev/hda2 || shellout
echo "tune2fs -L /tmp /dev/hda2"
tune2fs -L /tmp /dev/hda2
echo "mkdir -p /a/tmp || shellout"
mkdir -p /a/tmp || shellout
echo "mount /dev/hda2 /a/tmp -t ext3 -o defaults || shellout"
mount /dev/hda2 /a/tmp -t ext3 -o defaults || shellout

echo "mke2fs -j /dev/hda6 || shellout"
mke2fs -j /dev/hda6 || shellout
echo "tune2fs -L /usr/local /dev/hda6"
tune2fs -L /usr/local /dev/hda6
echo "mkdir -p /a/usr/local || shellout"
mkdir -p /a/usr/local || shellout
echo "mount /dev/hda6 /a/usr/local -t ext3 -o defaults || shellout"
mount /dev/hda6 /a/usr/local -t ext3 -o defaults || shellout

echo "mke2fs -j /dev/hda3 || shellout"
mke2fs -j /dev/hda3 || shellout
echo "tune2fs -L /var/lib /dev/hda3"
tune2fs -L /var/lib /dev/hda3
echo "mkdir -p /a/var/lib || shellout"
mkdir -p /a/var/lib || shellout
echo "mount /dev/hda3 /a/var/lib -t ext3 -o defaults || shellout"
mount /dev/hda3 /a/var/lib -t ext3 -o defaults || shellout

echo "mkswap -v1 /dev/hda5 || shellout"
mkswap -v1 /dev/hda5 || shellout
echo "swapon /dev/hda5 || shellout"
swapon /dev/hda5 || shellout

### END swap and filesystem creation commands ###


### BEGIN mount proc in image for tools like System Configurator ###
echo "mkdir -p /a/proc || shellout"
mkdir -p /a/proc || shellout
echo "mount proc /a/proc -t proc -o defaults || shellout"
mount proc /a/proc -t proc -o defaults || shellout
### END mount proc in image for tools like System Configurator ###


# Filler up!
rsync -av --exclude=lost+found/ --numeric-ids $IMAGESERVER::$IMAGENAME/
/a/ || shellout

# Leave notice of which image is installed on the client
echo $IMAGENAME > /a/etc/systemimager/IMAGE_LAST_SYNCED_TO || shellout


### BEGIN generate new fstab file from autoinstallscript.conf ###
cat <<'EOF' > /a/etc/fstab
LABEL=/	/	ext3	defaults	1	1
none	/dev/pts	devpts	gid=5,mode=620	0	0
none	/proc	proc	defaults	0	0
none	/dev/shm	tmpfs	defaults	0	0
LABEL=/tmp	/tmp	ext3	defaults	1	2
LABEL=/usr/local	/usr/local	ext3	defaults	1	2
LABEL=/var/lib	/var/lib	ext3	defaults	1	2
/dev/hda5	swap	swap	defaults	0	0
EOF
### END generate new fstab file from autoinstallscript.conf ###


### BEGIN overrides ###
for OVERRIDE in $OVERRIDES
do
    rsync -av --numeric-ids $IMAGESERVER::overrides/$OVERRIDE/ /a/ ||
echo "Override directory $OVERRIDE doesn't seem to exist, but that may
be OK."
done
### END overrides ###


##################################################################
#
# Uncomment the line below to leave your hostname blank.
# Certain distributions use this as an indication to take on the
# hostname provided by a DHCP server.  The default is to have
# SystemConfigurator assign your clients the hostname that
# corresponds to the IP address the use during the install.
# (If you used to use static_dhcp, is your man.)
#
#HOSTNAME=""


### BEGIN systemconfigurator ###
# Configure the client's hardware, network interface, and boot loader.
echo "Iamhavingproblems"
chroot /a/ systemconfigurator --verbose --debug --configsi --stdin <<EOL
|| shellout

[NETWORK]
HOSTNAME = $HOSTNAME
DOMAINNAME = $DOMAINNAME

[INTERFACE0]
DEVICE = eth0
TYPE = dhcp
EOL
### END systemconfigurator ###


### BEGIN Unmount filesystems ###
echo "umount /a/var/lib || shellout"
umount /a/var/lib || shellout

echo "umount /a/usr/local || shellout"
umount /a/usr/local || shellout

echo "umount /a/tmp || shellout"
umount /a/tmp || shellout

echo "umount /a/proc || shellout"
umount /a/proc || shellout

echo "umount /a/ || shellout"
umount /a/ || shellout

### END Unmount filesystems ###


# Tell the image server we're done.
rsync $IMAGESERVER::scripts/imaging_complete > /dev/null 2>&1

# Take network interface down
ifconfig eth0 down || shellout

# Cause the system to make noise and display an "I'm done." message
ralph="sick"
count="1"
while [ $ralph="sick" ]
do
    echo -n -e "\\a"
    [ $count -lt 60 ] && echo "I've been done for $count seconds. 
Reboot me already!"
    [ $(($count / 60 * 60)) = $count ] && echo "I've been done for
$(($count / 60)) minutes now.  Reboot me already!"
    sleep 1
    count=$(($count + 1))
done


### END WWW9.SH (www4.image.01a.master)

Re: [Systeminstaller-users] About mkdhcpconf command!

[Michael Chase-S. <mi...@ch...>]

Did you define your machines using mksimachine? What does the output of
mksimachine --List look like?

Mike

On Sun, 2003-05-11 at 10:31, =B6=AD=D0=A1=C9=E7 wrote:
> Hi,
>    I have a problem of using the mkdhcpconf command to generate my dhcp=
d.conf
> file. When I use "mkdhcpconf -o /etc/dhcpd.conf --interface=3Deth1
> --bootfile=3Dpxelinux.0 --gateway=3D172.16.0.1" to create the dhcpd.con=
f file, then
> restart the dhcpd service, the client cann't be installed through dhcpd=
 server.
> The following is the context of the dhcpd.conf:
> ####################################################################
> # This dhcpd.conf file was generated by the systeminstaller command
> # mkdhcpconf. It reflects the contents of the CLAMDR database.
> # File generated at 17:49:30 on 4/11/2003
> ####################################################################
>=20
> deny unknown-clients;
> option subnet-mask 255.255.0.0;
> option broadcast-address 172.16.255.255;
> option domain-name "";
> option routers 172.16.0.1;
>=20
> # Defined cluster nodes...
> subnet 172.16.0.0 netmask 255.255.0.0 {
>         group {
>         }
> }
>=20
> So,what's the matter with the dhcp server? What should I do?
>    Thank you!
>                                        yours,
>                                           Tong Duan
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solution=
s
> www.enterpriselinuxforum.com
>=20
> _______________________________________________
> Systeminstaller-users mailing list
> Sys...@li...
> https://lists.sourceforge.net/lists/listinfo/systeminstaller-users
--=20
Michael Chase-Salerno           br...@us...
IBM Linux Systems Technology    Poughkeepsie, NY=20
System Installation Suite       www.sisuite.org

[Systeminstaller-users] About mkdhcpconf command!

[¶­Ð¡Éç <nh...@ma...>]

Hi,
   I have a problem of using the mkdhcpconf command to generate my dhcpd.conf
file. When I use "mkdhcpconf -o /etc/dhcpd.conf --interface=eth1
--bootfile=pxelinux.0 --gateway=172.16.0.1" to create the dhcpd.conf file, then
restart the dhcpd service, the client cann't be installed through dhcpd server.
The following is the context of the dhcpd.conf:
####################################################################
# This dhcpd.conf file was generated by the systeminstaller command
# mkdhcpconf. It reflects the contents of the CLAMDR database.
# File generated at 17:49:30 on 4/11/2003
####################################################################

deny unknown-clients;
option subnet-mask 255.255.0.0;
option broadcast-address 172.16.255.255;
option domain-name "";
option routers 172.16.0.1;

# Defined cluster nodes...
subnet 172.16.0.0 netmask 255.255.0.0 {
        group {
        }
}

So,what's the matter with the dhcp server? What should I do?
   Thank you!
                                       yours,
                                          Tong Duan

Re: [Systeminstaller-users] some problem with buildimage!

[Shou H. W. <wa...@cn...>]

I think you miss the systemconfigurator packages on your system,=20
systemimager need this package to work. systeminstaller is a tool to=20
integrate systemimager, so the full sis packages includes=20
systemconfigrator, systemimager and systeminstaller. If you want to=20
buildimage, maybe you can try "buildimage" command provided by=20
systeminstaller, which will call "mksiimage" "mksidisk"=20
"mkautoinstallscript" "mksimachine" ... provided by systemimager, and deal =

all the things that you need to do.




Yours Sincerely

Shou Hua Wang

 IBM China Development Laboratory





"=B6=AD=D0=A1=C9=E7" <nh...@ma...>
Sent by: sys...@li...
2003-05-03 11:18
Please respond to "=B6=AD=D0=A1=C9=E7"

=20
        To:     Sys...@li...
        cc:=20
        Subject:        [Systeminstaller-users] some problem with buildimag=
e!

=20

Hi,everyone

I have try to build the image by using systeminstaller,but there are some
questions when I use the buildimage command:
"WARNING: Missing required packages, continuing:
        systemconfigurator
 at /usr/bin/mksiimage line 164
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No=20
such file
 or directory)
ls: : No such file or directory
/sbin/mkinitrd: [: : integer expression expected
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No=20
such file
 or directory)
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No=20
such file
 or directory)
ls: : No such file or directory
/sbin/mkinitrd: [: : integer expression expected
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No=20
such file
 or directory)
Setting root password in image....."
   And I have checked that the /etc/fstab file is exist and can be read.
   Another problem is that I mean to use the image that built by
systeminstaller,but when I boot the client with a floop,the client seemed=20
also to
use the image that built by systemimager,what should I do?
   Thanks a lot!





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Systeminstaller-users mailing list
Sys...@li...
https://lists.sourceforge.net/lists/listinfo/systeminstaller-users

Re: [Systeminstaller-users] New to the sisuite "family" of products.

[Charles H. <cho...@hi...>]

I'll take any documentation ya'll have no matter how "beta" it is.  I am
even willing to try to help flesh out the documentation as much as I
can.  I am looking for pretty much anything.  And unfortunately the X
client isn't an option,  I have no system with X in my development
cluster at all, I have however looked at the X client for a few minutes
on a personal computer and must say that just from a quick glance I much
prefer the command line structure to the X client.
On Mon, 2003-05-05 at 16:39, Michael Chase-Salerno wrote:
> There is a user's guide that is under development. For now, the closest
> thing we have is the SIS manpage. It has some quickstart info. Also, if
> you launch tksis, there's some help panels there and the process is a
> little more obvious.
> 
> Mike
> 
> On Mon, 2003-05-05 at 16:55, Charles Holbrook wrote:
> > I just downloaded the sisuite image management set and am confused to
> > say the least.  Has anyone out there written a good set of FAQs for
> > beginners using systeminstaller as the image management/deployment front
> > end?  And help or pointers on where to look for documentation outside of
> > the help files would be greatly appreciated.  The installs that I used
> > did not install the doc directory under /usr/share/systeminstaller(or
> > appropriate directory.)
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Systeminstaller-users mailing list
> > Sys...@li...
> > https://lists.sourceforge.net/lists/listinfo/systeminstaller-users