colinux-users — coLinux users mailing list

[coLinux-users] 0.7.1 pre-release not properly 'shutting down'

[Jason A. <ja...@co...>]

I'm trying out the 0.7.1 pre-release, so far everything is working
perfect except shut down.

I run coLinux as a service on Windows XP, and what happens when
'shutting down' is, the Linux portion seems to shut down fine,
eventually reaching  a safe to power off point, but the colinux-daemon
doesn't properly terminate. Windows thinks the service is still
'shutting down' and it never reaches a 'power off' point. If I manually
kill the colinux-daemon process, Windows then restarts it right away.
Oddness.

I'm not sure what informtion I might provide that's useful, so if
there's anything let me know:
C:\Program Files\coLinux>colinux-daemon.exe
Cooperative Linux Daemon, 0.7.1
Compiled on Mon Jan  1 03:59:29 2007

C:\Program Files\coLinux>ver

Microsoft Windows XP [Version 5.1.2600]

Found in the Application log:
The description for Event ID ( 1 ) in Source ( coLinux ) cannot be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following information
is part of the event: daemon: service control STOP.
.

Jason

[coLinux-users] Be it promulgate

[Jeannine C. <aln...@ma...>]

Alert for you!!



Sym8oL: GTAPCurr Price: $2.36 5 Day Target price: $5Action: Aggresive =
Buy/Hold..



All signs show that this one is going to Explode!!

See bullish news online right now, colinux-users...

[coLinux-users] To byline it query

[Nanette J. <npf...@an...>]

THE BULL REPORT..



S.umbol: GTAPCurrent price: $2.36 5 Day Target price: $5Recommendation: =
very aggresive buy!!


500% profit potential short term!!


GTAP has a nice fresh news, colinux-users...

Re: [coLinux-users] cifsfs/smbfs support?

[George P B. <geo...@gm...>]

Henry Nestler wrote:
> Ryan Underwood wrote:
>   
> After cofs is working, we use cofs to install all the other kernel 
> modules, and nobody has changed the smbfs to module.  I'm not shure, 
> perhaps some peoples with installing a new distri use smbfs for copying 
> files?  Would no risk to break this way.
>
> Is it ok to change it as module?
> What other modules are missed?
> For sample some of NLS?
> We can change something all in the devel version.
>
>   

The main reason for keeping it built-in and not module to this point was
because we didn't have what I'd call an reliable module delivery system
(initrd had problems/issues), with it working better these days, I'd be
more inclined to build-in less, and module more.  However, we still need
to balance size, as we don't want to make coLinux's install so big that
it's difficult to pull down on lower-end connections.  Additionally we
don't want to enable every module for every possible user scenario. 
coLinux is still very much a work in progress, and the last thing we
need to do is add complexities and possible crash-points to the kernel
when we are already working on some tough crashes.

Just my thoughts on the subject.

Re: [coLinux-users] coLinux-0.7.1-20070101 crash my Vista after linux halted.

[George P B. <geo...@gm...>]

Holger Krull wrote:
> Henry Nestler schrieb:
>   
>> Holger Krull wrote:
>>     
>>> Wisut Hantanong schrieb:
>>>       
>>>> I do install coLinux-0.7.1-20070101 with default option and run
>>>>
>>>> "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0"
>>>>
>>>>         
>>> root=/dev/ram0 seems a little odd. What do you expect to be there?
>>>
>>> Usually you would have something like:
>>> root=/dev/cobd0
>>> cobd0=E:\colinux_test\filesystem.img
>>>       
>> initrd=initrd.gz root=/dev/ram0
>> is ok for running a minimal linux from intrd.  The root filesystem is
>> the initrd self.
>>
>>     
> Then i guess, this is the nx-Bit problem.
> Wisut, which processor do you use?
>   
Not really.  I was able to confirm the problem on our Vista test machine
which is pre nx-Bit hardware.
  I was able to duplicate the problem, even after exempting coLinux
