Confirmed fixed in r7585.

@Sebastian-Roth Yup. forgot to do it.

Fixed in latest.

Saw the issue, and it was a problem. You may need to re-reset the value, but you should be good to go.

Video/picture is worth a thousand words… I thought you meant the hosts search function (not the search in the listing). 🙂

@Sebastian-Roth
have not installed fog on 16.04… yet. I will lol.

@Wayne-Workman Great video. Yeah, your image size isn’t large enough to find the standard transfer rates. Just as the transfer settles down its done. (not a bad thing). In our virtual environment we can pull a sustained 6-7GB transfer rate. That is with a VM with 2 vCPU and 2GB of RAM running on a 24 core processor. But again as long as the server can move the image from disk to net pretty quick, all of the heavy lifting is done by the client. On a e6410 with a HDD we can get no more than 4.5GB/min exchanging that HDD with SSD increases the transfer to 6.1GB/min on the same hardware.

Just for comparison, when I was working with that intel NUC as the FOG server. That dual core celeron with an 256GB SSD was able to transfer at 5GB/min to a e6410 with a SSD. So really the FOG server isn’t the key to deployment speed. It more compression used and target computer performance.

But either way FOG is darn impressive that it can wake the computer up and deploy a new image in under 3 minutes. With that you could almost reimage a whole computer lab {between classes} at any school system. That is impressive.

I just looked in the wiki, there are not spaces. those must have came from me copy/pasting on my phone.

Right now, this is verbatim what’s in the wiki, notice I put quotes around the message.

yum install git -y cd ~ mkdir git cd git git clone --depth 1 https://github.com/FOGProject/fogproject.git cd fogproject/bin ./installfog.sh echo "Now you should have fog installed."

@Wayne-Workman you can put me down again. As of right now I am free, but only time will tell.

@Wayne-Workman said:

I then booted into FOS using the on board NIC to see how the adapter is recognized. FOS sees it fine.

Just to make sure the kernel is really happy with it, can you please try DHCP or setting a static IP (ifconfig ethX 10.x.y.z netmask 255.255.x.y up) on that USB NIC when you have FOS up and send pings?

Guess I struck out on this one.

Sounds a bit like it.

At first I thought Tom is right about the NIC chip behind USB being a different story. But reading up on good old John Willis again I think USB should not play a major roll:

because the USB NIC is connected through a USB host controller, that USB host controller must also have a BIOS device driver and the USB host controller must be started before the USB NIC can be started
USB host controllers are internal and fixed, they do not change, they are built into the notebook, so only one device driver needs to be included in the BIOS for the USB host controller built into the notebook

Would be great to test all those machines with one or two different USB NICs. Not sure which one to recommend?! Do you have other adapters?

It was working for a little while and then recently stopped again. I have been monitoring this thread: https://forums.fogproject.org/topic/7271/scheduled-cron-tasks-don-t-start/17

I believe this was the same bug here, same version too, 7142, so I’m linking the two together.
https://forums.fogproject.org/topic/7144/build-7142-task-management-broken

Tom was able to get this fixed, and I’ve confirmed it’s fixed.

@Sebastian-Roth said in BASH on Windows 10 … and maybe FOG also?:

as well do Intel Macs (confirmed in my own lab!!)…

Any news on that subject? My organization has thousands of Macs. Is it easier now?

@Wayne-Workman

Ubuntu 14.04

| version_compile_os | debian-linux-gnu | | wait_timeout | 28800

Oh you know what? I just figured out why this happened. blah.

I was just talking to Tom and he asked to see if the /home/fog directory existed.

It doesn’t. Why? Because I blasted the entire /home directory this morning because all those fog backups in there was crashing the server… rm -rf /home/* Yes sir…

I fixed it with
mkdir /home/fog;chown fog:fog /home/fog