Latest Development FOG
-
You can also CD into trunk directory and type svnversion
-
SVN 2099 released.
With this comes some hopeful aspects to support Arch Linux for FOG Installation.
-
BSD support incoming as well or would that be painful?
-
SVN 2103 released.
Should fix, more properly, the __toString() issue as reported by andyroo. It’s needed so javascript will work properly, otherwise active tasks won’t update at all, it will just be an infinite spinner.
-
SVN 2119 released.
Has updates for tftp files. Also enables services if hosts are imported now.
-
Tom,
I had a few ideas for Full Registration option, if possible:[LIST]
[]Where it asks the yes/no questions, like joining the domain, it accepts input of other characters other than y/n. Is there any way to have FOG only accept y/n and if anything else is entered, prompt again, this time entering y/n? It would avoid having to shut down and restart the registration if you accidentally enter the wrong key
[]By default, the answer to the full registration questions is ‘no’ - is there any way to add an option in the web interface to change the defaults? For example, every machine we image gets joined to the domain - I know that can be done with groups, but it would be nice to be able to just hit enter when doing the registration
[/LIST] -
i like your ideas, but please post feature requests in the feature request section from now on
-
SVN 2160 released.
Please only update if you don’t care so much, right now, about the FOG Client, but with this release comes:
1.) Bandwidth graph now works properly based on the node that’s being looked at from the disk usage selector.
2.) Client count is based on the total number of clients the grouping of the node has.Hopefully you all enjoy.
-
Been a few changes.
SVN 2219 released.
With this release comes MANY changes. More than I’m willing to write about from 2160 to now.
The important things.
I’ve moved many of the PXE Menu stuff into db tables. This should allow, when I get around to it, me to get the PXE Menu systems into a GUI allow customization of sorts.
I’ve also added the capabilities to enable hooks for the BootMenu file. However, hooks aren’t as “dynamic” as Database entries in that they get removed when the FOG Server get’s updated. I will look into copying the hooks directory and replacing it on updates to help thwart this, however, I don’t know when it will happen.
We’re currently working on rebuilding the FOG Service as well, so many of the service files have been edited. If you want to see what we’re working on, maybe take a look at these files. The service files should all be legacy compliant, so if you have issues please let us know so we can fix them. I’ve tried testing all of the services using our testing service and the legacy, but there’s always the possibility that I’ve missed thigns.
I’ve also added Mentaloid’s wait for interface and wait for db stuff. (Thank you much Mentaloid).
Many of the ipxe files have been being updated regularly. Partially to help fix EFI/UEFI support and add support for Apple. Partially, it seems, better support for the Realtek/Intel driver subsystems. It seems things that once failed consistently are now seeming to work much better.
With that, also I’ve added a checker to the BootMenu to help fix the “console --picture” error thrown on some devices. It should detect if it’s errored out and give a basic text menu. All the same information is valid, but colors don’t display the same way. While it’s not as pretty as it once was, it should “work” better for those problematic systems.
I’m sure there’s much more information, but this hopefully gives some more information for people.
-
SVN 2248 released.
Once again, I’m falling behind the curve. Hopefully you all understand that this is not for a lack of trying, but rather a progression in work I’m attempting to get done.
With this release finally comes the ability to customize Menu Items. I will think about the ability to adjust the order of menu items, but for now this will have to do.
First and foremost. All items can be displayed in a new menu item called iPXE Menu Configuration. You will see all menu items as their own entry. The first 12 entries main fields are disabled from editing. The reason for this? Because I want to make sure you have the default menu entries we all use. If you start editing them, this may break the menu structure. That aside, you can adjust with which items are defaulted, even for the 12 that are disabled. You can also change which items they fall under. There are three main items. Non-registered Hosts, Registered Hosts, and All Hosts. These do as you might expect. If it’s all hosts, the menu entry displays on all menu’s regardless of if the host is registered or not. Non-registered Hosts items only display on hosts that are not registered. Registered hosts only display for hosts who are registered. Hopefully that makes sense. There are three others though. The Debug Options, Advanced Options, and Advanced Login Required. They’ll be unlikely to do anything for your particular new menus and I’ll think about adjusting this so it’s more proper. This field just helped me setting up the new system.
New menu items can be created through the next link called iPXE New Menu. This just presents a set of fields so you can create your own menu entries.
I’m sure there’s some kinks to work out and ask that you, the community, try to help me with this as I’m trying to make this as dynamic as possible.
When creating a new menu entry, you Must, at the least, specify Menu Item: which is the item flag that get’s called to boot the system. You must also specify a description (the neat name for the menu entry) as well.
If params is set, you will have to add a new method to rework the BootMenu which can be done with hooks, theoretically. I haven’t tested this aspect, but it should allow a method to work around new items that you want to do specific things such as changing a host name or what have you. If you’re worried, you could still edit the BootMenu file directly to pass through information. I have to figure out a way to allow this to be stored, and retrieved, from the database so things will be more dynamic and be maintained on updates, but for now it’s my best course of action.
If options is set, it will pass to the os layer calling the bzImage and init.xz files for that menu entry passing the options as command line kernel arguments. This is one method to get you a “bypass” methodology. You will need to specify the img, storage, web, imgType, and imgPartitionType. Yes, partition types can now be specified though I’ll request fractal’s assistance in documenting how to use it.
You can also delete menu items, unless they’re of the first 12 entries of course.
Of note, while you can delete the capone menu items and edit them to your liking, if you delete the capone menu item, it will be regenerated the next host that reboots. It will be regenerated with the normal defaults capone expects. After it’s generated, you are able to edit it as it’s outside of the first 12 items.
While it’s most definitely not a perfect solution, it should at least help add custom entries as so many have been requesting it.
I will be trying to improve it, and those with coding skills and methods to help make this easier are more than welcome.
-
SVN 2263 released.
With this release, temporarily, torrent-cast may be broken on newly uploaded images. However, it also maneuvers the resizable methodology aware from specifying the partitions and generate them using the same method MPS/MPA use only shrinking the partition first. This should allow OEM resizable imaging to work as it’s not taking account of the “defaults” set by microsoft.
I don’t have an OEM image with recovery and stuff to test, so please go forth and try it out if you’d all be so kind.
Thank you,
-
SVN 2269 Released.
While only a few past this time
This release comes with the following:The “new” methods of resizable images appears to work with Multicast imaging as well. It tries to first detect if sys.img.000 exists, if so, use the “old” methodology behind resizable images. Otherwise, it uses the same effects of the Linux resizable constraints. This works for Multicast and Unicast images, but may temporarily break Torrent Casting on new images as stated above already. On the files that sys.img exist, you shouldn’t have any issues. It may take me a bit before I can get torrent casting working on the new methods as I need to find a means to specify the download partition and create it.
With this also comes an image protection feature. A simple checkbox on the editing of an existing image that specifies whether or not to protect your image. It does not run chattr +i to the image folder so command line junkies will still be able to remove the contents of the files, but this is not a typical thing people just “do” from my experience. chattr +i was more used as a means in the older versions of fog because it was quick and easy to protect your image, but there was no way to know if it had been turned on and/or disabled. At least here we can see if it’s protected or not and update as needed.
-
Hi, i created images in svn rev 2209 i think it was, then updated to 2307 but after image is deployed the machine never restarts just sits waitinng so then i rolled back to the latest stable version 1.2.0. Now when i attempt to deploy said images down to the same machine it states cannot find sys.img.0000 (may not be exactly right) is this because images are no longer compatible in later svns ? from looking at it single disk resizable in 1.2.0 names the uploaded files as sys.img.0000 etc but doing the same in the latest svn names the uploaded files as dp1.img etc.
-
[quote=“sudburr, post: 33646, member: 4706”]Short of installing, is there a file in the trunk that indicates the svn?[/quote]
Just to note the following command, run from withing the root of the trunk folder, will provide the version number in the system.php of the trunk contained within the folder.
[FONT=arial][COLOR=#222222]grep FOG_VERSION packages/web/commons/system.[/COLOR][/FONT][FONT=arial][COLOR=#222222]php | sed “s/^[ \t]define(.FOG_VERSION., .([0-9.]).);/FOG Version: \1/”[/COLOR][/FONT]
Until at least the coders change how they define the FOG version.
[FONT=arial][COLOR=#222222]FYI[/COLOR][/FONT]
-
Or a simple:
[code]svnversion[/code]
In the trunk folder will tell you the current svn version.
-
Using Subversion
[CODE]apt-get install subversion[/CODE]… to retrieve the SVN of FOG only works on a ‘checked out’ version of FOG that was retrieved by using subversion itself:
[CODE]mkdir /opt/svn && cd /opt/svn && svn checkout [URL]https://svn.code.sf.net/p/freeghost/code/trunk[/URL][/CODE]On a virgin system where the FOG SVN was downloaded via:
[CODE]cd /opt && wget --no-check-certificate [URL]http://mastacontrola.com/fog_trunk.tar.bz2[/URL][/CODE]… then extracted and installed by:
[CODE]cd /opt && tar -xvjf fog_trunk.tar.bz2 && cd /opt/fog_trunk/bin/ && ./installfog.sh[/CODE]Running:
[CODE]cd /opt/fog_trunk && svnversion[/CODE]… elicits:
“Unversioned directory”
It’s only fair that the .tar.bz2 download can’t be expected to be the same version as the `checked out’ version; hence downloading the FOG SVN using:
[CODE]cd /opt && wget --no-check-certificate [URL]http://mastacontrola.com/fog_trunk.tar.bz2[/URL][/CODE]… you can then
[CODE]cd /opt && tar -xvjf fog_trunk.tar.bz2 && cd /opt/fog_trunk/ && grep FOG_VERSION packages/web/commons/system.php | sed “s/^[ \t]define(.FOG_VERSION., .([0-9.]).);/FOG Version: \1/”[/CODE]… to determine the version of what you just downloaded by this secondary method.
-
Hmmmm,
If you downloaded from my website, you DID NOT DOWNLOAD FROM SVN!
Perhaps, I’m being too harsh?
-
This may be the basic misunderstanding I developed.
I believe I got there by using your site to retrieve an unofficial kernel from way back that solved some serious NIC issues we once had.
I continued referencing your site as the source for the latest trunk of FOG, including this post in this same thread:
[QUOTE]Grabbing a version number from [URL=‘https://svn.code.sf.net/p/freeghost/code/trunk/’][U][COLOR=#0066cc]https://svn.code.sf.net/p/freeghost/code/trunk/[/COLOR][/U][/URL] doesn’t help me in identifying a downloaded trunk file.
This afternoon I saw 2093 posted as [URL=‘https://svn.code.sf.net/p/freeghost/code/trunk/’][U][COLOR=#0066cc]https://svn.code.sf.net/p/freeghost/code/trunk/[/COLOR][/U][/URL] , so I immediately downloaded [URL=‘http://mastacontrola.com/fog_trunk.tar.bz2’][U][COLOR=#0066cc]http://mastacontrola.com/fog_trunk.tar.bz2[/COLOR][/U][/URL] .
When the download completed I revisited [URL=‘https://svn.code.sf.net/p/freeghost/code/trunk/’][U][COLOR=#0066cc]https://svn.code.sf.net/p/freeghost/code/trunk/[/COLOR][/U][/URL] and it had changed to 2094. Which version did I just download? [/QUOTE]
So NOW I understand. There is the SVN and then there’s your private tarball which I mistakenly latched onto.
Meanwhile, this still works:
[CODE]Installed:
grep FOG_VERSION /var/www/fog/commons/system.php | sed “s/^[ \t]define(.FOG_VERSION., .([0-9.]).);/FOG Version: \1/”Run from within extracted fog_trunk directory:
grep FOG_VERSION packages/web/commons/system.php | sed “s/^[ \t]define(.FOG_VERSION., .([0-9.]).);/FOG Version: \1/”
[/CODE] -
While I do try to keep the tarball updated, sometimes I may make multiple svn updates before one tarball has the chance to update.
Once I’m done doing the frequent changes, I’ll run my tarball script which helps keep the private tarball updated.
I only keep it there for simplicity. It, for all purposes, is the SVN just without any of the SVN information so to keep the size small.
-
The BTSync is also still quite popular for seeding the latest updates.
Main Fog BTSync - BAU3NUY3XTKVMHHEZO6C7OH55AN2PCGJV
Fog Kernels - B7AGQ6JVIP4MF5LCRL3XURQBYC53UIS25both are read only secrets and get updates as soon as theyre put in
