[ previous ] [ next ] [ threads ]
 
 From:  Stefan Frank <Mono dot Developer at RootServices dot Biz>
 To:  Manuel Kasper <mk at neon1 dot net>, MonoWall-Developers List <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall-dev] Re: [m0n0wall] Looking for some version explanations ( OS/Patches/GUI )
 Date:  Sun, 19 Mar 2006 05:24:47 +0100
Manuel Kasper schrieb:
> [taking this to m0n0wall-dev since it really doesn't belong on the
> general mailing list]
>
> On 15.03.06 01:57 +0100, Stefan Frank wrote:
>
>   
>> The Developers Handbook mostly points to files/scripts
>> at http://m0n0.ch/wall/downloads which should be used
>> to create a own environment to create images from scratch.
>>
>> Is this Link only as archive or will it be updated from time
>> to time? I know that there is a SVN Repository available.
>>     
>
> It will be updated as necessary. The current version of the
> developers' handbook explains how to use SVN to get the latest
> version of phpconf and the webGUI. The idea is to fetch other files
> needed for building images (kernel configs, patches etc.) from the
> repository as well. As you've discovered, the "build" folder in trunk
> already contains most of what's needed, so the developer's handbook
> could be changed if somebody gets the chance.
>   
Thats what i mean - its misleading that the developer's handbook points for
needed files/scripts/patches http://m0n0.ch/wall/downloads/freebsd-4.11/
for example and not from the repository tree too.
>   
>> Can the webGUI from the latest trunk be used on 4.11?
>>     
>
> Yes.
>
>   
>> Will it be considered that the latest/trunk webGUI works
>> with FreeBSD 4.11 without trouble?
>>     
>
> Yes, as long as we don't actually move to something else.
>   
Do you tend to change to something else?
>   
>> Whats about the idea to add checks in the webGUI that
>> prove the running OS and disable/hide features that are
>> not possible (for example if its not supported by the
>> old Kernel?) That will be fine for me imho ;)
>>     
>
> I'd prefer not to start mixing up operating system and webGUI/phpconf
> versions. There are too many dependencies and it's just not worth the
> effort. When/if we move to FreeBSD 6.0, trunk will be copied to a new
> maintenance branch, then all the files in trunk will be modified as
> necessary.
>   
Well i used 4.x a long time ... all 5.x and the 6.0-BETA Releases let
servers/clients
reboot for unknown reason each day. The 6.0-RELEASE works very fine now and
i upgraded them to FreeBSD 6.0-RELEASE. If m0n0wall still works with 4.11R
and i dont miss any features then i will keep the old kernel ;)
>   
>> In the SVN Repository is a "build" folder in /trunk/ but
>> in /tags/release-1.21/ is no "build" folder. Has this any
>> reason? How should users be able to check for changes
>> in the older/stable versions of monowall?
>>     
>
> Tags are *never* changed. Changes may only be committed to branches
> or the trunk. The build folder was introduced after 1.21 was tagged.
> The next tagged version (probably 1.22) will have one as well.
>   
Just to understand it correctly ... the files (patches/kernel.conf ect)
in /trunk/build/
are for FreeBSD 6.0 ? Or still for FreeBSD 4.11 ? I thought the whole
time that
the files in /trunk/build/ are for FreeBSD 6.0-RELEASE. What is correct?
>   
>> If possible then it will be nice if somebody add the files
>> related to monowall 1.2.x brunch in /tags/release-1.21/
>>     
>
> No, if anybody commits to a tag directory they'll have their SVN
> commit access revoked. ;)
>   
I didnt asked to make any changes on /tags/release-1.21/ - just and ONLY to
add the patches,scripts and conf files to this folder. BUT if
/trunk/build/ still
keep the Files for FreeBSD 4.11 then it explain everything.

The mix between the download links in the developer's handbook and the
new repository make it not really clear to understand (for my self).

> - Manuel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash dev dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash dev dash help at lists dot m0n0 dot ch
>
>
>   
-- 
Best regards,
Stefan Frank

Looking for Monowall Adjustment?
http://M0n0WaLL.RootServices.Biz