Re: network with two gateways and one network card
Please don't crosspost. Am 15.12.2011 um 19:43 schrieb Jack Raats: I have a question. Perhaps soeone can point me to a solution. I have a server running FreeBSD 7.4-STABLE with one network card running ezjail My network has two gateways. The host is running as 10.10.10.10 netmask 255.255.255.0 with gateway 10.10.10.1 The jail must be running 192.168.178.10 netmask 255.255.255.0 with gateway 192.168.178.1 Is this possible? How to do it?? What kind of problems to expect? Look at kernel option ROUTETABLES and setfib(1). If you're adventurous, check out VIMAGE. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Atheros 9285 - not operating?
This is getting less and less funny as I get deeper in this. I tried a lower end model of the same laptop with 8.1 and 8.2 and completely failed to get the atheros 9285 to work (although I did have partial success building from head (9) on 8.1. Wouldn't work after that. Along came 9.0-RC3 and I thought I had it made: the bsdinstall setup the card on a new laptop with wpa and all. After some days of work, left the unit alone for a while and the network went down. Error was bb hang detected (0x4) resetting. Tried a few things to get it to work, and failed. Rebooted, and still nothing. Firstly, when I first set it up I set it standalone. After the install I've setup lagg failover (done that many times before). I plug in UTP and it comes good, dhcp an address and ping- good, unplug and ping- no good. ifconfig wlan0 scan shows my bssid and others in the area. The others are on different channels with six degrees separation. This is not the only unit with this to happen either. The problem is identical on another brand of laptop with this card installed using 9.0-RC3. Dmesg does not show any error that could be responsible. It only show the inital detection of the hardware, although one message shows up right after detection that may be of note: [ath] AR9285E_20 detected; using XE TX gain tables. The only thing I can conclude with the circumstances of the error (in both units) is that the card is timing out somehow and not waking up properly. I can't see any sysctl setting that would change this though. Any help appreciated. Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Perl Upgrade And Mailscanner Woes
Almost every time there is a perl upgrade, it manages to break Mailscanner even after running perl-after-upgrade. The solution ends up being a reinstall of Mailscanner, but this is a real pain, because you have to delete and reinstall every dependent perl package used by Mailscanner. Does anyone have a better way? -- --- Tim Daneliuk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Perl Upgrade And Mailscanner Woes
On 12/21/2011 03:59 PM, Tim Daneliuk wrote: Almost every time there is a perl upgrade, it manages to break Mailscanner even after running perl-after-upgrade. The solution ends up being a reinstall of Mailscanner, but this is a real pain, because you have to delete and reinstall every dependent perl package used by Mailscanner. Does anyone have a better way? Hi After a major perl upgrade? portmaster -r perl- portmaster p5- portupgrade -fr perl Disclaimer: http://www.ose.nl/email ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Perl Upgrade And Mailscanner Woes
On 21/12/2011 14:59, Tim Daneliuk wrote:
Almost every time there is a perl upgrade, it manages to break
Mailscanner even after running perl-after-upgrade. The solution
ends up being a reinstall of Mailscanner, but this is a real pain,
because you have to delete and reinstall every dependent perl
package used by Mailscanner.
Something is going wrong with your upgrade process. If you're doing a
minor version upgrade of perl (eg. from 5.x.y to 5.x.y+1), then almost
all perl modules (including XS) only need to be moved into the new
${LOCALBASE}/lib/perl5/site-perl/5.x.y+1 directory tree, which is
basically what perl-after-upgrade does.
A few packages which embed a perl interpreter would need recompiling,
but you could count those on the fingers of one hand.
Are you sure you are using perl-after-upgrade correctly? You do
understand that just running:
# perl-after-upgrade
doesn't actually modify anything on disk: instead it shows you what
needs to be done. To actually effect the change you need to run:
# perl-after-upgrade -f
Then rebuild and reinstall any packages it says need rebuilding.
If it has worked properly then almost all of the contents of
${LOCALBASE}/lib/perl5/site-perl/5.x.y will be gone, and that whole
directory tree should be able to be deleted without consequence.
Of course if your update is from perl 5.x.y to 5.x+1.z then you really
do need to recompile and reinstall all perl modules and anything else
that depends on perl. perl-after-upgrade is not effective in this case.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: Perl Upgrade And Mailscanner Woes
On 12/21/2011 09:28 AM, Matthew Seaman wrote:
On 21/12/2011 14:59, Tim Daneliuk wrote:
Almost every time there is a perl upgrade, it manages to break
Mailscanner even after running perl-after-upgrade. The solution
ends up being a reinstall of Mailscanner, but this is a real pain,
because you have to delete and reinstall every dependent perl
package used by Mailscanner.
Something is going wrong with your upgrade process. If you're doing a
minor version upgrade of perl (eg. from 5.x.y to 5.x.y+1), then almost
all perl modules (including XS) only need to be moved into the new
${LOCALBASE}/lib/perl5/site-perl/5.x.y+1 directory tree, which is
basically what perl-after-upgrade does.
A few packages which embed a perl interpreter would need recompiling,
but you could count those on the fingers of one hand.
Are you sure you are using perl-after-upgrade correctly? You do
understand that just running:
# perl-after-upgrade
doesn't actually modify anything on disk: instead it shows you what
needs to be done. To actually effect the change you need to run:
# perl-after-upgrade -f
Aha! And the lights go on ... Nevermind.
Slinks away in shame ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Perl Upgrade And Mailscanner Woes
Tim Daneliuk writes: Are you sure you are using perl-after-upgrade correctly? You do understand that just running: # perl-after-upgrade doesn't actually modify anything on disk: instead it shows you what needs to be done. To actually effect the change you need to run: # perl-after-upgrade -f Aha! And the lights go on ... Nevermind. No, not nevermind. While this seems like upgrading for dummies, there are enough of them out there waves this _really_ needs to go in the upgrade message. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
DMA problems with Broadcom 4312 under FreeBSD 9.0-RC3
I have a Broadcom BCM4312 LP PHY that is giving me a hard time. I installed FreeBSD 9.0-RC3 a few days ago and it was working just fine. Here is the card info: Dec 21 13:06:12 apeiron kernel: siba_bwn0: Broadcom BCM4312 802.11b/g Wireless mem 0xf6cfc000-0xf6cf irq 17 at device 0.0 on pci12 Dec 21 13:06:12 apeiron kernel: bwn0 on siba_bwn0 Dec 21 13:06:12 apeiron kernel: bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (manuf 0x17f ver 0x2062 rev 2) Dec 21 13:06:12 apeiron kernel: bwn0: DMA (64 bits) Dec 21 13:06:12 apeiron kernel: bwn0: Using 1 MSI messages Dec 21 13:06:12 apeiron kernel: wlan0: Ethernet address: 00:24:2b:b0:d6:a4 As I said, it used to work perfectly fine with the usual setup: if_bwn_load=YES wlan_ccmp_load=YES wlan_tkip_load=YES bwn_v4_lp_ucode_load=YES firmware_load=YES wlans_bwn0=wlan0 ifconfig_wlan0=WPA DHCP However, a few hours ago it started failing ocassionally, and now it fails almost all the time. The error message is: Dec 21 13:16:42 apeiron kernel: bwn0: Fatal DMA error: 0x800 0 0 0 0 0 Dec 21 13:16:42 apeiron kernel: bwn0: HW reset: DMA error Dec 21 13:16:42 apeiron kernel: bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) Dec 21 13:16:42 apeiron kernel: bwn0: Fatal DMA error: 0x400 0 0 0 0 0 Dec 21 13:16:42 apeiron kernel: bwn0: HW reset: DMA error Dec 21 13:16:42 apeiron kernel: bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) .. Dec 21 13:16:44 apeiron kernel: bwn0: Fatal DMA error: 0x400 0x400 0 0 0 0 Dec 21 13:16:44 apeiron kernel: bwn0: HW reset: DMA error Dec 21 13:16:44 apeiron kernel: bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) Dec 21 13:16:44 apeiron kernel: bwn0: Fatal DMA error: 0x400 0 0 0 0 0 Dec 21 13:16:44 apeiron kernel: bwn0: HW reset: DMA error Dec 21 13:16:44 apeiron kernel: bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) .. Dec 21 13:16:55 apeiron kernel: bwn0: Fatal DMA error: 0x400 0 0 0 0 0 Dec 21 13:16:55 apeiron kernel: bwn0: HW reset: DMA error Dec 21 13:16:55 apeiron kernel: bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) .. Any ideas? Best, Ramiro ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
two TOTALLY diff questions.
the first one is a bit off topic because our vim and the vim on linux may differ. but does anybody know how to get rid of the file and file~ OR, pref, turn the file~ into file.bak? i thought there was a areadme in .vimrc, but i don't see it. #2 q is out in the ozone. years ago i remember playing a game with black and brown rectangle, ovals, some vertical, some horizonttal. 16 way to win. i played it about 20 times and won only 2 or 3 times. i dont like games, but there is something about this one. i thought it was ; nope.. anybody? tx -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.57a release of Jottings: http://jottings.thought.org Twenty-five years of service to the Unix community. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: two TOTALLY diff questions.
* Gary Kline kl...@thought.org [2011-12-21 19:54 -0500]: the first one is a bit off topic because our vim and the vim on linux may differ. but does anybody know how to get rid of the file and file~ OR, pref, turn the file~ into file.bak? i thought there was a areadme in .vimrc, but i don't see it. Check out :help backupext while in vim. I learned something new by finding this out, so thanks! #2 q is out in the ozone. No idea on this one. ;) Regards, -- dave [ please don't CC me ] pgp9OZPHsbWoD.pgp Description: PGP signature
Revision control advice
Hello list, I apologize for this posting being not-much-on-topic, but my other resources have come to naught and I think you folks may have some experience in this area. I'm looking to set up some sort of revision control system at work. Simple enough, except that our situation is approximately the reverse of what most revision control systems are designed for. Unlike, e.g., FreeBSD kernel development, we have dozens or hundreds of small, rapid-fire projects that are created at the rate of 3 to 20 per month. They last a few days or a few months and are (usually) not developed afterward. Each project has one to three developers working on it, sometimes simultaneously. Usually it's one guy per project. Since my programmers are not necessarily UNIX-savvy, I'd like to deploy a web interface for them which will allow them to create new repositories (projects) as well as the normal checkin, checkout, etc. I want to set this up once, and from there on have the programmers deal with managing their own repos. And heaven forfend exposing them to the horrors of the shell. I've built a test server (9.0-RC3, amd64) for experimenting with this stuff. So far I've installed and played with: - fossil. I like the simplicity and light weight, but it doesn't seem to allow creation of new repos at all (let alone multiple ones) from the web interface, and the documentation is meager. I've pretty much given up on it. - subversion, which looks like the heavy hitter of RCSs, but it's not at all clear to me how to handle the multiple-project scenario. Still working on it. - git looks promising, but I have not installed it yet. If anyone can point me to a tool that might be suitable, I would be most grateful. -- Chris Hill ch...@monochrome.org ** [ Busy Expunging / ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Revision control advice
On 12/22/11 11:37, Chris Hill wrote: Hello list, I apologize for this posting being not-much-on-topic, but my other resources have come to naught and I think you folks may have some experience in this area. I'm looking to set up some sort of revision control system at work. Simple enough, except that our situation is approximately the reverse of what most revision control systems are designed for. Unlike, e.g., FreeBSD kernel development, we have dozens or hundreds of small, rapid-fire projects that are created at the rate of 3 to 20 per month. They last a few days or a few months and are (usually) not developed afterward. Each project has one to three developers working on it, sometimes simultaneously. Usually it's one guy per project. Since my programmers are not necessarily UNIX-savvy, I'd like to deploy a web interface for them which will allow them to create new repositories (projects) as well as the normal checkin, checkout, etc. I want to set this up once, and from there on have the programmers deal with managing their own repos. And heaven forfend exposing them to the horrors of the shell. I've built a test server (9.0-RC3, amd64) for experimenting with this stuff. So far I've installed and played with: - fossil. I like the simplicity and light weight, but it doesn't seem to allow creation of new repos at all (let alone multiple ones) from the web interface, and the documentation is meager. I've pretty much given up on it. - subversion, which looks like the heavy hitter of RCSs, but it's not at all clear to me how to handle the multiple-project scenario. Still working on it. - git looks promising, but I have not installed it yet. If anyone can point me to a tool that might be suitable, I would be most grateful. I'd suggest subversion. It allows individual files to be versioned, you can setup a webdav interface, and there are other tools that can help maintain it. Forget the individual repositories. Setup a single repository and have directories for each project. in each directory you can then setup trunk, branches, whatever, as per best practices in the Book. Designate a person or two to administer, and use directory level auth, or another alternative I haven't thought of. My 2c's anyway. HTH ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Revision control advice
On Wed, Dec 21, 2011 at 7:49 PM, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: On 12/22/11 11:37, Chris Hill wrote: Hello list, I apologize for this posting being not-much-on-topic, but my other resources have come to naught and I think you folks may have some experience in this area. I'm looking to set up some sort of revision control system at work. Simple enough, except that our situation is approximately the reverse of what most revision control systems are designed for. Unlike, e.g., FreeBSD kernel development, we have dozens or hundreds of small, rapid-fire projects that are created at the rate of 3 to 20 per month. They last a few days or a few months and are (usually) not developed afterward. Each project has one to three developers working on it, sometimes simultaneously. Usually it's one guy per project. Since my programmers are not necessarily UNIX-savvy, I'd like to deploy a web interface for them which will allow them to create new repositories (projects) as well as the normal checkin, checkout, etc. I want to set this up once, and from there on have the programmers deal with managing their own repos. And heaven forfend exposing them to the horrors of the shell. I've built a test server (9.0-RC3, amd64) for experimenting with this stuff. So far I've installed and played with: - fossil. I like the simplicity and light weight, but it doesn't seem to allow creation of new repos at all (let alone multiple ones) from the web interface, and the documentation is meager. I've pretty much given up on it. - subversion, which looks like the heavy hitter of RCSs, but it's not at all clear to me how to handle the multiple-project scenario. Still working on it. - git looks promising, but I have not installed it yet. If anyone can point me to a tool that might be suitable, I would be most grateful. I'd suggest subversion. It allows individual files to be versioned, you can setup a webdav interface, and there are other tools that can help maintain it. Forget the individual repositories. Setup a single repository and have directories for each project. in each directory you can then setup trunk, branches, whatever, as per best practices in the Book. Designate a person or two to administer, and use directory level auth, or another alternative I haven't thought of. My 2c's anyway. HTH ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Yeah I would second what Mr Rock says. Set up a single repo where folders can be used for projects. Since svn lets you checkout sub folders of a repo, each developer can check out the folder that corresponds to their project. Also, Tortoise svn is a very nice graphical utility that will allow your developers to manage there svn folders without even needing a web interface (most non unix people that I know like tortoise), so there is less maintenance for you :) Finally, kudos to moving towards using version control, its an important step for a software company. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Revision control advice
On Wed, Dec 21, 2011 at 10:24 PM, ss griffon ssgriffonu...@gmail.com wrote: On Wed, Dec 21, 2011 at 7:49 PM, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: On 12/22/11 11:37, Chris Hill wrote: Hello list, I apologize for this posting being not-much-on-topic, but my other resources have come to naught and I think you folks may have some experience in this area. I'm looking to set up some sort of revision control system at work. Simple enough, except that our situation is approximately the reverse of what most revision control systems are designed for. Unlike, e.g., FreeBSD kernel development, we have dozens or hundreds of small, rapid-fire projects that are created at the rate of 3 to 20 per month. They last a few days or a few months and are (usually) not developed afterward. Each project has one to three developers working on it, sometimes simultaneously. Usually it's one guy per project. Since my programmers are not necessarily UNIX-savvy, I'd like to deploy a web interface for them which will allow them to create new repositories (projects) as well as the normal checkin, checkout, etc. I want to set this up once, and from there on have the programmers deal with managing their own repos. And heaven forfend exposing them to the horrors of the shell. I've built a test server (9.0-RC3, amd64) for experimenting with this stuff. So far I've installed and played with: - fossil. I like the simplicity and light weight, but it doesn't seem to allow creation of new repos at all (let alone multiple ones) from the web interface, and the documentation is meager. I've pretty much given up on it. - subversion, which looks like the heavy hitter of RCSs, but it's not at all clear to me how to handle the multiple-project scenario. Still working on it. - git looks promising, but I have not installed it yet. If anyone can point me to a tool that might be suitable, I would be most grateful. I'd suggest subversion. It allows individual files to be versioned, you can setup a webdav interface, and there are other tools that can help maintain it. Forget the individual repositories. Setup a single repository and have directories for each project. in each directory you can then setup trunk, branches, whatever, as per best practices in the Book. Designate a person or two to administer, and use directory level auth, or another alternative I haven't thought of. My 2c's anyway. HTH ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Yeah I would second what Mr Rock says. Set up a single repo where folders can be used for projects. Since svn lets you checkout sub folders of a repo, each developer can check out the folder that corresponds to their project. Also, Tortoise svn is a very nice graphical utility that will allow your developers to manage there svn folders without even needing a web interface (most non unix people that I know like tortoise), so there is less maintenance for you :) Finally, kudos to moving towards using version control, its an important step for a software company. git or mercurial - best choices ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: two TOTALLY diff questions.
On Wed, Dec 21, 2011 at 08:19:05PM -0500, David J. Weller-Fahy wrote: Date: Wed, 21 Dec 2011 20:19:05 -0500 From: David J. Weller-Fahy dave-lists-freebsd-questi...@weller-fahy.com Subject: Re: two TOTALLY diff questions. To: freebsd-questions@freebsd.org Mail-Followup-To: freebsd-questions@freebsd.org * Gary Kline kl...@thought.org [2011-12-21 19:54 -0500]: the first one is a bit off topic because our vim and the vim on linux may differ. but does anybody know how to get rid of the file and file~ OR, pref, turn the file~ into file.bak? i thought there was a areadme in .vimrc, but i don't see it. Check out :help backupext while in vim. I learned something new by finding this out, so thanks! well, i'm a bit too dim to have =ever= thought of that helpNAME;so thanks. i don't keep my file.bak files very long but it's nice to have them... just in case to fmess up. hmm, maybe .Bak or whatever? 'bex', right? so : bex BAK [?] I'LL Try it #2 q is out in the ozone. No idea on this one. ;) rats. i dont like games, but this was next to murder even at the Very, very beginner level. anybody e lse? i dont know how to google this one up! gary ps: thanks el mucho. Regards, -- dave [ please don't CC me ] -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.57a release of Jottings: http://jottings.thought.org Twenty-five years of service to the Unix community. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Pysycache errors on run
Just something for the kids, but I'm wondering how to get this to work?
I've installed from ports, but when I run it from the cli to test it I
get an error:
Traceback (most recent call last):
File /usr/local/bin/pysycache.py, line 442, in module
if __name__ == '__main__': main(const.GWithFullScreen)
File /usr/local/bin/pysycache.py, line 266, in main
myrep = os.path.join(const.GRepPysycache,
'/usr/local/share/pysycache/help', const.GMyLocale )
File /usr/local/lib/python2.7/posixpath.py, line 66, in join
if b.startswith('/'):
AttributeError: 'NoneType' object has no attribute 'startswith'
Assuming this _does_ actually work, anyone know the trick to getting
this work?
Cheers
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Revision control advice
On 22 December 2011 15:07, Outback Dingo outbackdi...@gmail.com wrote: On Wed, Dec 21, 2011 at 10:24 PM, ss griffon ssgriffonu...@gmail.com wrote: On Wed, Dec 21, 2011 at 7:49 PM, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: On 12/22/11 11:37, Chris Hill wrote: Hello list, I apologize for this posting being not-much-on-topic, but my other resources have come to naught and I think you folks may have some experience in this area. I'm looking to set up some sort of revision control system at work. Simple enough, except that our situation is approximately the reverse of what most revision control systems are designed for. Unlike, e.g., FreeBSD kernel development, we have dozens or hundreds of small, rapid-fire projects that are created at the rate of 3 to 20 per month. They last a few days or a few months and are (usually) not developed afterward. Each project has one to three developers working on it, sometimes simultaneously. Usually it's one guy per project. Since my programmers are not necessarily UNIX-savvy, I'd like to deploy a web interface for them which will allow them to create new repositories (projects) as well as the normal checkin, checkout, etc. I want to set this up once, and from there on have the programmers deal with managing their own repos. And heaven forfend exposing them to the horrors of the shell. I've built a test server (9.0-RC3, amd64) for experimenting with this stuff. So far I've installed and played with: - fossil. I like the simplicity and light weight, but it doesn't seem to allow creation of new repos at all (let alone multiple ones) from the web interface, and the documentation is meager. I've pretty much given up on it. - subversion, which looks like the heavy hitter of RCSs, but it's not at all clear to me how to handle the multiple-project scenario. Still working on it. - git looks promising, but I have not installed it yet. If anyone can point me to a tool that might be suitable, I would be most grateful. I'd suggest subversion. It allows individual files to be versioned, you can setup a webdav interface, and there are other tools that can help maintain it. Forget the individual repositories. Setup a single repository and have directories for each project. in each directory you can then setup trunk, branches, whatever, as per best practices in the Book. Designate a person or two to administer, and use directory level auth, or another alternative I haven't thought of. My 2c's anyway. HTH ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Yeah I would second what Mr Rock says. Set up a single repo where folders can be used for projects. Since svn lets you checkout sub folders of a repo, each developer can check out the folder that corresponds to their project. Also, Tortoise svn is a very nice graphical utility that will allow your developers to manage there svn folders without even needing a web interface (most non unix people that I know like tortoise), so there is less maintenance for you :) Finally, kudos to moving towards using version control, its an important step for a software company. git or mercurial - best choices For what reasons? Rob -- Idiot : A member of a large and powerful tribe whose influence in human affairs has always been dominant and controlling. (Ambrose Bierce - The Devils Dictionary) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