binaries from Vista's 'software' nx-Bit functionality. :(  Looks like we
have a real problem here. :(

George

Re: [coLinux-users] cifsfs/smbfs support?

[George P B. <geo...@gm...>]

Sam Moffatt wrote:
> For future reference the kernel config files are available in the
> source packages.
>
>   

Also, 'typically' and as is the case with coLinux's kernel, as of 2.6
the kernel config is available with zcat /proc/config.gz | more

Re: [coLinux-users] MAC Address with Slirp

[Henry N. <Hen...@Ar...>]

René Berber wrote:
> May, Darron wrote:
> 
>> However I have a problem with the MAC address
>> that is being set when I use Slirp. I do not seem to be able to set it
>> and it automatic sets one which is random and different every time I
>> start.
> 
> Setting the MAC address works fine for me, I'm using coLinux 0.7.1 .

MAC for slirp is only usable in builds after date 2006-12-12.

>> one at set-up. Has anyone any ideas how I can get the MAC address
>> changed in colinx. Here is my start up : 
>>  
>> colinux-daemon kernel=vmlinux cofs0=c:\ ^ 
>> cobd0="c:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb" ^ 
>> cobd1="c:\coLinux\swap_device" ^ 
>> mem=128 ^ 
>> eth0=slirp,00:12:F0:76:09:1E,tcp:2222:22/tcp:8080:80 ^ 
>> root=/dev/cobd0 -t nt 
>>  
>> The MAC address is ignored at start up and a random is set, 
> 
> How do you start coLinux?  I use: "F:\coLinux\colinux-daemon.exe -t nt
> @default.conf" in a Windows shortcut, also notice that "-t nt" goes there, not
> in your root line.
> 
> What are those " ^" characters at the end of lines?  Perhaps you have garbage
> (i.e. CR) at the end.

it is better for you, to put all the lines without the cracked at the 
end into a file "colinux.conf", and call
colinux-daemon colinux.conf @colinux.conf

--­
Henry

[coLinux-users] A request for your input.

[<lm...@de...>]

Hello

My name is Lara Thynne and I am a PhD candidate at Deakin University
Australia.  I am currently researching the boundary between work and
leisure activities directly related to the open source community and
open source program development.

As part of this I am running a survey at the following address.

https://dcarf.deakin.edu.au/surveys/oss/

The survey is completely confidential and looks at your views and
motivations to use Open Source software and to participate in the
community.

It will only take a five to ten minutes to complete and your contact
details will not be
recorded. You can withdraw your participation at any stage.

I sincerely apologize for the spammish nature of this e-mail - I
don't mean to abuse this list.  I am trying to collect responses
from as many open source developers and users as possible and a
mailing list like can be the only way to reach many developers.

Thanks again

Lara

P.S The program that I am using is open source, of course
(www.phpsurveyor.org)!

[coLinux-users] CoLinux setup horror again

[Henk A. <al...@co...>]

I needed to upgrade to FC6 on an external USB drive and ran
into a series of typical issues that I encountered with earlier
installations but that I was not able to resolve this time.

1) There is little documentation regarding non DOS devices.
    All examples start with path="\DosDevices\d:\whatever",
    at some point I found that I need to use 
    path="\Device\Harddisk1\Partition2" and so on.
    I can't for the life of me remember where I found this, and
    the Wiki offers no support AFAICT. Does anybody know
    where this comes from so I can understand what I'm doing?
    What base do the indexes have? Ah I just found something 
    in the README.txt, is there more?

2) I want a /etc/fstab that can be used for both dual-booting
    and for colinux. For colinux I need to map /dev/cobd1 to /,
    for dual-booting I need to map /dev/whateverDevice to /.
    Earlier Henry advised me to define an alias and I tried this
    but I could not get it working. Where is the alias syntax
    documented (besides the README.txt)?

