Requests for Wiki Access <--- ASK HERE

[noktis]

Hey there,

I’m a bit new to the deeper parts of Linux (and loving it more every day), but have a pretty strong Windows imaging background. An associate suggested that I check this out, and I think it’s a fan-freaking-tastic idea. However, I saw that some of the information regarding Sysprep needed some help on the wiki, and wanted to offer to take care of that for you. From the notes on the Wiki, this appears to be the place to request that. Thanks!

[Sebastian Roth]

@bobsobol You are more than welcome to add to the wiki whatever you can. There is no one around the FOG team who knows everything (except maybe Tom! ) and it’s not necessary. I myself have learned so much by joining in and getting to know things step by step. @Wayne-Workman will add an account for you soon I am sure.

[bobsobol]

Sorry for the bump. I’m posting in response to the following suggestion:-

@sebastian-roth said in Error 500 after update to mySQL 5.7.19:

Thanks a lot for pointing out the missing command in the wiki page. We’ll fix it. You mind doing it while I don’t have access @Wayne-Workman? As well I would like to point out that you can request access to the wiki yourself here. It would be great to have more people from the community involved in updating the forum. There is lots to do and all help is highly appreciated!

I’m not sure how much time I can contribute, and I’m sure that whatever it is, it’s not as much as you deserve.

I’ve seen a few places in the wiki which are ambiguous. Not wrong, usually, just not clear what they are saying. Sometimes I know what they mean, (I’m fairly good with Linux, Windows, Mac, partitioning, boot sequences etc.) but it reads like they’re saying otherwise. Certainly, I can help clear that up. Sometimes I don’t know what they should be saying, (I’m less practiced with SQL, and much less skilled with php and Apache) and it’s only through breaking something that I learn the true meaning of the wiki. I’d certainly like to avoid others falling into that same trap.

Thanks for your consideration.

[Wayne Workman]

@aharrison I messaged you, top right in the talk bubble.

[aharrison]

Just requesting wiki access because I wanted to put my results in the Working Hardware page.

[THEMCV]

Wiki access would be nice to update as I go along on my quest to become a FOG master.

[Ben4485]

Hi,
I wrote a instruction on how to install FOG on MS Windows. Could you please give me a Wiki access, so that I can post it there.
Chears
Ben

[Wayne Workman]

@zefanja Account created.

[zefanja]

Hi, I am requesting access to the wiki to add/update informations!
Thanks!

[Wayne Workman]

@iyoung said:

to be honest, I didn’t expect such a quick response.

That’s how we roll around here.

And understand I’m just trying to figure out why you need this option but I don’t.

Are you in total control of your network equipment? Do you have iphelpers set?

[iyoung]

@Wayne-Workman I have a 2008r2 Domain controler that acts as the DHCP server as well and I have options 66 and 67 set as it shows on guide. My FOG is on Ubuntu 15.04. When my workstations go into network boot, they send out discovery packets but don’t get any packets in response. Looking into it, I found that DHCP option 60 needs to be enabled. I was going to test it on my server here before editing the wiki and to be honest, I didn’t expect such a quick response. I’ll make a post in the correct area of the forum if I need anything farther.

[Wayne Workman]

@iyoung Can you explain more about your environment? I ask because I only run Windows DHCP at work and I do not have option 060 set, but network booting works fine here. Other sites in my organization also work fine with just Windows DHCP and options 066 and 067 set. So I’m wondering what it is that your environment needs option 060 for.

[iyoung]

@iyoung said:

@Wayne-Workman This article only mentions option 66 and 67, but on Windows Server you also need to enable option 60 through netsh to turn on the PXEClient.

And the User Guide as well.

[iyoung]

@Wayne-Workman This article only mentions option 66 and 67, but on Windows Server you also need to enable option 60 through netsh to turn on the PXEClient.

[Wayne Workman]

@iyoung Which DHCP article are you looking at?

[iyoung]

HI,

I am requesting access to the Wiki to change the steps on how to step up Windows DHCP to work with FOG. I am also testing FOG on the latest versions of Debian, Ubuntu and Fedora to see which I like best and I will report here on my finds, when I have free time(hehe) to do so.

[FlowLive]

Hi, I am requesting access to the wiki to add information as I am deploying fog on Debian.

Thanks!

[cbemerine]

Hi,

I am requesting Wiki access to contribute as I get our company’s site up and running with the Fog Client.

[mauirixxx]

This post is deleted!

[Wayne Workman]

@mauirixxx By all means, go ahead. There are actually two articles on CentOS7.
https://wiki.fogproject.org/wiki/index.php/Installation_on_CentOS_7_x64_Full_Guide
https://wiki.fogproject.org/wiki/index.php/Installation_on_CentOS_7

I know for a fact that CentOS 7 is the very best option for FOG Trunk right now. (and I’m a Fedora kinda Guy)

I will also tell you that the instructions for CentOS 7 are even shorter than the instructions in the Fedora 21 Server article - but use almost exactly the same commands, less in fact.