-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sam Morrison wrote: > I just wanted to post my experience with the samba-client > (2.2.6-1.0.pre2.2mdk) package from a clean MDK 9 install: > > * Able to browse samba clients > * Unable to mount samba shares
How were you doing this? > * fstab/netfs wouldn't mount samba shares Could you post your fstab entries, and the results of trying the same from the command line. FYI, komba2 (in KDE) is probably the easiest tool to use. Sorry, this has never broken for me, I don't rely on it, but use it on a number of occasions. Unfortunately I am running cooker here, but it works fine under 9.0 with the shipped RPM. The one issue that is present in pre2 (and thus 9.0) is the fact that smbclient (and thus kio_smb for example) have an off-by-one bug in the directory listing against win9x shares. smbmounting the same share doesn't have this problem. > > Upgraded to samba-client-2.2.6-4mdk.i586.rpm and all is right in the > world. I've checked the changelog and couldn't find any reference to > this problem. Check the upstream (ie samba-2.2.6) changelog, which does list this (the smbclient issue) somewhere. My biggest concern is that stuff like this has happened in > the past. (USB devices, video cards, etc...) > > Recently I took a survey given by Mandrake. It was about our experiences > with Linux/Mandrake/OSS. One of the questions was whether or not the > latest and greatest software should be released in the final distro or > would it be better to release a little older more stable packages. The > more conservative answer to this is to use the more thoroughly tested > package.... There were many bugs in samba-2.2.5 (some specifically relating to printer drivers etc), and our samba-2.2.5 packages already a number of patches to the source. The samba team had given us a commitment to ship 2.2.6 with sufficient time for us to be able to test all functionality (which takes significant effort, since there are many features to samba, and you can't test them all on one box), but unfortunately they had to slip. Thus, you will see that there is an official update to samba-2.2.6 which has just been announced, specifically to handle all these issues. In fact, -4mdk also has some patches (which we didn't manage to get into the 2.2.6 official release, although they have been submitted) to allow smbumount to unmount dead connections. We are very serious about supporting samba on Mandrake, in fact you will notice (if you read the [EMAIL PROTECTED] mailing list) that Sylvestre and I answer most questions which have 'mandrake' in them, we provide RPMS of every samba release for all the distros we can compile on, put RPMS of the latest release for same on the samba.org ftp mirrors (2.2.6 seems not to have made it quite yet), maintain our packaging directory in the samba source so that one can easily build RPMs from a source tarball (try 'cd packaging/Mandrake; sh makerpms.sh' in the samba source). We also have samba3 RPMs that are parallel installable with 2.2.x currently in cooker (and available from my site for 9.0) so that people who need to use features of 3.0 can do that easily. Plus, we provide samba RPMs compiled with LDAP support (including smbldap-tools already setup). We have also provided samba-vscan modules for selected av-software (something I need to test again). Did I say we were serious about samba? http://ranger.dnsalias.com/mandrake/samba http://people.mandrakesoft.com/~staburet/ Oh yes, you will notice that in 9.0, lisa also has an init script, and in some cases (there seems to be a bug introduced by the gprintify scripts) it should work out-the-box. > > I am involved in a project deploying Mandrake on the desktop at a San > Diego, CA based corporation. Mandrake was the one distro that I have had > the best luck with when trying to get end users excited about Linux. I > am committed to promoting Linux, and especially Mandrake, if for no > other reason than to increase the number of Linux users and to change > the perception of Linux on the desktop. However, when I am in a > situation that allows me to use the distro as an example and I am forced > to spend a couple of hours to track down some strange nuance like the > one stated above, I get concerned about what others might be > experiencing while in a similar position as myself. I don't know what problem you are having, but the smbclient issue was posted on Mandrakeforum within a few days of the release. > > Is there any resource to turn to for deploying Mandrake on the desktop > in a corporate environment? MandrakeBizCases has some great war stories, > but I am looking for more of a repository of scripts and tips to get > Mandrake up on its feet ASAP. A lot of the issues we are currently > having is related to the lack of Office software compatibility, a decent > 5250 terminal emulator that doesn't lock up and provides the same > features as IBM's Client Access TE... My point is that I have a lot of > issues, and I'm sure I'm not alone, that I could use some help > addressing. Where would be the best place to start a repository like > this? (Mandrake Linux for Corporate Deployment) Any ideas? > I think there needs to be a new tool, (drakdeploy ?) which pulls together all the stuff that's available, to be able to roll out desktops. All te tools are there for deploying via PXE etc, and Stew did a similar thing with the terminal server. Actually, a combo of terminal server and a deployment tool would be very good (easy migration/setup, deploy terminals, and then migrate terminals to standalone where necessary). In the meantime, you should: # urpmi drakx-autoinstall-doc Which has docs on doing all of this. I don't have suggestions for your other issues. Also, it might help if you tell us more about your infrastructure. For example, Mandrake 9.0 has winbind support (ie join Mandrake 9.0 to a windows domain) allowing you to do all user account management on the windows domain without having to set up a seperate account database for linux. Finally, it may also in future be a good idea not to start deploying a release (of any software) into production until about a month or 6 weeks after release (about when the boxes start shipping), so you can catch all the errata and bugfix updates. Buchan - -- |----------------Registered Linux User #182071-----------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE9x6ZbrJK6UGDSBKcRAuiHAKCorz/tZ3OPRU/XZYCGNe+4NSpToQCgmSCZ 1OUhdjzEoBq2yACQ2eclyKc= =mFGS -----END PGP SIGNATURE-----
