Latest Development FOG
-
Hi,
would be nice if the webif would check that 5 signs are entered and auto add the “-” to the input field, also if key is pasted it have to check if there are 5x5 pairs separated by “-” if a key is pasted without the “-” it should auto add them if at least 25 signs are pasted.
Regards X23
-
SVN 2077 released: Please see below.
I’ve now added the ability to add “individual” password login settings to menu items
My current menu that is tested and working, although very minimal, is:
[code]isset ${userID} && goto do_me || goto MENU
:do_me
kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.1 web=10.10.10.118/fog/ consoleblank=0 loglevel=4 type=down img=win7actsysprep ftp=10.10.10.118 imgType=n osid=7 storage=10.10.10.118:/images capone=1 imgFormat=0
imgfetch init.xz && boot || goto MENU
:MENU
menu
item --gap Please Select one of the images below
item fog.local Boot from hard disk
item d101_64 D101 Base Image (64 bit load)
item return Return to main menu
choose --default fog.local target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:d101_64
chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU
:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || goto MENU
autoboot[/code]Notice the :d101_64 how it has the chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU ?That’s all that’s needed to have a “login” for your menu item. Notice the top where it says :do_me? This is important to note that it’s ABOVE the menu generation part of the advanced menu setup.
As I stated, this is very basic, but a method to :sort: the different functions could be:
[code]isset ${userID} && iseq ${bootnum} 1 && goto do_me ||
isset ${userID} && iseq ${bootnum} 2 && goto do_me2 ||
goto MENU
:do_me
kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.1 web=10.10.10.118/fog/ consoleblank=0 loglevel=4 type=down img=win7actsysprep ftp=10.10.10.118 imgType=n osid=7 storage=10.10.10.118:/images capone=1 imgFormat=0
imgfetch init.xz && boot || goto MENU
:do_me2
kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.1 web=10.10.10.118/fog/ consoleblank=0 loglevel=4 type=down img=blahblah ftp=10.10.10.118 imgType=n osid=7 storage=10.10.10.118:/images capone=1 imgFormat=0
imgfetch init.xz && boot || goto MENU
:MENU
menu
item --gap Please Select one of the images below
item fog.local Boot from hard disk
item d101_64 D101 Base Image (64 bit load)
item return Return to main menu
choose --default fog.local target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:d101_64
set bootnum 1
chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU
:d102_64
set bootnum 2
chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU
:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || goto MENU
autoboot[/code] -
Short of installing, is there a file in the trunk that indicates the svn?
-
[quote=“sudburr, post: 33646, member: 4706”]Short of installing, is there a file in the trunk that indicates the svn?[/quote]
The “cloud” on the FOG Web GUI page will display the SVN revision number.
-
Hi,
i also thougth that first, then i started to believe that he talks about a file (filename or content) with current svn number.
I searched for stuff like that and couldn’t find that if that was the scope.If yes you may could parse “Revision XXXX” from the source of:
[url]https://svn.code.sf.net/p/freeghost/code/[/url][IMG]http://i.imgur.com/0QOYnfU.png[/IMG]
Search for "Revision[SPACE][4NUMBERS], cut last 4.
Regards X23
-
Grabbing a version number from [url]https://svn.code.sf.net/p/freeghost/code/trunk/[/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/[/url] , so I immediately downloaded [url]http://mastacontrola.com/fog_trunk.tar.bz2[/url] .
When the download completed I revisited [url]https://svn.code.sf.net/p/freeghost/code/trunk/[/url] and it had changed to 2094. Which version did I just download?
-
As the previous gentleman have stated, it’d stored in the “cloud” on the logo part of the page. That being said, the version number’s only change when I make a commit. There’s still Chuck and Jian who can make commits. I do my best to keep up with them but can’t guarantee that it will always the be case. I was at the hospital with my wife so I’m sorry I wasn’t able to keep up when chuck made his commits.
-
Hi,
install subversion and get the trunk the right way…
[url]http://fogproject.org/forum/threads/ad-integration-on-new-fog-1-1-2.11128/#post-33016[/url]When a SVN checkout is finished it displays the SVN Version:
[IMG]http://i.imgur.com/WWduiVV.png[/IMG]Regards X23
-
You’re assuming I’ve installed it.
-
This is all updated.
-
[quote=“x23piracy, post: 33663, member: 3982”]Hi,
install subversion and get the trunk the right way…
[url]http://fogproject.org/forum/threads/ad-integration-on-new-fog-1-1-2.11128/#post-33016[/url]When a SVN checkout is finished it displays the SVN Version:
[IMG]http://i.imgur.com/WWduiVV.png[/IMG]Regards X23[/quote]
IIRC, I believe doing a ‘cd’ to the trunk directory and then typing ‘svn info’ will also show the revision.
-
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.
