Thanks for information , but I want to update the clamscan in the client side.
Posts made by Fernando Gietz
-
RE: Clamav version update
-
RE: FOG 0.33 Requirements
Hi,
BryceZ, the problem is only with monopartition resizeble images? -
RE: FOG 0.33 Requirements
We use FOG to deploy our images in the university. We have more 40 centers (faculties, high schooles, …), 270 IT rooms and 6300 computers and 60 diferents users. Until now we have used REMBO as clone solution, and most of our images are monolitic (one IT room, one hardware, one software => one image). Change the work philosophy is very dificult and slow
-
RE: FOG 0.33 Requirements
We don’t use sysprep :(.
We manage 230 images, and is impossible use sysprep in all images.
And this requirement will be a big problem for us. -
RE: FOG 0.33 Requirements
Ummmm… But the problem is the new structure of W7_SP1 and higher or the clone engine (partimage)?
-
RE: FOG 0.33 Requirements
And which is the problem?
FOG 0.32 can clone W7 without problems, no? -
FOG 0.33 Requirements
Hi,
I see in the SVN r898 the changelog.txt the next note:[QUOTE]Version 0.33
*Operating system was moved from the Host object to the Image object. All images created on previous versions will need to be updated!
*IP Address has been removed from the hosts section.
*Fixed issue with 2TB+ (with 4K sectors) devices not being able to be imaged
*Init.gz is now based on 2011.08
*Added support for Windows 8
*NOTE: FOG now requires the use of syspref with Window 7 sp1 and higher[/QUOTE]The use of sysprep will be a requirement or optional?
-
RE: Bugs in FOG 0.33
Ummm… If you need clone a ext4 partitions, you can do a RAW or dd image. This way is slower than a normal way.
-
Clamav version update
Hi,
How can I update the clamav version?
The version of clamav in init.gz is 0.96 and is obsolete. When you run a antivirus task appears a warning: "Version OUTDATED!!! ".
The release version of clamav is 0.97.6. -
RE: Change initrd size
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 megsdd 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 initNow 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] -
Change initrd size
Hi,
Often I make changes in the init.gz, usually in the /bin/fog script. But now I need add a few new libraries, and I can’t do it; because I don’t have free space.
When I mount the init in one local directory, the size of the mount directory is 36MB, used 35 MB and only 937 KB of free space. I need add some new libraries, and I need 7 MB more. How can i add more space in the initrd?
-
RE: BUG: clamAV antivirus error
The problem isn’t the kernel, is my customized init.gz. I try init.gz of 0.33 beta version and works fine.
-
RE: BUG: clamAV antivirus error
Well. I am using a fog 0.32 customized version (i don’t make any change in fog.av script). And I try with diferent version of kernel: Kernel-3.2.4.core and Kernel-linux-3.6.9.core.
-
RE: Integrate Windows Authentication in FOG
I glad
We use a fog 0.30 customized version :oops: But the LDAP validation, I think that is easy to migrate to a new version of FOG.
The “site” layer and technician rol, is much more difficult. Sorry.
I just started the migration of code from the old version to the new FOG version. -
RE: Integrate Windows Authentication in FOG
We use a LDAP validation to access to FOG webui, but firstly the username have been created in the FOG database.
Each user have his rol. We use one fog server to deploy images, and we have 60 diferent users. Also, we have created a new rol in fog webui and a new “administration” layer. This layer is “site”, one "site " is a building or a high school or a faculty.
FOG have two rol: site manager and fast deploy. We have a new one: technician. We can link one user with one rol, and one user is linked to one or more sites.The site manager rol can see the fog server setup and all computers/clients. The technician only can see the computers and the images from his linked site, he can’t see the server setup.
-
RE: Keeping hostname when imaging
I surrender
I don’t know where is the problem.
You can make ping to the server, you can get a response from the server in a navigator (you don’t obtain a forbidden response)
But the FOG client says that he can’t connect to the server, the access is forbidden.
I don’t understand nothing :mad: -
RE: Keeping hostname when imaging
And the config.ini in the client?
The server address is right in config.ini? -
RE: Keeping hostname when imaging
Ok
you can make ping to the server. But can you see the webui from the client?
Open a navigator and try the next direction:
[I]10.1.1.252/fog/service/hostname.php?mac=XX:XX:XX:XX:XX:XX[/I]
Where XX:XX:XX:XX:XX:XX is the mac addreess.
What response the server?In my servet the response is like this:
[I]#!ok=U103666 #AD=0 #ADDom= #ADOU= #ADUser= #ADPass=[/I] -
RE: Keeping hostname when imaging
Are you sure that you don’t have firewall?
[CODE]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destinationChain FORWARD (policy ACCEPT)
target prot opt source destinationChain OUTPUT (policy ACCEPT)
target prot opt source destination[/CODE]You can do a ping from client to the server?
You can see a pretty info in /var/log/httpd/access_log, like this:
[CODE]10.227.15.30 - - [03/Dec/2012:16:19:16 +0100] “GET /fog/service/servicemodule-active.php?mac=18:03:73:1B:62:DC%7C08:00:27:00:B0:3F&moduleid=ho
stnamechanger HTTP/1.1” 200 4 “-” “-”
10.227.15.30 - - [03/Dec/2012:16:19:16 +0100] “GET /fog/service/hostname.php?mac=18:03:73:1B:62:DC%7C08:00:27:00:B0:3F HTTP/1.1” 200 51 “-” "-
"[/CODE]