in the archive U can find:
MulticastTask.calss.php
the /bin/fog (present in mi Image.gz)

[url=“/_imported_xf_attachments/0/412_Archive.zip?:”]Archive.zip[/url]

It’s already posted at the original link:

[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]

From personal experience in work… avoid Toshiba laptops like the plague. Cheap tacky, and if you want to get WoL working, forget it. Our department was budgeted a small amount to buy 300… they went with C660’s, MUCH to my dismay and expressed objections… we have other models too and they’re mostly all the same… AVOID!

Though its slightly aged have you gotten this figured out? I suppose a little research could be done but I think you could do:
apt-get build-dep build root
But don’t quote me as I don’t use Debian based OS.
If you need help I’ll try where I can.

It did take me a good few minutes to work out how to deploy multicast, I’ve not tried your changes but it does sound like an improvement. Maybe something that could be implemented in the new version.

Hi,

[quote=“Dageezah, post: 12358, member: 4267”]used DHCP server to export the names and MAC addresses…[/quote]

Thank you nice idea, will try this 🙂

Greetz X23

[quote=“Orphen, post: 12239, member: 2992”]Could you please post the code in order to add the option on my fog, since I have no knowledge at php. Thank you a lot![/quote]
please forget this message. I’ve figured out how to do that

I’ve successfully compiled a custom kernel image on Gentoo x64 but grub menù doesn’t seem to show up at boot . It is rumoured that freebsd-update command does not work well with custom kernel .

[url=http://spotlaan.se/sms-lan/]nya smslån[/url]

If you have DHCP running you can export the MAC addresses from there.

There is no mass upload built into FOG. It’s meant more for a mass deploy. That being said, it’s open source and can be modified to do whatever you want. Sorry.

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]