3) One extra problem that I have is that this is the first time I set 
    up Fedora with logical volumes. Does colinux support that?
    I expected it to work but it doesn't (for me, yet). I never really 
    used aliases but I think this is what I needed to do without
    logical volumes:
    path="\Device\Harddisk1\Partition2" alias="sdb1"
    I now tried
    path="\Device\Harddisk1\Partition2" alias="VolGroup00/LogVol00"
    This did not work and I'm not sure if I picked the wrong
    alias, wrong disk or whatever. I listed my LVM mappings 
    and /etc/fstab (standard, non-colinux) below.

4) Do I need to execute something like this first:
    for i in 0 1 2 3 4 5 6 7 do mknod /mnt/hd/dev/cobd$i b 117 $i; done
    before I attempt to start colinux?

The number of traps that a non-expert can fall into, increases
geometrically with the number of problems. So even when each
of these questions is easy to answer (let's say 2 answers possible),
the total number of possibilities with 4 questions is 2**4=16.
There is a lot of information on the Wiki but not much that
explains the fundamentals in a systematic way. I browsed the
rest but could not find what I was looking for. The README.txt
appears to be the best reference I found so far but what I could 
use is some tools that show me how my system is configured
and documentation how to configure colinux in a systematic way.

Thanks in advance for any help you can give me,

Henk

LVM mappings:

LVM Volume Groups
  VolGroup00
    LogVol01                  swap   y        896 
    LogVol00    /             ext3   y        37120
Hard drives
  /dev/sda
    /dev/sda1                 ntfs            76011 1      9690
    /dev/sda4                 Foreign         306   9691   9729
  /dev/sdb
    /dev/sdb1   /boot         ext3   y        102   1      13
    /dev/sdb2   VolGroup00    LVM PV y        38052 14     4864

/etc/fstab:

  /dev/VolGroup00/LogVol00 /        ext3   defaults       1 1
  LABEL=/boot              /boot    ext3   defaults       1 2
  devpts                   /dev/pts devpts gid=5,mode=620 0 0
  tmpfs                    /dev/shm tmpfs  defaults       0 0
  proc                     /proc    tmpfs  defaults       0 0
  sysfs                    /sys/fs  sysfs  defaults       0 0
  /dev/VolGroup00/LogVol01 swap     swap   defaults       0 0

Re: [coLinux-users] MAC Address with Slirp

[<r.b...@co...>]

May, Darron wrote:

> I have just set-up colinux for the first time and its up and I'm able t=
o
> run X apps via cygwinx.

What version?

> However I have a problem with the MAC address
> that is being set when I use Slirp. I do not seem to be able to set it
> and it automatic sets one which is random and different every time I
> start.

Setting the MAC address works fine for me, I'm using coLinux 0.7.1 .

[snip]
> one at set-up. Has anyone any ideas how I can get the MAC address
> changed in colinx. Here is my start up :=20
> =20
> colinux-daemon kernel=3Dvmlinux cofs0=3Dc:\ ^=20
> cobd0=3D"c:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb" ^=20
> cobd1=3D"c:\coLinux\swap_device" ^=20
> mem=3D128 ^=20
> eth0=3Dslirp,00:12:F0:76:09:1E,tcp:2222:22/tcp:8080:80 ^=20
> root=3D/dev/cobd0 -t nt=20
> =20
> The MAC address is ignored at start up and a random is set,=20

How do you start coLinux?  I use: "F:\coLinux\colinux-daemon.exe -t nt
@default.conf" in a Windows shortcut, also notice that "-t nt" goes there=
, not
in your root line.

What are those " ^" characters at the end of lines?  Perhaps you have gar=
bage
(i.e. CR) at the end.

And please don't cross-post, if you want help this is the correct list, d=
on't
use the developer's list.
--=20
Ren=E9 Berber

Re: [coLinux-users] WinPcap + wireless can only send packets

[James H. <Jam...@ro...>]

On Wednesday 07 March 2007 12:44, Bruce Pinsky wrote:
> James Hirschorn wrote:
> > I have just installed colinux on Windows XP, and I unsuccessfully tried
> > to use winpcap bridged to my wireless adapter. I am using a Dell Dual
> > Band 1400 Mini-pci card built in to my laptop, which is listed as
> > supported on the WinPcap website.
> >
> > When I open the wireless network connection information in Windows, and
> > ping from colinux, I can see packets being sent from colinux but no
> > packets are being received. Presumably the WEP encryption on the wireless
> > network is not relevant to WinPcap? Any suggestions?
> >
> > I was able to get internet connectivity in colinux using the TAP
> > interface instead.
>
> Manually set the MAC address for the interface in colinux config to match
> the physical MAC address of the adapter.

Thanks. I had done this, but the problem was related:

The fixed MAC -> IP address in the router's DHCP server was the problem (or at 
least things worked after I removed this router setting). 

