We use an ajusted version of WebGUI in conjunction with our bookkeeping software Cash on our on-line shop.
It works quite well and we'll probably publish our changes to WebGUI on the dutch website about this beautifull Content Management System and Application Platform later this year.
It's a nice multi platform piece of software created by a company called SysV from Australia. It does backup based on md5 checksums, backing up only what has really changed.
Sounds interesting, 'Samba Experience'. Maybe I should even go there. But else there is not much news in this posting. There is an announcement and a call for papers. So, did anyone submit an abstract yet?
But still, once you find that your site crashes mozilla there must be something seriously wrong and you'd check why immediately. And if something like this (which I find surely deserves attention) does that I'd say it doesn't do good for PEAR.
I like WebGUI better since it is based on perl, well mod_perl actually. That and the fact that I know perl and don't know python.
WebGUI is built for end user usability and for letting the tech people get back to the tech part.
It is really feature rich and contains:
Flexible styling using built in macro's and HTML::Template.
Survey creation with no programming required (very cool!!)
Internationalisation (so you can get it in Dutch, German, Chinese, etc.)
Built in discussion method's
Built in calendar
Built in image gallery
Built in e-mail forms
There is also open support for WebGUI that can be found here.
Last time it was mentioned on/. the mysql daemon fell under the heavy load, but if you want to try it right now (and it's slashdotted) you can always go to sourceforge.
I own 3 samba books, which all help really much to help understand how samba works, but are no real help when it comes to actually implementing it. It still needs a lot of testing.
The 'for free' part is really great, but then again, I wouldn't have used it in the first place if it wasn't free. Oh and just for the record I am thankful.
I have contributed (more then once) to better documentation by supplying bug reports for the samba man pages but up till now I've been quite disappointed in the speed at which these get into the distribution. But hey, that was two years ago, things might have changed.
I've been using samba for over 5 years now in a large company with a mixed flavour unix and windows network environment.
When implementing samba I've always come across the same problems:
Unsufficient documentation available
E-mails for help to samba team members seem to get lost somewhere in/dev/null
Features that are reported to work don't and ones that are reported broken work perfectly
In the end it was always down to debug=999 in smb.conf and tcpdump. (But: I've implemented it on a solaris 2.6 sun cluster 2 machine supporting full failover capabilities and all.)
Once you find out what works and what doesn't you can use one version for years!
The article says: It's very easy to use Samba as a PDC. Simply enable a few options in the Samba configuration file, add users to the local Samba password database, and build machine accounts for each Windows NT machine on the network.
I find this at least peculiar.
When you have 500 users you are not simply going to 'add users to the local samba password database', especially not when you need to run samba on more that 4 machines simultaniously. One of the things I had to do to get this working was sniff all the passwords from the network (wasn't too hard, since we use unencrypted NIS, so all passwords travel the LAN in plain text) and then add them to the smbpasswd file with a specially manufactured perl script.
Also the 'simply enable a few options' isn't as simple as it seems, since even man smb.conf doesn't seem to have consequent answers for every switch you can set (and there are dozens of them).
Most of the features that this article is about have been around for a few years now and still haven't improved much.
I hope to see the day that installing and configuring samba for a medium to large corporation is really easy and clear. For now I'll just live with the kwirks.
Just for the record: I'm not saying samba is a bad product, it just needs a lot of better documentation and ease of use and installation for larger userbases.
Hi, this article seems a bit 'stale' to me. It states that samba is at 2.2.4 at the time of writing and according to my latest Freshmeat notification:
This email is to inform you of release '2.2.7' of 'Samba' through
freshmeat.net.
The changes in this release are as follows:
A security hole has been discovered in versions 2.2.2 through 2.2.6 of
Samba that could potentially allow an attacker to gain root access on
the target machine. The word "potentially" is used because there is
no known exploit of this bug, and the Samba Team itself has not been
able to craft one. In addition to addressing this security issue,
this release also includes thirteen unrelated improvements.
Years ago, Gerrit Hiddink (now doctor in Computer Sience) designed the World Wide Conferencing Protocol so he could build a World Wide Conferencing Network, designed for scalability, security and productivity.
It lacks 'bans' and 'kicks' but does allow for a group consented ignore.
It was far superior than IRC in 1994 and it still is, though everyone seems to stick with IRC. Then again there is something cool about being able to 'kick' someone.;)
I used to use e-safe and I've also used ZoneAlarm but with both these packages I experienced huge system instability over some time. The same goes for Cisco VPN software. It seems to me that anything you do to the Microsoft TCP stack makes it more instable. Guess that stack is 'part of the system that cannot be replaced' as of Windows XP?
You shouldn't forget that/. is also read by IP Lawyers. Therefore it is even a good place for such a question to ask since then Techies and Lawyers can share their points of view.
Ok, fine, but then please tell me how to determine the size of $some_large_number?
I'd much rather than putting a size-limit on my mail server automatically send an e-mail to the person who sent the large mail in the first place that says: 'You shouldn't do this, use ftp instead, here is a page on how to do it, URL.' That way people might actually learn the why.
To my opinion education is the only way your users will know what to do.
Putting a size limit on your e-mail server doesn't learn them anything exept that their e-mail administrator is a complete *ss (in their view).
E-mail size limits only help if you explain to your uses why they shouldn't send files by e-mail if there is another way and, how they should share documents. For example by providing a common storage place by http or ftp somewhere. These sharing tools however have to be just as simple as sending e-mail for people to use them.
Put simply, if you were the administrator of an e-mail server, what would you set the maximum size of an incoming email message to be, and what would be the reasoning behind said limit?
I would say $size_of_mail_disk divided by $number_of_users applied with a quotum. This would probably amount to something round and about 100MB.
My users would probably have a hell of a time actually getting this e-mail from the server, but I don't see the technical solution would help here. Users will simply use e-mail to transfer files simply because they can.
This going to be presented at a congress for the Netherlands Network User Group November 13th (a mostly Novell and Microsoft NT association).
I have been looking for a solution to mirror files between the two cluster nodes. SCSI is just too expensive for this, since low cost is one of the requirements. I've been trying to compile DRDB on my gentoo 1.3 systems but the 2.4 kernel isn't supported by the default DRDB distibution yet.
Does anyone know about any other projects like these that actually work?
I've heard about several 'put perl into HTML' tools now like ASP with perl and embperl but I never seem to like it.
I'm now actively involved in WebGUI (a content management system / application server) and we are looking for a templating system to allow for easy costumisation of the display our 'applications'
It just seems a lot more easy to embed HTML into perl than the other way round. Or maybe I should read this book?
I tend to think that Mason is trying to be php with the easy integration of all those nice perl modules. I'm not sure that is the best way.
Slashdot Mirror
- poll's
- discussion on anything
- user and group management
- builtin RSS feed reader
- keyword search builtin
- templateable everything (from page till user interface).
Try comparing it to Mambo or Typo3 using CMSMatrix while you are at it.if there where news it would probably be bad.
This is very good news.
:)
:)
I've been working with 5.3 beta 7 for the last few weeks. It is such a great system!
Perl 5.8.something is on there and even applications like WebGUI work like a charm.
I hope the official will be out soon.
I wouldn't be a bit surprised if the way this article describes the actions taken by Microsoft in court were true.
If Microsoft really 'plain lied' to the DoJ in the antitrust case, they might be 'really' convicted after all.
We use an ajusted version of WebGUI in conjunction with our bookkeeping software Cash on our on-line shop.
It works quite well and we'll probably publish our changes to WebGUI on the dutch website about this beautifull Content Management System and Application Platform later this year.
It's a nice multi platform piece of software created by a company called SysV from Australia.
It does backup based on md5 checksums, backing up only what has really changed.
We even use it to do internet backup (sorry, it's Dutch).
I just compiled the 2.6.0 kernel on my Woody system running on an centaurhauls processor (VIA C3) and it runs with no problems at all!
I even get the feeling it is faster (but perception helps a lot).
Sounds interesting, 'Samba Experience'. Maybe I should even go there. But else there is not much news in this posting. There is an announcement and a call for papers. So, did anyone submit an abstract yet?
But still, once you find that your site crashes mozilla there must be something seriously wrong and you'd check why immediately. And if something like this (which I find surely deserves attention) does that I'd say it doesn't do good for PEAR.
That site crashed my mozilla 1.3a instantly. And I didn't like PHP that much anyway.
Guess CPAN and Perl are here to stay.
I like WebGUI better since it is based on perl, well mod_perl actually. That and the fact that I know perl and don't know python.
WebGUI is built for end user usability and for letting the tech people get back to the tech part.
It is really feature rich and contains:
There is also open support for WebGUI that can be found here.
Last time it was mentioned on /. the mysql daemon fell under the heavy load, but if you want to try it right now (and it's slashdotted) you can always go to sourceforge.
And that is exactly what we are working on at WebGUI.nl.
You can of-course use Composite with mozilla on any platform with WebGUI.
I own 3 samba books, which all help really much to help understand how samba works, but are no real help when it comes to actually implementing it. It still needs a lot of testing.
The 'for free' part is really great, but then again, I wouldn't have used it in the first place if it wasn't free. Oh and just for the record I am thankful.
I have contributed (more then once) to better documentation by supplying bug reports for the samba man pages but up till now I've been quite disappointed in the speed at which these get into the distribution. But hey, that was two years ago, things might have changed.
I've been using samba for over 5 years now in a large company with a mixed flavour unix and windows network environment.
When implementing samba I've always come across the same problems:
The article says:
It's very easy to use Samba as a PDC. Simply enable a few options in the Samba configuration file, add users to the local Samba password database, and build machine accounts for each Windows NT machine on the network.
I find this at least peculiar.
When you have 500 users you are not simply going to 'add users to the local samba password database', especially not when you need to run samba on more that 4 machines simultaniously. One of the things I had to do to get this working was sniff all the passwords from the network (wasn't too hard, since we use unencrypted NIS, so all passwords travel the LAN in plain text) and then add them to the smbpasswd file with a specially manufactured perl script.
Also the 'simply enable a few options' isn't as simple as it seems, since even man smb.conf doesn't seem to have consequent answers for every switch you can set (and there are dozens of them).
Most of the features that this article is about have been around for a few years now and still haven't improved much.
I hope to see the day that installing and configuring samba for a medium to large corporation is really easy and clear. For now I'll just live with the kwirks.
Just for the record: I'm not saying samba is a bad product, it just needs a lot of better documentation and ease of use and installation for larger userbases.
Hi, this article seems a bit 'stale' to me. It states that samba is at 2.2.4 at the time of writing and according to my latest Freshmeat notification:
This email is to inform you of release '2.2.7' of 'Samba' through freshmeat.net.
The changes in this release are as follows:
A security hole has been discovered in versions 2.2.2 through 2.2.6 of Samba that could potentially allow an attacker to gain root access on the target machine. The word "potentially" is used because there is no known exploit of this bug, and the Samba Team itself has not been able to craft one. In addition to addressing this security issue, this release also includes thirteen unrelated improvements.
Years ago, Gerrit Hiddink (now doctor in Computer Sience) designed the World Wide Conferencing Protocol so he could build a World Wide Conferencing Network, designed for scalability, security and productivity.
It lacks 'bans' and 'kicks' but does allow for a group consented ignore.
It was far superior than IRC in 1994 and it still is, though everyone seems to stick with IRC. Then again there is something cool about being able to 'kick' someone. ;)
I used to use e-safe and I've also used ZoneAlarm but with both these packages I experienced huge system instability over some time. The same goes for Cisco VPN software. It seems to me that anything you do to the Microsoft TCP stack makes it more instable. Guess that stack is 'part of the system that cannot be replaced' as of Windows XP?
You shouldn't forget that /. is also read by IP Lawyers. Therefore it is even a good place for such a question to ask since then Techies and Lawyers can share their points of view.
Ok, fine, but then please tell me how to determine the size of $some_large_number?
I'd much rather than putting a size-limit on my mail server automatically send an e-mail to the person who sent the large mail in the first place that says: 'You shouldn't do this, use ftp instead, here is a page on how to do it, URL.' That way people might actually learn the why.
A little education goes a long way.
To my opinion education is the only way your users will know what to do.
Putting a size limit on your e-mail server doesn't learn them anything exept that their e-mail administrator is a complete *ss (in their view).
E-mail size limits only help if you explain to your uses why they shouldn't send files by e-mail if there is another way and, how they should share documents. For example by providing a common storage place by http or ftp somewhere. These sharing tools however have to be just as simple as sending e-mail for people to use them.
Put simply, if you were the administrator of an e-mail server, what would you set the maximum size of an incoming email message to be, and what would be the reasoning behind said limit?
I would say $size_of_mail_disk divided by $number_of_users applied with a quotum. This would probably amount to something round and about 100MB.
My users would probably have a hell of a time actually getting this e-mail from the server, but I don't see the technical solution would help here. Users will simply use e-mail to transfer files simply because they can.
I'm building a heartbeat cluster to serve WebGUI pages and files via samba.
This going to be presented at a congress for the Netherlands Network User Group November 13th (a mostly Novell and Microsoft NT association).
I have been looking for a solution to mirror files between the two cluster nodes. SCSI is just too expensive for this, since low cost is one of the requirements. I've been trying to compile DRDB on my gentoo 1.3 systems but the 2.4 kernel isn't supported by the default DRDB distibution yet.
Does anyone know about any other projects like these that actually work?
I currently have to implement a DotLRN (.lrn) site which is based on OpenACS.
But anyway, OpenACS is the reworked version of ACS (which stands for 'Asomething' Community System) that was written for Oracle and AOLserver.
OpenACS is written in TCL, specifically for PostgreSQL and AOLserver.
I don't like TCL that much, but at least it works
I've heard about several 'put perl into HTML' tools now like ASP with perl and embperl but I never seem to like it.
I'm now actively involved in WebGUI (a content management system / application server) and we are looking for a templating system to allow for easy costumisation of the display our 'applications'
It just seems a lot more easy to embed HTML into perl than the other way round. Or maybe I should read this book?
I tend to think that Mason is trying to be php with the easy integration of all those nice perl modules. I'm not sure that is the best way.