I will buy an iPad just for this app!

We’re looking into different solutions for managing the codebase and facilitating easier user contributions. But at the moment that’s on hold until 0.33 is released. After talking to the devs about this, the current solution is to either post patches here or use the Sourceforge project patch tracker.

@[URL=‘http://fogproject.org/forum/members/fernando-gietz.13/’][B][U]Fernando Gietz[/U][/B][/URL] well done thank u.

The short answer, maybe. FOG is currently built using Partimage. However, developers are looking to possibly move FOG over to Partclone. If Partclone is implemented, then you will be able to use Clonezilla easily to restore images since that’s what Clonezilla is built on.

Dell makes great business computers (I stress the business end end, not talking home PCs). Dell is also the only company to allow you to mass edit BIOs settings and other settings remotely. No other company has ever given that option. So if we wanted to change 2000 computers to boot to PXE first, with a flip of a switch we could. We have recently switched to Lenovo due to a big price difference when purchasing 300-600 PCs, as we do yearly.

Back on topic. I have a couple bugs to work out, then yes, I’ll post the files. 😉

No problem, glad it worked!

I have recently tried to image a virtual machine what was created under VMWare Workstation v9.0 on a Linux host. None of the available kernels worked and all reported that they could not find a hard disk.

lspci -k in the VM shows that the SCSI controller is a:

LSI Logic / Symbios Logic 53c1030 PIC-X Fusion-MPT Dual Ultra320 SCSI (rev 01)

With a kernel module “mptspi” in use.

I build a new kernel on another machine using:

CONFIG_FUSION=y
CONFIG_FUSION_SPI=y

and this kernel works fine with the VMWare Workstation v9.0 VMs that use the LSI Logic SCSI disk controller option.

Wondering what determines which SCSI controllers are chosen to be included in the FOG distribution kernels, and if just including all SCSI controllers would really make the kernel that much larger.

As I look at the core.config, I see that almost all the SCSI controller low-level devices are included.

I suspect that the Fusion MPT was simply missed because it is outside of the “SCSI device support” menu structure.

Fusion MPT device support is actually at the same level in the menu as “SCSI device support” and is only 4 menu items down from it. Also, Fusion MPT device support does not mention SCSI in the help until you drill down to the SPI, FC and SAS options.

Hope this helps to get Fusion MPT SPI support into an official kernel. 😉

Thanks!

you need to speak to microleaks, blackout or Chuck Syperski,

also how about getting it on to [url]http://www.turnkeylinux.org/[/url] this should help spread FOG even further they are also tied in with [url]http://www.proxmox.com/products/proxmox-ve[/url]

Sorry to necropost, but I came across this same issue with my PVE host and thought that others may find this thread via google (as I did) and I wanted to add my 2c.

FOG kernel support or a custom kernel are probably the ideal solutions, but a quick and dirty workaround is to remove the Virtio vHDD from the VM and reload the .raw file as IDE. Everything then works as expected! 🙂

Correct. It seems to have no problem with a system that has been sysprepped.

[quote=“Matthew Hood, post: 8958, member: 353”]I also have a Raid 5 with 6 drives but they are older drives, I would be in a lot of trouble if something happened and we lost data. We have over 30 images which as you know is a lot of man hours to recreate them. I know there is a backup script that comes with the previous versions of FOG is there one for .32?[/quote]

Maybe this would work, I modified the backup scripts a while ago, but YMMV

[url]http://sourceforge.net/tracker/?func=detail&aid=3449766&group_id=201099&atid=976201[/url]

Auto-answer 🙂
Source: [url]http://www.linuxquestions.org/questions/red-hat-31/increase-size-of-a-mounted-filesystem-459585/[/url]

[QUOTE]
what you want to do is create a new image, say existing one is initrd.img and we’ll call the new one init. To create an image with a max size of 50 megs

dd if=/dev/zero of=/init bs=1M count=50
mke2fs /init (answer yes to the question it asks)
mount -o loop /init_old /mnt/img
mount -o loop /init /mnt/img2
cp -Rp /mnt/img/* /mnt/img2
<now add whatever other files you want to /mnt/img2>
umount /mnt/img
umount /mnt/img2
gzip init

Now you have a new larger image as init. There are other ways to do it but this is by far the easiest/safest in my opinion (been doing it all day trying to install rhel as 2.1 to install on an unsupported SAS controller).
[/QUOTE]

We don’t have a release date for FOG 0.33 at this point. FOG 0.33 isn’t just a collection of bug fixes or feature updates, it’s a complete rewrite of the underlying code structure, so it’s not like we can say “feature X will have to wait until next time”. The standard response is “it’ll be released when it’s ready”.

I can find inactive accounts in AD, that’s simple. I need to find a relatively easy way to compare that to the inventory that FOG outputs. Then I will be able to tell which hosts I need to delete from FOG and/or AD.

As I said the easiest way would be for FOG to report when the last time hosts checked in which should be rather simple utilizing the FOG client.

1> As far as I know only the full disk wipe.
2> Check out Capone. [url]http://www.fogproject.org/wiki/index.php?title=Capone[/url]

Edit: Just thought, you might actually mean that you want to register the mac at the client computer. All you do in that case is choose quick or full registration from the PXE boot menu on the client PC

[quote=“djm79, post: 8006, member: 1568”]I’m trying to understand how the snapins work code wise. I’m wanting to try to implement a location based pull for the fog client much like the multi location patch. [/quote]

That sounds like a good project. I’d wait until 0.33 comes out, or just download that code on a spare machine and start working on it. 0.33 is unlikely to change dramatically before release (Right, Blackout?), but it is likely that whatever solution you find for 0.32 will need to be rewritten for 0.33.

Keep us updated on your efforts. If you get it working perhaps you can post a FAQ with your code.

–astrouga

You need to look into the way fog does it now. I believe it calls one of the scripts under {webdir}/fog/service/, passing in as POST arguments the information needed to create the task in the database and file under /tftpboot/pxelinux.cfg/

If you expand out the /tftpboot/fog/images/init.gz (instruction on wiki), and look into the /bin/fog folder, you’ll see the fog.man.reg file, which is what runs when you choose the Full Host registration and inventory from the PXE boot menu. If you can look through that file, you can see how the script is calling the page which creates the imaging task, and you can replicate that in whatever program you are wanting to interface with FOG.

one is based off of rhel the other ubuntu so it won’t be as easy as getting those images into the init/bzimage as both os’s handle splash/init a bit differently but I’ve taken apart init enough times and am fairly familiar with ubuntu so I think I should be able to marry the two without too much of a headache and in the end we can/will have a usb/cd bootable image that can come in handy aside from loading via pxe.