jumpstart filesys woes

From: Matt Bradshaw (mbrad1@iastate.edu)
Date: Fri Jun 07 2002 - 14:52:16 EDT


hello. :)

when jumpstarting a set of clients, my requested swap partition size is
being ignored. following the instructions provided in the 'advanced
solaris installation' guide, here's the relevant parts of my profile...

**********
install_type initial_install
system_type standalone
partitioning explicit
filesys c0t0d0s3 768 /var nosuid
filesys c0t0d0s7 768 /tmp nosuid
filesys c0t0d0s5 512 swap
filesys c0t0d0s0 free / logging
cluster SUNWCuser
package SUNWman install
...

**********

it looks as though the jumpstart process determines the swap size based on
the physical memory of the machine and ignores the 'filesys' directive.
am i doing something wrong here? what am i missing? :)

i'm using the latest solaris8 release (02/2002) and see the behavior on
both ultra30s, and ultra10s.

thanks for the help!

regards,

-matt

Matt Bradshaw
Iowa State University, College of Engineering
---------------------------------------------
there are only 10 types of people in the world...
those that understand binary and those who don't
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:25 EDT