That’s probably because it didn’t recognize the architecture.
You could use
[LIST]
[]wget [URL=‘http://pkgs.repoforge.org/rpmforge-release/’]http://pkgs.repoforge.org/[/URL]htmldoc/htmldoc-1.8.27-2.el6.rf.x86_64.rpm
[]rpm -i htmldoc-1.8.27-2.el6.rf.x86_64[URL=‘http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm’].rpm[/URL]
[*]yum install htmldoc
[/LIST]
or just change the x86_64 to i686
Alright, I’ve been here long enough, can I get wiki access? I plan to do some extensive walkthroughs on installation/set up on various distributions of linux. I will do my best to keep current with the distributions.
it is a repository for HTMLdoc hosted and distributed by the Elrepo group.
alternatively, there are posts about the problem you are experiencing, pertaining specifically to CentOS, you can find SOME documentation (not much, it would be nice if someone familiar in CentOS would do a write up of full installation for noobs like we have with Ubuntu) here on the forums.
this works for CentOs 6.2 should work for 6.4 as well, this uses RPMforge instead of elrepo.
[LIST]
[]wget [url]http://pkgs.repoforge.org/rpmforge-release/[/url][URL=‘http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm’]rpmforge-release-0.5.3-1.el6.rf.x86_64.rpm[/URL]
[]rpm -i [URL=‘http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm’]rpmforge-release-0.5.3-1.el6.rf.x86_64.rpm[/URL]
[*]yum install htmldoc
[/LIST]
Glad you got it sorted, Open another thread and lets get started on your deployment issues 
There is a way to add the driver to the kernel.
You can try your hand at making a kernel, Ozzy has made a WONDERFUL walk through on the process.
Second post.
Glad you found it! And thanks for letting us know where the issue was!
[quote=“chad-bisd, post: 19665, member: 18”]Faster server disk subsystem usually equals faster unicast deployment to multiple clients. I use an old Dell server that has 5 disks in RAID5 array. I can image 15 clients at about 3GB per minute per client, or I can image over 30 tablets that only have 100Mbps interfaces, and get about 900 MiB per minute per client.
When I was using an old desktop with a single 7200 RPM SATA drive it in, imaging more than 2 clients at a time slowed everything down due to the non sequential disk read requests. RAID5 makes it better, as does a RAID controller with built in cache.[/quote]
Confirmed!!!
I have a FOG machine built out of some old hardware, I used a 7200 rpm disk in them. It images at a decent speed, I wouldn’t say it is slow, it is QUITE the improvement over our WDS choice.
I got a hold of a e-Server IBM machine with RAID5 10K rpm disks. I installed my ubuntu of choice and fog 0.33b and this sucker FLIES compared to my 0.32 server. I’ve also tried installing the Fog 0.32 on this server and it seems it is the hardware that has made the major improvement.
I had some trouble initially setting up the IBM eServer because of the raid control it uses, but once I removed the PCI card, things went swimmingly, not to divert too far from the subject here but I am still working to try to get the PCI card to work incase it has some kind of caching abilities. This use to be a Novell Netware server (which to my understanding is a Linux OS), so I am not sure what I need to do to get the sucker to work right but I’m not giving up yet!
there are other ways to dance around it, this would be the fastest method to make sure permissions don’t bite you in the @$$
you can manually create the images in your image store of the WEB Gui, this would create the SQL database entry for the image, then you can copy the contents of /images to the respective folders. this will create the folders with the proper permissions you just need to copy the physical file to its folder.
After you have the images “created”, you can re-associate your hosts to the fog server, and ultimately, the image.
Well then I am glad you got it sorted, in the future, it would be a good idea to try a few different platforms before posting.
Were you running into display issues on your fog server, or were you getting display errors when using a windows box?
I don’t have any issues with displaying content in the native FireFox browser. Have you ran the update on Ubuntu?
You need a different kernel then, just because your nic card works before “linux” boots doesn’t mean that “linux” is happy with the driver supplied.
To be more specific, you need to include your network card driver in the kernel.
Use CoffeeCup FTP to ftp into your machine, I find that it works better and you can change permissions directly from the app.
You can even SSH from it if you like.
Awesome, I would like to seem some alternatives!
I would even like to see using the cloning portion as a “add-on” so that other can choose the derivative they want to go with. I’ve seen some people talking about using the Bittorrent to transfer, this would be a BAD idea for my environment, we have HEAVY restrictions against the torrents, but It would be nice to have an alternative for those that aren’t locked down as heavily as I.
Keep up the good work Tom, so far my 0.33b server is working beautifully, I should probably update it though, I’m still on 98something !
Fogprep is no longer required. Some still use it but it’s not a necessity. Sysprep is a MUST with Windows 7 if you plan to activate against a KMS server. KMS requires each machine to have unique identifiers and sysprep cleans the system so each machine can do so.
I can not verify if the same is true for other activation methods.
It could be the command being sent, it sounds to me like a time delay. The reason I say this is because when a machine decides to PXE boot it first looks to the server for a file named by it’s MAC address, and a few others you can look up the order of operations on the wiki, and if it doesn’t find the file named by the MAC address, it continues down the line until it reaches the PXE boot file.
You could also set up WireShark to capture packets and see for certain the file is made at the proper time.
I would FIRST check my /tftpboot/tftpboot folder, make a note of the files in there. Technically there shouldn’t be any. Then I would create a task on the server and check the folder again, make sure the file is created, then I would boot the machine and see what it does. If it continues to load the OS, I would lad WireShark to see if the file is being passed to the client.
Glad you got it going! Good luck!
I would check settings for Wake on Lan capabilites, and verify that you have set up the BIOS for “Lan Option Rom” or something along those lines.
If I am understanding you correctly, The host is registerred to FOG. You tell the FOG Server to image the machine. you go to the machine and power it on, it will boot to the OS. If you let it boot and power the machine down and back on, then the machine will image?
Are you by chance setting a time for the start? Is your server time correct?
So if I am understanding this correctly, you set up a machine to upload/download from the web gui and the machine doesn’t image it just continues to boot the Operating System? Is that correct?
Have you set up the unit on the Web gui so that the FOG server knows it is a host?
Does the FOG PXE screen every display?
What version of Ubuntu did you set up FOG on?