Latest FOG 0.33b

Tom Elliott

Sure.

warp

[quote=“Tom Elliott, post: 24602, member: 7271”]Sure.[/quote]
it works very well !!

warp

[quote=“Tom Elliott, post: 24602, member: 7271”]Sure.[/quote]
I have just one last problem : as I said the SYNOLOGY or IOMEGA put before their NFS shares a name like “[B]volume1[/B]” or “[B]nethdd[/B]” while sharing the same FTP did not !
For the same share on SYNOLOGY:NFS : /volume1/imagesFTP : /imagesThe problem after the backup operation when ftp_delete and ftp_rename.
So I added before line 57 in / var/www/html/fog/service/Post_Stage2.php
[CODE]
// SYNOLOGY —
if(stripos($dest, ‘volume1’) !==false){
$src = str_replace(“/volume1/”, “/”, $src);
$dest = str_replace(“/volume1/”, “/”, $dest);
// IOMEGA —
if(stripos($dest, ‘nethdd’) !==false){
$src = str_replace(“/nethdd/”, “/”, $src);
$dest = str_replace(“/nethdd/”, “/”, $dest); }
[/CODE]
And replaced the function delete($path) in /var/www/html/fog/lib/fog/FOGFTP.class.php because SYNOLOGY do not like the “[B]ftp_nlist[/B]” function but rather “[B]ftp_rawlist[/B] "
[CODE]
public function delete($path)
{
if (!(@ftp_delete($this->link, $path)||@ftp_rmdir($this->link,$path)))
{
$filelistraw = $this->ftp_nlist_Syno($this->link,$path);
$filelist = (array_keys($filelistraw));
if ($filelist[0]){
foreach($filelist AS $file)
{
$this->delete($path.”/".$file);
}
$this->delete($path);
}
}
// Return
return $this;
}

public function ftp_nlist_Syno($resource, $directory)
{
     if (is_array($children = @ftp_rawlist($resource, $directory))) { 
         $items = array(); 
         foreach ($children as $child) { 
             $chunks = preg_split("/\s+/", $child); 
             //$item['type'] = $chunks[0]{0} === 'd' ? 'directory' : 'file'; 
             array_splice($chunks, 0, 8); 
             $items[implode(" ", $chunks)] = $item; 
         } 
         return $items; 
     } 

     // Throw exception or return false < up to you 
}

[/CODE]

[COLOR=#3366ff]There he has a way to solve this problem ?[/COLOR]

[url=“/_imported_xf_attachments/0/610_Capture.JPG?:”]Capture.JPG[/url]

Tom Elliott

I didn’t design IOMEGA or SYNOLOGY NAS Systems. So it’s beyond me how and/or why you can’t use the true paths properly.

warp

The problem is the FTP step (rename and delete) why not just do these steps in NFS ?

Tom Elliott

So what’s wrong with the FTP Step? If I understood your previous post, FTP to those directories removes the /volume1/ label and sets the home to /volume1/ making the ftp step look at /images through relative means. I didn’t configure there FTP server, so I don’t know how to help. The reason for not doing it via NFS is because of permissions.

erod20

This post is deleted!

lepretre

Hello,

just for report:

blank page when i update an option in the service configuration page.(but the change is ok )
Apache Log:
PHP Fatal error: Call to a member function set() on a non-object in /var/www/fog/lib/pages/ServiceConfigurationPage.class.php on line 307

The fog FOGMulticastManager don’t start. I have to do chmod +x on the /opt/fog/service/FOGMulticastManager/FOGMulticastManager

Fog Rev :1377

I will try imaging this morning (french hours !!! )
Voila!!!

lepretre

Just a question:

how to for the FOG_KEY_SEQUENCE ?

Tom Elliott

r1378 released.

Should fix the service configuration page error reported above. A couple of minor fixes to Imaging Log report page.

@lepretre: Can you give more information about your question? Are you wondering what it is? How to use it? I don’t know.

lepretre

Thanks Tom
For the the FOG_KEY_SEQUENCE ?
What kind of key combination can I use?
Can I have an example of the parameter to write?

Olivier

Tom Elliott

It’s on the PXE Settings screen. It show’s the key combination that you would use to get to the menu. it’s only active when the Hidden Menu checkbox is checked.

Tom Elliott

r1383 released.

Moves Imaging Log to class file, for the time being it will display like normal, until I get all the default reports moved into the report class as their own objects, I’m leaving these files.

warp

[quote=“Tom Elliott, post: 24618, member: 7271”]So what’s wrong with the FTP Step? If I understood your previous post, FTP to those directories removes the /volume1/ label and sets the home to /volume1/ making the ftp step look at /images through relative means. I didn’t configure there FTP server, so I don’t know how to help. The reason for not doing it via NFS is because of permissions.[/quote]

Can we still correct code “[B]ftp_nlist[/B]” with a code “[B]ftp_rawlist[/B]” in “/var/www/html/fog/lib/fog FOGFTP.class.php” which seems to be more compatible with different NAS server?

Tom Elliott

What is the difference between nlist and rawlist?

What would happen if I just did basename to the path being sent? Would this, theoretically, work properly as the basename of /volumes1/images would be images and the basename of /images would also be images?

The only issue I see with using basename is for those file systems where you need the full path for things to work. I believe this is why nlist was used. It allows you to read the contents within a specified directory. I’m still under the impression that the NAS boxes just need to be configured so /volume1 is not where it plops you in for FTP. It should be relatively simple, though I don’t have a NAS to test with.

lepretre

Hy,

not working When i deploy image type “other” with multos windows + linux .(upload ok)
I try in debug deploy and nothing is done after update database:

Rev: 1378
[IMG]http://olivierlepretre.free.fr/CAM00110.jpg[/IMG]

Tom Elliott

@lepretre
I guess I’m confused? What do you mean nothing is done after the database is update?
Are you saying it doesn’t actually image the system? Are you saying it doesn’t reboot?

I’m guessing you’re saying it doesn’t actually deploy the image. I can try to take a look into that, but I don’t have a system to test with readily available, so I’m sorry if it’s a little delayed.

When you say image type, are you referring the “Single Disk (Resizable), Multi Part Single/All Disk (Non-Resizable), Raw” or the OS Type as “other”?

warp

[quote=“Tom Elliott, post: 24678, member: 7271”]What is the difference between nlist and rawlist?

What would happen if I just did basename to the path being sent? Would this, theoretically, work properly as the basename of /volumes1/images would be images and the basename of /images would also be images?

The only issue I see with using basename is for those file systems where you need the full path for things to work. I believe this is why nlist was used. It allows you to read the contents within a specified directory. I’m still under the impression that the NAS boxes just need to be configured so /volume1 is not where it plops you in for FTP. It should be relatively simple, though I don’t have a NAS to test with.[/quote]
I’m not strong enough in English to translate everything, but hey never mind, I will continue to change myself both programs.

Yet these modules certainly pose problems to other people as we speak in “FOGuserGuide-> Separate_NFS_Server” a rewrite these modules …
[url]http://www.fogproject.org/wiki/index.php?title=FOGUserGuide#Separate_NFS_Server[/url]

lepretre

Yes it doesn’t actually deploy the image and the task disappears from active task.
my image is Multi Part All Disk (Non-Resizable) and single too (I tried 2),and the os other

I’ll try again

sorry for my bad english :oops:

I’m not a hurry! you are already a lot to us!!

Vlad.R

Hello .

I am trying to install FOG 0.33 with dnsmasq .

Following this guide :

[QUOTE]Chainloading iPXE using dnsmasq setup
This information pertains to FOG 0.33 and the new iPXE boot method.
In order to continue to use dnsmasq to dole out ip addresses and to help find the boot file, some changes need to be made to force the boot file to load the iPXE boot file.
The old pxelinux.0 file is still included in the fog installation as pxelinux.0.old but this file has been replaced by a new file called [B]undionly.kpxe[/B]. We will use this file, undionly.kpxe, in place of the pxelinux.0 file when setting up the ltsp.conf file.
The reason we are able to do this is because pxe boot looks for files that match a query of names, first starting with the MAC address of the machine and moving down the list until it reaches the default file. We are going to create a file for it to find every time it queries for the default file.
[LIST=1]
[]Create a default file for undionly.kpxe to load (you may substitute gedit for your favorite text editor):
sudo mkdir pxelinux.cfg
cd pxelinux.cfg
sudo gedit default
[]Insert the following lines and edit the server ip address to reflect your own FOG server:
DEFAULT vesamenu.c32
LABEL fog
MENU DEFAULT
kernel ipxe.krn dhcp && chain [url]http://(fog-server-ip-address)/fog/service/ipxe/boot.php?mac=${net0/mac}[/url]
PROMPT 0
TIMEOUT 01
[*]Save your files and restart your dnsmasq service with the following command:
sudo service dnsmasq restart
[/LIST]
[/QUOTE]didn’t have any success in booting at all .

Then , I have renamed “pxelinux.0.old” in “pxelinux.0” , and now I can boot from PXE .
Now ,a client computer find “pxelinux.0” , load it, and then loads iPXE file.(i think)
How can I make use of [B]undionly.kpxe file ? [/B]In this workaround , I don’t think i am using it.

Latest FOG 0.33b

186

11.7k

17.2k

154.7k