Bugs in FOG 0.33
-
I can understand that. But, couldn’t you just put in a simple question during install, asking if you have any other websites or software that utilizes Apache? If yes, it skips. If no, it deletes the .html file. Seems pretty simple.
-
I’m sure it could, would be easier to attack the apache config file and add .php extension to the file so it looks for the php file first
Besides it tells you after you finish installation to navigate to the “[url]http://ipaddressofserver/fog/management[/url]”.
Hell, if I remember correctly the link is even clickable in the terminal window so you don’t actually HAVE to type or copy anything, just make a shortcut.
-
I’ve always been a proponent of making installations easier, or even more customizable through the installer. Ask a bunch of questions at first, and make the setup and configuration a lot more seamless.
-
I like your stance, but I feel differently about the said subject.
I could climb on a soapbox, but my final words to utter are “this is not a bug, and does not need to be addressed.” and that’s my two cents. If others feel the same way as you do, you need to twist Tom’s arm to get what you need
-
Could there be some kind of option during the installation wether to choose clamav and htmldocs or not? Installing these packages on Redhat/Centos needs editing in the config file as it will not work out of the box.
-
That is because FOG 0.32 is sorely outdated and was meant to run on the older versions of linux. Since then newer and updated packages are being used in the later distributions. Tom is working on FOG 0.33b and I’m sure when all is said and done he will iron out the issues with htmldocs and clamav by updating the repositories and versions it uses/installs.
In the mean time please use the work arounds found on the forum to install and configure the services.
Tom started working on FOG here recently he wasn’t always the maintainer so he doesn’t have access to edit the old FOG 0.32 files and NOR should he.
-
Sorry I forgot to mention I refer to 0.33 beta…
-
The deploy date in host management, as proposed/discussed here some days ago. Here is an example of how I think this could be (in red font): [url]http://awesomescreenshot.com/03a2cmvxc2[/url]
This way it is really easy to find “old” hosts which I have to get to my office for imaging.
-
This isn’t really a bug, but a request. That’s okay though. It will require a minor schema change, but I have to do so anyway to enable shutdown to work with iPXE.
-
Whilst I think it would be good for deploy date, that still leaves the issue of having to find what image version you deployed. Of course maybe each deploy date could have the image version with it.
For this (and other benefits) I have bginfo installed (connected to sql, and then MS Access for reporting) and have a reg key that bginfo picks up. The reg key gets updated to corresponde with the fog image it will become once uploaded -
Another missing feature is a date when an image was last uploaded: (red font) [url]http://awesomescreenshot.com/0682cwm8e6[/url]
-
While I don’t mind the suggestions, I would prefer if you refrain from using the word “missing” when requesting a “New Feature” as missing, at least in my eye’s, implies it was there to begin with, but then was removed. Once again, it will require a schema update, but ultimately you could actually use the “imaging” log to check when an image was uploaded/deployed last.
-
@falko - Do you have any sort of guide on how to have FOG update bginfo. We currently have to do this manually, and it would be so helpful to have it automated! Right now, we run bginfo, update the date and image name, then have a small batch that uses mini irfanview to change from bmp to jpg, then copies to the oobe folder for the lock screen. (this is for Win7).
-
It could also be based on the info on the date of the file/directory itself, rather than stored in the db!
-
So, I don’t know if this is a bug or not, but I just came across an interesting issue when the PXE menu comes up on Dell Optiplex 790 machines. I have PXE set to default to the HD after 3 seconds (I think that is standard), but when the 790 model tries to boot to the HD, it just reboots, thus and endless reboot cycle ensues… The odd thing is, the 780 and 7010 (older and newer model) boots to the HD just fine. I’ve also confirmed that all have the most updated BIOS and all have the same mobo settings, with regards to boot/HD options.
Any ideas?
-
I’ve been seeing this issue on and off again. Would you be willing to try the workaround fix for this issue through ipxe? I ask because, as you state, this isn’t really a big with fog but more a bug with the particular bios usually from dells.
-
I’ll try a workaround. We only have 3 790’s out of 180 anyway, so it’s not that big of an issue. Just let me know what I need to do.
-
I’m going to PM you as a test for these troubled systems.
The quickest thing I could think from iPXE though is to simply put the exit statement in place of the sanboot statement under the if ($option == ‘fog.local’) line. This should force it to exit ipxe and boot to the next device in line (bring it back to bios.)
-
we had this issue on a fair few dell models and setting up chain loading fixed it so i believe ipxe should do the trick! if not:
[url]http://fogproject.org/forum/threads/dell-bootloop-chainloader-problem.4147/#post-11373[/url]
-
@Tom - I’m looking in the boot.php file, and I see a line under “if ($option == ‘fog.local’)”
It says: print “sanboot --no-describe --drive 0x80\n”;
What should I be putting in it’s place? print “exit”; <–??
