On Sunday 23 February 2003 12:25, Buchan Milne wrote: > On Sun, 23 Feb 2003, Paul Misner wrote: > > I would report this in bugzilla, except I haven't been able to get into > > the site today, so it may be down. > > > > After installing RC! yesterday, with both network server and network > > client selected in the install process, I discovered that smb.conf was > > not present. > > > > It sppears that samba-common was not installed, since I can install that > > package and smb.conf is then present as expected. This seems like a > > minor oversight that should be corrected ASAP. > > Please provide the output of 'rpm -qa samba*' (and list which ones you > installed post-install). samba-server requires > samba-common, so it should be impossible to not get an smb.conf if you had > samba-server installed. It seems samba-server is at level 4 in rpmsrate > for file-server entries, so if you chose "Network Computer Server" you > should have got it ... > > Regards, > Buchan
I think I may see the reason for my problem. I have a local copy of both cooker and contrib, and it looks like I may have done an update that got pieces from each of them. I installed samba-common for 2.27a-3 to fix my problem. Looking at the results of the rpm -qa, it seems my update from cooker pulled in the samba-common from contrib for the 3.0 alpha. Odd that I would have gotten only the samba-common package if that was the case, but that would be the easiest explanation for the problem. It seems like it is probably an issue local to my install. Sorry about that. [EMAIL PROTECTED] paul]# rpm -qa samba* samba-common-2.2.7a-3mdk samba-client-2.2.7a-3mdk samba-server-2.2.7a-3mdk samba-doc-2.2.7a-3mdk samba3-common-3.0-0.alpha21.3mdk Paul
