[ previous ] [ next ] [ threads ]
 
 From:  "Alex M" <radiussupport at lrcommunications dot net>
 To:  "'Bernie O'Connor'" <Bernie dot OConnor at sas dot com>, "'Mono Dev List'" <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall-dev] Community development of 1.3a3
 Date:  Thu, 26 Oct 2006 13:43:41 -0400
"...it would probably be more than what people would need" - it's never
enough until it's too late to fix the outcome ;-)

I'm lazy windows person VS2005 has automated version tracing system so if
that  CVS server will work by itself and do its work then good, otherwise I
thing its not essential in dev image (at least for me).

So when do you think you can compile the dev image?
 

-----Original Message-----
From: Bernie O'Connor [mailto:Bernie dot OConnor at sas dot com] 
Sent: Thursday, October 26, 2006 1:20 PM
To: Alex M
Subject: RE: [m0n0wall-dev] Community development of 1.3a3

Svn server is like a cvs server.  Gcc would be part of the development
server.  Scripting and  access to it would probably be more than what people
would need.

-----Original Message-----
From: Alex M [mailto:radiussupport at lrcommunications dot net] 
Sent: Thursday, October 26, 2006 11:57 AM
To: Bernie O'Connor; 'Marten'; 'Mono Dev List'
Subject: RE: [m0n0wall-dev] Community development of 1.3a3

Yes if mono would have SHH option (Dev image only, otherwise it's less
secure) that would be great so that I can edit files with WinSCP3.

Also if I need GCC to compile C++ files for the LCD project fro WRAP. 

As to SVN server I don't really know what it does? And apache, I don't know
really why I might need it?

Finally since I never got IDE for mono to work I would assume it has the
script to build the release image that could be installed on either wrap or
PC 

So if such image would be available I can do integration in nono too, I
don't really care if its mono or pfsense, they both to similar tasks and
since I do php mostly the code would be identical or similar.

As to the mirrors to store dev images I can donate 2 servers w/ 10 Gb/mo
bandwidth on each. Connection speed 100Mbps (disk space 1Gig, can do more
but gotta check what I have there)






-----Original Message-----
From: Bernie O'Connor [mailto:Bernie dot OConnor at sas dot com]
Sent: Thursday, October 26, 2006 9:46 AM
To: Alex M; info at martenvijn dot nl
Subject: RE: [m0n0wall-dev] Community development of 1.3a3

I think Alex meant qemu (open source virtual machine).  So Alex, if m0n0wall
had an ssh client built-in would you be more active in m0n0wall development
or are you satisfied with how pfsense is going?

bernie

-----Original Message-----
From: Alex M [mailto:radiussupport at lrcommunications dot net]
Sent: Wednesday, October 25, 2006 6:58 PM
To: info at martenvijn dot nl; 'Mono Dev List'
Subject: RE: [m0n0wall-dev] Community development of 1.3a3

I havent been follow this topic but im one of those who tries to do the PHP
development but im not really the linux or bsd person so I decided to do my
scripts now under pfSense since I cn get into pfsense with SHH without
having headache setting up QUE which I hate

So far my current projects (as posted im pfsense forum) are:
1. Radius auto discovery
2. Auto NAS registration
3. NAS status system (wasn't planed but apparently I wrote the code another
weekend)
4. LCD for WRAP (Hardware should be out in coming month, but im stuck with
drivers etc.)



-----Original Message-----
From: Marten [mailto:wleiden at xs4all dot nl]
Sent: Wednesday, October 25, 2006 6:08 PM
To: m0n0wall dash dev at lists dot m0n0 dot ch
Subject: Re: [m0n0wall-dev] Community development of 1.3a3

On Wed, 2006-10-25 at 13:53 -0400, Bernie O'Connor wrote:
> All,
>
> I've had a short off-list email exchange with Lee about m0n0wall
development and I thought it might be useful to email the development list
for feedback.  This idea is a little rough, but bear with me (and keep in
mind that I'm a beginner subversion user).  I also realize Manuel has
commented on changing the future architecture for m0n0wall, but here goes...
>
> Problem:  improve community development process for m0n0wall
>
> One of the requests that occurs frequently on the list is help in
setting up a development environment from non-FreeBSD expert users (I do not
consider myself a FreeBSD expert).  Granted, depending on what changes are
being requested, FreeBSD expertise may be required, but for functional
enhancements to the gui, mostly PHP programming expertise is needed.  PHP
programmers are not always systems administrators nor are systems
administrators always PHP programmers.  Pulling together both types of
programmers into the m0n0wall development environment would be helpful.  The
m0n0wall development community has responded in different ways to address
these needs (sources under subversion, various image extraction/creation
tools, binary utilties/packages).
> *****
> Quick proposal (and request for comments/feedback):

if you (we) need a freebsd playground this might help:

1. - freebsd 7.0 (current) image for wrap/soekris with onboard a svn client
It build with tinybsd build script that's easily usage for 5.x 6.x freebsd.
For 7.x is small patch available.

I use it for personal use but it free (bsd license).

it has:
- serial console
- ssh/scp/rsync
- wireless
- nics
- usb support ( umass ucom uplcom)

You can write to cf/disk like monowall.


But you can put any kernel into in if needed.

https://svn.wifisoft.org/node/trunk/base.img

if needed custom images / kernel can be easily made


2. These you checkout or export to the flashdrive
- apache2 (perl/php)
- pen
- asterisk
- sudo
- kismet
- mtr
- dhcp

https://svn.wifisoft.org/node/trunk/pkgs/

ofcourse you can build up your own svn to have your own packages


3. there is some basic documentation.

https://svn.wifisoft.org/node/doc/


4. be gentle to this svn, it just behind a home dsl line.....


just my 2ct


kind regards,

Marten



---------------------------------------------------------------------
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


---------------------------------------------------------------------
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