@probbier Please tell us more about which files exactly you edit! Give full paths…

@nvdp2002 The installer uses curl instead of wget but both usually make use of the same environment variables. Please try this:

curl -ko /tmp/Kernel.TomElliott.4.19.6.64 https://fogproject.org/kernels/Kernel.TomElliott.4.19.6.64

@george1421 Cool thanks. Version os 2019.02.1 and current config is here 64 bit and 32 bit.

But we also need to modify partclone.mk… will try to give you more details on this later.

@mwolfe60 Snapins is not Plugins!

Did some more testing and will merge this into dev-branch now before the new release. Have tested on CentOS (existing installation and fresh) as well as Debian (fresh installation). Should be good to go.

@mwolfe60 Are you sure ALL nodes are updated to 1.5.5??

Do you use snapins? We have a bug in 1.5.5 where snapin replication is not working properly and will re-transfer over and over. This is fixed and will be in the next release coming very soon!

@mwolfe60 Seems like something corrupted your mysql package. But there is a solution: https://askubuntu.com/questions/643251/having-trouble-installing-and-removing-mysql-in-ubuntu

Simply create the file /etc/mysql/my.cnf.fallback with the following content: https://www.apt-browse.org/browse/ubuntu/xenial-security/main/all/mysql-common/5.7.25-0ubuntu0.16.04.2/file/etc/mysql/my.cnf.fallback

After that again run apt-get upgrade

@hariskar Where did you get the newer dnsmasq package from? Manually downloaded? You need to download dnsmasq-base as well. That is where the actual binary is included on Debian systems.

See the difference here:

dpkg -l | grep dnsmasq
ii  dnsmasq                               2.80-1
ii  dnsmasq-base                          2.72-3+deb8u4

@hariskar You are aware of the fact that you need to manually configure dnsmasq? https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq

Not sure about the version issue. Please run the following commands to find out more about this:

dpkg -l | grep dnsmasq
dpkg -L dnsmasq
dpkg -L dnsmasq-base | grep bin

Beste if you copy&paste the commands so you don’t mix up with the different parameters. Post results here in the forums.

Sorry if this sounds a bit daunting. Not meant to. I just stumbled upon a changelog message that I would like to discuss with all the FOG users out there:

From https://clonezilla.org/downloads/stable/changelog.php (Clonezilla and Partclone are kind of partner projects and as I simply couldn’t find release notes on Partclone itself I need to reference this one!):

Clonezilla live 2.5.3-3
…
Partclone was updated to 0.3.8. //NOTE// New image format is used in this release. It is different from the one saved by Partclone 0.2.x.

Within FOG we currently use version 0.2.89 which seems to be the latest 0.2.x release. That’s fine from my point of view even though it’s a bit dated. Updating our whole FOS base system to the latest Buildroot version I ran into a compiling error with Partclone as it still uses ustat function which is deprecated in up-to-date glibc version (2.28). So we seem to get to a point where we need to patch Partclone 0.2.89 to be able to further use it within FOG or we need to come up with a way on how to move to version 0.3.x…

One would think that newer versions of Partclone are able to read the old image format but there are hints on the web that it can cause trouble: https://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/34023334/

Keep in mind that Partclone versions 0.3.x still are proposed as unstable on the official website. On the other hand it’s in use with current Clonezilla releases since almost two years!

If you can’t follow all the tech details above, don’t worry about it too much. The basic message is Partclone seems to move on using a different image format not compatible with what we used to have! What that essentially means is that if we also move forward and add Partclone 0.3.x to FOG that would break all existing images I reckon (not tested yet).

@Quazz Would you find the time to compile FOS builds with Partclone 0.3.x for testing?

@pdit Really strange. Why would it detect the link properly after you get to the shell? Can you possibly connect your client directly to the FOG server just for a quick test? Just to get those switches out of the equation for the moment?

@pdit Try those inits: https://fogproject.org/inits/delay/init.xz and https://fogproject.org/inits/delay/init_32.xz (both have the timeout increased from 35 to 120 seconds - let’s see if that works for you)

@krait I guess there is no way around but you need to dive in and figure this out. We can’t configure that for you on your server but we can help when you run into issues and post steps you took and error messages you saw.

You already found one of the best resources on adding ISO boot files to FOG. ISO booting it a bit complicated but having George’s descriptions at hand is of great value! It’s also using “iPXE New Menu Entry” but as I said, there is more to it. Just get into and let us know when you run into issues.

especially Windows.iso installer

I haven’t done this myself but from reading other people’s posts here in the forums I get the impression that Windows ISOs might be a bit harder than Linux ISOs. Not exactly sure thought. @george1421?

@pdit The Linksys LGS108P is not a real old school dump switch. Take a look at the specs and you’ll see it does have Spanning Tree features.

The KEEBOX SGE05 seems to be more of a dump one.

I’ll upload modified init’s in the next hour for you. Let’s see if that is of any help to you.

@loosus456 said in Is the FOG installer supposed to ask for an image storage location?:

By that same logic, I could say, “one of the great features of install scripts is that you can ask everything upfront so that end users don’t have to change anything later.”

I won’t discuss this!

See I don’t want to bully you on this. It’s just that I have other things to do than argue about why a installer should be this or the other way. If you think it should then why don’t you implement the fix yourself and post a pull request on github. We’ll happily add that to the official code.

Cross linking this: https://forums.fogproject.org/topic/12506/client-inventory-option

@astrugatch While I definitely see why you’d like to have this feature in the fog-client I can’t see us adding this any time soon for different reasons:

• There aren’t many requests for that feature
• It would take a fair amount of time to implement because it needs to be done sort of from scratch in the fog-client and as well cross-platform (Win, Linux Mac). I guess that I’d take weeks to do this as I can spend only a couple of hours of my free time to work on this project.

If you really want/need this feature I may ask you to join in and help us. Does not need to be programming the client. First you might want to open an issue on github as things won’t get lost as fast as they do here in the forums. Second you better post which clients you have (Windows? Version?) so we might focus on those first when implementing the feature. And third, please get your hands dirty and help us find out how to grab the inventory data on the client (we can do registry querys, call programs and system libraries). Collect all that information in the new issue on github and we might be able to add this feature over the next few weeks.

I am making this a normal thread as this is not a real FOG problem that can be just solved. Please follow up in the feature request topic here: https://forums.fogproject.org/topic/12506/client-inventory-option

@loosus456 said:

I believe I actually used the dev-branch when I installed it. Just to verify, that is 1.5.5.3, right?

Yes that should be dev-branch. I will see if I can replicate the infinite loop issue when specifying the variables as you did.

Beside that I am wondering why ther is so much need to move the location to a different place?! One of Linux great filesystem features is that you can mount storage devices/partitions pretty much anywhere in the filesystem tree. So instead of having your images disk/partition mounted to /newpath/to/location just mount it in /images and everything else will fall in place. I am sure there might be good reasons not to do so and I am open to discuss this!

@nvdp2002 You keep having typos in the URLs! Try copy&paste this one: wget https://fogproject.org/kernels/Kernel.TomElliott.4.19.6.64

It’s “Elliott” (with two t’s) and “Kernel.” (with uppercase k)…