DevelopersBootStrapAndDevIso Guide Missing



  • hi

    i just wanted to try to build a 2.1 or 2.1.1 and was looking for the "DevelopersBootStrapAndDevIso" guide,

    The old link doesnt show anymore the guide, where to find the guide now ?

    The old link : http://devwiki.pfsense.org/DevelopersBootStrapAndDevIso

    thanks



  • Public access to the tools repo has been removed, so (re)-building yourself is not possible.  Nor is it possible to test your own developments, see what modifications ESF has done to FreeBSD code or build your own packages (even for package authors).  Read the past few months of forum and ML archives for more detail; there is quite a bit of discontent in the community, and effectively silence from ESF.



  • @charliem:

    Public access to the tools repo has been removed, so (re)-building yourself is not possible.  Nor is it possible to test your own developments, see what modifications ESF has done to FreeBSD code or build your own packages (even for package authors).  Read the past few months of forum and ML archives for more detail; there is quite a bit of discontent in the community, and effectively silence from ESF.

    • access to the tools has been restored

    • access to the source code was never impacted, so it was always possible to "see what modifications ESF has done"

    • you'll get farther with me by engaging with less BS



  • What was there was bad to begin with. devwiki had degraded to the point of near uselessness, which is why it no longer exists. You can find a cache in Google or archive.org I'm sure if you want dated info. Nothing's changed drastically since those instructions, they're just inadequate as they've always been.

    As for updated info, we're weighing our options there currently, but we'll have something available at some point.



  • To make Chris' point more clear, we were just discussing this last night.

    My desire is to make a 'developing with pfSense' e-book.



  • @gonzopancho:

    • access to the tools has been restored

    • access to the source code was never impacted, so it was always possible to "see what modifications ESF has done"

    • you'll get farther with me by engaging with less BS

    Note that he specifically said "public access" and "modifications […] to the FreeBSD code." Based on your statements elsewhere on this board, the pfsense-tools repo continues to be unavailable to anyone except those who were explicitly granted access by ESF, and the modifications to the FreeBSD base system live in pfsense-tools/patches. Is this not the case?



  • the -tools repo won't be accessible to anyone who doesn't sign (click through) the agreements.

    violate the agreements (once agreed to), and I will seek to pull your access.

    I remain uninterested in engaging in the debate you seek.



  • I'm not sure what debate it is you think I'm seeking; that was my first post on this thread. I was merely supporting charliem's claim that any modifications applied to the underlying FreeBSD base system have not been visible to the general public since -tools got pulled. I recently started another thread specifically because I was unable to find how exactly the pf sources used in 2.1.2-RELEASE differ from the version shipped in FreeBSD 8.3-RELEASE-p15.



  • I believe I've documented (in another thread) how to gain access to the -tools repo.



  • This statement of yours, specifically, is what I was referring to:

    @gonzopancho:

    • access to the tools has been restored

    • access to the source code was never impacted, so it was always possible to "see what modifications ESF has done"

    • you'll get farther with me by engaging with less BS

    As mentioned before, the modifications to the FreeBSD code live in the pfsense-tools repo, which – as you're obviously well aware -- was unavailable to outside developers for a while. So I don't think it's fair to call that particular claim of charliem's "BS."


  • Banned

    @gonzopancho:

    I believe I've documented (in another thread) how to gain access to the -tools repo.

    Wow… you "documented" it by posting a messy howto burried in the middle of some random thread on this forum. This is incredibly "useful" way of documenting source code access for a project that screams to be PROVEN OPEN SOURCE in huge letters right on its website. You dude are such an incredible fail that it is extremely hard to believe. Why just you don't crawl back into your office and let the professional employees handle things?



  • @gonzopancho:

    @charliem:

    Public access to the tools repo has been removed, so (re)-building yourself is not possible.  Nor is it possible to test your own developments, see what modifications ESF has done to FreeBSD code or build your own packages (even for package authors).  Read the past few months of forum and ML archives for more detail; there is quite a bit of discontent in the community, and effectively silence from ESF.

    • access to the tools has been restored

    • access to the source code was never impacted, so it was always possible to "see what modifications ESF has done"

    • you'll get farther with me by engaging with less BS

    I stand by my original statements; if you have, since then, moved toward restoring tools access, that's great.

    pfSense repository has been available, but code changes from FreeBSD were not available as they are in the tools repo.  I hope this is not news to you.

    I have no wish to engage you, I'm just a concerned user, trying to fill in another who was unaware of the recent changes in your development model and policies.



  • So now that access to the tools have been restored, what about the dev wiki and this guide?



  • as Chris said, they were out of date.  After the work on -tools in April, they would be way out of date.



  • I'm quite new to pfSense development so I don't now how it used to work.
    I understand that the dev wiki was obsolete, but I just find it rather extreme to take the whole thing down without the possibility for the dev community to update it.

    Or maybe, seeing the reduced activity on this forum, the problem is that the dev community is rather reduced and therefore updating and keeping a dev wiki up to date was illusory?
    Maybe that was your motivation for a dev e-book.



  • @gonzopancho:

    as Chris said, they were out of date.

    I'm pretty sure he was asking about a suitable, up-to-date replacement, which (paywall or otherwise) is still missing AFAIK.



  • @charliem:

    I'm pretty sure he was asking about a suitable, up-to-date replacement, which (paywall or otherwise) is still missing AFAIK.

    Indeed, or at least a place to eventually restart one.