the default size for jumbo frames is 9000. So you send 1/6th the number of packets, less headers and tail relative to the amount of data being sent. The real saving is the time it takes to get on the cable, as you’re transmitting a 1/6 of the number of frames for the same data, you save on the time to transmit. you also do 1/6th the number of mac checks, so it lowers CPU usage, unless you have a TCPIP off load card.

Always enable it with iSCSI, but check the “path” all support jumbo frames.

Hope it helps

the idea of the darkcoin miner was to provide a way for people to, as a purely voluntary option, generate darkcoins while imaging tasks are taking place and donate them to the fogproject. it runs exclusively on the clients being imaged, nothing is run on the server. the miner is run on the kernel sent over the network to clients.

probably not (1.1) maybe, but that miner is not active by default.

After years of storing photos on disks, I’ve started looking into subscribing to a cloud storage service to back up my photos. However, I recently saw a service called CloudBacko ([url]http://free.cloudbacko.com/?r=1d[/url]) that offers huge amounts of cloud storage.

thanks

FOG does not image or track Mobile devices. Nor does it really track desktops/laptops either.

I guess we need more info as to what you’re trying to ask.

Are you asking for “location setting (location plugin) from mobile?”

It worked, thank you very much.

Well, if mono can compile it, and compile it for Linux, that might be a “ready to go” situation (where .NET is used “properly” as a multi-platform framework, lol ?), avoiding more development… but it’d rather be working without a web black box, again so as to make sure we can be reasonnably certain there is no dependency on closed source (or un-runnable) things 😉
The only “rich man” concern would then be, will we allow a mono dependency on linux just to run this, but I know I would if it meant no need to worry about it 😉

Network boot does work from the local drive on the server.

It fails to work from the iSCSI drive though. We’ve copied, and confirmed the permissions, confirmed the drive settings Master and active etc.

It continually times out at TFTP. swapping the master drive back to the internal hard drive, imaging works. (within the fog storage node administration)

Thanks a lot for your support TOM.

I will test and let you know.

Thanks
Siva

it sounds to me like this might need the same fix that is used for hyper-v virtual machines, disabling certain console features loaded in the ipxe boot menu

Somewhat like that, but organized in such a way that FOG can automatically inject the correct drivers into the firstboot process. If I were to use the Driverpacks, I’d need to build a database linking device IDs to folder structure, and that complicates the script significantly.

I did it for memtest 5.01 and it works.

:MENU
menu
item --gap – ---------------- iPXE boot menu ----------------
item MEMTESTEFI MemTestEFI
:MEMTEST
kernel [url]http://{ip}/fog/service/ipxe/memtest/EFI/BOOT/BOOTX64.EFI[/url]
boot

Now, I have to do it for WINPE

[url]http://fogproject.org/forum/threads/ipxe-boot-menu-password-protected.11499/#post-35630[/url]

Its all about keywords 😉

Now…need to learn to UPLOAD an image in the same manner.

[CODE]
:MENU
menu
item --gap Please Select one of the images below
item fog.local Boot from hard disk
item img1 COOLNAME
item return Return to main menu
choose --default fog.local target && goto ${target}

:fog.local
sanboot --no-describe --drive 0x80 || goto MENU

:img1
kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=MY.IP web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=MYIMAGE.NAME ftp=${fog-ip} imgType=n osid=7 storage=${fog-ip}:/images capone=1 imgFormat=2
imgfetch init.xz
boot || goto MENU

:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || goto MENU
autoboot[/CODE]

if you wont give information, it’s harder to help you.

different solutions for different environments, but unless you know the why… things don’t always make sense.

Also, you might look through the Wikipedia/Wikimedia tutorial on editing articles and using Transclusion to reduce data duplication. I think that’s still what they call it. We really need a wikipedia team of super documenting super heroes!