Kernel Update - Revision history

Wayne-workman.28155: /* Kernel Update feature */

2018-02-07T16:50:29Z

‎Kernel Update feature

2018-02-07T16:50:11Z

‎Kernel Update feature

2017-02-10T06:17:00Z

‎Manual update to latest kernel

2016-08-23T04:37:06Z

‎Kernel Update Failure

2016-04-15T20:22:33Z

‎Kernel Update Failure

2016-02-13T23:11:44Z

‎Kernel Update feature

2016-02-13T22:58:24Z

‎Manual update to latest kernel

2016-02-13T21:34:46Z

‎Kernel Update feature

2016-02-13T21:29:05Z

‎Manual update to latest kernel

2016-02-13T21:27:20Z

‎Manual update to latest kernel

@@ Line 1: / Line 1: @@
 = Kernel Update feature =
-When running FOG 1.3.0 (In development as of Feb 2016), you may change what kernels are available to you via the Kernel Update feature. You may want to do this for a special or unique machine, or all machines, depending upon your needs. The feature is located here:
+When running FOG 1.3.0 (In development as of Feb 2016), you may change what kernels are available to you via the Kernel Update feature.
 Web interface -> FOG Configuration -> Kernel Update
@@ Line 17: / Line 19: @@
 If you've named your new kernel <font color="red">bzImage</font> or <font color="red">bzImage32</font> then all 64 or all 32 bit clients will automatically begin using this new kernel.
-If you've named your kernel something unique (which is suggested), you may assign the kernel to a particular host. You may do this by setting the "Host Kernel" of a host to the file name you have chosen, as pictured below.
+If you've named your kernel something unique (which is suggested), you may assign the kernel to a particular host.

← Older revision		Revision as of 16:50, 7 February 2018
Line 15:		Line 15:


−	If you've named your new kernel <font color="red">bzImage</font> or <font color="red">bzImage32</font> then all 64 or all 32 bit clients will automatically begin using this new kernel. If you've named your kernel something unique (which is suggested), you may assign the kernel to a particular host. You may do this by setting the "Host Kernel" of a host to the file name you have chosen, as pictured below.	+	If you've named your new kernel <font color="red">bzImage</font> or <font color="red">bzImage32</font> then all 64 or all 32 bit clients will automatically begin using this new kernel.
		+
		+	If you've named your kernel something unique (which is suggested), you may assign the kernel to a particular host. You may do this by setting the "Host Kernel" of a host to the file name you have chosen, as pictured below.

@@ Line 42: / Line 42: @@
 = Manual update to latest kernel =
-For CentOS 7, Fedora 21+, and RHEL 7, you may manually update the kernel and/or the inits to the latest  by following the below steps.
+For CentOS 7+, Fedora 19+, RHEL 7+, Debian8+, and Ubuntu14+ you may manually update the kernel and/or the inits to the latest  by following the below steps.
 You may copy/paste the entire script to backup all kernels/inits and download all new ones.
@@ Line 65: / Line 65: @@
 wget https://fogproject.org/kernels/bzImage32 -O /var/www/html/fog/service/ipxe/bzImage32
-#Reset permissions.
+#Reset Ownership:
 chown -R fog:apache /var/www/html/fog/service/ipxe
 chmod -R 775 /var/www/html/fog/service/ipxe
@@ Line 73: / Line 78: @@
 </pre>
-Steps for older Ubuntu and older Debian would be simiar, but the destination would be /var/www instead of /var/www/html. For owner:group permissions, on Ubuntu and Debian they would be fog:www-data instead of fog:apache
+Steps for older Ubuntu and older Debian would be simiar, but the destination would be /var/www instead of /var/www/html.

@@ Line 27: / Line 27: @@
 Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server
-If you experience the following error or a similar error, this is a FTP related issue and could be credentials or firewall or SELinux related. Usually, it is credentials or path related.
+If you experience the following error or a similar error, this is a FTP related issue and could be credentials, permissions, ownership, firewall, path, or SELinux related. Usually, it is credentials or path related.
 [[File:Kernel Update Failure.png]]

← Older revision		Revision as of 20:22, 15 April 2016
Line 38:		Line 38:


−	The above steps only skim the surface of the FTP issue, for a more complete guide, please see: [[Troubleshoot FTP]]	+	The above steps only skim the surface of the FTP issue, '''for a more complete guide''', please see: [[Troubleshoot FTP]]

	= Manual update to latest kernel =		= Manual update to latest kernel =

@@ Line 16: / Line 16: @@
 If you've named your new kernel <font color="red">bzImage</font> or <font color="red">bzImage32</font> then all 64 or all 32 bit clients will automatically begin using this new kernel. If you've named your kernel something unique (which is suggested), you may assign the kernel to a particular host. You may do this by setting the "Host Kernel" of a host to the file name you have chosen, as pictured below.
 [[File:FOG 1.3.0 Unique Kernel name graphic.png]]
@@ Line 28: / Line 30: @@
 [[File:Kernel Update Failure.png]]
 You can set the FTP username and password and destination path used for kernel updates here:
 [[File:FOG 1.3.0 Kernel Update FTP Settings.png]]
 The above steps only skim the surface of the FTP issue, for a more complete guide, please see: [[Troubleshoot FTP]]

@@ Line 45: / Line 45: @@
 rm -rf /var/www/html/fog/service/ipxe/old
 #Make a directory to put old kernels & inits into.
 mkdir /var/www/html/fog/service/ipxe/old
-#Move old kernels, get new ones.
+#Move old inits, get new ones.
 mv /var/www/html/fog/service/ipxe/init.xz /var/www/html/fog/service/ipxe/old
 wget https://fogproject.org/inits/init.xz -O /var/www/html/fog/service/ipxe/init.xz
@@ Line 54: / Line 54: @@
 wget https://fogproject.org/inits/init_32.xz -O /var/www/html/fog/service/ipxe/init_32.xz
-#Move old inits, get new ones.
+#Move old kernels, get new ones.
 mv /var/www/html/fog/service/ipxe/bzImage /var/www/html/fog/service/ipxe/old
 wget https://fogproject.org/kernels/bzImage -O /var/www/html/fog/service/ipxe/bzImage

← Older revision		Revision as of 21:34, 13 February 2016
Line 15:		Line 15:


−	If you've named your new kernel <font color="red">bzImage</font> or <font color="red">bzImage32</font> then all 64 or all 32 bit clients will automatically begin using this new kernel. If you've named your kernel something unique (which is suggested), you may assign the kernel to a particular host. You may do this by setting the "Host Kernel ~~Arguments~~" of a host to the file name you have chosen, as pictured below.	+	If you've named your new kernel <font color="red">bzImage</font> or <font color="red">bzImage32</font> then all 64 or all 32 bit clients will automatically begin using this new kernel. If you've named your kernel something unique (which is suggested), you may assign the kernel to a particular host. You may do this by setting the "Host Kernel" of a host to the file name you have chosen, as pictured below.

	[[File:FOG 1.3.0 Unique Kernel name graphic.png]]		[[File:FOG 1.3.0 Unique Kernel name graphic.png]]