PXE image looping

[Wayne Workman]

@george1421 said:

Sorry I shouldn’t think the whole world is virtualized.

I was just going with the flow lol.

[ManofValor]

This post is deleted!

[Wayne Workman]

@ManofValor It’s not a fog question. It’s a Linux question. If CentOS 7 supports it (or any other distro of Linux), then fog can use it.

[ManofValor]

@ManofValor

[Wayne Workman]

@ManofValor Looks good, the only suggestion I’d make is making the /boot partition 1GB. Who knows how long you’ll use this server?

Once I helped with a Ubuntu server that was literally out of space on it’s boot partition… We only got by because I found some older kernels to delete!

[george1421]

@ManofValor I know its probably too late, but I would have done the /opt mount point instead of /opt/fog/images. That way all of the opt stuff would go into that 400GiB drive. What you won’t get is /opt/fog/snapins that will still go onto the root partition. Sorry I was late, stuck in a teleconf call for 2 hours.

[Wayne Workman]

@george1421 said:

I know its probably too late, but I would have done the /opt mount point instead of /opt/fog/images.

It’s not too late. I’d say go back and do it right.

[ManofValor]

@george1421 I haven’t gone any farther than the pic. Waiting to make sure I do this right.

[george1421]

@ManofValor Ok then just change the mount point to /opt and you should be good to go.

Linux (*nix) is a bit confusing for the windows folks. As windows gets older it gets more features like *nix. This whole mount point is cool once you understand it. Its a bit like what DFS is but on a local hard drive concept. You can traverse between hard drives or network shares for that matter, but just changing to a different directory. From the UI level there is no drive or d: drive. The d: drive would just be mounted to a directory and you would change into that directory for data to go onto the d: drive.

[Sebastian Roth]

@george1421 Why using /opt/fog/images? As Wayne already said: “I would prefer though to mount the 2nd hdd to /images because /opt/fog/images is a deviation from the expected.” Both will work, but sticking with the default (/images) might be wise as well. @ManofValor Up to you.

[george1421]

@Sebastian-Roth The logic is that the snapins (which could also be huge) would not be captured if only /images were mounted over on the new disk. My preference would be to keep EVERYTHING fog related in /opt/fog. (But I’m one of those type ‘A’ people, so that that for what it is. )

[ManofValor]

@Sebastian-Roth Seeing that I am an infant (maybe a toddler by now) with this stuff I just went with a recommendation/suggestion.

[ManofValor]

Ok, so CentOS is installed. We’ve done so much I just wanna make sure I take the right steps again. I just go straight to installing fog trunk right?

[Sebastian Roth]

Give it a go I’d say. Make sure your internet connection is fine so that kernel and init files are properly downloaded.

[Wayne Workman]

@Sebastian-Roth said:

Give it a go I’d say. Make sure your internet connection is fine so that kernel and init files are properly downloaded.

Easier said than done. You might want to shoot him a PM. Poor guy keeps having a lot of network issues. I did some troubleshooting and I think his router isn’t letting the fog server’s traffic get out. He says there is no proxy but I’m not so sure about that.

[ManofValor]

@Wayne-Workman I’ve checked and asked my boss, who built our system from the ground up, and we are not behind a proxy.