Faq - Revision history

Bruce at 09:49, 17 January 2014

2014-01-17T09:49:26Z

2014-01-03T11:42:41Z

2014-01-03T11:41:27Z

2014-01-03T11:37:27Z

2014-01-03T11:34:52Z

2014-01-03T11:31:11Z

2009-08-17T14:45:13Z

2009-08-17T14:44:13Z

2008-05-23T13:35:26Z

2008-01-28T17:36:10Z

←Older revision		Revision as of 09:49, 17 January 2014
Line 227:		Line 227:

	pkg install network/dhcp/dhcpmgr - incase you want to use the GUI		pkg install network/dhcp/dhcpmgr - incase you want to use the GUI
		+
	pkg install service/network/dhcp - for pntadm etc		pkg install service/network/dhcp - for pntadm etc

@@ Line 194: / Line 194: @@
 JET was originally developed in the era of Solaris 7, 8 and 9. As such whatever documentation there is, normally uses one of those in examples.
-JET works fine with Solaris 10, and unless anything specific is said, it works in the same fashion with 10 and indeed 11, in the same fashion as previous versions of Solaris.
+JET works fine with Solaris 10 (and indeed Solaris 11), in the same fashion as with previous versions of Solaris.
 You can't currently use JET to install Solaris 11 systems, as Oracle have changed the installation technology to 'Auto Install' which is different from JumpStart. You can still use a Solaris 11 system to deliver both Jet/JumpStart installs to Solaris 10 (or lower) clients, and AI installs to Solaris 11 at the same time though.

@@ Line 190: / Line 190: @@
 JET will now "do the right thing" based on the allocation method in your template.
-==== Documents reference Solaris 8 and 9, not 10. Does this work with Solaris 10 ? ====
+==== Documents reference Solaris 8 and 9, not 10. Does this work with Solaris 10 and Solaris 11 ? ====
 JET was originally developed in the era of Solaris 7, 8 and 9. As such whatever documentation there is, normally uses one of those in examples.
-JET works fine with Solaris 10, and unless anything specific is said, it works in the same fashion with 10 (<strike>and indeed 11 if that is what it gets called</strike>) in the same fashion as previous versions of Solaris.
+JET works fine with Solaris 10, and unless anything specific is said, it works in the same fashion with 10 and indeed 11, in the same fashion as previous versions of Solaris.
 JET doesn't deal with upgrades at all; if you want to upgrade using JumpStart, then you need to hand-craft something - there are too many risks for JET to be able to claim to work properly in every situation, so it doesn't claim to do upgrades at all.

@@ Line 194: / Line 194: @@
 JET was originally developed in the era of Solaris 7, 8 and 9. As such whatever documentation there is, normally uses one of those in examples.
-JET works fine with Solaris 10, and unless anything specific is said, it works in the same fashion with 10 (and indeed 11 if that is what it gets called) in the same fashion as previous versions of Solaris.
+JET works fine with Solaris 10, and unless anything specific is said, it works in the same fashion with 10 (<strike>and indeed 11 if that is what it gets called</strike>) in the same fashion as previous versions of Solaris.
 JET doesn't deal with upgrades at all; if you want to upgrade using JumpStart, then you need to hand-craft something - there are too many risks for JET to be able to claim to work properly in every situation, so it doesn't claim to do upgrades at all.
@@ Line 212: / Line 212: @@
 Solaris 11 is "different" with Auto Install replacing JumpStart. This means it does not include many packages required for JumpStart by default
-To enable S11 to act as a JEt server, add the following.
+To enable S11 to act as a JET server, add the following.
 pkg install system/boot/network

@@ Line 224: / Line 224: @@
 pkg install network/dhcp/dhcpmgr        - incase you want to use the GUI
 pkg install service/network/dhcp        - for pntadm etc
 Then carry on as normal, except using zfs share and not /etc/dfs/dfstab

@@ Line 207: / Line 207: @@
 Timeservices
 SUNWcns
 === Configuration ===

@@ Line 198: / Line 198: @@
 JET doesn't deal with upgrades at all; if you want to upgrade using JumpStart, then you need to hand-craft something - there are too many risks for JET to be able to claim to work properly in every situation, so it doesn't claim to do upgrades at all.
-==== Using OpenSolaris as a JET server
+==== Using OpenSolaris as a JET server ====
 If you have installed OpenSolaris, you may need to add the following packages to enable all services required.

←Older revision		Revision as of 14:44, 17 August 2009
Line 197:		Line 197:

	JET doesn't deal with upgrades at all; if you want to upgrade using JumpStart, then you need to hand-craft something - there are too many risks for JET to be able to claim to work properly in every situation, so it doesn't claim to do upgrades at all.		JET doesn't deal with upgrades at all; if you want to upgrade using JumpStart, then you need to hand-craft something - there are too many risks for JET to be able to claim to work properly in every situation, so it doesn't claim to do upgrades at all.
		+
		+	==== Using OpenSolaris as a JET server
		+	If you have installed OpenSolaris, you may need to add the following packages to enable all services required.
		+
		+	For rpc.bootparamd and in.tftpd, needed to jumpstart a SPARC box,
		+	SUNWbs (formerly the packages were SUNWbsu and SUNWbsr)
		+
		+	Timeservices
		+	SUNWcns

	=== Configuration ===		=== Configuration ===

←Older revision		Revision as of 13:35, 23 May 2008
Line 812:		Line 812:

	This 'feature' is also present in Nevada builds (Solaris Express / Solaris 11).		This 'feature' is also present in Nevada builds (Solaris Express / Solaris 11).
		+
		+	==== Unable to locate suitable disks ====
		+
		+	If you install Solaris onto scrubbed disks which have no Solaris label on them, the install will halt because it can't find disks to install too. This is normally more of an issue with x86 systems that don't have a Solaris partition, but can also be encountered on Sparc boxes too.
		+
		+	On Sparc systems, use the 'format' command to 'label' the disks; on x86, fdisk can be used to create a Solaris partition.

	==== I am warned about missing patches, but cannot add ====		==== I am warned about missing patches, but cannot add ====

←Older revision		Revision as of 17:36, 28 January 2008
Line 301:		Line 301:

	Further comments are within the the zone template		Further comments are within the the zone template
		+
		+	==== How does flash work with JET ? ====
		+
		+	The JetFLASH module can be added in like any other
		+
		+	make_template -f -T <template> <template> flash
		+
		+	Simply edit the template, get to the new flash section and edit the flash_archive=
		+	with the path to your NFS shared flar file
		+
		+	line, taking note of the example higher up
		+
		+	ie
		+	flash_archive_locations="nfs://10.1.1.11/archives/sample"
		+
		+	Rerun make_client and JumpStart
		+
		+
		+
		+	===== What is the recommended flash creation line =====
		+	A recommended line to produce a flash archive
		+
		+	flarcreate -n "<Something meaningfull>" -R / -S -c file
		+
		+	ie:
		+
		+	flarcreate -n "Sol10 U2+Rec Patches" -R / -S -c /var/tmp/s10.flar

	==== Using Jet-4.1, how do I get 'sds' and 'flash' to work together - ie, after applying a flash image, I then want to mirror with the 'sds' module. ====		==== Using Jet-4.1, how do I get 'sds' and 'flash' to work together - ie, after applying a flash image, I then want to mirror with the 'sds' module. ====