Re: [Samba] oplocks and samba 2.2.7
On Tue, 2002-12-17 at 23:49, Keith G. Murphy wrote: Simo Sorce wrote: Samba 2.2.3a has been realeased on february the 6th, they are 10 (ten) months !!! And 2.2.7a contains *lot* of bugfixes that will make also woody users a lot more happy. Simo. Well, there is this: http://www.perrier.eu.org/debian/index.html.en I just noticed it, linked to by this: http://www.apt-get.org/ Cannot vouch for these unofficial packages, of course. :-) Unfortunately there is no access there: http://www.perrier.eu.org/samba-debian/ Forbidden You don't have permission to access /samba-debian/ on this server. However I'm going to build team packages for debian. Simo. -- Simo Sorce- [EMAIL PROTECTED] Samba Team- http://www.samba.org Italian Site - http://samba.xsec.it -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
On Wed, 2002-12-18 at 17:02, Keith G. Murphy wrote: To get it, you need to put this line into your /etc/sources.list: deb http://www.perrier.eu.org/samba-debian stable main Of course you need, but if you do not have access to the directory it is really difficult apt-get will have either (and it does not have infact) !! Then run apt-get update. apt-get install samba --simulate will show you what the installation *would* do then. Been there, done that. Simo. -- Simo Sorce- [EMAIL PROTECTED] Samba Team- http://www.samba.org Italian Site - http://samba.xsec.it -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
Simo Sorce wrote: On Wed, 2002-12-18 at 17:02, Keith G. Murphy wrote: To get it, you need to put this line into your /etc/sources.list: deb http://www.perrier.eu.org/samba-debian stable main Of course you need, but if you do not have access to the directory it is really difficult apt-get will have either (and it does not have infact) !! Well, I do not have access to it through the browser, but apt-get works with that line just fine. I think you should try it again. Use the *exact* line I showed above. I just tested it and it works. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
Simo Sorce wrote: Samba 2.2.3a has been realeased on february the 6th, they are 10 (ten) months !!! And 2.2.7a contains *lot* of bugfixes that will make also woody users a lot more happy. Simo. Well, there is this: http://www.perrier.eu.org/debian/index.html.en I just noticed it, linked to by this: http://www.apt-get.org/ Cannot vouch for these unofficial packages, of course. :-) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
begin Simo Sorce quote on Sat, Dec 14, 2002 at 12:15:21AM +0100: You got me wrong, I'm perfectly fine with debian, and use it with much joy. I do know debian only vaguely, just I see that sometimes it is really very slow, 10 months is really a lot of time without an upgrade. I'm ok with good scrutiny, but it seem that samba has been forgotten this time :-) But it's _really_ easy to rebuild samba from source for Debian if you want a newer version... the debian packaging, with instructions, is available in the .tar.gz. I do it all the time. I figure that the stability of Debian just allows me to worry about the actual problems on my network/systems, instead of playing the we must perform an upgrade dance all the time. M msg10876/pgp0.pgp Description: PGP signature
Re: [Samba] oplocks and samba 2.2.7
Hi all, I really know you'll tell me it is not an issue from Samba nor a matter of topic in this list. But. I have problems with oplocks, surely because of my version: Version 2.2.3a-12 for Debian I noticed it all in bug 26128 and posted here precisions, few days ago. Version 2.2.3a-12!!!??? YES, this is the *stable* version from Debian. What would I do? Install newer version (2.2.7,afaik), then corrupt my system? Or wait for Samba team to put 2.2.7 in the stable? For example, in current proposed-updates, samba version proposed is 2.2.3a-12!! I think I'll have to wait a year before 2.2.7 becomes stable, then you'll be supporting only version 2.4 ? :-) I really know again it is *not* the problem of Samba team. But, I think when I read docs always install newest version before asking to support, you put to rubbish all users who havent yet connexion to internet, or ones who just buy brand new RH, Mandrake, Suse, whatever, box, with surely not the latest Samba version in :-( What are my solutions then? Build my own deb package from your cvs? Thats what I'm gonna do finally, corrupting a bit my stable production debian server :-/ I'd really like you give your point of view on this. Thanks a lot for your efforts! -- Jean-Paul ARGUDO -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
On Fri, 2002-12-13 at 09:48, Jean-Paul ARGUDO wrote: Hi all, I really know you'll tell me it is not an issue from Samba nor a matter of topic in this list. But. I have problems with oplocks, surely because of my version: Version 2.2.3a-12 for Debian I noticed it all in bug 26128 and posted here precisions, few days ago. Version 2.2.3a-12!!!??? YES, this is the *stable* version from Debian. And it may contain lot of fixes that are in newer samba releases. I'm not saying they do, but I've seen a number of vendors that fixes packages but maintain older version to keep dependencies toward other packeags or such. What would I do? Install newer version (2.2.7,afaik), then corrupt my system? Or wait for Samba team to put 2.2.7 in the stable? with 2.2.7a you will not corrupt your system, however it seem strange debian does not upgrade to 2.2.7a as from 2.2.2-2.2.6 there a possible security problem, have you the security team url in your apt source list? For example, in current proposed-updates, samba version proposed is 2.2.3a-12!! I think I'll have to wait a year before 2.2.7 becomes stable, then you'll be supporting only version 2.4 ? :-) I really know again it is *not* the problem of Samba team. Not it is not. But, I think when I read docs always install newest version before asking to support, you put to rubbish all users who havent yet connexion to internet, or ones who just buy brand new RH, Mandrake, Suse, whatever, box, with surely not the latest Samba version in :-( Well if we know a problem is probably fixed in a later version, what can we do? We cannot do anything else that asking to upgrade to check it is not something else. What are my solutions then? Build my own deb package from your cvs? Thats what I'm gonna do finally, corrupting a bit my stable production debian server :-/ you do not need to build them out of cvs, we release packages in tar format, and you should really use them, cvs *may* contain new errors as we may be committing in steps a fix or something else while you cvs update and you do not notice. I'd really like you give your point of view on this. I generally use what the distribution provides. But if necessary I also install my custom packages (and I always build packages, as that way I have a trace in my system of what I've done exactly. To my customers I installed things like: samba-2.2.7pre2-xsec1.rpm/deb (Xsec is my company and pre2 never existed, I made it as I needed a special fix that was only in cvs). Thanks a lot for your efforts! Thank you, Simo. -- Simo Sorce- [EMAIL PROTECTED] Samba Team- http://www.samba.org Italian Site - http://samba.xsec.it -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
On Fri, 13 Dec 2002, Jean-Paul ARGUDO wrote: JP, Your question is one many samba users have to deal with. Debian Linux is user supported software, so if you want samba to always be up to date, volunteer to become the samba maintainer for Debian, then you will control you own destiny. If becoming the samba maintainer for Debian does not suit you, that's OK. But now if you want an up to date version of samba for Debian you will need to build your own. If building you own does not suit you, then you could hire a consultant )or find another volunteer) to do it for you. If, like most of us, you want someone to give you an update package as soon as a new version comes out, then find a source that will do that. The choice is yours. At one time, for every release of Samba I would compile and make available 10 for 10 different platforms. That took me nearly 4 days to build, QA, release - all unpaid work. I am not after sympathy, just want to make the point that it takes a lot of work and effort to serve our users fully. The more people who help the easier it is. Cheers, John T. Hi all, I really know you'll tell me it is not an issue from Samba nor a matter of topic in this list. But. I have problems with oplocks, surely because of my version: Version 2.2.3a-12 for Debian I noticed it all in bug 26128 and posted here precisions, few days ago. Version 2.2.3a-12!!!??? YES, this is the *stable* version from Debian. What would I do? Install newer version (2.2.7,afaik), then corrupt my system? Or wait for Samba team to put 2.2.7 in the stable? For example, in current proposed-updates, samba version proposed is 2.2.3a-12!! I think I'll have to wait a year before 2.2.7 becomes stable, then you'll be supporting only version 2.4 ? :-) I really know again it is *not* the problem of Samba team. But, I think when I read docs always install newest version before asking to support, you put to rubbish all users who havent yet connexion to internet, or ones who just buy brand new RH, Mandrake, Suse, whatever, box, with surely not the latest Samba version in :-( What are my solutions then? Build my own deb package from your cvs? Thats what I'm gonna do finally, corrupting a bit my stable production debian server :-/ I'd really like you give your point of view on this. Thanks a lot for your efforts! -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 13 Dec 2002, John H Terpstra wrote: Your question is one many samba users have to deal with. Debian Linux is user supported software, so if you want samba to always be up to date, volunteer to become the samba maintainer for Debian, then you will control you own destiny. If becoming the samba maintainer for Debian does not suit you, that's OK. But now if you want an up to date version of samba for Debian you will need to build your own. Ummm...just to clarify, Eloy and Steve always submit the bedian packaging so you can roll you own deb from the Samba source tarball. See packaging/Debian for details. cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc ISBN 0-672-32269-2 SAMS Teach Yourself Samba in 24 Hours 2ed You can never go home again, Oatman, but I guess you can shop there. --John Cusack - Grosse Point Blank (1997) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE9+h/KIR7qMdg1EfYRAm07AJ9c9NmeYtt1J666M5QiAe25OXjWiwCeJG+1 lP+5MadAWbAZy4FDvIj6m2E= =p4x6 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
JP, (Thanks to Jerry Carter for pointing out the following omission in my last reply to you) You should also be aware that two (2) samba team members actively maintain Samba packaging. You will find it under samba-2.2.7a/packaging/Debian, and you can use this to build a Debian comliant samba package. - John T. On Fri, 13 Dec 2002, Jean-Paul ARGUDO wrote: Hi all, I really know you'll tell me it is not an issue from Samba nor a matter of topic in this list. But. I have problems with oplocks, surely because of my version: Version 2.2.3a-12 for Debian I noticed it all in bug 26128 and posted here precisions, few days ago. Version 2.2.3a-12!!!??? YES, this is the *stable* version from Debian. What would I do? Install newer version (2.2.7,afaik), then corrupt my system? Or wait for Samba team to put 2.2.7 in the stable? For example, in current proposed-updates, samba version proposed is 2.2.3a-12!! I think I'll have to wait a year before 2.2.7 becomes stable, then you'll be supporting only version 2.4 ? :-) I really know again it is *not* the problem of Samba team. But, I think when I read docs always install newest version before asking to support, you put to rubbish all users who havent yet connexion to internet, or ones who just buy brand new RH, Mandrake, Suse, whatever, box, with surely not the latest Samba version in :-( What are my solutions then? Build my own deb package from your cvs? Thats what I'm gonna do finally, corrupting a bit my stable production debian server :-/ I'd really like you give your point of view on this. Thanks a lot for your efforts! -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
Simo Sorce wrote: On Fri, 2002-12-13 at 09:48, Jean-Paul ARGUDO wrote: Hi all, I really know you'll tell me it is not an issue from Samba nor a matter of topic in this list. But. I have problems with oplocks, surely because of my version: Version 2.2.3a-12 for Debian I noticed it all in bug 26128 and posted here precisions, few days ago. Version 2.2.3a-12!!!??? YES, this is the *stable* version from Debian. And it may contain lot of fixes that are in newer samba releases. I'm not saying they do, but I've seen a number of vendors that fixes packages but maintain older version to keep dependencies toward other packeags or such. What Debian actually did was backport the security fixes in 2.2.7 into 2.2.3a-12 (they weren't present in 2.2.3a-6). What would I do? Install newer version (2.2.7,afaik), then corrupt my system? Or wait for Samba team to put 2.2.7 in the stable? with 2.2.7a you will not corrupt your system, however it seem strange debian does not upgrade to 2.2.7a as from 2.2.2-2.2.6 there a possible security problem, have you the security team url in your apt source list? See above. Oddly enough, I got oplock problems when I upgraded from 2.2.3a-6 to 2.2.3a-12, whereupon I filed a bug and downgraded. The Debian maintainer assured me nothing had been done but security backports; so I upgraded again and crossed my fingers. I just noticed I got some oplock errors day before yesterday, so time to downgrade again and watch. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
On Fri, 2002-12-13 at 19:38, Keith G. Murphy wrote: Oddly enough, I got oplock problems when I upgraded from 2.2.3a-6 to 2.2.3a-12, whereupon I filed a bug and downgraded. The Debian maintainer assured me nothing had been done but security backports; so I upgraded again and crossed my fingers. I just noticed I got some oplock errors day before yesterday, so time to downgrade again and watch. I can't not understand with debian cannot update packeges that are in the stable version ... but that's a debian problem not samba related ... -- Simo Sorce - [EMAIL PROTECTED] Xsec s.r.l. via Durando 10 Ed. G - 20158 - Milano tel. +39 02 2399 7130 - fax: +39 02 700 442 399 signature.asc Description: This is a digitally signed message part
Re: [Samba] oplocks and samba 2.2.7
On Fri, 2002-12-13 at 23:24, Keith G. Murphy wrote: Simo Sorce wrote: I can't not understand with debian cannot update packeges that are in the stable version ... but that's a debian problem not samba related ... Well, I think I understand and approve of the reasons: it's so packages can get tested properly before you run them on your 'stable' server. That's fine with development versions, but samba stable is ... well ... stable :-) And they backport security fixes, so you get the best of both worlds, generally. Yes generally it is a really good idea If you want latest features, run 'testing' or 'unstable'. No on my servers I use stable too, it was not a general question, but a specific one toward samba. Samba 2.2.3a has been realeased on february the 6th, they are 10 (ten) months !!! And 2.2.7a contains *lot* of bugfixes that will make also woody users a lot more happy. Simo. -- Simo Sorce - [EMAIL PROTECTED] Xsec s.r.l. via Durando 10 Ed. G - 20158 - Milano tel. +39 02 2399 7130 - fax: +39 02 700 442 399 signature.asc Description: This is a digitally signed message part
Re: [Samba] oplocks and samba 2.2.7
Simo Sorce wrote: On Fri, 2002-12-13 at 23:24, Keith G. Murphy wrote: Simo Sorce wrote: I can't not understand with debian cannot update packeges that are in the stable version ... but that's a debian problem not samba related ... Well, I think I understand and approve of the reasons: it's so packages can get tested properly before you run them on your 'stable' server. That's fine with development versions, but samba stable is ... well ... stable :-) There's (at least) three other things involved here, though: * Because upstream (samba developers) say something is stable may not be good enough for Debian team, since they have to stand behind it * Some of the testing is on the Debian package itself: how well does it integrate into Debian, etc. * Debian is not one entity, but a group of developers; if the Samba maintainer were allowed to shove a new package into stable, that might be OK; but other developers would want to do the same thing, and, sooner or later, stable would get a showstopping problem. I would say that third reason is really important. Stated another way, because Debian is very loosely organized, no one person can decide what can/cannot go into stable; therefore it is governed by policy, which had to govern everyone, and therefore errs on the cautious side. Does that make sense? If you don't like this sort of loosely organized team, which has political problems, you might like another distribution better. With a whole other set of problems. :-) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
On Sat, 2002-12-14 at 00:06, Keith G. Murphy wrote: Simo Sorce wrote: That's fine with development versions, but samba stable is ... well ... stable :-) There's (at least) three other things involved here, though: * Because upstream (samba developers) say something is stable may not be good enough for Debian team, since they have to stand behind it * Some of the testing is on the Debian package itself: how well does it integrate into Debian, etc. * Debian is not one entity, but a group of developers; if the Samba maintainer were allowed to shove a new package into stable, that might be OK; but other developers would want to do the same thing, and, sooner or later, stable would get a showstopping problem. I would say that third reason is really important. Stated another way, because Debian is very loosely organized, no one person can decide what can/cannot go into stable; therefore it is governed by policy, which had to govern everyone, and therefore errs on the cautious side. Does that make sense? If you don't like this sort of loosely organized team, which has political problems, you might like another distribution better. With a whole other set of problems. :-) You got me wrong, I'm perfectly fine with debian, and use it with much joy. I do know debian only vaguely, just I see that sometimes it is really very slow, 10 months is really a lot of time without an upgrade. I'm ok with good scrutiny, but it seem that samba has been forgotten this time :-) Simo. -- Simo Sorce - [EMAIL PROTECTED] Xsec s.r.l. via Durando 10 Ed. G - 20158 - Milano tel. +39 02 2399 7130 - fax: +39 02 700 442 399 signature.asc Description: This is a digitally signed message part
[Samba] oplocks and samba 2.2.7
About two months ago our sysadmin upgraded to samba 2.2.7 and we have not had any oplock problems since. A heartfelt thanks from the University of Wisconsin in Madison to the Samba team for all their hard work. If our hundreds of users understood what was going on behind the scenes, they'd be thanking you too. --- Sam Barasch Computer Systems Support Department of Biostatistics University of Wisconsin Madison -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
On Thu, Dec 12, 2002 at 02:27:26PM -0600, Sam Barasch wrote: About two months ago our sysadmin upgraded to samba 2.2.7 and we have not had any oplock problems since. A heartfelt thanks from the University of Wisconsin in Madison to the Samba team for all their hard work. If our hundreds of users understood what was going on behind the scenes, they'd be thanking you too. Wow - thanks ! I only ever hear about problems people have with oplocks so it's occasionally nice to hear the code actually *does* work :-) :-). Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
Yeah, we've got kind of a big system too - our one samba server provides services for users in three buildings on campus, and no one from our support team (about 7 end-user support staff members) has heard of any oplock problems since our upgrade. It could be that something else has changed, network-infrastructure-wise , but I really doubt it. Anyway, I ask every year for the department to send me to the Samba conference - is it going to be in Germany again? At 08:33 PM 12/12/2002 +, [EMAIL PROTECTED] wrote: On Thu, Dec 12, 2002 at 02:27:26PM -0600, Sam Barasch wrote: About two months ago our sysadmin upgraded to samba 2.2.7 and we have not had any oplock problems since. A heartfelt thanks from the University of Wisconsin in Madison to the Samba team for all their hard work. If our hundreds of users understood what was going on behind the scenes, they'd be thanking you too. Wow - thanks ! I only ever hear about problems people have with oplocks so it's occasionally nice to hear the code actually *does* work :-) :-). Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
On Thu, Dec 12, 2002 at 03:40:27PM -0600, Sam Barasch wrote: Anyway, I ask every year for the department to send me to the Samba conference - is it going to be in Germany again? Yes, Volker is arranging it as he did such a good job last year :-). Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