Is this a known limitation?

James

Re: [coLinux-users] WinPcap + wireless can only send packets

[Bruce P. <be...@wh...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James Hirschorn wrote:
> I have just installed colinux on Windows XP, and I unsuccessfully tried to use 
> winpcap bridged to my wireless adapter. I am using a Dell Dual Band 1400 
> Mini-pci card built in to my laptop, which is listed as supported on the 
> WinPcap website.
> 
> When I open the wireless network connection information in Windows, and ping 
> from colinux, I can see packets being sent from colinux but no packets are 
> being received. Presumably the WEP encryption on the wireless network is not 
> relevant to WinPcap? Any suggestions?
> 
> I was able to get internet connectivity in colinux using the TAP interface 
> instead.
> 

Manually set the MAC address for the interface in colinux config to match
the physical MAC address of the adapter.

- --
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF7voIE1XcgMgrtyYRAj5oAJwJmeSbp68UQpTWkb6/+cwTcXDfbgCeIefR
/D1rFl69HPsEzQWZjiBTTXA=
=zcPq
-----END PGP SIGNATURE-----

[coLinux-users] WinPcap + wireless can only send packets

[James H. <Jam...@ro...>]

I have just installed colinux on Windows XP, and I unsuccessfully tried to use 
winpcap bridged to my wireless adapter. I am using a Dell Dual Band 1400 
Mini-pci card built in to my laptop, which is listed as supported on the 
WinPcap website.

When I open the wireless network connection information in Windows, and ping 
from colinux, I can see packets being sent from colinux but no packets are 
being received. Presumably the WEP encryption on the wireless network is not 
relevant to WinPcap? Any suggestions?

I was able to get internet connectivity in colinux using the TAP interface 
instead.

TIA,
James

[coLinux-users] MAC Address with Slirp

[May, D. <da...@mo...>]

Hi,=20
=20
I have just set-up colinux for the first time and its up and I'm able to
run X apps via cygwinx. However I have a problem with the MAC address
that is being set when I use Slirp. I do not seem to be able to set it
and it automatic sets one which is random and different every time I
start. The problem being that I have software that is fixed to the MAC
address of the hard wired MAC address. I could get another license but I
can't keep changing it. I have tried taking the eth0 down and changing
the MAC address but on coming back up it changes it back to the random
one at set-up. Has anyone any ideas how I can get the MAC address
changed in colinx. Here is my start up :=20
=20
colinux-daemon kernel=3Dvmlinux cofs0=3Dc:\ ^=20
cobd0=3D"c:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb" ^=20
cobd1=3D"c:\coLinux\swap_device" ^=20
mem=3D128 ^=20
eth0=3Dslirp,00:12:F0:76:09:1E,tcp:2222:22/tcp:8080:80 ^=20
root=3D/dev/cobd0 -t nt=20
=20
The MAC address is ignored at start up and a random is set,=20
=20
Many Thanks
=20
Darron

Re: [coLinux-users] Allocation of pty refused by openssh server

[Milandro S. <ex...@ya...>]

Claude Le Dû <ledu.claude@...> writes:

> 
> Colinux 0.7.1 - Fedora Core5 2006.8 from sourceforge - Putty - Xming
> 
> Hi,
> 
> I spend little time to have this set working with Windows XP SP2.
> I added some packages including kdebase, openssh,server-ssh, client-ssh 
> using yum.
> All works fine except one thing I could not fix.
> I cannot get a connexion with a pty with Putty (Putty on Windows or 
> Colinux to openssh on Colinux).
> "Server refused to allocate pty".
> 1) I created all  /dev/pty's with MAKEDEV in the colinux /dev directory 
> but it was not sufficient
> 2) Launching sshd with "-d" option shows that the function "openpty" is 
> not available on the Fedora root-fs (?)
> 
> I tried to find which package brings this libary without succes.
> Can you tell me if I made a mistake? Is there an update to do?
> 
> Thanks
> 
> Claude Le Du
> 
> (for information, in order to have passwords available with Fedora C5 I 
> had also to unistall et reinstall craklib-dicts in the root-fs)
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> 


