Latest FOG 0.33b
-
Update: I found the problem. When I ran an upload from the host listing I got an error telling the password for tftp server was wrong. When I corrected this it worked as expected. Perhaps this error checking could be implemented in the Host management as well?
-
[quote=“Albatros, post: 20970, member: 16710”]Yes the upload button in Active Tasks, donest work. Try it over this way: Host Management -> List All Hosts -> Click Upload button from your host
Over this way it it works on my side.[/quote]I noticed, thanks. Tom: probably a bug which needs to be fixed?
-
Tom:What is the difference between Partclone and the old system (dont remember the name)
-
I really miss the progress bar in active tasks in Task Management. What has happened with it?
-
Partimage is the “old” system.
Mainly that, technically, partimage for ntfs cloning was experimental, where it’s stable and fully supported in partclone.
The methods used for cloning are different as well, though I couldn’t possibly begin to tell you the main differences.
Hope that helps.
-
Hello all,
I’m about to release another revision of fog. This time, the only major change is from the config.php file(s). I’ve removed all the settings from the /opt/fog/service/etc/config.php and placed them in the {FOGWEBDIR}/commons/config.php file. The only thing the etc/config.php file contains is the webroot information for your server. The thought here is to have it stop relying on two config files. I’ve also, tried, to clear up duplicate variable assignments. All of the service files now reference the {FOGWEBDIR}/commons/base.inc.php. This means, presumably, I can maybe start using class calls from the service files to perform tasks. This, ultimately, means less code to maintain from the service sections as everything only has to be written the one time.
This, also, forced me to remove the extra spaces at the end of the MulticastManager.class.php
Hopefully all can test, just to be on the safe side, that all is still working properly for them, but then again, that’s why I have such a great community of supporters.I’m, systematically, trying to remove the need for the web/commons/functions.php file so please bare with me as I’m sure to break somethings unknowingly. I’m just trying to make things easier to change in the future.
r1029 is released.
-
Thanks for all the hard work Tom. I hope u have a really good Christmas
-
I will and wish the same for all of you!
r1030 released as well.
Apparently I had a weird type on FOGMulticastManager UDPSENDERPATH. It’s fixed now, or at least should be.
-
r1031 released now.
Has some more …reduction I guess… within functions.include.php being moved to classes and what not. I was also able to fix an issue when a task was performed (due to the moves of functions to class calls) it would not find the co.txt files properly.
Hopefully you all enjoy.
-
Working on moving many things to class files. Right now, I’ve moved and tested, processing of logins (mobile and regular) through a class file. Working on creating a LoginForm class as well. This allows less files, in the long run, for controlling all the aspects.
It’ll be a little while before I get another revision out I expect. If you want to see just let me know and I’ll send up the new stuff.
-
r1032 is out.
Contains the new Class files and uses those methods for both main and mobile pages. Removed the processlogin.php and processmobilelogin.php from commons. Remove mainmenu.php from commons. Removed loginform.include.php from their respective places of management/includes/loginform.include.php mobile/includes/loginform.php.
Had to adjust the Mobile image name just slightly so I can use the Mainmenu.class.php file for it’s menu generation.
Hopefully you all don’t even notice the change, but in case you do, as always, try to let me know and I’ll get a fix out.
Thank you,
-
Working on a rewrite, currently, of the Post_Stage2.php. Apparently using FOGFTP is not correct.
-
Post_Stage2.php has been updated, slightly, to work with class files which ultimately means MUCH less code for easier management. Will work this same methodology to the other service files, but this one was my starting point, therefore the best chance I had at testing.
r1034 released to fix the Post_Stage2.php file itself.
Thank you,
-
r1035 fixed issue with system.php file and created the basepath/web_root information.
r1036 updates the TomElliott.config file to allow native VMWare disk recognition. (I love this part.)
I know the changes are coming fast, but it’s all worth it I think. My normal tarball is also updated to r1036 just so all are aware. I haven’t, yet, added my new kernel to the tftp folder during installation, but somehow I think it’s worth it.
-
I have corrected the issue with XP imaging. First part, it was generating a random Sector to start imaging to. This has been fixed. Another issue I was running into was the boot flag wasn’t being set, so I’ve corrected this. Due to this, I’m rebuilding the init.gz file and it will be inserted into the latest revision of fog once complete. I’ll post once this is done and tested.
This issue should be corrected now. The only issue I’ve yet to get a fix is the renaming, if the image already exists. It’s renaming the $mac address folder /images/dev/$mac/$mac.000, so during the creation of the actual image file it gets stored as:
/images/$imgname/$mac.000 instead of /images/$imgnameThat’ll be for later. For right now, the correct action is to move the $mac.000 file and rename it as the image name.
For example, if your image name is testxpimage
The system will be stored as: (Assuming a mac address of 00:01:02:03:04:05)
/image/testxpimage/000102030405.000Just move the folder as and move the image file (the .000) as such:
[code]mv /image/testxpimage /image/tmpfolder
mv /image/tmpfolder/000102030405.000 /image/testxpimage
rmdir /image/tmpfolder[/code] -
r1038 was released to fix init.gz script to properly deploy windows xp images. (YAY, THIS WORKS NOW…I’ve tested with a VM and all seems to work properly, please test to properly verify.)
r1039, forgot to add my new Functions.class.php file to the last revision, so it couldn’t checkout the task. This is corrected now.
My fog tarball has been corrected as well.
Thank you,
Sorry about all the fixes/issues lately. It’s a lot of testing writing, so simple variable names (which is the issue in this case) keep getting missed. Hopefully all is now good.
-
r1040 is released.
This fixes UDPSENDERPATH issue in the config.php file. Originally had it as UPDSENDERPATH (UP rather than UD) . Fixed the WEB_ROOT/WEBROOT issue in the FOGTaskScheduler file.
-
r1041 is released.
It should fix issue of Windows XP images, when created resizable, not being moved/renamed correctly. The current method (before this) just moved the /images/dev/$mac/$mac.000 to /images/$imgname as a folder containing: /images/$imgname/$mac.000 Which when trying to redeploy didn’t work so well as it couldn’t find the file name and start the deploy. Though not fully tested, this new method should send the osid, if it’s the xp osid, it will move the file inside /images/dev/$mac/ and rename that rather than the entire folder.
Hopefully all works as expected. This is similar to the old way XP resizable images were created. I don’t know if other methods work properly under this, but I’m guessing we could make it work now that I’m starting, I think, to get a hang of this all.
-
r1042 is released.
Tested the Post_Stage2.php file and it performs a check on the srcdd as well as the src origination schema (/images/dev/$mac/$mac.000) so it copies the file into the correct location now. All else should remain the same as before, but needed this check for Windows XP resizable images.
Will try deploy, but as I’ve, as far as I can tell, fixed the fog script to create the partition properly all should work well. Tarball updated to r1042 as well.
Thank you all,
-
r1043 is released with “true” Image deletion. If you delete the image from fog, it will delete the image from the file system as well. I will add checks and balances to make sure people intend to delete the image or not, but for right now it’s default to delete the image. If you don’t want to delete the actual files, just rename the original image to something like /images/image2 and recreate the file or directory (as you choose) to /images/image, then delete the image record from fog. Hopefully r1044 will add that questioning functionality to the file deletion part so we don’t have to do that.
