Date: Mon, 12 Apr 2010 07:03:27 +0200 From: Egoitz Aurrekoetxea Aurre <egoitz@ramattack.net> To: freebsd-doc@freebsd.org Subject: Re: FreeBSD PXE installation howto Message-ID: <BDC6BAA3-190B-42B5-A16E-7DF548560AC5@ramattack.net> In-Reply-To: <4BC2A291.5020807@a1poweruser.com> References: <F79B7C55-2A17-4455-B0A3-679D74D87416@ramattack.net> <4BC2A291.5020807@a1poweruser.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi all, Erik when you specify there -DLOADER_TFTP_SUPPORT=3DYES this is a = directive for the preprocessor in the time it is looking wich source = code to compile... but it should be entered in cc line... not in make... = just do one check.... save the output of that make to a file and you = will see that nfs support is going to be used... check too the = makefiles... you will see that makefiles to enter the = -DLOADER_TFTP_SUPPORT they are checking if make variable = LOADER_TFTP_SUPPORT is initialized to something... you could perhaps = do...=20 export CPPFLAGS=3D"-DLOADER_TFTP_SUPPORT=3DYES"=20 make but not the way you said... and I won't do things this way too... just = use makefile for this kind of flags... as I say basically... make LOADER_TFTP_SUPPORT=3DYES try this and the way you set and you will see different output of make. The suggested parts to correct corrected... tftpd run from inetd is the same as base system really... so this is = done.... Fbsd1 I'll try to improve this aspects of the doc... yep perhaps I have = explained a little for me :)... Well if any developer could check too this howto, will be just fine :) Thankss a lot :) to all. bye!!! El 12/04/2010, a las 06:33, Fbsd1 escribi=F3: > Egoitz Aurrekoetxea Aurre wrote: > > Hi, > > > > I'm working on a project for setting up a freebsd installation = server > with pxe. > > When I started I see the doc was a bit old-fashioned. so I started > > looking at some blogs. freebsd doc that could help me understanding > > the whole process and so on. Finally I have ended looking at source > > code of some involved parts like sysintall, boot stages and so on = for > > understanding all properly for setting up this service. > > I have written a documentation that if you see it to be ok. (it = seems > > to be working fine) perhaps, would be nice to appear in handbook or > > in some official documentation site. So if you see something that > > should be done in another way, or some point which you consider is > > wrong, please make me know and I'll correct it. > > > > The url in which you could fetch the pdf file is : > > > > http://postfixquotareject.ramattack.net/freebsdpxehowto.pdf > > > > Thank you very much. > > > > > > >=20 >=20 > Thank you Egoitz for volunteering to write documentation for the = handbook. The following criticism is not meant in a negative way. >=20 > I can not evaluate the correctness of the technical procedure you = write about, but I am going to talk about your style of written = documentation. >=20 > What you have written is what I would call a personal short cut = outline of the steps you did. So next time you need to do the same thing = again you have something to follow and remind youself of what you did. = This only has value to you because you have in your head all the = understanding and background information of why you are doing these = steps. >=20 > When writhing documentation for the handbook you must keep in mind = that the reader has no idea what you are talking about. So your document = has to contain right at the beginning an explanation of what PBX is, how = you are using it, what other programs you are using and why. The general = rule is MORE details is better then LESS details. Explain what and why = for each step. >=20 > Know that the reader will execute every command just as you wrote = them, so test the sequence of commands to verify it's correct. This is a = very important step in writing documentation. It has to produce the = exact results you say it will. >=20 > Adding or replacing a section in the handbook takes a long time. Maybe = 1 or 2 RELEASE versions before it gets added. The documentation = department moves slowly. The technical stuff in the document is reviewed = by some of the developers for accuracy. >=20 > I know what I am talking about because I am the author of the handbook = Firewall section. I am willing to help and guide you through this = process. I suggest you put your document in Microsoft Word, add the = background information and step details talked about above, and then = attach it to an email for my review. >=20 > Let me know if you choose to proceed. >=20 > Joe >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BDC6BAA3-190B-42B5-A16E-7DF548560AC5>