@brakcounty Images are owned by the person who created it, which in the FOS os is Root. Sure we could change this, but since we give 777 permissions to the images folder, adding code and therefore complexity is useless. I’m fairly sure this is expected at this point, though I’ll admit I’ve kind of been out of the loop lately.
@jj-fullmer @Wayne-Workman I’m of the belief we keep centos/rhel support.
You’re right that many may not be using CentOS anymore, but I still believe it’s far more stable than even ubuntu/debian. People Seem to be using it because it is supported, but please don’t forget all the changes we have to make to our installation scripts each new release of Ubuntu/Debian.
Compared to RHEL, we rarely need to make any major adjustments it seems in my experience.
Plus, the installer seems to work for Rocky/Alma, because these are following with RHEL as well. Removing the one installation portion that seems to actually just work with limited intervention seems like a bad move. Plus it still allows the administrators to use different variants of linux.
Limiting specifically to Ubuntu/Debian would leave all of that out. Now, of course, the scripts could be cleaned up and should be, but I’m not kidding about each new Debian/Ubuntu release still has so many new issues that we still need to make up for.
As this is for testing I’d suggest:
wget -O /var/www/fog/service/ipxe/bzImage-rt-v215 https://drive.google.com/uc?id=1qxcjC9ZrV8lVh4T6rgBtmtgSp7SWRzL9&export=download
wget -O /var/www/fog/service/ipxe/bzImage-rt-opts https://drive.google.com/uc?id=1t4WgWHOv3wIFjnodRtMsRcaO87XIZxM4&export=download
From the host in question, assuming it’s registered, go to edit it and in the Kernel field type in the name of the kernel file to test:
E.G.:
bzImage-rt-v215
bzImage-rt-opts
@flareimp No, changing the name of either will not impact anything other than if you’re used to looking and clicking on Default/DefaultMember.
@quazz I already got it working on the working-1.6 repository. I started working to limit the amount of error messages too, though that’s going to be a project in and of itself.
For dev-branch:
Change the implode($noDBpattern, "|") to implode("|", $noDBpattern)
That should fix the issue as it seems PHP 8 standardized their usage of implode/explode for ease.
@sonic136 Can you describe what you did to fix the issue rather than just saying solved? I’m still “coming back” but I think a more descript message of what you did to fix the issue can help others more readily too.
I know I’ve been out of this for a little bit. I check in here or there, but just been extremely busy.
I don’t want to stop contributing, I just am taking time for myself after my workly duties.
I have to give a big gratitude and thanks for everyone here trying to help out whether by code, by helping the rest of the community, or documentation.
@Sebastian-Roth I know you’re busy but you’ve kept the project rolling even with the minimal availability you have. Thank you.
@george1421 I’m sure you’re busy, but I still see you posting and helping where possible and amenible. Thank you.
@Wayne-Workman I know you’re helping where you can as well. (Of course I can’t exactly post everybody because I’ve been busy and honestly not keeping up with the forums as much as I probably should.)
@everyone Thank you. Thank you for still believing in this project. We’re doing the best with what we have. Please understand in we’re lacking, it’s most likely unintentional. I know I’m just busy.
@sebastian-roth et al.
Sorry, I’ve not been able much to work on anything in a while. I will try to correct that moving forward though I’m still fairly busy with work and all.
I’m keen, if everybody else is, to look over 1.6 vs 1.5.x and just simply moving over to it. The UI for 1.5 was itself quite an overhaul but shows too little progress now (that we’re at 1.5.9). Moving to 1.5.10 seems cursory at this point, in my opinion.
I can’t say I’ll have a lot of cycles free to keep this moving in a linear fashion though.
The biggest hurdles with 1.5.x and 1.6.x are getting the codebase ready with PHP 8 support it seems too me.
I’m of course able to try to help release a 1.5.10 release if that’s what’s really needed, but I think the 1.6 codebase has been around long enough and in parallel long enough it might be a good position to just check the bases, clean up where necessary, and release 1.6.0.
Let me know what you all think.
@maxcarpone this can already be done. Per the image path field within the image, define your structure. So you could do win10/1903/imagename or win10/21H2/imagename
@90amper and the user:password is first your GUI username and password, the. Base64 encoded?
@tesparza You can update the information in FOG Settings, but it will not automatically apply it to the hosts. This is just the “default” storage point, not the thing each host uses.
If you update the AD information on each of the hosts, it will rejoin the domain using the new information. No need to redeploy the image or client.
To change all the hosts more quickly, create a group, add all the hosts you need to change into the group. Then update the AD information from within the group.
@cminus does l-testlaptop have an image assigned to it?
@chris-whiteley what do mean? What “last image date” are you referring to? The last uploaded date, or last deployed date? The last uploaded date is stored with the image. The last deployed date would be stored with the host. This could also be seen through the imagingLog item.
@tallier I don’t know what we have enough information to work off of here.
Based on what we’ve been given, it sounds like you’re attempting to use a Samba Share (Windows style sharing.)
FOG Doesn’t natively support CIFS shares currently. That’s not to say it cannot be done but it will not be a simple process.
FOG Uses NFS shares for image store currently.
@astrugatch if this host isn’t already registered, this can be enabled globally, and likely won’t hurt anything even if it’s forgotten about.
FOG Configuration Page -> FOG Settings -> KERNEL ARGS add noapic
@exworker9to5 Or this:
https://wiki.fogproject.org/wiki/index.php?title=NAS_Storage_Node
https://wiki.fogproject.org/wiki/index.php?title=Use_FOG_with_FreeNAS
https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node/1
@bruz35 What version of FOG did you install?
Are there 2 network cards on the machine?
Did you IP address change recently?
Is there firewall on the Server machine?
Is there a firewall between the client you’re using to access the UI and the FOG Server?
Was this a fresh install or an existing one?
@mnsk We don’t know what will error when. So if you see “empty response” the process is usually to view the error logs which will lead you in the direction the same way.
I have added some try/catches to the api information but this is in working-1.6 which I still think is not ready for prime time (though it is still functional in most areas).