Hi, 

I had the same error when I try to SSH on coLinux, I've tried MAKEDEV pty and
MAKEDEV ptmx they seems to fix the problem but the problem persisted if I
restart or reboot coLinux, ptmx and pty[0-xx] are again missing in the /dev
folder. Looking around I found out that you can fix this error permanently by
editing /etc/udev/makedev.d/50-udev.nodes, just append ptmx and pty[0-xx] then
restart coLinux. In my case I just appended ptmx and my SSH works.

Regards

[coLinux-users] you predatory at mcdaniel

[Mara F. <egn...@in...>]

Take a look at this ONE...

Sym8oL: ARSSCurr Price: $0.15 5 Day Target price: $0.75Action: Aggresive =
Buy/Hold!

All signs show that this one is going to Explode...

ARSS has a nice fresh news, colinux-users...

Re: [coLinux-users] cifsfs/smbfs support?

[Ryan U. <nem...@ic...>]

On Tue, Feb 27, 2007 at 09:48:03AM +0100, Anders Eriksson C (KI/EAB) wrote:
> > >=20
> > > For future reference the kernel config files are available in the=20
> > > source packages.
> >=20
> Less /proc/config.gz is your friend.

That works, not enabled in Debian kernels so I completely forgot about
that option's existence.

--=20
Ryan Underwood, <ne...@ic...>

Re: [coLinux-users] cifsfs/smbfs support?

[Anders E. C \(KI/EAB\) <and...@er...>]

> >=20
> > For future reference the kernel config files are available in the=20
> > source packages.
>=20
Less /proc/config.gz is your friend.

/A

Re: [coLinux-users] cifsfs/smbfs support?

[Henry N. <Hen...@Ar...>]

Ryan Underwood wrote:
> On Tue, Feb 27, 2007 at 02:00:27AM +1000, Sam Moffatt wrote:
>> Mmm, cifs should be in there as a module, I just checked the latest
>> autobuild and the module was there in it.
> 
> Henry's mail summarizes the problem:
> -----------------------------------------------
> coLinux 0.7.x with kernel 2.6.12:
> # CONFIG_CIFS is not set
> 
> coLinux 0.8.x with kernel 2.6.13, 2.6.14, 2.6.15:
> # CONFIG_CIFS is not set
> 
> coLinux 0.8.x with kernel 2.6.17:
> CONFIG_CIFS=m
> -----------------------------------------------
> 
> I'm not sure why smbfs is compiled in while cifs is built as a module
> though.

smbfs was the first and only way to copy files from Windows host into 
coLinux Guest before cofs and initrd was usabel.

After cofs is working, we use cofs to install all the other kernel 
modules, and nobody has changed the smbfs to module.  I'm not shure, 
perhaps some peoples with installing a new distri use smbfs for copying 
files?  Would no risk to break this way.

Is it ok to change it as module?
What other modules are missed?
For sample some of NLS?
We can change something all in the devel version.

-- 
Henry Nestler

Re: [coLinux-users] cifsfs/smbfs support?

[peter g. <plu...@P1...>]

