From: Sam M. <pa...@gm...> - 2007-02-26 15:15:45
|
Well if you had of noted your issue clearer I probably wouldn't have done my antinewb attack as from time to time newbs do come in here asking really stupid questions and your statement that Samba != fs mount was taken as one of those moments. I apologise as my attack was unrequired and its good to see you've solved the issue. Statically compiling in smb is a bit of a quirky thing I will admit but given its the easiest way to get to the host it also makes sense. For future reference the kernel config files are available in the source packages. Again, apologies and best of luck :) Sam On 27/02/07, Ryan Underwood <ne...@ic...> wrote: > > On Tue, Feb 27, 2007 at 12:34:22AM +1000, Sam Moffatt wrote: > > > > This is not a generic "I do not know how to use Linux" problem forum, > > if you are new to Linux get a distro on a physical machine or > > VMware/qemu and learn that way. When you have a problem with coLinux, > > please come back and ask it. > > I found the problem, smbfs/cifsfs are built into the kernel statically > instead of as modules, and smbmount was not in my path because my > profile was not being read. (Attempting to setup a common > cygwin/colinux home directory.) > > You can knock off the pretense, by the way - even elite experts such as > yourself should agree that it is unconventional to build these modules > statically, and I could not find a kernel config file anywhere in the > coLinux distribution. > > -- > Ryan Underwood, <ne...@ic...> > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFF4vgiIonHnh+67jkRAmsLAJ9nyMsisEsk9RDV3v2XO4fqiH3GyQCglepA > tQACU4xnq4MjCYZtiNXPydE= > =6nVo > -----END PGP SIGNATURE----- > > |