Baslinux mailing list

["James Miller (IA City)" <jamtat AT mailsnare.net>]

I am also an avid MC user, and also got the error message you mention.  My
solution was not especially elegant - but it worked.  I decided to get rid
of the fuller, Slack 7.1 MC and to install the tiny MC package provided by
JP.  This did the trick.  It runs faster than the Slack71 version also.
It may not be compiled with certain features (mouse support? - not sure on
that), but other than this I think it's a better choice than the Slack
version.  For those who have not already installed the Slack version, I
believe JP's MC may install without dependency issues, whereas the Slack
7.1 version did have some dependency issues that required installation of
an additional package (don't remember which at the moment).

James

PS Apparently, the Slack 7.1 version expectsd Samba because it was
compiled with Samba support.

On Sun, 18 May 2003, Constant Brouerius van Nidek wrote:

>
> Being an avid user of midnight commander I discovered that
> at every startup of MC there was an information.
> Always forgot about it because MC works fine but now being
> at cleaning up the system I want to get rid of this info.
>
> after my input mc following message is shown before
> midnight commander fills the screen:
>
> params.c:OpenConfFile() - unable to open configuration file
> "/etc/smb.conf":     No such file or directory
> Can't load /etc/smb.conf - run testparm to debug it
> load_client_codepage: filename
> /usr/lib/samba/codepages/codepage.850 does not exist.
>
> Why does mc expects samba? How to get rid of thsi info?
>
>
> --
>
> " Every little BYTE helps "
>
> NTReader v0.36w(P)/Beta (Registered) in conjunction with Net-Tamer.
>
> _______________________________________________
> BasLinux mailing list
> BasLinux AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/baslinux
>