[EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
>
>On Mon, 2002-03-18 at 11:35, Warly wrote:
>> It only appears when the smb exported name are encoded in 16 bits, if I
>> understood correctly.
>Why it's broke is really not the issue. The fact that it's still broken
>and you shipped it that way is the issue.
Knowing how and why it is broken might help you in figuring out how you could fix it
(by configuration), for example by trying to change character sets, ensuring you are
using the correct nls codepage on the clients etc.
>> There was plenty of time for you, maybe, but in case you did not notice,
>> I did not feel like lazy last days.
>I really don't know what you expect me to say here. Am I supposed to
>apologize for wasting your (collective) time with serious bug reports?
>For pointing out that release schedule or no release schedule, shipping
>this way was a seriously bad decision?
No, but I think you might want to apologise for the tone of your posts. I guess you
may not have considered that people involved in this are between a rock and a hard
place trying to ship a distro in time (according to other contracts) and providing
updates for the security issue of the day (kernel zilb issue), and probably
averaging less sleep than the rest of us (and we are probably all quite busy ...)
The fact that Mandrake will not ship with the one feature you require does not mean
you shouldn't use it (even though we would all like it that way). You seem to have
enough bandwidth and capability to be able to make your own contribution to this
issue (for example, nothing was stopping you from applying the kernel update to a
cooker kernel srpm and recompiling).
>I'm trying to get my company to cough up some support for MandrakeSoft,
>but stuff like this is not making it easy. It makes you look bad and it
>makes me look bad.
You should probably implement your systems, and ensure people are happy with the
system, and believe it is worth an investment, before trying to get them to "cough
up" money.
>I guess there's no help for it now, but please assure me you'll keep
>this in mind come 9.x time. Lie if you have to, even that would make me
>feel better.
Well, the chances are that this issue will be resolved before we have time to
reinstall all our machines with 8.2, since the kernel update is rather critical.
Please remember that this list is for development and debugging, not where people
post their latest wishes and expect the work to be done for them immediately. If you
think about this for a while, I am sure you will agree that it is reasonable for
Mandrake not to want to change the kernel during freeze with minimal time for
testing and QA.
Have you tested Juan's update kernel yet? If you need to, you can always set up a
minimal updates site on one of your internal machines, and require all your users to
run MandrakeUpdate during or after install, or create your own ISOs from the
shipping ISOs, but with the kernel update.
Also remember that you are not the only one who wants a working smbfs. Sylvestre and
I put in quite a bit of effort adding winbind to the samba rpms, and testing, and
with a working smbfs (and pam_mount, for which I have RPMs), winbind can be used to
make a Mandrake box look like a member of a windows domain, and even map smb shares
at login time with the users domain account.
The less time people have to spend answering questions about when something will be
fixed, the more time they can spend fixing it. Nevertheless, thanks for your testing
of samba and Mandrake 8.2, without your posts we might not have found the problem
until after the updates had shipped. Hopefully we will have a stable smbfs soon
enough (thanks to all ivolved, including you and other bug reporters, Sylvestre,
Juan, Warly etc)
Regards,
Buchan
