Posts made by Tom Elliott

@ice4192 Like this?
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@fred06 You need to use an imaging Task. You selected “Debug” task, which was not what @george1421 was requesting.

Host -> Tasks -> Deploy -> Check the box for Schedule as Debug

@ngriffith29 FOG can rename hosts.

It can do this in multiple ways.

The simplest method is the “HOSTNAME_EARLY” which should be enabled by Default. (FOG Configuration Page -> FOG Settings -> Hostname Early)

The second and probably the safest and most dynamic way is by installing FOG Client on the machines. When you change the hostname within the FOG GUI it will automatically update the hostname the next time it checks in.

You could sysprep the machine and edit an autounattend.xml file to set the name as it initializes using post download scripts.

You could also do a similar task at how hostname_early functions using post download scripts.

The point here is there are many ways to accomplish the same task.

What, exactly, do you mean by “dynamically?”

FOG will only change a hostname of a machine that is registered via the HOSTNAME_EARLY and FOG Client methods.

@john3892 Assuming you installed FOG via git, please run:

cd /path/to/fogproject #change this to where it is actually located
git checkout dev-branch
git pull
cd bin
./installfog.sh -y

This issue should be addressed.

Thank you,

@sebastian-roth in my testing language translation worked properly using the common provided version

@fog_newb Yes, that’s the expected part.

Because php-gettext is now part of the php7.4-common package, there’s not really a need to include it as part of the packages line.

You should be good to go now.

@fog_newb Please try again? After updating of course.

@fog_newb This should be fixed in the latest.

Issue is ubuntu 21.04 is using php{ver}-common for php-gettext where in the past it was its own package. I updated the code to check for php{ver}-gettext which showed it as part of php{ver}-common and the install went through properly. Going to double check language packs download properly too.

Got the language-packs to install properly too.

Thank you,

@jonhwood360
I’ll try to document better:

• 1. Why would we use this per host? Unless you mean per server containing images?
• 2. Not a totally new database. It would integrate with the existing FOG database, under it’s own tables for definition and association
• 3. Services have a web based portion under /var/www/fog/lib/service (plugins would use /var/www/fog/lib/plugin/{pluginname}/service/} which controls the event loops, but the systemd is what starts and maintains the service operationally speaking (so reboots of the server would start the relevant service.)

@b_man Edit the fog menu item for full and quick registration:

Forgive me if my menu pointing is off. I’m running working-1.6 which has separated the ipxe menu from the fog configuration section. The point I’m making is still relevant though so hopefully you can adapt to follow what I’m saying.

FOG Configuration Page
iPXE Menu Configuration
fog.reg

Edit the boot options and append shutdown=1 like so:
mode=autoreg shutdown=1

Do the same for fog.reginput

You should now longer have the machine reboot, rather it will completely shutoff after registration is complete.

Another method would be to edit FOG_KERNEL_ARGS and add shutdown=1 to it. (FOG Configuration Page->FOG Settings->Kernel Args) This will make it so all tasks will always shutdown when complete.

@florent I don’t control the donation system we currently have.

But, what do you consider “big customers”.

I would imagine 12 big customers (so to speak) but that only equates to a total of $12000 (which is not enough for 1 developer (let alone 2).

Plus, if it’s funded solely through “donations”, then a customer can simply not pay for that year. This means there’s no accountability.

I think 12 is a pretty large number, but it isn’t enough to support a full on paid system.

Even in a “good” scenario where we are running on the idea that there is enough donations to support 2 developers in the year, that’s only 2 developers. What of the people who are simply doing troubleshooting?

The point of this thread, I think, is to get more people interested in donating their time. Instead it’s asking us to give more (which is impossible at this point.)

Think about it. @Sebastian-Roth is saying he’s readying to step back and eventually fully away from the project. That leaves me to do the development. Who’s going to step up to do the troubleshooting to those who are “paying” for support? I’m only one person.

@jonhwood360 What I could suggest, then, would be to build a Plugin.

My thoughts of how this plugin would operate:

1. To allow the admin full configuration capabilities, make the plugin create a Database that would contain a “primary” table for storing definition of the item such as the name, description, and configuration items (Such as sha256 hash, or md5 or whatever may be preferred).
2. An association table so you can associate which images you want to be managed by said definition.
3. Create a service file to run on a regular interval. (This part would have to be manually done as creating the systemd or init file on subsequent reboots.) So documentation would need to be on point.

I would need to figure out how to integrate plugin service files. Not a huge issue as we currently inject classes, hooks, and events. I just need to add code to allow injecting services which hasn’t been done yet.

Why do I say a plugin? Because at one point there was a plugin being worked on, but then other things got in the way. If you’re keen to assist it would certainly help us out and you’d get to learn a few cool things along the way.

@astrugatch The issue is the “team” is built of mostly people helping on their own free time.

There’s not really a way for us to “work full time” on FOG as there’s not enough income received to do such a feat. As such, our “support team” comes from the community as a whole.

Believe me, if I could get paid to program on FOG all day, everyday, I would. Unfortunately that’s not feasible as of currently.

I’m only one person, and with Sebastian, that made 2 developers working mostly to keep things functioning.

While we have a few more developers on titled on the team, the large majority of active Developers was @Sebastian-Roth and myself.

@Fog_Newb @Sebastian-Roth I have updated the dev-branch and working-1.6 to what I hope should do better translation.

@Fog_Newb I will need some time to create an ubuntu 21.04 to find out about the gettext installation error.

Thank you for the report and information.

@sebastian-roth https://www.php.net/manual/en/book.gettext.php

Absolutely.

Of note, we would need the language files and binary of them for the text to reflect in the UI. Of course there may be something wrong with the implementation which I’ll admit I’m not very good with.

@bristow-0 That version is for what client is readily available. 0.32 was a version of FOG, not the client. This is very very old and most people are likely using the latest versions (0.12.0)

@bristow-0 the second one, which requires fogcrypt, is no longer needed unless you have machines using the client from 0.32 and earlier.

@sebastian-roth yes it is, almost everything is behind gettext.

All the text wrapped in _( and ) is using php gettext.

@sebastian-roth or the web items are being compressed, but not decompressing for display.

@altitudehack The clear current tasks run the following:

truncate table powerManagement;
truncate table scheduledTasks;

This will restart both tables to ID of 1, but hopefully after this you will be good to go.