@sebastian-roth Great job, the installation tests are looking beautiful today.

@sebastian-roth thanks for the information. Since everything else is running fine there has been no need to try the dev-branch. It’s good to know that it will be included in the next release.

Thanks, it’s done.

@zaboxmaster said:

I know about dban etc… just nothing seems to work

What exactly have you tried and what was the outcome/error?

Just a quick note: FOG is made up of several open source tools to also allow for wiping disks. BUT we only provide those tools and have no share in them producing any kind of report or proof for you. So we probably won’t be able to help you with that point.

@tom-elliott unicast fonctionne bien mais multicast non cela ne fonctionne pas en multicast j’ai toujours la même erreur comme tout à l’heure

@george1421 @Sebastian-Roth I just wanted to let you know that I moved to snapins and never regreted it for one second 🙂
It is indeed much more flexible and involves way less maintenance on FOG updates.

Thanks again!

bonsoir george, stp excuse moi de venir ce soir te poser ce problème,

je veux déployer mon image sur une machine physique mais cela ne fonctionne pas. voici l’erreur que je reçois.20210404_012630.jpg 20210404_012700.jpg

la marque de mon ordinateur c’est un dell latitude et en passant, mon serveur est sur une machine virtuel et j’ai connecté ma machine cible directement sur la machine physique qui abrite mon serveur fog sur virtual box. par quelle moyen savoir que ma machine physique est bien connecté à mon serveur virtuel???

@brakcounty said in Quick question about the tftp/ftp credentials:

The web ui login username is still fog and a password I set.

That is correct. Those are two different things. The web UI user has nothing to do with the fogproject service account (Linux).

@astrugatch I haven’t done anything on this yet.

@moderators would there be any issue with using a forums topic to host torrent files for a fog VM image?

@wayne-workman said in Fedora 33 and Ubuntu 16:

wants to get everything OS agnostic by replacing PHP components with NodeJS ones, getting the UI and API away from making native OS calls, so on.

I agree with this too. Node.js opens the door to running the FOG server on a lot more platforms than just linux. It WILL be a long road to get there (if ever). We do need 3-4 node.js new developers to step up and restart the FOG-too project to get things moving.

@george1421 @Sebastian-Roth Thank you very much for the recommendation I would try to integrate it into the database just for the trill of it, I may even try to edit the php to integrate it into the original system.
Thanks

The figures seem much more stable now, much less fluctuations. Thank you @Quazz !

@EduardoTSeoane It will be interesting to see how optimization works for you. With the size of your campus we may need to split the database from the FOG server to give the sql database more CPU time. We need feedback from large campuses like you have to help with performance tuning of FOG.

@Ken-Zug The only thing I might add to George’s answer is that we might add even newer kernels like 5.8.x to help people with newer hardware. There is nothing specific about 5.6.18 but it was a stable kernel version back then when people started asking about driver support on newer hardware.

The 4.9.x line is rock solid from a Linux and a FOG perspective - been tested many times in hundreds of setups. The 5.6.x and newer kernels have not been used as much…

Don"t worry it’s not for copy 😉
I use FOG, just want to see (untderstand) how wakeonlan is send by FOG. (etherwake or wakeonlan, with options or not etc)
When i have try grep i do mistake syntax this explain why i found nothing on my server.
Sorry thanks for the tips

@Kirill Great, I will add this to the fog-client in the next days!

For the FOG translations you wanna take a look at the files here: https://github.com/FOGProject/fogproject/tree/dev-branch/packages/web/management/languages

The master branch points to the current version (1.5.8 as of now) and for new things we work on dev-branch (as in the link above) or created feature branches. As we don’t have much changes in the language files currently I would suggest you work on what we have in dev-branch.

Best if you grab a copy of the english version and start translating on that. I know there are many lines marked as fuzzy because of changes in strings. I was hoping to clean this up at some point but never got to it so far. If you are keen you are more than welcome to clean this up first. Would be really great!