> I'm not sure why smbfs is compiled in while cifs is built as a module
> though.
smbfs is compiled in because before cofs and the module installing =
initrd (which still seems more trouble than its worth judging from =
reports from people whose crashes go away when they disable it) having =
the ability to mount windows volumes over the network without modules =
was deemed very usefull. Changing it now would mean stuff unexpectedly =
starting to fail on upgrade for a marginal saving in memory.

Re: [coLinux-users] cifsfs/smbfs support?

[Ryan U. <nem...@ic...>]

On Tue, Feb 27, 2007 at 02:00:27AM +1000, Sam Moffatt wrote:
> Mmm, cifs should be in there as a module, I just checked the latest
> autobuild and the module was there in it.

Henry's mail summarizes the problem:
-----------------------------------------------
coLinux 0.7.x with kernel 2.6.12:
# CONFIG_CIFS is not set

coLinux 0.8.x with kernel 2.6.13, 2.6.14, 2.6.15:
# CONFIG_CIFS is not set

coLinux 0.8.x with kernel 2.6.17:
CONFIG_CIFS=3Dm
-----------------------------------------------

I'm not sure why smbfs is compiled in while cifs is built as a module
though.

--=20
Ryan Underwood, <ne...@ic...>

Re: [coLinux-users] cifsfs/smbfs support?

[Henry N. <Hen...@Ar...>]

Hallo,

have grepped the kernel configs.  CIFS is not always enabled.  Think, 
that is your mistake here ;-)

coLinux 0.7.x with kernel 2.6.12:
# CONFIG_CIFS is not set

coLinux 0.8.x with kernel 2.6.13, 2.6.14, 2.6.15:
# CONFIG_CIFS is not set

coLinux 0.8.x with kernel 2.6.17:
CONFIG_CIFS=m

SMB FS is alway enabled as in kernel:
CONFIG_SMB_FS=y

If you need CIFS, should install a coLinux 0.8.0 with kernel 2.6.17 and 
  build date *after* 2006-10-05T19:03:59.  CIFS was enabled on this day.

The last autobuild has CIFS enabled as module:
http://www.henrynestler.com/colinux/autobuild/devel-20070225/

-- 
Henry Nestler

Re: [coLinux-users] cifsfs/smbfs support?

[Sam M. <pa...@gm...>]

Mmm, cifs should be in there as a module, I just checked the latest
autobuild and the module was there in it.

Sam

On 27/02/07, Ryan Underwood <nem...@ic...> wrote:
>
> On Tue, Feb 27, 2007 at 01:15:42AM +1000, Sam Moffatt wrote:
> > 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.
>
> Something else to note, and this is what mislead me initially, if you
> try to use /sbin/mount.cifs instead of smbmount (i.e. because you want
> to use the kernel cifs instead of smbfs), it doesn't work because only
> smbfs and not CIFS is compiled in.  Using CIFS instead of smbfs is
> considered the correct thing to do nowadays since smbfs is unmaintained.
>
> --
> Ryan Underwood, <ne...@ic...>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFF4v6+IonHnh+67jkRAmVWAKC3OqTsk5AOyEuAM5jDStCNBPojlACfY8u9
> umpINE6PBwROMUMSELwUXFg=
> =FOs9
> -----END PGP SIGNATURE-----
>
>

Re: [coLinux-users] cifsfs/smbfs support?

[Ryan U. <nem...@ic...>]

On Tue, Feb 27, 2007 at 01:15:42AM +1000, Sam Moffatt wrote:
> 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 !=3D 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.
>=20
> For future reference the kernel config files are available in the
> source packages.

Something else to note, and this is what mislead me initially, if you
try to use /sbin/mount.cifs instead of smbmount (i.e. because you want
to use the kernel cifs instead of smbfs), it doesn't work because only
smbfs and not CIFS is compiled in.  Using CIFS instead of smbfs is
considered the correct thing to do nowadays since smbfs is unmaintained.

--=20
Ryan Underwood, <ne...@ic...>

Re: [coLinux-users] cifsfs/smbfs support?

[Sam M. <pa...@gm...>]

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-----
>
>